A website does not need a redesign because it is a few years old. It needs one when the experience no longer represents the business, helps the customer, or supports the next sale.
1. Can a new visitor understand the business quickly?
- The headline clearly explains the customer outcome.
- Services are named and described in plain language.
- The site is organized around customer questions rather than internal jargon.
- Important information is not buried in long pages or confusing menus.
2. Does it work well on a phone?
Try this: Open the site on your phone. Without using the menu, can you identify the service and find the phone number or quote action in under 15 seconds?
- Text is readable without zooming.
- Buttons and navigation are easy to tap.
- Images do not push important content far down the page.
- Forms are short, labeled, and easy to complete.
- The site loads reliably on a mobile connection.
3. Does the site prove there is a real business behind it?
- Contact information is current.
- People, credentials, location, and process are explained accurately.
- Photography and examples are genuine.
- Reviews and results are real, attributed appropriately, and never invented.
4. Is the next step obvious?
A visitor should not have to hunt for the phone number, request form, appointment path, or location. Calls to action should match the visitor’s stage rather than pushing every person toward the same generic “Learn more” button.
5. Can search engines understand it?
- Every important service has a crawlable page.
- Page titles and headings describe the actual subject.
- The site has canonical URLs, a sitemap, and appropriate structured data.
- Old or duplicate addresses redirect correctly.
- Local business information is consistent across the web.
When to repair and when to rebuild
The information is accurate, the site works on phones, and one or two problems, such as an unclear button, an old photo, or a broken form, need fixing.
Navigation, page structure, mobile use, technology, visual trust, and the customer path all need correction together.
Examples: repair or rebuild?
Repair: wrong hours and a broken form
The site looks fine and works on phones, but the hours are out of date and the contact form stopped sending. Fixing those two things is a repair, not a new website.
Repair: a missing service
You added a service and there is no page for it. Adding one page and updating the menu doesn’t require a rebuild.
Rebuild: unusable on a phone
Text is tiny, the menu doesn’t open, and visitors have to pinch and zoom to find your phone number. The structure itself is the problem.
Rebuild: the business has changed
You changed focus or added several services, and the pages, menu, and wording all describe the old business.
A site being several years old isn’t, by itself, a reason to rebuild it.
If you avoid sending customers to the current site, that hesitation is useful evidence.
Read the website redesign approach to see how useful URLs, access, email continuity, and launch checks are handled.
Want a second opinion?
Share the current website and the business goals behind the redesign.
Get a quote ↗