Hosting and maintenance are the two parts of a website people forget until something stops working. Hosting is where your files live and the server that answers visitors; maintenance is the ongoing work of keeping that server, the platform underneath and the content on it safe and usable.
What hosting actually does
A hosting account provides the server, the storage, the software that serves your pages and the address that maps your domain to them. Most small business sites sit on shared hosting, where several sites share a server, or on managed platforms designed for a specific stack.
Cheap shared hosting is fine for small sites, but it has limits on traffic spikes, support response and how quickly problems are noticed. The most important factor is usually not the hardware specification but whether someone is watching. A site that goes down quietly at night is worse than a slightly slower site with monitoring.
What maintenance covers
Platform and plugin updates are the core. Every update exists because something was found and fixed, so an outdated site is a known, documented risk. Backups are the safety net, and they only count if restores have been tested.
Maintenance should also include the less visible work: renewing the SSL certificate, patching shared components, checking that forms still deliver mail, cleaning up unused plugins that still run code, and confirming analytics are recording correctly. A small allowance of content changes is usually included, so you are not billed hourly for adding a service or fixing a typo.
Who should do it
There are three arrangements. The developer who built the site maintains it, which is convenient and means one point of contact. Your own team does it, which costs nothing but requires someone to learn the platform. Or a separate maintenance provider handles it, which is useful if you want the relationship independent of a project.
Any of these can work. What does not work is an arrangement where nobody is clearly responsible.
Ask about email as well as hosting
Business email is usually hosted alongside the website, and a silent failure here is expensive: enquiries go nowhere. Confirm how email is delivered and what happens when the server is busy, whether a fallback route exists, and whether backups of your mailboxes exist separately from the site.
Also ask who has access to the mailbox accounts and whether sending is configured in a way that avoids being treated as spam. For most small businesses, this is the least understood and most important part of the setup.
Plan the handover properly
Handover should include written documentation: where the domain is registered, which hosting plan is used, how to run the CMS, what plugins or tools are installed, who holds the accounts and how to renew them. Book a short call to walk through it with the person who will actually operate the site.
Ask for the credentials to be transferred rather than shared, and confirm two-factor authentication is enabled on every account. A site whose administration lives in one person's inbox is a business risk regardless of how well it is built.
Questions to ask a provider
Ask who monitors uptime and how you are told about an outage. Ask how backups are stored, how often, and whether a restore has been tested. Ask which updates are applied automatically and which are reviewed first. Ask for a defined response time for a broken form or a down site, and what happens outside working hours.
Also ask about ownership. Your domain, hosting, CMS and email accounts should be registered to your business. Ask for handover of credentials and documentation of where everything lives. If you leave a provider, this is what makes a move possible.
Watch the recurring costs
Maintenance is a monthly figure and hosting is usually a monthly figure, so plan for both from the start rather than discovering them at renewal. Also account for third-party tools: paid plugins, premium themes, form or booking services, chat tools, analytics subscriptions and email sending plans. Ask which of these are optional, and which the site cannot function without.
A simple ownership checklist
Keep a written record of the domain registrar and login, the hosting account, the CMS admin, the analytics property, the search console property, and any third-party tool logins. Store it somewhere your team can access without asking one person. Most small business website emergencies are partly an access problem before they are a technical one.
For a related view on ongoing work, our website development guides cover hosting, security and performance separately. If you are unsure who is currently responsible for your site, tell us what you have and we will review the arrangement with you.
Common questions
Do I need a maintenance plan for a small website?
In most cases yes, because every site needs platform updates, backups, plugin updates and occasional fixes. A site with a CMS is more exposed than a static page, since plugins and themes develop vulnerabilities that are fixed in later versions. Without someone applying updates, a small business site quietly becomes an easy target.
Who should own the domain and hosting accounts?
You should, registered in your business name with your own email address and phone. This matters because a domain is a business asset, and if it is held by a provider's account, moving to another provider becomes a negotiation rather than a transfer. Ask for login details on handover and check that two-factor authentication is enabled.
What should a maintenance plan actually include?
A useful plan covers uptime monitoring, automatic backups with a tested restore, platform and plugin updates, SSL certificate renewal, security patching, minor content changes and a defined response time for problems. Ask what is included, what is billed separately, and whether backups have actually been restored as a test rather than merely recorded.