DIRECT ANSWER
Improve the existing site when it can support accurate content, clear customer paths and working functions. Consider a rebuild when documented structural or platform limitations prevent that work. Weak inquiry volume or an aging design alone does not establish that replacement is necessary.
Define the problem before choosing the project
“I need a new website” describes a purchase. Identify the problem first: customers cannot find the right service, the offer is unclear, inquiries fail, facts are outdated or the site cannot support a required function.
Record the affected page, the customer task, what happens now and what should happen instead. If your main concern is low contact volume, first review the inquiry path.
Compare three scopes
| Scope | Consider it when | Evidence to request |
|---|---|---|
| Targeted repair | A specific link, form or layout fails | Reproduction of the failure and a verified fix |
| Content and journey improvement | The site works but answers or service paths are missing | Revised copy, navigation and inquiry path within the existing site |
| Rebuild | Required changes are blocked by verified structural or platform limits | Explanation of the limit, replacement scope and migration plan |
This is SIS editorial guidance. Several scopes can apply to one site. A broken form can need immediate repair while a broader rebuild is planned.
Check whether the existing site can do the job
Ask whoever manages it to demonstrate whether they can:
- Edit service details, titles and customer answers.
- Add useful pages and descriptive links.
- Improve mobile layouts and keyboard navigation.
- Correct and test the inquiry path.
- Manage domain, hosting and required third-party access.
Do not accept “the platform is bad” as the evidence. Ask which requirement it cannot meet and whether a smaller change would resolve the limitation. W3C's preliminary checks can uncover accessibility issues, but they are not a complete evaluation. [1]
Better content means better answers
A longer homepage is not automatically an improvement. Missing service boundaries may belong on the service page. A detailed comparison may need its own guide. A confusing opening may need only a clearer headline and next step.
Start with homepage messaging, then collect customer questions worth publishing. Preserve answers that already help customers.
Illustrative example: a professional firm can edit its existing service pages and add a catalog. If its main gaps are scope, preparation and cost explanations, a focused content project deserves consideration before replacement. If the same site cannot deliver an essential approved function, evaluate that requirement separately.
A rebuild needs a preservation plan
Inventory existing public URLs, useful content, approved images, incoming links where known, forms, integrations and account ownership. Preserve useful URLs where possible. Map changed URLs to relevant destinations and test redirects. Google's site-move guidance covers URL mapping, redirects and monitoring; search fluctuations can occur during a move. [2]
Do not replace unrelated old pages with homepage redirects just to simplify the migration. Identify where their useful information will live.
If performance is part of the concern, first read the Core Web Vitals report correctly. A replacement project also needs a preservation and migration plan.
Compare complete costs and responsibilities
Request comparable written scopes. Include content, design, functions, testing, migration, ownership, hosting and after-launch support. Identify what the business must supply and which external subscriptions remain separate.
There is no verified universal cost or break-even threshold in this guide. The right comparison uses your requirements and actual proposals. For the delivery decision, read build it yourself or hire a designer.
Make the next decision concrete
Create a short list: preserve, repair, rewrite, add and replace. Ask the provider to explain each proposed replacement. Compare SIS plans against the resulting scope, or request a review with the pages and functions that concern you.