Website care plans and audits: what they include and when to use them

Guide / Post-launch

MARTINSWORKS
Studio

How to tell whether the site needs a one-off audit, ongoing support, or both.

Website care plans and audits: what they include and when to use them

Websites drift over time. Content changes, performance slips, and pages slowly lose their shape. Audits and care plans are two ways to get things back under control without defaulting to a rebuild.

The key is choosing the right one for the state the site is in.


What a useful audit should cover

A useful audit is not just a technical report. It should cover:

  • structure and navigation
  • content clarity and page hierarchy
  • mobile usability
  • accessibility and performance basics
  • a prioritised list of actions

The value is not only in the findings. It is in the ranking. A good audit tells you what matters first.


When an audit is the better first move

Start with an audit when:

  • enquiries have slowed without a clear reason
  • content has grown and the structure feels cluttered
  • editors have been patching around the site for months
  • the team no longer agrees on what should be fixed first

An audit is about diagnosis and prioritisation.


What a care plan is really for

A care plan is not just "support hours". It is a way to stop the site slipping back into neglect after launch or after a round of improvements.

It usually includes:

  • regular updates
  • routine checks
  • fixes for smaller issues
  • follow-on improvements
  • someone keeping watch on quality drift

Care plans are about continuity.


One common pattern

Often the best route is an audit first, then a care plan.

That works when the team knows the site is drifting but cannot yet say whether the issue is mostly clarity, technical quality, governance, or all three.

The audit tells you where to act. The care plan keeps those fixes in place.


What not to expect

An audit will not magically improve the site on its own. It gives you the map.

A care plan will not replace a deeper reset if the structure is already badly misaligned. It helps keep a basically sound site healthy.

That distinction matters because the wrong choice usually wastes time, not just money.


Which one to start with

If your site is business-critical and mostly healthy, a care plan reduces risk. If you are unsure what to fix first, an audit is the better starting point.

For practical post-launch routines, pair this with the first 30 days after launch and website governance for lean teams.

Put this into practice

If this mirrors your situation, compare it with services, how projects run, or use the Start a project pack.

Keep the site in shape

Next reads on launch follow-up, measurement, upkeep, and the routines that stop drift.

The first 30 days after launch: what to check

A first-month review plan for catching issues before they become habits.

Read article

What to measure after a website relaunch

The post-launch signals that tell you whether the new site is clearer, easier to use, and doing a better job commercially.

Read article

Website governance for lean teams (monthly rhythm)

A simple monthly routine for teams that need the site to stay accurate after launch.

Read article

Need the site to do a better job?

Send a short outline and we will come back within two working days with a sensible next step.

If you are still gathering input internally, start with the project pack.