A redesign usually starts with the question "how do we make it look better?" A better place to start is a different one: what's working on the current site that we must not break. A refreshed site that loses half its search traffic after launch is a common story, and the cause is almost never the design. It's that page URLs changed during the move, copy disappeared, or sections got blocked from indexing.
Below: how to tell whether a redesign is really needed, how it differs from building a new site, which stages to go through, and what to do to keep your search rankings.
When you need a redesign: signs it's time
"The site looks dated" isn't reason enough. A dated look annoys the owner, but customers may not care. Good reasons for a redesign are the ones you can see in the numbers or in how the sales team works.
- The mobile version is hard to use. Tables run off the edge of the screen, buttons are tiny, forms can't be filled out on a phone. Meanwhile, analytics shows that a large share of visitors come from mobile.
- Conversion is falling or lags behind other channels. There's traffic but few leads. Session recordings show people don't reach the form or abandon it.
- The site doesn't reflect the business. The company has grown, added new lines of business, changed its positioning, and the site still describes who you were three years ago. New services have to be squeezed into the old structure.
- Every change goes through a developer. Swapping a banner or adding a page means filing a ticket with a programmer. The admin panel is awkward or doesn't exist.
- Slow loading. The site takes a long time to load, especially on mobile data, and that affects both visitor behavior and search.
- Sales reps explain to customers what the site should be explaining. If sales keeps sending out a PDF deck because "the website isn't clear," the site isn't doing its job.
- The brand identity has changed. There's a new logo and visual language, but the site is still in the old one.
Redesign or a new site
The word "redesign" gets used for very different jobs, and the budget and risks depend on which one you mean.
Visual refresh
The visual layer changes: typography, colors, grid, illustrations, components. The structure, page URLs, CMS and most of the content stay. This is the safest option for search and the fastest. It fits when the site's logic is sound and the problem really is the look or the brand identity.
Redesign with UX rework
The section structure, user flows and key pages are rebuilt. Some pages are merged, some are created from scratch. This usually includes reworking the mobile version. Here, serious work on preserving traffic is already required.
A new site
Everything changes: structure, content, the technology platform. For example, moving from a homegrown system to a modern stack or to a traditional CMS. Technically it's a new project, and in this case it's easier to rebuild the site from scratch than to patch the old code. For search, it's the riskiest option, because everything the search engine relies on changes at once.
| Visual refresh | Redesign with UX | New site | |
|---|---|---|---|
| What changes | The visual layer | Structure, flows, key pages | Everything, including the platform |
| What stays | Structure, URLs, CMS, most content | Some pages and content | — |
| Risk to search | Lowest | Noticeable; traffic preservation work needed | Highest |
| When to choose | Logic is sound, the problem is the look | The problem is logic and flows | The old platform blocks growth |
How to choose: if the core of the site (CMS, front end, speed) is fine and the problem is perception, a visual refresh is enough. If the problem is in the logic and user flows, you need a redesign with UX. If the old platform holds you back and every change is expensive, it's more honest to build a new site, but migrate it by the book.
The stages of a redesign
- Audit of the current site. Analytics: where people come from, which pages bring traffic and leads, where people leave. Search: which pages are indexed, which queries they rank for, which backlinks point to them. UX: where flows break, what's awkward on mobile. Technical audit: speed, errors, CMS.
- Goals and scope. What should change and how we'll measure it: form conversion, the share of mobile leads, time to update content. This is also where you write down what must not change.
- Structure and prototype. A new sitemap informed by the audit. The key rule: pages that bring traffic and leads don't disappear without a replacement.
- Design. Concept, mockups, UI kit, responsive layouts.
- Development on a staging domain. The new version is built on a subdomain blocked from indexing, content is migrated, and redirects are set up.
- Pre-launch checks. The SEO checklist (below), plus testing forms, analytics, speed and rendering on devices.
- Launch and monitoring. The switchover, an indexing check, and monitoring traffic and errors in the first weeks.
How to redesign a website without losing traffic
A search engine doesn't rank "the site in general." It ranks specific pages at specific URLs with specific content. Anything that changes in that combination is a risk. The goal is to change things deliberately.
Collect a full list of URLs before work begins
Export every page that's in Google's index, in the sitemap, in analytics and in the CMS. Mark the ones that bring traffic and leads, and the ones with backlinks pointing to them. This is the redesign's master document: later, it's how you verify nothing got lost.
Keep URLs wherever possible
The best redirect is the one you never needed. If a page stays the same in substance, keep its old URL, even if a new one would look tidier. Change URLs when there's a real need: old URLs with parameters, duplicates, illogical nesting.
Set up 301 redirects page by page
Every page whose URL changes needs a permanent 301 redirect to the new page closest in meaning. If a page has no equivalent, pick the nearest section, or deliberately return a 404 or 410 if the page is no longer needed. Check that there are no redirect chains (A → B → C) or loops.
Carry over meta tags and headings
Move the title, description and H1 of well-ranking pages over unchanged, or change them carefully and with purpose. A new designer often shortens headings "to look cleaner" and deletes the key phrases along with them.
Keep the content
The most common cause of a drop after a redesign is missing copy. The old category page had a detailed description, and in the new minimalist design only two sentences survived. Or the copy got hidden in a tab loaded by a script. If the copy was working, it should stay on the page and be accessible without extra clicks.
The best redirect is the one you never needed.
Check the technical side
Before the switchover, go through the ranking-preservation checklist:
- the staging domain is blocked from indexing, and that block is removed on production: a forgotten robots.txt disallow or noindex meta tag after launch wipes out traffic;
- the sitemap.xml is updated and contains only new, working URLs;
- canonical tags point to the right pages, not to the staging domain;
- structured data has been carried over: breadcrumbs, products, organization, FAQ;
- internal links point directly to the new URLs, not through redirects;
- analytics tags and goals work on the new site from day one.
After launch: checking indexing
The first weeks after the move are a time for monitoring, not rest.
- Tell search engines about the changes. Submit the new sitemap in Google Search Console and Bing Webmaster Tools, and request recrawling of key pages.
- Go through the list of old URLs. Each should return either a 200, a 301 to the right page, or a deliberate 404 or 410.
- Watch for errors in the webmaster tools. A spike in 404s, pages excluded from the index, mobile usability problems: all of this shows up there before it shows up as a traffic drop.
- Compare traffic page by page, not overall. The total can hold steady while important individual sections sag. Compare equivalent periods and account for seasonality.
- Check conversion. That's what the whole thing was for. Make sure analytics goals fire, and compare the lead rate with what it was before launch.
How we approach a redesign
At Sphere, a redesign goes through the same stages as a new web development project, only the first stage is broader: before designing anything, we analyze what the current site already delivers for the business. Discovery, structure and messaging come first, then the visual language, development and launch. We design from scratch, but the structure and content are grounded in data, not taste.
To see the kinds of challenges companies bring to our digital agency, visit our projects page.
FAQ
Can a website be redesigned without losing traffic?
Yes, if you keep page URLs where possible, set up page-by-page 301 redirects for the rest, carry over meta tags and copy, and check indexing after launch. Short-term ranking fluctuations can happen, but a sustained drop usually points to a technical error that can be found and fixed.
How often should a website be redesigned?
Not on a schedule. A redesign is needed when the site has stopped doing its job for the business: it's awkward on mobile, doesn't reflect current services, converts poorly or is hard to update. It's better to make small improvements continuously than to rebuild everything every few years.
Do we need to change the CMS during a redesign?
Not necessarily. If the current system copes, makes content easy to edit and isn't slow, you can update just the design and front end. Switching the CMS makes sense when the old platform holds back growth and every change becomes expensive.
What should we do if traffic dropped after a redesign?
First, check the technical side: whether the site is blocked from indexing, whether redirects from the old URLs work, and whether copy and meta tags disappeared from key pages. Then compare traffic for individual pages before and after to find exactly where the loss happened, and fix it there.




