How to Redesign Your Website Without Torching Your Google Rankings

Last spring, I got a call from a small business owner a few weeks after his new website launched.

The redesign looked great. Professional photography, custom animations, cleaner branding. They’d invested a lot into it.

The problem was that his phone had slowed to a crawl. One of the pages that had been generating leads for years had quietly disappeared from Google’s search results. When he asked the web design company what happened, he was told that “rankings naturally fluctuate after a relaunch” and that things would settle down.

I don’t think this was gross negligence. It was a process problem. The redesign moved forward without an SEO migration plan. URLs changed, redirects weren’t mapped, and some of the site’s strongest pages quietly disappeared from search.

The business owner never saw any of it coming. He wasn’t a marketer or an SEO, and he barely spent time on a computer beyond what he needed to run his company. Like a lot of small business owners, he hired a web design company because he trusted them to handle the technical details he didn’t know to ask about. That’s a completely reasonable expectation.

If you’re in the market for a new website, you don’t need to become an SEO expert. You do need to understand what your current website may already be doing well, what can be lost during a redesign, and the questions your web team should be able to answer before anything goes live.

Redesigns don’t kill rankings. A short list of preventable mistakes does.

The five things that actually tank your rankings

You don’t need to know how to fix every one of these yourself. That’s what you’re hiring a web team for. But you should understand what they are, because these are the mistakes that most often turn a successful website redesign into months of lost traffic and leads.

1. Your URLs change and nothing redirects them. Fifteen years of links, bookmarks, and Google’s trust all pointed at /services/roofing/. Now that page lives at /what-we-do/roofing-services/ and the old address goes nowhere. Much of the authority that page built over the years can be lost.
2. Important content gets removed because it “looks cluttered.” Those 900 words may be a big part of why the page ranked in the first place.
3. Important elements like title tags and page headings get rewritten during the redesign. Those are ranking signals, not just layout decisions. Changing them without understanding how the page currently performs can cost you rankings you spent years earning.
4. The staging site’s noindex tag ships to production. The site may look perfect while still telling Google not to index it. The opposite can happen too, where the staging site gets indexed and competes with the real one.
5. The new site is slower than the old one. A heavier page builder, giant hero video, and unnecessary plugins can all hurt performance if nobody considers their impact before launch.

None of these problems are caused by good design. They happen when the technical side of a redesign isn’t planned with the same care as the visual side.

Before redesigning anything, understand what you already have

Before anyone starts redesigning your website, someone should understand what’s already working.

Which pages bring in leads? Which pages rank well? Which ones have earned links over the years? That’s the baseline you want to protect during a redesign.

A good web team should know these things before they begin redesigning your site:

• Crawl the whole current site. Screaming Frog or Sitebulb can export every URL, title tag, meta description, H1, and status code. This gives you a complete inventory of the current site before anything changes.
• Review your top-performing pages in Google Search Console. Identify the pages that already bring in the most clicks and impressions from Google. Those are the pages your web team should be protecting during the redesign.
• Identify the pages that generate leads, not just traffic. A page with 200 visits and 12 inquiries is often far more valuable than one with 4,000 visits and none.
• Review your backlinks. Pages with valuable links from other websites have earned authority over time and deserve extra attention during a redesign.
• Document where your most important keywords rank today. Date the report and save it somewhere you’ll be able to find after launch.

You don’t necessarily need to collect this information yourself. But you should know that someone has.

If your web team hasn’t reviewed your rankings, top-performing pages, backlinks, and conversions before redesigning the site, they’re making important decisions without knowing what’s already working.

The redirect map matters more than the mockups

Behind every successful website migration is a redirect map. Most business owners never see it, but they should know it exists.

It’s usually a simple spreadsheet with one row for every page on your existing website. Each old URL is matched with the page that will replace it after launch.

You don’t need to build this spreadsheet yourself. Your web team should. But it’s worth asking if one exists, who’s responsible for it, and whether it’s been tested before launch.

Old URL	New URL	Type	Monthly clicks	Backlinks	Done?
/services/roofing/	/roofing/	301	410	18	Yes
/blog/old-post-name/	/blog/new-post-name/	301	95	3	Yes

Every redirect plan should follow a few basic rules:

• Send every URL to its closest match. The new page should cover the same topic and serve the same basic purpose. Redirecting a pile of retired pages to the homepage may confuse search engines and creates a frustrating experience for visitors.
• Use 301s for permanent moves. A 301 tells search engines that the page has moved for good. A 302 signals that the move is temporary. Google’s documentation explains the difference, and this is worth confirming with your web team.
• Avoid redirect chains. If A once redirected to B and B now redirects to C, point A directly to C. Chains add unnecessary complexity and can make migrations harder to troubleshoot.
• Keep the redirect map after launch. If questions come up months or years later, it provides a record of where every old URL was supposed to go.

Google publishes a detailed site move guide for URL changes. It’s worth reviewing before approving a new URL structure. Better yet, avoid changing URLs that don’t need to change. Every unnecessary URL change creates another redirect that has to be planned, tested, and maintained.

Not everything needs to change

One of the biggest misconceptions about a website redesign is that everything has to change. It really doesn’t. Some of the most successful redesigns completely transform how a website looks while preserving the pages, content, and signals that have already earned Google’s trust.

Usually preserve	Redesign freely	Review first
URL structure	Layout and visual hierarchy	Navigation labels and site structure
Title tags on pages that rank	Photography and illustration	Merging several pages into one
H1s on pages that rank	Colors and typography	Blog categories and tags
High-performing page content	Button design and CTA placement	Adding JavaScript-heavy components
Internal links to key pages	Form styling	Rewriting copy on pages that rank
Existing structured data (schema)

The goal isn’t to preserve everything. It’s to understand what’s already working before you change it.

Sometimes your services change, your messaging evolves, or your business takes a different direction. That’s exactly when content should change. The key is making those decisions intentionally instead of changing things simply because the website is being redesigned.

A redesign should improve the experience without throwing away the pages, content, and technical signals that helped people find your business in the first place.

“Cleaner” is not the same as “less”

This is one of the most common mistakes I see during redesigns.

A designer opens your service page, sees 1,200 words of dense text, and reasonably concludes that it looks like a wall. The new version ships with 300 words and a lot more breathing room. It may look much better, but it may no longer rank nearly as well because much of the depth Google was rewarding has disappeared.

The goal isn’t to keep the wall of text. It’s to preserve the substance while improving how it’s organized and presented: clear subheads, comparison tables, shorter paragraphs, useful bullet points, and an FAQ where it makes sense.

If a section genuinely no longer belongs on that page, it may deserve a page of its own. Just make sure the decision is based on what helps the business and the reader, not simply on making the design look cleaner.

Launch day: the boring stuff that matters

Your web team should verify all of these before announcing the new site:

1. Confirm that the production site is indexable and that the staging noindex setting wasn’t carried over.
2. Check robots.txt to make sure the live site isn’t accidentally blocking search engines.
3. Test a representative sample of redirects, prioritizing your highest-traffic, highest-converting, and most-linked pages.
4. Generate a fresh XML sitemap containing only live URLs. Submit it through Google Search Console and Bing Webmaster Tools.
5. Confirm that canonical tags point to the live website and not back to the staging site.
6. Verify that GA4, conversion tracking, and every lead form are working on the live site.
7. Make sure your Google Business Profile, directory listings, and any running ads point to URLs that still exist.
8. Crawl the live site and fix any significant 404 or 500 errors before announcing the launch.
9. Turn on ongoing 404 monitoring, because even well-planned migrations can miss a few URLs.

You don’t need to sit beside the developer while every item is checked. But you should receive confirmation that the important launch checks were completed.

The first 90 days: don’t panic, and don’t panic-revert

Some movement after launch is normal while Google recrawls the website. Rankings may shift during the first few weeks, and larger migrations can take longer to settle.

That doesn’t mean the new site should be launched and ignored. Someone should be watching closely enough to tell the difference between normal fluctuation and an actual migration problem.

During that stretch:

• Watch the Pages report in Search Console for a growing “Not found (404)” count. That’s often a sign that the redirect map needs attention.
• Compare performance page by page, not just sitewide. A stable overall traffic number can hide the fact that an important service page has lost most of its visibility.
• Do not panic-revert in week two. Undoing everything while Google is still recrawling the site creates a second migration on top of the first one.
• Don’t launch during a broad core update. Check the Google Search Status Dashboard before setting a launch date. Launching during a major update can make it difficult to separate the impact of the redesign from changes in Google’s algorithm. We wrote about navigating a core update previously, and the same basic advice applies: wait for the rollout to finish before making another major change.

Before hiring a company, ask how long post-launch monitoring is included and who you should contact if an important page loses visibility. Waiting for you to notice a problem isn’t the same as actively monitoring the migration.

What about AI search?

AI search tools are changing how people discover websites, but they still rely on individual pages they can crawl and understand. If a redesign changes or removes those pages without a plan, existing visibility and citations can be disrupted just like traditional search rankings.

Two things still matter:

• Crawlable, stable URLs. Getting cited starts with being findable. If an important URL changes, the old address should lead cleanly to the correct new page.
• Existing structured data. If your current website uses schema markup, it should be reviewed and carried into the new templates wherever it still applies.

Beyond that, use descriptive headings, answer important questions clearly, and organize the page so both people and search systems can understand it.

Nothing about “optimizing for AI” requires you to buy a new tool. It’s the same technical SEO work that has always mattered.

The questions I’d ask before hiring a web design company

Before you fall in love with the mockups, ask who’s responsible for protecting everything your current website has already earned.

Who will review the existing site before design begins? Who owns the redirect map? Who reviews changes to pages that already rank or generate leads? Who tests the live site after launch? Who watches Search Console afterward, and for how long?

Also ask who will actually be doing the work. Are the people you meet during the sales process the same people who will build and launch the site, or will the project be handed to someone you never speak with? If an important page loses visibility in week three, are you calling someone who knows the project or opening a general support ticket?

Most business owners never think to ask these questions, and I don’t blame them. The owner who called me had hired professionals precisely because he didn’t know what could go wrong behind the scenes.

That’s often the difference between a redesign that builds on what you already have and one that quietly starts over. Someone needs to understand what your existing pages, rankings, links, and leads are worth—and remain responsible for protecting them through launch and afterward.

That’s also why we handle WordPress maintenance and support ourselves instead of handing it off once a site goes live.

Questions I get asked constantly

Will a website redesign hurt my SEO?

Not on its own. Rankings usually drop when URLs change without redirects, valuable content gets cut, or title tags and page headings are rewritten with no strategy behind them. A redesign that protects the parts of the current site that already perform well can maintain its rankings and sometimes improve them.

How long until my rankings recover after a redesign?

Some movement during the first few weeks is normal while Google recrawls the site. How long it takes to stabilize depends on the size of the website and how much changed. If an important page still hasn’t recovered after several weeks, your web or SEO team should investigate rather than simply continuing to wait.

Should I keep my old URLs?

Yes, wherever it reasonably makes sense. The safest redesign is one where good existing URLs don’t change unnecessarily. Every URL that does change creates another redirect your web team has to implement, test, and maintain.

Should I use 301 or 302 redirects?

In most website redesigns, permanent URL changes should use 301 redirects. You don’t need to configure them yourself, but you should confirm that your web team is using permanent redirects and testing them before launch.

Can I change my page titles during a redesign?

You can, but be selective. If a page already ranks well, understand what its existing title is doing before rewriting it. Ask your team to identify which pages already perform well rather than changing every title simply because the site is being redesigned.

Should I launch during a Google core update?

Generally, no. If a broad core update is actively rolling out, waiting until it finishes makes it much easier to separate the impact of your redesign from changes in Google’s algorithm.

Will a nicer design by itself boost my rankings?

Rarely, and not directly. A redesign can help through faster load times, a better mobile experience, clearer internal linking, and better-organized content. A beautiful website with thin content and a weak technical foundation may still underperform a simpler site that handles those fundamentals well.

How do I tell if my redesign hurt me or an algorithm update did?

Check the timing against confirmed Google update dates, then look at which pages were affected. Redesign problems are often concentrated around specific URLs, missing redirects, or technical errors. Algorithm updates tend to affect a broader group of pages. Search Console and a fresh crawl of the website should help your web or SEO team identify the difference.

Do I need to rebuild my site to show up in AI search?

No. The same fundamentals that help pages rank also help them get discovered and cited: crawlable URLs, useful content, clean structured data, and clear organization. If someone is selling you an “AI optimization” rebuild, ask what specifically is broken on your current website first.

Go forth and redesign responsibly

A redesign should make your website better looking and better performing. Those two goals aren’t in conflict. When design and SEO do end up working against each other, it’s usually because they weren’t planned together from the beginning.

As the business owner, you shouldn’t have to manage that coordination yourself. You should be able to trust the company you hired to identify what’s worth protecting, explain the important decisions in plain language, and flag risks before they become expensive problems.

At 1Brand, we’ve been rebuilding websites for Chicago businesses and companies well outside Chicago since 2009. We start planning the migration while we’re still working through the site structure and design, long before anything goes live. Because we handle both the redesign and migration planning, the technical work isn’t treated as an afterthought.

Take a look at some of our recent work or reach out and let’s talk about what you’ve got.