Does Google AI Overviews use live search or memory?

AI Overviews are generated over Google's search index rather than from a model's memory, so they reflect pages that are indexed now. The practical gate for you is therefore indexing: a page Google has not indexed cannot appear, and a page indexed today can appear soon after.

Why this changes your priorities

On an assistant that answers from memory, nothing you published last month exists. Here, the question is simply whether the page is in the index and ranking for the query. That makes the checklist much more ordinary than people expect, and much more actionable.

• Is the page indexed? Check rather than assume. This is the most common blocker and the easiest to miss.
• Does it render without scripts? Content that only appears after JavaScript runs can be seen as far thinner than it is.
• Does it rank for the question? Candidates come from the index, so ranking is still the entry condition.
• Is there a passage that answers the question directly? A summary is lifted from a passage, not from a whole page.
• Do your other pages agree with it? Two of your own pages answering the same question differently is a reason to use somebody else's.

What "live" does and does not mean

Live means over the current index, not over the current web. A page published this morning is not available until it has been crawled and indexed, and that is not instant. So the honest statement is that this engine has no months long training lag and it does have a crawl and index lag.

That distinction matters when you are testing whether new pages worked. If you publish on Monday and check on Tuesday, you have measured your crawl rate, not your content.

What this does not mean

Being in the index and ranking does not entitle you to appear. Overviews are not generated for every query, they select a small number of sources, and they favour passages that answer cleanly. Plenty of well ranked pages are never summarised because there is nothing compact in them to lift.

It also does not mean the model plays no part. Something has to write the summary, decide what the pages support and choose which names survive into it. What the index decides is the candidate set. What the model decides is the sentence. You can influence the first directly and the second only by what your page makes easy to say.

A worked example

Start with a real timescale rather than an assumed one. On 6 August 2026 ChatGPT cited the page clawlaw.in/blog/how-to-check-a-companys-court-cases-in-india as a source for a vendor due diligence question. That page had been published fourteen days earlier, and at baseline the same question set had named the company nowhere in that part of the market. clawlaw.in is our sister company, and both the page and the question are public, so this is one of the readings a reader can check independently.

Fourteen days from publishing to being used as a source is the order of magnitude to plan for on an engine working over a live index. Not one day, and not one quarter. So set your check points accordingly.

Week one: check only whether the page is indexed. Nothing else is meaningful yet. If it is not indexed, the experiment is paused and the task is a technical one.

Week two: search the question from a signed out browser and record three things. Did an overview appear, were you named, and where did your page rank in the ordinary results. An overview that appears while your page sits on the second page of results is a ranking problem rather than a summarising problem, and no amount of rewriting the opening paragraph will fix it.

Week four: if the page has reached the first page of results and is now linked under the overview, and you are still not named in the text, it is a writing problem and a narrow one. Open your page and look for the sentence a summariser could have repeated. If every candidate sentence carries an adjective rather than a fact, that is your answer.

Week six: either you have added a dated specific near the top and you are named, or you are not, and the overview is drawing its names from roundups, in which case your next month is outreach rather than writing.

The value of this sequence is that it separates four different failures that all look the same from the outside: not indexed, not ranking, not liftable, and not in the candidate lists.

How to measure it sensibly

Keep three records per question: whether an overview appeared, whether you were named, and whether you ranked underneath. Because this engine follows the index, a change you make can show up within weeks, which makes it a reasonable place to test whether new pages are doing anything at all.

Do it by hand or with something that issues the search and reads the screen, because Google includes overview performance inside overall Search reporting rather than breaking it out. There is no report that tells you this.

The comparison worth making

Run the same questions here and on an engine that always retrieves live. Where you appear in one and not the other, the difference usually tells you something specific: a page that is fetchable but not ranking, or a page that ranks but has no liftable answer. Both are fixable, and they need opposite fixes.

Why this is the friendliest engine to work with

There is no waiting for a model to learn who you are. The chain is ordinary and every link is inspectable: get indexed, rank for the question, and give the page a passage that answers it. When you are not appearing, you can usually find out which of those three failed in an afternoon, which is not true of an assistant answering from memory.

The part that is still out of your hands

Whether an overview is generated at all for your question is Google's decision, it changes, and no one can promise you a place in one. The same query can also produce different results in different countries, languages, devices and accounts, so your reading is local to you.

Google does not publish how sources are selected from the ranking set or how many are used. Everything above is what the feature's behaviour and Google's own documentation about indexing support, and it should be treated as a working model rather than as a specification.

Common questions

How long after publishing should I test?

Check indexing after a few days and the overview after two to three weeks. Testing the day after publishing measures crawl speed and tells you nothing about the page.

Why do two searches of the same question disagree?

Because overview generation is decided per query and varies with location, language, device and account, and because the feature changes. The disagreement is normal. Record where each reading came from.

How often should I check?

Monthly for a full set. This engine can reflect changes within weeks, so monthly is frequent enough to catch movement without recording noise.

It cited a competitor's page for a fact about us. Why would it not use ours?

Because their page either ranked for that query and yours did not, or stated the fact in a liftable block while yours buried it. Both are checkable in ten minutes: search the query and look at where each page ranks, then read the two opening blocks side by side.

Is being linked the same as being recommended?

No. Linked means a page of yours was used. Named in the text is what a buyer sees. Ranking underneath is a third thing that still sends visits. Three columns, always.

Does this mean SEO is all I need?

For this engine it is most of what you need, which is not true of the others. Two extra habits matter: put the answer in one liftable block near the top, and state facts a summary can repeat. Those are writing habits rather than technical ones, and they are what separates a page that ranks from a page that gets quoted.

What to do first

Take the page you most want summarised and confirm it is indexed, today. If it is, read its first two hundred words and ask whether a stranger could lift one sentence from them that answers the question with a fact in it. If not, rewrite that opening block before you touch anything else on the page.