Definition
A redirect map is the list of old URLs a change touches, each paired with the one new URL it should send visitors and search engines to. The guide to SEO for site migrations calls it the core artefact of the whole project, because every later check, from staging tests to the weeks of monitoring after launch, reads from it.
It is a document, not a server setting. The redirects themselves live in the server, the platform or the content management system; the map is the plan they are built from and the record they are tested against. Keeping the two apart is what lets a team spot a redirect that exists but should not, or a row that was agreed but never built.
What a usable map holds
The redirect map template gives the columns: the old URL and where it was found, the signals that say how much it matters (organic clicks, linking domains, revenue), the single new URL, the kind of match, the response code, a chain check, the new page's canonical and sitemap status, the test result and the owner of the decision. Three rules from the migrations guide shape most rows:
- One to one, to the equivalent page. Each old address goes to the page that now serves the same purpose. Sending many old pages to the homepage or a category is read as a Soft 404A page that returns a success status code but shows an error, empty or not-found message. for the ones that do not match.
- Permanent and direct. Rows use a permanent redirectA permanent server redirect telling browsers and search engines a URL has moved for good. and resolve any older redirect so the old address reaches its final destination in one hop.
- Removals are decisions. A page with no equivalent gets a deliberate gone response and is taken out of internal links and sitemaps, with the reason recorded.
The list of old URLs is the part teams get wrong. A crawl of the old site, the analytics landing pages, Search Console's pages with impressions and the backlink tools each miss addresses the others find, so the union of all four is what gets mapped. Files and images that earn links or rankings belong on it too.
In practice: from one page to a whole site
The same document scales down. The site architecture guide recommends changing a URL only with a reason and a map, and the SOP for changing a page URL carries that out for a single page: one dated row, then the ads, emails, profiles and links that still carry the old address. The row stays in the map afterwards as the lasting record of the change.
Paid search adds addresses an organic crawl never sees. The guide to Google Ads during a website migration puts the final URLs of ads, sitelinks and product feeds into the project's map rather than a separate sheet, so the web team can see every address the advertising depends on and record the best new destination for a paid click.
A joinery firm finds the pages it forgot it had
Vintrask Joinery, a bespoke kitchen and staircase maker, moved its website to a new platform. The first redirect map listed the 46 pages in the main menu. Four weeks after launch, organic visits were down by about a third. The rebuilt list, combining a crawl of the old site, 12 months of analytics landing pages, Search Console pages with impressions and a backlink export, found 212 old addresses, including 38 gallery pages that 19 other sites linked to and 9 PDF care guides that ranked on their own. Each was mapped one to one, 7 retired pages were given a gone response with a note of why, and every row was retested on the live site. Visits recovered over the following two months.
Related terms
A 301 RedirectA permanent server redirect telling browsers and search engines a URL has moved for good. is the instruction each row is built from; the map decides where each one points. A Soft 404A page that returns a success status code but shows an error, empty or not-found message. is what a blanket redirect to an unrelated page becomes. After a change, internal linksA link from one page to another page on the same website. should be updated to point straight at the new address rather than leaning on the redirect. A Content InventoryA record of every published content page with its owner, review date, audit decision and changes, kept so the next review knows what exists and what happened. is the list of what exists and how it performs, a natural source for the map's old URLs and signals.
Common confusions
- The redirect map is the redirect configuration. The configuration is what the server does; the map is the plan and the record it is checked against. A team with only one of them cannot tell whether they agree.
- Mapping the menu is enough. The pages that matter most are often the ones nobody browses to: old articles, files and filtered addresses that earned links years ago.
- Everything without an equivalent should go to the homepage. Search engines treat that as a missing page in disguise. A deliberate removal, recorded in the map, is better than a redirect that pretends.
- The map is finished at launch. It is the checklist for testing after launch and the record a later URL change starts from, so it stays with the site.
