Does Your Website Need a Redesign, or Just a Few Repairs?
Your website is showing its age. The mobile menu is awkward, the contact form is unreliable, and changing a simple piece of text feels like opening a can of worms. Does that mean you need a new website?
Sometimes. But a broken drawer does not automatically mean you need a new kitchen. Before you sign up for a rebuild, it is worth separating the problems that need repairs from the problems that need a different foundation.
That distinction matters when you run a small business. A redesign can be the right investment, but it can also swallow the budget that would have fixed the things actually stopping people from contacting you.
Start with what is costing you business
“The website feels old” is a starting point, not a project brief. Get specific. Can visitors understand what you do? Can they find the service they need? Can they contact you from their phone without pinching, zooming, or guessing where to click?
Write down the failures in plain English. The phone number is wrong. The form never reaches your inbox. The pricing is out of date. The service page takes too long to load. Those are problems someone can investigate and estimate.
Then separate “I would like this to look different” from “this is preventing a customer from doing something.” Both can matter, but they should not automatically receive the same priority.
When a repair is usually the sensible first move
If the site represents your business reasonably well and you can still manage its content, a focused repair may be enough. Common examples include fixing a broken form, updating a team page, cleaning up a mobile layout, replacing oversized images, and adding a landing page for a new service.
These jobs can often be scoped without reopening every design decision on the site. You keep the parts that work and address the parts that do not.
Say you run a local service business. Your homepage explains the offer, your service pages answer useful questions, and customers recognize your brand. But the request-a-quote button sits below a giant image on mobile. Moving the button and simplifying the opening section may be a better first project than rebuilding twenty pages.
The important word is “may.” A developer still needs to check how the site was built. A small visible change can sit on top of a messy technical problem.
When a rebuild starts making sense
A rebuild deserves a serious look when basic changes keep breaking unrelated features, the editing system is no longer workable, or the structure does not match the business you run today.
Maybe your site was built for one service, but you now offer five distinct services to different customers. Maybe the old platform makes every content change dependent on an unavailable vendor. Or maybe the site has been patched so many times that nobody can explain which code is responsible for what.
In those situations, another patch can become expensive twice: once to make the change, and again to work around the same foundation on the next job.
A rebuild should solve a named problem. “We need a simpler way to manage our services and quote requests” is a useful reason. “Everybody is redesigning this year” is less useful.
Keep the parts that have already earned their place
A new design does not require throwing away your history. Existing page addresses, useful articles, recognizable branding, and working integrations deserve an inventory before anything gets replaced.
If page addresses change, plan redirects to the relevant replacements. Record important forms and where their messages go. Check which pages customers already use and which pages search engines send visitors to. A launch is a poor time to discover that an old landing page was doing most of the selling.
Google describes redirects and canonical signals in its guidance on consolidating URLs. The practical lesson is straightforward: moving content needs a plan. A new homepage screenshot is only one piece of the job.
Ask for two options before choosing
If the decision is unclear, ask a developer to outline a focused repair option and a rebuild option. Each should describe what changes, what remains unresolved, and what needs investigation before a reliable estimate is possible.
The repair option might address the contact form, mobile header, and slow service pages. The rebuild option might add a new content structure and editing system. That makes the tradeoff visible.
Do not compare only the initial price. Consider how much of the problem each option solves and how much extra work you expect over the next year. A cheaper patch is not a bargain if you already know you are replacing the entire section next month.
You can make progress without deciding everything today
Some work is worth doing either way. Correct the phone number. Make sure inquiries reach the right inbox. Remove outdated offers. Fix a broken primary button. These changes can help customers now, even if a bigger redesign comes later.
That is the approach behind Web Dev Handyman: take the website you have, identify what needs attention, and make the next useful improvement. Sometimes the job is a repair. Sometimes it is a rebuild. You should understand the reason before committing to either.
If you are unsure which direction makes sense, take a look at website help for small businesses, then send me your website and the problems you want solved. We can start with the actual to-do list.
Keep useful content and search signals in the plan
If a repair or rebuild involves page addresses, headings, or indexing settings, include those changes in the scope. Technical SEO implementation can help carry the relevant recommendations through to the finished website.