"How long until Google picks this up?" is the question I get most from clients. Until now, the honest answer has been "it depends" (John is forbidden to say this as answer during the game!).
On Day 3 of Google Search Central Live Deep Dive Europe 2026, Gary Illyes put numbers on it. He showed three slides with Google's own estimates for how long crawling, indexing and serving changes take. Each one listed the fastest case, the typical case and how long it can stretch.
As the photos I took during the event were blurry, I've recreated those slides as infographics below and added what I think each number means in practice. One caveat up front: Google described these as estimates based on internal analysis, not guarantees.
How to read these timings
Every row shows three points on a time scale that runs from seconds to over a year:
- Fastest it starts: the quickest Google can act on the change.
- Typical: where most sites land. This is the number to plan around.
- Can take up to: the long tail. Some rows end in "or never", which usually comes down to quality or conflicting signals.
The gap between fastest and longest is often huge. A title change can show in seconds or take months. That spread is the point: the typical value tells you when to start worrying, not when to expect results.
How long it takes to crawl
Google typically discovers a new URL in about 20 hours and recrawls a known URL in about 30 days.
| Event | Fastest | Typical | Can take up to |
|---|---|---|---|
| Discovery (new URL) | Seconds | ~20 hours | Weeks, or never |
| Refresh (known URL) | Seconds | ~30 days | Weeks, or never |
| Sitemap processing | Minutes | ~24 hours | Up to 14 days, or never (quality) |
| robots.txt update | Seconds | ~24 hours | 25 hours |
| Crawl capacity update | Seconds (in back-off) | Drops: ~4 hours; rises: 1–2 weeks | 1–3 weeks (recovery) |
| Crawl demand update | Minutes | ~20 hours | Weeks to months |
The 30-day refresh figure matters more than people expect. If you update an existing page, Google may not see the change for weeks unless something prompts a recrawl.
A robots.txt change topping out at about 25 hours fits Google's documented behaviour of caching robots.txt for up to a day. Don't expect a robots.txt fix to unblock crawling the same afternoon.
Crawl capacity was the most useful detail of the talk. It drops fast because hostload is recalculated about every 4 hours. It rises slowly, typically over 1–2 weeks, because Google wants to be sure your server can handle the extra load. One bad afternoon of server errors can throttle crawling for weeks.
How long it takes to index
Most indexing changes typically land within hours to 3 weeks, but site moves typically take 1–3 months.
| Event | Fastest | Typical | Can take up to |
|---|---|---|---|
| Removal | Hours to days | 1–3 weeks | Months |
| Canonicalisation change | Seconds | 1–3 weeks | Months (conflicting signals) |
| Site move | A few weeks (small sites) | 1–3 months | 6 months to 1 year+ |
| Structured data updates | Seconds (extraction) | Hours to 1–2 weeks | Weeks, or never (quality) |
| Images | ≤150 seconds | Hours to days | Weeks to months |
| Videos | Minutes (metadata) | Hours to days | Weeks to months (deep analysis) |
For canonicals, the long tail comes from conflicting signals. If your rel=canonical says one thing but internal links, sitemaps and redirects say another, Google has to weigh them. Consistent signals are the fastest route to the canonical you want.
Site moves need the longest runway. Plan migrations, and their reporting, over months rather than expecting a clean switch in a fortnight.
Structured data can be extracted within seconds, but it may never be used if Google has quality concerns. Valid markup is necessary but not sufficient for rich results.
How long it takes to update search results
Titles and snippets typically update in 1–2 days, while recovery from a core update typically takes 3–6 months.
| Event | Fastest | Typical | Can take up to |
|---|---|---|---|
| Removal via Search Console (owner) | Minutes to 2 hours | ~2 hours | 24 hours |
| Snippet update | Seconds | 1–2 days | Several weeks to months |
| Text result image update | Days | 1–2 weeks | Several weeks to months |
| Title update | Seconds | 1–2 days | Several weeks to months |
| Manual action removal | 2–3 days | 1–2 weeks | 4–6 weeks, or much longer (dormant sites) |
| Core update change | 2–4 weeks (rollout) | 3–6 months (recovery) | 6 months to 1 year (next core update) |
| Spam update change | 1–2 days (rollout) | 1–2 weeks (continuous) | Months (batch refreshes) |
A Search Console removal is the fastest lever you have, at about 2 hours. Title and snippet changes are next, typically 1–2 days. My reading is that these clocks start once Google has recrawled the page, so on a rarely crawled page a title tweak can take over a month.
Core and spam updates run on very different clocks. Spam systems run continuously, so changes typically show in 1–2 weeks. Core update recovery typically takes 3–6 months and can wait for the next core update. If you were hit by one, judge the work over months, not days.
What I'd do with these numbers
The biggest lesson is that timings stack: a change has to be crawled, then indexed, then served. Here's how I'll use them:
- Set expectations by the typical value. Give clients the typical figure, not the fastest one. "Titles usually update in a day or two after a recrawl" is honest; "it's instant" isn't.
- Prompt recrawls for important updates. With a ~30-day refresh cycle, don't wait for Google to notice. Submit key URLs through URL Inspection in Search Console and keep
lastmodin your sitemap accurate. - Protect server stability. Capacity drops within hours and takes 1–2 weeks to recover. Watch for 5xx and 429 spikes in the Crawl Stats report, especially around deployments and traffic peaks.
- Keep canonical signals consistent. Align rel=canonical, internal links, redirects and sitemaps so a canonical change lands in weeks, not months.
- Measure on the right window. Check a title change after a week, a migration after three months and core update recovery after the next core update.
- Use Search Console removals for urgent cases. At about 2 hours, it's the only lever here that works on the same day.
FAQ
How long does Google take to index a new page?
Discovery typically takes about 20 hours, and indexing follows within hours to days for most content. Some pages are never indexed, usually because of quality.
How long does Google take to crawl a site again?
Known URLs are typically recrawled about every 30 days. Important pages may be crawled far more often, and low-value ones much less.
How long does it take for a title change to show in Google?
Typically 1–2 days, though it can take several weeks to months.
How long does a robots.txt change take to work?
Typically about 24 hours, and up to about 25 hours.
How long does it take to recover from a core update?
Typically 3–6 months. In some cases, recovery waits for the next core update, 6 months to a year later.
How long does a site migration take in Google?
Typically 1–3 months. Small sites can settle in a few weeks, while large or complex moves can take over a year.
