Most scans are for the person who ran them. Reports are for everyone else: the client who wants a monthly readout, the auditor asking for evidence that something got fixed, the standup where someone has to summarize the last sprint.

The Reports section turns your scan history into a clean, branded document you can hand off. Reports are gated to Core and above. See Pricing for tier details.

What a report contains

Pick a period (last 7, 30, or 90 days) and choose which sections to include. A report can pull together:

Executive summary. The current score and the headline takeaway.
Web Scan breakdown. Score by category, so the reader sees where the site is strong and where it isn’t.
Top issues. The highest-impact findings, ranked.
Recommendations. What to do about them.
Code Scan. Source-audit findings, if you’ve linked a folder.
Analytics. Traffic and search trends, if those integrations are connected.
Uptime. Availability over the period, if uptime monitoring is connected.
Deployments. What shipped, if GitHub is connected.

Every section is a toggle. Reviewing for an external auditor and not sharing traffic numbers? Turn the Analytics section off and it’s gone from the output.

Branding

A report carries your branding, not ours:

Company name in the header.
Logo (PNG, JPG, WebP, or GIF, up to 2 MB).
Primary color for accents.
“Prepared for” client name.
Footer text (defaults to “Confidential”).
Hide attribution, which removes the “Generated by SiteCMD” line for white-labeled output.

Branding is saved per project, so you set it once and every later report inherits it.

Generating a report

Open Reports from the sidebar.
Pick the period and toggle the sections you want.
The preview updates as you go.
Click Export PDF for a print-ready file, or Save HTML for a self-contained web page.

Export formats

Two formats, both generated locally:

PDF. A real, native PDF rendered by SiteCMD (not a browser print), so the layout is consistent wherever it’s opened.
HTML. A single self-contained .html file with styles inlined and no external dependencies. Opens in any browser.

Report history

Each generated report is saved to the project’s history. You can:

Re-open old reports
Re-export to a different format
Delete reports you don’t need

Report history lives in your local SiteCMD database. Reports aren’t uploaded anywhere.

SiteCMD doesn’t publish reports to a URL. The HTML you export is yours to share however you want:

Email it
Drop it in a Slack channel
Host it on your own intranet

There’s no public, hosted, shareable URL for reports, and there won’t be: the local-first commitment means there’s no reports server to run. If you need a hosted version, the exported HTML drops straight into your own static hosting (S3, Cloudflare Pages, GitHub Pages).

CSV exports

For raw data instead of a stakeholder-facing document, the Activity page has an Export CSV button. It writes the timeline of events (scans, deploys, uptime incidents, analytics anomalies) as a row-per-event CSV, ready for a spreadsheet or another tracker.

What reports do not do

No scheduled report delivery. You generate reports on demand. There’s no “email me a report every Monday” yet.
No collaborative editing. Reports are exports, not living documents. If you need to add commentary, do it after export in whatever tool you’re sharing it through.
No multi-project rollup. Each report covers one project. A “portfolio health” view across projects is on the roadmap; for now you generate per-project reports and combine them externally.