How do you redesign a website without losing SEO rankings?

You redesign a website without losing SEO rankings by keeping the URLs, copy, titles and internal links that earn traffic today. Every URL that does change gets a 301 redirect to its new page. Test the new templates for speed and mobile content before launch. Then make sure crawlers can reach the live site on day one and watch Search Console weekly for two months.

Website redesign SEO goes wrong in five common ways. URLs change with no redirect, copy gets cut to fit a cleaner layout, menu links disappear, a staging block stays in place at launch, or pages get heavier. Each one has a check that catches it before launch.

On this page

• How a website redesign affects SEO
• Record your SEO baseline before the redesign starts
• Protect the pages that already rank
• Plan URL changes and 301 redirects
• Keep internal links and the menu structure
• Keep the staging site out of Google, then let Google in
• Check page speed and Core Web Vitals on the new design
• Technical tags and data to carry over
• Launch-day website redesign SEO checklist
• What to monitor in the first 60 days

How a website redesign affects SEO

Google re-crawls a redesigned site and judges it again on what it finds. A new color scheme on the same URLs and copy changes little. A new URL structure, merged pages or a new platform changes almost everything Google knows about the site. Match your safeguards to the size of the change:

Some movement is normal even when the work is done well. Google's site move guide, updated in August 2026, tells site owners to expect temporary ranking changes during a move. Shopify SEO strategist Greg Bernhardt gives a benchmark in Shopify's guide to website redesign SEO. He puts a 0% to 20% change in organic traffic in the first month as common, and treats a 60% drop by day six as a sign of a real problem.

Record your SEO baseline before the redesign starts

Save these six records before a designer opens a file. They show what the redesign must protect, and they are the only way to prove afterwards what changed:

• A crawl of every live URL with its status code, title tag, meta description, H1, canonical tag and word count.
• Twelve months of the Search Console Performance report, exported by page and by query.
• Conversions by landing page from Google Analytics 4, so you can rank pages by leads and sales as well as visits.
• The pages that earn backlinks, from Search Console's Links report or a backlink tool.
• Core Web Vitals field data for your main templates: home page, service or category page, product page and blog post.
• A saved copy of each top page's text, so nobody has to rewrite it from memory.

From those records, list your top 50 pages by clicks and by conversions. That list becomes the protected set for every design decision and the test list on launch day. A crawl also shows existing problems, such as redirect chains or orphan pages, and the technical SEO audit checklist covers what else to look for.

Protect the pages that already rank

Design teams cut copy to make pages look cleaner, and the cut copy can be the reason the page ranked. For each page on the protected list, keep the URL, title tag, H1 and main body text. Change them only for a reason you can tie to search data. Move long text into tabs or accordions if the design needs space.

Check the mobile version with the same care. Google's mobile-first indexing documentation says Google uses the mobile version of a site's content for indexing and ranking. Content that the new design hides or removes on phones stops counting, even if desktop visitors still see it. The same page asks for equivalent titles, meta descriptions and structured data on both versions.

Change one thing at a time on top pages. When the URL, copy and template all change in one week, a ranking drop has three possible causes. Nobody can tell them apart. Launch the new design with the old copy, then rewrite in batches once traffic settles.

Plan URL changes and 301 redirects

The safest URL is the one that does not change. Hold on to the existing structure wherever the layout allows it. Map every URL that does change to the one new page that covers the same topic. Then redirect it with a permanent server-side redirect.

Google's redirect documentation recommends server-side 301 or 308 redirects whenever possible. It treats JavaScript redirects as a last resort, because Google might never see one if rendering fails. Keep redirects for at least one year, as the site move guide advises. Update your own internal links too, so visitors do not pass through a redirect on every click.

Say an accounting firm in Austin has 85 indexed URLs before its redesign. Sixty keep their URLs. Nine service pages merge into three, and 16 blog posts move from dated paths to /resources/. The redirect map has 25 rows. Each merged service page points to the new page that covers the same service, never to the home page.

A redesign that also moves platform, such as WooCommerce to Shopify, changes almost every URL at once. The WooCommerce to Shopify migration guide shows how to build that larger map from a crawl.

Keep internal links and the menu structure

Internal links tell Google which pages matter most. The main menu, footer, breadcrumbs and in-text links all count. A redesign that trims the main menu from 12 items to 6 cuts links to six pages from every page on the site.

• Compare the old and new menus side by side. Keep every page on the protected list within two clicks of the home page.
• Recreate in-text links from blog posts and service pages, since they are easy to lose when content moves into new templates.
• Check that menus render as plain HTML links. A menu built only in JavaScript can hide links from crawlers.
• Run a crawl of the staging site and list pages with no internal links pointing to them, then fix each one.

Keep the staging site out of Google, then let Google in

An indexed staging site puts a second copy of your pages in search results. A staging block left on the live site does the opposite and keeps Google out. Password protection is the cleanest way to block staging, because it stops both crawling and indexing. A noindex tag also works, but Google's noindex documentation says the rule works only if robots.txt does not block the page.

Launch day is where this goes wrong. Teams copy the staging setup to production, including a robots.txt that disallows everything or a sitewide noindex tag. The site move guide also says to remove any robots.txt blocks that were only needed during development. Put that check first on the launch list, before the redirect tests.

Review the new robots.txt for AI crawlers as well. If the old file allowed search crawlers from OpenAI, Google or Perplexity and the new one blocks them, your pages can drop out of those AI answers. The guide to llms.txt covers the related file some sites add.

Check page speed and Core Web Vitals on the new design

New designs add weight: larger images, web fonts, sliders and scripts. Test each template on staging against the thresholds Google publishes on web.dev. Largest Contentful Paint should land within 2.5 seconds, Interaction to Next Paint at 200 milliseconds or less, and Cumulative Layout Shift at 0.1 or less. Google measures them at the 75th percentile of real page loads, split by mobile and desktop.

Staging tests use lab data, while Google ranks on field data from real Chrome users, so recheck after launch once real visits arrive. The Core Web Vitals guide explains how to fix a slow LCP, a laggy INP or a jumping layout. Accessibility checks belong in the same pass, and the ADA compliance guide lists what to test.

Technical tags and data to carry over

Templates get rebuilt from scratch, and the tags inside them are easy to drop. Confirm each of these on staging for every template:

• Title tags and meta descriptions, copied from the old pages for every protected URL.
• Canonical tags that point to the page itself, not to the staging domain.
• Structured data such as Organization, LocalBusiness, Product, Article and FAQ markup.
• Hreflang tags, if the site serves more than one language or country.
• Image alt text and descriptive file names on images that rank in image search.
• An XML sitemap that lists the new URLs and only pages that return a 200 status.
• Analytics, Google Ads conversion tags and form tracking on every template.

Validate structured data with Google's Rich Results Test before launch. The schema markup guide shows what each type needs.

Launch-day website redesign SEO checklist

Run these checks in order, within the first hour after the new site goes live:

1. Confirm the live robots.txt allows crawling and that no page carries a stray noindex tag.
2. Test the redirects for your top 50 pages. Then crawl the full list of old URLs and confirm each returns a single 301 to a live page.
3. Crawl the new site and fix any 404s, redirect chains and canonical tags pointing to staging.
4. Submit the new XML sitemap in Search Console.
5. Use the URL Inspection tool on the home page and five top pages, and request indexing.
6. Place a test lead or order and confirm analytics and conversion tags record it.
7. Add an annotation in your reporting with the launch date, so later comparisons start from the right day.

If the domain changed, add the Change of Address request in Search Console. Google says the tool is needed only for moves between domains or subdomains, and not for HTTPS or URL-path changes.

What to monitor in the first 60 days

Check four numbers every week and compare each against the baseline:

• Clicks and impressions for the top 50 pages in Search Console.
• New entries in the Not found (404) and Redirect error rows of the Pages report.
• Conversions by landing page in Google Analytics 4.
• Core Web Vitals field data for each template once enough real visits arrive.

A dip in the first two to four weeks is expected. A drop that keeps growing after week four points to a missing redirect, a blocked page or deleted copy. So does a page that loses most of its clicks overnight. The traffic drop diagnosis guide walks through the checks in order.

Your first step costs nothing: run the crawl and export the Search Console data this week, then build the protected list of top 50 pages. The website design and development team and SEO team at Techno Mantra plan redesigns around the pages that already rank. They work with US businesses, plus clients in Canada and Australia. Send your current site URL through the Techno Mantra contact page or to info@technomantraa.com. Every inquiry gets a reply within one business day.