Web Design
Is Your Website Actually Being Maintained? A Small Business Checklist
A website that was built once and never touched again is a common small-business blind spot. Here is what managed hosting and maintenance should actually include, and a short checklist to find out whether anyone is really looking after yours.
A hosting bill going out every month is not proof that anyone is actually maintaining your website. Hosting keeps a site reachable. Maintenance is a separate, ongoing job: watching uptime, tracking renewal dates, and being the person who picks up when something needs to change. A lot of small-business sites have the first without the second, and the gap between them is where the real cost shows up.
Hosting Is Not the Same as Maintenance
A website built by a freelancer and hosted on whatever provider was cheapest at the time usually works fine on day one. The question is what happens in month eighteen, when a domain renewal notice goes to an inbox nobody checks, the site slows down as it accumulates images and old plugins, or a customer tries the contact form and nothing arrives. None of that shows up on a hosting invoice. A hosting bill pays for the server. Maintenance is someone actually watching the site and fixing what the hosting bill alone never covers.
What Actually Breaks When Nobody Owns Renewals and Monitoring
Domain registration and a site's TLS certificate fail in different ways, and conflating them leads to the wrong fix. For gTLDs such as .com, registrars are required to send renewal notices before a domain's expiration, but a notice that nobody reads does not stop the domain from lapsing: once it does, the site typically goes unreachable or shows the registrar's own parked-domain page, not your homepage. A certificate is a separate piece entirely. When it expires, visitors get a browser security warning instead of either of those. Most modern hosting handles certificate renewal automatically, which cuts down on manual work, but automation itself can still fail quietly from a validation, DNS, or issuance problem, so it does not remove the need for someone to actually watch for an expiry or renewal-failure alert. Uptime failures are quieter still: a site that goes down with nobody monitoring it is usually first noticed by a customer who gives up and calls a competitor instead of telling you.
What Managed Hosting and Maintenance Should Actually Include
"Managed" gets used loosely by a lot of hosting providers. At minimum, a website that is genuinely being maintained should have each of the following in place, not just a hosting bill that shows up every month.
- 1. Hosting with the basics handled:
- a real hosting platform with SSL, DNS, and automated backups configured and verified, plus a CDN where the site's traffic or audience actually calls for one, not left to whatever the default settings happened to be.
- 2. Uptime and performance monitoring:
- continuous monitoring that alerts a person when the site slows down or goes offline, plus a recurring test that actually submits the contact form and confirms delivery, since a site can return a normal page while its form, email relay, or CRM connection has quietly stopped working.
- 3. Domain and DNS ownership:
- domain registration, DNS records, and certificate renewal tracked by someone specific, with enough lead time to act before anything lapses.
- 4. Platform updates on a schedule:
- the content management system and its plugins or themes patched routinely. That is one layer of the security picture, alongside admin account protections, a firewall or security plugin, and tested backups, which our earlier look at why small-business websites get hacked covers in depth.
- 5. A real point of contact:
- an actual person who can make a content change, add a page, or fix a broken form without the request disappearing into a ticket queue.
- 6. Change-support turnaround:
- a known answer for how long a routine content request actually takes, not an open-ended "we'll get to it."
A Short Self-Check
Ask whoever currently hosts or built your site these questions. If more than one comes back as "I'm not sure," the site is running on nobody's active attention.
Who is specifically responsible for renewing the domain and certificate before they lapse, and how much lead time do they get? Is anything monitoring uptime and performance, or would a customer be the first to notice if the site went down? When was the contact form last actually tested end to end, not just loaded in a browser? How often are the platform and its plugins actually patched, and by whom? If you need a content change today, who do you call, and how long does that usually take? And could you answer all of that right now, or would you have to go find out?
How Cyber One Solutions Helps
Our website design, hosting, and maintenance services bundle design and development, managed hosting, scheduled maintenance and patching, security monitoring, performance and uptime monitoring, and domain and DNS management as one offering, with a real person on our team for the day-to-day requests that otherwise fall through the cracks. The security side of that patching work runs alongside our managed cybersecurity services, and for a business that wants its website handled by the same team managing everything else, it pairs naturally with our managed IT services. If you are not sure what your current setup actually includes, or want to talk through specifics like form-delivery testing or change-request turnaround for your situation, contact us and we will look at what you have before recommending anything new.
Frequently Asked Questions
How do I know if my website is actually being maintained or just hosted?
Hosting keeps a site reachable. Maintenance is the ongoing work of patching the platform, monitoring uptime, and renewing the domain and certificate before they lapse. If nobody can tell you when the site was last updated, who would notice if it went down, or who owns the next renewal date, it is hosted, not maintained.
What is the actual difference between a domain lapsing and a certificate expiring?
A lapsed domain registration usually makes the site unreachable or shows the registrar's own parked page, even though registrars of gTLDs such as .com are required to send renewal notices first. An expired certificate is a different failure: the site is still there, but visitors get a browser security warning instead of the page they expected. Fixing one does not fix the other, so it helps to know which one actually happened.
Do I need a developer to maintain my site, or just a hosting plan?
Most ongoing maintenance, patching, monitoring, and renewals do not require custom development work. It requires someone actually doing it on a schedule. A managed website plan typically bundles that ongoing work with hosting, so there is one point of accountability instead of a hosting bill and a separate, informal arrangement for everything else.
What should I ask a hosting provider before signing up?
Ask directly who owns domain and certificate renewal, whether uptime monitoring is included or sold separately, how content changes get handled and how fast, and who patches the platform itself. A provider that cannot answer those clearly is likely selling hosting space, not website maintenance.