A 301 redirect map is one of the most important documents in a website redesign. It connects old URLs with their closest relevant new destinations so visitors, existing links and search engines do not end up at dead pages. A redirect map should be prepared before launch, not assembled in a rush after traffic begins dropping.
Start with a complete inventory of old URLs
Collect URLs from your XML sitemap, WordPress export, crawling tools, Google Search Console and analytics. Add any valuable pages discovered through internal links or known backlinks. Record page type, current status, traffic, links and intended action. Some pages should be kept exactly as they are; changing a URL just to make it look newer creates unnecessary risk.
Decide what happens to every important page
- Keep: existing URL and search intent still fit.
- Improve: update content and design while keeping its URL.
- Move: create a permanent redirect to an equivalent destination.
- Consolidate: combine overlapping pages and redirect useful old versions.
- Remove: return an appropriate status only after checking whether a replacement is justified.
Do not redirect every retired page to the homepage. A visitor looking for a specific service should reach the closest matching service, not a generic destination.
Build a usable redirect spreadsheet
Useful columns include old URL, new URL, action, content owner, priority, expected HTTP status, tested status and notes. Include separate records for changed blog posts, service pages, old landing pages and location pages. Verify trailing-slash and protocol behaviour against the site’s canonical URL format.
Our SEO-friendly website redesign checklist covers the surrounding migration work, including preserving valuable pages and internal links.
How to implement and test 301 redirects
Use server-level rules or a dependable WordPress redirect manager. Test with a crawler or individual HTTP requests. A proper permanent redirect should return 301 and reach the final destination without avoidable chains. Confirm the target returns 200 and is relevant to the source page.
Review navigation, buttons and contextual links so they point directly to final URLs rather than relying on redirects forever. This is part of a sound internal linking strategy.
Check for special cases
Pay attention to product variants, paginated archives, translated URLs, query parameters, canonical rules and downloadable assets. Some redirects may need developer-level rules to avoid redirect loops or unintended matches. Test priority pages individually on mobile and desktop after launch.
Monitor the first weeks after launch
Watch 404 reports, indexation, organic landing pages and search clicks compared with the pre-launch baseline. A redesign can improve structure but still lose valuable traffic when the redirect map misses URLs with existing demand.
Example: a changed service URL
A business replaces /roof-repair-old/ with a comprehensive /roof-repair/ page. The correct map sends the old page directly to the new repair page with a permanent redirect. It does not redirect to /services/ or the homepage, because those destinations are less relevant. The team then updates internal menu and blog links to point directly to /roof-repair/ and checks that the old URL returns 301 and the final destination returns 200. That preserves a useful customer journey and avoids a needless redirect chain.
Frequently asked questions
Can a 301 redirect preserve all rankings?
No redirect can guarantee unchanged rankings. A relevant permanent redirect and equivalent content provide a better migration path, but other page and market signals also matter.
Should every old page redirect somewhere?
No. Redirect when a genuinely relevant replacement exists. For obsolete content with no appropriate destination, use the correct removal response rather than misleading visitors.
DigiFly’s technical SEO and content strategy service supports careful URL planning and post-launch validation. For the wider process, read our guide to redesigning without losing SEO rankings.
