Check Redirects After a Migration: Compare Each Old URL

Test old URLs after a site migration. Compare each result with its expected destination, redirect type, and planned removal status.

Like it ? share it

Keep the old URL list beside the approved migration map. Compare each response with its intended destination and action.

A final 200 does not establish a correct migration. A planned 410 does not automatically establish a failed migration.

The Bulk URL Checker supplies an initial response check. Its CSV does not supply your migration map, every redirect hop, or a content decision.

Define the expected result before the run

A migration map connects an old address to its intended replacement. A removal record states that a page has no replacement.

These are different plans. They need different acceptance rules.

Review field Example Purpose
Row ID M-001 Preserve the source record
Old URL https://old.example.com/item-a Identify the input
Action Move or remove Define the intended outcome
Expected final URL https://new.example.com/item-a Define the destination
Expected status 200 or a planned 404/410 Separate moves from removals
Expected redirect Direct 301 or 308 for this move Define the migration rule
Expected content Item A and its main details Identify the intended page
Observed result Status, hops, final URL, content Record the evidence

A row without an approved destination remains unresolved. A successful response cannot supply the missing decision.

Google recommends permanent server redirects where possible. Its migration guide also recommends direct destinations and warns against irrelevant homepage redirects.

Several old pages can legitimately move to one consolidated replacement. That replacement must serve the combined content purpose. Equal destination addresses alone do not establish an error.

Procedure: run the response check

  1. Keep a copy of the migration map.
  2. Copy the old URL column without its header.
  3. Open the Bulk URL Checker.
  4. Paste one complete address per line.
  5. Select LOAD LIST.
  6. Compare the loaded count with your input list.
  7. Select START CHECKING.
  8. Export the completed results as CSV.
  9. Match each result to its original URL.

The Excel and CSV guide explains the import and export steps.

Keep row IDs in your source map. Compare actual URL values when joining records. A row count alone cannot prove that every old address received a result.

The checker follows redirects and reports the final response. Thus, a moved URL and a direct page can both appear as 200.

Procedure: verify each move against the map

  1. Open the old URL in the Redirect Detector.
  2. Record the redirect status and each destination.
  3. Compare the final URL with the approved map.
  4. Record any additional hops.
  5. Open the final page in your browser.
  6. Compare its main content with the expected page.
  7. Record the result and test time beside the source row.

These steps add a separate review. They do not describe an automatic mapping feature in the bulk checker.

For this procedure, the selected move contract requires one permanent redirect to the expected page. It sends additional hops for review.

That is a deliberately narrow project rule. It does not mean every 302 is incorrect for every website or that Google cannot follow a chain.

Six local migration cases

On November 16, 2026, we tested six synthetic paths with Python 3.12.6 on Windows. All requests used GET against a local HTTP server.

Old path Actual response path Plan Review result
/old-a 301 → /new-a, 200 Direct permanent move Pass
/old-wrong 301 → /, 200 Move to /new-a Review: wrong destination
/old-chain 301 → /middle, 301 → /new-a, 200 Direct permanent move Review: extra hop
/removed 410 Planned permanent removal Pass
/missing 404 Move to /new-a Review: missing move
/temporary 302 → /new-a, 200 Permanent move Review: wrong redirect type

Four cases ended with 200. Only one met the complete move contract. The planned removal passed with 410.

All six expected-decision assertions passed. Two runs produced identical records. This experiment did not use Enfect, a browser, or Google's systems.

The model compares addresses, statuses, and hop counts. It does not judge content relevance. A separate main-content review remains necessary even for the passing move.

Decide removals from the plan

RFC 9110 distinguishes 404 from 410. A 404 does not specify permanence. A 410 indicates that the unavailability is likely permanent.

A removal decision therefore needs evidence from the site owner. A checker cannot infer that decision from an old spreadsheet.

For an accidentally missing replacement, repair the migration route. For an approved removal, fix stale internal references and sitemap entries.

An owner discussion describes missing URLs that lead to a homepage. A separate migration discussion asks how to handle pages during a domain change.

These reports describe review needs. They do not establish a recovery time or a general search penalty.

Close the audit with the next action

For access refusals, use the 403 investigation. An inaccessible response needs investigation before a removal decision.

For current sitemap entries, use the sitemap audit. The sitemap should identify intended canonical destinations.

Printed QR codes can still contain old URLs. The QR decoder reads those addresses so they can enter the same migration map.

Google's guide recommends retaining migration redirects for at least a year. It also recommends updating internal links. A passing test today is not permission to remove old redirects tomorrow.

A completed record includes the expected action, observed route, content review, owner, and next decision. Search Console indexing remains a separate check.

For several codes on one flyer, the multiple-code procedure keeps each decoded address attached to its source.