A new report from Google’s Search Central event in Barcelona offers a useful reminder for anyone waiting for a website change to appear in search: different parts of the process run on different timescales. Finding a page, indexing it and reassessing its quality are separate jobs.
For a business in Bath or the surrounding counties, that distinction can prevent two expensive mistakes: repeatedly changing a sound page because results have not moved, or leaving a genuine technical fault untouched because someone said Google needs more time.
What was reported in Barcelona?
In his first-hand recap of the 2 October session, ROAST’s John Campbell reports that Google’s Gary Illyes presented timing ranges based on internal analysis. The examples cover crawling, indexing and changes to search results.
The recap lists around 20 hours as a typical time to discover a new address, around 30 days to refresh a known one, and one to three weeks for a change to Google’s choice of canonical page: the version it treats as the main page among duplicates. It also reports one to three months for a site move, with much longer cases possible.
These are reported reference points, not a timetable for your website. The recap does not provide a sample size, measurement period or definition of “typical”. Some slowest cases are listed as never completing. A figure for one stage also cannot be added to another to promise an arrival date.
Google’s published site-move guidance gives a more familiar qualification: most pages on a small or medium website can take a few weeks to move, larger sites take longer, and processing happens address by address. The event ranges should not replace that guidance or become a new guarantee.
Which part are you waiting for?
Imagine a local company has rewritten a service page. First, Google needs to revisit it. Then its systems need to process the updated content. A change to the wording shown in results is another outcome; improved rankings or more enquiries are further outcomes again. Seeing the latest page in one place does not prove all of those things have happened.
Start with Search Console’s URL Inspection tool for the particular page. Its indexed result describes the version Google has stored, including the last crawl and its selected canonical address. A live test checks the page as it is now. Comparing them helps establish whether Google has seen your change or is still working from an older version.
A successful live test is useful evidence of access, but it does not guarantee indexing or a place in search results. It also cannot predict which canonical address Google will choose. Treat it as one diagnostic check, rather than a certificate that everything is finished.
When waiting is reasonable
If the page works, the intended content is present and there is no identified indexing obstacle, allow time for processing. Record what changed and when, so that the next review has something concrete to compare.
Google’s recrawl guidance says crawling can take days to weeks. It also says repeatedly requesting a recrawl for the same address will not make it happen faster. For a handful of important changed pages, an indexing request may be appropriate; for many pages, an updated sitemap helps discovery. Neither promises inclusion.
Quality reassessment can take longer. Google’s core-update guidance says some improvements can show effects in days, while confirming a wider improvement may take months. That is not evidence that every quiet week needs another rewrite, nor a promise that recovery will arrive after a set number of months.
When to investigate instead
Time will not fix a page that cannot be fetched, an accidental instruction excluding it from indexing, or a broken destination after a move. If inspection identifies an access or indexing problem, ask whoever maintains the site to diagnose that specific issue before waiting for a ranking change.
Keep the intended purpose of the page in view. A deliberate duplicate or excluded page may be correctly configured; it should not automatically be changed because a report flags it. For a domain move, use the checks in our earlier migration article rather than treating elapsed time as the only measure of progress.
The useful question for local search visibility is therefore more precise than “how long does Google take?” Establish which page and which stage you mean. Correct a confirmed fault, give sound changes time to be processed, and judge the business result separately from the technical progress.