With only 15/100 on the AI-Readiness Index, claimpepe.xyz is at severe risk of being overlooked by AI-powered search and answer engines. Compared to other infrastructure sites (avg score: 57), claimpepe.xyz is trailing the benchmark, indicating room for competitive improvement. A ghost ratio of 15% indicates a mixed rendering strategy where core content loads server-side but interactive sections rely on JavaScript. Token bloat registers at 7.6× — acceptable, but reducing inline scripts and redundant markup could yield measurable gains. The complete absence of JSON-LD schema is a missed opportunity: even basic Organization markup would improve how AI crawlers understand this domain. A total AI bot blockade means no AI-powered search or answer engine can crawl and index this domain's content.
🧮 Score Transparency — How is this calculated?
📊 ACRI Sub-Scores (AI Readiness Detail)
claimpepe.xyz is more visible to Google than to AI models. There's room to improve AI discoverability to match your search reputation. ACRI measures technical crawler readiness. Read the methodology →
Why claimpepe.xyz ranks here
Fastest improvements
- Allow GPTBot in robots.txt so AI crawlers can access your pages (see Crawl Access).
- Allow ClaudeBot (many assistants rely on it) — blocking it often correlates with “AI invisibility.”
- 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.txtfile 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 →
Traditional SEO
50/100 25 % of Global Score 🟢 High Confidence📝 Title Tag
Optimal range: 30–60 characters for SERP display.
📋 Meta Description
Optimal range: 120–160 characters for snippet control.
🔤 Heading Hierarchy
- ✓ Exactly 1 <h1> tag — found 1
- ✗ Has <h2> headings — found 0
- ✓ <h2> not before <h1>
🔍 Indexability
- ✗ Canonical tag present
- ✓ No noindex directive
- ✓ Meta viewport set
- ✓ HTML lang attribute →
en - ✗ Hreflang tags
- ✓ Googlebot allowed by robots.txt
🌐 Social / OpenGraph
- ✗ og:title
- ✗ og:description
- ✗ og:image
- ✗ 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
65/100 40 % of Global Score 🟡 Medium ConfidenceThis pillar aggregates citation share, hallucination risk, bot access, schema health, and content extractability. The individual diagnostic sections below contribute to this score.
Is AI lying about your brand? This panel measures how likely LLMs are to hallucinate facts when extracting information from your page.
🤖 Bot Access Matrix
Allow: / under User-agent: GPTBot in your robots.txt.👻 Rendering (Ghost Ratio) Docs
📊 Structure & Information Density Docs
🏷️ Schema Health Docs
Schema Coverage Map
📐 AI Efficiency Metrics Docs
Token Bloat Research
Multimodal Readiness
TDM Rights
🔥 Structural Entropy Check Research
🔬 AI-Crawler Simulation
See your website the way AI crawlers do. CSS stripped, structure labeled, content chunked.
Toggle to "AI Agent View" to see what GPTBot, ClaudeBot, and other AI crawlers actually extract from this page.
AI Answer Preview
NEWSee how AI models summarize your site. Left: your actual content. Right: what the LLM extracts and says about you.
🔧 Tech Stack
Performance & Speed
56/100 20 % of Global Score 🟢 High Confidence⏱️ Time to First Byte
Google considers <200 ms "good". AI crawlers may have even shorter timeouts.
📦 Page Weight
DOM nodes
HTML payload
🗄️ Cache & CDN
- ✓ Cache-Control header →
no-store, no-cache, must-revalidate - ✓ CDN cache status →
DYNAMIC - ✓ CDN detected → cloudflare
🔬 Tracker Tax
tracker scripts
third-party domains
token overhead
📐 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
internal links
external links
🔒 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 30/100. Reach 80+ to unlock the green "AI-Verified" badge. Fix the issues below to improve your score.
<a href="https://seodiff.io/radar/domains/claimpepe.xyz" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=claimpepe.xyz" 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 10 pages · Deep-10
| Page | Type | ACRI | Token Bloat | Words | Status |
|---|---|---|---|---|---|
| pricing | 42 | 153.5× | 282 | ✓ | |
| about | 42 | 153.5× | 282 | ✓ | |
| product | 42 | 153.5× | 282 | ✓ | |
| product | 42 | 153.5× | 282 | ✓ | |
| docs | 42 | 153.5× | 282 | ✓ | |
| blog | 42 | 153.5× | 282 | ✓ | |
| social-proof | 42 | 153.5× | 282 | ✓ | |
| support | 42 | 153.5× | 282 | ✓ | |
| support | 42 | 153.5× | 282 | ✓ | |
| integrations | 42 | 153.5× | 282 | ✓ |
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/claimpepe.xyzGet your free API key — 100 requests/month included.
🔗 Similar infrastructure Sites
Domains with a similar tech stack, industry, and AI readiness profile to claimpepe.xyz. Compare side-by-side.
| Domain | ACRI | AI Score | Tech Stack | Token Bloat | Schema | |
|---|---|---|---|---|---|---|
| claimpepe.xyz (this site) | 30 | 15 | Cloudflare Pages | 7.6× | 0 | — |
| x-ua.net | 30 | 61 | Cloudflare Pages | 7.6× | 0 | Compare → |
| lifespanohio.org | 30 | 55 | Cloudflare Pages | 7.7× | 0 | Compare → |
| fiberocity.co.uk | 30 | 61 | Cloudflare Pages | 7.7× | 0 | Compare → |
| gayteen.click | 30 | 61 | Cloudflare Pages | 7.7× | 0 | Compare → |
| dvdtoile.com | 30 | 15 | Cloudflare Pages | 7.8× | 0 | Compare → |
Remediation Patches
COPY-PASTEAuto-generated code fixes tailored to claimpepe.xyz. Copy and paste these into your codebase to improve AI visibility. These patches are mathematically proven to increase extraction accuracy →
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Claimpepe",
"url": "https://claimpepe.xyz",
"logo": "favicon.png",
"sameAs": []
}
</script>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "Claimpepe",
"url": "https://claimpepe.xyz",
"potentialAction": {
"@type": "SearchAction",
"target": "https://claimpepe.xyz/search?q={search_term_string}",
"query-input": "required name=search_term_string"
}
}
</script>
User-agent: GPTBot Allow: / User-agent: ChatGPT-User Allow: /
User-agent: ClaudeBot Allow: / User-agent: anthropic-ai Allow: /
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is Claimpepe?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Add your answer here — describe what Claimpepe does in 1-2 sentences."
}
},
{
"@type": "Question",
"name": "How does Claimpepe work?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Explain the key features and how users interact with Claimpepe."
}
}
]
}
</script>
Projected Impact
ROI EST.If you apply the patches above, here's the estimated improvement for claimpepe.xyz:
*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 →