Many website redesign projects start for the wrong reason. Someone senior is tired of looking at the site, or a competitor launched something with more animation, and a budget line appears. A year and a half later the organization has a site that looks current and works about as well as the old one. Nobody diagnosed what was actually broken.
A redesign is a big, disruptive and costly job, and sometimes it is exactly the right one. Other times a few weeks of targeted fixes would do more. The signs below help you tell the two apart before anyone commits a budget.
Eight signs you need one
1. Your team cannot publish without a developer
Organizations tend to mention this one last because they have stopped noticing it. If adding a page means filing a ticket, every update waits in a queue. The developer’s invoice is the smaller cost. The bigger one is all the updates nobody asked for because asking was too much trouble.
Measure it before you argue about it. Time one routine update, from the moment someone writes it to the moment it goes live. If it takes days, you have your business case.
2. It fails on mobile, measurably
For many organizations, phones now bring in most of the visits. Your analytics will tell you whether that holds for yours. A responsive theme only means the layout adapts to the screen. The test that counts is Core Web Vitals on a mid-range phone over a real connection. Largest Contentful Paint should land under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1.
Check the field data in Search Console, which reports what real visitors experienced, instead of trusting a one-off lab test. If real users miss those thresholds on your main page types, the cause usually lies in how the site was built, and tuning rarely gets you there.
3. You now have an accessibility requirement it cannot meet
Accessibility now appears in the contracts and regulations of a growing share of Canadian organizations. Picture a colour palette that can’t reach the required contrast, components nobody can operate with a keyboard and a document library that was never tagged. Fixing all of that amounts to rebuilding the site piece by piece. Adding accessibility to a design that ignored it often costs more than building it in from the start. If you work in or for the public sector, this summary of Canadian requirements lists the standards that apply.
4. The structure fights the content
The symptoms are easy to spot. Some pages exist only because there was nowhere else to put something. The menu mirrors your org chart instead of what visitors came for. Three page types do the same job because different people built them in different years.
A new look leaves this untouched, because the problem sits in how the site is organized. It also comes back fastest when a redesign jumps straight to page layouts and skips the sorting.
5. Plugins are holding it together
Count them. If several do overlapping jobs and at least one hasn’t been updated by its author in two years, the site rests on code other people have abandoned. Each of those plugins is a security exposure, and each one can block an update you need to apply.
6. Nobody dares update it
When updates to the platform and its plugins get put off because the last one broke the homepage, risk builds up on a schedule you don’t control. A site that can’t be updated safely is already failing in private. The incident that makes it public will pick its own moment, and that moment is rarely convenient.
7. The organization changed and the site did not
Maybe you serve different clients than when the site was built, sell something new, merged with another organization or now work in two languages. A site that describes an organization that no longer exists misleads the people who read it. That is a far bigger problem than looking dated.
8. You cannot tell whether it works
Sometimes analytics are missing, or installed and never read. Often nobody has defined what a successful visit looks like. If you can’t say which pages bring in enquiries, you can’t show that the current site underperforms. Later, you won’t be able to prove the new one does better either. Set up the measurement first so the redesign has a baseline to beat.
Three signs you do not
You are bored of it
Your staff look at the site far more often than any customer does. To the people inside, familiar feels stale. To everyone else it feels consistent. The boredom is real, but a year’s budget deserves a better reason.
A competitor launched something
You can’t see their conversion rate, what the new site costs them to maintain or whether the project ran over. Copying their redesign means copying a decision you have no evidence about.
One page is underperforming
If your service page converts badly, rewrite the service page. Rebuilding forty page types to fix one is a common way to overspend. Work on the pages that carry your traffic costs less, and it shows you with evidence what actually moves the numbers.
How to tell the difference
Before committing, spend two weeks gathering five things:
- Your top twenty entry pages, and what visitors do after landing on them.
- Core Web Vitals from real visitors, for each page type.
- Page and document counts from a full crawl of the site.
- Publishing turnaround, timed rather than estimated.
- A keyboard and screen reader pass on your three most important page types.
If the problems cluster in a handful of pages, fix those pages. If they show up on every page type and trace back to how the site was built, you need a redesign. You can now describe it in terms a budget holder will recognize. The same findings make a strong opening section for a website redesign RFP.
What a redesign should not cost you
Redesign projects often lose four things along the way. Plan for each one from the start.
- Search visibility. Map every existing URL to exactly one new URL, with a single redirect hop. Start the map early in the project, well before launch week. If the site holds a large document library, this guide to migrating documents covers the details.
- Content. Move it with a script so nobody retypes it. Retyping drops things quietly.
- Integrations. List everything that connects to the site before anyone starts designing.
- Your team’s time. A redesign that makes publishing harder has failed, whatever it looks like.
Where the platform allows it, rebuild in place, section by section, instead of building a parallel site for a year and switching over in one night. It is less dramatic and much harder to get badly wrong.
If the diagnosis points to a rebuild, our page on website redesign and modernization explains how we run one, from the URL map to the measured baseline.