Validate post-migration redirects are implemented as server-level 301 permanents.
- Validate post-migration redirects are implemented as server-level 301 permanents1 cited source1 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
Permanent 301 redirects transfer link equity and preserve rankings; temporary or incorrect redirects cause traffic and ranking losses.
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.
- Extract old-to-new URL redirect map prior to migration.
- Use server tools (e.g., nginx or Apache config) to implement 301 redirects at the server level.
- Test sample redirects using CURL or online HTTP header checkers to confirm 301 status.
- Audit site for redirect chains and flatten to direct hops.
- Monitor Google Search Console Coverage report for redirect errors post-launch.
Watch for
Using 302 or redirect chains reduces link equity transfer, delaying or preventing ranking recovery.
Definition of done
All old URLs redirect directly via server-level 301 responses to matching HTTPS URLs without chains or loops.
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.