“The website looks old” is a signal, not a scope. Write the job the site must do next: clarify services, recover from maintenance problems, support a paid-traffic path, or give the owner a site they can maintain.
Google’s technical requirements are a useful baseline: a page needs to be crawlable, return a successful response, and contain indexable content to be eligible for Search, although eligibility does not guarantee indexing or serving. Read Google’s technical requirements.
Choose repair when the foundation is usable
A focused rescue is often the better fit when the platform and core pages are sound. Signs include useful URLs, accurate services, a testable contact path, and a site that can become maintainable after outdated plugins, themes, scripts, or content are cleaned up.
- Inventory pages, titles, forms, redirects, plugins, and owners.
- Repair phone links, form handling, metadata, headings, and internal links.
- Preserve useful URLs and write a rollback or maintenance note.
Choose rebuild when the structure keeps fighting the offer
A larger redesign is justified when the platform or theme prevents reasonable updates, service pages are missing or mixed together, the URL structure no longer matches the business, or responsive, security, form, and ownership problems are systemic.
Write the case plainly: name the structural constraint, the business consequence, and the evidence that will show the new version solved it. “A new look” is a preference. “A visitor can reach the correct service page and submit a tested inquiry on mobile” is a requirement.
Compare scopes before approving design
Make a small table with the current problem, repair action, rebuild action, risk if unchanged, and proof after launch. Include pages that already receive inquiries or useful search traffic. Preserve useful URLs and map retired ones to relevant replacements.
Review service-page content before choosing templates. A page should say what the service is, who it fits, what is included, what it requires, what it does not promise, and what the visitor should do next. Google’s people-first content guidance supports writing for a defined audience rather than producing search-engine-first copy.
Then test phone links, form fields, confirmation states, spam handling, inbox ownership, privacy language, and follow-up. A rebuild without a working inquiry route has only moved the problem into a newer layout.
Use a staged decision
Start with an inventory. Repair an urgent failure if it is safe and bounded. Use the evidence to decide whether the remaining work is a focused redesign or a true rebuild.
How Synapticraft can help
Synapticraft’s Website Rescue and Web Design work can pair a baseline review with service-page planning, contact-path checks, WordPress cleanup, and ProofSignal SEO foundations. For related planning, see the website redesign checklist.
If you are unsure which scope fits, request the free Website and SEO Review with the current URL and the problem visitors are having.
Start here
Decide from evidence, then design.
Send the current URL, the services that matter most, and the problem visitors are having.
Request a Free Website and SEO Review