Historical data

Historical SEO data for audits and reports

Use historical crawl state, changes, exports, and weekly summaries to explain what happened across client sites.

Historical change exports

Historical exports package URL changes, issue lifecycle data, weekly summaries, and link history for reporting and audits.

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 historical context around URL state and changes so audits and client reports have a timeline.

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 meaningful change history.

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.