Your website is live. What happens now?

Launch day feels like the finish line. The copy is approved, the contact form works, the domain is connected and you can finally send customers the link.

Then a few weeks go by and the website simply sits there.

Until a phone number changes. A card used to pay for a service expires. A form stops delivering messages. An old promotion is still visible months later. Nobody remembers who controls the domain. Or a customer is the first person to tell you that something is broken.

That is when the question appears: who is responsible for the website after launch?

The answer is not automatically a monthly maintenance package full of technical tasks. It is also not realistic to assume every website will run forever without attention. The useful answer is to know what needs care, who owns each responsibility and how important the website is to the business.

The short answer: after launch, a website needs ownership

Not just legal ownership. Someone needs to know which accounts matter, what must keep working, what gets checked and who responds when something goes wrong.

In practice, there are seven areas worth making clear:

• domain, hosting and important accounts;
• forms, payments, bookings and other actions that create business;
• content that can become outdated;
• security and updates when the technology requires them;
• backups or another clear way to recover the site and its data;
• search visibility and changes that may affect traffic;
• support: who responds when you need a change or something stops working.

Not every website needs the same level of care. That distinction matters.

1. Make sure the important accounts are actually under control

A business can have a working website for years and still have no idea which email owns the domain, who pays for hosting or which person has the only administrator password.

That feels harmless until you need to switch providers, renew a service, recover an account or fix an urgent problem.

Before talking about maintenance, confirm the basics:

• Who is the domain registered to?
• Which email receives renewal notices?
• Who controls the hosting or website platform?
• Does the business have administrative access, or does everything depend on one person?
• Where are important credentials stored securely?
• Which outside services does the website depend on and who pays for them?

You do not have to manage everything yourself. The business should still know what exists and retain reasonable control of its digital assets.

2. Check the parts that create business, not only whether the homepage loads

A website can look perfectly healthy while the part that matters is failing.

For example:

• the form shows a success message but the email never arrives;
• the WhatsApp button still uses an old number;
• the booking page opens but no dates can be selected;
• a payment fails only on mobile;
• confirmation emails land in spam;
• a quote button points to a page that no longer exists.

A useful check does not stop at Is the website online? It asks whether the important customer actions still work from beginning to end.

If the website exists to generate inquiries, the form matters more than a decorative animation. If it sells, the checkout matters. If it takes bookings, test the booking flow.

3. Information needs maintenance too

Some websites are technically healthy but make the business look careless because the information is no longer true.

Old hours, discontinued services, outdated prices, photos of a team that changed, expired promotions or pages that describe a process the company no longer uses can all create confusion.

That is not a technology problem. It is an ownership problem. Someone needs a simple routine for checking the information customers actually depend on.

You do not need to change content every week just to look active. Update what is no longer accurate, add what genuinely helps and remove what can mislead people.

4. Security and updates depend on how the site is built

There is no useful one-size-fits-all rule here.

A simple website may have very few moving parts. Another site may use a content system, online store, database, customer accounts, payments or external tools that need more attention.

The more business-critical pieces a site has, the more important it becomes to know who watches for updates, access problems and security issues.

A business owner does not need to learn the technical vocabulary. The useful question is simpler: if an important update or security issue appears, who knows about it and who decides what happens next?

Ignoring outdated software can create risk. Applying changes carelessly can also break things. Good maintenance is not update everything blindly. It is making changes responsibly and checking that the website still works afterward.

5. A backup only helps if recovery is clear

Backup appears in almost every maintenance offer, but the better question is: if something goes wrong tomorrow, can we return to a working version without improvising?

Depending on the project, recovery may involve copies of data, previous content versions, project files or recovery features provided by the platform.

A simple brochure site and an online store do not carry the same risk. Losing a page revision is different from losing customer or order information.

Recovery should match what can actually be lost, not simply appear as a reassuring word in a proposal.

6. Launch does not mean you stop paying attention to search

You do not need to check rankings every day, and you do not need to keep rewriting pages to please a search engine.

But if the business depends on people finding the website, it helps to know whether important pages remain visible and whether search traffic changes in a meaningful way.

Search Console can show queries, clicks and indexing issues. The point is not to obsess over every movement. It is to notice changes that deserve investigation.

If an important page disappears from search, diagnose the problem before changing everything.

7. Maintenance does not mean unlimited development

This distinction prevents a lot of frustration.

Fixing a form that stopped working may be support. Updating a photo or business hour may fit content maintenance. Building a new booking system is a new project.

If a plan promises unlimited changes, ask what that actually means. Websites can evolve, but new features, new sections and major redesign work still require design, development and testing.

A useful agreement separates:

• preventive checks;
• fixing something that broke;
• small content changes;
• new features or larger improvements.

That is not about making the agreement complicated. It is about setting expectations before something becomes urgent.

Does every website need a monthly maintenance plan?

No.

A small informational site with stable content and few moving parts may do perfectly well with periodic checks and support when needed. An online store, customer portal or business application usually needs clearer ongoing ownership.

Company size does not decide this by itself. A small business can depend entirely on its online store, while a large company may have a simple corporate site that rarely changes.

Three reasonable ways to handle support

There is no single correct model.

1. Handle it internally

This works when someone on the team understands the accounts, can keep information current and knows when a technical issue needs outside help. The important part is that the responsibility is real, not vaguely shared by everyone.

2. Request support when needed

This can be enough for simple sites that change infrequently. It helps to know who you will call before there is an emergency and how one-off work is priced.

3. Keep an ongoing care plan

This makes more sense when the website changes often, supports an important process or when the cost of failure is higher than the cost of prevention. A useful plan should explain what gets checked, which small changes are included, expected response times and what is outside scope.

Before a website project is considered finished, ask these questions

1. Who controls the domain and how is it renewed?
2. Where is the website hosted and who controls that account?
3. Which other services or licenses does the site depend on?
4. What happens if a form, payment or integration fails?
5. Is there a clear way to recover the site or its data?
6. Who handles security and updates when they are required?
7. How are small content changes requested?
8. What counts as maintenance and what becomes a new project?
9. How long is support included after launch?
10. What happens if we want to work with a different provider later?

Signs that nobody is really looking after the website

• nobody knows who controls the domain;
• renewals depend on the personal card of someone who no longer works with the business;
• forms are only tested after a customer complains;
• important information is clearly outdated;
• there is no named person responsible for problems;
• nobody knows what would happen if the site or its data had to be recovered;
• every small change starts with searching for someone who can help.

That does not mean you need the most expensive plan available. It means ownership is missing. Someone should know what exists, what matters and who responds.

What if the budget is limited?

Start with the things that can directly hurt the business.

Make sure the domain cannot quietly expire, customer messages actually arrive, important information is accurate and there is a reasonable recovery path if something goes wrong.

Then add performance checks, search monitoring, content work or other improvements based on how important the website becomes.

You do not need to pay for work your website does not require. You also do not want to discover who was responsible only after something stops working.

The idea to take with you

A website does not need attention because it is inherently fragile. It needs ownership because it belongs to a business that changes.

People change. Services change. Tools change. Customers use the website in new ways. Sometimes technical problems appear too.

Maintenance should not be about inventing work every month. It should keep the website doing its job and make it clear who responds when something changes.

Next step