5 Signs Your Small Business Website Needs Work: Repair or Rebuild?

Reviewed September 13, 2026.

A frustrating website does not automatically need replacing. A broken form may need a repair. An unclear homepage may need better writing. A site that no longer supports your services or cannot be maintained reliably may need a rebuild.

Before asking for a redesign quote, try these five checks. Write down what fails, where it happens, and what a customer needs to do instead. That gives you a useful starting point for deciding what to fix.

1. Calling or requesting an estimate is awkward on a phone

Open your website on your phone and act like a first-time customer. Find a relevant service, tap the phone number, then submit a test inquiry. Let your team know it is a test.

Watch for text you have to zoom to read, buttons that overlap, fields that are difficult to complete, and a submit button that leaves you unsure whether anything happened. Check that the inquiry actually arrives at its intended destination.

Repair first: Correct a broken link, simplify unnecessary form fields, or fix the layout on an affected page.

Consider a rebuild: The same problems run through the whole site and the existing layout is difficult to adapt. Ask for an explanation of that limitation before assuming a new platform is necessary.

2. Visitors have to guess what you do or where you work

Read your homepage without relying on what you already know about the business. Can a potential customer identify your main services, service area, and next step?

Then open one service page. Does it explain the actual work, who it suits, and how to ask about it? “Quality solutions for all your needs” gives a visitor less to work with than a plain description of the jobs you handle.

Repair first: Rewrite the headline, clarify services and locations, and give each important page a relevant contact link.

Consider a rebuild: Your services have changed enough that the navigation and page structure no longer fit. A new structure may help, but useful existing pages should inform the plan.

3. Important details are wrong or difficult to verify

Check phone numbers, opening hours, service descriptions, team details, and any published prices. Look for discontinued services, expired promotions, and claims you cannot support.

Review the evidence a customer can use to judge your business. That might include real work photos, an explanation of your process, or genuine customer feedback used with permission. You do not need to fill every page with testimonials, and missing proof should never be replaced with invented examples presented as real.

Repair first: Correct the facts, remove unsupported claims, and add useful material you already have permission to use.

Consider a rebuild: Inaccurate content is scattered through duplicated pages and the current structure makes maintaining one clear version impractical.

4. Nobody has a dependable way to keep the site current

Pick one recent change your business needed, such as new hours or an updated service description. Who requested it, who made it, and who checked the result?

You do not have to edit your own website. A managed service can be a sensible choice if you would rather send changes to someone responsible for the site. What matters is knowing how requests work, what is included, and what needs a separate quote.

Repair first: Agree on an update process and a responsible contact. Clarify access, scope, and expected handling of requests.

Consider a rebuild: Essential changes are blocked by a platform or setup that cannot be supported reliably. Establish what is actually blocked before committing to replacement.

5. Pages repeatedly stall or stop you completing a task

Try your homepage, an important service page, and the contact page on a phone and a computer. Notice whether images appear late, content jumps while you are trying to tap, or forms stop working. Repeat a problem before treating one slow connection as a site-wide failure.

A performance report can help a developer investigate, but a single score is not a verdict on whether you need a new website.

Repair first: Ask for the cause of the observed problem and a scoped fix. Large images or an unnecessary third-party feature may be worth investigating.

Consider a rebuild: Problems are widespread and a technical review shows that repairing the existing setup would be less practical than replacing it.

Decide based on the problem, not the site’s age

That last row matters. After an inquiry, does the customer receive confirmation, and does someone know to respond? Those are customer-tool and team-process questions; they do not prove the website needs replacing.

Ready to discuss the website itself? Compare managed website options, or send an inquiry about the problems you found. Start with the work your customers need the site to do.