Change history
SEO change tracking with historical context
See what changed, when Crawle detected it, and which URLs were affected across titles, headings, canonicals, redirects, indexability, and content signals.
SEO change history
SEO change history
Field-level changes on crawle-demo.io — what changed, when, and which pages need review
Changes over time
Detected changes per day on crawle-demo.io — last 30 days
- Critical
- Warning
- Info
| Date | Critical | Warning | Info |
|---|---|---|---|
| May 11, 2026 | 0 | 1 | 1 |
| May 12, 2026 | 0 | 0 | 2 |
| May 13, 2026 | 1 | 1 | 0 |
| May 14, 2026 | 0 | 2 | 1 |
| May 15, 2026 | 0 | 1 | 3 |
| May 16, 2026 | 0 | 0 | 1 |
| May 17, 2026 | 1 | 1 | 1 |
| May 18, 2026 | 0 | 2 | 2 |
| May 19, 2026 | 0 | 1 | 0 |
| May 20, 2026 | 1 | 0 | 2 |
| May 21, 2026 | 0 | 1 | 1 |
| May 22, 2026 | 0 | 2 | 1 |
| May 23, 2026 | 0 | 0 | 1 |
| May 24, 2026 | 1 | 1 | 0 |
| May 25, 2026 | 0 | 1 | 2 |
| May 26, 2026 | 0 | 0 | 1 |
| May 27, 2026 | 1 | 2 | 1 |
| May 28, 2026 | 0 | 1 | 3 |
| May 29, 2026 | 0 | 1 | 1 |
| May 30, 2026 | 1 | 0 | 0 |
| May 31, 2026 | 0 | 1 | 2 |
| Jun 1, 2026 | 0 | 2 | 1 |
| Jun 2, 2026 | 0 | 1 | 2 |
| Jun 3, 2026 | 2 | 1 | 1 |
| Jun 4, 2026 | 1 | 3 | 1 |
| Jun 5, 2026 | 1 | 2 | 3 |
| Jun 6, 2026 | 2 | 3 | 4 |
| Jun 7, 2026 | 3 | 4 | 3 |
| Jun 8, 2026 | 4 | 3 | 2 |
| Jun 9, 2026 | 3 | 5 | 2 |
Change history
Content, metadata, indexability, and status changes with before/after diffing, ordered newest first.
1–10of318changes
| Change | ||||
|---|---|---|---|---|
| Jun 9, 7:42 AM | Warning | Title | Pricing — CrawlePricing & Plans — Crawle | /pricing |
| Jun 9, 7:42 AM | Critical | Canonical | /blog/technical-seo-checklist/guides/technical-seo-checklist | /blog/technical-seo-checklist |
| Jun 8, 6:15 PM | Critical | Status error | 200404 | /integrations/slack |
| Jun 8, 11:03 AM | Notice | First seen | Discovered | /changelog/2026-05 |
| Jun 7, 2:28 PM | Warning | H1 | Monitor your linksLink monitoring that never sleeps | /features/link-monitoring |
| Jun 6, 9:50 AM | Notice | Meta description | API auth docs.Authenticate to the Crawle API with workspace-scoped keys and rotating tokens. | /docs/api/authentication |
| Jun 5, 4:12 PM | Notice | First seen | Discovered | /customers/acme-case-study |
| Jun 4, 1:37 PM | Warning | Status code | 404301 | /legacy/old-pricing |
| Jun 3, 8:09 AM | Critical | Canonical | /blog/core-web-vitals(empty) | /blog/core-web-vitals |
| Jun 2, 10:44 AM | Notice | First seen | Discovered | /features/seo-change-tracking |
10 affected pages in this window need review.
The problem
When traffic drops, teams often know something changed, but not which template, redirect, metadata field, or URL group changed first.
The outcome
Crawle keeps the latest URL state and historical change history so teams can trace technical SEO changes without storing repeated noise.
- Track titles, descriptions, H1s, canonicals, status codes, redirects, and indexability.
- Differentiate first-seen URL state from later changes.
- Use history for QA, migration review, and client reporting.
- Export change datasets when a deeper investigation is needed.
Workflow
From crawl signal to team action
01
Baseline
The first crawl records the URL's initial state so later changes are compared against a meaningful baseline.
02
Compare
Subsequent crawls detect changed fields and preserve the latest non-empty state for reporting and exports.
03
Investigate
Open affected URL lists, drill into URL history, or export changes for release review.
Where teams use it
Release QA.
Template regression detection.
Indexability change review.
Client audit trails.
Related documentation
Related features
Keep exploring Crawle
Historical data
Historical SEO data for audits and reports
Use 2 years of retained crawl state and change history — plus exports and weekly summaries — to explain what happened across client sites.
ExploreMigration monitoring
SEO migration monitoring from redirect launch to cleanup
Detect migration patterns, verify target domains, monitor old and new URLs, export redirect mappings, and clean up stable old URLs safely.
ExploreAlerts and digests
SEO alerts that surface real problems, not noise
Detect critical regressions quickly while collecting lower-priority changes into digest windows your team can actually read.
ExploreContinuous monitoring
Put Crawle into your next client QA loop.
Continuous technical SEO monitoring with per-client workspaces, real-time alerts, and white-label reports.