Your site isn't in Google's AI Overviews — here's how to fix it

You search a question you know your page answers well. Google paints its AI Overview at the top, cites three or four other sites, and yours isn't one of them. You've written the better page. You're still invisible. It's a maddening feeling, and most of the advice you'll find for it is wrong.

The thing most guides get wrong

There is no separate "AI Overview index" to break into.

This is the single fact that changes everything, and almost nobody leads with it. Google builds AI Overviews from the same search index that produces ordinary blue links. The AI doesn't go and read the open web fresh each time it answers. It runs a search against the regular index, pulls back the pages it already ranks well, and writes a summary grounded in those. We covered the plumbing in how AI Overviews pick sources, but the headline is short: if Google's normal results don't already rate your page for a query, the AI never sees it as a candidate.

So the prerequisite is brutal and simple. To be quoted in an Overview, you usually need to be indexed and ranking somewhere around page one for that query. The same goes for AI Mode. A page sitting at position 40 is not "almost there" for AI search. It's nowhere, because the retrieval step never reaches that far down.

That reframes the whole problem. "How do I get into AI Overviews" is mostly the old question wearing new clothes: how do I rank? The AI-specific work matters, but it's the last 20%. It only pays off once the page is genuinely competitive in conventional search. The other engines work the same way under the hood, which is why the diagnosis in why ChatGPT isn't citing your website lands on the same retrieval-and-corroboration culprits.

Check this first

Before you change a single line, find out which step you're actually stuck on. Three checks, in order.

1. Is the page indexed at all? Open Google Search Console, paste the URL into the inspection tool, and read the verdict. "URL is on Google" means you're in. Anything else, an exclusion, a "Discovered – currently not indexed", a noindex tag, means the page isn't even in the running. No amount of structured data fixes a page Google hasn't indexed. Start there.

2. Do you rank in roughly the top ten for the query? Search the actual question, in an incognito window, and find your position. Top of page one and you're a strong Overview candidate. Page two or worse and the Overview will almost never reach you, no matter how clean your markup is. Be honest with yourself here. This is usually where the real gap is, and it's the least glamorous to admit. Google hides which pages it weighed; Perplexity prints them, so if you want a worked example of reading the citations a competitor won, why Perplexity cites your competitors but not you walks through it.

3. Is your answer extractable as plain text? Look at the page the way a machine does. Is the direct answer sitting near the top, written in selectable text? Or is it buried under 600 words of throat-clearing, locked inside an image, or assembled by JavaScript that leaves nothing in the raw HTML? If the answer isn't there as readable text, close to the question, the model can't lift it even when it has retrieved your page.

Most "I'm not in AI Overviews" cases die on check one or two. Run them before you touch the fixes.

The fixes, in priority order

Do these in this order. The early ones gate the later ones, so skipping ahead wastes effort.

Fix indexing and ranking first. Everything else is moot without it. If check one failed, sort out why the page isn't indexed: remove an accidental noindex, fix a robots.txt block, get it linked internally so Google can find it, request indexing in Search Console. If check two failed, you have a ranking problem, not an AI problem. The page needs to genuinely be the best answer for that query: depth that actually resolves the question, internal links pointing to it, and the trust signals Google has always rewarded. There's no shortcut around this one.

Then make the answer extractable. Once you rank, give the AI something easy to grab. Lead the relevant section with a tight, direct answer to the question, two or three sentences a person could read aloud and be satisfied. State the conclusion before you explain it. If the meat of your page only appears after a script runs, render it server-side or statically so it's in the HTML on first load.

Phrase your headings as the questions people ask. "Can you return a sofa after 30 days?" beats "Returns policy." The AI is matching question-shaped queries to question-shaped content, so an <h2> that mirrors the search wording gives it an obvious hook, and the paragraph beneath it the obvious answer.

Add structured data where it fits, without overrating it. FAQ and HowTo structured data help machines parse your page cleanly. They're worth adding when your content genuinely is a FAQ or a procedure. They are not an entry ticket, though. Markup on a page that doesn't rank changes nothing. Treat it as polish on a page that already qualifies, not a lever that gets you there.

Keep the page fresh and the HTML clean. A page last touched in 2021 competes badly against one updated last month for anything time-sensitive. Sensible semantic HTML, one clear heading per idea, no critical content hidden behind a click or a script, gives both the crawler and the AI a page they can read without guessing.

Notice what's not on this list. No llms.txt, because Google has said plainly it does nothing for their AI surfaces. No "AI-only" version of your content. No keyword stuffing dressed up as optimisation. The work that gets you into AI Overviews is, by and large, the work that should have been getting you ranked all along.

Where you're actually stuck

The hard part isn't the fixes. It's knowing which of the three checks is failing, because the symptom, "I'm not in the Overview", looks identical whether the cause is indexing, ranking, or extractability.

That's the bit Rankport does for you. It confirms whether the page is indexed, where it ranks for the query, and whether your answer is sitting in the HTML in a form an AI can lift, then tells you in plain English which step is blocking you and what to change first. Point it at the page that's being ignored and run the AI visibility checker. You'll know within a minute whether you have an indexing problem, a ranking problem, or a writing problem, and you can stop guessing.