Review a page's archived timeline
Load available cached archive snapshots and see when meaningful text changes appear.
Wayback Change History
Free, no signup. Compare a selected archive capture with today’s live raw HTML, an adjacent capture, or any other returned capture. Archive coverage is evidence, not proof of what every visitor saw.
This tool uses the Internet Archive’s Wayback Machine. If it helps your work, consider donating to the Internet Archive. We’re not affiliated.
How to use it
- Enter the complete public URL and load its timeline.
- Select the baseline capture.
- Choose current, previous, next, or another capture as the comparison target.
- Review field-level changes and the extracted-text diff, then open the source capture when context matters.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Choose comparison
Observable facts
Extracted-text comparison
Portable audit bundle
Historical data is provided by the Internet Archive. Support its preservation work if you can.
Rate this tool
Checks run from our server; we fetch the URL you enter and don't keep the results. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.
Example result
A comparison might show that the selected archive capture used one canonical URLHow search engines pick one canonical URL among duplicates and consolidate signals onto it. while the current raw HTML uses another, alongside the exact title, robots, heading, and extracted-text changes. Each difference is evidence to investigate, not an automatic SEO defect.
How it works
The tool loads a bounded capture timeline, fetches the two selected raw-HTML sources through the site API, extracts the same observable fields from each, and computes a capped text diff. It does not execute archived JavaScript or replay subresources.
What is compared
HTTP status where available, title, meta description, canonical, robots directivesThe robots meta tag is an HTML element in a page's head — <meta name="robots" content="noindex"> — that tells search engines how to index and serve that page. It's crawl-then-obey: a page blocked in robots.txt is never fetched, so the tag is never seen., H1s and heading outline, hreflang declarationsHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others., JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. type evidence, extracted word count, links, images, and images missing an alt attribute. Every value comes from bounded raw HTML; a difference is a review prompt rather than an automatic defect.
Limitations
Archived captures can be incomplete or replay incorrectly. Current and archived fetches can occur at different times. Text extraction includes templates and navigation, schema counts include malformed JSON-LD blocks, and truncated HTML can undercount facts. No scripts execute and no archived subresources load.
Frequently asked questions
What can I compare?
Choose one archived capture, then compare it with the current live raw HTML, the previous capture, the next capture, or any other capture in the returned timeline.
Does this reproduce an old rendered page?
No. It compares bounded raw-HTML facts and extracted text. It does not run archived scripts or load archived styles, images, fonts, or other subresources.
Does a missing capture prove the page did not exist?
No. Archive coverage can be incomplete, excluded, or unavailable. A missing capture is only absence from the returned timeline.
Is this affiliated with the Internet Archive?
No. The tool uses the Wayback Machine and links to the Internet Archive donation page, but this site is not affiliated.
Feature requests for Wayback Change History
Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
Where this tool helps
Common use cases
Investigate a traffic change
Compare snapshots around a known decline or recovery to find content edits worth deeper analysis.
Recover prior wording
Locate an earlier version of a section as a reference for editors without treating the archive as complete.
Document historical evidence
Create a dated comparison record and note missing captures or fetch limits before drawing conclusions.
Watch the full workflow
Wayback Change History walkthrough
Read the transcript
Wayback Change History
Historical pages can help explain when titles, canonicals, headings, content, links, or robots directives changed—but archive evidence has important boundaries. I’ll show you how to load a timeline, choose a baseline and comparison, read field and text changes, preserve a portable audit bundle, avoid unsupported conclusions, and turn the evidence into a focused investigation.
Step 1
Use this tool during a migration review, traffic-loss investigation, content refresh audit, canonical diagnosis, or historical competitor study. It compares bounded raw-H-T-M-L facts and extracted text; it does not recreate everything an old visitor saw.
Step 2
Enter the complete public U-R-L and select Load timeline. The tool requests a bounded set of returned Internet Archive captures. No result or a missing date means absence from that returned timeline—not proof the page did not exist.
Step 3
Select the archived baseline, then compare it with the current live page, the previous capture, the next capture, or another returned date. Adjacent captures help narrow a change window; a specific later capture supports controlled historical comparisons.
Step 4
This walkthrough uses fictional example dot com dates and values so the interface stays stable without claiming a live archive result. A real run fetches the timeline, then retrieves the selected raw-H-T-M-L sources only when you select Compare.
Step 5
Read the source note before interpreting differences. It records the selected capture, comparison source, raw-H-T-M-L boundary, text-token cap, and truncation warnings. Open the archive source link when visual or surrounding context matters.
Step 6
The facts table compares status, title, meta description, canonical, robots, headings, hreflang, schema evidence, word count, links, images, and missing-alt counts. Changed shading means the captured values differ; it does not label the newer or older value as correct.
Step 7
The extracted-text comparison highlights removed and added tokens, capped at the first two thousand. Navigation and template text can appear alongside main content, so use the diff to locate a change, then inspect the original captures before drawing conclusions.
Step 8
A changed canonical, noindex directive, heading, or content block can refine an investigation window. Compare that timing with releases, C-M-S revisions, Search Console, analytics, server logs, and stakeholder records. Correlation alone does not establish the cause of a performance change.
Step 9
After a real comparison, download the portable audit bundle. It records the structured evidence with shared sanitization and omits text token values. Later, import a saved bundle to compare it with a newly run audit and count changed data points.
Step 10
Archive captures may be incomplete, excluded, or replay incorrectly. Current and archived fetches happen at different times. Scripts and archived subresources do not run, truncated H-T-M-L can undercount facts, and malformed schema blocks still affect counts. This is observable evidence—not a rendered-page reconstruction.
Step 11
The Internet Archive provides the historical data, and this site is not affiliated. Open the original capture when you need layout or surrounding context, and consider supporting the Archive’s preservation work if this evidence helps your research.
Step 12
Choose the most relevant changed field, verify it in the cited sources, and write a narrow question about timing and mechanism. Gather independent evidence, document alternate explanations, and fix only current issues you can confirm. Save the bundle and capture links with your audit notes.
Use history as evidence—not as a verdict.
Open the cited captures, confirm the relevant change in context, and compare its timing with deployments, analytics, Search Console, logs, and stakeholder records. Form one testable explanation, document uncertainty, and fix only current problems you can verify. Preserve the audit bundle so later reviews can reproduce the evidence boundary.
Common issues & how to fix them
- Information Archived text changed materially Fix: Compare the archived wording with the intended release, then restore omitted copy or document the approved content change.
- Warning Material content was removed Fix: Confirm the removal was intentional; otherwise restore the missing production copy and verify it on the live page.
- Warning Archived page title changed Fix: Confirm whether the archived title change was intentional and restore the preferred title if it was not.
- Warning Archived canonical changed Fix: Align the live canonical with the intended preferred URL and verify redirects, links, and sitemap entries agree.
- Warning Archived HTTP status changed Fix: Confirm the current URL returns the intended status and repair accidental redirects or error responses.
- Information Archive history contains a long capture gap Fix: Use other dated evidence for the uncovered interval; the archive cannot prove what appeared between captures.