In this guide
A website audit investigates what needs attention and why. A redesign changes the site’s structure, presentation or underlying implementation. An audit can help determine whether a focused repair, a group of improvements or a rebuild is justified.
For a US service business, the decision should start with the work the website needs to do: explain the right services, establish credibility and help suitable customers make contact. An aging appearance or a disappointing test score does not settle that decision.
Define the problem before choosing the project
Replace “the website is not working” with an observation you can investigate. Perhaps people ask whether you cover their area, an important service gets few relevant visits, or mobile visitors struggle to complete the inquiry form.
Record the affected pages, what you expected and the evidence available. Separate a confirmed fault from a hypothesis. A failed submission is a specific problem. A decline in inquiries could involve search visibility, the offer, seasonality, measurement or the website experience.
When the cause is uncertain, a focused review helps narrow the decision. Agree which pages and journeys matter, what access is needed and what remains outside the review. This makes the audit useful without assuming every part of the site needs replacement.
Look for improvements the current site can support
Review content and navigation before attributing every problem to the design. Can visitors find your main services? Do those pages explain the work, actual service coverage and next step? Does the menu use language customers recognize?
Google’s SEO Starter Guide recommends logical organization and useful content. It does not require reorganizing an entire site whenever a page needs attention.
Imagine a hypothetical HVAC company whose site already works across screen sizes. Its heat pump service is buried inside a general services page, and the inquiry form sends requests to an obsolete address. A dedicated service page, clearer links and a corrected form route are sensible first candidates for repair. A new visual identity would not resolve those gaps by itself.
Ask whether the existing editor and templates can support those changes cleanly. Test the proposed approach before committing to a larger project.
Check mobile and form barriers directly
Walk through the important journey on a phone and with a keyboard. Look for obscured controls, unreadable text, confusing field labels and errors that give no useful correction. Test a submission through to receipt by the responsible person.
W3C’s forms guidance covers clear labels, instructions, validation and confirmation. These checks help distinguish a form component that can be repaired from a wider template problem affecting many pages.
A menu that cannot be used with a keyboard deserves attention even if it looks modern. Equally, fixing that menu does not automatically require rebuilding the site. W3C’s preliminary accessibility checks explain that a quick review cannot establish complete accessibility. Record the scope and limits of the evidence when deciding what work is needed.
Diagnose speed before replacing the platform
A performance result should lead to an investigation of the cause. Ask which pages are affected, what visitors experience and whether the issue comes from particular images, scripts, templates or server behavior.
Google’s Web Vitals guidance distinguishes controlled laboratory testing from measurements of real visits. It also separates loading, responsiveness and visual stability. A lab test is useful for diagnosis, while available visitor data helps establish how widely a problem occurs.
If a large banner image causes the main delay on one service page, investigate that asset first. If every important template has persistent problems that cannot be corrected within the current setup, broader changes may be justified. Neither conclusion follows from the headline score alone. Request a proposed remedy and a way to check its effect.
Identify constraints that justify a redesign
A redesign becomes more persuasive when several important improvements depend on changing the same underlying structure. Examples include a navigation model that cannot accommodate the business’s services, inflexible templates that repeatedly obstruct accessible content, or an editing system the team cannot use for essential updates.
Consider a hypothetical remodeling company that has expanded into several distinct services. Its existing site provides only a fixed gallery and a generic contact screen. If a developer confirms that useful service pages, navigation and inquiry routes require replacing most of that structure, rebuilding may be more coherent than accumulating exceptions.
Ask the supplier to identify the limitation, explain the alternatives and show what the proposed platform changes would enable. Separate a genuine constraint from a preference for another tool. A redesign can also retain working content, URLs and functions.
Compare the complete scope of each option
Compare targeted improvements and a redesign against the same business requirements. Include diagnosis, content work, development, testing, migration, recurring services and the effort your team must contribute. Ask what is included, what remains uncertain and who owns each decision.
For a redesign, identify useful existing pages and their URLs before removing anything. If URLs change, plan relevant replacements, redirects and monitoring. Google’s site migration guidance warns that rankings can fluctuate during a move. No migration plan guarantees unchanged rankings.
Optiseo’s website design and development service scopes pages, content, features and launch work around the project. If the evidence supports a rebuild, our website brief guide explains how to turn that decision into clear requirements.
Use a short decision checklist
Before approving either route, confirm the following:
- Problem: Which customer task is failing, and what evidence supports that finding?
- Reach: Is the issue isolated or repeated across important pages?
- Repairability: Can the current platform support a maintainable correction?
- Value: What useful content, search visibility and working functions should be retained?
- Scope: What does each proposal include, and what ongoing costs remain?
- Ownership: Who approves content, implements changes and checks the result?
Prioritize confirmed barriers to inquiries, then improvements with a clear purpose. Where uncertainty remains, commission the smallest useful investigation that can resolve it. Assign an owner and an acceptance check to the first agreed change.