How long does Google take to index a page? Once Google decides a page is worth indexing, Gary Illyes says the process typically takes about 1.5 hours end to end. The slow part is everything around it: discovery, canonical decisions, site moves and recovery after a core update, which can take weeks to a year.
Key takeaways
- Google showed its typical processing times publicly for the first time at Search Central Live Deep Dive Europe in Barcelona (2 October 2026).
- Indexing itself is fast. When a page takes months or never gets indexed, the reason is usually quality, not a technical queue.
- Canonical changes take 1 to 3 weeks, site moves 1 to 3 months, and core update recovery 3 to 6 months on average.
- Many of these steps depend on each other, so delays add up. A slow recrawl delays the canonical change, which delays the signals moving.
These numbers come from a slide Gary Illyes presented on the final day of Search Central Live Barcelona. Google hasn't published the slides yet, so I'm working from attendee notes, mainly John Campbell's day 3 recap at ROAST. Treat them as typical ranges Google shared on stage, not guarantees in its documentation.
Google's timelines at a glance
| Process | Typical | Slowest |
|---|---|---|
| Discovering a new URL | About 20 hours (single attendee report) | Not reported |
| End-to-end indexing | About 1.5 hours | Months, or never (quality) |
| Snippet or title update | 1–2 days | Several weeks to months |
| Canonical change | 1–3 weeks | Months (conflicting signals) |
| Manual action removal | 1–2 weeks | 4–6 weeks, longer for dormant sites |
| Spam update effect | 1–2 weeks (continuous) | Months (batch refreshes) |
| Site move | 1–3 months | 6 months to 1 year+ |
| Core update rollout | 2–4 weeks | Not reported |
| Spam update rollout | 1–2 days | Not reported |
| Core update recovery | 3–6 months | 6 months to 1 year |
Gary's warning that came with the slide, per ROAST: many processes are linked, so delays compound.
How long does Google take to index a new page?
Two numbers matter here, and people mix them up.
Discovery is Google finding the URL. One attendee summary at aioseo.fr recorded about 20 hours for that, though I haven't seen it confirmed elsewhere. Indexing is Google fetching, rendering and storing the page once it's in the queue. That's the 1.5 hours.
So if your post went live on Monday and still isn't indexed on Friday, the technical pipeline isn't the bottleneck. Google either hasn't prioritised crawling it or crawled it and decided not to index it.
That's what the two Search Console statuses tell you:
- Discovered – currently not indexed: Google knows the URL but hasn't crawled it. Look at internal links, server speed and crawl demand.
- Crawled – currently not indexed: Google fetched it and passed. Look at the page itself.
The word "never" on the slide was tied to quality. ROAST put it well: fast technical fixes don't help if Google doesn't think the page is worth indexing.
What speeds up indexing
From the crawl budget session on day 1, Cherry Prommawin said crawl demand comes from quality, change frequency and popularity, and the crawl rate limit drops when time to first byte rises or your server returns 429 or 5xx codes. So, in order of impact:
- Link the new page from pages Google already crawls often, like your homepage or a hub.
- Keep your server fast. Slow responses cut the crawl rate for every Google crawler on your host.
- Submit the URL in your XML sitemap with an accurate
lastmod. - Use URL Inspection's "Request indexing" for important pages, but don't expect it to override a quality decision.
Snippets and titles: 1–2 days
Changed your title tag or meta description? Expect the new version in 1–2 days typically. But Google can still rewrite what it shows. If your new title isn't appearing after a couple of weeks, check whether Google is choosing its own; my title tags guide covers why that happens.
Canonical changes: 1–3 weeks
When you change a canonical, Google has to recrawl the affected URLs, re-cluster them and move signals to the new canonical. John Mueller said on day 2 that Google clusters similar pages, chooses one and consolidates signals. It takes 1–3 weeks typically and months if your signals conflict.
Conflicting signals look like this: a canonical tag pointing to page A, internal links pointing to page B, and the sitemap listing page C. Google has to guess, and guessing takes longer. If you see Duplicate without user-selected canonical, clean up those signals before waiting it out.
Manual actions: 1–2 weeks after reconsideration
Once you fix the problem and file a reconsideration request, removal typically takes 1–2 weeks and up to 4–6 weeks. Dormant sites take longer. The fix has to be real; resubmitting without changes just restarts the wait.
Site moves: 1–3 months
Moving domains? Plan for 1–3 months before things settle and up to a year in bad cases. John Mueller's advice on day 2 was the standard list: use redirects, return proper status codes, keep canonical signals clear. He also noted a site: search on the old domain can still show results after a migration. That doesn't mean the move failed.
One community case from the same day, Martyna Ağanoğlu's merger of two domains, cut a site from 2,000 pages to 100 with no traffic drop and higher revenue. It's a single case, but it shows a well-planned move doesn't have to hurt.
Core updates: 2–4 weeks to roll out, 3–6 months to recover
This is the one people ask me about most.
A core update rolls out over 2–4 weeks. Recovery, once you've improved the site, typically takes 3–6 months and can take up to a year. Gary Illyes also said on day 3 that core updates evaluate content at page level, not domain level.
That explains a pattern you've probably seen. One section of your site drops, another climbs, in the same update. It isn't a sitewide penalty. Google re-judged pages individually.
So when a client's traffic drops in a core update, my process is:
- Wait for the rollout to finish before drawing conclusions. Dates for every update are in my Google core updates history.
- Compare page by page, not sitewide, in Search Console.
- Improve the pages that dropped against the four quality pillars Duy Nguyen named on day 3: effort, originality, talent or skill, and accuracy.
- Expect to wait a quarter or more. Recovery often shows up with the next core update, not before it.
Spam updates: fast rollout, slower effects
Spam updates roll out in 1–2 days. Changes from spam systems typically show within 1–2 weeks because they run continuously, but batch refreshes can take months. Gary also said spam updates are getting more frequent because AI has inflated the volume of content, and that scaled content is now a bigger problem than link spam.
How to use these numbers
I'm putting these into my client reports as expectation-setters. A rough rule I'll use from now on:
- Technical fix (robots, status codes, rendering): check again in 1–2 weeks.
- Canonical or internal linking change: check in 3–4 weeks.
- Content quality improvements after a core update: report in quarters, not weeks.
If you want to see where each of these fits in a full SEO timeline for a new site, read how long does SEO take.
Frequently asked questions
How long does Google take to index a new page?
Gary Illyes said end-to-end indexing takes about 1.5 hours once Google decides to index a page. Discovery can take longer, and pages Google judges low quality may take months or never be indexed.
How long does it take to recover from a Google core update?
Google's typical figure is 3 to 6 months after you've made real improvements, and up to a year in slow cases. Core updates judge individual pages, so recovery is usually page by page rather than sitewide.
How long does a site migration take to settle in Google?
Typically 1 to 3 months, and 6 months to a year or more in the slowest cases. Use 301 redirects, correct status codes and consistent canonical signals to stay at the faster end.
How long does a canonical change take?
Usually 1 to 3 weeks. It can take months when signals conflict, for example when the canonical tag, internal links and sitemap point to different URLs.
Where do these Google timelines come from?
Gary Illyes presented them at Search Central Live Deep Dive Europe in Barcelona on 2 October 2026. They're typical ranges from Google's internal data, reported by attendees, not official documentation.
.webp)
Connect with Akif on LinkedIn, Instagram and Facebook.
Driven by advanced SEO expertise, deep marketing analytics, high-impact content strategy
With 5+ years of hands-on experience, I specialize in holistic search strategies that don’t just rank—they drive real, measurable business growth. I’ve worked across industries including healthcare, hospitality, legal, e-commerce, and professional services, helping brands dominate their target markets. My approach bridges the gap between raw data and creative execution. Every strategy I build is rooted in rigorous market analysis, structured SEO frameworks, and tailored content ecosystems—no templates, no shortcuts. Whether you’re a single-location brand or scaling across multiple cities, I create data-driven marketing systems designed to compound results and grow with you.
Pages Missing From Google?
Get a technical SEO audit that finds indexing, canonical and crawl problems on your site — with a prioritised fix list.
Book a Free SEO Audit →