What Happens After Launch? A Website Care Checklist for Growing Businesses

A launch date creates the impression that a website is finished. In reality, it marks the first day the system has to cope with real people, changing browsers, new content, staff turnover and services that do not stay neatly frozen.

The launch matters. The operating rhythm after it matters for much longer.

We think every website should leave a project with three things: a named owner, a documented care routine and a clear route for problems that exceed the owner’s capability. Without those, even a well-built site drifts.

The first 48 hours

Do not spend launch day looking only at the homepage. Test the actions connected to the business.

• Submit every important form and confirm the record reaches its destination.
• Check notification emails, including spam folders and reply-to behaviour.
• Test telephone, email and booking links on a real phone.
• Confirm analytics and consent behave as agreed.
• Inspect redirects from old URLs.
• Check search-engine access, sitemap and robots rules.
• Review error logs and missing pages.
• Test the site on mobile data, not only office Wi-Fi.

Keep a simple launch record with the time, person responsible and outcome. “We clicked around and it looked fine” is difficult to diagnose later.

Every week: check the routes that make the site useful

For many SME websites, weekly care can be concise.

Enquiries

Submit the primary form. Confirm the lead is stored before relying on email notification. Check that the inbox is monitored and that staff know the response expectation.

Availability and obvious errors

Review uptime alerts, server errors and broken critical journeys. Automated monitoring helps, but it does not know whether the wrong telephone number is displayed.

Security notices

Act on credible platform, framework and plugin advisories. Do not install updates blindly on a live site; use backups and a preview environment where the change carries risk.

The National Cyber Security Centre provides small-business cyber guidance that is broader than website maintenance but useful for ownership, backups, devices and incident preparation.

Every month: review health and content

Dependencies and platform updates

Apply supported updates, remove software no longer used and confirm the site still builds or deploys cleanly. Old dependencies are not a character feature.

Backups and recovery

A backup is only reassuring if it can be restored. Confirm what is backed up—database, media, configuration and code—how long copies are retained and who has authority to recover them.

Performance

Review real-user performance where available, especially the pages that receive important traffic. Look for large new images, third-party scripts and layout shifts introduced by content changes.

Google’s Core Web Vitals guidance explains the main user-centred performance measures. Treat the thresholds as diagnostic signals, not a substitute for watching somebody use the site.

Accessibility regression

New content can introduce inaccessible headings, low-contrast text, missing alternative text and vague link labels even when the original components were sound. Test recent changes with a keyboard and run automated checks, while remembering that automation finds only part of the problem.

Content accuracy

Check prices or ranges, staff details, opening times, service descriptions and regulatory information. Remove expired campaigns rather than letting them become permanent archaeology.

Every quarter: ask whether the site still reflects the business

Quarterly review should move beyond maintenance.

• Which pages contribute to relevant enquiries?
• What do prospects still ask that the site should answer?
• Which services have changed?
• Are case studies current and properly evidenced?
• Are low-value pages competing with stronger ones?
• Do search queries reveal a new information need?
• Has the business entered a new location, sector or audience?

Turn the answers into a short prioritised backlog. A website becomes stronger through deliberate small improvements, not an annual burst of random edits.

Forms deserve their own operating procedure

Forms are often treated as visual components, but they are business infrastructure. Document:

1. where the submission is stored;
2. who receives the notification;
3. what happens when email delivery fails;
4. how spam is handled;
5. how long personal information is retained;
6. who can access and export the records;
7. how a customer is told what happens next.

Do not send personal enquiry data into analytics. Make sure the Privacy Notice reflects the actual flow.

Publishing is a risk boundary

Content management should distinguish saving from publishing. An editor ought to be able to prepare and preview a change without immediately replacing the live page. Images should have clear usage references, and a media file in use should not be deletable by accident.

If the CMS makes every change public instantly, staff will either avoid updating it or make riskier changes under pressure.

Measure decisions, not vanity

Monthly traffic can be useful context, but a growing business normally needs more operational questions:

• Which route produces qualified enquiries?
• Where do form errors occur?
• Which service pages are reached before contact?
• Are visitors finding the evidence they need?
• Are response times affecting the outcome after submission?

Analytics cannot answer all of these. Combine it with enquiry notes, sales conversations and usability observation.

Assign responsibility clearly

A care plan fails when everybody is vaguely responsible. Define:

• a business owner for factual accuracy and priorities;
• a technical owner for security, deployment and recovery;
• a content owner for publishing quality;
• an escalation route for incidents;
• access-review dates for former staff and suppliers.

One person may hold several roles in a small company. Naming them still matters.

A practical minimum schedule

If you need a starting point, use this:

Weekly: forms, notifications, critical errors and urgent security notices.

Monthly: updates, backups, performance, accessibility regression and content accuracy.

Quarterly: business fit, search visibility, enquiry quality, access review and improvement priorities.

Annually: privacy and cookie documentation, domain and service renewals, disaster-recovery exercise, major content audit and platform roadmap.

Adjust the frequency for the site’s risk. A transactional service requires more active monitoring than a small brochure site.

Care is not a retainer-shaped mystery

Ongoing support should state what is monitored, which changes are included, how incidents are handled and what sits outside the arrangement. Avoid paying indefinitely for an undefined promise to “keep things running”.

Our Website Care & Optimisation service is organised around this operating cycle. If the underlying structure is already preventing progress, first consider whether the business needs optimisation or a redesign.