Add to Preferred Sources
An seo redirect map checklist is the step-by-step process you follow to document every URL that needs to move before a website goes live on a new structure — and the single planning document most South African site redesigns skip entirely. Paired with a solid South African SEO strategy, a redirect map is how you transfer ranking equity from old pages to new ones rather than losing it on launch day.
Without a redirect map, pages that earned your search positions get orphaned: Googlebot follows an old URL and finds nothing recognisable on the other end. South African businesses building a website migration redirect map — whether they're moving from WooCommerce to Shopify, restructuring a WordPress catalogue, or launching an entirely new design — face this problem whenever URLs change without a documented redirect plan in place. For sites undergoing a full platform or domain move, the SEO migration guide for South Africa covers the broader technical scope; this checklist covers the redirect map specifically.
The steps below are ordered by dependency — each one sets up the next — and the spreadsheet template in Step 3 doubles as your handover document for the development team.
Quick Answer
An seo redirect map checklist has six steps: (1) crawl all existing URLs, (2) pull traffic and backlink data, (3) match old URLs to new equivalents in a spreadsheet, (4) flag and collapse any redirect chains, (5) test on staging, (6) monitor for 404 errors post-launch. Use 301 redirects for all permanent moves, never redirect to the homepage, and keep redirects active for at least a year. The redirect map is built before development finalises the new URL structure — not on launch day.
Jump to a Section
Facing a site redesign or CMS switch?
Send us your current URL structure and we'll identify the pages that carry the most ranking equity before you plan a single redirect.
Get a Pre-Migration ReviewWhat Is a Redirect Map?
A redirect map is a spreadsheet that pairs every old URL on your site with the new URL it should point to — the single source of truth your developers implement when restructuring a site. It documents not just where each URL goes, but how important it is and what kind of redirect to use.
The document matters because search engines carry ranking signals at the URL level. When Google has indexed a page at /old-category/product-name/ and that URL disappears without a redirect, those signals — backlinks, crawl history, authority — dissipate. A 301 (permanent) redirect instructs Google to transfer those signals to the new destination.
The Google SEO Starter Guide recommends redirects as the method for managing moved URLs: "try setting up a redirect from non-preferred URLs to a URL that best represents that information." Google's documentation also classifies 301 redirects as one of the strongest canonicalisation signals available.
Redirecting to the homepage is not a safe fallback — it's a soft 404. Google explicitly treats a 301 from a product or category page to the homepage as a soft 404, meaning no equity transfers. Redirect to a genuinely relevant page or, if no close equivalent exists, let the URL return a clean 404 or 410. The 301 redirect SEO checklist covers the technical implementation detail once your map is finalised.
A redirect map is distinct from a redirect implementation. The map is the planning document, owned by whoever oversees organic search; the implementation is what developers write into the server config, .htaccess file, Shopify's built-in URL redirects section, or a WordPress redirect plugin. Building the map without a clear handover process is how half-implemented migrations happen.
seo redirect map checklist: The Six Steps
A complete seo redirect map checklist follows six steps in dependency order — skipping Step 1 makes Step 3 unreliable, and skipping Step 5 makes launch day unpredictable.
Step 1: Crawl Your Existing Site
A site crawl gives you the master list of URLs your redirect map needs to cover — every row in the export is a URL that needs a decision. Tools like Screaming Frog, Sitebulb, or Ahrefs Site Audit generate a complete URL inventory that goes beyond what your sitemap contains.
Start from a crawl, not your sitemap. Sitemaps include only the URLs you intended to index; crawls surface existing redirects, orphan pages, parameterised URLs, and old content that's been quietly accumulating equity. Redirect only what's in the sitemap and you'll leave traffic and link value behind.
Step 2: Pull Traffic and Backlink Data
Traffic and backlink data are how you prioritise — a URL driving any meaningful organic traffic or attracting links from external sites is a Tier 1 priority regardless of how it looks in the new design. Export landing page sessions from GA4, then overlay backlink counts from Ahrefs, Semrush, or Moz Link Explorer. Add columns for both alongside the URL list from Step 1 — these two signals determine your priority tier in Step 3.
Step 3: Match Old URLs to New Equivalents
Map each old URL to its best-fit new destination — ideally a direct one-to-one equivalent with matching user intent. For a WooCommerce-to-Shopify migration, /product-category/running-shoes/ maps to the equivalent Shopify collection; /product/nike-pegasus/ maps to the new product handle. Shopify enforces /products/ and /collections/ URL prefixes regardless of your previous structure, so almost every WooCommerce migration requires a 301 redirect map for product and category pages.
Where no direct equivalent exists, map to the closest topically relevant page. If you are consolidating pages, map multiple old URLs to a single new destination (a many-to-one pattern) and document the rationale in a notes column. This redirect map template approach — complete with priority, type, and notes columns — is covered in the spreadsheet section below.
Step 4: Check for and Collapse Redirect Chains
A redirect chain exists when URL A redirects to URL B, which redirects to URL C — each extra hop wastes crawl budget and dilutes the equity transfer. Google's Search Advocate John Mueller stated that redirect chains should stay under five hops, and that Google will follow up to five hops in a single crawl session before resuming in the next. For any URL carrying real traffic or link value, one hop is the target.
If your existing site already has historic redirects from earlier URL changes, update those source URLs to point directly to the final destination before launch — otherwise you inherit and extend existing chains with every migration.
Step 5: Test on Staging Before Launch
Before DNS changes go live, verify the redirect map on a staging environment. Use Screaming Frog's list crawl mode to load all source URLs from the map and confirm each returns a 301 status code, resolves to the correct destination, and produces no redirect loop. Confirm that final destinations return 200, not another redirect — a destination that itself redirects creates an unintended chain.
This is the step most South African development teams skip, and the one that produces post-launch firefighting. Any Tier 1 URL (defined in the priority section below) returning a 302, 404, or loop is a build blocker before go-live.
Step 6: Monitor Post-Launch and Keep Redirects Active
After launch, check Google Search Console's Pages report for new 404 errors weekly during the first few weeks after launch. Any 404 with prior organic traffic or backlinks needs a redirect added as quickly as possible — delays allow ranking signals to dissipate. On retention: John Mueller stated in the "Ask Googlebot" series that 301 redirects should remain active for at least one year, giving Google enough crawl cycles to record the move as permanent. Where server overhead allows, keeping them indefinitely is the safer default. If you are restructuring a site and would like support with the redirect plan, our technical SEO help for SA sites starts with a free audit and continues on a flat monthly retainer.
What Your Migration Spreadsheet Must Include
A useful redirect mapping checklist spreadsheet carries more than two URL columns — it is a QA document and a priority queue that makes launch blockers visible before go-live.
| Column | What to Record | Why It Matters |
|---|---|---|
| Source URL | Old URL exactly as it appears in crawl data | What developers implement in server or CMS |
| Destination URL | New URL, verified live on staging | Must return 200, not another redirect |
| Redirect Type | 301 (permanent move) or 410 (intentionally removed) | Use 301 for moved content; 410 signals deliberate removal to crawlers |
| Priority Tier | 1 / 2 / 3 (see section below) | Sets implementation order when time is tight at launch |
| Monthly Sessions | GA4 organic landing page sessions over recent period | Quantifies cost of a missed redirect |
| Referring Domains | Unique domains linking to source URL | High-link pages are the most expensive to leave unmapped |
| Chain Depth | How many existing hops before final destination | Flag any chains for collapse before launch |
| QA Status | Tested / Untested / Broken | Pre-launch sign-off column |
| Notes | Mapping rationale or content consolidation decisions | Audit trail for post-launch investigations |
Keep this spreadsheet as a living document with a named owner — it is as much a part of your seo redirect map checklist as the steps that built it. A one-time export that no one updates after launch is how unmapped 404s accumulate unnoticed for months.
On redirect type: 301 vs 308. Both signal a permanent move and pass link equity equivalently in Google's systems. The difference is technical: a 308 preserves the original HTTP method, which matters if POST requests need to stay as POST at the new destination. For standard content migrations — product pages, blog posts, category pages — use 301. Reserve 308 only when you have a specific technical reason to preserve HTTP method.
Priority Tiers: Which Pages Get Redirected First
Every URL in your crawl export needs a decision, but not every URL deserves equal effort — prioritising by traffic and link value ensures the highest-cost gaps are closed before launch, even if time runs short.
| Tier | Criteria | Action | Timing |
|---|---|---|---|
| Tier 1 — Critical | Recent organic traffic, external backlinks from other domains, or direct conversion value | Map 1:1 to exact content equivalent. Verify correct destination. | Must be live at launch |
| Tier 2 — Important | Indexed pages with some crawl history but no external links and minimal traffic | Map to best available equivalent. Document mapping decision. | Aim for launch; acceptable shortly after if time runs short |
| Tier 3 — Low Value | Paginated pages, filtered URLs, old campaign landing pages with no history | Let return 404 or implement a pattern-based redirect rule. | Post-launch is acceptable |
As a working rule of thumb, Tier 1 will represent a minority of your total URL inventory on most SA business sites — but it accounts for the vast majority of the organic search value at risk. Work through it exhaustively before touching Tier 3.
Pattern-based rules save time on Tier 3. If your old URLs follow a predictable structure — for example, all blog posts at /news/year/month/title/ now live at /blog/title/ — write one server-side rule rather than mapping each individually. Manually verify a sample of URLs before trusting the pattern across the full set.
Not sure which pages carry the most link equity?
Share your domain and we'll pull a backlink and traffic profile to show you which URLs belong in Tier 1 before your redirect map is built.
Get a Link Equity ReviewRedirect Mapping Mistakes That Cost South African Sites Their Rankings
The most damaging redirect mapping mistakes share one trait: they look like they work, but they quietly prevent equity from transferring. Running a thorough seo redirect map checklist eliminates each of these before they reach production.
Redirecting everything to the homepage. Sending discontinued product pages or removed category URLs to / appears to solve 404 errors, but Google treats these as soft 404s — the destination doesn't match the original content, so no signals transfer. Either find a relevant equivalent or let the URL return a clean 404.
Using 302 redirects for permanent moves. A 302 tells Google the move is temporary, so Google may continue indexing the old URL and will not fully transfer link equity to the new destination. Use 301 for every permanent content move — CMS migrations, URL restructures, and domain consolidations included.
Starting redirect planning after the new URL structure is already built. If developers have deployed the new site and someone is reverse-engineering what moved where, the risk of missed pages multiplies significantly. A redirect map is an input to the URL structure decision, not a clean-up task after go-live.
Allowing redirect chains to propagate from previous migrations. Migrating a site that already has historic redirects without checking chain depth creates three- or four-hop paths. Each hop is a crawl cost, and chains longer than five hops risk Googlebot abandoning the path before reaching the destination. Collapse all existing chains to a single hop before launch.
Testing Redirects and Monitoring Post-Launch
Testing your redirect map before launch is the only reliable way to catch mapping errors before they affect rankings — a missed redirect found post-launch is a gap that may take months to recover from, not days.
On staging, use Screaming Frog's list crawl to load all source URLs from your map and verify each returns the correct HTTP status code (301) and resolves to the correct destination. Run a second pass with destination URLs to confirm they all return 200 — not another redirect. Any URL returning a loop, a 302, or landing on an unintended page is a fix before Tier 1 is signed off.
After launch, run a weekly task for the first few weeks post-launch:
- Check the Pages report in Google Search Console filtered by "Not found (404)"
- Cross-reference each new 404 against your redirect map — any with prior organic traffic or backlinks needs a redirect added promptly
- Monitor organic landing page traffic in GA4 to identify high-value pages no longer receiving clicks
- Check for redirect chain alerts in your crawl tool as new pages get added
Keep 301 redirects active for at least one year — preferably indefinitely. Google's John Mueller stated in the "Ask Googlebot" series that redirects need to stay live for at least twelve months so Google can crawl and record the permanent move multiple times across crawl cycles. External sites linking to old URLs may update those links slowly; a redirect that stays live indefinitely ensures those links always reach valid content. For a comprehensive view of crawl efficiency across your full site, pair redirect monitoring with a regular crawl audit.
Industry practitioners report that organic traffic typically fluctuates for two to six weeks after a migration before stabilising. When stabilisation takes longer — or traffic plateaus at a lower level — missed Tier 1 redirects or topic-mismatched destinations are the most common cause.
Why South African Businesses Work with Growth Pulse Media on Website Migrations
Website migrations and URL restructures are among the highest-risk moments in an organic search programme. Growth Pulse Media approaches them from an operator background — the same analytical instinct that tracks inventory movement and conversion paths at ecommerce scale applies when auditing a URL inventory and setting priority tiers.
We build redirect maps as pre-launch planning documents rather than post-launch recovery tools. The development team receives a complete, tested spreadsheet with implementation instructions before DNS changes go live. Every map is tied to GA4 traffic data and backlink analysis so the priority tiers reflect real commercial risk rather than a guess based on page layout.
All work is executed in-house, with a limited client load so each migration gets senior attention rather than being delegated to a junior account manager. The result is a handover document the development team can implement without re-interpretation. If you're planning a site redesign, a CMS switch, or a domain consolidation, the time to involve us is before the new URL structure is finalised — not after launch. Read more about our approach to SEO for South African businesses.
Who This Is NOT For
Sites that haven't established organic search traffic yet. If your site is newly launched with no meaningful organic traffic and no external backlinks, a full redirect map is disproportionate effort. Focus on building an indexed presence before managing URL equity migration.
Teams planning to handle redirects on launch day. A redirect map built under launch-day pressure is incomplete. The work requires careful analysis of crawl data, traffic history, and backlink profiles — tasks that cannot be done accurately in the same window as a DNS change.
Operators redirecting a brand-new domain with no index history. If the domain has never had indexed pages, there are no search signals to preserve. Redirects exist to carry signals that have already been accumulated — if the domain is new, build the URL structure correctly from the start rather than planning a redirect migration.
Businesses treating redirects as a permanent architectural substitute. A redirect map bridges old and new URL structures; it is not a replacement for building URLs correctly. Sites that accumulate redirect layers over successive redesigns create maintenance debt and crawl inefficiency that compounds with every subsequent migration.
Handing the migration to developers who haven't done this before?
Walk us through your migration plan and we'll identify the gaps before launch day — no obligation, response within 24 hours.
Review My Migration PlanFrequently Asked Questions
What is the difference between a redirect map and a redirect implementation?
A redirect map is a planning document — a spreadsheet that lists source URLs, destination URLs, redirect types, and priority tiers. A redirect implementation is the technical execution of those instructions in a server config, an .htaccess file, or a CMS's built-in redirect manager. The map is produced by whoever oversees organic search; the implementation is carried out by developers. Separating the two clearly is how you prevent redirects being implemented without a proper audit behind them.
How long should 301 redirects stay active after a site migration?
Google's Search Advocate John Mueller stated in the "Ask Googlebot" video series that 301 redirects should remain active for at least one year to give Google enough crawl cycles to register the permanent move. Google Search Console's Change of Address guidance recommends a minimum of 180 days. In practice, keeping redirects active indefinitely is the safest approach — external sites that link to old URLs update those links slowly, and a redirect that persists ensures those links always reach valid content.
Do I need a redirect map if I'm only changing my CMS, not my URL structure?
It depends on whether the new CMS preserves your existing URL structure exactly. Shopify enforces /products/ and /collections/ prefixes regardless of previous structure, so a WooCommerce site moving to Shopify will almost always require URL remapping. The only way to confirm a CMS migration doesn't require redirects is to compare the crawl of the old site against a staging crawl of the new one, URL by URL.
What happens if I redirect an old URL to a different topic than the original page?
Google treats topic-mismatched redirects as soft 404s — the same outcome as redirecting to the homepage. No meaningful equity transfers, and the original URL's signals are effectively discarded. Always match the redirect destination to the closest available content covering the same topic. If no equivalent exists and the original content is gone, a clean 404 or 410 is more honest and produces the same equity outcome as a soft 404, with less crawl waste.
Should I use 301 or 308 redirects for a site migration?
For standard content migrations — product pages, blog posts, category pages — use 301. Both 301 and 308 signal a permanent move and pass link equity equivalently in Google's systems. The technical difference is that 308 preserves the original HTTP method, which is relevant only when POST requests need to stay as POST at the new destination. For nearly all SA site migration scenarios, 301 is the correct choice.
Planning a Site Migration or URL Restructure?
Growth Pulse Media builds redirect maps as pre-launch planning documents — tied to your GA4 traffic data and backlink profile, so the priority tiers reflect real commercial risk. All work is executed in-house, with senior-level attention on every migration project. We work with South African businesses across Johannesburg, Cape Town, and Durban on Shopify, WooCommerce, and WordPress migrations.
No obligation — we'll get back to you within 24 hours.
Get a Free Pre-Migration Review