SEO & AI search

How to Redesign Your Website Without Losing Your Google Rankings

How to redesign a website without losing Google rankings: crawl first, map every URL to a 301, keep what ranks, avoid staging noindex traps, watch 8 weeks.

Sean Melton
November 17, 2026 · 14 min read
Share
Illustration of a browser window for a website redesign that keeps Google rankings in Houston and The Woodlands

The new site went live on a Monday. It looked great. By Thursday the office manager at a Woodlands service company noticed the phone was quiet, and by the next Monday the owner was in Search Console staring at a line that had fallen off a cliff.

Nothing was “wrong” with the new site. It just had different addresses. The old /ac-repair-spring-tx/ page that had ranked for six years now returned a 404, and so did forty other pages. Google had been sending people to rooms that no longer existed.

To redesign a website without losing your Google rankings, you crawl and record every URL on the old site, map each one to its closest new page with a permanent 301 redirect, and keep the titles, copy and structured data that were earning traffic. Make sure the live site isn’t carrying the staging site’s noindex, keep your analytics and conversion tracking intact, and watch Search Console closely for about eight weeks after launch.

The rest of this post is the detail, in the order we do it.

First, know which kind of change you’re making

“Redesign” covers a lot of ground. Google treats a new paint job very differently from a new domain, and the steps you need depend on which one you’re doing.

What’s changingExampleRedirects needed?Change of Address tool?
Design only, same URLsNew theme, same page addressesNo, but check nothing movedNo
Platform changeWix to WordPress, Squarespace to WebflowAlmost always (URL patterns differ)No
URL structure change/services/ac-repair/ becomes /ac-repair/Yes, every changed URLNo
HTTP to HTTPShttp:// to https://YesNo, Google detects it
New domainoldname.com to newbrand.comYes, every URLYes, for every variant

Google’s site move guide recommends changing only one thing at a time where you can. If you’re rebranding, moving domains and switching platforms in the same week, you lose the ability to tell which change caused a drop. We’d rather move the domain first and redesign a month later than do it all on one Saturday.

Google also suggests scheduling a move for a slower traffic period. For a Houston HVAC or roofing company, that means not launching in July or the week after a named storm. For a retailer, not in November.

If you’re still deciding whether you need a new site at all, our signs your website needs a redesign post is the place to start.

Before anyone touches the design: crawl and inventory

Most ranking losses we get called in to fix trace back to one missing spreadsheet. Nobody wrote down what the old site had before it was replaced.

Checklist of what to inventory before a website redesign to protect Google rankings in Houston and The Woodlands
One spreadsheet, filled in before design starts. It becomes your redirect map.

Here’s what goes into that spreadsheet:

  • Every URL on the old site. Run a crawler like Screaming Frog over the live site and export the list. Add URLs from the current XML sitemap too, since crawlers miss orphan pages.
  • Your top pages by search traffic. In Search Console, go to Performance, set the date range to the last 12 or 16 months, open the Pages tab and export. These are the pages you protect at all costs.
  • Top landing pages and conversions from GA4. Reports, then Engagement, then Landing page. A page that gets little traffic but produces half your form fills matters more than its traffic suggests.
  • Pages other sites link to. Your SEO tool’s backlink report, or Search Console’s Links report. Each linked page needs a redirect or you lose that link’s value.
  • Titles, meta descriptions, H1s and structured data for the top 50 pages. The crawler pulls these. Save them before the old site disappears.
  • PDFs, images that rank in image search, and any landing pages your ads point to.

Keep a full copy of the old site, or at least the crawl export, after launch. When something drops in week three, you’ll want to compare the before and after.

URL mapping and 301 redirects, done properly

Once you have the old URL list, every row gets a destination. Old URL in column A, new URL in column B, status in column C.

Old URLNew URLRule
/services/ac-repair-spring-tx//ac-repair/spring-tx/One-to-one, same topic
/blog/2019/05/hurricane-prep//blog/hurricane-prep-checklist/Updated post on the same topic
/heating-repair-conroe.html/heating-repair/conroe-tx/Platform change, same page
/specials-summer-2021/None (returns 410)Expired offer, no equivalent
/about-us/team/ and /about-us/history//about/Merged pages, closest match

The rules from Google’s site move guide:

  • Use permanent, server-side redirects (301 or 308). Google says permanent redirects don’t cause a loss in PageRank.
  • Redirect straight to the final page. Avoid chains like old URL to interim URL to new URL. If a chain can’t be helped, keep it short.
  • Don’t send everything to the home page. Google specifically warns against redirecting many old URLs to one irrelevant destination like the home page of the new site.
  • Let content you’ve truly dropped return a 404 or 410 rather than redirecting it somewhere unrelated.
  • Keep the redirects for as long as possible, generally at least a year.
Comparison of bad and good 301 redirect practices for a website redesign in Houston and The Woodlands
Based on Google’s site move guide and Google’s redirects documentation.

The redirect type matters. Per Google’s redirects documentation, Google follows a 302, but its indexing pipeline doesn’t treat a temporary redirect as a sign the new URL should be canonical, so the old URL can hang around in results. Instant meta refresh redirects are read as permanent, delayed ones as temporary, and JavaScript redirects are a last resort because rendering can fail.

Then test the map before launch. Load the old URL list into your crawler in list mode against the staging site (with redirects in place), and confirm every row returns a single 301 to a page that returns a 200.

Keep what was ranking: titles, content and schema

Redirects pass the signals. They don’t protect you if the page on the other end is a different page.

The quiet killer in redesigns is the copy rewrite. A designer “cleans up” the AC repair page from 1,100 words to 140 words and three icons, removes the Spring and Klein references because they looked cluttered, and changes the title tag from “AC Repair in Spring, TX | Same-Day Service” to “Comfort Solutions.” The redirect works perfectly. The rankings still go.

For every page on your protect list:

  • Keep the title tag and H1 close to what ranked, unless you have a reason backed by data to change them.
  • Carry the body copy over. You can tighten it and improve it. Don’t delete the sections that answered real questions.
  • Bring the structured data with you: LocalBusiness, Service, FAQ, Product, Review markup, whatever the old site had. Theme changes often drop it silently.
  • Keep image alt text and file names on images that brought traffic.
  • Keep the page in the navigation if it was in the navigation. A top page buried three clicks deep loses internal link weight.

Our local landing pages guide explains why those town-by-town pages carry so much of a Houston service company’s search traffic. They’re usually the first thing a redesign cuts and the last thing you want to lose.

The staging site trap: noindex, robots.txt and passwords

Every new site gets built somewhere first. That staging site should be invisible to Google, and the live site shouldn’t be. Both halves of that sentence go wrong more often than you’d expect.

The two common versions of this mistake:

  1. The staging site gets indexed. Someone forgets to hide it, Google finds it, and now you have a duplicate copy of your new site at staging.yourdomain.com or a developer’s preview URL. The best fix is a password on staging (HTTP authentication), which keeps everyone out, Google included.
  2. The noindex follows the site to production. WordPress has a “Discourage search engines from indexing this site” checkbox under Settings, then Reading. It gets ticked on staging and nobody unticks it at launch. Other platforms have their own version. The new site launches with a noindex tag on every page and starts falling out of Google within days.

There’s a subtler trap too. Per Google’s noindex documentation, a noindex only works if Google can crawl the page and see it. If robots.txt blocks a page, Google never reads the noindex, and the URL can still show up in results when other pages link to it. So “block it in robots.txt” isn’t a reliable way to hide staging, and a leftover “Disallow: /” in the live robots.txt is a launch-day disaster of its own.

On launch day, view the source of the home page and three inner pages and search for “noindex.” Open yourdomain.com/robots.txt and read it. It takes two minutes and it’s the check we never skip.

Change of Address in Search Console (domain moves only)

If you’re keeping your domain, skip this section. The Change of Address tool is only for moving from one domain or subdomain to another, per Search Console’s Change of Address help page. It isn’t for HTTP to HTTPS (Google works that out itself), for URL changes inside the same site, or for switching between www and non-www.

If you are moving domains, the steps:

  1. Verify both the old and new domains in Search Console with the same Google account. You must be an owner of both.
  2. Have your 301 redirects live, at minimum from the old home page to the new one, and ideally for every page.
  3. In the old property, open Settings, then Change of Address, pick the new property and submit.
  4. Repeat for every subdomain variant of the old domain. Google updated its site move guide on June 17, 2026 to say this includes www and non-www, even if you weren’t using one of them, according to PPC Land.

Google says the tool forwards signals for 180 days, and asks you to keep redirects at least that long, longer if Google still sends traffic to the old URLs. It also recommends keeping the old domain registered for at least a year. We’d keep it forever. A lapsed old domain can get bought by someone who points your old links at whatever they like.

Submit a fresh XML sitemap of the new URLs in Search Console on launch day. Google’s guide notes that warnings about redirects on an old-URL sitemap are expected, so don’t panic if you keep the old sitemap around for a few weeks to help Google find the redirects.

Internal links are the part teams skip because “the redirects will handle it.” They will, but every internal link that hits a redirect is a wasted hop and a sign of a sloppy site. Update menus, footers, buttons and body links to point at the new URLs directly. Then crawl the new site and filter for internal links returning 3xx or 4xx codes.

Also update the links you control off the site: your Google Business Profile website and appointment links, Facebook and Instagram bio links, Yelp, Nextdoor, BBB and industry directories, email signatures, and the final URLs in every Google Ads and Meta ad. Ads pointed at a 404 keep spending.

Core Web Vitals: don’t launch a slower site

New designs often arrive heavier than the old ones. Big hero videos, sliders, four web fonts, a chat widget and two tracking scripts that duplicate each other.

Core Web Vitals targets to check before launching a redesigned website in Houston and The Woodlands
Thresholds from Google’s Core Web Vitals page. Test the mobile tab in PageSpeed Insights.

Per Google’s Core Web Vitals page, the targets for a good experience are a Largest Contentful Paint within 2.5 seconds, an Interaction to Next Paint under 200 milliseconds and a Cumulative Layout Shift below 0.1. Google says it highly recommends site owners achieve good Core Web Vitals for success in Search. Even apart from rankings, a slow site loses calls because people leave.

Test the staging site in PageSpeed Insights on the mobile tab before launch and compare it with the old site. If the new one is slower, fix it before launch rather than after. The usual culprits are an uncompressed hero image, lazy-loading the image at the top of the page, and third-party scripts loading before the content. Our page speed guide goes deeper.

Tracking and GA4 continuity

A redesign that keeps its rankings but breaks its tracking still costs you, because for the next two months nobody can tell whether the new site is working.

  • Keep the same GA4 property and measurement ID. Don’t create a new property for the new site. You lose the year-over-year comparison you’ll want in week four.
  • Rebuild every key event. If “generate_lead” fired on the old thank-you page and the new form shows an inline message instead, the event stops firing and your lead count drops to zero overnight.
  • Check Google Ads conversions separately. Many accounts import from GA4, some use the Google tag directly, and some use both. Submit a test lead and confirm it shows up in both places.
  • Carry over call tracking numbers. Dynamic number insertion scripts often don’t make it into new templates.
  • Keep Search Console verified. If verification relied on an HTML file or meta tag on the old site, it can disappear with the old theme.

Add a GA4 annotation on launch day so everyone reading reports later knows what happened. Annotations arrived in GA4 in March 2025: right-click a point on a line chart and choose Add annotation, which needs Editor access, per PPC Land’s write-up of GA4 annotations.

Our guide to tracking forms and calls in GA4 and Google Ads has the setup step by step.

Launch-day checklist

Launch on a Tuesday or Wednesday morning, with the developer and whoever owns SEO both available for the rest of the week. Never on a Friday afternoon.

Six-step website launch day checklist for keeping SEO rankings after a redesign in Houston and The Woodlands
The first two steps catch most of the disasters we see.

Run the old URL list through the crawler against the live site within the first hour. Every row should be a single 301 to a 200 page. Anything else gets fixed that day. Google tends to crawl a moved site more heavily than usual right after the move, so the first few days are when broken redirects do the most damage. Google’s own guide says to make sure your server can handle the extra load.

Then use URL Inspection in Search Console on the home page and your five most important pages, and request indexing. It won’t make Google move faster across the whole site, but it confirms the live pages are crawlable and indexable.

The 8 weeks after launch: what to watch

Launch is the middle of the project. The next eight weeks decide whether it worked.

Timeline of what to monitor in Search Console and GA4 for eight weeks after a website redesign in The Woodlands
Most problems show up in the first two weeks, when they’re cheapest to fix.
  • Daily for the first week: Search Console’s Pages report for new “Not found (404)” and “Excluded by noindex” entries, and GA4 for leads and calls compared with the same weekdays before launch.
  • Weekly through week four: Search Console Performance, comparing clicks and impressions for your protect-list pages against the four weeks before launch. Check that the new URLs are appearing in results and the old ones are fading out.
  • Weeks four through eight: rankings for your money keywords, Core Web Vitals field data as it builds up, and backlinks still pointing at old URLs.
  • Any week: if a specific page drops hard while others hold, compare it with the saved copy of the old page. It’s almost always missing content, a changed title or a missing redirect.

How big a dip to expect, and how long recovery takes

Some wobble is normal. Google’s site move guide says to expect temporary fluctuation in rankings during a move, and that a medium-sized site can take a few weeks or more for Google to start showing the new URLs instead of the old ones, with larger sites taking longer. Every URL on both the old and new site has to be crawled at least once for the move to finish.

Google people have given ranges over the years. Gary Illyes said at SMX Advanced in 2017 that a domain move can take two weeks for some sites and closer to three months for larger ones, as reported by Search Engine Roundtable. John Mueller said in 2021 that Google recommends keeping redirects at least a year so it can be sure they’ve been seen a few times, per Search Engine Journal.

Illustrative chart of organic traffic after a website redesign with complete 301 redirects in Houston and The Woodlands
Illustrative only. Your site’s curve depends on its size and how cleanly the move was done.

From the redesigns we’ve worked on and the broken ones we’ve been brought in to repair, our experience is this. A same-domain redesign with a complete redirect map and preserved content usually wobbles for a couple of weeks and settles. A redesign without a redirect map doesn’t recover on its own, because nothing is wrong from Google’s point of view; the old pages are simply gone. Fixing the redirects late helps, but you’re rebuilding from a lower starting point. We can’t promise a number for your site and nobody honest can.

If traffic is still down 20% or more on your protect-list pages at week six, stop waiting and go page by page. Our troubleshooting guide for sites missing from Google covers the checks.

Who should do this work

A good web designer can build a beautiful site and still have no idea any of this exists. Before you sign a redesign contract, ask who builds the redirect map, who carries over the content and schema, who checks tracking at launch and who watches Search Console for the eight weeks after. If the answer to all four is a shrug, budget for someone who does it.

Our team handles redesigns and migrations under web design and SEO, with the SEO work built into the plan from the first meeting rather than bolted on at launch. If you’re weighing the cost, our website cost guide and SEO pricing guide lay out typical ranges. And if your designer is holding the old site hostage before you can even start, read our companion post on getting your website and domain back from a web designer.

If you’re planning a redesign and want it done without the Thursday-morning panic, get in touch and tell us what you’re changing.

Frequently asked questions

Will redesigning my website hurt my SEO?

It can, but it doesn’t have to. Rankings usually drop after a redesign because URLs changed without 301 redirects, ranking content was cut, title tags changed, or a staging noindex tag went live. If you map every old URL to its closest new page, keep the content and structured data that ranked, and check tracking and indexing at launch, most sites see only a short wobble before settling.

How long should I keep 301 redirects after a redesign?

Google’s site move guide says to keep redirects as long as possible, generally at least one year. For a domain move, Search Console’s Change of Address help says to keep them at least 180 days and longer if Google still sends traffic to the old URLs. In practice we leave them in place indefinitely, since they cost almost nothing and old links keep working.

Do I need to use the Change of Address tool for a redesign?

Only if you’re moving to a new domain or subdomain. Google says the Change of Address tool isn’t for HTTP to HTTPS moves, URL changes within the same site, or switching between www and non-www. If you’re moving domains, verify both properties, set up 301 redirects, and submit the change for every variant of the old domain, including www and non-www.

How long does it take to recover rankings after a website migration?

Google says a medium-sized site can take a few weeks or more for the new URLs to replace the old ones, and larger sites take longer. A Google spokesperson once described the range as two weeks to about three months. A migration done with complete redirects usually settles within weeks. One done without redirects often doesn’t recover until the missing redirects and content are restored.

What is the most common mistake in a website redesign?

In our experience it’s launching without a redirect map, so every old URL that ranked now returns a 404. A close second is the staging site’s noindex setting carried over to the live site, which tells Google to drop every page. Both are quick to check on launch day: crawl the old URL list against the new site, and search the page source for noindex.

Sean Melton
Written by

Sean Melton is the founder of First Byte, a digital marketing agency in The Woodlands, TX. A former global CMO of a $250M software company, he has spent his career inside the businesses he markets. His team runs paid social, search, CTV and creative for brands like Equinox, Kroger and Viceroy, and shares what works here.

Let’s talk

Want results like these?

Tell us a little about your business and what you need. We never clock out — and neither should your marketing. Expect a reply within an hour or two, 7 days a week.

(713) 578-0634
Call nowGet in touch →