If your traffic dropped after a website redesign, something likely changed in how search engines access, understand, index or evaluate your pages. The problem is usually not the visual redesign on its own. It is more often caused by changed URLs, missing redirects, removed content, weaker internal links, noindex tags, canonical mistakes, slower templates, rendering issues or broken tracking.
Start with diagnosis before making fixes. The key question is: what changed at launch, and did that change affect the pages that previously brought in organic traffic, enquiries or sales?
A redesigned website can look cleaner and still perform worse in search if the rebuild weakens the technical, content or internal-linking signals behind important pages.
First, work out what kind of drop you have
Not every post-redesign decline is the same. A traffic drop, ranking drop, tracking issue, redesign issue and migration issue can look similar in reports, but they need different fixes.
| Problem type | What it means | What to look for | Best first response |
|---|---|---|---|
| Traffic drop | Fewer organic visits are reported | Organic sessions fall after launch | Confirm tracking, then inspect affected landing pages |
| Ranking drop | Pages lose search positions | Key queries lose position or impressions | Compare old and new page content, links and redirects |
| Tracking issue | Reports changed, but traffic may not have | Drop starts exactly when analytics, tags or consent settings changed | Fix measurement before changing SEO |
| Redesign issue | Layout, navigation, copy or templates changed | Same URLs remain, but content or linking is weaker | Compare old and new templates, headings, copy and internal links |
| Migration issue | URL, CMS, platform, domain or site structure changed | Redirect errors, 404s, canonical changes or indexing issues appear | Review redirects, crawlability, canonicals and sitemap coverage |
A redesign is mainly a change to design, layout, content presentation or templates. A migration usually changes the CMS, ecommerce platform, domain, URL structure or technical setup. Many website projects are both, which is why post-launch traffic drops often need technical and content review together.
What to check first
Do not start by rewriting pages or publishing new blog posts. Work through the most likely failure points in order.
First, confirm whether the drop is real. A redesign can break analytics tracking, change consent behaviour, remove tags or alter channel attribution. If the tracking setup changed on launch day, reports may show a traffic drop even when search visibility has not fallen as sharply as it appears.
Next, compare the decline with the launch date. A drop that starts immediately after launch usually points to tracking, redirects, indexation, crawlability or template changes. A slower decline may involve content changes, internal-link losses, recrawling patterns or market factors.
Then identify the affected pages. Total traffic is too broad. Look at the landing pages that lost organic clicks, impressions, enquiries, sales or revenue. Prioritise pages that previously had commercial value.
After that, review old and new URLs. If the redesign changed URL structure, important old URLs should redirect to the closest relevant new page. Redirecting everything to the homepage may be convenient, but it usually weakens topical relevance.
Finally, review indexation. Important live pages should be crawlable, indexable and canonicalised correctly. A forgotten noindex tag, blocked template, wrong canonical or broken sitemap can undermine pages that look perfectly fine in the browser.
Why traffic drops after redesigns
The most common redesign problems fall into four groups: URL changes, content changes, internal-link changes and technical template changes.
Old URLs were changed without proper redirects
This is one of the highest-risk redesign issues. If a service page, category page or guide had organic visibility before the rebuild, the old URL needs a relevant destination after launch.
A proper redirect should preserve user intent as closely as possible. An old “technical SEO audit” page should point to the new technical SEO audit page, not the homepage. An old ecommerce category should point to the matching new category, not a generic shop page.
The more valuable the old page was, the more carefully the redirect should be handled. Pages with organic traffic, backlinks, sales, enquiries or strong internal links should never be bulk-redirected without review.
Useful pages were removed
Redesigns often simplify websites. That can improve user experience, but it can also remove pages that were quietly doing important search work.
Old blog posts, FAQs, service pages, comparison pages, location pages and ecommerce category descriptions may look dated, but some may still attract qualified traffic or support internal links to commercial pages. The decision is not automatically to keep everything. The better decision is to assess whether each page should be restored, merged, redirected or retired.
The mistake is deleting pages because they look old without checking whether they had search visibility or commercial value.
The new copy is cleaner but less useful
A redesigned page can be visually stronger and still less helpful. This happens when specific headings are replaced with broad brand statements, service details are shortened too aggressively, FAQs are removed, category copy disappears or internal links are stripped from the body copy.
Good SEO content does not need to be long for the sake of it. It does need to answer the questions that matter: who the page is for, what problem it solves, what has changed, what the user should do next and why that page is the right destination.
If the redesign made important pages thinner, vaguer or less connected to buyer intent, traffic and rankings may soften even if the design improved.
Internal links were lost
Internal links are often rebuilt without enough attention during a redesign. Navigation changes, footer changes, related-resource modules, breadcrumbs and contextual body links can all affect how important pages are discovered.
A high-value service page that used to be linked from the homepage, resources and related service pages may still exist after launch, but carry less internal authority if those links disappear. The page has not been deleted, but it has become less prominent in the site structure.
This is where a website technical audit can be useful, especially when the old site structure was not documented before launch.
Technical settings changed during launch
Some redesign issues are caused by small technical settings with large consequences. A page can look live to users while search engines receive the wrong signals.
Common examples include noindex tags left over from staging, robots rules blocking important areas, canonicals pointing to old or incorrect URLs, broken templates, redirect chains, JavaScript rendering issues and sitemap URLs that no longer match the live site.
These problems are easy to miss if the post-launch review only checks visual design and page copy.
How to decide what to fix first
A redesign traffic drop should be prioritised by commercial impact, not by the length of the issue list.
| Priority | Fix type | Examples | Why it matters |
|---|---|---|---|
| Urgent | Visibility blockers | Noindex on important pages, broken redirects, 404s on valuable URLs, blocked crawling, wrong canonicals, broken tracking | These can prevent the business from understanding or recovering search performance |
| Important | Relevance and structure issues | Lost internal links, thinner service pages, removed category copy, buried commercial pages, weak redirect targets | These can reduce visibility even when pages remain indexable |
| Monitor | Lower-risk issues | Minor metadata changes, low-value page losses, newly launched pages awaiting recrawl | These matter, but should not distract from higher-impact fixes |
This order prevents teams from spending time polishing title tags while core service pages are noindexed, old URLs are returning errors or ecommerce categories have lost crawlable content.
Ecommerce redesign example
Ecommerce redesigns need extra care because one template decision can affect hundreds of pages.
For example, an online store may move from WooCommerce to Shopify, or rebuild a category template to look cleaner on mobile. During that process, the new category page might lose its introductory copy, remove links to subcategories, hide pagination behind scripts and canonicalise product variants differently.
The result is not one isolated page issue. It can affect every category using that template.
In that situation, the review should separate category traffic, product traffic, brand traffic and blog traffic. Losing visits to old informational posts is different from losing visibility on high-intent category pages that previously drove sales.
If the redesign involved a platform move, category rebuild or product-template change, an ecommerce SEO consultant can help assess whether the issue is technical, structural or category-targeting related.
When to get expert help
You should bring in specialist support when the drop affects leads, ecommerce sales, important service pages or business confidence in the new website.
It is also worth getting help when the team cannot clearly answer:
- Which pages lost visibility?
- Did tracking change at launch?
- Were old URLs redirected to relevant new URLs?
- Are important pages indexable?
- Did the redesign remove useful copy or internal links?
- Are rankings down, or are reports inaccurate?
A focused technical SEO South Africa review can bring those questions into one investigation. The aim is not to undo the redesign. The aim is to understand what changed, separate real visibility loss from reporting problems and prioritise the fixes that matter commercially.
Related reading
If the issue appears technical, start with the technical SEO and audit resources before making content changes. The SEO resources South Africa section also includes related guides for site structure, redirects, audits and technical SEO decision-making.
Next step
A traffic drop after a redesign is stressful because the new site is already live and the old version may no longer be easy to compare. The safest next step is a clear review of what changed at launch, which pages were affected and whether the problem sits in tracking, redirects, indexation, content, internal links or templates.
If the drop started around launch and affected important commercial pages, start with diagnosis before changing content or commissioning another redesign.
Discuss a technical SEO review to get a clearer view of what to investigate, what to fix and what to monitor next.