Most scans are for the person who ran them. Reports are for everyone else: the client who wants a monthly readout, the partner asking “is the site healthy?”, the auditor needing evidence of remediation, the team meeting where someone has to summarize the last sprint.

SiteCMD’s Reports section turns scan history into a clean, branded artifact you can share. Reports are gated to Core and above. See Pricing for tier details.

What a report contains

A report covers a configurable period (1 day to 365 days) and pulls together the data SiteCMD already has on your project:

Score history. Daily score across the period, with annotations for scans and deploys.
Active findings. Top issues at the end of the period, ranked by impact.
Fixed findings. What got resolved during the period, with timing.
Regressions. Issues that reappeared after being marked fixed.
Category breakdown. Where the score is improving or declining.
Analytics signals. Traffic, search visibility, uptime trends (if integrations are connected).
Deploy events. What shipped during the period (if GitHub is connected), with score before/after each deploy.

Sections are toggleable. If you don’t want analytics in the report (it’s an external auditor and you’re not sharing traffic data), turn that section off.

Branding

Each report can be customized:

Project name (defaults to the SiteCMD project name)
Report title (defaults to “[Project] Site Health Report — [date range]”)
Logo (upload an image, used in the header)
Color accent (matches your brand)
Custom footer text (your company name, contact info)

Branding is saved per project, so you only configure it once. Subsequent reports inherit the saved branding.

Generating a report

Open Reports from the sidebar.
Pick the project and the date range.
Toggle which sections to include.
Click Preview to see the report rendered in the app.
Click Export to save it.

Export formats

Reports render to HTML by default. From the preview you can:

Download as HTML. A single self-contained .html file with styles inlined, no external dependencies. Opens in any browser.
Print to PDF. Use your browser’s Print → Save as PDF.

The HTML is the canonical format. PDF is just the HTML printed. SiteCMD doesn’t generate its own PDF, which means the output is always exactly what you see in the preview, no font-substitution surprises.

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
Print and physically mail it (unironically a real use case for some compliance work)

If you need a public, hosted, shareable URL for reports, that’s outside SiteCMD’s scope by design (the local-first commitment means we don’t run a reports server). Many teams put the HTML in their own static-hosting setup (S3, Cloudflare Pages, GitHub Pages) when they need a hosted version.

CSV exports

Some workflows want the raw data, not a stakeholder-facing report. From the Issues page, Export → CSV dumps the current filtered view as a CSV. You can filter by severity, category, status, or source before exporting, so the CSV is exactly the slice you want.

Use this for bulk imports into other trackers, for analysis in Excel/Sheets, or for any pipeline that needs the data as a row-per-issue dump rather than a rendered report.

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.