A 301 redirect SEO checklist is a structured set of steps that ensures every permanent URL change on your website transfers its search ranking signals to the new destination — without losing rankings, breaking crawl paths, or sending Google the wrong canonicalisation signal. As part of any serious SEO strategy in South Africa, getting redirects right is the difference between a migration that builds on your existing rankings and one that quietly drains them over the following weeks.
Whether you are switching from WooCommerce to Shopify, changing your domain after a rebrand, or restructuring your URL hierarchy after poor initial planning, the redirect decisions you make before, during, and after the change determine how much of your built-up search equity survives.
A missed redirect, a redirect chain, or an irrelevant destination page can mean Google downgrades your link signals entirely — treating your carefully built authority as a soft 404. This guide gives you the complete checklist, phase by phase.
Quick Answer
A 301 redirect SEO checklist covers three phases: pre-migration planning (URL auditing, redirect mapping, staging tests), implementation (deploying server-side 301s, updating sitemaps, DNS preparation), and post-launch verification (crawl checks, Search Console monitoring, internal link cleanup). Single-hop 301 redirects from an old URL to a topically relevant new URL preserve the strongest link equity signal. Google requires server-side implementation — JavaScript and meta-refresh redirects are a last resort and may be ignored.
In This Guide
Not sure if your site's redirect setup is hurting your rankings?
Send us your URL and we will run a redirect audit — showing you exactly where chains, loops, and missing maps are leaking search equity right now.
Request a Redirect AuditWhat Is a 301 Redirect and Why Does It Matter for Search Rankings?
A 301 redirect is an HTTP status code that tells browsers and search engines a URL has permanently moved to a new location. When Google's crawler requests the old URL, your server responds with the 301 status and the new destination — and Google's indexing pipeline treats the redirect target as the canonical URL, transferring the original page's accumulated link signals to the new address.
The critical word is permanent. A 301 tells Google the old URL is retired and the destination is where authority should consolidate. This is why a correct 301 preserves your rankings through a domain move or URL change, while a 302 (temporary redirect) leaves the original URL indexed and passes no canonicalisation signal at all.
How Google processes 301 redirects: Google follows the redirect, indexes the destination URL as canonical, and consolidates link equity there. The original URL is eventually dropped from the index. Full re-indexing of a well-redirected migration typically takes two to eight weeks for smaller sites, and up to three months for large-scale URL restructures.
Google is explicit about its preference: server-side permanent redirects are the best way to ensure Google Search and users reach the correct page. JavaScript-based redirects are a last resort — see the note in the 301 vs 302 section below for why.
When Should You Use a 301 Redirect?
Use a 301 redirect whenever a URL change is permanent and you want search authority to move with it. The most common triggers for South African businesses include:
| Trigger | Why a 301 Applies |
|---|---|
| Domain migration or rebrand | All old domain URLs must redirect permanently to their new-domain equivalents |
| Platform move (WooCommerce to Shopify, etc.) | New platform generates different URL patterns — old URLs need to map to their closest equivalent |
| HTTP to HTTPS consolidation | Redirects www/HTTP variants to the canonical HTTPS version to consolidate link signals |
| URL slug correction | Fixing a messy URL structure (e.g. /category/subcategory/product → /product) requires permanent redirects |
| ccTLD migration (.co.za ↔ .com) | South African businesses moving between a .co.za and a .com — or adding a .co.za to an existing .com — need 301 redirects to consolidate link equity under the preferred domain |
| Duplicate content consolidation | When multiple URLs serve the same content, redirect duplicates to the preferred canonical — related to fixing keyword cannibalisation |
| Page deletion with a suitable replacement | If a page is removed but a closely related page exists, redirect the deleted URL there rather than returning a 404 |
What you should not use a 301 for: temporary redirects (A/B testing, seasonal promotions — use 302 instead), or redirecting a deleted page that has no meaningful equivalent to your homepage. The latter is one of the most common ranking killers in South African site migrations — Google reads a blanket homepage redirect as a soft 404 and strips the equity.
The 301 Redirect SEO Checklist: Three Phases
Every effective 301 redirect SEO checklist runs in three distinct phases. Most ranking losses after a migration are caused by skipping Phase 1 — mapping is rushed, the launch is messy, and the subsequent Google dance is blamed on the redirect type rather than the missing preparation.
Phase 1: Pre-Migration Planning
| Task | Detail |
|---|---|
| Crawl and export all indexed URLs | Use Screaming Frog or Google Search Console's Coverage report to get a complete list of currently indexed pages — not just the ones your CMS knows about |
| Pull your backlink profile | Identify URLs with significant external backlinks (Ahrefs, Semrush). These are your highest-priority redirect candidates — a missed redirect on a page with dozens of referring domains is a significant equity loss |
| Identify top-performing pages from GSC | Sort by impressions and clicks over the last 12 months. Pages generating organic traffic must be mapped first — do not just redirect by page type |
| Build a 1:1 redirect map | Each old URL maps to exactly one new URL. Match by topic relevance, not URL similarity alone. Document this in a spreadsheet with columns: Old URL | New URL | Status | Priority |
| Decide what to do with orphaned pages | Pages with no traffic and no backlinks may not need a redirect — a clean 404 is sometimes better than a low-quality irrelevant redirect |
| Test redirects in staging | Before the live launch, verify every redirect in your staging environment using a tool like Screaming Frog or a browser redirect checker. Confirm 301 status codes, not 302s |
| Lower DNS TTL (for domain moves) | Reduce Time To Live to the lowest value your DNS provider allows — at least 24-48 hours before cutover — so propagation completes faster after the switch |
Redirect Mapping Rule
Every redirect destination must be topically relevant to the old URL. A product page for running shoes should redirect to the equivalent product on the new site — not to the footwear category page, and never to the homepage. Google may treat irrelevant redirects as soft 404s — meaning link equity may not transfer at all.
Phase 2: Implementation
| Task | Detail |
|---|---|
| Deploy server-side redirects | On Apache/cPanel hosts (common on South African shared hosting), add rules to your .htaccess file. On Nginx-based hosts, modify the server block configuration or use your hosting dashboard's redirect tool |
| Verify status codes after deployment | Use a redirect checker or Screaming Frog to confirm every rule returns HTTP 301 — not 302, not 200 (redirect loop), not 404 |
| Check for redirect chains | A chain occurs when old URL → intermediate URL → final URL. Every additional hop reduces the equity signal and adds latency. Flatten all chains to a single hop before launch |
| Check for redirect loops | URL A redirecting to URL B redirecting back to URL A creates an infinite loop. Both crawlers and browsers abandon looped chains entirely |
| Update your XML sitemap | Remove old redirected URLs from the sitemap. Submit only canonical destination URLs. Do not submit a sitemap containing URLs that return 301 status codes |
| Update internal links | Update every internal link in your CMS to point directly to the new URL. Leaving old internal links in place creates unnecessary redirect hops on every crawl — exactly the kind of crawl budget drain covered in improving your site's crawlability |
| Use Google Search Console's Change of Address tool (domain moves only) | For full domain migrations, use the Change of Address tool in your old domain's GSC property after 301 redirects are live. GSC validates the redirects before the tool activates. Keep the redirects and the tool declaration active for at least 180 days |
Phase 3: Post-Launch Verification
| Task | When | What to Look For |
|---|---|---|
| Crawl the new site | Day 1 after launch | Check for 404s, 302s where 301s are expected, chains, broken canonical tags |
| Submit new sitemap to Search Console | Day 1 | Confirm all URLs in the sitemap are the canonical destination URLs returning 200 |
| Monitor GSC Coverage report | Daily for first 2 weeks | Watch for spikes in "Page with redirect" or "Soft 404" errors — these signal redirect mapping problems |
| Monitor organic traffic | Weekly, first 12 weeks | A correctly executed migration shows a short dip then recovery. A sustained drop after week 4 signals a redirect mapping problem, not normal Google behaviour — check indexation for pages that are not being re-indexed |
| Crawl for chains introduced by new content | Monthly | New internal links added post-migration sometimes point to old redirected URLs — run a monthly crawl to catch these early |
| Keep redirects live | Ongoing (minimum 180 days — ideally permanent) | Do not remove 301 redirects after a few months — external backlinks pointing to old URLs continue arriving. Google's own Change of Address tool recommends keeping domain-move redirects live for at least 180 days; the practical standard for any migration is to leave them in place indefinitely |
Post-Launch Monitoring Window
Ranking stabilisation after a well-executed migration typically takes two to eight weeks. If significant declines persist beyond four weeks despite clean redirect coverage, the issue is usually irrelevant redirect destinations, missing redirects on high-backlink pages, or redirect chains that have not been flattened. Check the mapping, not the redirect type.
Common 301 Redirect Mistakes to Avoid
Running your 301 redirect SEO checklist correctly means avoiding the errors below — they consistently cause post-migration ranking drops and typically surface in audits months after a launch, when the connection to the migration is no longer obvious.
Redirecting Everything to the Homepage
Sending hundreds of deleted product pages, old category URLs, or retired blog posts to the homepage is the most common migration mistake. Google sees no topical relationship between the old URL and the destination and treats the redirect as a soft 404. Result: zero equity transfer on every affected URL.
Leaving Redirect Chains in Place
When a site has been through multiple migrations, redirect chains accumulate: the 2021 URL redirects to the 2023 URL which redirects to the 2026 URL. Each additional hop adds latency and reduces how reliably Google processes the equity signal. Flatten all chains to a direct single-hop before launch — this step is not optional and should be verified, not assumed.
Using 302 (Temporary) Instead of 301 (Permanent)
A 302 redirect sends users to the new page but tells Google the original URL is still the canonical version. Google keeps the old URL indexed and does not transfer equity. If the original URL is gone, this means nothing is indexed and nothing is earning. Many platform-level redirect tools default to 302 — check the status code explicitly.
Forgetting to Update Internal Links
After a migration, internal links pointing to old URLs create unnecessary redirect hops on every page visit and every crawl. The pages load more slowly, Google processes more redirects per crawl, and your effective crawl budget shrinks. Update internal links to point directly to new destination URLs. This is a core step in prioritising your technical search fixes.
Moving platforms and worried about losing your current rankings?
Tell us about the migration you are planning and we will map the redirect risk areas — showing you which pages need a 1:1 map and which can be safely archived without a redirect.
Get a Migration Assessment301 vs 302: Which Redirect Type Should You Use?
The rule is straightforward: 301 for permanent moves, 302 for temporary ones. The SEO consequences of getting this wrong are significant enough to warrant understanding the distinction.
| Redirect Type | Signal to Google | Indexed URL | Link Equity | Use Case |
|---|---|---|---|---|
| 301 (Permanent) | Old URL is retired permanently | Destination URL becomes canonical | Transfers to destination | Domain moves, platform migrations, URL restructures, HTTP → HTTPS |
| 302 (Temporary) | Old URL will return | Original URL stays indexed | No transfer | A/B testing, seasonal page swaps, maintenance pages |
| 308 (Permanent, no method change) | Permanent, like 301 | Destination URL becomes canonical | Transfers to destination | Same as 301 — modern alternative that preserves HTTP request method |
Google treats 301 and 308 redirects equivalently for canonicalisation purposes — either signals a permanent move. The distinction matters for form submissions and APIs, not for standard SEO purposes. What matters most is that you never use a 302 where a 301 is appropriate, and that you implement via server-side rules, not client-side JavaScript.
On JavaScript redirects: Google can process JavaScript redirects, but they depend on rendering — if Googlebot's render queue is delayed, or if the script fails, the redirect instruction may be missed entirely. Server-side redirects process before any rendering occurs and are always Google's stated preference for permanent URL changes.
Why South African Businesses Choose Growth Pulse Media for Technical SEO
If you have read this far and want someone else to run the crawl, build the map, and verify the status codes — that is exactly the work GPM does through its SEO services for South African businesses. Dirk built and scaled a South African ecommerce operation before founding Growth Pulse Media — which means the team has been on the wrong side of a botched platform migration and knows exactly what a redirect chain costs in real revenue.
That operational background shapes how we approach technical work: we prioritise the pages that generate traffic and backlink equity first, not the pages that are easiest to map.
GPM works with a deliberately limited number of active clients at any time so that every migration, technical audit, and redirect implementation gets senior review rather than being handed to a junior team member following a template. We use Screaming Frog, Google Search Console, and Ahrefs as our primary tools — no proprietary black boxes — and every recommendation is explained in plain language alongside the data that supports it.
Who This Checklist Is NOT For
If your site is small and stable with no structural URL changes planned, if the redirect you need is temporary, or if you have no access to a crawl tool to verify status codes — a different approach applies for each scenario.
Sites still on HTTP with no HTTPS migration planned
If your site has not yet moved to HTTPS, the 301 redirect checklist is a downstream concern. The HTTP-to-HTTPS consolidation itself is the more urgent priority. Resolve the certificate and HTTPS canonicalisation first.
Businesses doing a temporary campaign redirect
If you need to redirect a URL temporarily — a seasonal product page, an A/B test variant, a maintenance holding page — use a 302. Applying a 301 to a temporary situation means Google drops the original URL from its index, and recovering that when you revert is an unnecessary headache.
Sites with fewer than 50 indexed pages doing no structural changes
A small, stable site with no URL changes, no domain move, and no platform switch does not need a redirect audit. This checklist applies to migrations and structural changes — if your URL structure is not changing, your energy is better spent on content and backlinks.
Teams planning to manage this manually without audit tooling
Running a 301 redirect implementation across hundreds of URLs by hand — without a crawl tool confirming status codes — produces errors at scale. Status code verification is the one step that cannot be done by eye. If you do not have access to Screaming Frog or an equivalent, invest in a one-month licence before the migration, not after.
Ready to migrate but not sure your redirect map is complete?
Share your current URL structure and we will identify gaps in your redirect coverage before a single visitor hits a 404.
Get a Pre-Migration AuditFrequently Asked Questions About 301 Redirects and SEO
Does a 301 redirect preserve link equity when moving to a new URL?
Google's official position is that a single-hop 301 redirect passes the original page's link equity to the destination. The practical caveat is that equity transfer is not instantaneous — it takes days to weeks for Google to fully consolidate, and if the redirect destination is topically irrelevant, Google may treat the redirect as a soft 404 and pass nothing. The closer the match between old content and new destination, the more reliably signals transfer.
How long does it take for Google to re-index a redirected URL?
For well-crawled sites with clean redirect implementation, Google typically picks up the change within days to a few weeks. Full ranking stabilisation after a large-scale migration can take two to eight weeks for smaller sites and up to three months for migrations involving hundreds or thousands of URLs. Submitting a fresh sitemap in Google Search Console immediately after launch speeds up the process.
Should I remove 301 redirects after the migration is complete?
No — keep 301 redirects live for as long as possible. Google's Change of Address tool guidance for domain moves specifies a minimum of 180 days, but external backlinks pointing to old URLs continue to arrive long after a migration. Removing redirects prematurely turns those links into 404 errors that return no equity. The server overhead from redirect rules is minimal compared to the ranking cost of early removal.
What is a redirect chain and how does it affect rankings?
A redirect chain occurs when the destination of one redirect is itself a redirect: URL A redirects to URL B which redirects to URL C. Each additional hop adds latency, consumes crawl budget, and reduces how reliably the equity signal reaches the final destination.
Google's crawler will stop following a chain after enough hops, meaning very long chains are a reliable way to lose crawl coverage entirely. Flatten all chains to a single direct hop before launch and run a monthly crawl to catch new ones added post-migration.
Can I use JavaScript for 301 redirects on my WordPress site?
JavaScript redirects are a last resort, not standard practice. Google can process them but requires a full render cycle, which may be delayed or skipped. For WordPress sites on Apache hosting, use .htaccess rules for the most reliable server-side 301 implementation. On Nginx-based hosts, modify the server block or use your host's redirect management dashboard — most managed WordPress hosts provide a redirect tool specifically for this reason.
Get a Technical SEO Audit That Catches Redirect Issues Before They Cost You
GPM's technical audits check redirect chains, status codes, sitemap consistency, and canonicalisation signals across your full URL set — using Screaming Frog, Search Console, and Ahrefs against your live site, not a stale export. We handle WordPress, Shopify, and custom builds across South African hosting environments. No obligation — we will get back to you within 24 hours.
Book Your Technical Audit