Wayback Machine alternatives: how to see old versions of a website
PageWatch team · November 13, 2026 · 4 min read
Short answer: The Wayback Machine (web.archive.org) is still the first place to look for an old version of a page: type the address, pick a date on the calendar, open a capture. When it doesn't have the page or the date you need, your options are other public archives, the site's own records, and, for the future, keeping your own history by monitoring the page. The only way to be sure you'll have tomorrow's version of a page is to start saving it today.
How to use the Wayback Machine properly
The Internet Archive's help center explains the basics:
- Enter the address on web.archive.org and press "Browse History".
- Pick a capture from the calendar. Dots are colored by what the crawler got back: blue for success, green for a redirect, orange for a client error, red for a server error. You almost always want the blue ones.
- List everything under a site with a wildcard address such as
web.archive.org/*/www.example.com/*. - Save a page now with "Save Page Now". It saves that one page once; it doesn't add the address to future crawls or save a whole site.
New crawls aren't instant: the Archive mentions a lag of three to ten hours between a crawl and its appearance in the Wayback Machine.
Why the page you need may not be there
The help center lists the usual reasons:
- The crawler never found it, for example an orphan page with no links pointing to it.
- The site is password protected, blocked by robots.txt, or excluded at the owner's request.
- The page depends on scripts that call the original server, so the capture is empty or broken.
Simple HTML pages are the easiest to archive; app-like pages and anything behind a login are the hardest.
Alternatives when the Wayback Machine falls short
1. Other archives and caches
Other public web archives exist (national libraries run their own, and some services let anyone save a snapshot on demand). Coverage varies a lot, so treat them as a second chance, not a guarantee.
2. The site's own history
- Changelogs, release notes and press pages often record what changed and when.
- Sitemaps sometimes include a last-modified date per page (see how to check when a website was last updated).
- Version histories exist on wikis, documentation sites and public code repositories.
- Ask the owner. For policy or pricing pages, companies sometimes share previous versions on request.
3. Your own records
Your browser history, saved PDFs, screenshots in a ticket or a chat, emails that quote the page. If you needed the page once, look where you used it.
Keep your own history from now on
Archives capture pages when their crawlers pass by. If a specific page matters to you (a competitor's pricing, the terms you agreed to, a product you're waiting for), the reliable option is to monitor it yourself, so every version is saved the moment it changes.
There are three ways to do it:
| Option | How it works | Good for |
|---|---|---|
| Self-hosted open source | changedetection.io is Apache-2.0 software you run with Docker or pip; its README also offers a hosted plan | Technical users who want full control |
| Browser extension + cloud | Distill runs local monitors in your browser (which must stay open) and cloud monitors on its servers | People who want many options and channels |
| Hosted, condition-based | PageWatch checks the page on a schedule, keeps the latest versions and emails you only when a change matches what you're waiting for | People who want one plain-English email |
Whatever you pick, monitoring gives you something archives can't: the exact moment a page changed, and the lines that changed.
A practical routine
- Today: look the page up in the Wayback Machine and save a copy with "Save Page Now".
- Same day: start monitoring it so future changes are recorded.
- When it changes: keep the alert email (it contains the lines added and removed) and, if it matters, save a new archive snapshot.
Common mistakes
- Trusting a single capture. Captures can be partial; open several dates.
- Ignoring redirects. A green dot may land on a different page than you expect.
- Waiting until you need the old version. By then it may be gone.
- Monitoring pages you shouldn't. Watch public pages only and respect the site's robots.txt; that's also what archives do.
FAQ
Is the Wayback Machine free? Yes, it's run by the Internet Archive, a non-profit.
Can I see a page that was behind a login? Generally no. Archives and monitors only see public pages.
How do I prove what a page said on a date? An archive capture with its date is the most widely recognised public record. Keep your own monitoring emails as a supporting record.
What's the easiest way to track one page going forward? Paste it into PageWatch and choose daily checks; it's free for three pages.
Sources
- Internet Archive Help Center: Using the Wayback Machine (read 13 Nov 2026)
- changedetection.io (GitHub README) (read 13 Nov 2026)
- Distill Web Monitor documentation (read 13 Nov 2026)