September 28, 2026

What a Redirect Map Should Explain Before a Site Migration

A redirect spreadsheet can contain hundreds of source and destination URLs and still leave important questions unanswered. A destination may be technically reachable but unrelated to the page it replaces. Before a migration, the map should explain the reason for each change as well as the URL pair.

Record the intent behind each mapping

For every source URL, capture the proposed destination and a short reason: the page moved, two pages were consolidated, or the old path is being retired. If no close replacement exists, make that choice explicit instead of sending unrelated pages to a broad category or the home page.

A reason column helps reviewers distinguish a deliberate consolidation from a guessed match. It also makes later checks easier when a page owner asks why a route changed.

Keep the source and destination easy to compare

Preserve the full paths, including useful trailing-slash and case details, and note whether query parameters are expected to remain. Similar-looking URLs can represent different pages, languages, or product variants. A map should make those distinctions visible before rules are written.

For a small migration, a practical row can include the source, destination, reason, content owner, test result, and review status. Larger projects may need extra fields, but the basic purpose remains the same: make each decision inspectable.

Check chains and loops, not just individual rows

A source can redirect to a second old URL before reaching its final destination. A chain may still resolve in a browser while adding unnecessary hops or hiding a stale intermediate rule. Test the full path from the original URL and look for loops, missing destinations, unexpected status codes, and redirects that cross to an irrelevant section.

Testing a representative sample is useful during drafting; before launch, the complete map should be checked automatically where possible. Keep failed rows visible so they cannot be mistaken for completed work.

Revisit internal references after the rules are set

Redirects are a safety net for old addresses, not a replacement for updating links that the site controls. Navigation, related-page links, canonical references, and XML sitemaps should point to the intended final URLs. This reduces avoidable hops and makes the new structure clearer to readers and crawlers.

Make ownership and verification explicit

Before launch, identify who reviewed each group of mappings and how the result was checked. After launch, sample the most important routes and inspect server or crawl data for unexpected responses. A concise map with reasons, owners, and test outcomes is easier to maintain than a long list of unexplained replacements.

The goal is not to redirect every old address at any cost. It is to preserve useful journeys, make intentional content changes, and leave a clear record of what the migration is expected to do.