Your website acts fine until the day it doesn’t. The contact form stops sending. The hours on the contact page are from two winters ago. On a phone over cell data, the homepage hangs long enough for a homeowner to hit back and call the next company.
Then you email the person who built it, and nothing comes back. That is more common than it should be. I have inherited plenty of sites in exactly that shape: an abandoned WordPress install, a DIY builder nobody remembers how to edit, or a “custom” template that looks suspiciously like three other contractor website design jobs in the same county.
If that is where you are, the first move is not panic and it is not automatically a full rebuild. Start by figuring out what you still control, what is actually broken, and what would happen if the site went down tomorrow.
First, find out what you still own and can access
The most important question is simple: can you still get into the things that matter.
You need access to a few separate pieces, and they are often owned in different places:
- the domain name, which is the web address itself
- the website hosting account, which is the server space where the site lives
- the website admin dashboard, if the site has one
- the form notifications, so quote requests and contact messages still reach you
- Google Business Profile and Google Search Console, if someone set them up
If you can log into all of that, your situation is annoying but manageable. If you cannot, you need to sort out access before you worry about design changes.
A lot of owners assume the website is one thing. It usually is not. The domain might be with one company, the hosting with another, and the site itself built on top of that with a theme, plugins, and custom edits. When the original builder disappears, those pieces do not disappear with them, but finding them can take a little digging.
Start with your old emails and invoices. Search for terms like domain renewal, hosting, WordPress, SSL, and backup. You are looking for account names, login portals, renewal notices, and billing receipts. If the card on file is still being charged every month or every year, that statement can tell you where to look.
What is usually going wrong underneath
When a site gets abandoned, the problem is rarely just “the internet being weird.” Usually there is a real maintenance issue under the hood.
On many WordPress sites, the weak point is the plugin stack. A plugin is an add-on that handles one feature, like forms, sliders, backups, image compression, or spam filtering. One plugin by itself is not a problem. Five or ten that all need updates, depend on each other, and were set up by somebody else can become one.
Here is what that often looks like in plain English:
- the contact form plugin updated, but the email settings did not, so leads stop arriving
- the security plugin expired or broke, and now the admin area is locked down or hacked
- the image slider loads huge files, so the page speed on phones gets ugly fast
- the page builder update changed spacing or layout on several pages at once
- the PHP version on the server changed, and the old theme cannot keep up
Even if the site still loads, it may be quietly getting worse. An expired SSL certificate throws a warning. Broken backups mean there is no easy restore if something fails. Old plugins leave holes that bots can find before a human notices anything is wrong.
Then there is the content problem. A lot of sites were built quickly with stock photos, generic copy, and a template that was never really tailored to the business. That is why so many homepages feel interchangeable. Same smiling hard-hat guy. Same “quality service you can trust.” Same layout. A homeowner can smell that from a mile away, even if they could not explain why.
That kind of website for service business use is not always broken in the technical sense. It is broken in the trust sense. If the photos are fake, the copy is vague, and the phone number takes three taps to find, the site is doing a poor job before anyone calls.
How to judge your own site honestly
Do not start with the backend. Start like a customer.
Open your site on your own phone with Wi-Fi turned off. Use cell data. That one step tells the truth faster than most audits.
Look for a few things:
- How long before you can read the first real piece of information?
- Is the phone number visible without hunting for it?
- Can you tell what cities or service areas you cover?
- Do the photos look like your actual work and crew?
- Does the contact form work all the way through?
- Are the hours, service list, and business name accurate everywhere?
Then ask one practical question: if you had never heard of your company before, would this site make you comfortable inviting you into someone’s house.
A second check is to count clicks. If it takes more than one or two taps to call you, request a quote, or confirm you work in their town, that friction matters. People do not study local service websites for fun. They are usually trying to solve a problem and move on.
Another useful test is to ask a recent customer what they thought of the site before they called. Not a marketing survey. Just ask. Did anything confuse them? Did they find the service area easily? Did the site feel current? You will usually get a more useful answer than you expect.
DIY builders and WordPress are not the enemy, but they do have costs
A fair answer here is that plenty of decent sites are built in WordPress or a DIY platform. Those tools exist for a reason.
The issue is not moral failure. The issue is ownership cost over time.
A DIY builder is attractive because it gets a site online quickly. The tradeoff is that design tends to follow the platform’s rules, performance can get heavy once you stack on features, and moving away later can be painful.
WordPress is flexible and widely supported. The tradeoff is that flexibility usually comes from layers: theme, plugins, hosting settings, security settings, backups, updates, and whoever understands how they all fit together. That is fine when someone is actively maintaining it. It is less fine when the one person who knew the setup vanishes.
That is why maintainability matters as much as design. A small business website redesign is sometimes needed because the old site looks dated. More often, it is needed because nobody can safely change anything without risking three other things.
For a local service business, good maintenance is pretty boring on purpose. The site should have working SSL, which is the security certificate that keeps the browser from showing warnings. It should use a CDN, which simply means the files are delivered from servers closer to the visitor so pages load faster. It should have daily backups, security patches, uptime monitoring, and somebody checking that forms still work after updates.
None of that is glamorous. All of it matters.
Decide whether you need repair, cleanup, or a rebuild
You do not always need to throw the whole thing away.
If the site is basically sound and you still have access, a cleanup may be enough. That usually means fixing broken forms, updating old content, tightening security, removing unnecessary plugins, compressing oversized images, and making the mobile layout behave.
If the site is technically fragile, hard to edit, and built around a bloated template or page builder, a rebuild may save money and headaches in the long run. Especially if every small change requires a developer, or worse, a developer who no longer answers.
Good rebuilt sites are simpler than people expect. For most service companies, they need to load quickly on phones, show real work, explain services clearly, make the phone number obvious, cover each service area properly, and give the owner a clean way to update text and photos without touching code.
That is the standard I build to now. Our custom website design for service businesses is hand-built, not assembled from templates or page builders, and launches in 2 to 4 weeks from kickoff. Owners can update text, photos, service areas, and posts themselves through a clean admin dashboard that does not require a developer. That setup is not fancy for the sake of being fancy. It is meant to prevent the exact dependency problem this article is about.
What good looks like for a business your size
For a local contractor, plumber, electrician, or excavation company, good usually looks pretty straightforward.
The site loads fast on a phone. The homepage clearly says what you do and where you do it. The photos are your jobs, your trucks, your crew, not generic stock images. The contact options are obvious. The quote form works. The service pages sound like a real business in a real town, not a template trying to rank everywhere at once.
Underneath, it should also be maintainable. You should know who hosts it, who has access, how backups are handled, and what happens when something breaks. If you stay with an ongoing service, there should be one clear place to call and one clear monthly charge. No scavenger hunt through five vendors and an old Gmail thread.
That is also why we keep hosting and management under one roof after launch. It starts at $50/mo, and it covers hosting, SSL, CDN delivery, daily backups, security patches, uptime monitoring, platform improvements, and support from the same people who built the site. If your current builder disappeared, you already know why that continuity matters.
One practical step to take this week
Make a one-page access list.
Write down where your domain is registered, where the site is hosted, who can log into the website admin, where form notifications go, and who receives renewal emails. Then test the site on your phone over cell data and submit your own contact form.
If you can do those two things and everything works, you are in better shape than a lot of owners. If you cannot, you have found the real problem, and now you know where to start.
