How to redesign a website
without losing SEO.

Most website redesigns lose organic traffic, and almost none of them lose it because Google decided it liked the old design more. They lose it because pages that quietly earned clicks for years got new URLs with no redirect, got merged into a thinner page, or got cut altogether because nobody checked what they were earning. The good news is that every one of those causes is preventable with a checklist and a bit of discipline, and a redesign done properly usually ends up gaining traffic, because the new site is faster, cleaner and easier to crawl. Here is the process we run when we rebuild a website that already ranks.

Key takeaways

• Crawl and export the old site before anyone designs anything. You cannot protect what you have not inventoried.
• Keep URLs where you can. Where you cannot, map every old URL to one new URL and 301 it. No blanket redirects to the homepage.
• The pages that rank need their titles, headings, copy, images and internal links carried over, not reinvented.
• Staging must stay out of the index, and the noindex must come off on launch day. Both mistakes are common.
• Launch is the start of the job, not the end. Watch Search Console daily for the first month and fix 404s and drops as they appear.

Step 1: Inventory what you have before you touch anything

A redesign starts with a spreadsheet, not a mockup. Before the design brief is written, you need to know every URL on the current site and what each one is worth.

• Crawl the live site with a tool like Screaming Frog and export every URL, its title, meta description, H1, canonical, status code and word count. This is your baseline.
• Pull 12 months of Search Console data by page: clicks, impressions, top queries. Pull the same from Analytics. Now you know which pages actually earn traffic and which ones nobody visits.
• Pull your backlinks by page. A page with external links pointing at it is an asset even if it gets little traffic today.
• Note the technical setup: sitemaps, robots.txt rules, structured data, hreflang if you run multiple languages, and any redirects already in place from previous redesigns.

This inventory is what every later decision is checked against. A page that gets 400 clicks a month does not get cut because it does not fit the new nav.

Step 2: Decide what to keep, merge and cut, on purpose

With the inventory in front of you, every existing page gets one of three labels.

Decision	When	What happens to the URL
Keep	The page earns traffic, links or conversions	Stays at the same URL, or 301s to its one new equivalent
Merge	Several thin pages cover one topic	All of them 301 to the single stronger page
Cut	No traffic, no links, no purpose	301 to the closest relevant page, or 410 if nothing fits

Two rules keep this honest. First, nothing with meaningful traffic or links gets cut without a redirect. Second, the decision is written in the spreadsheet next to the URL, so when the new site is built, the map already exists.

Step 3: Keep the URLs, or map every change

The single highest-leverage move in a redesign is keeping URLs the same. A page that keeps its address keeps its backlinks, its internal links and everything Google has learned about it. Changing a URL, even to a nicer one, resets some of that and depends on the redirect to carry the rest.

When URLs do have to change (a platform move, a genuinely bad old structure, a new language setup), build the redirect map one row at a time:

• One old URL to one new URL. The new page should be the closest equivalent in topic, not just the nearest category.
• Never redirect everything to the homepage. Google treats mass redirects to the homepage as soft 404s, and the link value does not carry.
• Use 301s, not 302s. Permanent redirects pass authority; temporary ones hedge.
• Avoid redirect chains. If the old site already redirected A to B, and now B becomes C, point A straight at C.
• Include everything. Images, PDFs and old campaign landing pages count too, especially if anything external links to them.

Load the whole map into the new site’s redirect layer before launch and test a sample of it on staging.

Step 4: Carry the content over, not just the design

A redesign is a design project, so content gets treated as the stuff that goes in the boxes. That is where rankings leak. A page ranks because of its title, its headings, its copy and the links pointing at it, and a redesign that “freshens” all of that at once gives Google a different page at the same address.

For every page in the keep column:

• Title tag and meta description carry over, or improve in a way that keeps the target keyword.
• H1 and heading structure stay equivalent. Designers love turning an H1 into a decorative div. Do not.
• The body copy keeps its depth. Trimming an 1,800-word guide to three punchy paragraphs because it looks cleaner is how you lose the long-tail queries that page earned.
• Images keep descriptive filenames and alt text, and ideally keep their paths or get redirected.
• Internal links are rebuilt. New nav and new templates usually drop a lot of the contextual links the old site had, and those links are part of why pages ranked.
• Structured data moves across. If the old site had FAQ, product or article schema, the new one should too.

You can absolutely improve copy during a redesign. Just do it page by page against the old version, not as a blank-page rewrite.

Step 5: Keep staging out of Google, and then let the new site in

Two opposite mistakes, both common.

Staging gets indexed. The new site sits at a staging URL for weeks, nobody blocks it, and Google indexes a duplicate of your whole site. Protect staging with password access or a noindex header, and ideally both.

The noindex ships to production. The site launches with the staging noindex still in place, or robots.txt still blocking everything, and rankings fall off a cliff over the following week. This is the most expensive single checkbox in the whole process.

Launch-day technical checklist:

• Noindex removed, robots.txt allows crawling, canonicals point to the live domain.
• Redirect map live and spot-tested.
• New XML sitemap generated and submitted in Search Console. Old sitemap removed or replaced.
• Analytics, Search Console and tag manager verified on the new site.
• HTTPS everywhere, with www and non-www resolving to one version.
• Core pages load fast on mobile. A redesign that doubles page weight is a redesign that loses rankings slowly.

Step 6: Crawl again, then watch for a month

Once the site is live, crawl it exactly as you crawled the old one and compare the two exports. You are looking for 404s, pages that lost their title or H1, pages that dropped to a handful of words, orphan pages with no internal links, and redirect chains.

Then watch Search Console daily for the first few weeks:

• Pages report: new “Not found (404)” entries are missing redirects. Fix them the day they appear.
• Performance report: compare clicks and impressions by page against the pre-launch baseline. A short dip is normal. A page that drops and stays down needs a look.
• Crawl stats: a spike is expected as Google recrawls; a collapse means something is blocked.
• Core Web Vitals: make sure the new build did not regress what the old one had.

If traffic is still down after six to eight weeks, the cause is almost always in that list: a missing redirect, a page that lost its content, a block on crawling, or a lost set of internal links. It is rarely mysterious.

Only use Change of Address if the domain changes

Redesigning on the same domain needs no special signal to Google beyond a new sitemap and a clean redirect map. The Change of Address tool in Search Console exists for one case: moving to a new domain. If that is part of your project, run it after the redirects are live, and keep the old domain redirecting for years, not months.

The redesign checklist

Keep this next to the project plan.

1. Crawl and export the old site: URLs, titles, headings, canonicals, status codes, word counts.
2. Pull 12 months of Search Console and Analytics data by page, plus backlinks by page.
3. Label every URL keep, merge or cut, with the decision written down.
4. Keep URLs wherever possible. Map every change one to one and use 301s.
5. Carry titles, headings, copy depth, images, internal links and schema over for every kept page.
6. Protect staging with a password or noindex, and remove the noindex on launch.
7. Launch-day checks: robots, canonicals, redirects, sitemap, analytics, HTTPS, speed.
8. Crawl the new site and compare against the baseline.
9. Watch Search Console daily for 30 days and fix 404s and drops immediately.

That list is not complicated, but it does need to be owned by someone who cares about the rankings as much as the design, and in most redesigns that person does not exist, because the designer, the developer and the SEO are three different vendors who never met. That is the fragmentation problem in a nutshell, and it is exactly why we run design, build and SEO as one connected team. If you are planning a rebuild, our website development services handle the redesign with the SEO checklist built in, and the same crew that does SEO keeps watching the rankings after launch. Book a call and we will start with the crawl, or see pricing to find the plan that fits.