Changing URLs without a redirect plan can create broken links, lost referral traffic, and confusing signals for users and search engines. This practical guide explains how to create a 301 redirect map, choose relevant destinations, test the implementation, and monitor the site after launch.
Overview
A redirect map is a working document that connects each old URL to its intended new URL. It is useful for a redesign, domain move, platform migration, permalink change, content consolidation, or a simple restructuring of categories and folders.
The goal is not to redirect every old address to the homepage. The goal is to send visitors and crawlers to the most relevant available replacement. A well-planned map also helps preserve useful internal links, referral paths, and backlinks pointing to older pages.
Choose the redirect type deliberately
| Situation | Typical response | Planning note |
|---|---|---|
| A page has a permanent replacement | 301 redirect | Map the old URL directly to the closest relevant new URL. |
| A change is genuinely temporary | Temporary redirect, such as 302 | Use only when the original URL is expected to return or remain the preferred address. |
| A page has no replacement and should remain unavailable | 404 or 410 response, depending on the site’s plan | Do not invent an irrelevant destination just to avoid an error response. |
| A page moved more than once | Update the map to point to the final URL | Avoid redirect chains and make the old URL resolve directly to the destination. |
The exact implementation depends on your CMS, hosting environment, or server configuration. The mapping logic comes first: identify the old address, select the best destination, record the reason, and then implement the rule in the appropriate system.
Checklist by scenario
1. Build a complete old-URL inventory
Start with more than the URLs currently visible in the main navigation. Combine several sources so that less obvious pages are not missed:
- Export the current XML sitemap and crawl the live site.
- Review analytics landing pages, especially pages that received visits during the period you are studying.
- Export known URLs from Google Search Console or another search-performance platform.
- Review backlink reports to find old pages that other websites still reference.
- Check CMS exports, product feeds, category archives, image attachment URLs, and regional or mobile variations where relevant.
- Include URL variations caused by trailing slashes, capitalization, parameters, or old folder structures when they can resolve separately.
Keep the original URL exactly as it was requested, including the path and any important query-string behavior. Normalizing everything too early can hide duplicate or conflicting rules.
2. Identify the new URL set
Export the planned URLs from the new site before launch. Group them by page type, such as articles, products, services, categories, authors, or resources. Confirm that each destination will return a successful response, use the preferred protocol and hostname, and contain the intended content.
If the migration also changes topics or page purpose, use search intent as a guide. A page about one specific service should usually move to the closest page about that service, not to a broad services index. For content consolidation, select the surviving page that best covers the original subject and update its internal links accordingly.
3. Create the redirect map
A spreadsheet is often sufficient for small and medium changes. Use one row per old URL and include columns such as:
| Column | What to record |
|---|---|
| Old URL | The complete source address, preferably without accidental whitespace. |
| New URL | The final, canonical destination or a blank value if no replacement exists. |
| Redirect type | Usually 301 for a permanent move; record exceptions clearly. |
| Page type | For example, blog post, product, category, or landing page. |
| Reason | Renamed, consolidated, deleted, migrated, or corrected. |
| Priority | High for pages with valuable traffic, links, or business importance. |
| Test status | Not tested, passed, failed, or needs review. |
For a reusable SEO prioritization framework, rank high-value URLs first. This helps the team test important routes early rather than treating every row as equally urgent.
4. Handle common migration scenarios
- Domain change: Map each old path to the equivalent path on the new domain where the content remains substantially relevant. Confirm that the old and new hostnames do not create a loop.
- Permalink change: Redirect the old path directly to the new path. Preserve the page’s subject and avoid changing the slug and content at the same time unless there is a clear reason.
- Content consolidation: Redirect pages into the strongest surviving resource only when it genuinely addresses the old page’s main need. Update references that still point to retired URLs.
- Deleted content: If no useful replacement exists, leave the URL unavailable and remove it from XML sitemaps and internal navigation. A generic homepage redirect is rarely a meaningful substitute.
- Category or taxonomy change: Check links to archive pages, pagination, feeds, and filtered views. These URL types often require separate rules from ordinary content pages.
What to double-check
Review the map before implementation
- Every important old URL has a decision: direct replacement, intentional removal, or review.
- No destination is misspelled, blocked, unpublished, or dependent on a future launch step.
- Source and destination URLs use the correct protocol, hostname, path, and capitalization.
- Redirects do not point to another redirect when a direct final destination is available.
- Rules are ordered from specific to general where the server or plugin evaluates patterns in sequence.
- Parameters are handled intentionally rather than copied into every destination by accident.
- Important backlinks and high-value landing pages have received manual review.
Use a crawl of the staging environment if possible. If staging cannot reproduce the production configuration, test representative rules in a controlled environment and confirm the final server or CMS settings separately. For URL-level troubleshooting after launch, the Google Search Console URL Inspection guide provides a practical workflow for checking individual pages.
Validate the finished redirects
- Test a sample from every URL pattern, including old posts, categories, products, image paths, and domain variants.
- Confirm that each permanent move reaches the intended final URL without an intermediate redirect.
- Check for redirect loops, repeated hops, unexpected protocol changes, and incorrect hostnames.
- Crawl the new site and look for internal links that still reference retired URLs.
- Review server logs, crawl reports, analytics landing pages, and search-performance reports after launch.
- Record failures in the spreadsheet, assign an owner, and retest after each correction.
Do not judge the migration only by whether the homepage loads. A redirect map is successful when representative URL groups, valuable old pages, internal links, and user journeys all resolve as intended.
Common mistakes
- Redirecting everything to the homepage: This creates a poor experience when the homepage does not answer the visitor’s original need.
- Using relative assumptions: A rule that works for one protocol or hostname may fail when visitors use another valid version of the old address.
- Leaving chains in place: Old URL to temporary URL to new URL adds unnecessary complexity. Point the old address directly to the final destination.
- Forgetting non-content URLs: Feeds, media paths, pagination, search pages, and downloadable files can appear in links and reports even when they are absent from navigation.
- Launching before the map is complete: A partial list makes it difficult to distinguish planned removals from accidental 404s.
- Removing redirects too soon: Keep a record of implemented rules and review their continued need as part of normal site maintenance rather than deleting them without checking traffic and link references.
For content that survives the migration, review its internal links and on-page targeting with the keyword mapping to URLs workflow. A technically correct redirect cannot compensate for a destination that no longer matches the original intent.
When to revisit
Revisit the redirect map before every major redesign, domain change, CMS migration, permalink update, seasonal restructuring, or content consolidation. It should also be reviewed when a new folder structure, product catalog, language version, or publishing workflow changes the site’s URL patterns.
After launch, check the site in stages:
- Immediately: Test priority URLs and one example from every redirect rule.
- During the first monitoring period: Review crawl errors, server responses, landing-page behavior, and unresolved old URLs.
- After content settles: Reconcile the final crawl with the spreadsheet and remove duplicate or obsolete rules only after review.
- Before the next change: Export the current URL inventory again instead of reusing an old map unchanged.
Keep the spreadsheet as a living migration record. Add launch dates, test results, exceptions, and follow-up notes. When the next site change arrives, this history becomes the starting point for a more accurate inventory and a shorter validation cycle. For related maintenance work, pair it with an SEO content refresh checklist and a current crawl report.
Action step: Before changing any URL, export the old site’s URLs, add the final destinations to a redirect mapping template, prioritize pages with traffic or backlinks, test one row from each pattern, and schedule a post-launch crawl. That sequence turns redirect planning from a last-minute technical task into a repeatable part of site health management.