What has to be true before a page can appear in an AI Overview?

Three things, per Google's own documentation: the page must already be crawlable and indexed by Google, eligible to rank for the relevant query in ordinary Search, and the site must be confirmed as included in Search generative AI features inside Search Console. AI Overviews retrieve from Google's core Search index using retrieval-augmented generation and query fan-out — there's no separate index or ranking system to target.

How do you check if your site is included in Search generative AI features?

In Search Console, under the AI features inclusion setting Google documents. This is a distinct check from ordinary indexing status — a page can be indexed and ranking normally while the site itself is still excluded from AI features, so confirming inclusion is a separate step, not something to assume.

Does adding special schema or an AI-specific file improve AI Overview visibility?

No. Google's AI features documentation states directly that no new machine-readable files, AI-specific text formats, or special Schema.org markup are required or specifically rewarded for AI Overview inclusion. Existing structured data (FAQPage, Article) helps the same way it helps ordinary Search — by clarifying page structure — not because it's an AI-specific requirement.

What's a tactic that can actively hurt AI Overview visibility?

Publishing a separate thin page for each way Google's query fan-out might phrase a related question. Google explicitly classifies this pattern as scaled content abuse under its spam policies, which can suppress a site's visibility across ordinary Search results, not just AI features. One thorough, well-structured page covering a topic and its natural variations is the corrective approach.

How to Appear in Google AI Overviews

What has to be true before your page can appear in an AI Overview?#

Three prerequisites, all documented by Google, in order:

The page is crawlable and indexed. AI Overviews retrieve from Google's core Search index — the same one ordinary organic rankings come from. A page that isn't indexed can't be retrieved, generative feature or not.
The page is eligible to rank for the query. Google's retrieval step uses query fan-out — issuing related searches based on the original query — to gather candidate sources, then synthesizes an answer via retrieval-augmented generation (RAG). A page that wouldn't rank for the query or its close variants isn't a candidate source.
The site is confirmed included in Search generative AI features. This is a distinct, explicit setting inside Search Console, separate from ordinary indexing status. Google documents it as a real eligibility gate — a page can be indexed and ranking normally while the site is still excluded from AI features specifically.

Skipping any one of these means the rest of this page's advice has nothing to act on. Confirm inclusion in Search Console before investing in content or structure changes.

What's the highest-leverage technical fix?#

For most sites, it's making content visible without JavaScript execution. AI Overviews use Google's own rendering pipeline, so a site that Google can already render correctly for ordinary Search has already cleared this bar for AI Overviews too — but many sites that pass a basic Googlebot check still have client-rendered sections that don't reliably resolve, especially on category or listing pages. This is exactly what CrawlReady's Crawlability score measures: how much of a page's content reaches a crawler that executes no JavaScript at all, which is the strictest and most common failure case among AI systems generally.

See how the AI Readiness Score is calculated for the full methodology behind that measurement.

What content structure makes a page more likely to be quoted?#

Lead with the direct answer. The first sentence of a section should answer the question the heading asks, in "X is Y" form — that's the shape most likely to survive extraction into a generated summary.
Phrase headings as real questions. A heading like "Configuration" gives a retrieval system nothing to match against a user's query. "How do you configure X?" does.
Make paragraphs self-contained. Retrieval happens at the paragraph or chunk level. A paragraph that depends on "as mentioned above" to make sense will be misquoted or skipped if it's retrieved on its own.
Keep structured data accurate. Existing Schema.org markup — FAQPage, Article — is not a special AI requirement, per Google, but it does clarify page structure for any system parsing the page, human-built or automated.

What's a mistake that actively hurts your chances?#

Treating query fan-out as an instruction to publish one page per phrasing. It's a common instinct — if Google generates variations on a query, the logic goes, build a page for each variation. Google's documentation names this pattern directly as scaled content abuse, a spam policy violation that can suppress visibility across ordinary Search results, not just AI features.

The corrective approach is consolidation, not expansion: one page that answers the core question and its natural variations thoroughly, rather than several thin ones split across near-duplicate URLs.

What should you check first?#

Confirm Search generative AI features inclusion in Search Console.
Confirm the page is indexed and ranking for the target query in ordinary Search — if it isn't, fix that before anything AI-specific.
Check whether your page's content is visible to a crawler that doesn't execute JavaScript.
Check that new or updated pages are reaching Google's index quickly rather than waiting on its normal crawl schedule — see how AI assistants index your site.

Run a free scan to check all of the above on a specific URL.