Reports and exports - SiteCMD Docs

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. Local report generation and every export format are part of the complete free workbench.

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. The section labeled this way shows findings and their impact by category, alongside the single SiteCMD Score.
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.

The branding text fields are saved per project, so you set them once and every later report inherits them. The logo stays with the current session; pick it again when you come back.

Generating a report

Open Reports from the sidebar.
Pick the period and toggle the sections you want.
Click Generate Report to open the preview. Generate again after changing its settings.
In the preview, 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 PDF generated locally with a consistent page layout, without using the browser's print dialog.
HTML. A single self-contained .html file with styles inlined and no external dependencies. Opens in any browser.

Report history

Each generated report adds an entry to the project's history. The entry stores its settings and summary metadata, not the exported document. You can:

Regenerate a report using its saved period, section choices, and branding
Export the regenerated report to PDF or HTML
Delete history entries you don't need

Regeneration uses current project data, so it can differ from the original report. Save the exported PDF or HTML if you need an exact historical record. History entries live in your local SiteCMD database and are not automatically uploaded.

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

The local workbench does not publish a report URL. If you need one without connecting the site, upload the exported HTML to your own static hosting.

For a connected site, open Settings → Connected → Shareable Reports and choose Create Report Link. This creates a separate, frozen health snapshot containing the score, severity and category counts, verification wins, and trends. Routes are optional and off by default; code and raw evidence are excluded. Choose an expiry of 7, 30, or 90 days. Copy the complete link when it is created, because it is shown only once. Anyone with the link can open it without an account until it expires or you revoke it from the same card.

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

Local reports are generated on demand. Creating a connected report link is also an explicit action; it does not upload a local PDF or HTML file.
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.
Each report covers one project. Use Overview to inspect multiple projects in the app, or combine per-project exports externally.