Google AI Overviews
Why Google May Rank Your Page but Leave It Out of AI Overviews
A page can rank in normal Google Search and still be a poor source for an AI Overview. That does not automatically mean the page is bad. It may mean the query does not trigger an AI Overview, the page is not snippet-eligible, the answer is not clear enough, or Google has better supporting sources for that specific question.

Direct answer: why can a ranked page be left out of AI Overviews?
A ranked page may be left out of Google AI Overviews because ranking is not the same as being useful source material for an AI answer. The page must be indexed, snippet-eligible, crawlable, clearly answer the query, provide enough evidence, and fit the specific AI Overview Google decides to generate.
This is one of the most useful Search Console questions for a small business owner: "We are visible, so why are we not in the AI answer?" The wrong response is to publish five more thin articles around the same topic. The better response is to diagnose the page.
Google says the same foundational SEO best practices remain relevant for AI features, and that there are no special AI Overview requirements beyond eligibility for Search and snippets. It also says AI Overviews only trigger when Google systems decide they add value beyond classic Search. In practical terms, a ranking can open the door, but it does not force Google to use your page as a supporting link.
If your page already ranks, treat that as evidence that something is working. Then look for the missing layer: page clarity, answer usefulness, crawl controls, internal links, source support, freshness, or a mismatch between the page and the AI-generated answer.
Ranking and AI Overview inclusion are not the same job
Classic SEO often starts with a keyword, a URL, and a ranking position. That still matters. But AI Overviews and AI Mode can assemble answers from broader subtopics, related searches, and supporting pages. Google describes this as a query fan-out technique, where multiple related searches may be used to develop a response.
That changes the diagnostic. Your page might rank for "AI search visibility checklist" but be skipped when the AI Overview is answering a more specific question like, "What should a local service business fix before AI search tools can trust its website?" The ranking page may be close to the topic, but not specific enough for the generated answer.
This is why I separate broad optimization from page diagnosis. The broader guide to Google AI Overviews optimization explains the overall approach. This article is narrower. It is about the frustrating middle case: your page has search visibility, but Google still chooses other sources when it builds an AI answer.

What Google says, translated for an SMB owner
Google's AI features guidance gives business owners a useful boundary. To be eligible as a supporting link in AI Overviews or AI Mode, a page must be indexed and eligible to appear in Google Search with a snippet. There is no special schema or machine-readable AI file that guarantees inclusion.
That means the first checks are ordinary but important: can Google crawl the page, is it indexable, can it show a snippet, is the important content visible in text, and does the structured data match what users can actually see?
Google's public guidance also warns against using generative AI to create many pages without adding real value. That matters here. If a business reacts to AI Overview exclusion by creating five near-duplicate pages, the site can become less useful, not stronger. Better source material usually comes from sharper answer blocks, original examples, real buyer questions, and evidence that supports the claim.
For a practical background on the broader discipline, see the Generative Engine Optimization guide. The same operating idea applies here: make the business findable, understandable, citeable, and trustworthy.
The diagnostic framework: eligible, relevant, useful, trusted
I would not start with "How do we get into the AI Overview?" I would start with four more grounded questions.
Eligible: can the page even be used?
Check whether the page returns HTTP 200, is indexable, is not blocked by robots.txt or CDN rules, has no accidental noindex tag, and is eligible for snippets. If preview controls such as nosnippet or very short max-snippet rules are active, you may be limiting what Google can show from the page.
Also check whether the page is internally linked from relevant pages. A page that exists but is buried has less context. Internal links help people and search systems understand why the page matters.
Relevant: does the page match the question being answered?
A page can rank for a head term and still miss the exact buyer question. AI Overviews often appear around more complex questions. If the page answers "what is AI search visibility" but the AI Overview answers "how should an accounting firm prove expertise in AI search," the page may be too broad.
This is where the work overlaps with how AI search engines choose sources. The source has to fit the answer, not just the keyword.
Useful: is there extractable answer material?
Look for practical source blocks: direct answer, definition, checklist, comparison table, process steps, constraints, FAQ, examples, and next actions. A polished page that says "we help businesses improve visibility" is weaker than a page that explains what to check, why it matters, and what the owner should do next.
Trusted: why should this page be believed?
Add visible reasons to trust the page: author experience, updated date, specific business examples, source links for technical claims, consistent service descriptions, and related pages that support the topic. Do not invent data or dramatic case studies. A clear example is more credible than a big promise.

Checklist: diagnose one ranked page
AI Overview diagnostic checklist
- Confirm the URL is indexed and eligible to appear in Google Search with a snippet.
- Check robots.txt, noindex, nosnippet, data-nosnippet, and max-snippet settings.
- Confirm the main answer is visible as normal text, not hidden in an image or script-only component.
- Rewrite the opening so the buyer, problem, service, and practical answer are clear in the first screen.
- Add a 40-60 word direct answer to the specific question the page should support.
- Add one table, checklist, or process section that helps a buyer make a decision.
- Add one concrete SMB example with roles, workflow, constraint, and next step.
- Add internal links from relevant supporting posts and the GEO hub.
- Add credible source links for technical claims, especially Search, privacy, AI features, or measurement claims.
- Update the author note, visible date, FAQ, and FAQPage schema where appropriate.
- Track Search Console and AI visibility patterns over several weeks, not one prompt on one day.
Decision table: what to fix first
| What you see | Likely reason | Best first move |
|---|---|---|
| The page ranks, but no AI Overview appears for the query. | Google may not think an AI Overview is additive for that search. | Do not force a page rewrite. Track the query set and improve clarity where buyers need more help. |
| An AI Overview appears, but competitors are linked instead. | Competitor pages may answer the specific sub-question more clearly. | Compare the cited pages and add sharper answer blocks, examples, FAQ, and proof. |
| Your page is broad and ranks for several related queries. | It may be too general to support a detailed AI Overview answer. | Create one distinct supporting section or article only if it owns a real buyer question. |
| The page has strong content but weak internal links. | Google may have less site context for why this page matters. | Add natural internal links from the hub, related guides, and service pages. |
| You cannot see generative AI data in Search Console. | The report may not be rolled out to your property or the site may lack enough impressions. | Use normal Search Console data, analytics, and repeatable prompt tests until the report is available. |

US SMB example: a local HVAC company
Imagine a small HVAC company near Columbus. Its heat pump replacement page ranks on page one for a few normal Search queries, but when Google shows an AI Overview for "how to choose a heat pump replacement contractor," the page is not linked.
The owner might assume the ranking should be enough. It probably is not. The page says the company offers reliable service, free estimates, and quality installation. Those claims may be true, but they do not help a buyer compare contractors.
A stronger page would answer the questions behind the AI Overview: when replacement makes sense, what affects price, what a first visit includes, which equipment options are usually compared, what rebates or financing questions to ask, what can delay installation, and what proof a homeowner should check before hiring.
That does not guarantee inclusion. Nobody can honestly promise that. But it changes the page from a ranked sales page into useful source material. That is the right improvement.

Mistakes to avoid
Assuming a ranking should automatically earn an AI Overview link
A ranking is a signal, not a guarantee. AI Overviews are generated for specific searches and may use different supporting links depending on the question.
Publishing near-duplicate support articles
If the primary intent is already covered, do not create another version just to chase AI visibility. Improve the existing page or create a distinct support page only when the buyer question is genuinely different.
Trying schema before fixing the visible page
Structured data should match visible content. It is not a replacement for a clear answer, practical examples, and trustworthy page copy.
Using AI to generate thin pages at scale
Google's guidance is clear that scaled content without real value can be a problem. For SMB sites, five useful pages are better than fifty generic ones.
Measuring one prompt and calling it proof
AI visibility changes. A single test is a clue, not a measurement system. Use repeated prompts, Search Console, analytics, and URL checks.
How to measure progress
Google has introduced generative AI performance reports in Search Console for a subset of site owners. The Search report can show impressions from supported generative AI features, including AI Overviews and AI Mode, grouped by pages, countries, devices, and dates. If you do not see the report, it may not be available to the property yet or there may not be enough impressions.
Until you have that report, use a simple monthly routine:
- Track the target page in the normal Search Console Performance report.
- Record target queries, impressions, clicks, CTR, and average position.
- Run the same buyer-style prompt set in Google and other AI search tools.
- Record whether your business appears, whether the description is accurate, and which page is linked.
- Review conversions and time on page in analytics where available.
If this sounds like a lot, start with ten questions a real customer would ask before contacting you. That will tell you more than searching your brand name.

Related reading
Next step: check the page before publishing more content
If your page ranks but is not being selected as an AI Overview source, do not rush into another article. First check whether the existing page is eligible, specific, useful, and supported by real evidence.
Sources
- Google Search Central: AI features and your websiteGoogle guidance on AI Overviews, AI Mode, eligibility, SEO fundamentals, controls, and measurement.
- Google Search Console Help: Generative AI performance report for SearchCurrent Search Console help page for generative AI impressions, supported features, dimensions, and rollout limitations.
- Google Search Central Blog: Introducing Search Generative AI performance reports in Search ConsoleGoogle's June 2026 announcement of dedicated generative AI visibility reporting.
- Google Search Console Help: How are you performing on Google?Reference for Search Console performance metrics such as impressions, clicks, CTR, queries, pages, countries, and filters.
- Google Search Central: Guidance on using generative AI content on your websiteGoogle guidance on using AI content responsibly and avoiding low-value scaled content.
Written by Miklos Kovacs, AI leverage partner for SMB owners. I help small businesses find practical AI and search-visibility opportunities without turning the website into a pile of generic AI content.
Last updated: August 21, 2026
FAQ
Can a page rank well and still be excluded from AI Overviews?
Yes. A ranking does not guarantee that Google will use the page as a supporting link in an AI Overview. The query may not trigger an AI Overview, the page may not match the generated answer closely enough, or other sources may provide clearer evidence.
Is there special schema for Google AI Overviews?
Google says there is no special schema.org structured data required for AI Overviews or AI Mode. Structured data can still support normal SEO when it matches visible page content, but it is not a shortcut that guarantees inclusion.
Should I create a new article if my ranked page is not cited?
Not automatically. First improve the existing page if it owns the intent. Create a new supporting article only when the buyer question is genuinely distinct and the current page would become bloated or unfocused by covering it.
What is the fastest practical fix for an SMB page?
Rewrite the opening so the buyer, problem, service, and direct answer are obvious. Then add a checklist, example, FAQ, updated date, and internal links from related pages. This is usually more useful than chasing a new tool.
How should I measure AI Overview visibility?
Use Google's generative AI performance report if your property has access. If not, track normal Search Console data, analytics referrals, and a repeatable set of buyer-style prompt tests. Measure patterns over weeks, not one result on one day.
