Every agency has had the call. The new service pages went live on Monday, the client checked Google on Wednesday, and nothing had moved. Or the title tags were rewritten three weeks ago and the old ones are still showing. The question underneath is always the same: how long does Google take to index a change, and is the wait normal or is something broken?
Until now the honest answer was a shrug and some experience. In early October, Google's Gary Illyes put actual numbers on it. They are not perfect, and Google has not published them anywhere official, but they are the closest thing agencies have had to a timetable. This guide walks through them and turns them into something you can use: what to tell a client, when to check, and what to put in the monthly SEO client report so a slow week does not turn into a difficult meeting.
Key takeaways
The figures were shown by Gary Illyes during his session at Google Search Central Live Deep Dive in Barcelona. The most complete write-up is John Campbell's day 3 recap for ROAST, published on 2 October 2026, and Barry Schwartz covered it on Search Engine Roundtable three days later.
So when a client asks "how long does Google take to index our new pages?", you can now answer with a range instead of a guess. Two caveats matter before you quote any of this, though. First, the times are described as based on Google's internal analysis, shared on slides and passed on by people in the room. There is no Google help page behind them. Second, Gary pointed out that the processes are linked. A page cannot be indexed until it has been crawled, so if crawling is slow, everything after it is slow too. Treat each number as one link in a chain, not a stopwatch you can start the moment you hit publish.
Short version: if nothing gets in the way, about a day. In the figures, Google typically discovers a new URL in around 20 hours, and indexing it end to end takes about 1.5 hours once the page has been crawled. "End to end" here means all the critical processes finished, not just that Googlebot visited.
The slow cases are where client conversations go wrong. Discovery of a new URL can take weeks, or never happen. The same goes for indexing, where a page judged low quality can wait months or never be indexed at all. A sitemap usually gets processed in about 24 hours, but it can take up to 14 days, and again the note on the slide was blunt: sometimes never, for quality reasons.
Pages that already exist are on a different clock. A known URL is typically refreshed about every 30 days. That surprises people. If you improve the copy on a page that has been live for two years, Google may not look at it again for a month unless something prompts a recrawl, such as fresh internal links or the page being in a sitemap with an updated date.
Indexing is only the first question. The one that follows is "how long does Google take to index a change and actually show it?" Here is the part worth printing out: the typical and slow times for the changes agencies make every week, taken from the same set of figures.
| Change | Typical | Slow case |
|---|---|---|
| New page discovered | About 20 hours | Weeks, or never |
| Page indexed after crawling | About 1.5 hours | Months, or never (quality) |
| Existing page recrawled | About 30 days | Weeks, or never |
| Sitemap processed | About 24 hours | Up to 14 days, or never |
| Title or snippet update shown | 1 to 2 days | Several weeks to months |
| Structured data update | Hours to 1 to 2 weeks | Weeks, or never |
| Canonical change | 1 to 3 weeks | Months (conflicting signals) |
| Site move | 1 to 3 months | 6 months to over a year |
| Manual action removed | 1 to 2 weeks | 4 to 6 weeks, longer for dormant sites |
| Recovery after a core update | 3 to 6 months | 6 months to a year |
A few rows deserve a sentence of context. The title row assumes Google has recrawled the page and is happy to use your title; it can still rewrite one it thinks does not fit the page. The canonical row is slow mostly because of mixed signals: if your canonical tag says one thing and your internal links and sitemap say another, Google takes its time deciding who to believe. And the core update row is the one to underline. Recovery usually comes at the next core update, which is why "we fixed it, why hasn't it come back?" is such a common question two months after a drop. Core updates themselves take two to four weeks to roll out; spam updates take one to two days.
The word "never" turns up a lot in the slow column, and nearly every time it comes with the same note: quality. Google does not crawl, render and index everything it finds. If a site produces thin location pages by the hundred, or a blog full of near-duplicate posts, some of those pages will sit in "Discovered, currently not indexed" in Search Console indefinitely. Waiting longer does not fix that. Improving the pages, merging the weak ones or cutting them does.
The second common cause is a weak path to the page. A URL that is only reachable from a sitemap, with no internal links pointing at it, gives Google little reason to prioritise it. When a page is stuck, check three things before blaming Google: is it linked from pages that already get crawled often, is it in the sitemap, and is the canonical pointing at itself.
Rendering is the third. Google typically renders a page in seconds, but it can wait hours in the queue, and days to weeks in slow cases. If the important content only appears after JavaScript runs, that queue time is part of your wait. Server-rendered content skips the problem.
Numbers like these are most useful before the work starts, not after the client gets nervous. A few habits make a real difference.
Give every change a review date. When you rewrite titles, tell the client you will check them in a week. When you move a site, agree on a three-month review before launch. A date turns "nothing has happened yet" into "we're on schedule".
Note changes on the timeline. A dip or a jump means little without context. Mark the day the migration went live, the week the titles changed and the dates of any core update. In AgencyReportr, which is marketing reporting software for agencies, you can add notes to the trend chart of any report, so when you review the month you see each change against the line it was meant to move. Carry the same dates into the summary you send the client, so they read the change and its timing together.
Report the leading signal first. Before rankings move, Search Console usually shows the page being indexed and starting to collect impressions. Showing indexing and impressions in the report tells the client the work has landed, weeks before clicks catch up. Pair that with daily keyword rank tracking so they can see movement as it starts rather than in a monthly snapshot.
Say what "never" means. If pages are stuck for quality reasons, say so plainly and recommend what to do about them. It is better for the client to hear it from you than to read a cheerful report while half their new pages sit unindexed.
One last point on tone. These timelines are typical ranges from a talk, so quote them as "Google has said a title change typically shows in one to two days", not "Google guarantees". That keeps you honest if a client's site lands in the slow column, and it is still far more reassuring than "it depends". If you send reports on a schedule, branded PDF reports sent automatically mean the review dates you promised arrive with the numbers already in them.
AgencyReportr puts Search Console, GA4 and daily rank tracking in one white-label SEO report, sent to clients on your schedule. Start with a $1 trial.
7-day trial · Cancel any time
In the figures Gary Illyes presented, Google typically discovers a new URL in about 20 hours, and indexing takes about 1.5 hours once the page has been crawled. The slow cases run to weeks, and a page Google judges low quality may never be crawled or indexed at all.
Typically one to two days for title and snippet updates, according to the same figures, with slow cases taking several weeks to months. The page still has to be recrawled first, and Google can rewrite a title it does not think describes the page.
One to three months is typical for a site move, and the slow end is six months to more than a year. Agree a review date with the client before the move, not after traffic dips.
The figures put typical recovery at three to six months, and six months to a year in slow cases, often only at the next core update. Core updates themselves take two to four weeks to roll out.
No. They come from slides at a Google Search Central Live event, described as based on Google's internal analysis, and were reported by attendees. Use them as typical ranges for setting expectations, not as guarantees or a service level.
Connect SEO, Google Ads, Meta Ads, Amazon Ads and more, and send a branded client report on schedule.
No credit card required · Cancel anytime