Two jobs, one outcome
Hosting is the server and the connection. Maintenance is the work done on the site itself. A fast host can't fix an unpatched site, and careful upkeep can't save a host that keeps going down.
Website hosting is where your site lives and how it reaches visitors. Maintenance is the ongoing work that keeps it secure, fast, accurate and findable once it's live. Every site needs both, and who owns each one belongs in the conversation before a custom website build starts, not after launch.
Most websites don't fail at launch. They fail slowly: a security update nobody ran, a certificate that expired over a long weekend, a contact form that quietly stopped sending, a domain renewal billed to a former employee's card.
Key Takeaways
Downtime costs more than the outage
Google slows its crawling when a server keeps returning errors, and drops pages that stay unavailable. Repeated outages can show up in search after the site is back.
Maintenance includes search
Watching Search Console, AI crawler access and contact forms is maintenance too. A site can be fully patched and still be losing enquiries.
Ownership keeps you free to move
When the domain, hosting and analytics accounts are in the business's name, changing providers is a project. When they aren't, it's a negotiation.
Best For
If your site takes enquiries, bookings or payments, put hosting and maintenance under one accountable owner with terms in writing. If it's a brochure that rarely changes, lighter upkeep can work, but renewals, backups and security updates still need someone's name on them.
What's the difference between website hosting and website maintenance?
Hosting is the service that stores your website and serves it to visitors: the server, the connection, the security certificate and the infrastructure behind them. Maintenance is the work done on the website itself after launch: updates, backups, fixes, monitoring and content changes. A site needs both, and a failure in either one looks the same to a visitor.
| Hosting | Maintenance | |
|---|---|---|
| What it is | Where the site runs and how it reaches visitors | The ongoing work that keeps the site sound |
| What it covers | Servers, uptime, bandwidth, security certificates and server-level backups | Software updates, tested backups, monitoring, fixes, and content and search checks |
| What failure looks like | The site is slow or unreachable | The site loads, but it's insecure, outdated or quietly broken |
| Who usually handles it | A hosting provider, or the developer who built the site | The developer or an in-house team, by agreement |
Ask about both separately. "Hosting included" on a quote can mean the server and nothing more, with updates, fixes and monitoring left for someone to notice later.
If your site runs on a builder subscription, hosting and much of the upkeep come bundled in, along with the platform's limits. Here's when a custom website beats a website builder.
What does website maintenance include?
Website maintenance covers security updates, tested backups, uptime and error monitoring, renewals, checks on forms and tracking, performance, search and AI visibility, and keeping content accurate. Some of it runs automatically; the rest needs a person looking. The test of a maintenance plan is what gets checked, how often, and who acts on it.
| Area | What gets done | What happens if it's skipped |
|---|---|---|
| Security updates | Platform, framework and dependency updates applied and tested | Known vulnerabilities stay open on a public site |
| Backups | Regular copies of the site and its data, with restores tested | A backup that's never been restored may fail when you need it |
| Uptime and error monitoring | Alerts when the site goes down or starts returning errors | Outages are found by customers, not by the people paid to fix them |
| Renewals | Domain, security certificate and paid services renewed on time | The site disappears or shows a browser security warning |
| Forms and tracking | Contact forms, booking flows and conversion tracking tested | Enquiries stop arriving and nobody can tell when it started |
| Performance | Page speed and mobile layout checked after changes | The site slows down one update at a time |
| Search and AI visibility | Search Console errors, sitemaps and AI crawler access reviewed | Pages drop out of Google or AI answers without anyone noticing |
| Content accuracy | Hours, services, team and contact details kept current | Search engines and assistants repeat outdated information |
The Canadian Centre for Cyber Security's top security measures for small and medium organizations (February 2024) put patching software and backing up data among the first four controls to start with. They also say to test backups regularly, and to make sure an outsourced website's host has security measures in place.
What happens to your search rankings when your website goes down?
A brief outage usually leaves rankings intact, because Google keeps pages it has already indexed while it retries. Repeated or prolonged outages are different. When a server keeps returning errors, Google slows how often it crawls the site, and pages that keep failing are eventually dropped. Assistants that can't reach a page can't cite it either.
Google's documentation on how HTTP status codes affect its crawlers (last updated February 2026) sets out the mechanics: server errors make its crawlers back off, indexed pages are kept for a while, and URLs that persistently return a server error are removed. Crawling picks back up gradually once the server responds normally again.
Monitoring is the fix. An alert that reaches someone quickly keeps an outage short; finding out from a customer a week later is how it becomes a search problem. Ongoing SEO and AEO work watches the same signals from the search side, and if you suspect past outages have already cost you, what a full SEO and AEO audit includes is the place to start.
Does your website need to be hosted in Canada?
For most private businesses, no. Canada's federal private-sector privacy law, PIPEDA, doesn't prohibit storing or processing personal information outside the country. The business stays accountable for that information wherever it's hosted, though, and must tell people it may be processed in another jurisdiction. Public bodies and some provincial laws can set stricter rules.
The Office of the Privacy Commissioner of Canada's guidelines for processing personal data across borders set out the position. Transfers for processing are allowed, the business must protect the information through its contract with the provider, and it must be open with customers that the information may be accessible to foreign courts and authorities.
Those guidelines don't cover public-sector bodies or provincial private-sector privacy laws, so public organizations should confirm their own rules before choosing a host. For everyone else, if the site collects more than a name and an email address, ask where the data is stored and get the answer in writing.
Who should own your domain, hosting and website accounts?
Your business should. The domain should be registered to the business in a registrar account it controls, and the business should hold administrator access to hosting, analytics, Search Console and every paid service the site depends on. Your developer can have the access needed to do the work. Ownership stays with you.
- The domain, registered to the business with a business email as the contact
- Administrator access to the hosting account, or a written right to move the site
- Owner access to Search Console and analytics
- The site's code, content and media, with handover terms stated
- A list of every paid service the site depends on, with renewal dates
- Passwords kept in the business's own password manager, not someone's inbox
Ownership is what keeps every provider replaceable. It's also the clearest test of what you keep when an agency contract ends, and what you've only been renting.
Should the company that built your website also host and maintain it?
Often, yes. The team that built the site knows how it's put together, so updates and fixes start from knowledge instead of guesswork, and there's one accountable owner when something breaks. The trade-off is dependence, and the answer to dependence is ownership: the domain and accounts in your name, and the terms in writing.
| Setup | Works well when | Watch for |
|---|---|---|
| Your developer hosts and maintains | The site is custom-built and takes enquiries, bookings or payments | Accounts in the developer's name, and vague terms |
| Separate host, developer maintains | You already have a hosting provider you trust | Two parties pointing at each other during an outage |
| Separate host, in-house maintenance | You have technical staff with time set aside for it | Updates that slip when the team gets busy |
| No maintenance arrangement | Rarely the right call for a business website | Problems found by customers first |
We host and maintain the sites we build. The people who built your site are the ones keeping it running after launch, so there's no handover between companies for anything to get lost in.
How do you change web hosts without losing rankings?
Move the site with its URLs unchanged, and test everything on the new host before you point the domain at it. A host change carries far less risk than a redesign, but security certificates, redirects, robots.txt rules and AI crawler access all have to carry over exactly, or pages can drop out of search without anyone noticing.
- Copy the site and test it on the new host before switching anything
- Confirm the security certificate, redirects and robots.txt rules match the old setup
- Shorten the domain's DNS cache time (TTL) a day or two ahead, then switch the domain
- Keep the old hosting running until the new setup is confirmed
- Watch Search Console for crawl and server errors in the days after the move
If the move also changes your URLs, platform or domain, it's a migration, not a host change. Here's how to protect rankings during a rebuild or domain move.
What should a website hosting and maintenance agreement include?
It should say exactly what's included, how often each task happens, who responds when the site goes down and how quickly, who owns which accounts, and what you receive when the agreement ends. Vague coverage such as "ongoing support" is where disputes start. If a task isn't written down, assume nobody is doing it.
- What's included, task by task, and what's billed separately
- How often updates, backups and restore tests happen
- Who is alerted when the site goes down, and the agreed response
- Which accounts are in the business's name, and who else has access
- How content changes are requested and how quickly they're made
- What you receive at the end: code, content, data and access
A promised uptime figure is only as useful as what happens when it's missed. Ask what the remedy is, not just the number.
So, what does your website need after launch?
Reliable hosting, maintenance with named tasks and a named owner, monitoring that reaches someone quickly, and a domain and accounts that stay in the business's name. Treat launch day as the start of the site's working life, not the end of the project, and put the terms in writing before it goes live.
I'm the practitioner on every SyncDS engagement, and we host and maintain the sites we build, alongside the search work that keeps them findable. If your site is already live and nobody is clearly responsible for it, start there.
Frequently Asked Questions
How much should I pay for website maintenance?
It depends on what the site does. A brochure site needs far less than one that takes bookings, payments or logins, and a custom build with integrations needs more attention than a single page. Compare quotes by the tasks and response times they include, not the monthly figure. A low price that excludes fixes isn't a saving.
How often does a website need maintenance?
Some of it runs continuously, such as uptime monitoring and automated backups. Security updates should be applied as they're released, after testing. Forms, tracking, Search Console and content are worth checking at least monthly, and after any change to the site. A site that changes often needs closer attention than one that rarely does.
Can you have a website without hosting?
No. Every website runs on a server somewhere, even when the hosting is bundled into a subscription and you never see it. The real questions are who controls that hosting and whether you can move the site if you need to.
What happens if my domain name expires?
Your website and any email on that domain stop working. Registrars usually allow a short window to renew, but the terms vary, and once it passes, anyone can register the name. Set the domain to auto-renew, keep a current payment card on file and make sure renewal notices reach an inbox the business controls.
Is website maintenance necessary for a small website?
Yes, though it can be lighter. Even a small site runs software that needs security updates, a domain and certificate that need renewing, and forms that need to keep sending. What a small site can usually skip is frequent content work and deep performance tuning.
Does website maintenance include content updates?
It depends on the agreement. Some plans cover technical upkeep only, while others include a set amount of content changes. Ask how changes are requested, how quickly they're made and whether there's a limit. A well-built admin panel lets your team handle routine edits without waiting on anyone.
Does website maintenance help SEO?
It protects it. Maintenance keeps the site online, fast, secure and free of broken pages, which search engines and AI assistants need before they'll rank or cite it. Building visibility takes search work on top of that: content, structure and authority. Maintenance protects what you have; search work builds on it.
Can I switch web hosts without losing my website?
Yes, if you have access to the site's files, data and domain. Test the site on the new host before switching the domain, keep the URLs the same, and leave the old hosting running until the move is confirmed. Problems usually start when the old provider holds the accounts and the business doesn't.
Who is responsible for my website's security?
Your business is, even when someone else does the work. The host secures the servers, whoever maintains the site keeps its software patched, and your team controls passwords and access. Put each responsibility in writing, use multi-factor authentication on every account, and remove access when people leave.
Can website hosting and maintenance be handled remotely?
Yes. Hosting, updates, monitoring and fixes are all done remotely, and changes can be requested and approved without anyone on-site. We're based in Winnipeg and work with clients across Canada and any English-speaking country.