Quick answer
SEO redirect mapping is the process of matching old website URLs to the most relevant new URLs before a site structure changes. It is used during website redesigns, CMS migrations, domain moves, ecommerce restructures, content cleanups and URL changes.
The goal is to make sure users and search engines are sent to the right replacement page instead of landing on a broken page, irrelevant page or generic homepage. A good redirect map gives developers a clear implementation file and gives the SEO team a way to check that important pages have been protected before launch.
For South African businesses planning a new website, redirect mapping should happen before the new site goes live. It belongs inside the wider technical SEO South Africa process, alongside crawl checks, canonical tags, internal links, XML sitemaps and post-launch QA.
Google’s site move documentation includes preparing URL mapping as part of a move where URLs change, with old URLs mapped to their new locations before redirects are implemented.
Redirect mapping vs redirects, URL mapping, canonicalisation and XML sitemaps
These terms are often used together, but they do different jobs.
| Term | Difference |
|---|---|
| Redirect mapping | The planning document that decides where each old URL should point after a change. |
| Redirects | The technical rules that send one URL to another. The map tells developers what to implement. |
| URL mapping | A broader migration planning term. SEO redirect mapping adds relevance, priority and QA decisions. |
| Canonicalisation | Clarifies the preferred version of similar or duplicate pages. It does not send users to another URL. |
| XML sitemap | Lists URLs you want search engines to discover. It does not replace redirect rules. |
| Migration planning | The wider launch process. Redirect mapping is one part of that process. |
A simple way to think about it:
Redirect mapping decides the destination. Redirects do the sending. Canonicals clarify preferred versions. XML sitemaps help discovery. Migration planning coordinates the launch.
Why this matters
A redesign can improve how a website looks and works, but URL changes can still create problems if they are handled casually.
An old service page that used to generate leads might be redirected to the homepage. A category page with backlinks might be forgotten and return a 404. A discontinued product might be redirected to an unrelated product. Old blog URLs might pass through two or three redirect hops before reaching the final page.
These are not just technical details. They affect how users move through the site, how search engines crawl the new structure, how performance is measured after launch and how confidently the business can judge whether the migration worked.
Google’s redirect documentation explains that redirects are used when a page has a new location, when a site moves to a new domain, when websites merge, or when removed pages should send users somewhere else.
A redirect map prevents important URL decisions from being rushed during development. It records what should happen to old URLs, why each destination was chosen and which pages need extra QA before and after launch.
Common causes or scenarios
SEO redirect mapping is needed when existing URLs will change, be removed, merged or replaced.
A website redesign may change navigation, folder structure and page names. A page such as /services/seo/ might become /seo/consultant/. Without a redirect map, the old page may be missed or redirected to a weak destination.
A CMS migration can change URLs automatically. Blog posts may lose date folders, ecommerce pages may move into new category paths, and trailing slash behaviour may change. These platform-driven changes still need SEO review.
A domain migration needs even tighter control. Important pages on the old domain should point to the closest equivalent pages on the new domain, not simply to the new homepage.
Ecommerce sites need special care because URL changes often happen at scale. A store with 300 products, 40 categories and years of old product URLs can quickly create hundreds of redirect decisions. Some products may have direct replacements. Others may need to redirect to a parent category. Some may be better left as removed if there is no relevant alternative.
For ecommerce URL changes, redirect mapping should be reviewed alongside category targeting, crawl control, faceted navigation and product availability. For this type of work, see ecommerce SEO consultant.
Content consolidation is another common trigger. If several weak or overlapping articles are merged into one stronger resource, the old URLs can often redirect to the new consolidated page, provided the new page genuinely covers the same intent.
Not every deleted page needs a redirect. If a page is genuinely gone and has no relevant replacement, a 404 or 410 may be more appropriate than sending users to an unrelated page. Google’s site move documentation notes that deleted or merged content that is not moved should correctly return a 404 or 410 response.
Example: service business redesign
Imagine a consulting business redesigns its website and changes this old URL:
/services/seo/
to this new URL:
/seo/consultant/
A homepage redirect would be weak because the user expected information about SEO consulting, not a general introduction to the business. The better destination is the closest matching SEO consultant page, because it preserves the user’s original intent and gives search engines a clearer relationship between the old and new page.
This is where redirect mapping adds value. It stops URL decisions from being made only by folder structure or convenience. Each old URL is judged by relevance, page purpose and business importance.
What a redirect map should include
A useful redirect map is more than a two-column list of old and new URLs. It should help developers implement the redirects and help the SEO reviewer check whether each decision makes sense.
| Old URL | New destination or decision | Reason | Priority |
|---|---|---|---|
/services/seo/ | /seo/consultant/ | Closest matching new service page | High |
/blog/seo-audit-checklist/ | /resources/seo-audit-checklist/ | Resource moved to new folder | Medium |
/shop/running-shoes/ | /footwear/running-shoes/ | Category structure changed | High |
/product/old-model-123/ | Review replacement product or parent category | Product discontinued; no exact replacement confirmed | Medium |
/old-campaign-page/ | No redirect — return 404/410 if appropriate | Campaign ended; no relevant replacement | Low |
The “reason” column is important. It forces the team to explain the decision instead of choosing the nearest live page by default. A discontinued product, for example, should not automatically redirect to a random product just because that page exists.
In the final working file, the redirect map can also include redirect type, implementation owner, notes and QA status. For the published article, the simplified version above is easier to read.
How to assess the issue
Start by building a full URL inventory. Do not rely only on the new sitemap or the pages visible in the main navigation. Many valuable URLs sit deeper in the site, receive backlinks, rank in search, appear in old campaigns or still bring users through organic search.
Use the current XML sitemap, CMS exports, crawl data, Google Search Console, analytics landing page reports, backlink data, paid media URLs, email campaign links and ecommerce exports where available. Google’s site move guidance recommends identifying old URLs from several sources, including sitemaps, server logs, analytics data and linked pages.
Once the URL list is ready, separate it by risk. High-risk URLs usually include service pages, ecommerce categories, top-selling products, pages with backlinks, organic landing pages, paid campaign pages, location pages and resources used by sales or support teams.
A practical rule: any URL that has earned links, receives organic traffic, supports leads or sales, ranks for commercial searches, or appears in Search Console data should be reviewed carefully. Once a project involves more than a few dozen changing URLs, or any ecommerce catalogue/category restructure, redirect mapping should be treated as a formal SEO task rather than a quick developer handover.
Recommended redirect decisions
The strongest redirect is usually from an old URL to the closest relevant new URL. The destination should match the user’s original intent as closely as possible.
An old SEO service page should redirect to the new SEO consultant or SEO strategy page, not the homepage. An old ecommerce category should redirect to the equivalent new category, not a generic shop page. A discontinued product may redirect to a replacement product or parent category if that helps the user, but not to an unrelated product. An old guide should redirect to an updated guide on the same topic, not a blog archive.
Avoid bulk homepage redirects. They may be easier to implement, but they usually create a poor user experience and weak relevance. Google’s site move documentation warns against redirecting many old URLs to an irrelevant destination such as the homepage because it can confuse users and may be treated as a soft 404.
For permanent URL changes, a permanent server-side redirect is usually the right choice. Google’s redirect documentation recommends permanent server-side redirects where possible when a page URL needs to be changed as shown in search results.
After the redirects are implemented, update internal links so the new site points directly to final URLs. Redirects should not become a permanent substitute for clean internal linking. Navigation, breadcrumbs, body links, related resources, XML sitemaps and canonical tags should all be checked after launch.
Google’s canonical URL guidance recommends linking consistently to the URL you consider canonical. Google’s sitemap guidance also explains that sitemaps should include URLs you want to see in search results.
Example: ecommerce category restructure
Imagine a South African ecommerce store moving from an old structure like:
/shop/mens-running-shoes/
to a new structure like:
/footwear/men/running-shoes/
That category should usually receive a direct 301 redirect because the new page is the closest equivalent destination.
A discontinued product is different. If /product/nike-model-2021/ no longer exists, the best decision depends on the replacement options. If there is a newer equivalent product, that may be useful. If not, the parent category may be better. If the product is gone and there is no relevant alternative, forcing a redirect to an unrelated product creates a poor user journey.
That is why redirect mapping needs judgement. The question is not only “where can this URL go?” The better question is “where would this user reasonably expect to land now?”
Implementation notes for teams
Redirect mapping works best when it is treated as a shared launch decision, not a last-minute developer task.
The SEO lead should define the mapping logic, flag high-risk URLs and review unclear destinations before the redirects are built. The developer should not have to guess whether an old page should point to a new service page, a parent category, a replacement product or no redirect at all. Those decisions should already be clear in the redirect map.
Once the rules are implemented, the SEO and development teams should test the same source file. The old URL is tested, the final destination is checked, the status code is confirmed, and redirect chains or canonical conflicts can be picked up before they become post-launch problems.
Before launch, prioritise the URLs that matter most: lead-generating pages, ecommerce categories, products with sales history, backlink URLs and pages with organic search visibility. After launch, crawl the old URL list again and check the final destination, status code, redirect hops, canonical tag, indexability and sitemap consistency.
The cleaner pattern is:
Old URL → final URL
not:
Old URL → old intermediate URL → another intermediate URL → final URL
Google’s site move guidance recommends avoiding chained redirects and redirecting to the final destination where possible.
For larger sites, this QA should form part of a website technical audit or migration SEO review.
When to get expert help
Get expert help when the redirect decisions carry commercial risk, not only when the site is large.
That includes websites that generate leads, ecommerce stores with changing category or product URLs, domain migrations, CMS moves, sites with legacy redirects, and sites with pages that receive organic traffic or backlinks.
As a practical benchmark, redirect mapping deserves SEO review when:
- more than 30–50 URLs are changing
- any high-value service or category pages are moving
- a domain or CMS is changing
- ecommerce categories, products or filters are being restructured
- previous redesigns caused organic traffic or indexing issues
- developers are unsure which new pages should receive old URLs
- Search Console already shows indexing, redirect or crawl issues
The goal is not to make a migration risk-free. The goal is to reduce avoidable mistakes, protect important URL relationships and give the launch team a clear QA process.
Related resources
Redirect mapping usually sits alongside a few other technical SEO checks. These resources are the best next steps:
- Technical SEO South Africa — start here if the redesign or migration also needs crawlability, indexation and site architecture review.
- Website technical audit — use this when redirects, canonicals, sitemaps, internal links and launch QA need to be checked together.
- Ecommerce SEO consultant — use this when category, product or collection URLs are changing on an online store.
- SEO resources South Africa — browse related SEO planning and implementation guides.
Next step
Get a redirect map your developer can implement and your marketing team can QA
Redirect mapping is easiest to fix before launch. After launch, the same issues become harder to diagnose because traffic, indexing, reporting, redirects, canonicals and internal links are all changing at once.
SEO Strategist can review the old URL inventory, proposed new URL structure, redirect rules, high-risk pages, redirect chains, canonical tags, XML sitemaps and post-launch crawl checks. The output is a prioritised redirect review that gives your developer clearer implementation decisions and gives your marketing team a practical QA process before the site is pushed live.
If your website is being redesigned, migrated or restructured, use a technical SEO review to check the redirect map before avoidable launch issues become harder to untangle.