Test priority redirects manually before DNS cutover.
- Test priority redirects manually before DNS cutover2 cited sources1 category
Save for later 0
Use × to move an item here. You can restore it when you’re ready.
Your checks and saved items stay in this browser. Nothing is submitted.
Why this matters
Manual testing ensures critical URLs redirect correctly, avoiding unexpected issues.
Hypothetical standard operating procedure
Adapt this example to your site, access, tools, and change process. It is our suggested procedure, informed by the sources below.
- Select representative old URLs including homepage, top blog posts, and product pages.
- Use tools like curl or online redirect checkers to test redirect status and location.
- Confirm HTTP status 301 and no intermediate redirects occur.
- Document test results and fix issues before migration.
- Repeat tests post-migration for verification.
Watch for
Untested redirects may cause 404s or redirect loops harming SEO and UX.
Definition of done
All key redirects return HTTP 301 and lead directly to correct canonical new URLs.
Sources & attribution
Original checklist wording and example SOP by Best SEO Checklist, using source-grounded AI assistance. Editorial contact: Ted Kubaitis, @tedkubaitis on Teams. Check current source guidance before implementation.