Bookmend
← BlogSAVING & ARCHIVING THE WEB

Google Cache Is Gone: How to View Cached Pages Now

By
⚡
THE SHORT ANSWER

Google removed cached pages from search results in early 2024 — the cached link disappeared first, and the cache: operator was fully retired by September 2024. The Wayback Machine at web.archive.org is the most reliable replacement: paste any URL to find dated snapshots. archive.today works better for recent pages and paywalled news. Neither requires an account.

Google Cache Is Gone: How to View Cached Pages Now

Google’s “Cached” link was a reliable shortcut for years. You would click the small arrow next to a search result, tap “Cached,” and see a snapshot of the page as Google last crawled it — useful for pages that had gone down, changed significantly, or simply loaded slowly. That feature is gone now, and so is the cache: search operator that many power users relied on. If you have tried either recently and got nothing, you are not missing something obvious. Google removed them.

This guide explains what happened, when it happened, why Google made the call, and what actually works now for viewing cached or archived versions of pages.

What Google’s Cache Feature Actually Was

When Google’s crawler visited a webpage, it stored a snapshot of that page in its index. This snapshot — called a cached page — was Google’s most recent copy of the content at that URL at the time of the last crawl.

It served two related purposes.

First, it gave you a way to see a page even if the live version was temporarily unavailable. If a site was down, overloaded, or serving an error, you could load Google’s copy instead without waiting for the site to recover.

Second, it let you compare what a page looked like at crawl time versus what it showed now. This was useful for SEO professionals checking how Google rendered a page, for researchers tracking content changes, and for anyone trying to read content that had since been removed or heavily edited.

There were two ways to reach a cached page. The first was the “Cached” link in the small dropdown menu under each search result. The second was the cache: operator — you could type cache:example.com/page directly into the Google search bar and jump straight to the stored snapshot without going through results at all.

Both are gone.

When Google Removed It

The removal happened gradually rather than all at once.

In December 2023, SEO journalist Barry Schwartz reported that cached links were beginning to disappear from search results for some users. Google had not made any announcement, and at first it was not clear whether this was an experiment, a bug, or a decision to retire the feature entirely.

On February 1, 2024, Google’s Search Liaison Danny Sullivan confirmed on X (formerly Twitter) that the cached link was being removed from search results. He explained the reasoning: the cached link existed because, years ago, it was genuinely common for pages to load slowly or fail entirely, making a backup copy valuable for everyday browsing. Those conditions have improved substantially since the feature launched. Pages load reliably for most users in most circumstances now, so the fallback had become largely unnecessary. Sullivan pointed to services like the Wayback Machine as existing options for cases where accessing historical versions of pages genuinely matters.

The change rolled out broadly through early 2024. By September 2024, the cache: search operator was officially retired as well. The URLs at webcache.googleusercontent.com that previously served cached pages now redirect to Google Search rather than showing stored snapshots.

The precise timeline: cached links began disappearing in December 2023, Google’s Search Liaison confirmed the removal on February 1, 2024, and the cache: operator was fully decommissioned by September 2024.

The cache: Operator Is Also Gone

Some users — particularly in the SEO and web development world — skipped the search results interface entirely and typed the operator directly:

cache:example.com

This used to open the cached version of the page immediately, with no extra clicks. You could also add a specific path to check any individual page on a site. It was fast, consistent, and worked from any browser address bar when Google was set as the default search engine.

That operator no longer functions. Typing cache: into Google Search now returns regular search results — the operator is not recognized and no cached content is returned. Browser extensions, bookmarklets, and internal workflows that relied on constructing cache: URLs have all broken as a result.

If you have a tool or workflow that used this operator, it needs to be replaced. The alternatives in the following sections cover what actually works today.

Browser Cache vs Google Cache: A Necessary Clarification

A common source of confusion: people sometimes search for “google cache” or “cached pages” when they actually mean their browser’s local cache. These are completely different things, and it is worth separating them clearly.

Your browser’s cache is a collection of temporary files stored on your own computer. When you visit a website, your browser saves images, stylesheets, scripts, and other assets locally so subsequent visits to the same pages load faster. Clearing your browser cache deletes these local files and forces your browser to re-download everything fresh on the next visit.

Google’s cached pages were server-side copies stored at Google’s data centers after the search crawler visited a page. They had nothing to do with your computer. Clearing your browser cache had no effect on Google’s cached copies, and Google’s removal of cached pages has no effect on how your browser’s local cache works.

If you are trying to speed up your browser, fix display issues, or free up disk space, that is a browser cache question. Chrome’s built-in settings still handle this under Settings > Privacy and security > Clear browsing data, and that feature is unchanged.

If you are trying to view a previous version of a web page that has since changed or gone offline, that is a web archive question — and the sections below cover what works now.

Wayback Machine: The Primary Replacement

The Internet Archive’s Wayback Machine at web.archive.org is the largest publicly available web archive. It has been crawling the web since the 1990s and holds hundreds of billions of pages across decades of crawl history.

To look up a specific URL:

  1. Go to web.archive.org
  2. Paste the URL into the search box
  3. If the URL has been archived, a calendar appears showing which years and dates have snapshots
  4. Select a year, then click a highlighted date, then choose a specific timestamp to load that version

For a page that recently went down, the most recent snapshot is usually the best starting point. For content that changed significantly over time, you can browse earlier dates to find the version you remember.

The Wayback Machine is free, requires no account for basic browsing, and is the most reliable first stop when a page is no longer accessible.

A few practical limitations worth knowing: not every page has been crawled. Pages behind logins, paywalled content, smaller niche sites, and pages that explicitly blocked the Internet Archive’s crawler via robots.txt may have few or no snapshots. There is also typically some lag between when a page is published or updated and when the Wayback Machine captures it, so very recently changed content may not yet be available.

For a detailed guide to navigating snapshots, using Save Page Now, and getting the most out of the archive, see the full walkthrough at /blog/wayback-machine-sites.

archive.today: Better for Recent Pages and Paywalled Content

archive.today — also accessible at archive.ph and archive.is — is a separate service that works differently from the Wayback Machine. Rather than automated background crawling, it archives pages on demand. You submit a URL, the service fetches a complete snapshot immediately, and stores it at a permanent link.

This makes it particularly useful in a few situations.

For news articles behind paywalls: archive.today has historically captured full page content more aggressively than standard automated crawlers, making it a common option for retrieving paywalled journalism that the Wayback Machine may have only partially captured.

For pages that need to be captured right now: because it archives on demand, you can save any public page before it changes or disappears. This is the most reliable way to preserve a page you know you will want later.

For pages with heavy JavaScript: the service sometimes handles dynamic, JavaScript-rendered content more completely than the Wayback Machine’s standard crawlers for certain sites.

To search existing archives at archive.today, enter the URL and you will see a list of saved snapshots ordered by date, with links to the oldest and newest available copies.

The trade-off is historical depth. The Wayback Machine goes back much further and covers far more of the web overall. archive.today is best for on-demand captures and recent content; the Wayback Machine is better for anything more than a year or two old.

The post at /blog/archive-today goes deeper into how the service works and the specific cases where it outperforms the Wayback Machine.

Other Options Worth Checking

Beyond the two main archives, a few other paths are worth knowing about.

Bing’s cached pages. Microsoft’s Bing has maintained a cached page feature. In Bing search results, a Cached option sometimes appears in the menu next to a result. Coverage varies and Bing’s crawl depth is narrower than Google’s was, but it is a reasonable secondary check when the archives come up empty and you specifically want a recent crawl snapshot.

Google’s AMP cache. For pages that were originally served as AMP (Accelerated Mobile Pages), Google’s AMP cache occasionally retains accessible versions at https://[publisher-name].cdn.ampproject.org/c/s/[URL]. This is narrow in scope and only applies to sites that used AMP formatting, but it occasionally surfaces content that has since been removed from the live site.

Search result snippets. When you search for a page that no longer loads, the text snippet Google or Bing shows in results sometimes contains enough of the page’s content to answer your question without needing to load the page at all. Not a true cached page, but a quick way to confirm what a page said if the snippet captures the relevant portion.

Social preview cards. When URLs are shared on platforms like X, LinkedIn, or Facebook, those platforms generate link preview cards that capture the page’s title, description, and sometimes a featured image at the time the link was shared. If a page was widely shared before it changed or went offline, searching for the URL on those platforms can sometimes surface its original headline or description.

For a full comparison of archiving tools and services, /blog/wayback-machine-alternatives covers the broader landscape.

The same problem that made Google Cache useful — pages disappearing or changing — is a persistent issue for anyone who saves links over time. A bookmark is just a pointer to a URL. If the page at that URL is taken down, restructured, moved without a redirect, or the domain expires, the bookmark stops working. You get a 404 error, a domain parking page, or a site that has been completely replaced with different content.

This is called link rot, and it affects saved links at a rate that compounds over time. Pages get restructured when companies redesign their sites. Blogs go offline when their owners stop paying hosting fees. News sites reorganize archives and break old URLs. The link you saved two or three years ago has a meaningful chance of being dead or pointing at something entirely different today.

Bookmend is a free Chrome extension built around this problem. It scans your existing Chrome bookmarks and identifies which links are dead, which are redirecting to unexpected destinations, and which still resolve correctly. For dead bookmarks, it queries the Internet Archive to find the snapshot closest in date to when you originally saved the bookmark — so you recover the version of the page you actually saw when you saved it, not just any random historical snapshot.

It works entirely with your local Chrome bookmarks folder with no account required. Your bookmark data stays on your computer. The dead-link check is free, and the recovery workflow surfaces archived snapshots directly from within the extension.

If you have been collecting bookmarks for a few years, dead links are almost certainly in there. The free bookmark rot check at bookmend.app scans your collection in about 60 seconds and shows you exactly what has broken.

For more detail on why bookmarks break and what the recovery process looks like, the guide at /blog/website-archive covers both manual and automated approaches to keeping your saved pages accessible.

What Changes in Practice

If you relied on Google Cache for specific workflows, the practical impact depends on how you used it.

For the occasional “this page will not load right now” situation: the Wayback Machine handles this well. Paste the URL, find the most recent snapshot, load the page. It takes a few extra steps compared to clicking “Cached” from search results, but the result is comparable for most purposes.

For checking how Google renders specific pages for SEO work: this use case has no perfect replacement. Google’s URL Inspection tool in Search Console shows indexing status and can render a page as Googlebot sees it, but it is not the same as browsing a cached snapshot. This is a genuine gap the removal created for technical SEO practitioners.

For research and content recovery on pages that have changed or disappeared: the Wayback Machine and archive.today are arguably better than Google Cache was for serious research use cases. They offer longer historical range, date-specific snapshots, and more consistent long-term storage. Google Cache only ever showed the most recent crawl — it was a snapshot of one point in time, not a historical archive.

For recovering dead bookmarks specifically: Bookmend automates the Wayback Machine lookup and matches the snapshot to your actual save date, which is more targeted than manually navigating the archive calendar.

Google Cache’s removal is a genuine inconvenience for users who relied on it, but the Internet Archive’s infrastructure was always more comprehensive for the use cases that matter most. The adjustment mostly involves knowing where to go now rather than losing a capability entirely.

Frequently asked questions

Yes. Google has fully removed the cached pages feature from search results. The visible cached link that appeared under search results is gone, the cache: search operator no longer returns cached content, and the webcache.googleusercontent.com URLs that served snapshots now redirect to regular search results. There is no official workaround to restore this functionality.

Google's Search Liaison confirmed the removal on February 1, 2024, after users began noticing cached links disappearing from search results in December 2023. The rollout was gradual throughout early 2024. The cache: search operator was fully decommissioned by September 2024, completing the removal.

Google's Search Liaison explained that the cache feature originally existed because pages frequently failed to load or loaded slowly, making a backup copy genuinely useful for everyday browsing. That problem has become much less common. Google cited improved webpage reliability as the reason the feature was no longer necessary, and noted that the Internet Archive's Wayback Machine serves the historical access use case more appropriately.

No. Typing cache:example.com into Google Search no longer returns a cached version of that page. The operator is not recognized and produces regular search results instead. Any browser extensions, bookmarklets, or internal tools built around cache: URLs will also have stopped working.

The Wayback Machine at web.archive.org is the most comprehensive replacement for most use cases. It holds hundreds of billions of archived pages going back to the 1990s and is free to use without an account. For pages that need to be archived right now or for paywalled news content, archive.today is a useful complement — it archives pages on demand and handles some content types more completely.

Go to web.archive.org, paste the URL you want to find into the search box, and press Enter. If the page has been archived, you will see a calendar view showing which dates have snapshots. Select a year, then click a highlighted date, then choose a specific timestamp. That loads the archived version of the page as it appeared on that date. The most recent snapshot is usually the best starting point for pages that recently went down.

Bing still maintains a cached page feature similar to what Google offered. In Bing search results, you can sometimes find a Cached option in the three-dot menu next to a result. Coverage and availability vary by page and region, and Bing's crawl depth is narrower than Google's was, but it is a reasonable secondary option when the major archives do not have what you need.

Browser cache refers to temporary files your browser stores locally on your computer — images, scripts, and stylesheets saved to speed up repeat visits to the same sites. Google cache referred to Google's server-side snapshots of web pages stored after the search crawler visited them. These are completely separate systems. Clearing your browser cache has no effect on web archives, and Google's removal of cached pages has no effect on your browser's local cache.

archive.today is an on-demand archiving service — you submit a URL and it immediately captures and stores a snapshot. The Wayback Machine runs automated crawlers that archive pages without user prompting. archive.today is better for capturing pages right now and for some paywalled content. The Wayback Machine is better for historical depth, going back decades for many sites. They complement each other well.

Several reasons: the site blocked the Internet Archive's crawler using robots.txt, the page required a login or was behind a paywall at crawl time, the page was very recently published and not yet crawled, or the site was small and infrequently crawled. If the Wayback Machine has nothing, try archive.today next. Some content may simply not be recoverable through any public archive.

The Wayback Machine's Save Page Now feature at web.archive.org/save accepts any public URL and creates an archived snapshot immediately. archive.today offers the same capability — paste a URL and click the save button. Both are free. Using either service before a page goes down is more reliable than hoping a search engine's automated crawler happened to visit it recently.

Link rot describes the process by which URLs stop working over time as pages are moved, restructured, or deleted without proper redirects, and as sites and domains shut down entirely. It affects bookmarks meaningfully — links saved several years ago have a significant chance of being dead or pointing at different content today. Regular bookmark audits can surface dead links before you need them.

Bookmend is a free Chrome extension that scans your existing bookmarks and identifies dead links. For each dead link, it queries the Internet Archive to find the snapshot closest in date to when you originally saved the bookmark. This gives you the version of the page you actually bookmarked rather than an arbitrary historical snapshot. No account is required and your bookmark data stays on your computer.

Nafiul Hasan
WRITTEN BY

Nafiul Hasan is the founder of Bookmend. He builds tools that fix small, specific frustrations rather than reinvent them — Bookmend started after losing a decade of bookmarked research links to dead pages he couldn't get back. He writes here about link rot, how the Wayback Machine actually works, and what's real versus marketing in the browser-extension space.

Drafted with AI assistance, reviewed and edited by Nafiul Hasan.How we write

FounderChrome extension builderWrites about link rot & bookmarks