The report is the product

A maintenance plan is a promise that someone is watching the site. The client cannot see the watching. They cannot see the updates applied at 6am, the backup that ran, the uptime monitor that stayed green. All of that is invisible by design, and invisible work is the first thing a client cuts when money is tight.

The monthly report is the only place that work becomes visible. For most clients it is the whole product. If the report is a list of version numbers, the plan looks like an insurance policy they have never claimed on. If the report shows what was wrong, what was fixed and what it means for their business, the plan looks like a service they would miss.

This article sets out what a maintenance plan report should contain, section by section, and why each section earns its place. It is written for studios of three to fifteen people that sell monthly plans, but the shape works for a freelancer with a handful of clients just as well.

Start with findings, not activity

There are two kinds of report. An activity report lists what you did: plugins updated, backups taken, uptime percentage. A findings report lists what you found: a page with no title, a contact form that no longer submits, an image gallery that has quietly dropped its alt text. Activity is about you. Findings are about the client's site.

Lead with findings. Put the three to five items that matter most at the top, in plain language, each with a one-line note on why it matters and what you will do about it. A client who reads only the first screen should come away knowing the state of their site and that someone competent is on it.

Activity still belongs in the report. It goes further down, as evidence that the routine work happened. The order is the point: the thing the client cares about first, the thing you need on record second.

The sections a good report carries

A one-paragraph summary

Three or four sentences. Is the site healthy, is anything urgent, what changed since last month. Write it so that the owner can forward the email to a business partner without explaining anything.

Findings, ranked

Each finding needs four things: what it is, which page it is on, why it matters and what the fix is. Rank by impact on the business, not by the order your tooling reported it. A missing contact method on the service page outranks a missing Open Graph tag on the blog, even though both are a single line to fix.

Keep the language in the client's world. "Search results show a generic snippet for your pricing page" is a finding. "Meta description absent" is a log entry.

What was fixed

Findings from last month that are now closed. This is the section that makes the plan feel like progress rather than maintenance. If the same finding appears for the third month running, say so, and say why it is still open. Clients forgive an open item with a reason. They do not forgive a report that pretends not to notice.

What changed on the site

Pages added or removed, content edited, redirects set up, forms changed. If the client's own team edits content, this section catches the moment someone pastes a page in from a document with a dozen heading levels, or publishes a page with placeholder text still on it.

Routine work

Updates applied, backups verified, uptime for the month, certificates renewed. One short table. This is the evidence section. It should be boring, and it should be there every month.

Next month

What you plan to do, and anything you need from the client to do it. A plan that ends with a next step reads as a relationship. One that ends with a backup count reads as a receipt.

What a public-page check can and cannot tell you

Most of the findings section can come from checking the site the way a visitor and a search engine see it: the public pages only. Titles, descriptions, heading structure, alt text, a visible way to get in touch, text that is readable on a phone, pages that overflow a narrow screen, keys or credentials that have leaked into public files. None of that needs a login, and none of it depends on which platform the site runs on. A hosted site on Webflow, Shopify or Squarespace reads the same way as a self-hosted one.

What a public check cannot tell you is anything behind the login: plugin versions, user accounts, server configuration, the state of the backups. That is your routine section, and it comes from your own tooling and your own access. A good report combines both and is honest about which is which.

Our hosted website audit is built for the first half. It runs on our servers against the public pages of a site, never logs in and never touches a file. The free check covers up to five pages. The Website Audit Report covers every public page up to 100 and carries your studio's name and logo. It is the findings section of a maintenance plan report, ready to send.

Rules that keep the report credible

  • Every finding is on a named page. "Some images are missing alt text" is a worry. "Four images on /services/ have no alt text" is a job.
  • Every finding has a fix. If you do not know the fix yet, say that, and say when you will.
  • Numbers are real. Uptime is what the monitor recorded. Page counts are what was checked. If the check was capped, say it was capped.
  • The same format every month. Clients learn to read a report by its shape. Change the shape and they have to start again.
  • Short. Two screens on a phone is about the limit for a report that gets read rather than filed.

Make the report the renewal conversation

A maintenance plan that is renewed without a conversation is a plan whose report did the talking. The client opened it, saw that something was found, saw that it was fixed and saw what is coming next. That is the whole job of the document.

If your current report is a list of version numbers, the fastest improvement is to add a findings section at the top, ranked, in plain language, with a page and a fix on every line. The routine work stays where it is. The report just stops leading with it.

See what a website audit report finds on a real site. Get a free website audit: enter a URL and an email, and we check the public pages on our servers. We never log in and never touch your files.