Who takes care of your website after launch
Hosting keeps running whether anyone remembers it or not
An email arrives every month, plain subject line, an amount, a due date. It comes from your hosting company, and after the first year it stops feeling like anything at all.
That gap is exactly where the risk lives. Hosting is a computer your site lives on, rented on a recurring basis. It doesn't pause because the project ended. It keeps running until someone stops paying for it, on purpose or by accident.
The one-time cost of building a site and the ongoing cost of hosting it often land on the same invoice at launch, which is part of why the two get confused. They aren't the same thing, and mixing them up is how a renewal notice ends up ignored.
Ask three plain questions now: whose card is on file, what the renewal price will be, and which inbox the notice actually lands in. How ongoing costs like this typically get structured is covered fully in what drives the cost of a website.
Backups and whether anyone has actually checked them
A backup toggle sits switched on in a dashboard nobody has opened since launch. It's been that way for months, doing something, though nobody could quite say what.
A backup that has never been restored is a guess dressed up as a safety net. The only way to know it works is to pull a copy out somewhere other than the live site and confirm it opens cleanly.
A hosting plan that advertises backups isn't the same as a hosting plan that has ever produced one you can actually use. Read what's included. Don't just assume the box is checked.
Does your website actually have backups, and who can restore them is the full checklist, covering where copies are stored, how far back they reach, and who holds the ability to run a restore when it matters.
Updates and security patching over time
Plugins push updates on their own schedule. So does the platform underneath them. None of it waits for a convenient week or checks whether anyone's paying attention.
Skipping those patches is one of the plainer ways a site gets compromised, sometimes months after the last time anyone looked at the admin panel. A patch that breaks something else is nearly as disruptive as the vulnerability it was meant to close.
That's exactly why this can't run unattended. Somebody needs to apply updates, watch for the one that causes a problem, and know how to roll it back.
Why a website needs updates after it's already live covers what that ongoing work actually involves.
What happens when the site breaks, and who gets the call
A site can go dark at midnight on a Saturday and stay that way until Monday, when a customer finally mentions it in passing. Whether that gap is minutes or days depends entirely on who's set up to notice first.
Decide this while nothing is broken: who gets the first alert, what they're expected to do with it, and how long is a reasonable wait before you look elsewhere for help. What actually happens in the first hour your website goes down walks through that response in detail.
And if the person who's supposed to fix it has gone quiet on you entirely, what happens if your designer stops answering email covers that specific, uncomfortable version of the same problem.
Domain and certificate renewals that lapse without a sound
A padlock icon disappears from the browser bar, and a customer texts to ask if something's wrong. The certificate behind it expired quietly, on its own separate clock from everything else on this list.
A domain name runs the same way, renewed on its own schedule through a registrar with no connection to your hosting company. Both send a reminder email or two and then go silent. Set your own reminder for each renewal date, separate from whatever the registrar or certificate provider sends, because a missed automatic notice is common enough that it shouldn't be your only line of defense.
The domain and SSL renewals nobody remembers until they lapse lays out that full calendar, including what it actually takes to lose a domain outright.
How a site is supposed to keep changing after launch
A launched site describes the business as it existed on one specific day. The business kept moving. A second location opened. A service list changed. The site, left alone, stayed exactly where it was.
A homepage that still lists only the original address, two years after a second location opened, is what this neglect looks like in practice. Nobody decided to leave it that way. Nobody was ever assigned to catch it, which is the actual problem, not any single missed update.
Small, ongoing edits are supposed to keep happening well past launch, as a normal part of running the business online rather than an afterthought. How a website is supposed to grow after the launch date covers what that looks like month to month.
That's distinct from the point where the whole structure has outgrown small fixes and needs a full redesign instead, covered in how to redesign a website without losing what works.
Who's responsible by default, and who should be in writing
Unless a contract says otherwise, a builder who finishes a project owes nothing once the invoice clears. That's a fair arrangement on its own. Nobody signs up for unpaid work indefinitely, and expecting free upkeep forever isn't reasonable either.
What shouldn't be left to default is who actually owns the accounts that keep the site alive, covered fully in who owns your website, and whether you'd rather someone else handle the ongoing care for a fee, covered in is a website maintenance plan worth paying for.
A verbal understanding rarely survives a falling-out. Put both answers in writing while the relationship is still good and nobody has anything to argue about. Or decide plainly that the job is yours. Either one works. Leaving it undecided is how a site ends up with nobody minding it at all.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go