Should you redesign your website or improve the one you already have?

Do not prescribe a redesign before diagnosing the website

A redesign is a delivery method, not a business outcome. The actual goal may be clearer enquiries, stronger credibility, easier editing, better mobile usability or improved search visibility. Once the problem is specific, it becomes easier to decide whether the current website can support the fix.

Start by separating visible symptoms from structural causes. An outdated hero image is a symptom that can be changed. A template that prevents important services from having proper pages is a structural limitation.

Can a mobile visitor understand and act without fighting the page?

Many local-service customers arrive from a phone while comparing several businesses or dealing with an immediate problem. Test the real page at common phone widths instead of relying only on a desktop preview.

• The business, service area and main offer are clear without zooming.
• Phone, booking or quote actions are easy to tap and do not overlap.
• Navigation labels fit and important pages remain reachable.
• Text is readable and sections do not require horizontal scrolling.
• Forms use suitable fields, show useful errors and submit successfully.
• Images load at sensible sizes and do not push content around.

If these failures are isolated to a component or two, targeted work may be enough. If every template relies on fixed desktop dimensions, rebuilding the responsive system is often the cleaner option.

Does the website still represent the business accurately?

A business can outgrow the website that launched it. Services change, the team develops and the quality of work improves, while the site continues to present an older or more generic version of the company.

• The message reflects the customers and work the business wants now.
• Photography shows the real people, work or environment where possible.
• Reviews, qualifications and relevant proof appear near decisions.
• Claims are specific, current and supportable.
• Typography, colours and layouts feel consistent across the site.
• Old promotions, team members, accreditations and contact details have been removed.

Can every important service answer its customer properly?

A website becomes difficult to improve when every service is squeezed into one page or the navigation reflects internal departments instead of customer decisions. Content problems can often be edited, but architectural problems may affect templates, URLs and navigation throughout the site.

• Each commercially important service has enough space to explain the problem, approach, proof and next step.
• Visitors can distinguish services with different urgency or buying intent.
• The home page directs people to useful detail instead of trying to contain everything.
• Location information reflects genuine coverage without copied suburb pages.
• Related pages are connected with descriptive internal links.
• New content can be added without breaking the navigation or visual system.

Is the website slow because of a fixable issue or its foundation?

Large images, excessive tracking scripts and neglected plugins can make an otherwise sound website slow. Those issues may be repairable. A rebuild becomes more reasonable when the theme, page builder, hosting or dependency stack imposes problems that cannot be removed without reconstructing most pages anyway.

• The site uses HTTPS and supported software.
• Core templates load reliably on mobile connections.
• Images and embedded media are delivered appropriately.
• There are no recurring security, update or plugin conflicts.
• Forms, analytics and integrations are documented and still required.
• The domain, hosting and administrative accounts are controlled by the business.

Performance tools are diagnostic aids, not a redesign vote. Investigate what creates the delay and what it would cost to correct before replacing the website.

Do not redesign away search performance you already have

A website can look dated while still earning valuable search traffic. Before changing URLs or removing pages, use Search Console and analytics to identify which content receives impressions, clicks, enquiries and external links.

• Record the current URLs and their purpose.
• Identify pages with meaningful organic traffic, rankings or links.
• Keep successful URLs where practical.
• Map every removed URL to the closest relevant replacement.
• Preserve useful content instead of discarding it for shorter marketing copy.
• Submit the updated sitemap and monitor indexing after launch.

Can the business safely maintain what needs to stay current?

The right editing model depends on the business. Some owners need frequent control over services, team members or articles. Others prefer direct support and rarely touch the site. The problem is not limited editing by itself. The problem is an unclear or unreliable update process.

• Someone knows where the domain and hosting are managed.
• The business retains appropriate ownership and account access.
• Routine content changes can be made without damaging the layout.
• Backups, security updates and technical responsibility are defined.
• There is a practical process for urgent changes to hours, services or contact details.
• The cost and response time for ongoing support are understood.

If the current provider has disappeared, the platform is unsupported or nobody can make a safe update, a controlled migration may be more valuable than another visual patch.

Low enquiries do not automatically mean bad design

A website cannot convert traffic it does not receive, and it cannot repair a weak offer by changing button colours. Diagnose the full path from search or referral through to enquiry.

Use the evidence to choose a targeted improvement or redesign. A clear diagnosis also gives the eventual project a measurable purpose beyond making the site look newer.

A practical redesign scorecard

When the improve column wins, create a prioritised repair plan and measure the result. When several structural areas fall into the redesign column, scope the rebuild around those constraints and preserve everything that already works.

Website redesign FAQs