playhyping.com 51 D
🛡️ SEO 50 🤖 GEO 49 ⚡ Perf 34 🏗️ Arch 79

playhyping.com — Global SEODiff Score 51/100

playhyping.com
📊

At 61/100, playhyping.com falls in the moderate bracket of AI-Readiness, suggesting its content is partially accessible to AI systems but not fully optimized. Within the infrastructure vertical, this places playhyping.com above the industry average of 58 —, suggesting strong competitive positioning in AI search. A ghost ratio of 30% indicates a mixed rendering strategy where core content loads server-side but interactive sections rely on JavaScript. The bloated 44.3× token ratio highlights an urgent need to clean up non-content markup, scripts, and navigation clutter. No structured data was detected, which means AI systems must infer all entities and relationships from raw HTML alone. All major AI bot user-agents (GPTBot, ClaudeBot, CCBot, Google-Extended) are permitted by robots.txt, ensuring broad AI crawler access.

51
D — Global SEODiff Score
Comprehensive search visibility assessment
Below average — Performance (34) needs urgent attention.
🎯 Top Fix: Reduce token bloat (44×) → +5–10 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 25, 2026 · 📋 API
📈 ACRI Trend 2 snapshots
Feb 23 Feb 25
🔔 Recent AI Indexing Activity
No recent changes detected by adaptive crawler.
Does your site score higher than playhyping.com?
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)50 × 0.25 = 12.5
🤖 AI Readiness / GEO (40% weight)49 × 0.40 = 19.6
⚡ Performance (20% weight)34 × 0.20 = 6.8
🏗️ Architecture & Trust (15% weight)79 × 0.15 = 11.8
Weighted sum = 12.5 + 19.6 + 6.8 + 11.8
Global SEODiff Score = 51 (D)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
84
Rendering
avg 93
22
Structure
avg 36
0
Schema
avg 9
55
Tech Stack
avg 63
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 50%+
Rank #683870
-16 pts
Gap
AI (ACRI)
Top 52%
Score 61/100

playhyping.com ranks much higher on Google (Tranco Top 50%+) than in AI search (Top 52%). This is the 'Invisible Giant' pattern — implement the patches above to close the AI gap. ACRI measures technical crawler readiness. Read the methodology →

Why playhyping.com ranks here

Tech stackVue.js
RenderingHybrid
Schema coverage0 blocks
Token bloat44.3×

Fastest improvements

  • Add basic Organization and WebSite JSON-LD to fix “0 schema blocks” (see Schema Coverage).
  • 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

50/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

44 chars
Good length

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

155 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://playhyping.com/fr/
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✓ HTML lang attribute → fr
  • ✓ Hreflang tags
  • ✓ Googlebot allowed by robots.txt

🌐 Social / OpenGraph

  • ✓ og:title — Hyping - Serveur Minecraft Survie & OneBlock
  • ✓ og:description — Rejoins Hyping, le meilleur serveur Minecraft français gratuit en Survie et OneBlock du moment. Une communauté active et fun t’attend dès maintenant !
  • ✓ og:image — preview
  • ✗ twitter:card
📐 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

49/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 →
playhyping.com
36
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.

👻
Shadow Content Detected: 30% of your page token budget is trapped in non-rendered regions (JavaScript-dependent content invisible to AI crawlers). Combined with 44.3x token bloat, AI models are using most of their context window on noise instead of your real content. This dramatically increases hallucination probability — models fill the gap with made-up facts.
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 30%
0% — Safe 50% 100% — Risk
Status Server-Side Rendered (Safe)
Rendering Type Hybrid

📊 Structure & Information Density Docs

Structure Grade 22/100 — Low
Structured Elements 26 elements (26 lists, 0 rows, 0 headers)
Total Words1821
Raw Density1.4%
💡Low structure score (22/100). Your content appears as a wall of text with few structured HTML elements. You have 26 list items, 0 table rows, 0 table headers. Convert features into <ul> lists and data into <table> elements to help AI models extract structured information.

🏷️ Schema Health Docs

Organization Schema ❌ Missing
Product / Service Schema ⚠️ Not Found
Total Schema Blocks0 — No JSON-LD detected

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

30
AI Extractability
Medium
Crawl Cost
None
Blocklist Risk
Extractability30/100 — AI models can barely extract answers from this page
Crawl CostMedium (65/100) — moderate for AI crawlers to process
Blocklist RiskNone — 0 of 5 AI crawlers blocked

Token Bloat Research

2%
🗑️ 98%
Useful Content (11.2 KB)Bloat (485.3 KB)
Token Bloat Ratio44.3× — Bloated

Multimodal Readiness

Visual Context95% Optimized for Vision
Image Alt Coverage19 / 20 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set
💡Your HTML is 496.5 KB, but only 11.2 KB is text. 2% useful / 98% bloat. AI crawlers have limited context windows (e.g. 128k tokens). This level of bloat (44.3×) 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: 97.7% · SNR: 0.02 · Signal: 2868 / Noise: 124240 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

FrameworkVue.js
AI-Readiness Score55/100
Servercloudflare
CDNcloudflare
HTTP Status200
Load Time2614 ms
Raw HTML Size496.5 KB
Visible Text Size11.2 KB

Performance & Speed

34/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

2614 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

1211
DOM nodes
496 KB
HTML payload
Heavy page — consider reducing DOM complexity

🗄️ Cache & CDN

  • ✗ Cache-Control header
  • ✓ CDN cache status → DYNAMIC
  • ✓ CDN detected → cloudflare

🔬 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

79/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

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

🔗 Linking

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

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

Homepage ACRI
36
Single-page score
-3
Consistent readability
Δ delta
Site-Wide ACRI
33
Avg across 1 pages · Range 33–33
Total Words
72
Avg Bloat
154.6×
Page Type ACRI Token Bloat Words Status
https://playhyping.com/blog
Hyping Blog - Everything you need to know about Minecraft
pricing 33 154.6× 72 💰 Pricing
📂
Health by Sub-Directory
Average ACRI and top issues aggregated by URL path prefix
Path Pages Avg ACRI Ghost % Bloat Top Issue
/blog/ 1 33 1% 154.7× Bot Blocked
🔗
Outbound External Citations
0 unique external domains cited across 1 pages
dynmap.playhyping.com ×1
instagram.com ×1
discord.gg ×1
youtube.com ×1
x.com ×1
facebook.com ×1
tiktok.com ×1
🔄 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/playhyping.com

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

🔗 Similar infrastructure Sites

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
playhyping.com (this site) 36 61 Vue.js 44.3× 0
atrssv.dz 61 74 Custom / Proprietary 3.8× 0 Compare →
petropavlovsk-kamchatskiy.gdeetotdom.ru 61 72 Custom / Proprietary 2.1× 0 Compare →
shop.bobmarley.com 61 82 Shopify 11.1× 0 Compare →
brantley.lakesonline.com 61 74 Custom / Proprietary 3.1× 0 Compare →
eye.psdschools.org 61 78 Drupal 5.7× 0 Compare →
Compare All 5 Similar Sites →
🩹

Remediation Patches

COPY-PASTE

Auto-generated code fixes tailored to playhyping.com. 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": "Playhyping",
  "url": "https://playhyping.com",
  "logo": "https://playhyping.com/favicon.ico",
  "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": "Playhyping",
  "url": "https://playhyping.com",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://playhyping.com/search?q={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}
</script>
Reduce Token Bloat
Medium Impact ⏱ 1–2 hrs
Only 2% 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 Playhyping?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Playhyping does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Playhyping work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Playhyping."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for playhyping.com:

Current Score
61
Projected Score
79
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