SEO Migration Redirect Auditor & Client Report

Verify your old-to-new URL mappings after a website migration. Receive one actionable result per mapping plus a printable HTML report for your client. No browser, proxy, AI API key or database required.

Quick start

Paste the following into the Actor input. Replace the demo pair with your real migration mappings.

{
  "pairs": [
    { "oldUrl": "https://example.com/", "expectedUrl": "https://example.com/" }
  ],
  "maxRedirects": 5,
  "timeoutSecs": 15,
  "delayMillis": 250
}

Supply 1–1000 mappings. URLs must be publicly reachable HTTP(S) URLs using standard ports without embedded credentials. The demo checks a direct page; use an actual old URL to test redirects.

What you receive

• Exact expected-destination checks, preserving paths and query strings; fragments ignored.
• Every HTTP redirect hop; loops, temporary redirects, missing Location headers and HTTPS downgrades.
• Final HTTP status, canonical URL, page title, HTML/header noindex signals and concrete fixes.
• pass, warning or fail verdict for each mapping. Warnings deserve review.
• SUMMARY JSON and REPORT HTML in the run's default key-value store. Download the HTML, open it locally and print to PDF if needed.
• Results in the default dataset, exportable as JSON, CSV or Excel from Apify Console.

Results preserve input order and include pairIndex. Duplicate mappings are checked separately and may be charged separately. Direct old=expected URLs are allowed for destination health checks.

Pricing behavior

The source supports the Apify pay-per-event event pair-audited. Each completed mapping produces one event, including observed HTTP failures (such as 404 or 429) and redirect-rule failures. Network, TLS, DNS and unsafe-target errors produce free diagnostics. Checks stop when no further event fits the run's charge budget.

Pricing is displayed in the Actor’s Pricing tab. At $2 per 1,000 completed mappings ($0.002 each), a 500-mapping run has $1 in event charges. Check the Pricing tab for platform usage treatment before running.

Limitations

This is an HTTP migration check, not a comprehensive SEO crawler. It does not execute JavaScript, inspect robots.txt, verify Google indexing, detect soft 404s or compare page content. Canonicals in HTTP Link headers are not evaluated. Only UTF-8 HTML with identity encoding is parsed; body inspection is capped at 2 MB. Bot-specific noindex directives are conservatively flagged for review. A clean result does not guarantee search-engine indexability or migration readiness.

Trailing slashes, query ordering and case-sensitive paths remain significant. Expected destinations are compared as supplied after standard URL parsing. We do not independently crawl expected URLs if an old URL goes elsewhere. Access denials and rate limiting are reported separately from ordinary HTTP failures; requests are not automatically retried. Increase the delay or rerun later.

Requests run sequentially with a delay between hops and pairs. Every destination's DNS is validated and pinned to a public IP. Private networks, custom ports, unsafe protocols and URL credentials are rejected. Results stay in the caller's Apify storage; no external analytics or database is used. Do not submit URLs containing secret query parameters or personal data. Storage access and retention follow your Apify account settings.

Support

Include a run ID, sanitized input, expected behavior and the relevant issue code in your Apify Actor issue. Never share your API token.