How long does it take to appear in Google AI Overviews

How long does it take to appear in Google AI Overviews? Google does not publish an appearance SLA, and nobody can sell you a week-count. The honest plan is calendar bands: discovery and index often take days to a few weeks, a recrawl request can take a few days to a few weeks, and preview-control changes can take several days to several months. Eligibility — indexed, snippet-eligible, included in Search generative AI features — is not appearance. Appearance is a supporting link inside an Overview that actually fired. Book the wait labels. Do not book a date for the CEO.

This spoke sits under the Answer Engine Optimization playbook. It is the calendar, not the how-to. Eligibility and quotation mechanics live in how to get cited in Google AI Overviews. If you already rank and the unit cites someone else, stop waiting and run ranked but missing AI Overviews. Lane work lives on /visibility.

The short answer

• Google documents no AI Overview inclusion date. Plan ranges Google already published for crawl and index, then observe. Do not invent a week-count.
• Eligibility and appearance are different events. A page can sit in the index for months and still never appear as a supporting link.
• Use four board labels only: ELIGIBILITY WAIT, RECRAWL WAIT, OBSERVE, DIAGNOSE.
• Request indexing typically takes a day or so and can take a week or two. It still does not guarantee the index, let alone an Overview.
• Recheck after last crawl is newer than the ship date. Rechecking at 9 a.m. the next morning is anxiety, not measurement.

How is this wait different from other AEO timelines?

This page is the Google AI Overviews calendar. It does not replace the how-to or the ranked-but-missing diagnostic. If you paste this spoke’s tables into a ChatGPT-citation deck, you are mixing clocks Google never joined.

Job	Lives on	What this page will not do
Multi-engine citation clocks (retrieval vs index vs memory residue)	A different timeline spoke	Invent a 37-day or 6.81-day Overview SLA from vendor samples
Operator sequence: extractable answer, entity, crawl, measure	How to get cited in AI Overviews and the appear-in-Overviews how-to	Teach you how to write the passage
Rank plus Overview miss	Ranked but missing AI Overviews	Run the quote-test while you are still in RECRAWL WAIT
Recrawl bands, eligibility vs appearance, board labels	This page	Convert Google’s crawl ranges into a booked cite week

If the ticket is “when will we show up,” stay here. If the ticket is “make the page quotable,” leave. If the ticket is “we rank and they got the cite,” leave. Mixing those three is how a wait becomes a rewrite becomes a fake miss.

Why doesn’t Google publish an appearance SLA?

Because an Overview cite is not a job Google queues for you. How Search works is crawl, index, then rank and serve. AI Overviews retrieve from those same ranking systems. The unit only shows when Google decides it is additive to classic Search, and it often does not trigger. There is no ticket that says “cite this URL by Friday.”

What Google does publish are crawl and index ranges. Those are eligibility clocks. Teams treat them as appearance clocks and then fire a working URL for being “late.”

Documented statement	What it covers	What it does not cover
Crawling can take a few days to a few weeks	Recrawl after you ask Google to fetch	A supporting link in an Overview
Indexing typically takes a day or so, can take a week or two, is not guaranteed	Request indexing on a URL you manage	Rank, snippet, or citation
New page or site: a week or so before crawl may even start	Discovery lag	Appearance
After a URL is known, crawl of some or all of the site can take up to a few weeks	Site-level crawl schedule	A booked Overview
Preview-control recrawl: several days to several months	nosnippet / max-snippet / similar processing	“We will be cited this quarter”
Generative-AI exclude: 1–2 days after the control is live, some longer from cache	Property-level include/exclude	Ranking or a cite you can promise

Those rows are planning inputs. They are not an inclusion contract. If a vendor quotes “14 days to AI Overviews,” they are collapsing Google’s crawl language into a sales number. I have been SEO certified since 2021. The certification does not include a Google appearance SLA, because there is not one.

Decision list when someone asks for a date:

1. If they want a cite date, refuse. Offer a wait label instead.
2. If they want a recrawl window, quote the Google row that matches the job (new URL vs preview-control change vs Request indexing).
3. If they want a results date, point at OBSERVE after eligibility is green — still not a promise.
4. If the Overview does not fire on the query, stop the wait. There is no appearance clock on a unit that never exists.

What is eligibility versus appearance on this clock?

Eligibility is the floor that lets Google consider the page as a supporting link. Appearance is the event: the Overview fired, and your URL was one of the links. Mixing those two is how a team celebrates “we’re indexed” and then panics that “AEO doesn’t work.”

Google’s floor is explicit. To be eligible 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, meeting Search technical requirements. There are no additional technical requirements. The optimization guide adds that the site must be included in Search generative AI features in Search Console. Meeting every requirement still does not guarantee crawl, index, or serving.

State	What is true	Board label	Clock that has started
Not crawled	Google has no last-crawl date you can trust	ELIGIBILITY WAIT	Discovery only
Crawled, not indexed	Fetch happened; index selection did not	ELIGIBILITY WAIT	Index selection
Indexed, snippet blocked	nosnippet, max-snippet:0, or data-nosnippet on the answer	ELIGIBILITY WAIT	Preview-control recrawl after you fix it
Indexed, snippet-eligible, site excluded from generative AI	Classic Search may still show you	ELIGIBILITY WAIT	Control propagation after you Include
Indexed, snippet-eligible, included	You are a candidate	OBSERVE	Appearance — only if the unit fires
Overview present, your URL cited	Appearance happened	Log it. Do not call it a permanent slot	Measurement, not a wait
Overview present, others cited	Eligibility may be green; selection lost	DIAGNOSE	Not more waiting
Overview absent	Feature did not fire	Do not score as a cite miss	No appearance clock

Eligibility is binary-ish. Appearance is query-by-query and not guaranteed on a green URL.

Checklist before you start a wait at all:

• URL Inspection says the URL is on Google, or you have a documented reason it is not
• Live HTML is allowed to snippet (nosnippet and max-snippet:0 also block the page as direct input for AI Overviews and AI Mode)
• Search generative AI control is Include on the property
• You have named the query, locale, and device you will score
• You have confirmed whether an Overview even appears on that query

If any of the first three boxes is red, you are not late for an Overview. You have not entered the candidate set.

Which calendar bands belong on a planning board?

Five bands. Four of them are Google-sourced ranges. The fifth is observation, which Google does not time. Label the band. Do not convert the band into “we appear in N weeks.”

Band	Job	Google-sourced range	Planning label
1. Discovery	Google finds the URL via links, sitemap, or inspect	New page/site: about a week before crawl may start; after known, up to a few weeks to crawl some or all of the site	ELIGIBILITY WAIT
2. Index selection	URL is chosen for the index	Request indexing: typically a day or so, up to a week or two; still not guaranteed. “URL is on Google” is still not a Search guarantee	ELIGIBILITY WAIT
3. Recrawl after HTML change	Google fetches the version you think it has	Ask-to-recrawl: a few days to a few weeks. Repeat requests on the same URL do not go faster	RECRAWL WAIT
4. Preview-control processing	Snippet / AI-input tags actually take effect	Several days to several months, depending on how often systems decide the page needs a refresh	RECRAWL WAIT
5. Appearance observation	Overview fires and your URL is a supporting link	No published duration	OBSERVE, then DIAGNOSE if the window is spent

Band 4 is the one executives hate, because it is the longest Google range in public docs. It applies when you flipped nosnippet, max-snippet, data-nosnippet, or similar preview controls. It is not a generic “AEO takes months” slogan. If you did not change preview controls, do not borrow the months language as your default.

How to pick a band in one pass:

1. Name the change you shipped (new URL, copy edit, preview-control flip, generative-AI Include).
2. Match it to one row. One row. Do not average Band 2 and Band 4 into “three weeks.”
3. Write the Google range on the ticket as the observation window, attributed to the doc.
4. Set the label. The due date on the ticket is “re-inspect,” not “appear.”
5. When last crawl is newer than ship date, move ELIGIBILITY WAIT or RECRAWL WAIT to OBSERVE or DIAGNOSE. Not before.

Change you shipped	Band to plan	Wrong band people steal
Brand-new money URL, never crawled	1 then 2	5 — they want a cite before Google has fetched
Copy edit on an already indexed URL	3	4 — they quote “months” for a paragraph tweak
Removed accidental nosnippet	4	2 — they think Request indexing clears preview controls overnight
Flipped Search generative AI from Exclude to Include	Control propagation (next section)	5
Already eligible, Overview cites a competitor	Skip wait. DIAGNOSE	3 — they recrawl a page Google already has

A sitemap helps discovery; it does not force crawl or index. Putting twenty URLs in a sitemap is not a Band-5 accelerator.

How long can discovery and indexing take before eligibility starts?

Until Google has crawled and selected the URL, the Overview clock has not started. This is the expensive confusion on new domains and orphan money pages.

Google’s Page indexing report is blunt. A new page or site can take a week or so before crawl and indexing even start. After a URL is known, it can take up to a few weeks before Google crawls some or all of the site. New content can take a few days to index; requesting indexing can shrink that lag, and still does not put every URL in the index. You should not expect 100% of URLs to be indexed. Indexed also does not guarantee the URL will show in a given search.

URL Inspection adds the Request-indexing caveats. Indexing can take up to a week or two. It typically takes a day or so, but can take much longer. Submitting a request does not guarantee the page will appear in the Google index. “URL is on Google” does not guarantee the page is appearing in Search results. There is a daily quota; requesting recrawl multiple times for the same URL will not get it crawled faster.

Inspection reading	What it means for Overviews	Next label
URL unknown to Google	Discovery has not happened	ELIGIBILITY WAIT. Request indexing once if you own the URL
Discovered – currently not indexed	Found, not selected	ELIGIBILITY WAIT. Do not hammer Request indexing as a ritual
Crawled – currently not indexed	Fetched, declined or delayed for index	ELIGIBILITY WAIT. Fix uniqueness, links, quality — not more tickets
URL is on Google, snippet blocked	Candidate floor is still red	ELIGIBILITY WAIT on preview controls
URL is on Google, snippet allowed	Eligibility floor may be green	OBSERVE on named queries
Last crawl older than the HTML you shipped	Google does not have your change	RECRAWL WAIT after one request

Procedure on a new money URL:

1. Confirm a 200, a canonical you intend, and internal links from a crawled page.
2. Put the URL in the sitemap. Request indexing once.
3. Record request date, last-crawl date, and index status.
4. Do not score Overview citation until index status is on Google and snippets are allowed.
5. If the URL stays unknown past Google’s “week or so / few weeks” language, debug findability. Do not debug “AEO copy.”

Mistake	Cost	Do this instead
Twenty Request-indexing clicks on one URL	Burns quota. Does not speed that URL	One request. Then wait the documented range
Scoring Overviews on an unknown URL	Fake fail	Stay on ELIGIBILITY WAIT
Treating “on Google” as “in the Overview”	Fake pass, then a board fight	OBSERVE only after the unit fires
Launching a microsite with no internal links	Discovery stretches into the few-weeks band	Link it from a crawled page the day you ship

What “a week or so” is not:

Phrase in Google’s docs	Honest use on a ticket	Dishonest use
A week or so before crawl may start	Observation window for a brand-new URL	“We appear in seven days”
Up to a few weeks to crawl some or all of the site	Site-level findability, not one hero page	“The whole site is in Overviews in three weeks”
A few days to index new content	Index lag after discovery	“Cited by Wednesday”
Typically a day or so after Request indexing	Typical index attempt, not a median cite	“Google’s SLA is 24 hours”
Up to a week or two	Upper published Request-indexing range	A booked Overview on day 14

Eligibility starts when the URL is indexed and snippet-eligible. Not when the CMS said “published.”

How long does recrawl take after you change a page?

Two Google ranges, two jobs. Mixing them is how a paragraph edit inherits a “several months” story it does not deserve.

For a normal recrawl request, crawling can take anywhere from a few days to a few weeks. Be patient and watch URL Inspection or the index reports. Requesting a crawl does not guarantee inclusion in search results instantly, or at all.

For preview-control troubleshooting, Google tells you to allow time to recrawl and process the change, and that crawling can take several days to several months depending on how often systems decide the page needs to be refreshed. You can still request a recrawl. You cannot compress that range into a standup date.

What changed	Range to plan	Proof the wait ended
Title, lead, table, FAQ HTML	Few days to a few weeks	Last crawl ≥ ship date; fetched HTML shows the new passage
Accidental nosnippet removed	Several days to several months	Live test plus later indexed result show snippets allowed
max-snippet:0 lifted	Several days to several months	Snippet appears in Search; Overview input is no longer blocked by that rule
Canonical or redirect	Few days to a few weeks, plus index selection	Google-selected canonical is the URL you want cited
JavaScript-only answer moved into server HTML	Few days to a few weeks after the HTML actually contains the answer	View crawled page shows the answer unit

Gate the recrawl request:

• The live HTML already contains the change. Do not request on a staging URL Google cannot fetch.
• You have not already requested this URL today as a panic click.
• You are inside quota. Twenty blog posts go in the sitemap, not twenty inspect tickets.
• You wrote the ship timestamp next to the URL. The wait math needs that stamp.
• You will not rescore appearance until last crawl moves.

Worked wait, no invented cite:

Ticket	Ship	Request indexing?	Label until last crawl moves	After last crawl moves
New /pricing paragraph	Monday 16:00	Once	RECRAWL WAIT	OBSERVE on the pricing queries
Removed sitewide nosnippet	Monday 16:00	Once on the money URLs	RECRAWL WAIT using the months-capable range	OBSERVE, then DIAGNOSE if still snippet-blocked
Rewrote a passage already being quoted	Do not ship	No	You created a new wait you did not need	Restore the winning passage
CMS “update” with no HTML diff	Do not request	No	There is no recrawl job	Stop

If last crawl is already newer than ship date and the Overview still cites someone else, the wait is over. You are in DIAGNOSE. More recrawl tickets will not select your passage.

How long does the Search generative AI control take to move?

This is the one Google timebox that is not a crawl band. It is a property switch, and it is still not an appearance SLA.

Search Console’s Search generative AI control defaults to Include. Include means the site can appear in Search generative AI features, including as links and as grounding input. Exclude prevents that visibility. Google says once you change the control, it generally takes a few days for content to be excluded, typically within 1–2 days after the control goes live, with some URLs lingering longer because of caching and propagation. Include does not mean Google will show you. Exclude does mean you should not expect Overview supporting links from that property.

Control state	Eligibility for Overviews	Planning note
Include (default)	Allowed to be considered	Still not a cite. OBSERVE on queries
Exclude, just flipped	Falling out over 1–2 days, some longer	Do not diagnose “why aren’t we cited” during propagation
Exclude, settled	Not eligible as generative-AI input or link	Waiting is wasted. Flip Include, then start ELIGIBILITY WAIT / OBSERVE
Inherited from a parent property	Follows the parent	Check the parent before you rewrite pages

Procedure if someone turned Exclude on during a “block the AI” scare:

1. Confirm the control on the exact property that owns the money URLs.
2. If it is Exclude and you want Overviews, set Include.
3. Label CONTROL PROPAGATION for a few days, using Google’s 1–2 day language plus cache hedge.
4. Do not mix this with Google-Extended. That is training/grounding in other Google systems, not this Search feature switch.
5. After propagation, return to index + snippet checks. The switch does not skip crawl.

Confusion	What people do	What is true
Exclude to “protect content,” then ask why Overviews vanished	Wait, then rewrite	You opted out of the feature
Include, then demand a cite in 1–2 days	Steal the exclude timebox	1–2 days is documented for exclusion, not inclusion-as-cite
robots.txt Google-Extended vs this control	Flip the wrong switch	Different jobs. Overviews follow Googlebot + snippet rules + this control

If the control is Include and you are still absent, the control is not your clock. Move on.

When does a missing Overview freeze the wait entirely?

When the unit never fires. Google is explicit: AI Overviews are only shown when systems determine they are additive to classic Search, and as such, often don’t trigger. Absence of the unit is not a citation failure. You cannot be late to a slot that was never opened.

This is the freeze that wastes the most calendar. Teams recrawl, rewrite, and burn inspect quota on queries that never generate an Overview in their locale.

Confirm the feature before you start a wait:

1. Search the exact query on the device and locale you sell in.
2. Repeat it in a second session. Units flicker. Log both.
3. Note Overview present / absent. Do not note “we weren’t cited” if the unit was absent.
4. If absent across repeats, mark the query FEATURE-OFF. Take it off the appearance calendar.
5. If present, then and only then score your URL as cited or not.

SERP you captured	Clock status	Allowed label
No Overview, both sessions	Frozen. No appearance clock	FEATURE-OFF. Not a miss
Overview some sessions, not others	Noisy trigger	Log both. Do not average into a week-count
Overview present, you cited	Appearance happened	Record URL + quoted passage
Overview present, competitor cited	Wait is the wrong tool	DIAGNOSE
Overview present, you unindexed	Eligibility never started	ELIGIBILITY WAIT

Query fan-out can attach a wider set of links than the classic ten. That is a selection and coverage problem, not a reason to invent a longer SLA. If the unit fired and skipped you, the calendar did not fail. The extract or the sub-question coverage did. That diagnostic is the ranked-but-missing spoke, not another recrawl week.

Do not put FEATURE-OFF queries on a “days to appearance” chart. They will make the channel look dead.

What failure mode burns the most calendar time?

Booking an appearance date, then spending the wait on the wrong layer.

The pattern I see on audits: a founder hears “AI Overviews” on a call, someone writes “in Overviews by the 15th” on a slide, the team ships a blog calendar, hammers Request indexing every morning, and never checks whether the money URL is snippet-eligible or whether the query even grows an Overview. Two weeks later the slide is red. They declare AEO a fad. The URL was never in the candidate set, or the unit never fired.

I will not attach a fabricated client loss to that. The cost is the weeks you cannot get back, plus a burned inspect quota, plus a passage you rewrote while Google still had the old HTML.

Failure	What it costs	What you do instead
Cite date on a slide	A fake miss on a working wait	Four labels. Re-inspect date, not appear date
Daily Request indexing on one URL	Quota. Zero speedup	One request. Then last-crawl math
Recrawl before the HTML change is live	Google fetches the old page; you wait again	Ship, verify View Source, then request
Preview-control bug ignored	Months-capable range, still ineligible	Fix nosnippet / max-snippet:0 first
Scoring FEATURE-OFF queries	Editorial panic	Remove them from the appearance panel
Rewriting a quoted passage during RECRAWL WAIT	You reset the clock and may lose the lift	Wait until last crawl; then DIAGNOSE
Treating GSC impressions as a live SLA	You wait on reporting, not on Googlebot	SERP log first; Console as aggregate

Checklist that would have stopped the slide:

• No date in the deck that Google did not publish
• Eligibility boxes green, or the ticket says ELIGIBILITY WAIT with the blocking reason
• Overview presence logged per query
• One Request indexing per URL per change
• Ship timestamp and last-crawl timestamp in the same row
• DIAGNOSE owner named for “unit fired, we lost”

If you need a sentence for leadership: “We are in RECRAWL WAIT on the Google few-days-to-few-weeks range. Appearance is not scheduled.” That sentence is true. “We will be in AI Overviews next Tuesday” is not.

What labels should you put on the board instead of a date?

Four labels, plus FEATURE-OFF when the unit does not exist. That is the whole vocabulary. If a ticket needs a fifth status, you are smuggling a promise back in.

Label	Means	Exit condition	Forbidden translation
ELIGIBILITY WAIT	Not yet a candidate	Indexed + snippet-eligible + Include	“Almost cited”
RECRAWL WAIT	Candidate HTML may be stale	Last crawl ≥ ship date; fetched HTML matches	“Google is slow, so we appear Friday”
OBSERVE	Floor is green; unit can fire	Logged sessions on frozen queries	“Results week”
DIAGNOSE	Floor green, unit fired, you lost — or wait spent with no movement and eligibility still green	A named mechanism, not another wait	“Give it one more month” as a stall
FEATURE-OFF	Overview did not fire	Query stays off the appearance panel	“We failed AEO”

Print this on the ticket template:

1. URL
2. Query / locale / device
3. Ship timestamp
4. Last-crawl timestamp
5. Index status
6. Snippet allowed? (yes / no / unknown)
7. Generative-AI control (Include / Exclude)
8. Overview present? (yes / no / mixed)
9. Our URL cited? (yes / no / n/a)
10. Label (one of the five)

If column 10 is a date, you filled the form wrong.

Board text that looks professional	What it actually is	Replace with
“AIO by 8/27”	Invented SLA	OBSERVE after last crawl moves
“Day 14 checkpoint for citations”	A cousin of a 14-day promise	Re-inspect when last crawl ≥ ship date
“On track vs 21-day median”	Vendor sample from a different measurement, or fiction	Google range for this band
“Need more content this sprint to hit Overviews”	Volume as a clock	Eligibility row, then DIAGNOSE
“Request indexing again to be safe”	Anxiety	Quota rule: same URL does not go faster

Worked tickets, labels only — no appearance dates:

URL job	Ship	Last crawl vs ship	Overview on query?	Label now	Next action
/pricing copy edit	Mon 16:00	Last crawl Sun	Yes, competitor cited	RECRAWL WAIT	Do not DIAGNOSE until last crawl ≥ Mon 16:00
/pricing after crawl	Mon 16:00	Last crawl Tue	Yes, competitor cited	DIAGNOSE	Ranked-but-missing. Stop recrawl tickets
New /compare URL	Wed 09:00	Unknown to Google	Yes	ELIGIBILITY WAIT	One Request indexing. Internal link from a crawled page
/guide with leftover nosnippet	Last month	Last crawl yesterday	Yes	ELIGIBILITY WAIT	Remove the tag, then Band 4 RECRAWL WAIT
Brand query, no Overview in locale	n/a	Indexed, snippets on	No, both sessions	FEATURE-OFF	Drop from the appearance panel

I will not put day-30 or day-90 appearance rates here. Those are measurement horizons on other spokes, and they are still not Google inclusion dates. On this page the only honest horizons are the ranges in Google’s crawl and index docs, used as observation windows.

How do you measure whether the wait is working?

You measure whether the wait did its job: Google has the HTML you shipped, eligibility is green, and you scored the query honestly. You do not measure “is AEO working” from a single screenshot during RECRAWL WAIT.

Two instruments. They answer different questions.

Search Console’s generative AI performance report counts organic impressions when links to your site were shown in AI Overviews or AI Mode. For AI Overviews, an impression requires the link to be scrolled or expanded into view; the Overview occupies one SERP position and every link in it inherits that position. The report is directional and aggregated. It is not a live cite log, and it is not a substitute for knowing whether the unit fired on your frozen queries.

The frozen panel is the operator log. Same wording. Same locale. Same device class. Overview present / absent. URL cited / not. Quoted passage versus live HTML.

Signal	What it proves	What it does not prove
Last crawl ≥ ship date	Recrawl wait can end	You appeared
URL is on Google	Index selection happened	Search or Overview placement
Snippet allowed in inspection	Eligibility floor for quotation	A supporting link
GSC generative-AI impression	A link to you was shown in a generative feature (with impression rules)	The query you care about, or a stable slot
Panel: Overview absent	FEATURE-OFF for that session	That you are ineligible
Panel: Overview present, you cited	Appearance on that prompt	You will keep it next week
Panel: Overview present, not you	Selection loss	That you should recrawl again

Procedure for one recheck (do not turn it into a workshop):

1. Open the ticket. Confirm the label is still honest.
2. Inspect the URL. Copy last crawl, index status, snippet state.
3. If last crawl is still older than ship date, stay on RECRAWL WAIT. Stop. Do not run the SERP yet as a pass/fail.
4. If last crawl moved, fetch what Google got. Confirm the answer unit is in that HTML.
5. Run the frozen queries. Log Overview and citation separately.
6. Move the label: OBSERVE if you are still collecting sessions; DIAGNOSE if the unit fired and you lost; FEATURE-OFF if it never fired.

Cadence	Object	Stop doing this
After last crawl moves	That URL	Daily SERP theater during RECRAWL WAIT
Weekly on money queries that fire Overviews	Frozen panel	Changing the prompt because you disliked yesterday’s answer
When GSC generative-AI report updates	Property-level impressions	Treating a dip as “we fell out in 48 hours” without a panel
After a preview-control change	Snippet state, then panel	Declaring success from the CMS publish ping

Search Console is delayed relative to the live SERP. I am not going to invent a reporting SLA. Use the panel as the clock you control. Use Console as the aggregate you cannot screenshot by hand.

If impressions exist and your panel never shows a cite, you are looking at a query-set mismatch, not a faster recrawl. Fix the panel.

What should you skip if you only have a week?

Skip anything that burns the inspect cap, resets a winning passage, or pretends a week is an appearance SLA. A week is enough to start the right wait. It is not enough to demand the cite.

Do this week	Skip this week
Inventory five money URLs: index, snippet, last crawl, generative-AI control	A twenty-URL Request-indexing binge
Fix noindex / nosnippet / max-snippet:0 on those URLs if they are wrong	A blog calendar “for AEO”
Request indexing once on URLs that are unknown or whose HTML actually changed	Rewriting a passage already being quoted
Freeze 10–20 queries. Log Overview presence	Promising the board an Overview by Friday
Confirm Include on Search generative AI	Flipping Google-Extended as if it were this control
Label each URL with one of the four waits	Building a 14-day Gantt called “AI Overview launch”

Day-by-day, planning labels only:

1. Day 1 — Pull URL Inspection on the money set. Write blocking reasons. No copy yet unless eligibility is already green and the lead cannot stand alone — and even then, the how-to spoke owns the rewrite, not this calendar.
2. Day 2 — Ship eligibility fixes. Verify View Source. Request indexing once per changed URL.
3. Day 3 — Freeze the query list. Capture baseline: Overview on/off, cited URL if any.
4. Days 4–5 — Do not rescore appearance. Watch last crawl. Do other SEO work that is not this clock.
5. End of week — If last crawl moved, run the panel once. Move labels. If last crawl did not move, stay on RECRAWL WAIT. That is a successful week of waiting, not a failed week of AEO.

Week-one “win” you can report	Week-one “win” you cannot report
“3/5 URLs moved from unknown to requested; 2 were already on Google with snippets”	“We appeared in AI Overviews”
“Sitewide nosnippet removed; Band 4 wait started on the Google days-to-months language”	“Preview controls will clear by Thursday”
“8/12 queries never fire an Overview in our locale — removed from the appearance panel”	“Citation rate is 0%, AEO failed”
“Include confirmed; no Exclude scare switch”	“Include means we will be cited”

A week is for eligibility hygiene and honest labels. Appearance sits after last crawl, after the unit fires, and after selection. None of those owe you Friday.

When is waiting not the next action?

Waiting is the wrong ticket when eligibility is red for a reason you can fix today, when the unit does not fire, or when the unit fires and you already lost. More calendar will not repair those.

Situation	Wait?	Do this
noindex, robots block, soft 404	No	Fix availability. Then ELIGIBILITY WAIT
nosnippet / max-snippet:0 still live	No, not on appearance	Fix the tag, then RECRAWL WAIT on Band 4
URL unknown, zero internal links, no sitemap	No	Make it findable, then Band 1
Search generative AI = Exclude	No	Include, then CONTROL PROPAGATION
Overview never fires on the query	No	FEATURE-OFF. Pick a query that grows a unit, or drop the KPI
Overview fires, you rank, competitor cited	No	DIAGNOSE on ranked-but-missing. Not another recrawl
Last crawl already has your HTML, still no cite	No	OBSERVE a few more sessions, then DIAGNOSE. Do not reset the clock
You have no frozen queries	No	You are not waiting. You are guessing
Legal / paywall / login wall on the answer	No	Google cannot quote what it cannot fetch as a snippet-eligible page

Decision list:

1. If a checkbox on the eligibility list is red and you can ship the fix today, ship it. Waiting on a noindex is theater.
2. If the only red is “last crawl is old,” wait. That is the one honest RECRAWL WAIT.
3. If last crawl is new and the unit is off, stop. FEATURE-OFF.
4. If last crawl is new and the unit is on and you lost, stop waiting. Diagnose extract, entity, fan-out, or competitor citeability — on the diagnostic spoke, not on this calendar.
5. If you cannot name the query, you are not in a wait. You are in a strategy gap. That belongs under the playbook, not under a recrawl ticket.

Waiting is a tool for Googlebot. It is not a strategy. If the floor is red, fix the floor. If the unit is off, change the KPI. If the unit is on and you lost, change the page — then, and only then, start a new RECRAWL WAIT on the new HTML.

Do not open a second wait on the same URL while the first last-crawl has not moved. That is how you lose the plot.

FAQ

How long does it take to appear in Google AI Overviews?

Google does not publish an appearance SLA. Plan crawl and index bands instead: Request indexing typically takes a day or so and can take a week or two without guaranteeing the index, recrawl can take a few days to a few weeks, and preview-control changes can take several days to several months. Eligibility is not appearance. Appearance is a supporting link when an Overview actually fires.

How do I measure whether long does it take to appear in Google AI Overviews is working?

Measure the wait, not a booked cite. Re-inspect when last crawl is newer than the ship date, confirm the fetched HTML has your answer, then score a frozen query panel: Overview present or not, your URL cited or not. Use Search Console’s generative AI impressions as a directional aggregate. A screenshot taken during RECRAWL WAIT is not a result.

What usually fails first when teams try this?

They put a cite date on a slide, then burn Request indexing quota on URLs that are still noindex, nosnippet, unknown to Google, or attached to queries that never grow an Overview. The calendar looks late. The floor never went green, or the unit never fired. Fix eligibility and feature presence before you start a wait.

How long does this take to show results?

Eligibility can move on Google’s crawl and index ranges, and still is not guaranteed. Appearance has no published duration after that floor is green. Report label changes and last-crawl movement, not a week-count inclusion. If the Overview never fires, there is no result clock to wait on.

What should I skip if I only have a week?

Skip appearance promises, daily inspect clicks, and a content blast “for Overviews.” Spend the week on index/snippet/control hygiene for a handful of money URLs, one Request indexing per real change, a frozen query log, and honest labels. A week can start the right wait. It cannot collect an SLA Google never wrote.

When is this not worth doing yet?

When the URL is not indexable, snippets are blocked, the property is set to Exclude from Search generative AI features, or the target query never shows an Overview. Waiting will not repair those. Fix availability and controls, or pick a query that actually grows the unit. If you already rank and lose the cite, stop waiting and run the ranked-but-missing diagnostic.

CTA

If your AI Overview plan is a week-count, stop. Put eligibility and recrawl labels on the money URLs, then observe — or diagnose.

Lane: /visibility · Book a visibility audit.