How Long Google Takes to Crawl, Index, and Update Search Results
Google can take days or weeks to reflect a published change. Check the live response first, then Google's dated observations. An unchanged search result does not prove your deployment failed.
Google's work has several stages. Discovery means learning that a URL exists. Crawling means fetching its response. Rendering executes page JavaScript. Indexing processes page information for Google's index. Serving selects and presents search results for a query. Search Console performance reporting follows its own schedule.
Reported Processing Times
An October 2026 Search Engine Roundtable report describes internal timing observations presented by Google's Gary Illyes. It attributes the figures to attendee reporting from John Campbell and Neil McCarthy at Search Central Live Deep Dive.
Gary described the slides as an audience exercise using internal numbers. The report supplies no sample size, measurement period, or statistical definition of “typical”. Treat these figures as context, not deadlines for your page.
These selected rows come from the reported presentation:
| Process | Reported typical time | Reported slow cases |
|---|---|---|
| New URL discovery | About 20 hours | Weeks or never |
| Known URL refresh | About 30 days | Weeks or never |
| Sitemap processing | About 24 hours | Up to 14 days, or never because of quality |
| Rendering | Seconds executing, hours queued | Days to weeks |
| Indexing, end to end | About 1.5 hours | Months or never because of quality |
| Canonical change | 1 to 3 weeks | Months with conflicting signals |
| Site move | 1 to 3 months | 6 months to over a year |
| Structured data update | Hours to 1 to 2 weeks | Weeks or never because of quality |
| Title or snippet update | 1 to 2 days | Several weeks to months |
The indexing time covers cases where all critical indexing processes finished successfully. It does not measure the wait from publishing a page or submitting a request. Earlier stages can add delays. Some pages never progress. The slow cases do not establish maximum waits or explain an individual page's delay.
What to Check After a Change
First, confirm the deployed response contains your intended change. Check the exact URL, status code, crawler access, and initial HTML. If content depends on JavaScript, compare the rendered HTML too.
Then compare the change date with Google's last crawl and indexed version in URL Inspection. A live test checks the current response. It does not prove Google has updated its index. Google's recrawl guidance says crawling can take days to weeks. Requesting a crawl does not guarantee inclusion. Repeated requests do not make the same URL crawl faster.
Choose the next check from what changed:
| Change | Next check |
|---|---|
| New page | Check crawlable internal links, sitemap membership, and URL Inspection |
| Sitemap | Check fetch and processing status, then inspect important URLs separately |
| Canonical | Compare live declarations, redirects, internal links, and Google's selected canonical |
| Title or description | Confirm the edit, then check the displayed result after recrawling and processing |
| Structured data | Validate current markup and check the selected feature's eligibility requirements |
| Site move | Test redirects and compare old and new URL observations over time |
For example, suppose you change a page title on Monday. Your live HTML check can confirm the edit that day. If Google's last crawl predates Monday, it has not fetched that version in the recorded crawl. Google must recrawl and reprocess the page before noticing changed title sources. Its title-link guidance describes a wait of days to weeks. Google can also choose a different title from your preference.
Record the edit date before comparing complete performance periods. A click-through rate change alone does not prove the edit caused it.
Robots Rules Have a Separate Cache
Google generally caches robots.txt for up to 24 hours. Fetch errors can extend caching. A successful request to your live file does not prove Google refreshed its cached rules. Check the robots.txt report and server responses when access remains blocked.
Keep Your Checks Separate
Submitting a sitemap tells Google about its URLs. Processing it does not prove Google indexed every listed URL. Indexing makes a page eligible for search results. It guarantees no ranking or particular search appearance.
Nuxt SEO Pro's Crawl reads your site. A Scan measures a page with Lighthouse. GSC sync reads Search Console data. These operations do not make Google complete its own processing stages.
If a fix is live, compare later dated observations before changing it again. If a live block remains, fix that block rather than waiting for a typical timeframe to pass.
See the indexing investigation guides for Nuxt and Vue.
Pre-launch setup, post-launch verification, and ongoing monitoring. Interactive checklist with links to every guide.