How to Create a Redirect Map for a Website Redesign

The two-column spreadsheet—old URL, new URL—is only the final output. The real work is determining what each old resource meant, whether that meaning still exists, and how the server should respond. A good map serves a customer opening an old bookmark, a partner following a link, a search crawler revisiting an address, and a support representative using an old document. That is why traffic alone cannot decide the destination.

Build the old URL inventory from more than one source

• Crawl the public site, including linked HTML pages, files, canonicals, pagination, hreflang where used, and current redirects.
• Export URLs from the content management system, commerce catalog, media library, database, or route configuration.
• Export Search Console page data and Page Indexing examples so discoverable URLs outside the navigation are not missed.
• Collect organic, paid, email, referral, and direct landing pages from analytics over a period that includes relevant seasonality.
• Include known backlinks, high-value partner links, local profiles, campaign destinations, QR codes, printed materials, and support documentation.
• Review XML sitemaps, server logs if available, legacy redirect files, subdomains, protocol variants, alternate hostnames, and important downloadable files.
• Ask sales, support, recruiting, and operations for URLs used in templates, proposals, onboarding, job listings, and customer instructions.

Merge those sources into a master list, but retain a column showing where each URL was found. Discovery source helps with prioritization and post-launch updates. A URL that appears in a partner agreement needs a different follow-up from a bot-created parameter variant. Keep the complete absolute URL during analysis so hostname, protocol, path, case, trailing slash, query string, and fragment decisions are visible.

Give the map enough columns to support a decision

The match rationale is the most valuable column. It forces the team to explain equivalence in customer terms. If a row says “closest page available” or “marketing chose Home,” it is not ready. For help protecting the wider content, canonical, structured-data, and internal-link system, use the SEO-safe redesign playbook alongside this map.

Match by intent before matching by words

Similarity in the URL slug is weak evidence. `/commercial/maintenance-plan` and `/residential/maintenance-tips` share words but address different people and decisions. Review the rendered old page, title, headings, search queries, inbound link context, and business use. Then confirm that the proposed destination answers the old visitor's likely question without forcing a second search.

Choose redirect behavior for the actual HTTP request

Google recommends permanent server-side redirects such as 301 or 308 for permanent URL moves. HTTP semantics distinguish permanent and temporary redirects and whether a user agent may change the request method. For normal public GET pages, 301 is widely used. Routes receiving POST or other methods need developer review; a redirect that changes method can break a transaction even if a browser successfully lands somewhere. The map should not blindly assign one code to APIs, form handlers, downloads, and HTML pages.

Turn approved rows into safe implementation rules

• Generate exact one-to-one rules for high-value and exceptional URLs before using broad patterns.
• Apply patterns only when every URL in the pattern follows the same transformation and the destination exists.
• Order rules so a general wildcard cannot capture a more specific exception first.
• Point each old URL directly to the final production URL; do not recreate old hops in a new chain.
• Resolve existing redirect chains by updating the original rule to the final approved destination where possible.
• Preserve required query parameters and discard tracking parameters only under an explicit, tested policy.
• Decide hostname, HTTPS, slash, case, index-file, and extension normalization in one coordinated rule set.
• Keep redirect configuration version-controlled or exported, reviewed, and tied back to map row identifiers.

Test the map as requests, not as spreadsheet cells

A browser landing on the right-looking page is not enough. Record the response chain. A client-side script or meta refresh may hide an avoidable intermediate page. The final target should return a successful response, show the expected content, use the intended canonical URL, and remain linked from the new site where appropriate. A qualified SEO services review should test the server response and the destination's search signals together. Update internal links to point directly to new destinations so visitors and crawlers do not take the redirect path on every navigation.

Monitor the map after the launch window

Google's site-move guidance recommends keeping redirects generally for at least one year and notes that retaining them longer is useful for users. Do not remove an important redirect merely because an internal dashboard stopped showing clicks. Old bookmarks, backlinks, documents, and offline materials may continue sending people for years. Set a review policy that weighs ongoing use, operational cost, security, and platform constraints.

Redirect mapping is one part of the larger website redesign and migration system. Pair it with content inventory, canonical and structured-data review, sitemap updates, internal-link changes, form and integration tests, baseline exports, and post-launch monitoring. A technically perfect redirect cannot compensate for a destination that no longer answers the question.

Final approval checklist for the redirect owner

• Every discovered old URL has an explicit approved disposition; unresolved rows are zero or formally deferred outside launch scope.
• Every redirect target is an absolute production URL with an evidence-based equivalence rationale.
• No redirect target uses a staging host, preview token, obsolete domain, internal admin route, or unapproved third party.
• Homepage and top-level category mappings have been challenged; convenience is not being mistaken for relevance.
• Exact rules and pattern rules have owners, precedence, exception tests, and traceable row references.
• Old URLs point directly to final destinations without loops or avoidable chains.
• Internal links, canonicals, structured data, sitemaps, campaigns, and important controlled profiles use the new URLs directly.
• Launch smoke tests, complete crawl checks, monitoring sources, escalation contacts, and the redirect retention policy are documented.

The map is finished when the business owner can defend the content decisions, the developer can implement them without guessing, and the QA owner can prove the live responses match. That standard turns redirects from a launch-day patch into a durable record of how the old website's useful routes were carried into the new one.