Google's Cached Pages Are Gone

The cache link and the cache: operator were both retired in 2024. Here is what to use instead, depending on what you were actually trying to do.

Quick answer

Google removed cached page links from search results during 2024 and retired the cache: operator later that year. Nothing you do will bring them back. For page history use the Wayback Machine; for what Google stored about your own page use URL Inspection in Search Console; for a cached copy of someone else's page right now Bing still has one.

What actually happened

For most of Google's existence, every result carried a link to a stored copy of the page as Googlebot last saw it. It was useful when a site was down, slow, behind a paywall that had not always been there, or had been edited since you last looked.

During 2024, Google removed those links from the results page. Later the same year the cache: search operator stopped working too — it no longer returns a stored copy, just ordinary results for whatever you typed.

Google's stated reasoning was that the feature was built for an era when pages frequently failed to load, and that this problem has largely gone away. Whether or not you find that convincing, the practical position is settled: there is no Google cache and no replacement for it inside Google.

Pick your replacement by what you were doing

"The cache" served at least four unrelated jobs. They have four different answers now, and choosing the wrong one is why people conclude nothing works.

You wanted to see how a page used to look

Use the Wayback Machine at archive.org. This is a genuine upgrade rather than a workaround: Google's cache held one recent copy, while the Wayback Machine often holds years of snapshots, so you can watch a page change over time.

Google now surfaces Wayback Machine links itself, in the "About this result" panel behind the three dots next to a search result.

You wanted to check what Google has for your own page

Use URL Inspection in Google Search Console, then "View crawled page". You get the exact HTML Googlebot received, a rendered screenshot, and a list of resources the renderer could not load.

This was always better than the cache for this purpose. The cache showed you a rendering; URL Inspection shows you Google's actual view, including the JavaScript that failed and the CSS it was blocked from fetching.

You wanted a cached copy of a page that is down right now

Bing still has one. Click the dropdown arrow beside a Bing result to reach its cached copy. Yandex retains cached versions too. The feature has not disappeared from the web — it disappeared from Google.

You wanted to capture a page before it changes

archive.today captures on demand, which the Wayback Machine also supports via "Save Page Now". If you are documenting something that may be edited or deleted, capture it deliberately rather than hoping a crawler happened to be there.

The one thing the cache was never for

A persistent misunderstanding, worth stating plainly: the cache was never a ranking signal, never an indicator of indexing health, and never something to optimise for. Pages were not "in the cache" as a status distinct from being in the index.

If you were checking the cache to confirm Google had picked up a change, that instinct was sound but the tool was indirect. URL Inspection answers the question properly — it tells you the last crawl date and lets you compare what Google holds against what you published.

If you are here because a change is not showing up

That is the most common reason people go looking for the cache, and it is a different problem with a different fix. Google has to re-crawl the page before anything you changed can be reflected.

Why Google is not indexing my page How Googlebot works

For Bing, Yandex and the other IndexNow engines, you can notify them directly that a URL changed — that is what this tool does. It does not apply to Google, which has no equivalent open endpoint.

Frequently asked questions

Does the cache: search operator still work?
No. Google removed the "Cached" links from search results during 2024 and retired the cache: operator later the same year. It now returns ordinary search results for the URL you typed, rather than a stored copy of the page. There is no replacement operator.

Why did Google remove it?
Google's public explanation was that the feature existed to help people read pages that would not load reliably, and that page loading has improved enough that the original reason no longer applies. The cache was also widely used for purposes Google never intended, including competitive research and checking what a site looked like before an edit.

How do I see an old version of a web page now?
The Internet Archive's Wayback Machine is the general answer, and it holds far more history than Google's cache ever did — often years of snapshots rather than one recent copy. Google itself now links to it from the "About this result" panel on many results. archive.today is a useful second source, since it captures on demand and holds pages the Wayback Machine has missed.

How do I see what Google actually stored for my own page?
Use the URL Inspection tool in Google Search Console and select "View crawled page". This shows the raw HTML Googlebot received, the rendered screenshot, and any page resources that failed to load. For your own site this is strictly better than the old cache ever was — it shows Google's actual view, including what its renderer could not fetch.

Do other search engines still have a cache?
Bing still offers cached copies for many results, reachable from the dropdown arrow next to a result. Yandex also retains cached versions. So the feature is not gone from the web generally — it is gone from Google, which is where most people were using it.

Does the cache being gone affect my SEO?
No. The cache was a way for humans to view a stored copy. It was never a ranking factor and its removal changes nothing about how your pages are crawled, indexed or ranked. If you were using it to verify that Google had picked up a change, switch to URL Inspection, which answers that question far more directly.