thisdayinhistory.co shows strong AI visibility with an ACRI of 70/100, outperforming 67% of indexed domains. In the infrastructure sector, thisdayinhistory.co 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 9.0× token bloat ratio falls within the normal range, though there is room to trim navigation, footer, and script overhead. 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.
🧮 Score Transparency — How is this calculated?
📊 ACRI Sub-Scores (AI Readiness Detail)
thisdayinhistory.co ranks much higher on Google (Tranco Top 50%+) than in AI search (Top 33%). This is the 'Visibility Gap' pattern — implementing the recommendations above can help close the AI gap. ACRI measures technical crawler readiness. Read the methodology →
Why thisdayinhistory.co ranks here
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.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
0/100 25 % of Global Score 🟡 Medium 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 0
- ✓ Has <h2> headings — found 20
- ✗ <h2> not before <h1>
🔍 Indexability
- ✗ Canonical tag present
- ✗ No noindex directive
- ✓ Meta viewport set
- ✓ HTML lang attribute →
en-US - ➖ Hreflang tags — N/A (single language site)
- ✓ Googlebot allowed by robots.txt
🌐 Social / OpenGraph
- ✓ og:title — Taming the Salt: Theodore Roosevelt Opens the Roosevelt Dam, Transforming the Arizona Desert
- ✓ og:description — On March 18, 1911, under the scorching Arizona sun, President Theodore Roosevelt stood triumphant before a vast crowd, dedicating a monumental feat of engineering: the Roosevelt Dam. Stretching nearly 350 feet across the Salt River northeast of Phoenix, it was the largest dam in the United States at the time, symbolizing a new era of water control and agricultural prosperity for the arid Southwest. The dam's story began not with construction, but with vision. President Roosevelt, championing the New Nationalism and conservation efforts, saw the potential to transform the American West through controlled water use. The vast, fertile Salt River Valley, however, lacked the consistent water needed for widespread farming. Enter the Roosevelt Dam, a project spearheaded by the Reclamation Service, an agency Roosevelt himself created. Construction, begun in 1905, was a herculean task. Thousands of laborers, including many Mexican immigrants and Native Americans, battled scorching heat, dangerous conditions, and even dynamite mishaps. Their efforts, however, were fueled by the promise of a brighter future for the region. Finally, in 1911, with the dam complete and its reservoir filling, Roosevelt arrived for the grand opening. He threw a symbolic switch, sending water coursing through a canal network for the first time. The crowd erupted in cheers, recognizing the dam as a game-changer. This wasn't just concrete and steel; it was the key to unlocking the potential of the land, transforming parched desert into productive farms and vibrant communities. The impact was immediate and profound. Water flowed to previously barren lands, enabling the cultivation of a wider variety of crops, from citrus trees to cotton. Towns like Mesa and Chandler experienced dramatic population growth, fueled by the agricultural boom. The dam also provided much-needed hydroelectric power, electrifying homes and businesses across the region. But the story of the Roosevelt Dam isn't without its complexities. The project displaced Indigenous communities and relied on cheap, often dangerous, labor. Later concerns arose about environmental impacts downstream, highlighting the need for responsible water management. Despite these challenges, the Roosevelt Dam remains a landmark achievement. It stands as a testament to human ingenuity, the power of collaboration, and the enduring struggle to manage water resources in a dry land. As Arizona continues to grapple with water scarcity in the 21st century, the legacy of the Roosevelt Dam serves as a reminder of both the transformative power of water and the need for thoughtful stewardship of this precious resource. Further Points of Interest: Explore the cultural impact of the dam, like its role in shaping the identity of the Salt River Valley. Discuss the dam's role in shaping water management policies and the ongoing debate about its environmental impact. Highlight the lives of individuals who played pivotal roles in the dam's construction or benefited from its creation. By adding these layers, you can create a richer and more nuanced historical portrait of the Roosevelt Dam and its enduring significance.
- ✓ 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
75/100 40 % of Global Score 🟢 High 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
📊 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
65/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 →
max-age=600, 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
65/100 15 % of Global Score 🟡 Medium 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-US
- ✓ 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 47/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/thisdayinhistory.co" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=thisdayinhistory.co" 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
Homepage scores 47, but internal pages average only 0 — a -47-point gap. Blogs, docs, and legacy content are dragging down AI readability site-wide.
| Page | Type | ACRI | Token Bloat | Words | Status |
|---|---|---|---|---|---|
| pricing | 0 | 0.0× | 0 | ✓ | |
| about | 0 | 0.0× | 0 | ✓ | |
| product | 0 | 0.0× | 0 | ✓ | |
| product | 0 | 0.0× | 0 | ✓ | |
| docs | 0 | 0.0× | 0 | ✓ | |
| blog | 0 | 0.0× | 0 | ✓ | |
| social-proof | 0 | 0.0× | 0 | ✓ | |
| support | 0 | 0.0× | 0 | ✓ | |
| support | 0 | 0.0× | 0 | ✓ | |
| integrations | 0 | 0.0× | 0 | ✓ |
| Path | Pages | Avg ACRI | Ghost % | Bloat | Top Issue |
|---|---|---|---|---|---|
| /products/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /pricing/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /contact/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /about/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /docs/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /faq/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /features/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /blog/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /case-studies/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /integrations/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
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/thisdayinhistory.coGet your free API key — 100 requests/month included.
🔗 Similar infrastructure Sites
Domains with a similar tech stack, industry, and AI readiness profile to thisdayinhistory.co. Compare side-by-side.
| Domain | ACRI | AI Score | Tech Stack | Token Bloat | Schema | |
|---|---|---|---|---|---|---|
| thisdayinhistory.co (this site) | 47 | 70 | WordPress | 9.0× | 0 | — |
| topcinema.media | 72 | 81 | WordPress | 7.7× | 1 | Compare → |
| ero-gazou.jp | 72 | 83 | WordPress | 5.4× | 0 | Compare → |
| taos.org | 72 | 85 | WordPress | 6.9× | 1 | Compare → |
| bbqexperiencecenter.be | 72 | 81 | WordPress | 13.4× | 1 | Compare → |
| aktivioslo.no | 72 | 80 | WordPress | 4.1× | 1 | Compare → |
📊 Semantic Share of Voice
How often would an AI cite thisdayinhistory.co 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-PASTEAuto-generated code fixes tailored to thisdayinhistory.co. 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": "Thisdayinhistory",
"url": "https://thisdayinhistory.co",
"logo": "https://thisdayinhistory.co/wp-content/uploads/2024/08/cropped-icononly-32x32.png",
"sameAs": []
}
</script>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "Thisdayinhistory",
"url": "https://thisdayinhistory.co",
"potentialAction": {
"@type": "SearchAction",
"target": "https://thisdayinhistory.co/search?q={search_term_string}",
"query-input": "required name=search_term_string"
}
}
</script>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is Thisdayinhistory?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Add your answer here — describe what Thisdayinhistory does in 1-2 sentences."
}
},
{
"@type": "Question",
"name": "How does Thisdayinhistory work?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Explain the key features and how users interact with Thisdayinhistory."
}
}
]
}
</script>
Projected Impact
ROI EST.If you apply the patches above, here's the estimated improvement for thisdayinhistory.co:
*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 →