A redirect map is a list of old URLs and the action each one needs. Create it while the old site is still available so you can preserve useful pages and test the move before changing traffic.

Collect URLs from more than the menu

Combine the old sitemap, a site crawl, search landing pages and any campaign or backlink destinations you know about. Keep the original path in the sheet. Group near duplicates for review while retaining each exact incoming URL for testing.

Decide what happens to each URL

Use keep when the old URL remains the preferred address. Redirect an old page to its closest replacement when the new page serves the same reader. For example, send /services/design to /website-development if the pages cover the same offer. Retire a withdrawn page when there is no suitable replacement.

Make the new destination the default

Update navigation, contextual links and the sitemap to point directly to the final URLs. Check that pages meant to appear in search use their intended canonical and can be fetched publicly. Review rules for query strings that support campaigns or filters.

Test a sample before changing traffic

Record the expected final URL and response for each high-value old address. Test a retired page, a changed page, an unchanged page and a tracked campaign link. After launch, compare the live results with the map and watch for loops or chains.

A sample row for your spreadsheet

For an old brochure URL such as /services/design, record the exact old URL, the mapped final URL, the planned status, who approved it, and the actual HTTP result after launch. Put the pages with active enquiries at the top. Also record what happens to uppercase or trailing-slash variants if you know they are in use.

Use the website redesign checklist to plan the wider launch and the technical SEO checklist to check what search engines receive.

Redirect mapping template for a website migration

Use one row per old address, keeping the exact URL that visitors or search engines may request. Record the intended action separately from the test result. A completed mapping sheet is not proof that the redirects work.

Old pathPlanned actionDestination or resultAcceptance check
/services/designPermanent redirect/website-developmentOne hop to a relevant page returning 200
/contactKeep/contact200 response and working enquiry route
/withdrawn-offerRetire when no suitable replacement exists404 or 410No redirect to an unrelated homepage

These are illustrative paths. Add columns for the old page’s purpose, approval owner, expected status, actual final URL and test date. Prioritise pages with search visits, relevant backlinks or active campaign destinations.

How to test a 301 redirect map after launch

  1. Request the exact old URL and record every redirect hop.
  2. Confirm that the final destination serves the same useful purpose and returns its intended response.
  3. Check that internal links point to the final page, not through the redirect.
  4. Verify the new page’s canonical and sitemap entry.
  5. Test important query strings, forms and downloads as well as the HTML page.

Google’s site-move documentation explains URL mapping and post-move monitoring. For a broader rebuild, combine this sheet with the website redesign checklist and agree the website implementation scope.

Frequently asked questions

Should every old URL redirect to the homepage?

No. Map an old page to a relevant replacement when one exists. When it does not, record the retirement and return an appropriate status instead of hiding the missing page behind an unrelated destination.

Does a redirect map guarantee that rankings stay unchanged?

No. A map helps plan and test a URL change. Search engines still need to process the move, and content, internal links and technical issues can also affect the outcome.