A redesign is exciting. A fresh look, a faster build, clearer messaging. It is also one of the easiest ways to lose search traffic that took years to earn, and most of that loss is avoidable.
Search engines do not punish you for looking different. They react to what changes underneath: your URLs, your page content, your internal links, and your speed. Control those four things and a redesign can improve your rankings instead of resetting them.
Start with a snapshot of what works today
Before anyone opens a design tool, record how the current site performs. You cannot protect what you have not measured, and after launch you will want something to compare against.
- Export every indexed URL from your sitemap and from a full crawl of the site.
- Pull your top landing pages by organic clicks over the last twelve months from Google Search Console.
- Mark the pages that bring in enquiries or sales, not just visits. A page with modest traffic that produces leads matters more than a popular page that produces none.
- Record load speed and Core Web Vitals for your ten most important pages.
- Take a full backup of the files and the database.
It sounds like a lot of admin for a design project, and it is. It also takes about a day, and it is the cheapest insurance you will buy. When someone asks in March why traffic dipped, you will have an answer instead of a guess.
Rule of thumb: if a page earns clicks or leads today, its redesigned version should keep the same address, the same main topic, and at least as much useful content.
Keep URLs stable wherever you can
The single biggest cause of lost traffic after a redesign is changed URLs without proper redirects. Search engines have learned that /services/web-design is the page about web design. Move it to /what-we-do/websites and, to a crawler, it is a brand new page with no history.
When a URL has to change
Sometimes it does. You merge two thin pages, retire a service, or fix a messy structure. That is fine, as long as every old address points to the closest new one with a permanent (301) redirect. A 301 tells search engines the move is permanent and that the old page’s signals should carry over. A 302 says the move is temporary, which is almost never what you mean in a redesign.
Build a redirect map
Create a simple spreadsheet before development starts, not after. One row per old URL:
| Old URL | New URL | Redirect | Note |
|---|---|---|---|
| /services/web-design | /services/web-design | None | Address unchanged |
| /our-work | /portfolio | 301 | Section renamed |
| /blog/2019/05/old-post | /blog/old-post | 301 | Date removed from path |
| /old-offer | /services | 301 | Page retired, closest match |
Redirect to the most relevant page, not blindly to the homepage. Sending every old URL to the home page looks like a soft error to search engines and frustrates visitors who clicked a specific result. Google’s own guidance on site moves with URL changes is worth reading with your developer.
Protect the content that ranks
Designers love white space. Search engines love answers. The two can coexist, but only if someone checks that a cleaner layout did not quietly delete the paragraphs doing the ranking.
Do not thin out your pages
If a page ranks for a question, keep the section that answers it, along with its headings. Shortening copy to make a page feel airy is the most common way a redesign trims rankings. Move supporting detail into tabs or accordions if you must, but keep it in the page itself.
Carry over the metadata
These details are invisible on the page and easy to forget in a rebuild:
- Title tags and meta descriptions
- Canonical tags and hreflang annotations, if you use them
- Structured data, as explained in our guide to structured data in plain English
- Image file names and alt text
- The heading structure, with one clear H1 per page
Rebuild internal links on purpose
Internal links tell search engines which pages matter. New navigation, new footers, and new templates change those links overnight. Make sure your most valuable pages are still linked from the main menu, from relevant articles, and from each other, using descriptive link text rather than ‘click here’.
Test on staging, then test again
Build and review the new site on a private staging copy. Two rules apply here, and both are about indexing.
First, keep staging out of search results while you test. A staging site that gets indexed creates duplicate content and confusion. Second, and this one catches experienced teams, remember to remove that block when you launch. A leftover noindex setting has hidden many freshly launched sites from Google for weeks.
Run through this list before the switch:
- Crawl the staging site and compare it to your list of old URLs.
- Test every row of the redirect map.
- Compare titles, headings, and key copy on your top twenty pages.
- Check mobile layouts, forms, and tracking codes.
- Run speed tests, and fix anything slower than the old site. Our WordPress speed checklist is a good place to start.
- Confirm accessibility basics, using the ten quick fixes as a guide.
The first thirty days after launch
Launch day is the start of the monitoring period, not the end of the project.
On day one, submit the new sitemap in Search Console, confirm the robots file allows crawling, and spot-check a dozen redirects by hand. During week one, look at the Pages report for new errors and crawl the live site to catch broken links. Over the following month, compare impressions, clicks, and conversions with your snapshot.
Expect some movement. Rankings often wobble for a few weeks as search engines reprocess the site. A steady, gradual recovery is normal; a sharp, sustained drop on specific pages usually means a missing redirect or removed content, and it is fixable once you know where to look.
The short version
Treat a redesign as a migration with a design attached. Measure first, keep addresses stable, redirect what must move, protect the content that earns its place, and watch the numbers afterwards. Do that, and your new site gets to be both better looking and better found.