SEO Migration Auditor — Redirect, Canonical & Noindex Checks

Validate a website migration before organic traffic is put at risk. The Actor reads an existing public sitemap, maps every path to a new domain, and checks both versions side by side. You can also provide explicit source/target URL pairs.

What it checks

• Final HTTP status and complete redirect chain
• Accidental noindex directives in HTML or X-Robots-Tag headers
• Missing or mismatched canonical URLs
• Missing title and meta description
• H1 count
• Title and normalized-content changes
• Long redirect chains
• A transparent 0–100 diagnostic score with issue codes

Typical uses

• Domain or CMS migrations
• HTTP-to-HTTPS and subdomain moves
• Staging-to-production launch checks
• Redirect-map quality assurance
• Scheduled post-launch monitoring

Input

Use either:

1. sourceSitemapUrl plus targetBaseUrl, or
2. urlPairs containing exact sourceUrl and targetUrl values.

Runs are capped at 200 pairs. Only public HTTP(S) URLs are accepted. Static HTML and response headers are inspected; client-rendered metadata is outside scope.

Output

Each dataset row contains the source URL, intended target, final target URL, status, redirect chain, source and target metadata, issue list, verdict, and score. A run-level summary is stored as SUMMARY in the default key-value store.

Important

The results are diagnostic signals. They do not guarantee indexing, rankings, traffic, or revenue. Always review critical findings before changing production redirects.

Pricing

$1.50 per 1,000 dataset results ($0.0015 each), plus $0.0001 per Actor start. Platform usage is included. Diagnostic error rows also count as results. A 10-pair run costs $0.0151.

Limits and interpretation

Up to 200 pairs, 20 sitemap documents, index depth 2, 8 redirect responses and 2 MB per HTTP response. Plain XML sitemaps only; gzip archives and JavaScript rendering are not supported. The normalized content fingerprint covers the first 100,000 characters. Target base must be a domain origin; path mapping preserves source paths and query strings. The source must remain accessible for content comparison. This is a page parity check: it does not certify that old URLs redirect to the expected new URL. Canonical differences are review signals and can be intentional. The score is a heuristic, not a Google metric.