Website Migration QA — Source vs Target Diff
Pricing
from $10.00 / 1,000 path compareds
Website Migration QA — Source vs Target Diff
Before you switch DNS, compare every page on your old and new site: HTTP status, redirects, title, meta description, canonical, robots, H1, word count and structured data. Get a per-field diff with severity, configurable tolerances, and a summary of what regressed.
Pricing
from $10.00 / 1,000 path compareds
Rating
0.0
(0)
Developer
Aleksandr Jelohhin
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Replatforming, moving domains, or pushing a big redesign? Before you switch DNS, run this Actor to compare every page on the old site and the new site side by side and catch what changed before your users — and Google — do.
For each path it fetches both the source and the target, then diffs the things that matter for SEO and content parity, and flags every difference with a severity.
What it compares
- HTTP status and redirects (does the new page 200, or 404, or add an unexpected redirect?)
- Title and meta description
- Canonical URL and robots / indexability — catches the classic "staging
noindexshipped to production" - H1 and heading structure
- Word count (with a configurable tolerance so tiny changes are ignored)
- Structured data — the schema types present on the page
- Broken links (optional) — did the new page introduce dead links?
- Response time
Input
{"sourceBaseUrl": "https://www.example.com","targetBaseUrl": "https://staging.example.com","paths": ["/", "/pricing", "/about"],"wordCountTolerancePercent": 10}
Or turn on sitemap discovery to compare every URL in the source site's
sitemap.xml automatically.
Output
One dataset row per path:
{"path": "/pricing","score": 82,"worstSeverity": "warning","source": { "statusCode": 200, "title": "Pricing | Example" },"target": { "statusCode": 200, "title": "Example" },"differences": [{ "type": "title_changed", "field": "title", "severity": "warning","sourceValue": "Pricing | Example", "targetValue": "Example" }]}
Plus a run SUMMARY: paths compared, how many differ, how many have errors,
counts by difference type, average score, and the worst-affected paths.
Use it for
- A go/no-go check the day before a migration launch
- Post-launch verification that nothing regressed
- Ongoing parity checks between production and a staging environment
- Vendor QA — proving a migration project delivered what was scoped
Pricing
Pay per path compared (one fetch on each side plus the diff).