How Google Gemini and AI Overviews choose what to show
Gemini and AI Overviews answer above the blue links. Here is how they read the web, what a page needs to be readable to them, and how to check yours.
You can hold the number one organic ranking and still watch Google answer the question above your link, in a box you are not part of. That box is a different reader making a different decision.
AI Overviews are not the same reader as classic ranking
For years the goal was to win a click from a list of ten links. The reader was a person scanning results, and ranking decided who got scanned first.
An AI Overview changes the reader. Gemini reads pages and writes an answer that sits above those links, often resolving the question in place. The person may never scroll to the list at all.
So a page can rank well for a human and still read poorly to the overview that now sits on top of it. Good ranking does not guarantee the engine can cleanly parse you into an answer.
How they read the web and decide what to show
Gemini and AI Overviews gather pages relevant to a query, read them, and compose an answer grounded in what they could parse. The general mechanics are laid out in how AI engines decide what to recommend.
This is retrieval feeding generation: the engine reads live pages and builds an answer it can stand behind, drawing on the ones it could actually read into clear statements.
We are not going to invent Google's selection rules. They are proprietary, layered, and they change. What stays true is that a page the system cannot read cleanly is a page it cannot use cleanly, no matter where it ranks.
What a page needs to be readable to them
To be usable by Gemini and AI Overviews, a page has to carry its meaning in a form a machine can read without a human reading along.
- A clear heading that states the topic, so it is not inferred from layout.
- A direct, plain-text answer near the top, not buried below the fold.
- Structured data that labels what the page is, what it offers, and what it costs.
- Crawlable HTML, so the content is reachable rather than locked behind script.
Old way: optimize for the ranking and assume the overview inherits it. New way: keep the ranking work and add a machine-readable layer so the overview can read you as clearly as the index does.
This does not force you into the box. It makes you legible enough to be eligible, which is the part you can act on.
The damaging admission
Readable is not shown. We measure whether the engines, including Gemini, can read and name you, and we report it plainly, but we will never promise placement in an AI Overview.
The system is probabilistic and Google moves the goalposts often. It can read two clear pages and feature only one. Anyone guaranteeing you a spot in AI Overviews is selling certainty no one owns.
Readiness is the floor. If the overview skips a page it cannot parse, that is fixable. If it reads you and features someone else, at least you were in the running.
The automated fix is WordPress-only. On other platforms the scan still diagnoses the gaps, but you apply the changes yourself.
Why the overview is a moving target
AI Overviews are still expanding across more queries, and the surface keeps changing, so a page that fed an overview cleanly can fall out of one as Google adjusts what it pulls and how it reads. Add your own churn, new pages that ship without structure, and the readiness you measured once describes less of your site each month.
So this is not a fix you finish. It is a page you keep legible to a system that is itself rewriting how it reads.
And the stakes sit right on the results page. In 2024, 58.5% of American Google searches ended without a click, according to SparkToro. When the overview answers above the links, being a page it can actually read is the new top of the page.
How to check whether Gemini can read your page
Pick the page you would most want to feed an AI Overview and find out if it can be read today.
Run a free scan on the URL to see whether Gemini and the other engines can parse it and which structural pieces are missing, or read how Citedon makes a site agent-ready and keeps it that way as the engines change.