You change a page, publish it, and the preview snippet still shows what you removed two weeks ago. It feels like Google is ignoring you, but the truth is more mechanical: Google only updates what it recrawls, and it recrawls on its own schedule unless something tells it to hurry. Between your page and that snippet sit three layers — your host's cache — A ready-made copy of your pages kept warm so the server doesn't rebuild everything on every visit., your CDN — Content Delivery Network — copies of your files served from cities near each visitor, so pages load faster worldwide.'s cache, and Google's own cache and index — and each one can hold an older copy. Knowing which one is stuck is the entire diagnostic.
Check these first, yourself
Open `site:yourdomain.com/pagename` and click the cached/About this result preview: the screenshot shows which layer serves the old copy — Google's cache, or your server.
Check your page's last crawl date in Search Console (URL Inspection → 'Last crawl'). If the crawl date is old, Google hasn't re-visited — that's the layer to speed up.
Request a re-crawl from that same URL Inspection panel: 'Request Indexing'. Google queues it, and a real update usually follows within a day or two.
Clear your CDN and hosting — The service that runs your site on a server; the plan you pick decides your speed ceiling and your crash risk. cache for that URL. If the CDN still serves the old HTML, even a perfect recrawl will re-capture a stale page — cache invalidation belongs to you, not Google.
Should you fix it yourself or call a rescue?
Still have questions?
Is Google legally or algorithmically 'stuck' on an old version?
No. Search engines are crawling machines with budgets. If your page's priority is low or your CDN keeps serving identical-old content, Google has little reason to re-crawl. It's not a penalty and not a blacklist — it's crawl economics.
How long does a re-crawl request take?
Usually a day to a few days for a normal page. If a week passes with no new 'last crawl' date, the deeper three-layer check (host cache, CDN, redirect) is where the problem sits.
Does 'Request Indexing' cost anything?
No, it's free in Google Search Console and you can use it on one page at a time. What it doesn't do is override technical staleness — a cached CDN still hands Google the old file regardless of your request.