thestoryoftexas.com 68 C
🛡️ SEO 36 🤖 GEO 81 ⚡ Perf 80 🏗️ Arch 70

thestoryoftexas.com — Global SEODiff Score 68/100

thestoryoftexas.com
📊

thestoryoftexas.com achieves a 74/100 on the AI-Crawler Reality Index, reflecting above-average readiness for AI-driven discovery. Compared to other infrastructure sites (avg score: 57), thestoryoftexas.com performs above the benchmark, 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. A tight 3.7× token bloat ratio reflects disciplined markup: minimal noise between the crawler and the content it needs. The complete absence of JSON-LD schema is a missed opportunity: even basic Organization markup would improve how AI crawlers understand this domain. Robots.txt grants unrestricted access to the key AI user-agents, which is the strongest starting position for AI visibility.

68
C — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Traditional SEO (36) is your bottleneck.
🎯 Top Fix: Add Organization + WebSite JSON-LD → +5–8 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 26, 2026 · 📋 API
Does your site score higher than thestoryoftexas.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)36 × 0.25 = 9.0
🤖 AI Readiness / GEO (40% weight)81 × 0.40 = 32.4
⚡ Performance (20% weight)80 × 0.20 = 16.0
🏗️ Architecture & Trust (15% weight)70 × 0.15 = 10.5
Weighted sum = 9.0 + 32.4 + 16.0 + 10.5
Global SEODiff Score = 68 (C)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
99
Rendering
avg 93
70
Structure
avg 35
0
Schema
avg 10
50
Tech Stack
avg 64
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 23%
Rank #225702
Aligned
Gap
AI (ACRI)
Top 21%
Score 74/100

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

Why thestoryoftexas.com ranks here

Tech stackCustom / Proprietary
RenderingSSR
Schema coverage0 blocks
Token bloat3.7×

Fastest improvements

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

36/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

38 chars
Good length

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

236 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

  • ✗ Exactly 1 <h1> tag — found 4
  • ✓ Has <h2> headings — found 2
  • ✓ <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 — The Bullock Texas State History Museum
  • ✓ og:description — Welcome to the web site of the Bob Bullock Texas State History Museum. Check out the interactive collection of artifacts and exhibits, educational resources and programs, upcoming events and movie show times on the state's largest IMAX.
  • ✗ 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

81/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 →
thestoryoftexas.com
59
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 70/100 — Good
Structured Elements 76 elements (76 lists, 0 rows, 0 headers)
Total Words523
Raw Density14.5%

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

66
AI Extractability
Low
Crawl Cost
None
Blocklist Risk
Extractability66/100 — AI models can partially extract answers from this page
Crawl CostLow (10/100) — efficient for AI crawlers to process
Blocklist RiskNone — 0 of 5 AI crawlers blocked

Token Bloat Research

27%
🗑️ 73%
Useful Content (9.1 KB)Bloat (24.6 KB)
Token Bloat Ratio3.7× — Lean

Multimodal Readiness

Visual Context100% Optimized for Vision
Image Alt Coverage12 / 12 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set

🔥 Structural Entropy Check Research

32 Entropy
Poor Token Bloat: High
Noise Ratio: 73.1% · SNR: 0.37 · Signal: 2320 / Noise: 6304 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

AI-Readiness Score50/100
ServerApache/2.4.18 (Ubuntu)
CDN
HTTP Status200
Load Time702 ms
Raw HTML Size33.7 KB
Visible Text Size9.1 KB

Performance & Speed

80/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

702 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

420
DOM nodes
34 KB
HTML payload
Lean page — fast for bots and users

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

70/100 15 % of Global Score 🟡 Medium Confidence

🗺️ Sitemap & Robots

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

🔗 Linking

97
internal links
9
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 59/100. Reach 80+ to unlock the green "AI-Verified" badge. Fix the issues below to improve your score.

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

🔗 Similar infrastructure Sites

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
thestoryoftexas.com (this site) 59 74 Custom / Proprietary 3.7× 0
edenred.jp 59 78 Custom / Proprietary 3.7× 0 Compare →
weddinginlove.com 59 71 Custom / Proprietary 3.7× 0 Compare →
llscdn.com 59 80 Custom / Proprietary 3.7× 0 Compare →
vn.ru 59 72 Custom / Proprietary 3.7× 0 Compare →
rizzoli.ro 59 72 Custom / Proprietary 3.7× 0 Compare →
Compare All 5 Similar Sites →
🩹

Remediation Patches

COPY-PASTE

Auto-generated code fixes tailored to thestoryoftexas.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": "Thestoryoftexas",
  "url": "https://thestoryoftexas.com",
  "logo": "https://thestoryoftexas.com/theme/TSHM/apple-touch-icon-57x57.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": "Thestoryoftexas",
  "url": "https://thestoryoftexas.com",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://thestoryoftexas.com/search?q={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}
</script>
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 Thestoryoftexas?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Thestoryoftexas does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Thestoryoftexas work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Thestoryoftexas."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

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

Current Score
74
Projected Score
87
Improvement
+13 pts
Add Organization schema +6 pts
Add WebSite schema +4 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