Quick answer
A redirect plan connects an old URL to its most relevant replacement when content moves. It helps visitors and search engines reach the right information instead of encountering broken links or unrelated homepage redirects.
Before you begin
Keep a list of existing important URLs from navigation, search reports, campaigns, and known incoming links. Identify which pages will move, merge, remain, or disappear.
What to do
- Map each changed URL to an appropriate destination that satisfies a similar purpose. Keep useful URLs unchanged where a move is unnecessary.
- Review mappings for loops, chains, and destinations that do not exist. Several retired pages may share a destination only when that destination genuinely fits their content.
- Implement the approved redirect type through the supported server, platform, or application mechanism. Avoid conflicting rules in several layers.
- Update internal navigation, links, sitemaps, and relevant canonical references to the final URLs rather than relying on redirects everywhere.
- Test old addresses after release and confirm they reach the intended public destination. Monitor important errors and traffic patterns during the transition.
How to check the result
Check response behavior and the final page, including HTTPS and common URL variations. A redirect accepted in a dashboard is not enough if it creates a loop or lands on a missing page.
If you need help
For a large migration, ask for a documented mapping and sample verification before launch. Do not remove all redirect rules immediately after the new site appears to work; old links and bookmarks can remain in use.
Related help
- Create a content inventory before redesigning a website
- Plan a website hosting migration before changing DNS
- Redirect an old Shopify URL after moving or removing a page
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
