Most businesses do not redesign because someone decided the site looked dated. They redesign because something stopped working and the website turned out to be the cause. Knowing which problem you actually have decides whether you need a rebuild, a few targeted fixes, or nothing at all.
On this page
Looks are the symptom, not usually the reason
Appearance matters, but mostly because of what it signals. When a referral looks you up and finds a site that clearly has not been touched in eight years, they start wondering what else has not been touched. That is a real business cost, and it is the honest argument for caring how the site looks.
What it is not is a good sole reason to spend money. If the current site loads fast, works on a phone, explains the business clearly, and brings in inquiries, a redesign is a preference rather than a need. Plenty of plain websites outperform pretty ones.
The signals that actually matter
It is hard to use on a phone
Pull your own site up on your phone and try to find your phone number, your hours, and one specific service. If any of that requires pinching, zooming, or hunting, you have found a problem that costs you work. Most people looking for a local business are on a phone, often standing somewhere inconvenient.
It loads slowly
Slow pages lose people before they read anything. The usual culprits are enormous uncompressed images, a pile of plugins nobody audits, and cheap shared hosting. Google publishes a free PageSpeed Insights tool that will tell you where you stand on a phone connection.
Nobody can find anything
Navigation built around your internal org chart instead of what customers are looking for. Services buried three clicks deep. A menu with fourteen items. If a stranger cannot tell what you do within a few seconds of landing, the structure is the problem.
The information is out of date
Services you no longer offer, services you added two years ago that are not listed, old staff, old hours, an old phone number. Every one of these quietly costs you credibility, and inaccurate hours or contact details cost you actual calls.
The photos do not match the work
Stock photography of people who do not work for you, in buildings you do not own, is one of the quickest ways to look like every other site in your category. Real photos of real jobs are often more persuasive than any design decision.
There is no obvious next step
A visitor who is convinced still needs to be told what to do. If the phone number is not tappable on mobile, if the estimate form is buried on a contact page, or if every page ends without an action, you are losing people who had already decided.
Your service area is unclear
If someone two counties over cannot tell whether you will drive to them, they call somebody else. Naming the places you actually work is simple to fix and helps with local search at the same time.
You do not appear in local searches
Sometimes this is a website problem, sometimes it is a Google Business Profile problem, and often it is both. Worth diagnosing before assuming a redesign fixes it. The guide on why a business does not show up on Google Maps covers the causes that a new website will not solve on its own.
You cannot edit your own site
Waiting a week and paying a fee to change your hours is a structural problem. So is not knowing who holds the login. If you are not sure what you control, work through the digital ownership checklist before you commit to any new project.
Forms and tracking are broken
Contact forms fail silently more often than owners realize, usually after a host change or a plugin update. Send yourself a test submission today. Then check whether you have analytics at all, because without it you are guessing about everything else on this list.
Nobody is maintaining it
Unpatched software, expired certificates, no backups. An unmaintained site is not merely stagnant, it is exposed, and the cleanup after a compromise usually costs more than the maintenance would have.
Full rebuild or targeted fixes
Not every problem on that list needs a rebuild. A rough guide.
- Targeted fixes are usually enough when the structure is sound and the issues are specific: outdated content, a broken form, slow images, a missing service page, no analytics.
- A rebuild makes more sense when the problems are structural: the site cannot work properly on a phone, the page structure does not match how customers search, the platform locks you out of your own content, or the underlying software is too old to update safely.
The test we use is simple. If fixing the list one item at a time costs a meaningful fraction of a rebuild and still leaves you on a foundation you do not want, rebuild. Otherwise fix what is broken and spend the difference on content and photography.
A practical redesign checklist
- Open every important page on your phone and note what fails
- Run the homepage and one service page through PageSpeed Insights
- Submit a test inquiry through every form and confirm it arrives
- Search your own main service plus your town and see where you land
- Confirm you can log in and edit a page yourself
- Check that hours, phone, address, and services are correct everywhere
- List the pages that currently bring in traffic, so you know what to protect
How to prepare before you start
Projects stall on content, not design. Before the work begins, gather your service list with real descriptions, the areas you cover, photos of finished jobs, any licensing or insurance details worth showing, and your best customer reviews. Decide internally who approves copy, because a single decision-maker moves faster than a committee.
Also write down what the site is supposed to accomplish. More estimate requests, fewer unqualified calls, better applicants, easier online ordering. That goal shapes every structural decision that follows.
Protecting the search visibility you already have
This is where redesigns go wrong, and it is usually avoidable. A site that ranked reasonably well can lose that overnight if the migration is careless.
- Inventory the old URLs first. Export everything indexed before anything changes.
- Keep URLs identical where you can. The safest redirect is the one you did not need.
- Map 301 redirects for everything that moves. Point each old URL at its closest equivalent, not at the homepage.
- Carry over the content that earns traffic. Rewriting a page that ranks is a decision, not a default.
- Preserve titles and descriptions on pages that already perform.
- Check indexing settings before launch. Staging sites are usually blocked from search engines, and shipping that block to production is a common and expensive mistake.
- Keep analytics running through the transition so you can tell what changed.
- Submit the new sitemap in Google Search Console and watch coverage for a few weeks.
Our website redesign service treats this as part of the build rather than an afterthought, and the local SEO work is planned alongside it so the new structure is built to be found. You can see finished redesigns in the portfolio.
Common questions
How often should a business website be redesigned?
There is no fixed schedule worth following. A well-built site that is maintained and updated can run for many years. Redesign when the site stops doing its job, not because a calendar says so.
Will a redesign hurt my Google rankings?
It can, if URLs change without redirects or if content that was earning traffic is removed. Handled carefully, with redirects mapped and valuable pages preserved, a redesign should not cost you visibility. Short-term fluctuation after any migration is normal.
Can I keep my existing content?
Often yes, and you usually should where it still holds up. Photography, service detail, and company history frequently carry straight over. Thin or outdated material gets rewritten.
Should I change my domain at the same time?
Only if there is a real business reason, such as a name change. Changing domain and rebuilding at once stacks two risky migrations together and makes it much harder to tell which one caused a problem.