Why limit twenty-five URLs?

Each row triggers network calls. The cap keeps browser sessions responsive; run multiple batches for big lists.

Does it validate response bodies?

It grabs titles from fetch results for quick context but focuses on redirect correctness.

Can it test query strings?

Normalization trims `?` fragments for comparison. Decide policy on parameterized URLs before relying on equality checks.

What if /api/redirects errors?

Treat the row as an error, retry, and verify CORS or server availability. It is not a search-engine live test.

Technical SEO

Live

Post-Migration Auditor

Compare pre/post-migration crawls for regressions and 404s.

X / Twitter LinkedIn Facebook

Migration mapping

One pair per line: old_url,expected_new_url (max 25)

Start here · What does the post-migration audit check?

After launch, legacy URLs should 301 to the right destination once. Search engines and users depend on predictable hops.

Enter old_url,expected_new_url pairs, up to twenty-five rows per run. The tool calls redirect tracing plus HTML fetch in parallel for each old URL.

It normalizes final URLs, compares them to your expected target, counts redirect hops, surfaces long chains, and shows mismatches or fetch errors in a summary grid.

When to use this tool

Weekly cutover QA
Paste the riskiest legacy paths from analytics and verify their destinations after deploy windows.
Vendor acceptance tests
Give stakeholders a green pass count versus mismatches before you close a migration ticket.
Chain shortening backlog
Rows that show multiple hops highlight places to collapse redirects server-side.
Staging versus prod parity
Run the same CSV in staging first if your APIs can reach those hosts.

Examples

Walk through these with the form above — they are practice scenarios, not live data.

Happy path match

Try this

Old /old-page should land on /new-page with one 301.

What to look for

Matched badge, final URL equals expectation, hop badge stays minimal.

Wrong destination

Try this

Expected /products/blue-widget but server still points to homepage.

What to look for

Mismatch note compares final URL with expectation so you can fix server rules.

Short tutorial

Follow in order the first time you use the tool; later you can skip to the step you need.

Step 1 — Build redirect pairs
Source pairs from your redirect map, crawl diff, or analytics top landings.
Step 2 — Paste CSV lines
Comma-separated, no header row. Keep ≤25 lines to respect rate limits.
Step 3 — Run Audit
Wait for sequential processing. Progress counts show how many pairs finished.
Step 4 — Fix failures first
Errors mean transport problems. Mismatches mean mapping problems. Long chains mean infrastructure cleanup.
Step 5 — Re-run after deploy
Iterate until matched count equals your critical list. Expand coverage with new batches.

More detail

New here? Skim Start here first, then run one Examples scenario in the form above.

Post-Migration Auditor does one job: compare pre/post-migration crawls for regressions and 404s. It lives under Technical SEO on SEOToolkits, where the beginner idea is simple: Technical SEO keeps pages crawlable, indexable, fast enough, and understandable to search engines.

FAQ

Why limit twenty-five URLs?: Each row triggers network calls. The cap keeps browser sessions responsive; run multiple batches for big lists.
Does it validate response bodies?: It grabs titles from fetch results for quick context but focuses on redirect correctness.
Can it test query strings?: Normalization trims ? fragments for comparison. Decide policy on parameterized URLs before relying on equality checks.
What if /api/redirects errors?: Treat the row as an error, retry, and verify CORS or server availability. It is not a search-engine live test.