Reports
What is in a report, how the share link works, and what white-labelling changes.
The report is the artefact you actually send. It has to be readable by a business owner, survive a developer's scrutiny, and be worth paying for on its own, so it is written for the first, sourced for the second, and priced into the audit rather than sold separately.
What is in one
Executive summary: the pain grade, the three worst findings in plain language, and an estimated revenue impact, on one page before anything technical appears.
Category scorecards: the ten categories with their scores and the measurements behind each.
Findings: each one with what it means, why it matters, its business impact, and a confidence label distinguishing a measurement from a heuristic.
Action plan: the ranked, sellable issues, several with paste-ready fixes: a DNS record, an nginx block, a robots directive, a schema snippet.
Evidence: screenshots of the site as rendered, desktop and mobile.
Sharing
Every report has a public URL with an unguessable identifier. It works without an account, which is the whole point: the prospect opens it from your email on a phone. Opens are counted, and obvious bot traffic is filtered out so the view count means something when you follow up. The same report downloads as a PDF for anyone who would rather forward a file.
The URL is stable. Re-running an audit updates the report behind the same link rather than minting a new one, so a link you sent last month still resolves.
White-labelling
On plans that include it, your workspace's name and accent colour replace ours across the web report and the PDF, and the "powered by" footer disappears. The brand is resolved at render time in one place, so the web report, the PDF generated in the background, and any cached copy always agree. Downgrading restores the default branding and clears cached PDFs rather than serving a stale white-labelled file.
Accessibility
The report is structured with real headings, table semantics and alt text, and the PDF carries a tagged structure. A product that scores other people on WCAG failures does not get to ship an inaccessible deliverable.
Link previews
A shared report URL unfurls properly in Slack, WhatsApp, LinkedIn and iMessage: the metadata is rendered server-side, with the score gauge as the preview image. Unfurlers never execute the page's JavaScript, so anything that depends on it would show a blank card.