Your new website went live on a Friday. It looks better, loads faster, and the client is happy.
Three weeks later the enquiries have dried up. Pages that used to rank on page one are gone. Nobody changed the content, nobody was penalised, and the SEO team swears nothing was touched.
What happened is almost always the same thing. The URLs changed, the redirects were not set up properly, and Google quietly dropped every page it could no longer find.
This is the most common way a website redesign destroys organic traffic, and it is entirely preventable. Here is what actually breaks, and what to check before you launch.
We handle both web development and SEO in the same studio, which means we see this from both sides. The developer did nothing wrong. The SEO was never in the room when the URL structure was decided.
What is a 404 error
A 404 is the status code a server returns when a page does not exist at the requested URL. It tells browsers and search engines that the address is valid but there is nothing there. On its own a 404 does not harm your rankings. The damage comes from what a redesign leaves behind: pages that used to rank, now returning 404, with nothing pointing visitors or Google to the replacement.
Google’s own position is that “404s are a normal part of a website” and you can safely ignore them when those URLs genuinely should not exist. The problem is that after a redesign, most of them should exist.
Five things that break during a redesign
1. URLs change without anyone deciding to change them
This is the big one, and it usually happens by accident.
A new theme or CMS restructures the permalink format. /services/seo-services/ becomes /service/seo/. The page is still there; the content is identical, but to Google it is a brand new URL with no history, no backlinks, and no rankings. The old URL now returns a 404.
Multiply that across 40 pages and 99 blog posts, and you have lost the entire site’s search presence in one deployment.
2. Everything gets redirected to the homepage
When someone notices the 404s after launch, the fastest fix is to point every broken URL at the homepage. It clears the error report and feels like a solution.
It is not. Google treats a mass redirect to the homepage as a soft 404, because the destination has nothing to do with what the visitor asked for. Martin Splitt from Google has been direct about this, warning that redirecting all 404 pages to the homepage has a negative impact on rankings.
Every redirect should go to the closest equivalent page. A blog post about packaging design goes to the new packaging post, not to the homepage. If there is no equivalent, leave the 404.
3. Internal links still point at the old URLs
Your redirects are working, so the pages load. But every internal link on the site is now routed through a redirect instead of going straight to the destination.
That slows the site, wastes crawl budget, and on a large site can create redirect chains where one old URL points to another old URL before finally reaching a live page. Google follows a limited number of hops before giving up.
Google’s own guidance on site moves is explicit about updating “internal links on the new site from the old URLs to the new URLs.” Redirects are a safety net for external traffic, not a substitute for fixing your own links.
4. The sitemap still lists pages that no longer exist
A sitemap full of 404s tells Google your site is poorly maintained, and it sends the crawler to dead addresses instead of your new pages.
Google’s instruction after a move is to “submit the new sitemap in Search Console” and then remove the old one. Most redesigns skip both halves.
5. The staging site’s noindex tag goes live with the site
This one is rare, catastrophic, and we have seen it more than once.
Development sites are usually blocked from search engines with a noindex meta tag or a Disallow in robots.txt. If that block is still in place when the site goes live, Google will deindex the entire website within days.
Everything looks perfect to a visitor. The site simply vanishes from search.
Check this on launch day. It takes thirty seconds and it is the single highest consequence item on the list.
301 or 302: which redirect to use
A 301 is a permanent redirect. It tells Google the page has moved for good and that ranking signals should transfer to the new URL. This is what you want for a redesign.
A 302 is temporary. It tells Google to keep the old URL indexed because the original will return. Using a 302 for a permanent move means Google keeps looking at a URL that no longer has content.
Google’s guidance is to “use server side permanent redirects if technically possible” and recommends “HTTP permanent redirects if possible, such as 301 and 308.”
Two things to avoid. Meta refresh redirects in the page HTML and JavaScript redirects both work for humans but are slower and less reliable for crawlers. Server side is always better. And on WordPress, a redirect plugin is fine for a handful of URLs but creates a database lookup on every request at scale. For a full migration, redirects belong in the server configuration.
When to redirect and when to leave the 404
Not every broken URL deserves a redirect. Over-redirecting creates its own mess.
Redirect when:
- The content moved to a new URL
- An equivalent page exists, even if the wording changed
- The old page has backlinks pointing at it from other sites
Leave the 404 when:
- The content is permanently gone and nothing replaces it
- The page was a test, a duplicate, or something that should never have been published
- No external site links to it
A clean 404 with a helpful page is a better answer than a redirect to something irrelevant. Build a proper 404 page with your navigation, a search box and links to your main sections, so a visitor who lands there has somewhere to go.
How long to keep redirects running
This is where most businesses underestimate the timeline.
Google’s guidance is to “keep the redirects for as long as possible, generally at least 1 year,” because that is how long it can take for all signals to transfer to the new URLs.
A year. Not a month, and not until the error report looks clean.
If your hosting plan or your developer wants to remove the redirect rules after the launch settles down, say no. Removing them early undoes the entire migration.
The redesign checklist
Before you launch
Export every indexed URL on the existing site. Search Console and your sitemap together give you the real list.
Map each old URL to its new destination in a spreadsheet. One row per URL. This document is the migration.
Note which pages have backlinks. Those are the ones where a lost redirect costs the most.
Record current rankings and traffic so you have a baseline to compare against.
On launch day
Check that the noindex tag and the robots.txt block are removed.
Test a sample of redirects manually, including the deepest pages, not just the homepage.
Submit the new sitemap in Search Console.
Confirm the canonical tags point at the new URLs.
In the weeks after
Watch the Index Coverage report in Search Console for new 404s and crawl errors.
Fix internal links so they point directly at new URLs instead of through redirects.
Compare traffic against your baseline at two weeks, one month and three months.
Keep the redirect rules in place for at least a year.
Common mistakes
Launching on a Friday. If something breaks, nobody is available until Monday and the crawler has had three days with a broken site.
Treating the redirect map as the developer’s job. The developer knows which page is which technically. Only someone looking at search data knows which pages matter.
Changing URL structure for cosmetic reasons. A shorter, prettier URL is not worth losing a page that ranks. If the current URL works, keep it.
Assuming a plugin handled it. Most redirect plugins only catch what you tell them to catch. They do not discover your old URLs on their own.
Checking only the homepage after launch. The homepage almost always works. The damage is three levels down.
Where this usually goes wrong
In most redesign projects the developer and the SEO team are different vendors, and the URL structure gets decided in a design meeting that the SEO person was not invited to. By the time anyone looks at search data, the site is live and the rankings are already falling.
We run website development and search engine optimisation from the same team in Ahmedabad, so the URL map gets built before the design is signed off rather than after launch. If you are planning a redesign, that sequence matters more than almost anything else on this page.
For the wider technical picture, our technical SEO checklist covers what to audit beyond redirects, and 10 common SEO issues covers why a site that looks fine still does not rank.
Before your next redesign
Open Search Console, export your current list of indexed URLs, and save it somewhere safe. If a redesign is coming, that file is the most valuable document in the project.
Everything else on this page follows from having it.
If you want the development and the SEO handled by the same team rather than two vendors blaming each other after launch, talk to us. We have been building and ranking websites from Bopal since 2018, with a 4.8 rating from over 130 client reviews.
Frequently asked questions
Do 404 errors hurt SEO?
Not directly. Google states that 404s are a normal part of any website. The damage comes indirectly, through lost link equity when ranking pages return 404, wasted crawl budget, and a poor experience for visitors who land on a dead page.
Should I redirect all 404 pages to my homepage?
No. Google treats this as a soft 404, and it can hurt rankings. Redirect each URL to its closest equivalent page, and leave a proper 404 where no equivalent exists.
What is the difference between a 301 and a 302 redirect?
A 301 is permanent and transfers ranking signals to the new URL. A 302 is temporary and tells Google to keep the old URL indexed. Use 301 for a redesign or migration.
How long should redirects stay in place after a redesign?
Google recommends keeping them for as long as possible, and at least one year, so that all signals have time to transfer to the new URLs.
Why did my traffic drop after a website redesign?
The most common causes are URL changes without redirects, mass redirects to the homepage, a staging noindex tag left live, and a sitemap still listing old pages. Check those four first.
What is a soft 404?
A page that returns a success status code while showing no real content, or a redirect that sends a missing page somewhere irrelevant, such as the homepage. Google flags both because they make the site structure harder to understand.
