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.

Built by Patrick Stox

This tool uses the Internet Archive’s Wayback Machine. If it helps your work, consider donating to the Internet Archive. We’re not affiliated.

Feedback
Report a bug

Found something broken in Wayback Change History? Let us know what happened — this goes straight to a private triage queue, not a public list.

What will be sent 
 No tool inputs, uploads, pasted source, complete results, query parameters, or URL fragments are attached automatically. You can edit or remove the selected passage above. Browser and anti-abuse metadata is processed for spam prevention. 
  
 
  
 
 
  
 
 
  
 
How to use it
  1. Enter the complete public URL and load its timeline.
  2. Select the baseline capture.
  3. Choose current, previous, next, or another capture as the comparison target.
  4. Review field-level changes and the extracted-text diff, then open the source capture when context matters.
 
     
 Local data 
Saved targets, named lists, and recent check summaries remain only in this browser.
 
   
 
     
  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.
 
Next stepHistorical Page Comparison — verify it with a direct check.

Explore more
ToolHTTP Header CheckerToolDNS CheckerToolHosting CheckerArticleHTTPS for SEOArticleIndexingArticleTechnical SEO
 
 
 
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.

   
Loading…
  
  ➕ Request a feature   
New requests are reviewed before they appear here.
 
     
  
  
 
 
 
 
    
        
 
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. 
  •  Warnings Material content was removed Fix: Confirm the removal was intentional; otherwise restore the missing production copy and verify it on the live page. 
  •  Warnings Archived page title changed Fix: Confirm whether the archived title change was intentional and restore the preferred title if it was not. 
  •  Warnings Archived canonical changed Fix: Align the live canonical with the intended preferred URL and verify redirects, links, and sitemap entries agree. 
  •  Warnings 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. 
    •