7 Signs Your Business Needs a Website Redesign — and 4 Problems That Only Need a Fix

Most businesses know something is wrong with their website before they know what to call the problem.

It feels dated. Enquiries are weaker. Updating a page is stressful. The mobile version is awkward. The business has changed but the site still explains the old version.

That does not automatically mean you need a full redesign.

The better question is: is this one isolated defect, or has the website stopped working as a coherent business system?

A second question matters if the site already gets search traffic: what must survive the redesign? A new visual system is not a good trade if useful URLs, rankings, enquiries or analytics disappear in the process.

Sign 1: the website explains the business you used to be

This is one of the clearest redesign signals.

Maybe you started with one service and now have four. Maybe you moved upmarket. Maybe the company now serves businesses instead of individuals. Maybe your strongest proof did not exist when the site was built.

If visitors are learning an outdated version of the company, changing a few colours will not solve it. The information hierarchy itself needs reconsideration.

Sign 2: the important mobile journey is frustrating

Do not ask only whether the site “is responsive.”

Try to complete the customer’s actual task on a phone:

• understand the offer;
• find the right service;
• view proof;
• call or WhatsApp;
• fill a form;
• book;
• buy;
• find the location.

If those tasks are consistently harder on mobile because of the navigation, content structure, pop-ups, forms or layout, the experience may need redesign rather than cosmetic adjustment.

Sign 3: good visitors arrive but do not know what to do next

A website can receive traffic and still fail commercially.

Common symptoms include:

• strong traffic but almost no enquiries;
• visitors reaching service pages but not contacting you;
• paid traffic landing on a generic homepage;
• forms that ask too much too early;
• multiple competing calls to action;
• no clear distinction between services.

If this is your main problem, also read 5 Reasons Your Website Gets Traffic but No Sales.

When conversion problems appear across many pages, the issue is usually structural enough to justify redesign work.

Sign 4: you avoid sending people to your own website

This is a surprisingly useful test.

If you send a prospect your Instagram, LinkedIn or PDF instead because you feel the website weakens the impression of the business, the gap between the company and its digital representation has become commercially relevant.

That does not mean the site must look fashionable. It means it no longer communicates the level of trust or clarity the business needs.

Sign 5: publishing a simple change feels dangerous

A website becomes an operational problem when changing a phone number, team member, price, service or article requires workarounds you are afraid will break something.

That can happen because:

• nobody understands the CMS;
• the theme is heavily patched;
• plugins depend on one another unpredictably;
• page layouts are inconsistent;
• previous developers hard-coded ordinary content;
• ownership and credentials are unclear.

If the content system actively prevents the business from staying current, redesign or rebuild work may be justified.

Sign 6: search performance is being constrained by the structure

Not every SEO decline means “redesign the website.”

But structural problems matter when:

• important services share one thin page;
• useful pages are buried from navigation;
• old and new URLs compete with one another;
• the site cannot create the page types you need;
• title, canonical or metadata control is unreliable;
• performance problems are systemic;
• migrations were done without redirect discipline.

In those cases the design and information architecture are part of the SEO problem.

Sign 7: several of these problems are happening at once

This is the strongest signal.

One ugly section is not a redesign case. One broken form is not a redesign case.

But when the site is simultaneously hard to edit, confusing on mobile, weak at conversion, outdated in message and technically difficult to improve, patching each symptom can become more expensive than redesigning the system deliberately.

Four problems that often need a fix, not a redesign

1. One broken form

Repair it. Test submission, confirmation, notification and analytics. Do not rebuild a whole site to solve one failed integration.

2. Weak homepage copy

If the structure is sound but the message is vague, rewrite the copy and test the change first.

3. A few slow pages

Find the cause. Oversized media, a third-party script or one bad template can sometimes be fixed without touching the rest of the site.

4. An outdated visual section

If the business positioning, navigation, SEO structure and conversion path are still healthy, a targeted visual refresh may be enough.

Redesign vs rebuild: they are not the same

A redesign changes how customers understand and use the website.

A rebuild changes deeper technical foundations.

You can redesign on the same platform. You can rebuild while preserving nearly the same visual design. And sometimes you need both.

The decision should come from constraints, not terminology.

If the site already ranks, redesign it like a migration

This is where otherwise good redesign projects can become expensive.

A developer may see a cleaner route structure. A designer may want fewer pages. A new CMS may generate different URLs automatically. None of those changes are necessarily wrong, but an existing website is not a blank canvas once search engines and customers already know its pages.

Google’s current site-move guidance recommends preparing the new site, mapping old URLs to their new destinations, using server-side permanent redirects when URLs change, updating internal links and canonical references, submitting the new sitemap, and monitoring the move in Search Console. Google also recommends changing one major thing at a time where practical rather than combining a domain change, CMS migration and redesign into one uncontrolled release.

Before development, create a URL inventory

Start with the pages that already have evidence behind them:

• URLs receiving organic clicks or impressions;
• pages with backlinks;
• pages that generate enquiries, bookings or sales;
• service pages people regularly enter from search;
• useful articles and guides;
• downloadable files or media that attract links.

Then make an explicit decision for each URL: keep, improve, consolidate, redirect or intentionally remove.

For many redesigns, the safest SEO decision is also the simplest: keep a useful URL unchanged when there is no business reason to change it.

If a URL must change, map it to the closest replacement

Do not wait until launch day to discover that /old-service disappeared.

Keep a migration sheet with at least:

Google recommends direct server-side permanent redirects such as 301 or 308 for moved pages. Avoid chains where an old URL redirects to another old URL before eventually reaching the new one. Also avoid sending many unrelated deleted pages to the homepage; a redirect should lead to a genuinely relevant replacement.

Preserve the reason the page ranked

A redirect alone does not make a weak replacement equivalent to a useful old page.

When a high-value page is redesigned, preserve or deliberately improve:

• its search intent;
• useful copy and proof;
• title and heading logic;
• internal links;
• structured data that is still accurate;
• images or downloadable assets that matter;
• the conversion path that made the page commercially useful.

A common redesign mistake is to replace a detailed service page with a visually elegant paragraph and assume the 301 redirect will do the rest.

Launch checks matter as much as the design

Before and immediately after launch, verify:

1. staging noindex or crawler blocks are not accidentally left on production;
2. old URLs return the intended redirect or intentional 404/410;
3. new pages have self-referencing canonicals where appropriate;
4. internal links point directly to new URLs rather than through redirects;
5. the XML sitemap contains the intended canonical URLs;
6. forms, calls, bookings and payments still work end to end;
7. analytics and conversion events still fire;
8. Search Console is monitored for unexpected indexing and crawl errors.

Google notes that ranking fluctuations can happen during significant site moves while pages are recrawled and reprocessed. The goal is not to promise “zero ranking movement.” The goal is to avoid preventable losses caused by broken redirects, missing pages, accidental noindex rules or a redesign that quietly removed what was working.

A simple redesign triage

Score each area from 0–2:

0–3: targeted fixes probably deserve the first attempt.

4–7: a focused redesign may be justified.

8–12: investigate a broader redesign/rebuild before continuing to patch symptoms.

This is not a scientific score. It is a way to force the conversation away from “I am bored with the design” and toward actual evidence.

Before requesting redesign quotes

Write down:

1. what changed in the business;
2. what visitors currently struggle to do;
3. which pages receive traffic or rank;
4. which URLs must be preserved;
5. what you need to edit regularly;
6. what integrations matter;
7. what a successful redesign should improve;
8. who owns the domain, hosting, analytics and Search Console;
9. who is responsible for the redirect map and post-launch checks.

Then use 11 Questions to Ask a Web Designer Before You Pay when comparing providers.

If the diagnosis points to a real redesign rather than a handful of repairs, see my web design service. If you want a second opinion before committing to a rebuild or migration, contact me. I can help identify whether the real need is a repair, redesign, migration or new website.