How to view the cached version of any website in 2026
The short answer: Google Cache is gone — the cache:
operator and the "Cached" link were retired in 2024. Today there are two reliable ways
to see a cached or archived copy of a page: the
Wayback Machine (and its cousin archive.today)
for archived snapshots, and the CDN edge cache for the live cached
copy that visitors are actually served — which you can inspect with response
headers or a cache checker. Which one you need depends on
why you're asking.
What happened to Google Cache?
For two decades, "view cached version" meant Google: every result had a Cached
link, and cache:example.com jumped straight to Google's stored copy.
Google removed the Cached links from search results in early 2024 and retired the
cache: operator later that year, saying the feature dated from an era
when pages often failed to load. Google's own search liaison pointed users to the
Internet Archive instead — and for a while Google even linked Wayback Machine copies
in its "About this result" panel. Bing quietly dropped most of its cached links in
the same period. The era of search-engine page caches as a public utility is over.
Option 1: The Wayback Machine — archived snapshots over time
The Internet Archive's Wayback Machine stores point-in-time snapshots of nearly a trillion web pages. Three ways in:
- Search: enter the URL at web.archive.org and pick a date from the calendar.
- Direct URL:
https://web.archive.org/web/2026/https://example.com/pagejumps to the newest snapshot; replace2026with a full timestamp for older ones. - Save a page now: web.archive.org/save archives the current state on demand — useful before content disappears.
Strengths: history (you can compare versions across years), and it's what Google itself recommends. Limits: coverage is uneven for small sites, snapshots can be days or months apart, and JavaScript-heavy pages sometimes archive incompletely.
Option 2: archive.today — on-demand snapshots
archive.today (also archive.ph/archive.is) takes a snapshot of any URL the moment someone asks, and keeps it permanently. It renders JavaScript before archiving, so dynamic pages often capture better than in the Wayback Machine. It's the tool of choice for "preserve exactly what this page says right now" — with the caveat that it's a single independently run service, not a library-backed institution.
The other meaning: the CDN's cached copy of a live site
When developers say "cached version," they usually mean something else entirely: the copy a CDN keeps at its edge locations and serves to visitors instead of hitting the origin. That copy is invisible in any archive — but you can inspect it directly:
$ curl -sI https://example.com/ | grep -iE 'cf-cache-status|x-cache|age'
cf-cache-status: HIT
age: 8412Three headers tell the story: the cache status
(cf-cache-status on Cloudflare,
x-cache on CloudFront/Fastly), the
Age header (how long the copy has
been in cache), and Cache-Control
(how long it's allowed to stay). One catch: each edge location caches independently,
so a curl from your machine shows exactly one location's state. Our free
cache checker queries several regions at once and shows
the status, Age and TTL headers for each.
Which tool for which job
| You want to… | Use |
|---|---|
| See what a page said last month/year | Wayback Machine |
| Preserve a page exactly as it is right now | archive.today (or Wayback "Save Page Now") |
| Read a page that's down right now | Wayback Machine newest snapshot; on Cloudflare sites, the CDN may also serve stale via Always Online |
| Check whether/where a live page is cached at the edge | Cache checker or curl headers |
| Verify your deploy replaced the cached version | Check Age + cache status per region, then purge and re-warm |
FAQ
Is there a replacement for the Google cache: operator?
No direct one. Google removed the cache: operator in 2024 and recommends the Wayback Machine at web.archive.org instead. For live pages, the CDN's edge copy — visible via response headers or a multi-location cache checker — is the closest thing to "the cached version" that still exists.
How do I view the cached version of my own website?
Request it and read the response headers: cf-cache-status (Cloudflare) or x-cache (CloudFront, Fastly) tells you whether the response came from cache, and the Age header tells you how old the copy is. Because every CDN edge location caches independently, check from multiple regions — a free multi-location cache checker does this in one pass.
Can I see a cached version of a page that was deleted?
Try the Wayback Machine first (web.archive.org), then archive.today — one of them has a snapshot of most public pages. CDN caches won't help: they expire within hours to days, and a deleted page's cache entries disappear with the next purge or eviction.
Why does my site still show the old version after an update?
A cache between you and the origin is still serving the previous copy — the browser cache, the CDN edge cache, or both. Check the Age header: a large value on a page you just changed means the CDN copy predates your update. Purge the URL at your CDN, then re-warm it so real visitors don't pay the cache-miss penalty.
See the cached version of any URL — from multiple regions
The free cache checker shows the CDN cache status, Age and TTL headers of any URL from several locations worldwide, in one pass.
Check a URL now