geolintv0.4.0AI-search readiness audit
https://react.dev/
HTTP 404text/htmlTTFB 101mstotal 1.3srobots.txt 404llms.txt 2002026-09-17 12:55 UTC
Grade B
2 errors·5 warnings·9 hints
36/52 checks passed

Categories

AI Crawler Access
94
1 warning
llms.txt
96
2 hints
Structured Data
90
1 warning · 2 hints
Citability
80
2 warnings · 4 hints
Technical Foundation
62
2 errors · 1 warning · 1 hint

AI crawler access 51/51 allowed

BotPurposerobots.txtAccess
OpenAI
GPTBottraininghonored✓ allowed
OAI-SearchBotsearchhonored✓ allowed
ChatGPT-Useruser-fetchmay bypass✓ allowed
OAI-AdsBotmixedhonored✓ allowed
Anthropic
ClaudeBottraininghonored✓ allowed
Claude-Useruser-fetchhonored✓ allowed
Claude-SearchBotsearchhonored✓ allowed
anthropic-airetiredtrainingunverified✓ allowed
Claude-Webretiredsearchunverified✓ allowed
Perplexity
PerplexityBotsearchhonored✓ allowed
Perplexity-Useruser-fetchmay bypass✓ allowed
Google
Googlebotsearchhonored✓ allowed
Google-Extendedopt-outtraininghonored✓ allowed
Apple
Applebotsearchhonored✓ allowed
Applebot-Extendedopt-outtraininghonored✓ allowed
Meta
Meta-ExternalAgentmeta-externalagenttraininghonored✓ allowed
Meta-WebIndexersearchhonored✓ allowed
Meta-ExternalFetcheruser-fetchmay bypass✓ allowed
facebookexternalhituser-fetchunverified✓ allowed
FacebookBotretiredtrainingunverified✓ allowed
Amazon
Amazonbotmixedhonored✓ allowed
Amzn-SearchBotsearchhonored✓ allowed
Amzn-Useruser-fetchhonored✓ allowed
Mistral AI
MistralAI-Useruser-fetchunverified✓ allowed
MistralAI-Indexsearchunverified✓ allowed
MistralAI-Trainingtrainingunverified✓ allowed
Microsoft
Bingbotsearchhonored✓ allowed
DuckDuckGo
DuckDuckBotsearchhonored✓ allowed
DuckAssistBotuser-fetchhonored✓ allowed
You.com
YouBotsearchhonored✓ allowed
Moonshot AI
KimiBottrainingunverified✓ allowed
Kimi-Useruser-fetchunverified✓ allowed
Alibaba
TongyiBotmixedunverified✓ allowed
Exa
ExaBotsearchunverified✓ allowed
Tavily
TavilyBotsearchunverified✓ allowed
Timpi
Timpibotsearchunverified✓ allowed
ByteDance
Bytespidermixedunverified✓ allowed
Common Crawl
CCBottraininghonored✓ allowed
Cohere
cohere-aiuser-fetchunverified✓ allowed
cohere-training-data-crawlertrainingunverified✓ allowed
Diffbot
Diffbotmixedhonored✓ allowed
Webz.io
Omgilibotomgilibotretiredtraininghonored✓ allowed
webziotraininghonored✓ allowed
Webzio-Extendedopt-outtraininghonored✓ allowed
The Hive
ImagesiftBottraininghonored✓ allowed
Huawei
PanguBottrainingunverified✓ allowed
Kangaroo LLM
Kangaroo Bottrainingunverified✓ allowed
Allen Institute for AI
AI2Bottraininghonored✓ allowed
Ai2Bot-Dolmatraininghonored✓ allowed
NICT
ICC-Crawlertrainingunverified✓ allowed
Velen
VelenPublicWebCrawlertrainingunverified✓ allowed

Findings

✕Errors 2
✕ errortechnical/http-errorTechnical Foundation
HTTP status healthy

Page returned HTTP 404

Crawlers receive the error response, not your content.

FixReturn a 200 with real content; fix the underlying 4xx/5xx or the rules that trigger it.

https://react.dev/ → HTTP 404
✕ errortechnical/client-renderedTechnical Foundation
Content in the initial HTML

Page appears client-rendered — AI crawlers see an empty shell

A JS mount point (id="root"/"app"/"__next"…) is present but only ~21 words of text shipped in the HTML. Crawlers without a JS engine get almost nothing.

FixUse server-side rendering, static generation or prerendering so the real content is in the first HTML response.

21 words of visible text
⚠Warnings 5
⚠ warningai-crawler/robots-missingAI Crawler Access
robots.txt present

No robots.txt — AI crawler access is uncontrolled

GET https://react.dev/robots.txt returned HTTP 404. Bots fall back to "everything allowed", and you have no way to welcome or restrict specific AI crawlers.

FixPublish a /robots.txt that explicitly Allows the AI search bots you want (e.g. OAI-SearchBot, PerplexityBot, Claude-SearchBot).

HTTP 404 for https://react.dev/robots.txt
⚠ warningschema/no-jsonldStructured Data
JSON-LD structured data present

No JSON-LD structured data on the page

AI engines use schema.org markup to identify entities, dates, authors and page types. Without it they fall back to unreliable inference.

FixAdd JSON-LD blocks describing the page (Article, Organization, BreadcrumbList, FAQPage as appropriate).

⚠ warningcontent/thin-contentCitability
Substantive visible text

Thin content — only ~21 words of visible text

Pages with very little extractable text give AI engines nothing to quote; they also correlate with client-rendered shells.

FixExpand the page with substantive, answerable content — explanations, specifics, Q&A.

21 words
⚠ warningcontent/missing-datesCitability
Visible publication/modified date

No machine-readable publication or modified date found

Checked <time datetime>, article:* meta tags and JSON-LD datePublished/dateModified — none present.

FixExpose a date via <time datetime="…">, article:published_time meta or JSON-LD datePublished/dateModified.

⚠ warningtechnical/sitemap-missingTechnical Foundation
XML sitemap discoverable

No sitemap discoverable

No Sitemap directive in robots.txt and /sitemap.xml does not resolve.

FixPublish an XML sitemap at /sitemap.xml and declare it in robots.txt ("Sitemap: https://…/sitemap.xml").

https://react.dev/sitemap.xml → HTTP 404
ℹHints 9
ℹ hintllms-txt/llms-full-missingllms.txt
llms-full.txt companion file

No llms-full.txt found

GET https://react.dev/llms-full.txt returned HTTP 404. The optional full-content companion is absent.

FixConsider publishing /llms-full.txt with your key documentation inlined as markdown.

https://react.dev/llms-full.txt → HTTP 404
ℹ hintllms-txt/ai-manifestllms.txt
Emerging AI manifest files (agents.json, ai.txt)

No emerging AI manifest files found

Checked /agents.json, /ai.txt, /.well-known/ai-plugin.json — all absent. These conventions are early and entirely optional.

FixPrioritize /llms.txt; add agents.json or ai.txt only if they fit your AI distribution strategy.

ℹ hintschema/no-organizationStructured Data
Organization schema present

No Organization schema found

Without entity grounding, engines cannot connect this site to a known organization — weaker trust signals for citation.

FixAdd an Organization JSON-LD block (name, url, logo, sameAs links) at least on the homepage.

ℹ hintschema/no-breadcrumbStructured Data
BreadcrumbList schema present

No BreadcrumbList schema found

Breadcrumbs expose site structure to machines; without them a page floats without context.

FixAdd BreadcrumbList JSON-LD matching the visible breadcrumb trail.

ℹ hintcontent/no-question-headingsCitability
Question-shaped headings

No question-shaped headings (h2/h3 ending in "?")

Question headings map directly onto user prompts and make sections self-contained citable answers.

FixRewrite a few section headings as the actual questions your audience asks.

ℹ hintcontent/no-authorCitability
Author attribution

No author attribution found

No meta[name=author], rel=author, JSON-LD author or author/byline markup — the content looks anonymous.

FixAttribute the content: an author byline, meta[name=author] or a Person in JSON-LD author.

ℹ hintcontent/no-data-pointsCitability
Concrete data points

Few concrete data points found (0 numeric stats)

Percentages, growth figures and quantities give AI engines precise, attributable claims to quote.

FixAdd verifiable numbers — percentages, counts, benchmarks — near the claims they support.

ℹ hintcontent/answer-firstCitability
Page leads with a direct answer

Lead paragraph after the H1 is thin (~4 words)

A teaser or caption-length opener is hard to quote verbatim; engines prefer a self-contained answer they can lift whole.

FixExpand the opening paragraph into a direct, self-contained answer (roughly 40–80 words) before diving into details.

This page doesn’t exist.
ℹ hinttechnical/meta-descriptionTechnical Foundation
Meta description present

No meta description

A 1–2 sentence description gives answer engines a clean, pre-written summary of the page.

FixWrite a meta[name=description] of ~50–160 characters summarizing the page.