Why Is My Site Not Appearing in Google AI Overviews?
Google publishes more about this than any other engine, including that AI Overviews often do not trigger at all. The diagnostic order, quoted from Google.
Start by confirming an AI Overview appeared at all, because Google states they only show when its systems judge them additive and often do not trigger. Google also states there are no additional technical requirements beyond being indexed and snippet-eligible, so the usual causes are indexing, a nosnippet-family tag suppressing previews, blocked crawling, or content that is not in textual form. Nobody can promise inclusion.
Someone searched your topic, saw a box of AI-written text above the links, and you were not in it. So you went looking for the AI Overviews checklist.
Before you optimize anything: check whether the box appears at all for the query you actually care about. Google says it often does not.
Step one, and most people skip it
Google's Search Central documentation is unusually blunt here. It states that "AI Overviews are only shown when our systems determine that it is additive to classic Search, and as such, often don't trigger" (Google Search Central, page last updated 2025-12-10, checked 2026-08-06).
Run your five most important queries. Note which ones produce an AI Overview and which produce plain results. For the ones with no overview, there is nothing to be absent from and nothing to fix.
That single check will delete a third of the problem for most sites, and it costs five minutes.
Step two: Google says the bar is the ordinary bar
Here is the sentence that contradicts most of the AEO advice you have read.
"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, fulfilling the Search technical requirements. There are no additional technical requirements."
The same page adds that "while specific optimization isn't required for AI Overviews and AI Mode, all existing SEO fundamentals continue to be worthwhile."
No AI schema. No special tag. No file you are missing. The floor is the one you already know, and the sites that fail it fail it in ordinary ways: not indexed, not snippet-eligible, not crawlable, or not written as text.
If someone is selling you a proprietary markup that unlocks AI Overviews, that is the claim to check against the paragraph above.
Step three: the one people do to themselves
Snippet-eligible is doing real work in that sentence, and it is the most commonly self-inflicted failure on this list.
Google states that to limit what is shown from your pages in Search, site owners use nosnippet, data-nosnippet, max-snippet, or noindex. Those are the documented controls, and they apply to AI features because AI features draw on the same eligibility.
So a max-snippet value set years ago to keep competitors from scraping your descriptions, or a data-nosnippet wrapper around the paragraph that actually answers the question, is a working feature doing exactly what you asked. Check the rendered HTML of the page, not your intentions.
Google also notes that after changing a preview control you have to wait, because "crawling can take anywhere from several days to several months, depending on how often our systems determine a page needs to be refreshed."
Step four: you are not competing for one query
The retrieval mechanism matters here more than the ranking instinct you built over a decade.
Google names the technique: "Both AI Overviews and AI Mode may use a 'query fan-out' technique, issuing multiple related searches across subtopics and data sources, to develop a response." It adds that while responses are being generated, its models identify more supporting web pages, which lets it show a wider and more diverse set of links than a classic web search.
Read that as an opportunity rather than a threat. Your page is not fighting for the one query you track. It is being considered against a spray of sub-questions you never see, several of which are narrower than anything you would target on purpose.
Which is why a page that answers one specific sub-question cleanly can appear as a supporting link while a broader page that outranks it does not. Query fan-out has the mechanics.
Step five: AI Mode is a different surface
Google is explicit that these are not one system. "AI Mode and AI Overviews may use different models and techniques, so the set of responses and links they show will vary."
So being absent from one tells you very little about the other. And neither is the Gemini app, which is a separate Google product with its own retrieval, covered in is Google AI Overview the same as Gemini. Three doors, and AI Mode is its own.
What Google actually lists as worth doing
The documentation gives a list. It is unglamorous and every item is checkable, which is what makes it useful:
- Crawling is allowed in robots.txt, and by any CDN or hosting infrastructure.
- Content is easily findable through internal links on your site.
- Important content is available in textual form.
- Structured data matches the visible text on the page.
- Merchant Center and Business Profile information is up to date.
- The page provides a good page experience.
The fourth one is the quiet killer, and it is not neutral when it fails. Markup that disagrees with the page is a machine-readable claim that happens to be false, made on a surface where the machine cannot check it. Keeping schema valid after edits is the maintenance job that item creates.
The fifth one is the one local businesses skip, and it is on Google's own list. How AI assistants choose which local businesses to mention goes into what that changes.
Old way, new way
The old way was one query, one rank, one number, checked weekly.
The new way is that the same query can produce an AI Overview, an AI Mode response, and a classic result set with different links in each, plus every other engine your buyer might open instead. Your position stopped being a number. It became a set of yes-or-no answers to "could this system read my page while it was building its answer?"
That is not a softer question. It is a harder one, because it is per surface, and it moves.
Measuring it without fooling yourself
Two reporting facts that people get backwards.
Search Console has no AI Overviews report. Google states that "sites appearing in AI features (such as AI Overviews and AI Mode) are included in the overall search traffic in Search Console" and are "reported on in the Performance report, within the 'Web' search type." Those impressions have been inside your existing numbers all along, which is exactly why nobody noticed the shift as it happened.
GA4 does not fill the gap either. Google's own definition of the AI Assistants default channel group states that it "excludes Google's AI Overviews and AI Mode" (GA4 help, checked 2026-08-06). Traffic from an AI Overview arrives as Organic Search. If you have been reading the AI Assistants channel as your total AI exposure, it never included Google. How to see AI referral traffic in GA4 sets out what that channel does and does not cover.
Google does make one claim worth quoting in full, since it is theirs and not ours: "We've seen that when people click from search results pages with AI Overviews, these clicks are higher quality (meaning, users are more likely to spend more time on the site)." That is Google reporting on its own surface, not an independent finding, and it is about the clicks that do happen, not the ones that do not. The zero-click mechanism runs alongside it, described in AI answers are eating the click.
The damaging admission
Citedon cannot place you in an AI Overview, and we are not going to imply the selection is ours to move.
Being specific about what our scan does on this surface, because it matters most here: the Gemini check queries a Gemini model through Google's API with web search grounding enabled. That is a real read of the live web by a real Gemini model, and it tells you whether your page can be retrieved and named. It is not a capture of the AI Overview box on a Google results page, and we do not present it as one.
We also do not promise a citation after a fix. Google's documentation is public and it says there is no additional technical requirement, which means there is no lever anyone can sell you that unlocks inclusion. What we promise is that you will know whether your page can be read, and that you will keep knowing as that shifts.
And the automated fix layer is WordPress only, through the connected plugin with a preview and a per-fix approval. Elsewhere, the scan gives you the diagnosis and you apply it yourself.
Where to start
Take your most important query. Confirm whether an AI Overview triggers for it at all. If it does, open the page you would want cited and check the two things Google names: that a crawler can fetch it, and that the answer exists as real text rather than as layout.
Run a free scan on that URL to see how ChatGPT, Perplexity, Gemini, and Claude read it today, and which structural pieces are missing. If your miss is on a different engine, the diagnosis changes machine by machine: the full list of answer engines maps them, and the Perplexity version of this checklist starts from a different failure entirely.