xetai.store 52 D
🛡️ SEO 50 🤖 GEO 61 ⚡ Perf 43 🏗️ Arch 42

xetai.store — Global SEODiff Score 52/100

xetai.store
📊

xetai.store achieves a 74/100 on the AI-Crawler Reality Index, reflecting above-average readiness for AI-driven discovery. In the developer sector, xetai.store outperforms the average (58), suggesting strong competitive positioning in AI search. The low ghost ratio (5%) confirms that what crawlers see matches what users see — a hallmark of strong SSR implementation. The bloated 50.0× 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.

52
D — Global SEODiff Score
Comprehensive search visibility assessment
Below average — Architecture (42) has the most room for improvement.
🎯 Top Fix: Reduce token bloat (83×) → +5–10 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 25, 2026 · 📋 API
Does your site score higher than xetai.store?
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)61 × 0.40 = 24.4
⚡ Performance (20% weight)43 × 0.20 = 8.6
🏗️ Architecture & Trust (15% weight)42 × 0.15 = 6.3
Weighted sum = 12.5 + 24.4 + 8.6 + 6.3
Global SEODiff Score = 52 (D)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
99
Rendering
avg 93
57
Structure
avg 36
0
Schema
avg 9
75
Tech Stack
avg 63
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 27%
Rank #271658
Aligned
Gap
AI (ACRI)
Top 22%
Score 74/100

xetai.store has balanced Google and AI visibility — both rank roughly in the same tier. ACRI measures technical crawler readiness. Read the methodology →

Why xetai.store ranks here

Tech stackGatsby
Industrydeveloper
RenderingSSR
Schema coverage0 blocks
Token bloat50×+

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

55 chars
Good length

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

150 chars
Good length

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✓ Canonical tag present → index.htm
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✗ HTML lang attribute
  • ✗ Hreflang tags
  • ✓ Googlebot allowed by robots.txt

🌐 Social / OpenGraph

  • ✓ og:title — SDK & API for Video Conference Call & Chat API | Voxeet
  • ✓ og:description — Build the best user experience possible with the clearest audio with Voxeet voice and video chat SDK, live voice call API. Boost your user engagement.
  • ✗ og:image
  • ✓ 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 developer sector, hikkoshizamurai.jp (ACRI: 88) 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 →
xetai.store
48
Your ACRI Score
88
Industry Peer ACRI
AI models prioritize pages with strong semantic structure and schema coverage. hikkoshizamurai.jp has schema coverage of 5 blocks and uses Custom / Proprietary. 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 5%
0% — Safe 50% 100% — Risk
Status Server-Side Rendered (Safe)
Rendering Type SSR

📊 Structure & Information Density Docs

Structure Grade 57/100 — Fair
Structured Elements 76 elements (76 lists, 0 rows, 0 headers)
Total Words780
Raw Density9.7%

🏷️ 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

43
AI Extractability
Medium
Crawl Cost
None
Blocklist Risk
Extractability43/100 — AI models can partially 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

1%
🗑️ 99%
Useful Content (4.9 KB)Bloat (399.2 KB)
Token Bloat Ratio50×+ — Bloated

Multimodal Readiness

Visual Context4% Optimized for Vision
Image Alt Coverage2 / 47 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set
💡Your HTML is 404.0 KB, but only 4.9 KB is text. 1% useful / 99% bloat. AI crawlers have limited context windows (e.g. 128k tokens). This level of bloat (50×+) risks context-window truncation by ChatGPT, Claude, and Gemini. Reduce inline scripts, CSS, hydration payloads, and tracking code.
💡Only 4% of images have alt text. Add descriptive alt attributes so multimodal AI (ChatGPT Vision) can understand your images.

🔥 Structural Entropy Check Research

0 Entropy
Poor Token Bloat: High
Noise Ratio: 98.8% · SNR: 0.01 · Signal: 1245 / Noise: 102183 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

FrameworkGatsby
AI-Readiness Score75/100
ServerLiteSpeed
CDN
HTTP Status200
Load Time2080 ms
Raw HTML Size404.0 KB
Visible Text Size4.9 KB

Performance & Speed

43/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

2080 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

517
DOM nodes
404 KB
HTML payload
Heavy page — consider reducing DOM complexity

🗄️ Cache & CDN

  • ✗ Cache-Control header
  • ✗ CDN cache status
  • ✗ CDN detected

🔬 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

42/100 15 % of Global Score 🟡 Medium Confidence

🗺️ Sitemap & Robots

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

🔗 Linking

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

AI-Verified badge for xetai.store
Pending Audit — score below 80 threshold
<a href="https://seodiff.io/radar/domains/xetai.store" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=xetai.store" 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
48
Single-page score
-2
Consistent readability
Δ delta
Site-Wide ACRI
46
Avg across 2 pages · Range 46–46
Total Words
481
Avg Bloat
286.0×
Page Type ACRI Token Bloat Words Status
https://xetai.store/blog
Poker88 - Login Daftar ID Provider MultiGaming Indonesia
blog 46 300.8× 225
https://xetai.store/contact
Lapak303: Agen Judi Poker Online dengan Pelayanan Terbaik
support 46 271.2× 256
📂
Health by Sub-Directory
Average ACRI and top issues aggregated by URL path prefix
Path Pages Avg ACRI Ghost % Bloat Top Issue
/blog/ 1 46 0% 300.9× High JS Bloat
/contact/ 1 46 0% 271.2× High JS Bloat
🔗
Outbound External Citations
0 unique external domains cited across 2 pages
rebrand.ly ×2
yakiniku-shortlink.site ×1
reebrandly.vip ×1
apoia.org ×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/xetai.store

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

🔗 Similar developer Sites

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
xetai.store (this site) 48 74 Gatsby 83.0× 0
morpher.ru 73 79 Custom / Proprietary 2.9× 0 Compare →
inveniordm.docs.cern.ch 73 80 Custom / Proprietary 2.1× 0 Compare →
apollo.auto 73 80 Custom / Proprietary 1.6× 0 Compare →
search.wolfram.com 73 80 Custom / Proprietary 3.4× 0 Compare →
timetrend.pl 73 80 Express 6.1× 0 Compare →
Compare All 5 Similar Sites →

📊 Semantic Share of Voice

How often would an AI cite xetai.store when users ask about topics in this domain's niche? We run entity queries through our 188k-page search index and measure citation probability.

Analyzing citation landscape…

🩹

Remediation Patches

COPY-PASTE

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

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for xetai.store:

Current Score
74
Projected Score
92
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