All articles

How to Redesign Your Website Without Losing Your Google Rankings

VenbitThe Venbit TeamJune 24, 20269 min read

The short answer

Redesigns kill rankings when teams forget to preserve URLs, redirect old pages, and keep the content that was already ranking. Do the inventory first, keep your URLs wherever possible, redirect the ones you change, don't throw away ranking pages, and watch Search Console hard after launch.

Key takeaways

  • Audit your current rankings before you touch anything. You can't protect what you haven't mapped.
  • Keep existing URLs wherever possible. Every URL change is a risk, even with a proper 301.
  • Set up 301 redirects for every URL that changes. A broken redirect is a dead ranking.
  • Do not delete or gut pages that are bringing in traffic. Rewrite them, don't replace them with blank stubs.
  • Check Search Console daily for two to four weeks after launch and fix any 404s fast.

A website redesign is one of the highest-risk moments in your business's digital life. At Venbit, a web design and SEO studio based in Mill Creek, Washington, we've guided clients through redesigns both here in the Puget Sound area and across the US and Canada, and the pattern we see is always the same: get it right and you come out with a faster, better-converting site that keeps all its rankings. Get it wrong and you can watch years of SEO work disappear in the first week after launch. The difference almost always comes down to preparation, not the design itself.

Step 1: Inventory your current pages and rankings before you touch anything

This is the step most teams skip, and it's the one that costs them. Before a single wireframe gets drawn, you need to know exactly which pages are ranking, what they're ranking for, and how much traffic they're bringing in. You cannot protect what you haven't mapped.

  • Pull a full list of your URLs from Google Search Console or a crawl tool like Screaming Frog.
  • Export your top queries and the pages they point to from Search Console (Performance report).
  • Note which pages bring in the most organic traffic. These are your non-negotiables.
  • Flag any pages that rank for specific long-tail or local terms, even if the traffic volume is modest. Those terms may be driving your best leads.
  • Save screenshots of your current ranking positions for key terms. You'll want a before-and-after reference after launch.

This inventory is your redesign contract with yourself. Everything on that list needs to be accounted for in the new site, one way or another.

Step 2: Keep the same URLs wherever possible

Every URL change is a ranking risk. Even a perfect 301 redirect passes most, but not all, of the ranking signal from the old URL to the new one. There's always some loss. So the safest move is to keep your URLs exactly the same when you redesign. If your service page lives at /plumbing-services today, it should live at /plumbing-services on the new site.

The most common mistake is switching URL structures because the new CMS or platform works differently. A developer might default to a different slug format, or someone decides to "clean up" the site architecture mid-project. These decisions feel minor at the time and can cost you months of ranking recovery.

Step 3: Set up 301 redirects for every URL that changes

Sometimes URL changes are unavoidable. A platform migration might force a new structure. An old URL might be genuinely confusing or wrong. When that happens, a 301 redirect is the only acceptable solution. It tells Google that the page has permanently moved and passes the ranking credit to the new address.

  1. 1Build a redirect map: a spreadsheet with the old URL in one column and the new destination in another. Every old URL that is changing needs a row.
  2. 2Implement all redirects before launch, not after. Launching and then adding redirects later means your pages are effectively dead for however long it takes you to notice.
  3. 3Test every redirect before you go live. A common failure is redirect chains, where old URL A goes to old URL B which goes to new URL C. Flatten them so each old URL points directly to its final destination.
  4. 4Check for redirect loops. These break the page entirely and Google will just drop it.
  5. 5Do not redirect everything to the homepage. If your old /about-us page is being replaced, redirect it to the new /about page, not to the root domain. A redirect to the homepage sends a confusing signal.

Step 4: Preserve the content on pages that are ranking

This is the one that hurts the most to watch. A business gets a shiny new design, the designer wants clean pages with minimal text, and the result is that every ranking page gets stripped down to a headline and a button. The rankings disappear within weeks.

Google ranks pages partly because of the content on them: the text, the headings, the specifics. If your old /hvac-repair page had 800 words covering the exact services, the areas you serve, and answers to common questions, those 800 words are doing work. Replacing them with a hero image and two sentences is not a refresh. It's a demolition. We've seen this happen to businesses from Bellevue to Boston, and the recovery process is the same painful slog every time.

  • Keep your page titles and H1 headings consistent if the keyword targeting was working.
  • Preserve or improve the body content on ranking pages. If you want a cleaner look, work with a designer who understands that content and design have to coexist.
  • Don't delete pages that rank just because they feel old. Update them. Redirect them to a newer, richer version. Do not simply remove them.
  • If you're consolidating pages, redirect the old ones to the best surviving equivalent and make sure that destination page covers the topics the old one did.

Step 5: Keep your site fast, or make it faster

Page speed is a ranking factor, and redesigns are notorious for adding weight. New themes come with full-page animation libraries. New hero sections use large unoptimized images. A plugin gets added for a feature no one uses. Before you know it, your site that loaded in 2 seconds now loads in 6, and your Core Web Vitals score drops into the red.

Test your new site's speed in staging before you ever launch it. Use PageSpeed Insights and compare the scores to your current live site. If the scores are worse, find out why and fix it before launch. A redesign that makes your site slower is not an improvement.

Step 6: Do not block search engines at launch

This one sounds obvious, and yet it happens constantly. Developers build the new site behind a staging environment with a robots.txt file that blocks all crawlers. It's the right move while you're building. Then launch day arrives, the developer flips the domain, and nobody remembers to update the robots.txt. Google is now blocked from crawling the entire new site.

The same thing happens with noindex tags. A template or plugin adds a noindex header to every page while the site is in development. It's perfectly fine in staging. Catastrophic if it goes live.

Item to checkWhat you're looking forHow to check
robots.txtNo Disallow: / rule blocking all crawlersVisit /robots.txt directly after launch and read it
Noindex tagsNo pages accidentally set to noindexCrawl with Screaming Frog or check Search Console coverage
Redirect mapEvery old URL that changed has a working 301Test each redirect with a browser or redirect checker tool
Page speedNew site scores as well as or better than the old siteRun PageSpeed Insights on the live domain within an hour of launch
SitemapNew sitemap is generated and submitted to Search ConsoleSubmit via Search Console Sitemaps report
Canonical tagsPages are not accidentally canonicaling to staging or the wrong URLView page source and look for rel=canonical in the head
AnalyticsTracking is firing correctly on the new siteCheck real-time view in GA4 immediately after launch
Launch-day checklist: what to verify before you go live

Step 7: Submit your new sitemap and watch Search Console hard after launch

Once the site is live, submit the new sitemap in Google Search Console under the Sitemaps report. This isn't a magic fix, Google crawls on its own schedule regardless, but it signals that the site has changed and prompts a fresh crawl.

Then watch Search Console daily for at least two to four weeks after launch. You're looking for two things: a spike in 404 errors and a drop in impressions or clicks. A spike in 404s means your redirect map has gaps. Find the missing redirects and add them fast. A drop in impressions can indicate crawling or indexing problems, content loss, or slow re-crawling of redirected URLs.

  1. 1Check the Coverage report for new "Not found (404)" errors every day for the first two weeks.
  2. 2Check the Performance report weekly. Compare clicks and impressions to the same period before launch.
  3. 3If you see a sharp drop in a specific page's impressions, pull up that page and verify the content, redirect, and indexability.
  4. 4If organic traffic drops significantly and doesn't recover within four to six weeks, it's time to do a deeper audit. Check for content loss, redirect chains, and crawl issues.

Do this, not that: common redesign mistakes and the right alternative

Instead of thisDo this instead
Launching on the new platform and figuring out redirects laterBuild the full redirect map and implement it before launch day
Deleting old blog posts or service pages that feel outdatedUpdate the content on ranking pages, or redirect them to a richer replacement
Stripping page content down to match a minimal designKeep the ranking content and design around it, not instead of it
Switching URL structures to match the new platform's defaultsOverride the defaults to preserve existing URLs, even if it takes extra setup
Forgetting to check robots.txt and noindex settings at launchMake "verify crawl access" item one on the launch-day checklist
Assuming the redesign will be fine and checking analytics a month laterWatch Search Console daily for the first two to four weeks after launch
Redesign SEO: what to do vs. what to avoid

The honest reality: most redesign ranking drops are avoidable

The businesses we've seen lose rankings after a redesign almost always lost them for the same avoidable reasons: no redirect map, gutted content, or an accidental crawl block that nobody caught. It's rarely something exotic. The fix is preparation and a checklist, not a 10-step recovery plan six months later.

If you're planning a redesign and you're not sure whether your current site has rankings worth protecting, pull up Search Console now. Look at the Performance report. If you're getting any organic clicks at all, those clicks came from somewhere, and that somewhere is worth knowing about before your developer starts building. Whether your business is in Seattle, Chicago, or anywhere else in North America, the stakes and the process are the same.

The best time to audit your current rankings is before the redesign starts. The second-best time is right now, before you go any further.

Planning a redesign? Let's protect your rankings first.

Before you hand off to a designer, we'll audit what your current site is ranking for and build a redirect and content plan that protects every position. Whether you're in the Seattle area or running a business anywhere in the US or Canada, the process is the same and it starts before the first wireframe. No guesswork, no surprises after launch.

Venbit

The Venbit Team

Web design & SEO, Seattle

Venbit is a Seattle-area web design, SEO, and digital marketing studio. Since 2011 we've designed, built, and ranked small-business websites for clients across the Puget Sound and around the country, so the numbers and advice here come from real projects, not a content mill.

Sources

Common questions

Questions, answered straight.

Straight answers about guides for your business. If yours isn't here, ask us directly and we'll give it to you straight.

Ask the team

It can, but it doesn't have to. Redesigns hurt rankings when teams change URLs without redirects, remove ranking content, accidentally block search engines, or launch without testing. If you inventory your rankings first and follow a proper redirect and content preservation process, most of the risk is manageable.

Free 30-minute strategy call

Let's talk about your project.

Tell us what you need and we'll give you an honest read on the project, the timeline, and what it takes, before you spend a dollar. Based in Seattle, working across the Puget Sound.

4.8 on Google 5.0 on Yelp