Google has given site owners and SEO teams unusually specific timing ranges for how long Search changes can take to move through crawling, indexing, serving and recovery.
The figures came from Gary Illyes of Google Search Relations during Search Central Live Deep Dive Europe in Barcelona on Oct. 2, 2026, according to a recap by ROAST’s John Campbell.
The timing ranges came with caveats
ROAST’s recap says Illyes showed fastest, typical and slowest times based on Google’s internal analysis. The public recap reproduces typical and slowest ranges, but it does not provide the sample size, measurement period or a formal definition of “typical.”
The table is useful for planning and expectation-setting, but it should not be treated as a service-level promise from Google. It also does not mean a page will rank as soon as one technical step finishes.
In the recap, Illyes gave one caveat that explains much of the table: a page cannot be indexed until it has been crawled, so delays stack.
The key crawl, indexing and recovery ranges
The figures below are the main timing ranges from the ROAST recap most likely to matter for site owners, publishers and SEO teams.
| Process | Typical timing reported | Slowest case reported |
|---|---|---|
| Discovery of a new URL | About 20 hours | Weeks to never |
| Refresh of a known URL | About 30 days | Weeks to never |
| Sitemap processing | About 24 hours | As long as 14 days, or never for quality reasons |
| Rendering | Seconds to render, with hours in the queue | Days to weeks |
| End-to-end indexing | About 1.5 hours | Months, or never for quality reasons |
| Canonicalization change | 1 to 3 weeks | Months when signals conflict |
| Site move | 1 to 3 months | 6 months to more than 1 year |
| Snippet update | 1 to 2 days | Several weeks to months |
| Title update | 1 to 2 days | Several weeks to months |
| Search Console removal request by owner | About 2 hours | 24 hours |
| Manual action removal | 1 to 2 weeks | 4 to 6 weeks, or much longer for dormant sites |
| Core update change or recovery | 3 to 6 months to recover | 6 months to 1 year, tied to the next core update |
| Spam update change | 1 to 2 weeks on a continuous basis | Months in batch refreshes |
The 1.5-hour indexing number is not the full waiting period
The recap also says “end to end” means all critical processes finish successfully. That makes the 1.5-hour indexing figure easy to misread. It does not mean every new page should appear in Search within 90 minutes of publication.
A new URL still has to be discovered. A known URL may wait for a refresh. A sitemap may need processing. Rendering, link processing or canonicalization may add more time.
In practical terms, the relevant clock is often the slowest unresolved upstream step, not the final indexing step by itself.
That explains why one page might be found and processed quickly while another sits in Search Console for weeks. The slower page may not be waiting on the same part of Google’s systems.
Quality is a gate, not a clock
The repeated use of “never” in the slowest-case column is the most useful part of the reported table. Several slowest cases are tied to quality, including sitemap processing, end-to-end indexing and structured data updates.
That lines up with Google’s existing public guidance. Google’s recrawl documentation says requesting a crawl does not guarantee instant inclusion, or inclusion at all, and that its systems prioritize high-quality, useful content. Google’s crawling and indexing FAQ also says crawling and indexing take time, rely on many factors and cannot be predicted or guaranteed.
The quality caveat also fits Google’s broader direction on low-value and scaled content. Tech Help Canada has covered the same risk in its guide to AI-generated content, search quality and spam risk.
The figures match existing Google guidance
The Barcelona ranges add specificity, but they do not fully replace Google’s existing documentation.
Google’s recrawl guidance says crawling after a recrawl request can take from a few days to a few weeks. Google’s site move documentation says small to medium-sized sites can take a few weeks for most pages to move, while larger sites take longer. It also recommends keeping redirects in place for at least one year so Google can transfer signals, recrawl and reassign links.
Google’s core update guidance already gives a similar recovery pattern. It says some improvements may show effects in a few days, but systems may take several months to learn and confirm that a site is producing helpful, reliable, people-first content over time. If there is still no effect after a few months, Google says the site may be waiting until the next core update.
What site owners can take from the numbers
For site owners, the timing ranges are most useful as escalation thresholds. They help separate normal waiting from problems that deserve a deeper review.
- New pages: Immediate indexing should not be assumed. Discovery, crawl, rendering and indexing need to be checked separately before drawing conclusions.
- Edited pages: Title and snippet changes may appear within days in typical cases, but slower updates do not always mean the change was ignored.
- Site moves: Planning should allow months, not days, especially when many URLs, mixed canonical signals or server limits are involved.
- Core update recovery: A few weeks may be too short for judging whether broad content improvements have been recognized.
- Persistent non-indexing: Once technical access is confirmed, the issue may be quality, duplication, canonical conflict or low crawl demand rather than the submission process.
The figures also matter for AI-assisted SEO workflows. Automated publishing can create more pages than a site can support with originality, accuracy and maintenance. Tech Help Canada’s guide on what not to automate in SEO applies directly to publishing systems where volume can outpace quality control.
For reporting, a single “indexed or not indexed” check is often too blunt. A stronger review separates the question into stages: whether Google discovered the URL, crawled it, rendered it, selected it for indexing, chose the intended canonical and reflected the change in served results.

Tech Help Canada Staff researches, writes, and reviews practical content for business owners and professionals. Our coverage spans business, marketing, SEO, technology, and the tools and systems people use to grow and operate online. We focus on clear, useful information backed by research, hands-on experience, and editorial review. Learn more about our team and editorial standards. Need help with something? Contact Us







