Website planning
Should you redesign your website or improve it?
A redesign is not always the answer. Sometimes clearer copy, a faster page, or a better form fixes the real problem for less. Here is how to tell which situation you are in before you spend money.
Check what is actually wrong
“The site looks old” is a feeling, not a diagnosis. Before choosing, look at evidence: are pages indexed, are they fast on a phone, do visitors reach the contact path, and are inquiries being tracked? Our guide on why a site may not show up on Google covers the first check, and fixing a slow website covers speed.
When improving is enough
Targeted improvements usually fit when the structure is sound but the pages underperform. Examples of illustrative situations:
- The service pages exist but say very little. Rewrite them.
- The site loads slowly because of oversized images. Fix the images.
- The contact form is hard to use on a phone. Simplify it.
- Nobody can tell which inquiries came from the website. Add tracking.
These are smaller jobs than a rebuild, and they keep the URLs that search engines already know.
Two documented improvements on our own site
In October 2026, we corrected inconsistent navigation across this site. Older headers linked to a retired page while newer pages used a different menu. We kept the existing service and article URLs, moved the header into one shared source, and checked that all 34 static pages and generated service pages use the same menu. That addressed a navigation problem through a focused implementation change.
We also replaced existing project screenshots with smaller WebP files. One Cypris Roofing screenshot went from 716,616 bytes to 79,180 bytes at the same pixel dimensions, an 89.0% file-size reduction. The documented image comparison explains the method and limits. This measures asset weight, not an improvement in search rankings or real-user load time.
These examples give you a practical decision rule: name the problem and the smallest change that resolves it, keep useful URLs, and check the result before extending the scope.
When a redesign is justified
A redesign makes sense when the problem is structural: the site cannot be edited without a developer, it is not usable on mobile, the navigation hides important services, or the platform blocks changes you need. In those cases patching costs more over time than rebuilding. Our website redesign service starts with an audit so the scope matches the problem.
Protecting what already works
Whichever route you choose, do not lose pages that bring in visitors. Keep a list of existing URLs, keep the addresses that rank where possible, and set up permanent redirects for any that must change. Google documents how to do this in its guidance on site moves with URL changes. Record Search Console data before launch so you can compare afterward.
A simple way to decide
- List the specific problems, with evidence for each.
- Mark which ones copy, speed, tracking or navigation fixes would solve.
- If most are fixable that way, improve first and measure.
- If the platform or structure is the cause, plan a redesign and protect your URLs.
For cost context on either path, read how much a contractor website costs.