Practical guide
Website migration: reducing SEO risk
Careful planning, complete redirects and post-launch monitoring reduce the risk of a migration; rankings can still fluctuate for a while afterwards.
The work to plan together
A scope shaped around this requirement.
- Inventory URLs and linksScope
- Map redirects one-to-oneReview
- Keep content and metadataCheck
The useful starting point
Treat migration as a controlled change to discovery, content and URLs. Prepare the redirect map, validate the staging site and decide who handles launch checks and post-launch issues.
What to review
- Inventory URLs and links
- Map redirects one-to-one
- Keep content and metadata
- Monitor Search Console after launch
A practical sequence to follow
Identify what is changing
A domain move, platform change and URL restructuring create different dependencies. Record the actual change and which pages, templates and integrations it affects. Agree who owns content, redirects, hosting and release approval.
Protect useful destinations
Map retained content and changed URLs before the move. Test redirects against relevant destinations and avoid chains where possible. Internal links, canonicals and the sitemap should point consistently to the new preferred URLs.
Test the production release
Check important pages and customer actions on the live domain, not only screenshots from staging. Confirm crawler access, working forms, expected redirects and the removal of temporary blocking instructions.
Monitor and respond
Keep a record of the release date and compare crawl, indexing and enquiry evidence with the baseline. Some variation can occur even with careful planning. Assign an owner to investigate errors and prioritise practical fixes; stable rankings are not guaranteed.
What to avoid or interpret carefully
The URL is retained, but a migration cannot promise zero ranking changes. This guide focuses on reducing the risk and identifying problems early.
Practical detail
Make the mapping and launch evidence inspectable
No migration can guarantee unchanged rankings. The useful preparation is a documented route for important URLs and a controlled launch.
| Part of the work | Example output | How to review it |
|---|---|---|
| Old useful page | /old-service/ → /service/ | Map to the relevant replacement rather than the homepage by default. |
| Retained page | Keep /contact/ where the purpose remains | Avoid unnecessary address changes. |
| Launch check | Response, canonical, internal links, sitemap and content | Record actual checks instead of only saying “SEO ready”. |
Keep a baseline of important queries/pages and a post-launch issue log. Review access and tracking first when traffic or enquiries change; do not assume every fluctuation is permanent loss.
Reduce avoidable risk without promising an unchanged result
A migration can be planned carefully, but nobody can guarantee identical rankings after every change. The practical goal is preserving useful information and avoiding preventable routing or indexing problems. Define whether the domain, platform or URLs are changing.
Prepare the inventory
Capture important old URLs and their purpose. Identify genuine replacements for merged or retired content. Useful historical pages should not disappear because they are absent from a new navigation sketch.
Test before release
Review representative templates, mappings and contact paths. Include production configuration responsibilities. Staging access restrictions should not accidentally remain on the live site.
Review after release
Inspect redirects, canonical references and important page access. Monitor relevant search observations with dates and context. Keep a recovery route and unresolved issues visible.
How to interpret this guidance
The title describes the objective of protecting visibility, not a guarantee. A controlled change needs implementation and follow-up ownership as well as a page map.
What should we do if visibility falls after migration?
Investigate affected URLs and queries against the release record. Check routing, indexing and changed content before assuming a penalty. Keep evidence and coordinate corrective work with the release owner.
Can we launch before the redirects are ready?
That leaves known discovery and visitor gaps. Prepare and validate the important mapping as part of launch readiness.
Can Tangensys help with the next step?
Yes. Share your website, goal and the issue you are investigating. We can discuss the relevant service and provide a custom quote within 2 working days.
Related reading and services
Let’s agree the right next step.
Tell us your goals and current setup. We’ll recommend a practical starting point and provide a custom quote.
Custom quote within 2 working days