reports · monthly or weekly · client-ready

The best maintenance is invisible. The report is the proof.

When nothing breaks for six months, clients start to wonder what they’re paying for. Our reports answer with a record instead of reassurance: every update performed, every backup taken and verified, the uptime line, what the scans found. Proof, not promises.

001 / what's inside
five sections, zero adjectives

One month of work, itemized.

A report is only as good as what feeds it. Ours is assembled from the same records the dashboard keeps — the updates that ran, the backups that were taken and verified, the uptime checks that fired all month. Nothing in it is written after the fact.

01

Updates performed

Every core, plugin and theme update that ran — each one verified with before/after screenshots rather than assumed fine.

02

Backups taken — and verified

Not “backup completed.” Captured, verified byte-for-byte, and covered by weekly restore drills. The second half is the whole point.

03

Uptime record

Availability and incident history from multi-region checks — every 5 minutes on Economy, every minute on Extended.

04

Scan outcomes

What the broken-link crawls turned up and how visual-regression review went — what was flagged, and what was checked and cleared.

05

Webmatik growth audit (Standard & Extended)

The bundled Webmatik audit attached as a PDF — technical SEO, keyword positions, content gaps, Core Web Vitals — once a month on Standard, twice on Extended.

002 / cadence

A rhythm that matches the plan.

economy
Monthly

The full record: updates, backups, uptime, scan outcomes. Everything that happened, itemized.

standard
Monthly

The full record, plus the Webmatik growth-audit PDF attached — one audit every month.

extended
Weekly

The same report, every week, with Webmatik twice a month — for sites where a month between proofs is too long.

Cadence follows the plan, not an add-on menu. What each tier includes — and what it costs per site — is on the pricing page, in the open.

003 / the portal

Clients can log in, not just read.

The report is the summary; the portal is the source. Clients get their own login with their sites, their reports and their billing — and public status pages they can check whenever they’re wondering if the site is up. Value that stays visible between invoices, without anyone writing a word.

Their sites

Every covered site in one place — no asking, no waiting.

Their reports

Current and past reports live in the portal, not just in an inbox.

Their billing

Invoices and plan details, self-serve. Nobody emails anyone for a PDF.

Public status pages

A live uptime page you can share — running whether or not anyone asks.

004 / why trust it

A report someone writes is marketing. A report generated from the log is evidence.

Every action on your site — every update, backup, check and fix — is logged in the operations dashboard as it happens. The report is a summary of a log that always exists, not prose composed at the end of the month. Want to go deeper than the summary? The log is right there. The engineering behind it — signed commands, per-site secrets, a fully audited pipeline — is documented on the security page.

005 / questions

Report questions, answered.

What's actually in a maintenance report?
The period's work record: every core, plugin and theme update performed; backups taken and verified — including byte-for-byte checks and weekly restore drills; the uptime record with any incidents; and the outcomes of broken-link and visual-regression scans. On Standard and Extended, the Webmatik growth-audit PDF is attached.
How often do reports go out?
Monthly on Economy and Standard, weekly on Extended. Webmatik audits are attached once a month on Standard and twice a month on Extended.
Can my client access anything directly?
Yes. Clients get their own portal with their sites, their reports and their billing, plus public status pages for uptime. The report is the summary; the portal is where they can look any time without asking anyone.
Are the reports white-label?
No, and we'd rather say so than fudge it. Reports are client-ready — written to be forwarded or presented as-is, and they carry the actual work log rather than marketing prose. If your model requires your own brand on every artifact, a self-service tool like WP Umbrella offers white-label reports; what ours carry instead is the evidence, and in our experience proof matters more than the logo.
Do you report on non-WordPress sites?
Yes. Non-WordPress sites run in monitoring-only mode — uptime, broken links, visual regression and Webmatik audits from the public URL — and those results feed the same client reports. Updates and backups are WordPress-only, so a Next.js or static site's report covers the monitoring scope.
the log starts on day one

Make the invisible work visible.

Connect a site and the record starts immediately — updates, backups, uptime, scans. The first report assembles itself from there. If you’d rather see specifics first, send your URL for a free audit.