Executive summary
Give stakeholders the scope, date and headline result first.
Client-ready reporting
Give teams and clients the scope, evidence, priorities and next steps behind an audit, with a dated baseline for the re-test after delivery.
The reports page shows the public report of cometweb.io, plus a separately labelled example scenario that explains the structure.
Direct answer
A website audit report is the document that presents audit results to a team or a client. It says what was checked, what was found and on what evidence, which fixes come first, who owns them and how the result will be re-tested.
Content reviewed:
A report with a job to do
A useful report separates the signal from the noise. It shows what was checked, why a finding matters, who should look at it next and how to compare the result later.
Give stakeholders the scope, date and headline result first.
Lead with the issues that deserve attention before the long tail.
Keep the URL, module and signal close to each finding.
Explain data sources, automated scope and what needs manual review.
Use the date and same measures to show what changed.
Share a view that supports a conversation without exposing an account.
From scan to handoff
Keep the report close to the work: establish scope, discuss the first priorities, ship changes and return to the same evidence.
Choose the domain, scan depth and modules that answer the question.
Start with the result, date and top issues, not a wall of raw output.
Use the findings to clarify ownership, effort and the next decision.
Re-run the audit and show the new state next to the baseline.
At minimum: scope, date, data sources, key findings, priorities, evidence and next steps. A re-test should use the same context so the change can be discussed honestly.
Last updated:
Yes. The PDF report is available from the Free plan, CSV and XLSX exports from Growth, and reports without CometWeb branding on Scale. The findings are the same on every plan.
Last updated:
No. It summarises detectable automated signals. It is not a legal opinion, compliance certificate, pentest or complete manual accessibility review.
Last updated:
No. The sample is a clearly labelled structure example. It demonstrates the report workflow without presenting fabricated production findings as a case study.
Last updated:
A report an agency presents under its own brand rather than the tool vendor’s. In practice it means the client sees the findings, priorities and evidence without the vendor’s logo dominating the document. It changes presentation, not what the audit measured.
Last updated:
Three things decide whether it survives contact with a client: whether the report can carry your branding at all and on which plan, whether findings arrive in an order you can hand to a developer, and whether the same audit can be re-run afterwards to show what changed. A branded PDF nobody can re-run is a document, not a workflow. On Insight, reports without CometWeb branding belong to the Scale plan, and how far back you can compare depends on the plan history window. There is none on Free.
Last updated:
White-label options are available from the Scale plan. Lower plans still produce a client-facing report with a read-only sharing view; what changes with the plan is the branding, not the findings. Check the pricing page for what your plan includes.
Last updated:
Start with scope and date, then lead with the findings that change a decision (indexability, canonicals, titles, headings and internal links), each with the URL and the signal behind it. Close with next steps and a re-test date so the next report compares like with like.
Last updated:
No. Insight reports on technical quality (performance, SEO signals, accessibility, security and CO₂e), not on keyword positions. Rank tracking is a separate category of tool and CometWeb does not claim it.
Last updated:
Use a dated result to align the team today and show the difference after the work ships.