Quick answer: To redesign a website without losing SEO, audit and benchmark your current rankings first, then map a 301 redirect for every old URL to its new one, preserve the pages and content that already rank, keep your metadata and internal links intact, and verify everything after launch. The most common mistake is launching a new design and deleting the pages that were earning your traffic.
There's a pattern that plays out the same way over and over.
A business gets a fresh new website. It looks sharp. The owner's proud. And then, about two weeks later, they check their traffic and it's fallen off a cliff. Leads dry up. Calls stop. And nobody can figure out why, because the new site is objectively prettier than the old one.
The answer is almost always the same: they redesigned the site and threw away the SEO by accident. They deleted pages that were ranking, changed URLs without redirecting them, and replaced content that was doing real work with new copy that wasn't.
A redesign should make your site look better, not make it disappear.
Why redesigns tank rankings
Google has spent years building a map of your site. It knows which pages rank, which URLs earn clicks, which content answers real questions. That map is your accumulated SEO equity, and it's worth more than any design.
A redesign that ignores that map is like renovating a house and accidentally demolishing the foundation. You don't notice while you're focused on the new paint, and then the whole thing lists sideways.
The specific mistakes, in order of how often they tend to happen:
Deleting pages that rank. The single biggest one. A page that's been earning you traffic for years gets cut because it "didn't fit the new design." That page was an asset. Deleting it deletes the ranking.
Changing URLs without redirects. You move a page to a new address and don't tell Google where it went. Every link, every bookmark, every bit of accumulated trust now points to a 404.
Rewriting content that was working. New copy that's cleaner but no longer answers the question the page ranked for. Google's own guidance on helpful, people-first content points to relevance and usefulness, not polish, and rewriting past the point that made the page useful can cost you the ranking.
Ignoring metadata and structure. Titles, descriptions, headings, schema. The redesign swaps them for defaults, and the page loses the signals that told Google what it was about.
The website redesign SEO checklist
Twelve steps, in the order they happen. None of them is hard. Skipping them is what costs rankings.
Before you touch anything
1. Benchmark what you have today. Export the last 12 months from Google Search Console: every query and every page, with clicks, impressions and average position. Export your top landing pages from your analytics too. This is the baseline you'll compare against after launch, and the list of what you can't afford to lose.
2. Crawl every URL: run the whole site through a crawler such as Screaming Frog and list every URL that exists, including pages, blog posts, PDFs and images. Not a sample, every one.
3. Note which pages other sites link to. Search Console's Links report shows your most linked pages. A page with links pointing at it keeps a job even when it brings little traffic, because those links carry trust you want to pass on.
4. Decide each URL's fate: for every URL, choose one: keep it, merge it into a stronger page, or retire it. Anything that ranks, converts or has links stays or merges. Nothing that earns gets deleted.
During the build
5. Keep URLs the same wherever you can. The safest redirect is the one you never need. If the new platform lets you keep an address exactly, keep it, trailing slash and all.
6. Build the redirect map: one row per old URL, where it goes and why. Every redirect should be permanent, a 301 or 308, and go straight to the final page in one hop. Googlebot can follow up to 10 hops in a chain, but Google's site move guide advises redirecting to the final destination directly.
Here's the shape of a redirect map, with example rows:
| Old URL | New URL | Type | Why |
|---|---|---|---|
| /services/furnace-repair.html | /furnace-repair | 301 | Same page, new address |
| /blog/2019-furnace-tips | /blog/furnace-maintenance | 301 | Merged into the stronger article |
| /summer-promo-2021 | /offers | 301 | Retired, sent to the closest live page |
7. Keep what made each page rank. The title, the headings, the answers on the page, the internal links pointing to it and its structured data. Make it look better, but don't strip out the substance.
8. Build on a staging site Google can't see. Password-protect it or mark it noindex, so the half-built site never competes with the live one. Then plan its removal: Google's guide says to prepare the list of URLs that need their noindex removed before the move starts. A forgotten noindex is one of the fastest ways to vanish.
On launch day
9. Switch on the redirects and test them. Run every old URL from your map through a redirect checker. Each one should answer 301 and land on the right page in one hop, never on a 404, and never on the homepage by default.
10. Tell the search engines: remove the staging block, submit the new sitemap in Search Console, and request indexing for your most important pages. If the domain itself changed, submit a Change of Address in Search Console for the old site. Submit the sitemap to Bing Webmaster Tools too, or use IndexNow, which shares new and changed pages with Bing and other engines as soon as you publish.
After launch
11. Watch the first 12 weeks. In week one, check Search Console every day for 404s and redirect errors. After that, compare clicks and positions with your benchmark every week. Google's guide says a medium-sized site can take a few weeks or more before the new URLs replace the old ones in results, and larger sites longer, so expect some movement while it recrawls.
12. Fix fast, then improve: a missing redirect or a dropped page shows up as a drop on one URL. Restore the page or redirect it properly as soon as you find it. Once traffic is steady, start improving the pages that never ranked.
Changing platforms or domains
Moving from WordPress to Wix, from Wix to something else, or from an old domain to a new one adds two risks. URL patterns change all at once. And the new platform may write titles, headings and structured data differently from the old one.
- Compare key pages side by side before launch: title, H1, body text, internal links and structured data on the old page and the new one.
- Check what the new site shows without JavaScript. Some builders draw the page in the browser, and a crawler that doesn't run scripts sees an almost empty page. In our study of 1,061 business websites built with AI app builders, 71% of 430 Base44 homepages showed fewer than 100 words to such a crawler.
- Keep the old redirects running for at least a year. That's Google's own guidance: generally at least 1 year, so it can transfer the signals and links that point at your old URLs.
Common redesign mistakes that cost rankings
- Sending every old URL to the homepage. Google's site move guide warns that redirecting many old URLs to one irrelevant page, such as the new home page, can confuse users and might be treated as a soft 404.
- Leaving the staging noindex on after launch, or blocking the new site in robots.txt.
- Stacking new redirects on top of old ones, so an address from three redesigns ago now takes three hops.
- Changing every URL, title and heading at once, so when a page drops you can't tell which change did it.
- Deleting old blog posts that still bring in traffic or links.
- Forgetting the links you control elsewhere, such as your Google Business Profile, directory listings and social profiles still pointing at old addresses.
What we did for the Clearly.ca migration
Before we touched a single redirect, we ran the entire existing site through Screaming Frog and documented every URL that existed, not a sample and not just the important pages, so nothing got lost in a bulk mapping sheet.
This mattered more than usual because the backend architecture was changing, not just the design on top of it. That kind of shift means URL patterns, content groupings, and even how pages get generated can all move at once. A quick bulk redirect approach assumes the old structure maps cleanly onto the new one. It rarely does.
The process felt slow. There were moments it felt like overkill to check URL by URL when a spreadsheet macro could have "finished" the job in an afternoon. But that documentation step was the deciding factor in landing the migration without losing rankings. We knew exactly what existed, what it mapped to, and why, before a single redirect went live.
The real danger is redirect chains, not redirect count
Google's Search Central community guidance is specific about where quantity actually becomes a problem: redirect chains. A redirect chain happens when URL A redirects to URL B, which redirects to URL C, and so on. That's where SEO damage shows up, not simply from having a lot of 301s in place.
There's a second piece of this that most redesign guides skip entirely. Redirects increase crawl demand, because both the old URL and the new URL need to be crawled. Google's own community guidance confirms this directly, and it's the kind of detail that only shows up when you've actually mapped a full site rather than skimmed a template.
If your site has thousands of URLs and you're not careful, that extra crawl demand can starve other pages from getting crawled at all. That's a real cost of sloppy migration work, and it's rarely mentioned next to the usual "don't forget your sitemap" advice.
The rule that prevents the whole mess
Here's the single principle that saves you from most redesign disasters:
Preserve what ranks, improve what doesn't.
A redesign is not a reset. It's an upgrade. The pages that are already earning your traffic are doing their job. You don't tear them out. You keep them, redirect them cleanly, and make them look better while they keep working.
The pages that aren't ranking, those are the ones you can freely rethink, rewrite, or retire. The winners stay. The losers get rebuilt. That's the whole discipline, and it's the difference between a redesign that grows your business and one that sets it back a year.
Why this matters for your revenue
Here's the part that should make you careful.
Your rankings aren't a vanity metric. They're the pipeline that feeds your phone. Every page that ranks is a page that sends you customers, month after month, for free. That's an asset you've spent years building, and it compounds.
A redesign that deletes those pages isn't a cosmetic mistake. It's a revenue cut. You don't notice it in the design review, because the new site looks great. You notice it thirty days later, when the phone stops ringing and you can't figure out why the pretty new site is making less money than the ugly old one.
The businesses that redesign successfully treat their SEO equity like what it is: the most valuable thing on the site, and the thing that gets protected first.
The bottom line
A website redesign should make your site better, not make it disappear. The difference is entirely in the planning: audit what ranks, preserve it, redirect every URL, keep the content and structure that earned your traffic, and verify after launch.
The businesses that get burned are the ones who treated the redesign as a fresh start and threw away their winners by accident. The ones that win treat it as an upgrade and protect the pages that were already paying them.
I built WebCore to handle the migration layer by default, the redirects, the structure, the preserved ranking content, so a redesign improves your site instead of tanking it. If you'd rather hand the move over, we move your pages, copy and URLs onto WebCore for you: migration is $1,500 for the first 20 pages and $2,000 for every 20 pages after that.
Price your move in about 30 seconds → webcore.pro
Frequently Asked Questions
Will a website redesign hurt my SEO?
It will if you delete ranking pages, change URLs without 301 redirects, or strip the content that was earning traffic. Done right, with an audit and full redirect mapping, a redesign can improve your rankings instead of hurting them.
What's a 301 redirect and why does it matter?
A 301 redirect tells Google that a page has moved permanently to a new URL, and passes the accumulated ranking trust along. Without it, every old link and bookmark points to a 404, and that trust is lost.
Do I need to redirect every page or just the important ones?
Every page with traffic, links, or rankings. The ones that are earning your business are non-negotiable. Pages with no traffic and no links are lower risk, but the safe move is to map them all.
Should I keep the same URLs when I redesign?
Yes, keep them wherever you can. An address that doesn't change needs no redirect and loses nothing. Redirect only the URLs that truly have to move.
How long does a traffic dip last after a redesign?
A small dip while Google recrawls is normal. Google's site move guide says a medium-sized site can take a few weeks or more for the new URLs to replace the old ones in results. A sustained drop on particular pages points to a migration error, usually a missing redirect or deleted content.
Can I redesign and change my domain at the same time?
You can, but it doubles the risk. If both have to happen, map every old URL on the old domain to its new URL on the new one, submit a Change of Address in Search Console, and keep the redirects for at least a year.
What should I check in Search Console after launch?
The Pages report for 404s and redirect errors, the status of your new sitemap, and the Performance report page by page against your benchmark. Check daily in the first week, then weekly.
How much does it cost to have someone move my site without losing SEO?
With WebCore, we move your pages, copy and URLs for you: $1,500 for the first 20 pages and $2,000 for every 20 pages after that.