What Happens If Your Website Breaks? Who's Responsible, and What It Costs

At some point, most websites have a moment where something just stops working. A page won’t load, a form stops sending, an image disappears overnight for no obvious reason anyone can immediately explain. It’s rarely a disaster, but the panic of not knowing who’s supposed to fix it, or what it’ll cost, is a genuinely common and completely avoidable problem that a bit of planning solves ahead of time.

The most common reasons a site actually breaks

An expired domain or SSL certificate. Both need periodic renewal, and a missed one is one of the most common causes of a site suddenly going down entirely, seemingly out of nowhere with no warning the owner actually noticed. A plugin or software update conflict, mostly a WordPress-specific headache, where one plugin updates and doesn’t play well with another that hasn’t caught up yet to the same version. Hosting issues, an outage, a resource limit getting hit during a traffic spike, or a hosting account that lapsed on payment without anyone noticing the failed charge in time. A change made without testing, content or design edits that accidentally break something else on the page nobody thought to check afterward.

Who’s actually responsible when it happens

This depends entirely on what got agreed at launch, which is exactly why it should be agreed at launch rather than discovered the hard way afterward during an actual emergency. If you have an ongoing maintenance agreement, the developer or agency handling it is responsible, usually within a defined response time written somewhere both sides can refer to. If you don’t have one, you’re generally on your own to either fix it yourself, for simple things, a login issue, a content mistake, or pay for one-off support at whatever the developer’s hourly or emergency rate happens to be at that point. If the site runs on a platform you manage yourself, a builder, or WordPress you administer, platform-level outages are usually the platform’s responsibility, but anything specific to your own site’s setup is on you to sort out.

What a reasonable support arrangement actually looks like

A defined period after launch, commonly thirty days, where fixes related to the original build are included at no extra charge to you. A clear, separate rate for ongoing maintenance or emergency fixes after that window closes, ideally quoted upfront rather than discovered mid-crisis when you have no leverage to negotiate. A realistic response time stated in writing somewhere, not just implied or assumed based on a friendly conversation during the sales process.

A realistic walkthrough of a common breakage scenario

Imagine a contact form that quietly stops sending emails after a hosting provider changes a setting on their end without notifying anyone. Weeks pass before the business owner realizes they haven’t received a new inquiry in a while, only to discover the form’s been silently failing the entire time. This is exactly the kind of issue a maintenance arrangement with periodic checks would catch quickly, while a site with no oversight at all can lose real business for weeks before anyone notices something’s actually wrong behind the scenes.

What to do right now if you don’t know the answer

If you currently have a website and genuinely don’t know who would fix it if it broke tomorrow, that’s worth resolving before it actually happens rather than after the fact under pressure. Ask whoever built it directly, or get a second opinion from someone else who can look at the setup and tell you honestly where you actually stand right now, today.

The real cost of not knowing this

A broken site during business hours, with no clear plan for who fixes it, often means it stays broken for days while you scramble to find someone, and during that stretch you’re invisible to anyone searching for you or trying to reach you online for something urgent. A clear plan, agreed on in advance, is what turns that into a same-day fix instead of a multi-day scramble that costs real business.

How to reduce the odds of something breaking in the first place

Regular small maintenance, keeping software and plugins updated, monitoring that certificates haven’t lapsed, checking core functions like contact forms every so often, prevents the majority of breakages before they ever happen at all. This is exactly what a maintenance plan is actually paying for, not just emergency fixes after something’s already gone wrong, but the ongoing attention that keeps small issues from ever becoming visible problems a customer notices first.

Setting up your own basic monitoring even without a formal plan

If you’re not paying for ongoing maintenance, a free tool that simply checks your site is loading every so often and emails you if it goes down catches problems faster than waiting for a customer to mention it, or worse, never mentioning it at all and just quietly going to a competitor instead. This takes a few minutes to set up and gives real peace of mind that something will catch a serious outage even without a formal support arrangement in place, and it’s a reasonable stopgap for a small business not yet ready to commit to a paid monthly maintenance plan.

A short list of things worth checking once a year

Even without a formal maintenance plan, a yearly self-check catches a lot. Confirm the domain and SSL certificate both show a renewal date well in the future. Test the contact form yourself by actually submitting it and confirming the email arrives. Click through the main navigation links to confirm nothing’s quietly broken since the last time anyone looked closely. This whole check takes maybe fifteen minutes and catches problems while they’re still small and easy to fix.

Keeping a simple record of who to contact

Write down, somewhere easy to find later, who built your site, how to reach them, and what your support arrangement actually covers. This sounds obvious, but a surprising number of business owners lose track of this basic information within a year or two, especially if the original build happened during a busy period and the details never got written down anywhere beyond an old email thread nobody can find anymore when it actually matters.

Thirty days of post-launch support comes included with every build here, and ongoing maintenance is available after that at a stated monthly rate, no surprises waiting down the road.