How to redesign a website without losing your Google rankings

The short answer

You can redesign a website without losing SEO if you treat it as a move, not a makeover. Record your current traffic and rankings, list every URL that earns visits or links, map each one to its new page, keep the content that ranks and add one-to-one 301 redirects. Then check indexing on launch day and watch Search Console for about 30 days.

On this page

Most rankings lost in a redesign are lost for dull, preventable reasons. A page moved and nobody told Google, a setting from the test site went live, or a page that brought in leads was cut because it looked cluttered. The new design is rarely the problem. The move is.

This guide is the method I use, in the order I use it. It is also the process behind my website redesign service, which starts at $2,500.

Why rankings drop after a redesign

Search results list individual pages, not whole websites. Each page has its own address, its own content and its own history of links from other sites. A redesign can break any of those, often without anyone noticing until the phone goes quiet.

  • Changed URLs with no redirects. The new site uses /services/ where the old one used /our-services.html. Google, and every site that linked to you, still points at the old address, which now shows "page not found."
  • Removed or thinned content. A detailed page gets cut to three lines and a stock photo because it "looked busy." Those words were the reason it ranked.
  • Lost internal links. Pages drop out of the menu and footer with nothing else linking to them, yet Google uses links "as a signal when determining the relevancy of pages and to find new pages to crawl."
  • Staging settings left on. A noindex tag, a robots.txt file that blocks everything, or a password from the test site ships with the live site.
  • Canonical mistakes. A canonical tag tells Google which address is the preferred version of a page. If new pages still point to the staging domain or to old URLs, you are telling Google the real page lives elsewhere.
  • Slower or less crawlable pages. Heavier themes and scripts can make pages slow on phones. Menus built with buttons instead of real links can hide pages, because Google can generally only crawl a link that is an HTML <a> element with an href.
  • Domain or protocol changes. Moving from http to https, from www to non-www, or to a new domain changes every URL at once, and each one needs a redirect.

None of these is a design decision. A careful plan catches all of them before launch.

How to redesign a website without losing SEO, in order

SEO people call this a website migration, and the order matters because each step feeds the next:

  1. Benchmark the current site.
  2. List every URL and mark what earns traffic, leads and links.
  3. Map every old address to a new one.
  4. Carry over the content that ranks.
  5. Set up and test 301 redirects.
  6. Keep staging private.
  7. Run launch-day checks.
  8. Monitor for about 30 days.

Benchmark everything before you touch the site

You can't tell whether a redesign hurt you unless you know exactly where you started. Before any design work, take a snapshot of the current site and save it somewhere it won't change.

  • Search Console. In the Performance report, set the date range to at least the last 12 months and export the queries and pages tables. This shows which pages get clicks, and for which searches.
  • Analytics. Record organic visits and, more important, conversions (calls, forms, bookings) for each landing page. A quiet page that produces half your leads matters more than a popular post that produces none.
  • A full crawl. Run a crawler such as Screaming Frog over the whole site. It gives you a reference copy of every URL, title, heading and status code.
  • Key rankings. Note where you appear for the 10 to 20 searches that matter most to the business.

List every URL and mark what earns its keep

Combine those sources into one spreadsheet with one row per URL. Pull addresses from the crawl, the XML sitemap, the Search Console export and your analytics landing pages. Each source finds pages the others miss, especially old pages that left the menu years ago but still get visits from Google.

For each URL, add its clicks, its conversions, its backlinks (how many other websites link to it, from a backlink tool) and its fate: keep, merge or retire.

Any page with real clicks, conversions or links is a page you protect. It keeps its content, gets a clear new home and gets a redirect if its address changes. Pages with no traffic, no links and no business purpose are the ones you can safely merge or retire.

Build a URL map from old pages to new pages

The URL map is the heart of a safe redesign: every old URL on the left, the single best new URL on the right. Google's site move documentation puts it simply: "It's important to map your old site's URLs to the URLs for the new site."

Here is a small slice of one for a law firm:

Old URLNew URLWhy
/our-services.html/services/Same page, cleaner address
/practice-areas/dui/practice-areas/dui-defense/Same topic, clearer name
/blog/2019/after-an-arrest/guides/after-an-arrest/Article moved to guides
/free-consultation-2018/contact/Old campaign page merged
/about//about/Unchanged, no redirect needed

The rules I follow when filling it in:

  • Keep URLs the same wherever you can. The safest redirect is the one you never need.
  • If several old pages are combined into one new page, they can all point to it. Google allows this when content has genuinely been consolidated.
  • Update internal links so the new site links straight to new URLs. Google's checklist includes changing "the internal links on the new site from the old URLs to the new URLs."

Keep and improve the content that ranks

A redesign is a good time to rewrite weak pages, but pages that already rank need a lighter touch. They rank because their words answer what people search for. Moving those words into a new layout is fine. Cutting them for more white space is one of the most common ways to lose a ranking.

For each protected page, I check that:

  • The topic and main heading stay the same, and the title tag and meta description are carried over or improved, not reset to a template default.
  • The sections that answer the searches in your Search Console export stay. Tighten the writing if you like, but keep what people found you for.
  • Alt text, useful in-text links and structured data (business details, FAQs, breadcrumbs) are rebuilt on the new templates.

If a page earns traffic but converts poorly, improve it rather than replace it. You keep what it already earns and get more from it.

Set up one-to-one 301 redirects

Every row in your map where the address changes becomes a redirect: a server instruction that says "this page has moved, go here instead." Visitors land on the right page, and Google can carry what it knew about the old URL over to the new one.

Use permanent redirects. Google recommends "HTTP permanent redirects if possible, such as 301 and 308," and its redirects documentation explains why: a permanent redirect shows the new page in search results, while a temporary one keeps showing the old page.

  • One to one. Each old page goes to its closest new equivalent. Google is explicit: "Don't redirect many old URLs to one irrelevant single URL destination, such as the home page of the new site." It warns this "might be treated as a soft 404 error," meaning Google may treat the redirect like a missing page.
  • No chains. If an old URL already redirects from a previous redesign, point it straight at the final page. Google advises "redirecting to the final destination directly" and keeping chains short, "ideally no more than 3 and fewer than 5."
  • Server-side. Set redirects on the server or host, not with JavaScript. Google recommends "a permanent server-side redirect whenever possible."

On Netlify, redirects live in a plain text file called _redirects. Each line is an old path, a new path and a status code, and Netlify uses 301 when no code is given. Here is the map above as that file:

# Old path                     New path                         Status
/our-services.html             /services/                       301
/practice-areas/dui            /practice-areas/dui-defense/     301
/blog/2019/after-an-arrest     /guides/after-an-arrest/         301
/free-consultation-2018        /contact/                        301
A Netlify _redirects file built from the URL map: each old address points to one matching new page with a permanent 301.

On Apache, the same rule is one line in .htaccess: Redirect 301 /our-services.html https://www.example.com/services/. Whatever the platform, run the old URLs through a redirect checker and confirm each returns a single 301 to a page that loads normally.

How long to keep redirects in place

Longer than you would think. Google says: "Keep the redirects for as long as possible, generally at least 1 year." Its reason is that this timeframe "allows Google to transfer all signals to the new URLs, including recrawling and reassigning links on other sites that point to your old URLs." I treat them as permanent. They cost nothing to keep, and old links in emails, directories and bookmarks keep working.

Protect the staging site, then unlock it at launch

While the new site is being built, it lives at a test address called staging. Google should not find it, or half-finished pages can appear in search next to your real ones.

Google notes that "some site owners block all crawling while in development," and asks you to plan what robots.txt and any noindex rules should look like once the move starts. I prefer a password on the whole staging site. It keeps out search engines and curious visitors alike, and it is obvious on launch day if it is still on.

The two other common methods each have a catch:

  • Noindex. A tag such as <meta name="robots" content="noindex"> tells Google to drop the page "entirely from Google Search results." Copied to the live site by accident, it removes the pages you most want found.
  • A robots.txt block. Search Console's help notes this "does not guarantee that the page won't be indexed through some other means." It also hides any noindex tag: if a page is blocked by robots.txt, "the crawler will never see the noindex rule."

Launch-day checks for a website redesign

Launch day is when the risk becomes real, so I work through a short website redesign SEO checklist in the first hour:

  1. robots.txt. Open yourdomain.com/robots.txt and confirm there is no blanket Disallow: / left from staging.
  2. Noindex removed. Check the source of the home page and your top 10 pages for any noindex tag or header.
  3. Canonicals. Each page's canonical should point to its own new, live URL, as Google's site move guide asks.
  4. Redirects live. Test old URLs from the map, starting with those that earned the most traffic and links.
  5. Sitemap submitted. Submit the new sitemap.xml in Search Console. Google's guide also has you submit a sitemap of the old URLs during the move, and says warnings about them redirecting are normal.
  6. Change of Address, only if the domain changes. Moving to a new domain? Use the Change of Address tool in Search Console. Google says not to use it for http to https moves, www and non-www switches, or moving pages within the same site.
  7. Forms and analytics. Submit every form, check the message arrives, and confirm analytics records the conversion.
  8. Speed on a phone. Test key pages on mobile in PageSpeed Insights. Google's Core Web Vitals guidance asks for the main content to load within 2.5 seconds, an INP below 200 milliseconds and a CLS below 0.1.

These sit inside a longer list I run on every project. My new website SEO checklist has the full 20 checks.

Watch the first 30 days and fix drops early

Even a clean move causes some movement. Google is direct about it: "Expect temporary fluctuation in site ranking during the move." For medium-sized sites, "it can take a few weeks or more for Google to gradually start showing the new URLs," and larger sites can take longer.

For about 30 days I check these, several times in the first week and then weekly, so real problems are caught early:

  • Page indexing report. Watch for a rise in pages listed as not found (404), excluded by noindex or blocked by robots.txt. Google's help is plain: "If your page has moved, use a 301 redirect to the new location."
  • Performance report. Compare clicks and impressions for top pages and searches with your benchmark. Old URLs should fade as new ones pick up impressions.
  • Rankings and leads. Recheck your 10 to 20 key searches, and compare calls, forms and bookings from search with the weeks before launch.

If something drops

Find the specific pages that lost clicks in Search Console, then check each one in this order:

  1. Does the old URL redirect, in one hop, to the right new page?
  2. Is the new page indexable, with no noindex, no robots.txt block and a canonical pointing to itself?
  3. Was content cut? Compare it with your crawl of the old site and restore it.
  4. Did it lose internal links from the menu, footer or related pages?
  5. Is it slower on a phone than the old version?

Fix the cause, then request indexing for the most important pages with the URL Inspection tool. Fix clear errors at once, but avoid rewriting pages or changing URLs again while things settle. If someone else's relaunch has already gone wrong, a speed and technical SEO sprint is the quickest way I know to find and fix indexing problems.

When a redesign is worth doing at all

A redesign carries real risk, so it should have a real reason. In my view it is worth doing when:

  • The site is hard to use on a phone, or slow enough that people leave.
  • It no longer matches the business: new services, new markets or a higher price point.
  • Visitors arrive but don't call, book or fill in forms, and smaller fixes have not helped.
  • You can't add service pages or fix technical problems without paying a developer every time.

It is usually not worth it when the only complaint is that the site feels dated to you, or when traffic is growing and leads are steady. Then targeted work tends to beat starting over.

If you do go ahead, the planning comes first. In my seven-step process, the keyword and page plan is approved before any design starts, and that is when the URL map is settled too. By the time the new design exists, every page has a job and every old address has a destination.

More questions

Should I change my domain name at the same time as the redesign?

Ideally not. Google's site move guidance says to change one thing at a time, for example moving to the new domain first and changing the layout afterwards. If both happen at once and traffic drops, you can't tell which change caused it. If the domain must change, redirect every old URL and use the Change of Address tool in Search Console.

Can I change my URL structure during a redesign?

Yes, if the new structure is genuinely clearer and every changed URL gets a one-to-one 301 redirect. Changing URLs adds work and some risk, so I only do it where it helps visitors or the page plan, such as grouping all services under /services/. Aim for short, readable, lowercase addresses you won't need to change again.

Does switching platforms, for example WordPress to Webflow, affect SEO?

The platform matters less than what changes with it. Google lists a CMS change as one of the changes to plan separately from others. Each platform has its own URL habits, templates and settings, so treat a switch like any other move: map URLs, carry content over, rebuild titles and structured data, then check speed.

My new site already launched and traffic dropped. Can I still fix it?

Often, yes. Set the Search Console Performance report to dates before launch to find the old URLs that earned clicks, then add 301 redirects to their closest new pages and restore any content that was cut. Check noindex tags, robots.txt and canonicals at the same time, because one stray setting can affect the whole site.

Sources

  1. How to move a site (site moves with URL changes), Google Search Central
  2. Redirects and Google Search, Google Search Central
  3. Change of Address tool, Search Console Help
  4. Block Search indexing with noindex, Google Search Central
  5. Page indexing report, Search Console Help
  6. SEO link best practices for Google, Google Search Central
  7. Understanding Core Web Vitals and Google search results, Google Search Central
  8. Redirect options, Netlify Docs

Keep reading

Tell me about your website

A 20-minute video call, no slides and no pressure. Bring your current site or your plan, and you'll leave with the three changes I'd make first, whether or not we work together.

Chat