How to redesign a website without losing SEO

When a new website loses Google traffic, the new colors and fonts are rarely to blame. The damage tends to come from old addresses that stop working, a test-site setting that goes live, or a page Google ranked rewritten into something shorter. Most of it can be prevented before launch.

One honest caveat: if your site gets little search traffic, redirect the pages people actually visit and launch. The rest of this is for sites where Google already sends calls or sales you would miss.

A redesign is a risk even when no URL changes

Google’s John Mueller said Google does not change a site’s ranking just because it was revamped, but advised keeping the URLs, internal linking, and page content and layout “the same as much as possible,” according to Search Engine Journal (July 2021). Google’s Gary Illyes was blunter: “when you redesign a site, its rankings in search engines may go nuts,” according to Search Engine Roundtable (January 2023).

Google reads your HTML, not your mockups. It builds the title link in results from your title tag, the main heading and other page text, according to Google’s title link documentation (updated December 2025). Change those and you change what shows in search.

So take your top handful of pages by clicks and give them a do-not-touch list for launch:

• The title tag
• The H1 and H2 headings
• The main body copy, especially the part that answers what people searched
• The internal links pointing to the page

Improve them later, one page at a time.

Change one thing at a time

Google’s guide to site moves with URL changes (updated August 2026) says to “plan your changes to your site one after the other, not everything at the same time.” Its own example puts the domain move first and the new layout after.

Don’t switch platform, URL structure, domain and copy in the same launch week. Moving from Wix or WordPress to a custom build? Keep the old URLs if you can. If the new platform forces a different format (.html endings, trailing slashes, a /blog/ prefix), match the old one or redirect every address that changes.

Step 1: Inventory every old URL

The same guide says “it’s important to map your old site’s URLs to the URLs for the new site,” and suggests building the list from your sitemaps, from server logs or analytics for your highest-traffic URLs, and from Search Console’s Links report.

Then add two sources that are easy to miss:

• Search Console’s Performance report, by page. Pick the longest date range it offers, sort by clicks and export it.
• Addresses you have published off-site. The website and booking links in your Google Business Profile, ad landing pages, directory listings such as Yelp or Angi, email signatures, and QR codes on flyers, vehicle wraps and business cards. Print cannot be updated, so those redirects must last as long as the print does.

Include embedded files too: Google lists videos, images, JavaScript and CSS.

Save the list somewhere that outlives the old site. It is also on our list of what a website needs before launch.

Step 2: Build the 301 redirect map

The map is a spreadsheet: old URL in one column, new URL in the next, each going to the closest equivalent page. Google’s rules:

• Use permanent, server-side redirects. The site-move guide recommends “HTTP permanent redirects if possible, such as 301 and 308.” Google’s redirects documentation (updated April 2026) says a permanent redirect shows the new URL in results, while a temporary 302 or 307 keeps the old one showing. JavaScript redirects are a last resort.
• No chains. “Avoid chaining redirects.” Googlebot can follow up to 10 hops, but the guide advises sending each old URL straight to its final page.
• Don’t send everything to the homepage. Google warns against redirecting many old URLs to “one irrelevant single URL destination, such as the home page of the new site,” and says this might be treated as a soft 404. If several old pages were merged into one new page, redirecting them there is fine. A retired page with no real equivalent should return a 404 or 410. Already-indexed URLs that return a 404 or 410 are removed from the index, according to Google’s HTTP status codes page (updated February 2026).
• Keep them for at least a year. Google says “for as long as possible, generally at least 1 year.” If the domain changes, keep the old one registered, because its redirects stop working the day it lapses. Leaving Wix or Squarespace means the redirect rules live on the new host, so make sure someone owns that job.

Step 3: Rebuild without dropping what ranks

Faster and cleaner is a good goal, not a reason to delete content that brings calls.

• Mobile is the version Google reads. Google’s mobile-first indexing guidance (updated December 2025) says to “make sure that your mobile site contains the same content as your desktop site.” A mobile layout that trims text and headings, or loads content only after a tap, changes what gets indexed.
• Real links, pointing at new URLs. Google’s link best practices (updated December 2025) say Google crawls ordinary HTML links (an anchor element with an href) and “every page you care about should have a link from at least one other page on your site.” The site-move guide adds that internal links should use the new URLs and each new page should carry a canonical tag pointing to itself.
• Structured data comes along, and stays honest. Carry existing markup into the new templates. Google’s structured data guidelines (updated July 2026) say it “must be a true representation of the page content.” Check it with the Rich Results Test and URL Inspection.
• Speed matters, but less than relevance. Google’s Core Web Vitals page (updated December 2025) sets “good” targets of LCP within 2.5 seconds, INP under 200 milliseconds and CLS under 0.1. But its page experience documentation (updated September 2026) says Google “always seeks to show the most relevant content, even if the page experience is sub-par.” If speed is the main reason for the redesign, fixing a slow website may not need a rebuild at all.

Step 4: Staging and launch day

Staging has a trap on each side of launch.

Before launch, keep it out of Google properly. A robots.txt Disallow does not do it. Google’s robots.txt guide (updated December 2025) says: “To keep a web page out of Google, block indexing with noindex or password-protect the page.” And noindex only works if robots.txt does not block the page, because Google has to crawl it to see the tag, according to Google’s noindex documentation (updated December 2025). A password is simplest.

At launch, take it all off. Google’s site-move guide lists this among common mistakes: “Don’t forget to remove any noindex or robots.txt blocks that were only needed for the migration.” On launch day, check that robots.txt does not say Disallow: /, that no page you want found carries noindex, and that the sitemap and canonical tags use the live domain, not the staging one. Then submit the new sitemap in Search Console. Google’s sitemap documentation (updated July 2026) says to list absolute canonical URLs, and that “submitting a sitemap is merely a hint.”

Don’t wait for traffic to reveal a stray noindex. Google’s guide to debugging traffic drops (updated December 2025) says a misplaced noindex causes a slower drop, because it depends on Google crawling each page, so it is easy to miss. Run URL Inspection’s “Test live URL” on the homepage and top pages on launch day instead.

Then test what Search Console cannot see. A redesign can break analytics, conversion tracking or form delivery, and the drop in leads gets blamed on Google. Send a test request and confirm it arrives and registers as a conversion. If form emails have ever gone missing, why contact form leads go to spam covers the fix.

After launch: a normal dip or a real problem?

Some movement is expected. Google’s site-move guide says “a small to medium-sized website can take a few weeks for most pages to move, and larger sites take longer.” The traffic-drop guide calls small position changes normal and saves concern for “a dramatic, persistent drop in position.”

A rough way to read the first weeks:

• Early on: positions swing as Google recrawls old and new URLs. Watch, don’t rewrite.
• After a few weeks: on a small site, most pages should have moved and numbers should be settling.
• Red flags at any point: new URLs that stay unindexed; jumps in “Not found (404)”, “Soft 404” or “URL marked noindex” on pages you meant to keep; “Couldn’t fetch” in the Sitemaps report; repeated server errors; site-wide impressions that fall and stay down.

In the Page indexing report, old URLs marked “Page with redirect” are expected, and the report’s help page (undated, checked October 2026) says “Don’t expect every URL on your site to be indexed.” Filter it by your new sitemap to see how many new URLs are indexed, as the Sitemaps report help page (undated, checked October 2026) describes.

Compare year over year to rule out seasonality, and check whether a Google update landed in the same weeks. If the drop does not fit the redesign pattern, why your Google ranking dropped walks through the other causes in order.

Write it into the contract

Redirects are easy to leave out of a quote because nobody notices them until they are missing. Ask for these in writing: the redirect map as a file you keep, a crawl of the old site before launch and the new one after, Search Console checks in the months after launch, and the domain, hosting and analytics in your name.

If you want a second pair of eyes

Planning a redesign and want someone to check the redirect map, or wondering whether a post-launch dip is normal? Send us the details. Maxverse Lab replies within 24 hours, quotes a fixed price in USD, and on anything we build you own the domain, hosting and code, with every login handed over. If your current developer already has this covered, you do not need us.