Added
A canonical URL appears only in the newer scope.
Whole-site time travel
Compare the website that was with the website that is.
Open two completed scoping snapshots and see page inventory, redirects, rendered HTML, archived CSS, visual captures, templates and automated accessibility movement—without fetching today's live site.
Example comparison
Spring release · whole-site movement
14 Apr18 Jul
- Added
- +6
- Removed
- −2
- Changed
- 31
- Unchanged
- 109
Before
HTML + CSS archivedStart trial
After
Current scopeGenerate report
−<button>Start trial</button>+<button>Generate report</button>
Change classification
One comparison. Eight useful answers.
A page is not simply “different.” OnChange records which evidence identity moved so reviewers can filter the site to the kind of change they actually need to inspect.
Removed
A previously scoped URL no longer appears in discovery.
Redirected
The final URL or redirect outcome changed between captures.
HTML changed
Rendered document identity or reviewable line evidence moved.
CSS changed
The archived stylesheet bundle differs between versions.
Visual changed
The deterministic screenshot comparison detected movement.
Template changed
The page moved into a different structural family.
Accessibility changed
Automated findings are new, resolved or persistent.
Evidence views
Choose the view that answers the question.
Review the visual record, inspect a safe page replay or read exact line evidence. Every view stays attached to the same archived capture pair.
Resizable archived replay
Place the two historical HTML and CSS states side by side, resize the split and review responsive flow without executing page scripts.
Captured screenshots
Use desktop and mobile images when exact pixels matter or a dynamic page cannot be fully reconstructed in safe replay.
HTML line evidence
Read inserted and deleted markup with bounded, searchable output for engineering handoff and audit notes.
Manifest-level reasons
See whether content, style, template, redirect, visual, accessibility or capture state caused the page to be classified as changed.
Reproducible by design
The live site cannot rewrite the past.
Comparison reads completed manifests and content identities only. It never performs a new browser capture, HTTP request or live storage discovery while calculating the result.
- Same ordered pair returns the same comparison identity
- Unrelated sites and incomplete captures are rejected
- Archived scripts never execute inside replay
- Blocked and failed states remain first-class evidence
Historical boundary
Archived evidence in. Deterministic explanation out.
The current website is deliberately absent from the calculation.
FAQ
Historical comparison, clearly bounded
- Does snapshot comparison load the current live website?
- No. Comparison reads the two completed evidence manifests and their archived artifact identities. Opening an archived replay also uses scriptless, networkless evidence rather than asking the live origin for current resources.
- Can I compare snapshots from two different websites?
- No. OnChange only compares completed snapshots belonging to the same watched site. Rejecting unrelated scopes prevents misleading added-and-removed totals and keeps the comparison identity deterministic.
- What happens when an older HTML capture has no archived CSS?
- New scope captures archive their corresponding stylesheet bundle. Legacy monitor history may use the current known stylesheet as a clearly labelled approximation, while visual-monitor screenshots remain the strongest pixel-level evidence for those older states.
- Is website time travel a pixel-perfect browser emulator?
- No. Archived replay is intentionally scriptless and blocks live network requests for safety and reproducibility. The report combines replayable HTML and CSS with the captured desktop and mobile screenshots, which remain the exact visual evidence from that run.
Capture twice. Explain the movement.