Freeze the input and identify the environment
For each row, keep the old URL, approved action, expected final destination and owner. Return unresolved destinations to the content owner. The developer should not choose the homepage simply to make an incomplete row pass.
Record the code version, redirect configuration, test host and date. A static preview may serve the right HTML without applying the hosting platform’s redirect rules. Use an isolated environment that can exercise those rules, and retain a known copy of the previous configuration. Keep credentials out of the test record.
Capture the first response and every subsequent hop
Make the first request without automatically following redirects. Record the status and Location header, then trace each hop to the final URL. An approved permanent move will usually call for an appropriate server-side 301 or 308. The exact implementation depends on the hosting environment; a rule in a repository is not evidence of the response visitors receive.
In a fictional test, /old-service/ should lead straight to /services/maintenance/. A journey through an intermediate route and a temporary redirect is a deviation from that intended direct move, even if the final page returns 200. Test trailing slashes, relevant host variants and query parameters against the agreed URL policy. Understand a parameter’s purpose before discarding it.
Read the destination and check its page signals
Open the final page and confirm the service, language and working enquiry path. Check its canonical, indexing decision and genuine language equivalents. A private staging site may deliberately use noindex. Document the intended production difference rather than removing staging protection to make a check pass.
Internal links and the sitemap should use the agreed final addresses. Retired content without a replacement should return the chosen error status; an attractive error page returning 200 is a different outcome. Include an unchanged URL to catch broad rules that accidentally redirect working pages.
| Test | Expected outcome | Evidence |
|---|---|---|
| Permanent move | Direct to approved destination | Initial status, Location and final status |
| Unchanged page | Same working address | No accidental rule match |
| Retired without replacement | Agreed 404 or 410 | Real status rather than error copy alone |
| Language version | Correct language and equivalent | Canonical and language relationships |
Resolve exceptions without silently changing the expectation
Keep the observed result, exception, owner and retest for each row. Correct the rule or obtain a new content decision when the response is wrong. Do not rewrite the expected destination just to match a broken implementation. If a shared rule changes, repeat the checks for all affected path patterns.
Passing the protocol does not authorise launch or guarantee search visibility. After a separately approved move, repeat the same checks against the actual hosting environment and review logs and available Search Console data. ImbaHub can help scope a migration check: bring the approved map, hosting details and a reproducible failing journey.