
The Scenario: A Rebrand That Silently Cost a South African Brand Its Category Rankings
A mid-sized South African retailer rebrands mid-year. The new site launches with fresh category URLs and a 'cleaner' structure. Six weeks later, organic revenue is down 40% and the former top-ranking category pages are gone. No redirect map was built; the old URLs simply 404'd. A redesign is not a design project - it is a migration. Migrations are won or lost before a single pixel is drawn.
The thesis: SEO must own the migration plan, not just audit the wireframes. Treat every URL as a revenue-bearing asset, build a redirect map with developer sign-off, and measure recovery in revenue - not just sessions.
Why a Redesign Is a Migration Project, Not a Design Project
Design teams think in templates; search engines think in URLs and links. When you replatform, you move equity between addresses. Google's guidance is explicit: plan carefully, use 301 redirects for permanent changes, and avoid redirect chains. For same-domain redesigns you do not use the Change of Address tool in Search Console - that is only for domain changes. A same-domain redesign depends entirely on your own redirect discipline.
Warning: Google does not 'figure out' new URLs from a sitemap. Every retired URL needs a mapped 301 or it becomes a dead end for users and crawlers.
The Pre-Launch Inventory: What You Must Map Before Anyone Designs a Page
Before design starts, inventory every indexable URL from your sitemap, Search Console's indexed pages report, and a full crawl. For each, record organic sessions, conversions, revenue (GA4), internal link count, backlinks (Ahrefs), and keyword rankings. This is the baseline for every redirect decision. Also capture canonicals, hreflang (especially for UK, EU, or Middle East audiences), structured data (Product, FAQ, Organisation), and internal link paths - the elements most commonly dropped in a rebuild.
URL Decisions Are Revenue Decisions
Use a revenue-weighted framework:
| URL category | Action | Rationale |
|---|---|---|
| Top 20% by organic revenue | Preserve URL exactly. | Zero risk; design wraps around existing URL. |
| Mid-tier pages with backlinks | 301 to closest equivalent. | Passes link equity. |
| Low-value or duplicate | Retire; 301 to parent or 410. | Reduces crawl waste. |
Map redirects to the most relevant page - not the homepage, which signals soft 404s and loses relevance. If a retired page had traffic or links, 301 to a close match rather than 404.
The Redirect Map: Who Owns It
The map is a spreadsheet: old URL → new URL → status code → notes. SEO owns and signs off; developers implement but lack revenue context. Prioritise high-revenue URLs and validate every entry: no chains (A→B→C), no loops, no redirects to 404s. Crawl staging with Screaming Frog to compare.
Tip: For large sites, script the map by matching old and new URLs on title or H1 similarity, then manually review the top 100 by revenue.
Staging Discipline and the Post-Launch Trap
Launch Timing: Scheduling Around Your Commercial Calendar
Never launch during peak trading - Black Friday, festive season, or a major product drop. Schedule at least two weeks before or after, with the team available for monitoring. For South African brands with international customers, avoid major holidays in key markets too. Aim for a quiet window where a temporary dip won't cost a quarter's revenue.
What Redesigns Quietly Break
- Canonicals: New templates may omit or mispoint them. Each page should self-canonicalise.
- hreflang: Update for new URLs; broken hreflang causes wrong-country pages to rank.
- Structured data: Product, Breadcrumb, and Organisation schema are often dropped. Re-implement and test with the Rich Results Test.
- Internal links: Navigation changes can orphan deep pages. Compare link counts pre- and post-launch.
- XML sitemap: Regenerate and resubmit; remove old references. For same-domain redesigns, do not use Change of Address.
Warning: Keep the old Search Console property verified for at least 6 months post-launch to monitor legacy 404s and redirect issues.
Tracking Readiness: GA4, Consent, and Server-Side Tagging
If conversion events change names or parameters, historical data breaks and bidding algorithms lose signal. Document every GA4 event and parameter, and fire the same names on the new site. Implement consent mode v2 for EU/UK traffic; POPIA requires consent for non-essential cookies in South Africa. If you use server-side tagging, update the container for the new domain and paths. Breakages here create attribution gaps that make recovery impossible to measure.
Post-Launch Measurement: Organic Revenue Recovery
Compare organic sessions, conversions, and revenue against the equivalent pre-launch period and year-on-year. Also monitor:
| Metric | What it reveals | Action threshold |
|---|---|---|
| Indexed page count | Whether new URLs are discovered. | Escalate if 20%+ of key pages unindexed at 4 weeks. |
| 'Crawled - currently not indexed' | Quality or crawl budget issues. | Investigate if it spikes for revenue pages. |
| 404 errors | Missed redirects or broken links. | Fix 404s on backlinked URLs within 48 hours. |
| Organic revenue (GA4) | True business impact. | Escalate to a technical audit if down >20% at 8 weeks. |
A well-executed migration typically stabilises organic revenue within 4-8 weeks and recovers to baseline by 12. Use [Prebo Digital's custom reporting approach](https://prebodigital.co.za/our-custom-reporting-approach/){: target='_blank' rel='noopener noreferrer' class='text-blue-600 hover:text-blue-700 hover:underline'} to align stakeholders.
POPIA and the Redesign
POPIA (Act 4 of 2013), enforced by the Information Regulator, applies to new forms, tracking pixels, and data flows. With your legal/DPO, update consent banners, privacy notices, and cookie categories. Don't claim compliance - document the review and block non-essential tags until consent is given. It is also a trust signal.




