The case against redesigning by default
Many redesigns are triggered by fatigue rather than evidence. A new leader arrives, the brand feels dated, a competitor launched something shiny. None of these is a reason to discard a site that may be ranking, converting and carrying years of accumulated equity.
The uncomfortable truth is that a redesign resets your learning. Every tested headline, every page that earned links, every form that was tuned over time is put at risk. Sometimes that risk is worth taking. It should always be a decision, not a reflex.
Redesign the site you have measured, not the site you are tired of.
Good reasons and bad reasons
Legitimate triggers tend to be structural. The platform cannot be secured or updated. The site cannot be edited without a developer. The business has changed what it sells or to whom. The architecture cannot hold new products or markets. Mobile experience is fundamentally broken, not merely unfashionable.
Weak triggers are cosmetic or political: 'it looks old', 'the CEO does not like the homepage', 'we have budget left this year'. Cosmetic issues can usually be solved with a visual refresh on the existing structure, at a fraction of the risk.
Fig. 01 · Matrix
Tap to explore
Redesign, refresh, repair or leave alone
Fig. 02 · Process
Tap to explore
A low-risk redesign sequence
Step 1: Audit before you plan
Before any design work, take a baseline. Export every URL with its traffic, conversions and inbound links. Identify the pages that bring in most organic search visits and most enquiries or sales. Note top-performing calls to action and forms. This inventory becomes the list of assets the redesign must protect.
Add qualitative evidence: heatmaps and session recordings, customer interviews and sales feedback. The goal is to separate what visitors actually struggle with from what internal stakeholders dislike. They are rarely the same list.
Self-diagnostic
0/6Do you need a full redesign?
Answer honestly. Several yes answers in the first three questions point to structural change; mostly no answers suggest iteration.
01Does editing a simple page require a developer?
If yes: Your CMS is a structural constraint. Consider re-platforming or a redesign with a proper content model. If no: The editing workflow is not your problem; look elsewhere.02Has your offer, audience or positioning materially changed?
If yes: Architecture and content likely need rethinking, not just restyling. If no: A visual refresh may be enough.03Is the platform out of support or hard to secure?
If yes: Re-platforming is a necessity. Decide separately whether design should change at the same time. If no: Technology is not forcing your hand.04Do you have a baseline of traffic, rankings and conversions by page?
If yes: Good. You can judge the redesign against it. If no: Build the baseline first. Without it you cannot tell whether the new site is better.05Are the main complaints about appearance rather than task completion?
If yes: Consider a refresh on the current structure and keep what converts. If no: Usability problems justify structural work. Test the fixes.06Can you name the single business metric the redesign should move?
If yes: Write it into the brief and design every decision towards it. If no: Agree one before you brief anyone.
Step 2: Protect search equity
The most common avoidable damage in a redesign is lost organic traffic. It happens when URLs change without redirects, when ranking content is cut or merged carelessly, or when internal links and metadata are dropped in the new templates.
- Map every old URL with traffic or links to its closest new equivalent and implement permanent (301) redirects.
- Keep high-performing content, or improve it, rather than rewriting it from scratch for the sake of a new tone.
- Carry over titles, meta descriptions, headings and structured data, then improve them deliberately.
- Crawl the staging site before launch and compare it to the old site's crawl.
- Monitor Search Console and rankings daily for the first weeks after launch.
For a deeper treatment of migrations, see site migration SEO. Treat it as a parallel workstream with its own owner, not a launch-week task.
Step 3: Redesign the journeys, not the homepage
Visitors rarely arrive at the homepage and browse politely. They land on a service page from search, a product page from an ad, an article from a social post. A redesign that starts with the homepage optimises the page with the least decisive role in most journeys.
Instead, start with the page types that carry the most traffic and the highest intent: service or product pages, landing pages, pricing, contact and checkout. Rewrite the value proposition first, then design these templates around it.
Step 4: Decide what changes at once
Changing platform, URLs, design, copy and navigation simultaneously makes it impossible to diagnose what went wrong if performance drops. Where possible, stage the change. Re-platform with the existing structure, then evolve design. Or launch new templates on a section of the site before rolling them out.
| Approach | Strength | Risk |
|---|---|---|
| Big-bang launch | One coordinated release, clear moment for brand change | Many variables change at once; hard to diagnose drops |
| Phased by section | Lower risk, lessons carry into later phases | Temporary inconsistency between old and new sections |
| Iterative evolution | Continuous testing, no single risky moment | Slower to deliver a visible new identity |
Step 5: Launch, then measure against the baseline
A redesign is only better if the numbers say so. Compare the new site against the baseline on the metric you agreed: qualified leads, revenue, task completion. Allow for seasonality and for a short settling period in organic search, but do not wait months to look.
Expect some things to be worse. That is normal, and it is why a post-launch budget for fixes and A/B testing matters. The teams that come out of redesigns well are the ones that kept money and attention for the weeks after launch.
Myth vs reality
Redesign myths
Budgeting for the work nobody sees
Redesign budgets tend to concentrate on visible design and build. The invisible work, including content migration, redirect mapping, analytics configuration, accessibility testing and editor training, is where projects overrun. Name these tasks explicitly in the plan, give each an owner, and you remove most of the late surprises.
Content migration deserves particular care. Moving hundreds of pages by hand is slow and error-prone, but automated migration copies old problems into the new site. The pragmatic middle path is to triage: migrate high-value pages carefully and improve them, consolidate thin or duplicate pages with redirects, and retire pages that serve no audience. That triage is also the moment to agree who owns each section after launch, so the new site does not decay the way the old one did.
Key takeaways
- 01Redesign only when evidence shows structural problems; cosmetic issues usually need a refresh, not a rebuild.
- 02Baseline every page's traffic, links and conversions before planning so you know what to protect.
- 03Treat redirects and SEO migration as a parallel workstream with its own owner.
- 04Start with high-intent page types, not the homepage.
- 05Keep budget and attention for the weeks after launch, when the real comparison happens.
Frequently asked
- How do I know if my website needs a redesign?
- Look for structural signals: an outdated or insecure platform, editing that requires a developer, an offer or audience that has changed, or architecture that cannot hold new content. If the main complaint is that the site looks dated while it still ranks and converts, a visual refresh or iterative optimisation is usually the safer route.
- Will a website redesign hurt my SEO?
- It can if URLs change without redirects, ranking content is removed, or templates drop metadata and internal links. It need not. Map old URLs to new ones, keep or improve content that performs, crawl the staging site, and monitor search data closely after launch. Most losses are preventable with planning.
- What should I keep from my old website?
- Keep anything with evidence of value: pages that attract organic traffic or links, copy and calls to action that convert, tested forms, and content customers reference. Export a full URL inventory with performance data before planning so these assets are visible to everyone involved.
- What is the difference between a redesign and a refresh?
- A refresh changes the visual layer, such as typography, colour, imagery and some components, while keeping structure and platform. A redesign may change architecture, content, navigation and technology too. A refresh carries less risk and cost; a redesign is justified when structural problems block the business.
- How should we measure whether the redesign worked?
- Agree one primary business metric before the project starts, such as qualified leads or online revenue, and compare against a pre-launch baseline, adjusting for seasonality. Track supporting metrics too: organic traffic to key pages, form completion and task success. Review weekly for the first months.
Published by Fabulous.Media, a network of specialist marketing agencies. Updated 9 October 2026. Platform features change often; check current official documentation before acting on platform-specific detail.
