knihobot.cz 57 D
🛡️ SEO 42 🤖 GEO 69 ⚡ Perf 28 🏗️ Arch 90

knihobot.cz — Global SEODiff Score 57/100

knihobot.cz
📊

With an ACRI of 85/100, knihobot.cz stands out as one of the highest-performing sites in AI search visibility, outranking 98% of its peers. In the infrastructure sector, knihobot.cz outperforms the average (57), suggesting strong competitive positioning in AI search. Its server-rendered architecture ensures AI crawlers receive complete HTML on first request, a key advantage for extractability. The bloated 50.0× token ratio highlights an urgent need to clean up non-content markup, scripts, and navigation clutter. The site includes 2 schema blocks, providing adequate structured data for basic entity recognition. The site maintains an open-door policy for AI crawlers — GPTBot, ClaudeBot, and other major agents are all allowed.

57
D — Global SEODiff Score
Comprehensive search visibility assessment
Below average — Performance (28) needs urgent attention.
🎯 Top Fix: Reduce token bloat (90×) → +5–10 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 26, 2026 · 📋 API
Does your site score higher than knihobot.cz?
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)42 × 0.25 = 10.5
🤖 AI Readiness / GEO (40% weight)69 × 0.40 = 27.6
⚡ Performance (20% weight)28 × 0.20 = 5.6
🏗️ Architecture & Trust (15% weight)90 × 0.15 = 13.5
Weighted sum = 10.5 + 27.6 + 5.6 + 13.5
Global SEODiff Score = 57 (D)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
99
Rendering
avg 93
82
Structure
avg 35
44
Schema
avg 10
70
Tech Stack
avg 64
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 7%
Rank #66214
Aligned
Gap
AI (ACRI)
Top 2%
Score 85/100

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

Why knihobot.cz ranks here

Tech stackNext.js
RenderingSSR
Schema coverage2 blocks
Token bloat50×+

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

42/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

69 chars
Too long

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

115 chars
Too short

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✓ Canonical tag present → https://knihobot.cz/
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✓ HTML lang attribute → cs
  • ✓ 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

69/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 →
knihobot.cz
67
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 5%
0% — Safe 50% 100% — Risk
Status Server-Side Rendered (Safe)
Rendering Type SSR

📊 Structure & Information Density Docs

Structure Grade 82/100 — Excellent
Structured Elements 223 elements (223 lists, 0 rows, 0 headers)
Total Words1105
Raw Density20.2%

🏷️ Schema Health Docs

Organization Schema ✅ Present
Product / Service Schema ⚠️ Not Found
Total Schema Blocks2 block(s) — Basic (low value for AI)

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

61
AI Extractability
High
Crawl Cost
None
Blocklist Risk
Extractability61/100 — AI models can partially extract answers from this page
Crawl CostHigh (100/100) — expensive for AI crawlers to process
Blocklist RiskNone — 0 of 5 AI crawlers blocked

Token Bloat Research

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

Multimodal Readiness

Visual Context83% Optimized for Vision
Image Alt Coverage5 / 6 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set
💡Your HTML is 696.3 KB, but only 7.8 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.

🔥 Structural Entropy Check Research

0 Entropy
Poor Token Bloat: High
Noise Ratio: 98.9% · SNR: 0.01 · Signal: 1987 / Noise: 176262 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

FrameworkNext.js
AI-Readiness Score70/100
Server
CDN
HTTP Status200
Load Time1430 ms
Raw HTML Size696.3 KB
Visible Text Size7.8 KB

Performance & Speed

28/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1430 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

3350
DOM nodes
696 KB
HTML payload
Heavy page — consider reducing DOM complexity

🗄️ Cache & CDN

  • ✓ Cache-Control header → private, no-cache, no-store, max-age=0, must-revalidate
  • ✗ 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

90/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

  • ✓ Sitemap declared in robots.txt → https://knihobot.cz/feeds/sitemaps/sitemap_cz.xml
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

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

AI-Verified badge for knihobot.cz
Pending Audit — score below 80 threshold
<a href="https://seodiff.io/radar/domains/knihobot.cz" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=knihobot.cz" 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
67
Single-page score
-15
Moderate hidden bloat
Δ delta
Site-Wide ACRI
52
Avg across 2 pages · Range 41–63
🔍
Hidden Bloat Detected

Homepage scores 67, but internal pages average only 52 — a -15-point gap. Blogs, docs, and legacy content are dragging down AI readability site-wide.

Topical Cohesion
4%
Topical Drift
TF-IDF cosine similarity
Total Words
811
Avg Bloat
431.2×
RAG Fractures
1
Ext. Citations
15
⚠️
1 RAG-Chunking Fracture Detected

Poorly formatted tables or pricing grids on 1 page will be split incorrectly during RAG chunking, causing AI models to hallucinate prices and features.

Page Type ACRI Token Bloat Words Status
https://knihobot.cz/blog
Knihobotí blog: novinky, tipy a zajímavosti ze světa knih - knihobot.cz
blog 63 128.3× 719
https://knihobot.cz/contact
Knihobot antikvariát online | vracíme knihy do oběhu - knihobot.cz
pricing 41 734.0× 92 ⚠️ RAG Fracture
🔗
Outbound External Citations
15 unique external domains cited across 2 pages
bookbot.be ×2
instagram.com ×2
bookbot.at ×2
bookbot.de ×2
bookbot.nl ×2
youtube.com ×2
bookbot.sk ×2
bookbot.it ×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/knihobot.cz

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

🔗 Similar infrastructure Sites

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
knihobot.cz (this site) 67 85 Next.js 89.7× 2
mall.hr 67 82 Next.js 89.6× 1 Compare →
eternz.com 68 86 Next.js 89.3× 1 Compare →
bookbot.de 62 81 Next.js 90.0× 2 Compare →
livelo.com.br 66 90 Next.js 90.6× 3 Compare →
pontoslivelo.com.br 66 90 Next.js 90.9× 3 Compare →
Compare All 5 Similar Sites →
🩹

Remediation Patches

COPY-PASTE

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

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 Knihobot?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Knihobot does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Knihobot work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Knihobot."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for knihobot.cz:

Current Score
85
Projected Score
93
Improvement
+8 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