Should You Fix Your Business Website or Rebuild It?

A website can look dated and still do its job. A beautiful website can quietly lose inquiries because its forms fail or its services are hard to understand. Before deciding on a redesign, look at what customers need to accomplish and what currently gets in their way.

Start with the customer’s next step

Open your site on a phone. Without using the menu, can a new visitor tell what you do, where you work, and how to contact you? Try calling, requesting an estimate, and finding a specific service. Submit the contact form and confirm the message reaches the right inbox. These simple checks often reveal more than a visual redesign proposal.

Write down the problems you actually observe. “The site feels old” is a preference. “The phone number is hard to tap” and “the estimate form never arrives” are specific problems you can fix and verify.

Repair the site when the foundation still works

Targeted improvements are a good starting point when you can edit the site safely, its important pages load reliably, and the current platform supports your needs. You may only need clearer service descriptions, better navigation, updated photos, faster images, or a working booking integration.

• Keep useful pages and URLs that customers already find.
• Replace vague headlines with specific services and service areas.
• Make contact details and next steps easy to use on mobile.
• Fix broken links, missing page titles, and outdated business information.
• Check whether the changes improve actual inquiries.

Consider a rebuild when changes fight the platform

A rebuild becomes more reasonable when routine edits repeatedly break the layout, the business has outgrown the site’s structure, or essential integrations cannot be supported. A platform with unclear ownership or no practical export path can also make long-term maintenance difficult.

The site’s age alone is not a reason to start over. Neither is a missing structured-data block. Ask whether the existing platform can support the experience your customers need at a reasonable cost, including future upkeep.

Compare the complete cost

Ask for two clearly scoped options: the highest-priority repairs and a rebuild. Compare content work, migration, hosting, recurring software fees, maintenance, and your own time. A lower initial quote may leave photography, copywriting, redirects, or form setup outside the project.

Agree on who owns the domain, hosting account, source files, and business data. Make sure you will have access after the project ends. A website should remain a usable business asset.

Protect what already works

Before replacing a site, inventory its pages and review available Search Console and analytics data. Identify useful landing pages, backlinks, and contact paths. Map old URLs to relevant new pages with permanent redirects where URLs must change. Keep a backup and test the new site before switching traffic.

At launch, verify mobile layouts, keyboard navigation, page titles, indexing settings, contact forms, analytics, and redirects. Check again after launch: a successful design review does not prove an inquiry reached your inbox.

A useful decision rule

Choose repairs if a limited set of changes can deliver a clear, reliable customer experience. Choose a rebuild if the structure or platform prevents that outcome and the full cost makes sense. If you are unsure, start with an independent review and a prioritized list of problems before committing to a design project.

See how our website and visibility review works, or talk through your options with Gabe.