If you clicked the three dots next to a Google result this week and could not find the “Cached” link, you are not imagining it. Google has removed the cache link from search results, and it is not coming back. The Google cache link is gone for good, and the cache: search operator is going away too.
For most website owners, this changes very little. But many SEOs used the cache every week, so in this article I explain what changed, why Google did it, and the tools I now use for each job the cache used to do.
What Happened to the Google Cache Link
For years, Google kept a stored copy of most pages it crawled and let anyone view that copy. You reached it through a “Cached” link near each result. In recent years that link moved from a small menu next to the result into the “About this result” panel.
Over the last few months, the link started to disappear from more and more results. On 1 February 2024, Google’s Search Liaison, Danny Sullivan, confirmed on X that the feature has been removed. He called it “one of our oldest features.”
He also said the cache: operator (typing cache:example.com into Google to open the stored copy) will go away as well. At the time of writing it may still work for some pages, but I would not build any process around it.
Here is what this does and does not mean:
- Gone: the public link that let anyone see Google’s stored copy of a page.
- Going: the
cache:search operator. - Not changed: how Google crawls, stores and indexes pages. Google still keeps copies of pages to build its index. It just no longer shows them to the public.
Why Google Removed the Cache Link
Google’s reason is simple. The cache was built for a time when web pages often failed to load. If a site was slow or down, the cached copy let searchers still read the content.
Sullivan said that “things have greatly improved” since then, so Google decided to retire it. Most sites today load reliably, and when one is down, people usually just pick another result.
In my view, there is a second, unspoken reason. Keeping a public viewer for billions of stored pages costs effort, and very few normal searchers ever used it. SEOs and researchers were the main users, and Google has other tools for site owners.
Sullivan also said he personally hopes Google might add links to the Internet Archive inside “About this result”, where the cache link used to be. He was clear that there were no promises. So for now, treat that as a hope, not a plan.
What the Google Cache Link Was Used For
Before looking at replacements, it helps to list the jobs the cache did. When I think about it, SEOs used it for five main things:
- Checking when Google last crawled a page. The cached copy showed a date at the top, which gave a rough idea of when Googlebot last fetched the page.
- Seeing the text Google could read. The “Text-only version” stripped out styles and scripts, which helped spot content hidden in images or loaded in odd ways.
- Spotting cloaking and hacks. Some hacks show spam only to Googlebot. The cache sometimes showed that spam when the live page looked clean.
- Reading a page that was down or changed. If a page was offline or had just been edited, the cache showed the older version.
- Looking at competitor pages. You could see roughly what Google had stored for any site, not just your own.
The first four now have decent replacements for your own sites. The fifth is where SEOs lose the most, because there is no Google tool that shows the stored copy of someone else’s page.
The Cache Was Never a Perfect View of Indexing
One thing I want to clear up, because I still see it confused often. The cached page was not an exact picture of what Google indexed.
The cache stored the HTML Google fetched. When you opened it, your own browser then tried to load the scripts, styles and images from the live site. So a JavaScript-heavy page often looked broken or empty in the cache, even when Google had rendered and indexed it fine.
In my experience, this caused a lot of false alarms. People saw a blank cached page and assumed Google could not see their content. Usually the problem was only the cache viewer.
So in one way, losing the cache pushes SEOs toward better tools. The tools below show what Google actually rendered, not just what your browser made of the stored HTML.
What SEOs Can Use Instead
There is no single replacement for the Google cache link. Instead, I use a small set of tools, each for a different job.
URL Inspection in Search Console
For pages on sites you own or manage, the URL Inspection tool in Google Search Console is the best replacement. Sullivan pointed site owners to it as well.
When you inspect a URL, it shows the indexed version of the page, including:
- Whether the URL is on Google, and why not if it isn’t.
- The last crawl date and which Googlebot type crawled it.
- The Google-selected canonical (the version Google picked as the main one when there are duplicates).
- Under “View crawled page”, the HTML Google stored, the HTTP response headers and more details.
The “Test live URL” button fetches the page right now, as Googlebot. That view adds a screenshot and the rendered HTML (the code after JavaScript has run). Google’s URL Inspection tool help page notes that screenshots are only available in the live test, not for the indexed version.
This covers the crawl date, the text Google can read and the hack check far better than the cache ever did. If you work with many URLs, I covered the Search Console URL Inspection API in an earlier article, which lets you pull the same data in bulk.
The Rich Results Test for Any Public URL
The Rich Results Test is meant for checking structured data, but I use it as a quick “what does Googlebot see” tool. It works on any public URL, so you don’t need Search Console access.
Run a URL, then open “View tested page”. You get the rendered HTML, a screenshot and a list of resources that could not load. You can also switch between the smartphone and desktop crawler.
This matters more now because Google retired the Mobile-Friendly Test in December 2023, along with the report I wrote about in Google Retires the Mobile Usability Report. The Rich Results Test is the main public tool left that renders a page the way Google does.
One limit: it is a live fetch. It shows the page as it is now, not the copy Google stored last week.
The Wayback Machine for Old Versions
For “what did this page look like before?”, the Internet Archive’s Wayback Machine is now the go-to option. It stores snapshots of many public pages over time, often going back years.
It is especially useful for competitor research. You can see how a competitor’s page, title or offer changed around the time of a ranking shift.
Keep its limits in mind:
- It does not capture every page, and smaller sites may have few snapshots.
- Snapshots can be days, weeks or months apart.
- It shows what the archive saw, not what Google indexed.
Other archive services exist too, but I treat all of them the same way: helpful for history, not proof of what Google has.
Your Own Crawls and Change Logs
The cache was a free safety net for “what did my page say last month?” Without it, I recommend keeping your own record.
A few simple options:
- Use the revision history in your CMS, such as WordPress post revisions.
- Run a site crawl on a schedule and save the exports, so you can compare titles, headings and word counts over time.
- Use a page change monitoring tool for your most important pages, like money pages and top landing pages.
- Keep a short change log of big edits, migrations and template changes with dates.
When rankings drop, the first question I ask is “what changed?” A change log answers that much faster than any cache did.
How to Check What Google Sees on Your Page Now
Here is the process I follow now when I would once have opened the cache for one of my own pages.
- Open URL Inspection. In Search Console, paste the full URL into the search bar at the top and wait for the result.
- Check the index status. Confirm whether the URL is on Google, and note the last crawl date and the Google-selected canonical.
- View the crawled page. Click “View crawled page” and search the HTML for your main heading and a key sentence, to confirm Google stored the content you expect.
- Run a live test. Click “Test live URL”, then “View tested page”. Check the screenshot and look at “More info” for blocked or failed resources.
- Compare with the live page. Open the page in a normal browser. If Googlebot sees different content, such as spam links or missing text, treat it as a possible hack or rendering problem.
- Check a second view if needed. For a quick outside check, or for a page you don’t own, run it through the Rich Results Test and compare.
If the page has changed and you want Google to see the new version sooner, you can click “Request indexing” after the live test passes. Don’t overuse it; it has a daily limit and does not guarantee faster indexing.
Replacing Each Old Cache Task
This table sums up where I now go for each job.
| Old cache task | Best replacement | Works for other sites? |
|---|---|---|
| See when Google last crawled a page | URL Inspection (last crawl date) | No |
| See the text and HTML Google stored | URL Inspection, “View crawled page” | No |
| See how Google renders the page | URL Inspection live test or Rich Results Test | Rich Results Test only |
| Spot spam shown only to Googlebot | URL Inspection live test or Rich Results Test | Rich Results Test only |
| Read a page that is down or changed | Wayback Machine or your own records | Yes (Wayback) |
| Track competitor page changes | Wayback Machine or a change monitoring tool | Yes |
What About the noarchive Tag?
Some sites use the noarchive robots meta tag. It told Google not to show a cached link for the page. Publishers often used it so people could not read paid content through the cache.
With no public cache link in Google, the tag no longer has much to do in Google Search. I would not rush to remove it, though. It does no harm, and other search engines may still respect it.
If you were using noarchive to protect paywalled content, keep in mind that the Wayback Machine and other archives are separate. They have their own rules for what they capture.
Does the Cache Removal Affect Rankings?
No. The cache link was a viewing feature for people. It was not a ranking signal, and removing it does not change how pages are crawled, indexed or ranked.
So if you see a traffic change this week, look elsewhere first. Check Search Console performance data, your recent site changes, and the Google Search Status Dashboard for any confirmed updates or incidents.
The one small effect I can think of is on trust and research, not rankings. Searchers who used the cache to read slow or blocked pages now have to go elsewhere. For site owners, that is one more reason to make sure your pages load fast and reliably.
What I’m Changing in My Own Workflow
Honestly, I stopped relying on the cache for technical checks a while ago, because of the JavaScript issue above. URL Inspection was already my first stop for my own sites.
The main change for me is competitor research and history. I now check the Wayback Machine first, and for important competitor pages I set up change monitoring instead of hoping a cached copy exists later.
For client audits, I’ve also added one habit: I save a crawl export and screenshots of key pages before any big change. That way I never need a third party’s copy to know what the site looked like.
My advice: don’t waste time looking for workarounds to keep using the cache: operator. Google has said it is going, so build habits on tools that will still be there next year.
Final Thoughts
The Google cache link was a small feature, but a lot of SEOs leaned on it. Now that the Google cache is removed, the job splits across a few tools: URL Inspection for your own pages, the Rich Results Test for a quick public check, the Wayback Machine for history, and your own records for everything else.
A good next step is to inspect your three most important URLs in Search Console today and run a live test on each. It takes ten minutes, and it shows you exactly how Google sees the pages that matter most to your business.
