Use server-side redirects
For permanent moves, Google recommends server-side 301 or 308 redirects when possible. Temporary 302 or 307 responses communicate different intent.
Site migrations · redirect graphs · live destination evidence
Plan and verify URL redirects
Audit an exact URL migration map before launch. OpenWebmaster finds conflicting sources, loops, chains, self-redirects, status-intent problems, and HTTPS downgrades, then verifies small maps against live responses.
- LOCAL MAP
- 500 RULES
- LIVE BATCH
- 20 SOURCES
- CONCURRENCY
- 3
↪
Ready for a migration map.
No example results or scores are shown. Analysis begins only after you provide actual URL mappings.
LIVE DEPLOYMENT CHECK
Verify final destinations and chain length
OpenWebmaster fetches each valid source through the bounded Googlebot inspection path. It compares the observed final URL with the planned final target and retains every failure.
Analyze at least one deployable redirect to enable live verification.
Live evidence boundary: the check records the final URL, terminal HTTP status, and observed URL chain at request time. The current preflight contract does not retain each hop’s status code, so it cannot verify whether the deployed source uses the planned 301, 302, 307, or 308.
Move each old URL to its relevant final replacement
Avoid chains
Point each source directly to its final destination. Chains add latency and make migrations harder to verify and maintain.
Verify the new destination
Confirm that new URLs return successful responses, use updated canonicals and internal links, appear in the new sitemap, and are not blocked by migration-only directives.