quackquack.in 77 B
🛡️ SEO 67 🤖 GEO 83 ⚡ Perf 62 🏗️ Arch 100

quackquack.in — Global SEODiff Score 77/100

quackquack.in
📊

With a solid 76/100 ACRI, quackquack.in is well-positioned for AI search — better than 84% of sites in the Radar. In the infrastructure sector, quackquack.in outperforms the average (57), suggesting strong competitive positioning in AI search. While the majority of content is server-rendered, the 15% ghost ratio suggests some content remains invisible to static crawlers. The 7.8× token bloat ratio falls within the normal range, though there is room to trim navigation, footer, and script overhead. The site includes 3 schema blocks, providing adequate structured data for basic entity recognition. Robots.txt grants unrestricted access to the key AI user-agents, which is the strongest starting position for AI visibility.

77
B — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Performance (62) is your bottleneck.
🎯 Top Fix: Monitor weekly to catch regressions early
🔬 Automated SEODiff Assessment · Snapshot: Feb 26, 2026 · 📋 API
Does your site score higher than quackquack.in?
Run the same 40-signal audit on your own domain — free, instant results.
Scan Your Site Free →
🧮 Score Transparency — How is this calculated?
🛡️ Traditional SEO (25% weight)67 × 0.25 = 16.8
🤖 AI Readiness / GEO (40% weight)83 × 0.40 = 33.2
⚡ Performance (20% weight)62 × 0.20 = 12.4
🏗️ Architecture & Trust (15% weight)100 × 0.15 = 15.0
Weighted sum = 16.8 + 33.2 + 12.4 + 15.0
Global SEODiff Score = 77 (B)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
94
Rendering
avg 93
51
Structure
avg 35
46
Schema
avg 10
50
Tech Stack
avg 64
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 8%
Rank #79076
+9 pts
Gap
AI (ACRI)
Top 16%
Score 76/100

quackquack.in shows stronger AI visibility than traditional SEO ranking. Great AI foundation to build on. ACRI measures technical crawler readiness. Read the methodology →

Why quackquack.in ranks here

Tech stackCustom / Proprietary
RenderingHybrid
Schema coverage3 blocks
Token bloat7.8×

Fastest improvements

  • Reduce token bloat (navigation/footer/code) so agents reach your main content faster (see Token Bloat).
  • Create an llms.txt file so AI crawlers can discover your content structure without heavy crawling. Generate llms.txt →
  • Run a full entropy audit to find which DOM regions waste the most tokens. Run Entropy Audit →
🧪

JavaScript Rendering Check

We check what AI crawlers miss when they skip JavaScript execution.

Running headless browser to simulate AI extraction…
🛡️

Traditional SEO

67/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

61 chars
Too long

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

154 chars
Good length

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

  • ✓ Exactly 1 <h1> tag — found 1
  • ✓ Has <h2> headings — found 5
  • ✓ <h2> not before <h1>

🔍 Indexability

  • ✓ Canonical tag present → https://www.quackquack.in/
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✓ HTML lang attribute → en-IN
  • ✗ Hreflang tags
  • ✓ Googlebot allowed by robots.txt

🌐 Social / OpenGraph

  • ✓ og:title — QuackQuack - 100% Free Online Dating Site to Meet Singles
  • ✓ og:description — QuackQuack is a free social networking and online dating site that offers features like sending waves, chat and more. Start meeting new people today!
  • ✓ og:image — preview
  • ✓ twitter:card — summary
📐 How the SEO Pillar score is calculated

SEO Pillar = Title (20 pts) + Meta Desc (20 pts) + Heading Hierarchy (20 pts) + Indexability (20 pts) + Social/OG (20 pts)

Each sub-score is derived from the checks above. Canonical tag, lang attribute, og:image, and a single H1 are the highest-impact items.

🤖

AI Readiness / GEO

83/100 40 % of Global Score 🟢 High Confidence

This pillar aggregates citation share, hallucination risk, bot access, schema health, and content extractability. The individual diagnostic sections below contribute to this score.

🔗

Citation Alternatives

Research
💡
Insight: In the infrastructure sector, safely.co.jp (ACRI: 90) currently has stronger AI extractability. AI models tend to prefer sources with higher semantic structure and schema coverage. Domains with ACRI < 40 see 3.5× more hallucinations. Read the research →
quackquack.in
63
Your ACRI Score
90
Industry Peer ACRI
AI models prioritize pages with strong semantic structure and schema coverage. safely.co.jp has schema coverage of 3 blocks and uses WordPress. Improve your score by implementing the remediation patches below.
📊 Side-by-Side Comparison →
🚨

Hallucination Risk

Research

Is AI lying about your brand? This panel measures how likely LLMs are to hallucinate facts when extracting information from your page.

Analyzing hallucination risk…

🤖 Bot Access Matrix

GPTBot (OpenAI)
Allowed
ClaudeBot (Anthropic)
Allowed
CCBot (Common Crawl)
Allowed
Google-Extended
Allowed
Googlebot
Allowed

👻 Rendering (Ghost Ratio) Docs

Ghost Ratio 15%
0% — Safe 50% 100% — Risk
Status Server-Side Rendered (Safe)
Rendering Type Hybrid

📊 Structure & Information Density Docs

Structure Grade 51/100 — Fair
Structured Elements 89 elements (89 lists, 0 rows, 0 headers)
Total Words1138
Raw Density7.8%

🏷️ Schema Health Docs

Organization Schema ✅ Present
Product / Service Schema ⚠️ Not Found
Total Schema Blocks3 blocks

Schema Coverage Map

2/7 schema types detected
✅ Organization
❌ Product/Service
❌ Breadcrumb
❌ FAQ
❌ Article
✅ WebSite
💡Product / Service schema missing. AI models don't know this is a SaaS product. Add Product or SoftwareApplication schema so AI understands what you offer and can surface pricing/features.
💡BreadcrumbList schema missing. AI cannot understand your site hierarchy or how pages relate to each other.
💡FAQ schema missing. Adding FAQPage schema lets AI models directly extract Q&A pairs for Featured Snippets and chatbot answers.

📐 AI Efficiency Metrics Docs

63
AI Extractability
Medium
Crawl Cost
None
Blocklist Risk
Extractability63/100 — AI models can partially extract answers from this page
Crawl CostMedium (40/100) — moderate for AI crawlers to process
Blocklist RiskNone — 0 of 5 AI crawlers blocked

Token Bloat Research

12%
🗑️ 88%
Useful Content (12.8 KB)Bloat (87.0 KB)
Token Bloat Ratio7.8× — Normal

Multimodal Readiness

Visual Context100% Optimized for Vision
Image Alt Coverage12 / 12 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set

🔥 Structural Entropy Check Research

0 Entropy
Poor Token Bloat: High
Noise Ratio: 87.2% · SNR: 0.15 · Signal: 3279 / Noise: 22269 tokens

🔬 AI-Crawler Simulation

See your website the way AI crawlers do. CSS stripped, structure labeled, content chunked.

🌐
This is what humans see — styled, branded, visual.
Toggle to "AI Agent View" to see what GPTBot, ClaudeBot, and other AI crawlers actually extract from this page.
🤖

AI Answer Preview

NEW

See how AI models summarize your site. Left: your actual content. Right: what the LLM extracts and says about you.

Simulating AI extraction…

🔧 Tech Stack

AI-Readiness Score50/100
Servernginx
CDN
HTTP Status200
Load Time1522 ms
Raw HTML Size99.8 KB
Visible Text Size12.8 KB

Performance & Speed

62/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1522 ms
Slow — bots may time out or deprioritise

Google considers <200 ms "good". AI crawlers may have even shorter timeouts.

📦 Page Weight

715
DOM nodes
100 KB
HTML payload
Lean page — fast for bots and users

🗄️ Cache & CDN

  • ✓ Cache-Control header → no-store, no-cache, must-revalidate
  • ✗ CDN cache status
  • ✗ CDN detected

🔬 Tracker Tax

1
tracker scripts
1
third-party domains
0.0%
token overhead
Minimal tracker load — clean signal for bots
googletagmanager.com
📐 How the Performance Pillar score is calculated

Perf Pillar = TTFB (35 pts) + Page Weight (25 pts) + Cache/CDN (20 pts) + Tracker Tax (20 pts)

TTFB <200 ms = full marks. DOM >3000 or payload >300 KB incurs heavy penalties. Tracker scripts beyond 5 reduce score.

🏗️

Architecture & Trust

100/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

  • ✓ Sitemap declared in robots.txt → https://www.quackquack.in/sitemap.xml
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

95
internal links
3
external links
Good internal linking — helps crawlers discover content

🔒 Security & Trust

  • ✓ HSTS header (Strict-Transport-Security)
  • ✓ Content-Security-Policy header
  • ✓ HTTP status 200 OK (got 200)

♿ Accessibility Signals

  • ✓ HTML lang attribute → en-IN
  • ✓ Meta viewport for mobile
  • ✓ Single H1 for screen readers
📐 How the Architecture Pillar score is calculated

Arch Pillar = Sitemap & Robots (30 pts) + Linking (25 pts) + Security (25 pts) + Accessibility (20 pts)

Having a valid sitemap, allowing AI bots, HSTS, and a good internal link count are the highest-impact items.

🏅 AI-Verified Trust Badge

Your site scores 63/100. Reach 80+ to unlock the green "AI-Verified" badge. Fix the issues below to improve your score.

AI-Verified badge for quackquack.in
Pending Audit — score below 80 threshold
<a href="https://seodiff.io/radar/domains/quackquack.in" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=quackquack.in" alt="AI-Verified by SEODiff" width="280" height="52"></a>

💡 Paste in your site footer, GitHub README, or email signature. Badge updates automatically as your score changes.

🔗 Similar infrastructure Sites

Domains with a similar tech stack, industry, and AI readiness profile to quackquack.in. Compare side-by-side.

Domain ACRI AI Score Tech Stack Token Bloat Schema
quackquack.in (this site) 63 76 Custom / Proprietary 7.8× 3
bijuteriiania.ro 63 74 Custom / Proprietary 7.7× 3 Compare →
museedupatrimoine.fr 63 77 Custom / Proprietary 7.6× 3 Compare →
finsa.com 63 77 Custom / Proprietary 7.6× 3 Compare →
thewillowlabel.com 64 85 Custom / Proprietary 7.8× 3 Compare →
filmnadvd.cz 63 75 Custom / Proprietary 7.3× 3 Compare →
Compare All 5 Similar Sites →
🩹

Remediation Patches

COPY-PASTE

Auto-generated code fixes tailored to quackquack.in. Copy and paste these into your codebase to improve AI visibility. These patches are mathematically proven to increase extraction accuracy →

Add FAQ Schema
Medium Impact ⏱ 10 min
FAQ schema lets AI models directly extract Q&A pairs. This is the easiest way to get featured in AI responses.
html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is Quackquack?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Quackquack does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Quackquack work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Quackquack."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for quackquack.in:

Current Score
76
Projected Score
82
Improvement
+6 pts
Reduce token bloat +3 pts
Add FAQ schema +3 pts

*Estimates based on SEODiff's scoring model. Actual results depend on implementation quality.

📋 Data Export

Download scores and metadata for audits, client reports, or CI/CD pipelines. Exports contain computed metrics only (no copyrighted content).

All data is generated automatically and updated with each crawl. JSON exports contain scores and metadata only (no copyrighted content).

Is this your company?

Monitor your AI visibility score weekly and get alerted when changes happen.

Start Free →

🧭 Self-Diffing (Private Layer)

For owned domains, combine this world snapshot with private drift + regression history.
Template Drift
Track in My Site
Drift → Traffic Impact
In development coming soon
Regression Incidents
Track in My Site
Internal Linking
Deep Audit graph
Semantic Structure
GEO view in Deep Audit
Content Quality
Thin/duplicate tracking

🕒 History

Score over timeAvailable in My Site history
Drift eventsTemplate timeline + incidents
Drift → Revenue AttributionComing soon
Schema/rendering/extractability changesTracked per scan in project history