Crawle
Start monitoring

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.

Start monitoringRead setup docs

Historical change exports

History

2 years of change history retained — package recent changes for reporting and audits

  1. 1
  2. 2
  3. 3
  4. 4

Data type

What to export from crawle-demo.io.

URL changesEvery detected content, metadata, and status change across crawls.
Issue lifecycleWhen issues opened, regressed, and resolved over time.
Weekly reportsReconstructed weekly summaries for any week in range.
Link historyBroken-link first/last-seen history with source and target.

Date range

Last 90 daysLast 12 monthsLast 2 yearsCustom

2026-03-11 → 2026-06-09

Point-in-time snapshot

Reconstruct the dataset as it existed on any past date from change history.

Snapshot date2026-05-26

Between 2024-05-01 (site added) and 2026-06-09 (today).

Full dataFull reconstruction available — all tracked fields reconstruct exactly.

Review & download

Confirm the export, then queue it.

Site
crawle-demo.io
Data type
URL changes
Format
CSV
Columns
14 change fields
Date range
Last 90 days
Snapshot date
2026-05-26

Estimated rows

0

+13.4%vs. prior period

Estimated file size

~16.4 MB

CSV · all change types

Change types in this export

  • Title / meta
  • Status code
  • Canonical
  • Indexability
  • Content body
Queue export

Large export (24,612 rows). Crawle processes it in the background and emails you when ready.

Historical exports package URL change history, issue lifecycle data, weekly summaries, and link history for reporting and audits — 2 years retained, full historical exports rolling out.

The problem

One-off crawls make it hard to prove when an issue appeared, when it was resolved, and how much of the site was affected.

The outcome

Crawle keeps 2 years of historical change context around URL state and changes so audits and client reports have a timeline.

  • 2 years of change history retained for paid workspaces.
  • Historical changes tied to URLs and issue types.
  • Weekly reports per domain.
  • Exports for URLs, issues, broken links, and changes.
  • Dashboard views use current-state summaries while exports can take longer when needed.

Workflow

From crawl signal to team action

01

Collect

Continuous crawls update current state and store baseline plus meaningful field-level changes.

02

Summarize

Weekly reports and dashboards translate crawl data into client-facing updates.

03

Export

When a deeper audit is required, export the relevant dataset instead of waiting on a dashboard query.

Where teams use it

Monthly client reporting.
Post-release review.
Migration audit trail.
Historical exports for analysts (full 2-year exports rolling out).

Related documentation

ExportsAlerts and digestsGetting started with Crawle

Related features

Keep exploring Crawle

View all features

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.

Explore

Migration 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.

Explore

Agency operations

Agency SEO workspaces for clients, tags, and teams

Organize client portfolios with workspaces, client groups, tags, roles, scoped notification settings, and persistent filters.

Explore

Continuous monitoring

Put Crawle into your next client QA loop.

Continuous technical SEO monitoring with per-client workspaces, real-time alerts, and white-label reports.

Start monitoring