ampproject.org 54 D
🛡️ SEO 35 🤖 GEO 61 ⚡ Perf 49 🏗️ Arch 76

ampproject.org — Global SEODiff Score 54/100

ampproject.org
📊

The AI-Readiness profile for ampproject.org is strong: an ACRI of 73/100 places it ahead of 75% of domains in the index. Within the infrastructure vertical, this places ampproject.org above the industry average of 58 —, suggesting strong competitive positioning in AI search. The low ghost ratio (10%) confirms that what crawlers see matches what users see — a hallmark of strong SSR implementation. A 26.4× token bloat ratio means crawlers must process significantly more tokens to reach the actual content — a drag on extraction efficiency. Minimal structured data (1 block) limits the site's ability to communicate entity relationships to AI systems. Robots.txt grants unrestricted access to the key AI user-agents, which is the strongest starting position for AI visibility.

54
D — Global SEODiff Score
Comprehensive search visibility assessment
Below average — Traditional SEO (35) needs urgent attention.
🎯 Top Fix: Reduce token bloat (26×) → +5–10 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 26, 2026 · 📋 API
📈 ACRI Trend 26 snapshots
Feb 21 Feb 26
🔔 Recent AI Indexing Activity
No recent changes detected by adaptive crawler.
Does your site score higher than ampproject.org?
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)35 × 0.25 = 8.8
🤖 AI Readiness / GEO (40% weight)61 × 0.40 = 24.4
⚡ Performance (20% weight)49 × 0.20 = 9.8
🏗️ Architecture & Trust (15% weight)76 × 0.15 = 11.4
Weighted sum = 8.8 + 24.4 + 9.8 + 11.4
Global SEODiff Score = 54 (D)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
97
Rendering
avg 93
55
Structure
avg 36
2
Schema
avg 9
75
Tech Stack
avg 63
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 0.1%
Rank #294
+25 pts
Gap
AI (ACRI)
Top 25%
Score 73/100

ampproject.org punches above its weight in AI — AI visibility exceeds Google ranking. This is a competitive moat worth protecting. ACRI measures technical crawler readiness. Read the methodology →

Why ampproject.org ranks here

Tech stackNetlify
RenderingHybrid
Schema coverage1 blocks
Token bloat26.4×

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

35/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

85 chars
Too long

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

199 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

  • ✗ Exactly 1 <h1> tag — found 7
  • ✗ Has <h2> headings — found 0
  • ✓ <h2> not before <h1>

🔍 Indexability

  • ✓ Canonical tag present → https://amp.dev/index-2021/
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✓ HTML lang attribute → en
  • ✓ Hreflang tags
  • ✓ Googlebot allowed by robots.txt

🌐 Social / OpenGraph

  • ✓ og:title — AMP - a web component framework to easily create user-first web experiences
  • ✗ og:description
  • ✓ og:image — preview
  • ✓ twitter:card — summary_large_image
📐 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

61/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 →
ampproject.org
49
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 10%
0% — Safe 50% 100% — Risk
Status Server-Side Rendered (Safe)
Rendering Type Hybrid

📊 Structure & Information Density Docs

Structure Grade 55/100 — Fair
Structured Elements 52 elements (52 lists, 0 rows, 0 headers)
Total Words567
Raw Density9.2%

🏷️ Schema Health Docs

Organization Schema ❌ Missing
Product / Service Schema ⚠️ Not Found
Total Schema Blocks1 block(s) — Basic (low value for AI)

Schema Coverage Map

0/7 schema types detected
❌ Organization
❌ Product/Service
❌ Breadcrumb
❌ FAQ
❌ Article
❌ WebSite
💡Organization schema missing. AI models cannot identify your brand entity. Without it, your brand won't appear in Knowledge Panels or be associated with your content.
💡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.
💡WebSite schema missing. Add WebSite + SearchAction so Google can generate a Sitelinks Search Box for your brand in AI results.

📐 AI Efficiency Metrics Docs

45
AI Extractability
Medium
Crawl Cost
None
Blocklist Risk
Extractability45/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

3%
🗑️ 97%
Useful Content (5.1 KB)Bloat (129.3 KB)
Token Bloat Ratio26.4× — Heavy

Multimodal Readiness

Visual Context100% Optimized for Vision
Image Alt Coverage1 / 1 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set
💡Your HTML is 134.4 KB, but only 5.1 KB is text. 3% useful / 97% bloat. AI crawlers have limited context windows (e.g. 128k tokens). This level of bloat (26.4×) risks context-window truncation by ChatGPT, Claude, and Gemini. Reduce inline scripts, CSS, hydration payloads, and tracking code.

🔥 Structural Entropy Check Research

0 Entropy
Poor Token Bloat: High
Noise Ratio: 96.2% · SNR: 0.04 · Signal: 1304 / Noise: 33096 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…
🧠

The LLM Interpretation

AI-VERIFIED

A local LLM (mlx-community/Qwen2.5-7B-Instruct-4bit) analyzed the extracted content of ampproject.org and produced this structured business intelligence. Fields marked SEMANTIC VOID indicate information the AI could not find — a critical gap in your site’s machine-readability.

Core Offering
Build and optimize AMP pages for fast, discoverable, and interactive web experiences.
Target Audience
Web developers, content creators, PWA builders
Pricing Model
Free (tutorial and guide content)
🏆 Competitive Moat
Comprehensive guide and tutorial content for AMP development.
📊 Content Depth
7/10
🔄 Programmatic SEO Signals
Recent Guides & Tutorials
⚡ Key Pain Points
• No specific technical issues observable in this text.
Model: mlx-community/Qwen2.5-7B-Instruct-4bit · Analyzed: 2026-02-27 · Data extracted from the site’s main content via strict JSON prompting.

🔧 Tech Stack

FrameworkNetlify
AI-Readiness Score75/100
ServerNetlify
CDNnetlify
HTTP Status200
Load Time2287 ms
Raw HTML Size134.4 KB
Visible Text Size5.1 KB

Performance & Speed

49/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

2287 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

768
DOM nodes
134 KB
HTML payload
Moderate weight — acceptable for most scenarios

🗄️ Cache & CDN

  • ✓ Cache-Control header → public,max-age=604800,stale-while-revalidate=86400
  • ✗ CDN cache status
  • ✓ CDN detected → netlify

🔬 Tracker Tax

0
tracker scripts
0
third-party domains
0.0%
token overhead
Minimal tracker load — clean signal for bots
📐 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

76/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

  • ✗ Sitemap declared in robots.txt
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

51
internal links
31
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
  • ✓ 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 49/100. Reach 80+ to unlock the green "AI-Verified" badge. Fix the issues below to improve your score.

AI-Verified badge for ampproject.org
Pending Audit — score below 80 threshold
<a href="https://seodiff.io/radar/domains/ampproject.org" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=ampproject.org" 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.

� Deep Crawl Analysis 2 pages · Deep-10

Homepage ACRI
49
Single-page score
+16
Subpages outperform homepage
Δ delta
Site-Wide ACRI
66
Avg across 2 pages · Range 64–67
Topical Cohesion
1%
Topical Drift
TF-IDF cosine similarity
Total Words
1147
Avg Bloat
54.6×
Page Type ACRI Token Bloat Words Status
https://ampproject.org/docs
AMP Websites Guides & Tutorials - amp.dev
docs 67 60.0× 538
https://ampproject.org/case-studies
Success Stories - amp.dev
social-proof 64 49.2× 609
📂
Health by Sub-Directory
Average ACRI and top issues aggregated by URL path prefix
Path Pages Avg ACRI Ghost % Bloat Top Issue
/docs/ 1 67 0% 60.0× High JS Bloat
/case-studies/ 1 64 0% 49.2× High JS Bloat
🔗
Outbound External Citations
0 unique external domains cited across 2 pages
openjsf.org ×2
trademark-policy.openjsf.org ×2
terms-of-use.openjsf.org ×2
bylaws.openjsf.org ×2
github.com ×2
youtube.com ×2
cdn.ampproject.org ×2
trademark-list.openjsf.org ×2
🔄 Re-Crawl & Update 📡 Track this Domain

Scores update automatically each month. Create a free account for on-demand re-crawls (3/month free).

🔌 API Access

Pull this data programmatically. All sub-page metrics are available via our public API.

curl https://seodiff.io/api/v1/deep10/domain/ampproject.org

Get your free API key — 100 requests/month included.

🔗 Similar infrastructure Sites

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
ampproject.org (this site) 49 73 Netlify 26.4× 1
de.hudsonreed.com 74 85 Express 12.1× 2 Compare →
digitaldeckcovers.com 74 79 Express 3.2× 1 Compare →
coko1.ru 74 81 WordPress 7.0× 1 Compare →
gpstrategies.com 74 86 WordPress 5.4× 1 Compare →
heartlandferry.jp 74 90 WordPress 2.8× 1 Compare →
Compare All 5 Similar Sites →
🎭

Bait & Switch Delta

A 2 PAGES

Compares your homepage rendering quality with inner pages. A high drift score means AI crawlers see a polished homepage but degraded inner content — the "bait & switch" that erodes trust.

67
Homepage ACRI
64
Inner Avg ACRI
+3
ACRI Delta
20%
Homepage Ghost
40%
Inner Avg Ghost
8
Drift Score [?]
Worst Inner Pages
64 40% social-proof https://ampproject.org/case-studies
🛡️

E-E-A-T Trust Signals

F 0/100

Trust indicators extracted from surface pages. These signals help AI systems verify your site's Experience, Expertise, Authoritativeness, and Trustworthiness.

Physical Address
Phone Number
Email Contact
About Page
Contact Page
Privacy Policy
Terms of Service
Named Leadership
🔗

Citation Profile

14 DOMAINS

Outbound citation patterns across surface-crawled pages. Sites that cite diverse, authoritative sources signal higher E-E-A-T to AI systems.

28
Total Links
14
Unique Domains
14.0
Avg/Page
50%
Diversity
bylaws.openjsf.org privacy-policy.openjsf.org linuxfoundation.org blog.amp.dev youtube.com github.com policies.google.com twitter.com terms-of-use.openjsf.org cdn.ampproject.org
🏘️ Outbound Neighborhood Trust Avg Trust: 32.2

AI trust scores for the domains ampproject.org links to. Citing high-trust sources lifts your own credibility signal.

🩹

Remediation Patches

COPY-PASTE

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

Add Organization JSON-LD
High Impact ⏱ 5 min
AI models cannot identify your brand entity without Organization schema. This is the #1 fix for AI visibility.
html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Ampproject",
  "url": "https://ampproject.org",
  "logo": "https://ampproject.org/static/img/favicon.png",
  "sameAs": []
}
</script>
Add WebSite + SearchAction JSON-LD
High Impact ⏱ 5 min
Enables the Sitelinks Search Box in Google and allows AI to understand your site structure.
html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Ampproject",
  "url": "https://ampproject.org",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://ampproject.org/search?q={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}
</script>
Reduce Token Bloat
Medium Impact ⏱ 1–2 hrs
Only 3% of your HTML is useful content. AI crawlers waste context window tokens on bloat.
html
<!-- Move inline CSS to external stylesheets -->
<link rel="stylesheet" href="/css/main.css">

<!-- Move inline scripts to external files with defer -->
<script src="/js/app.js" defer></script>

<!-- Remove duplicate navigation blocks -->
<!-- Keep only ONE <nav> in the <header> -->

<!-- Ensure <main> wraps your primary content -->
<main>
  <!-- Your content here — this is what AI sees first -->
</main>
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 Ampproject?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Ampproject does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Ampproject work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Ampproject."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for ampproject.org:

Current Score
73
Projected Score
91
Improvement
+18 pts
Add Organization schema +6 pts
Add WebSite schema +4 pts
Reduce token bloat +5 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