I’ve lost count of the number of times a business owner has contacted me a month after launching a new website, confused and worried. The site looks great. Everyone loves the design. But enquiries have dropped and Google traffic has fallen by half.
When I look into it, the cause is nearly always the same. Old pages were deleted or moved without redirects. Content that ranked well was cut down to a few sentences because it “looked cleaner”. The staging site’s noindex setting went live with the new design. Nobody did anything malicious; they just didn’t know what search engines rely on.
A redesign doesn’t have to cost you rankings. Often it improves them. But it needs a process. This is the one I follow on every redesign and migration.
Why redesigns cause ranking drops
Search engines rank individual pages, not websites as a whole. Each page has built up signals over time: the content on it, links pointing to it, its URL, its title and how users interact with it. When a redesign changes those things without care, the signals break.
The most common causes of lost traffic are:
- URLs changing without 301 redirects, so old links and rankings lead to 404 errors.
- Content being removed or heavily shortened.
- Page titles and meta descriptions being lost or replaced with generic ones.
- Internal links being restructured so important pages become harder to reach.
- Technical settings, such as noindex tags or robots.txt rules, being carried over from staging.
- Slower page speed from a heavier new design.
Each of these is preventable.
Step 1: Benchmark before you change anything
Before work begins, record where you stand. You’ll need this baseline to measure the redesign’s impact and to spot problems quickly.
- Export performance data from Google Search Console: top pages, top queries, clicks and impressions for the last several months.
- Note key metrics from analytics, including organic traffic and conversions by page.
- Record rankings for your most important keywords if you track them.
- Run speed tests on key templates.
Save all of this somewhere safe. After launch, you’ll compare against it constantly.
Step 2: Crawl the old site
Use a crawler tool to collect every URL on your current site, along with titles, meta descriptions, headings, canonical tags and status codes. Desktop crawling tools make this easy, and many have free versions for small sites.
Don’t rely on the crawl alone. Some valuable pages may not be linked internally anymore but still receive traffic or have external links. Combine your crawl with:
- URLs from your XML sitemap.
- Top landing pages from analytics.
- Pages with impressions in Search Console.
- Pages with external backlinks, from a backlink tool.
The result is a complete inventory of URLs that matter.
Step 3: Decide what happens to each page
With the inventory in hand, go through each URL and decide its future:
- Keep with the same URL.
- Move to a new URL, which needs a redirect.
- Merge with another page, redirecting to the combined page.
- Remove, either redirecting to the most relevant alternative or, if truly obsolete with no traffic or links, returning a 404 or 410.
This step is where you protect your best assets. Pages that bring in traffic or enquiries should keep their content, or improve it. Be very careful about cutting long, detailed pages down to a few lines for design reasons. That depth is often exactly why they rank.
Keeping URLs unchanged wherever possible is the safest option of all. If your current URLs are reasonable, there’s often no need to change them just because the site is new.
Step 4: Build a redirect map
For every URL that moves or merges, map the old address to the most relevant new one. A simple spreadsheet works: old URL in one column, new URL in another.
Rules for good redirects:
- Use 301 redirects, which tell search engines the move is permanent.
- Redirect each old page to its closest equivalent, not everything to the homepage. Mass redirects to the homepage are treated much like 404s.
- Avoid redirect chains, where one redirect leads to another. Point directly to the final URL.
- Include variations such as trailing slashes and old URL parameters if they were used.
In WordPress, you can implement redirects with an SEO or redirection plugin, or at the server level for better performance. On Nginx, a simple redirect looks like this:
For large redirect maps, server-level rules or a dedicated redirect plugin with import features save a lot of time.
Step 5: Carry over on-page SEO
For every page you keep, move or merge, make sure the essentials survive:
- Page titles and meta descriptions, rewritten only if you’re improving them.
- Heading structure, with one clear main heading.
- Image alt text.
- Structured data such as Organization, LocalBusiness, Product or FAQ schema.
- Canonical tags pointing to the correct URLs.
New themes often output headings and schema differently. Check what the new templates actually produce rather than assuming it matches.
Step 6: Keep internal linking strong
Internal links tell search engines which pages matter most. Redesigns often simplify navigation, which is good for users but can accidentally bury important pages several clicks deep.
Make sure your key service and category pages remain linked from the main navigation or homepage. Update internal links in content to point to new URLs directly, rather than relying on redirects.
Step 7: Test on staging, properly
Staging sites should be hidden from search engines while you work. Use password protection, ideally, since it’s more reliable than a noindex tag alone.
Before launch, test thoroughly:
- Crawl the staging site to find broken links, missing titles and incorrect canonicals.
- Test your redirect map against staging to confirm every old URL lands in the right place.
- Run speed tests on key templates and compare with your benchmark.
- Check mobile layouts and Core Web Vitals.
- Validate structured data.
Step 8: Launch carefully
On launch day, go through a short but critical checklist:
- Remove password protection and noindex settings. In WordPress, make sure “Discourage search engines” is unticked under Settings, then Reading.
- Check robots.txt isn’t blocking anything important.
- Confirm the XML sitemap lists the new URLs and submit it in Search Console.
- Test a sample of old URLs to confirm redirects work on the live site.
- Check analytics and conversion tracking are firing.
I’ve seen more traffic disasters caused by a forgotten noindex setting than by any other single mistake. Check it twice.
Step 9: Monitor closely after launch
Some fluctuation in the first few weeks is normal while search engines reprocess the site. What matters is spotting real problems early.
For the first month, check regularly:
- Search Console’s page indexing report for 404 errors and excluded pages.
- Crawl errors and redirect issues.
- Organic traffic and conversions compared with your benchmark.
- Rankings for important terms.
- Server logs, if you have access, for frequently requested old URLs you missed.
When you find a 404 for an old URL that had value, add a redirect. Small fixes in the first weeks prevent long-term losses.
Domain changes need extra care
If the redesign also involves changing domain, everything above still applies, plus a few more steps. Redirect every old URL to its equivalent on the new domain, keep the old domain registered and redirecting for the long term, and use the Change of Address tool in Search Console. Expect a longer settling period than with a simple redesign.
Frequently asked questions
Will my rankings drop temporarily after a redesign?
Some movement is common for a few weeks, even with a perfect process. If you’ve kept URLs or redirected them properly and preserved content, rankings usually settle at or above their previous level. Sustained drops point to a problem that needs investigating.
How long should I keep redirects in place?
Ideally, permanently. Old links on other sites and bookmarks can keep sending visitors for years. Redirects cost almost nothing to maintain.
Can a redesign improve SEO?
Yes. Faster load times, better mobile experience, clearer structure, improved content and proper schema can all lift rankings. The goal of this process is to protect what you have so those improvements add to it rather than replace it.
Should I change my URL structure during a redesign?
Only if the current structure is genuinely poor, for example URLs full of parameters or dates that make no sense for your content. Changing URLs always carries some risk, so do it when the benefit is clear, and redirect everything carefully.
Final thoughts
A redesign is a chance to improve how your site looks and works, but it shouldn’t come at the cost of the search visibility you’ve built over years. Benchmark first, map every URL, redirect carefully, protect your best content and watch closely after launch. With that process, a new design can be a fresh start rather than a setback.




