# Why Pages Are Not Appearing in AI Overviews > The causes of absence from Google AI Overviews in dependency order, what to check for each, what Google documents, and what is not fixable. Source: https://aiseoperth.net.au/guides/not-appearing-in-ai-overviews/ --- Diagnostic guide # Why your pages are not appearing in AI Overviews: a diagnostic order The causes of absence from Google AI Overviews in dependency order: the query does not trigger one, the page is not indexed or reachable, the answer is buried, entity signals are unclear, coverage is thin, corroboration is weak. What to check for each, what Google documents, and what is not fixable. Author Dorian Menard, founder of Search Scope Published 9 September 2026 Reading time 7 min ## Absence is the normal state Most indexed pages never appear in an AI Overview, so absence is not a penalty and rarely has one cause. The causes below are not equally likely, and they depend on each other. Working them in order stops you rewriting content to solve a rendering problem. ## Cause 0: The query does not produce an Overview DOCUMENTED Google shows an AI Overview “when our systems determine that generative AI can be especially helpful”. Many queries do not trigger one, and the set changes. TESTED [Ahrefs](https://ahrefs.com/blog/ai-overviews-reduce-clicks/) found that 99.2% of the keywords that triggered an Overview in its 300,000-keyword sample were informational. A commercial or transactional query may produce no Overview at all, in which case there is nothing to appear in. - **Check:** Search the query from a Perth location, in a fresh session, three times across a fortnight. No Overview on any run means this page’s absence is not a page problem. ## Cause 1: The page is not indexed, not eligible, or not reachable DOCUMENTED “To be eligible to be shown as a supporting link in AI Overviews or AI Mode, a page must be indexed and eligible to be shown in Google Search with a snippet.” A `noindex`, a `nosnippet`, a crawl block, or a page Google has discovered and not indexed is not a candidate. Two variants are common: Google cites the business but picks a different page than the one intended, usually an article rather than a service page; or the intended page is indexed and simply does not rank well enough on the query to be retrieved. Neither is an AI problem. - **Check:** Inspect the URL in Search Console for its index status. Confirm no `noindex` meta or `X-Robots-Tag`, and no `nosnippet` or restrictive `max-snippet`, since Google says “more restrictive permissions will limit how your content is featured”. View the raw source and confirm the content is present without JavaScript, per the [crawler access guide](https://aiseoperth.net.au/guides/ai-crawler-access/). - **Fix time:** Days to weeks for a directive; weeks to months for a rendering architecture. ## Cause 2: The answer is buried INFERRED Answers are composed from passages. A page that reaches its point in paragraph nine competes with pages that reach it in paragraph one, and the section is the unit being used. - **Check:** Count the words before the first sentence that directly answers the query; more than about a hundred is a probable cause. Read the headings: “Our approach” tells a system nothing, “How long does an entity audit take?” tells it what the section contains. - **Fix time:** Hours per page, then weeks for recrawl. ## Cause 3: Structured data contradicts the page DOCUMENTED Google’s guidance is that structured data must match the visible text. Markup asserting a name, address or service the page does not show is a conflict the site created. - **Check:** Read the JSON-LD against the visible content. The [structured data guide](https://aiseoperth.net.au/guides/structured-data-entity-clarity/) lists the five errors. - **Fix time:** Hours, then weeks for recrawl. ## Cause 4: Entity signals are unclear INFERRED A business that resolves to three partial records is a weaker source to name than one that resolves to one. DOCUMENTED Google’s own fundamentals for AI features include keeping Business Profile information current. - **Check:** Search the business name and read the descriptions that come back; if they disagree, the disagreement is in the data. Compare the site footer, the ABN record and the Google Business Profile for name and address. The [consistency audit](https://aiseoperth.net.au/guides/entity-consistency-audit/) is the full inventory. - **Fix time:** Weeks to correct; months for third-party sources to update. ## Cause 5: Coverage is thin or unoriginal DOCUMENTED Google documents query fan-out, issuing related searches across subtopics, and its advice to “provide them with unique, satisfying content”. INFERRED A page restating what is already indexed hundreds of times gives nothing a reason to prefer it, and a single page on a topic gives a fan-out little to retrieve. - **Check:** List the sub-questions a buyer would have around the query and count how many the site answers. Then ask whether anything on the page could not have been written by someone who had read three competitors. - **Fix time:** Months. Content work does not compress. ## Cause 6: Corroboration is weak INFERRED A business that is registered, listed and mentioned elsewhere is a less risky thing to summarise than one that exists only on its own site. This is the slowest layer and the one the business controls least. - **Check:** Search the business name in quotes, excluding its own domain, and count genuine independent mentions. Fewer than a handful for an established business is a finding. - **Fix time:** Many months. ## What is fixable quickly, and what is not Cause Effort Time to any effect Query triggers no Overview None possible n/a Crawl or index directive Low Days to weeks Rendering architecture High Weeks to months Buried answer, weak headings Low Weeks Contradictory markup Low Weeks Entity inconsistency Medium Weeks to months Thin coverage High Months Weak corroboration High Many months ## What is not fixable at all DOCUMENTED Google’s caveat applies to everything above: meeting every requirement “doesn’t mean that Google will crawl, index, or serve its content. Indexing and serving isn’t guaranteed.” Generation varies week to week; a source present one week and absent the next has not necessarily done anything wrong. Chasing individual query appearances is a poor use of budget compared with fixing the structural causes, and no technique documented by Google forces inclusion. ## What is documented and what is inferred - **Documented:** when Overviews show; the eligibility rule; preview controls; fan-out; the no-guarantee caveat; Ahrefs’ informational-intent finding. - **Inferred:** passage-level extraction; entity and corroboration effects; the effort table. - **Not established:** any Perth trigger rate, pending the [planned source study](https://aiseoperth.net.au/research/). ## Related pages - [ Reference Google AI Overviews What Google documents about eligibility. ](https://aiseoperth.net.au/google-ai-overviews/) - [ Guide Can AI crawlers read your site? Cause one in detail. ](https://aiseoperth.net.au/guides/ai-crawler-access/) - [ Guide Entity consistency audit Cause four in detail. ](https://aiseoperth.net.au/guides/entity-consistency-audit/) - [ Guide AI Overviews and organic traffic What appearing is worth. ](https://aiseoperth.net.au/guides/ai-overviews-organic-traffic/) ## Sources 1. [AI features and your website](https://developers.google.com/search/docs/appearance/ai-features), Google Search Central (read 9 September 2026) DOCUMENTED 2. [Find information in faster and easier ways with AI Overviews in Google Search](https://support.google.com/websearch/answer/14901683), Google Search Help (read 9 September 2026) DOCUMENTED 3. [AI Overviews Reduce Clicks by 34.5%](https://ahrefs.com/blog/ai-overviews-reduce-clicks/), Ahrefs, 17 April 2025 (read 9 September 2026) TESTED 99.2% of keywords triggering an AI Overview in the sample were informational. On this page - [Absence is the normal state](#absence-is-the-normal-state) - [Cause 0: The query does not produce an Overview](#cause-0-the-query-does-not-produce-an-overview) - [Cause 1: The page is not indexed, not eligible, or not reachable](#cause-1-the-page-is-not-indexed-not-eligible-or-not-reachable) - [Cause 2: The answer is buried](#cause-2-the-answer-is-buried) - [Cause 3: Structured data contradicts the page](#cause-3-structured-data-contradicts-the-page) - [Cause 4: Entity signals are unclear](#cause-4-entity-signals-are-unclear) - [Cause 5: Coverage is thin or unoriginal](#cause-5-coverage-is-thin-or-unoriginal) - [Cause 6: Corroboration is weak](#cause-6-corroboration-is-weak) - [What is fixable quickly, and what is not](#what-is-fixable-quickly-and-what-is-not) - [What is not fixable at all](#what-is-not-fixable-at-all) - [What is documented and what is inferred](#what-is-documented-and-what-is-inferred) - [Sources](#sources) Evidence labels Claims on this page are labelled DOCUMENTED, OBSERVED, TESTED, INFERRED or HYPOTHESIS. [What the labels mean](https://aiseoperth.net.au/methodology/#evidence-labels). Published by Search Scope AI SEO Perth is published by Search Scope, a Perth SEO consultancy founded by Dorian Menard. Search Scope provides commercial SEO and AI search optimisation services; this website is maintained as its specialist Perth AI search research and reference publication. [Search Scope](https://searchscope.com.au/)