Key answers are visible in HTML and self-contained
Why it matters
Microsoft's guidance for AI search answers is blunt about where content gets lost: "Don't hide important answers in tabs or expandable menus: AI systems may not render hidden content," keep core information out of PDFs, and avoid key facts that exist only inside images. Bing also recommends self-contained phrasing — "sentences that make sense even when pulled out of context" — because assistants assemble answers from extracted passages. A pricing table that exists only as a screenshot, or a core FAQ answer locked in a PDF, is invisible to the systems deciding whether to cite you. Note what this check is NOT: Google explicitly debunks "chunking" content for AI ("There's no requirement to break your content into tiny pieces … There's no ideal page length"), so this check imposes no word counts, paragraph lengths, or section sizes.
Severity rationale
Low because Bing hedges the consequence ("may not render hidden content") and the failure degrades extraction for affected answers rather than removing the site from AI search.
Remediation
Put core answers in served HTML text. If pricing, specs, or FAQ answers live only in a PDF, an image, or a client-rendered tab panel, add an HTML rendering of the same facts on the page. Prefer self-contained sentences for key claims ("AuditBuffet's Stack Scan runs 25 checks in about 30 seconds" survives extraction; "It runs them in about 30 seconds" does not). Server-rendered disclosure widgets like <details> are fine — the text is in the HTML.
// Instead of an image-only pricing table:
<table>
<caption>Pricing</caption>
<tr><td>Free</td><td>Stack Scan, 25 checks</td></tr>
<tr><td>Pro, $9/mo</td><td>Every Pro audit</td></tr>
</table>
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the GEO Readiness Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- external · bing-geo-guidance — Microsoft — Optimizing Your Content for Inclusion in AI Search Answers
- external · google-ai-optimization-guide — Google — Optimizing your website for generative AI features (chunking mythbust)
Taxons
History
- 2026-04-18·v1.0.0·Initial import from geo-readiness·automated
- 2026-06-10·v1.1.0·Renamed from content-well-chunked and rewritten. The old check imposed word-count and paragraph-length thresholds — the exact "chunking" practice Google's generative-AI guide debunks. New substance, grounded in Microsoft's first-party AI-search guidance: key answers must be visible in served HTML (not PDF-only, not image-only, not client-rendered-hidden) and phrased to stand alone. Severity info → low (Bing documents hidden content as a real extraction failure). Old dotted name and bare slug preserved as aliases.·by geo-first-party-alignment