✕Errors 3
✕ errorai-crawler/meta-robots-blockingAI Crawler AccessNo noindex/nosnippet directives blocking AI use
Page is marked noindex — AI engines will not index or cite it
noindex/none removes the page from search indexes, and answer engines that rely on those indexes will never cite it.
FixRemove the noindex/none directive from the meta tag or X-Robots-Tag header.
<meta name="robots">: noindex,nofollow
✕ errortechnical/http-errorTechnical FoundationHTTP status healthy
Page returned HTTP 403
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://stackoverflow.com/questions → HTTP 403
✕ errortechnical/client-renderedTechnical FoundationContent in the initial HTML
Page appears client-rendered — AI crawlers see an empty shell
Only ~0 words of visible text in the initial HTML — likely rendered client-side.
FixUse server-side rendering, static generation or prerendering so the real content is in the first HTML response.
0 words of visible text
⚠Warnings 7
⚠ warningai-crawler/robots-missingAI Crawler Accessrobots.txt present
No robots.txt — AI crawler access is uncontrolled
GET https://stackoverflow.com/robots.txt returned HTTP 418. 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 418 for https://stackoverflow.com/robots.txt
⚠ warningllms-txt/missingllms.txtllms.txt present
No llms.txt found
GET https://stackoverflow.com/llms.txt returned HTTP 404.
FixCreate /llms.txt at the site root: an H1 title, a short blockquote summary, and ## sections linking to your key content.
https://stackoverflow.com/llms.txt → HTTP 404
⚠ warningschema/no-jsonldStructured DataJSON-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-contentCitabilitySubstantive visible text
Thin content — only ~0 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.
0 words
⚠ warningcontent/no-h1CitabilitySingle descriptive H1
No <h1> on the page
The H1 anchors how machines understand and index the page topic.
FixAdd one descriptive <h1> that states what the page is about.
⚠ warningcontent/missing-datesCitabilityVisible 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 FoundationXML 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://stackoverflow.com/sitemap.xml → HTTP 404
ℹHints 10
ℹ hintllms-txt/llms-full-missingllms.txtllms-full.txt companion file
No llms-full.txt found
GET https://stackoverflow.com/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://stackoverflow.com/llms-full.txt → HTTP 404
ℹ hintllms-txt/ai-manifestllms.txtEmerging 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 DataOrganization 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 DataBreadcrumbList 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-headingsCitabilityQuestion-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-authorCitabilityAuthor 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-pointsCitabilityConcrete 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.
ℹ hinttechnical/canonicalTechnical FoundationCanonical link sanity
No canonical link element
Without a canonical, engines pick one themselves — and may consolidate onto the wrong URL.
FixAdd <link rel="canonical" href="…"> pointing at the preferred URL for this page.
ℹ hinttechnical/meta-descriptionTechnical FoundationMeta 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.
ℹ hinttechnical/redirectTechnical FoundationNo unexpected redirect
The URL redirected to a different final URL
Requested https://stackoverflow.com/, ended at https://stackoverflow.com/questions.
FixMake sure redirects are intentional, single-hop and point at the canonical destination.
https://stackoverflow.com/ → https://stackoverflow.com/questions