White-Label Website Audit Reports (PDF & JSON)
Every audit can leave as a deliverable: a branded PDF for the client, or structured JSON for your own tooling.
Reports & Exports
PDF Reports
After running an audit, click "Create Report" in the export bar. The report customization page lets you toggle up to 8 sections (Overview, PageSpeed, SEO, Security, Hosting, CSS, Accessibility, GEO) and preview before generating the PDF.
Reports also include the AI Recommendations block (executive summary and prioritized fixes) shown after your audit. You can leave it out with the "Include Recommendations" toggle on the customization page.
White-Label Branding
Available on Pro and Agency plans. Four branding fields carry through to the PDF: your agency name, your agency logo, an optional client name (used for the "Prepared for" line), and an optional client logo. Logos are uploaded as images up to 500KB; around 200x60px works best. Every page footer reads "Prepared by {your agency name}".
On the Starter plan the branding fields are ignored at generation time and reports carry Web Audit Suite branding instead. Page layout itself is fixed for every plan: A4, portrait, no page numbers.
JSON Export
Agency plan only. Export the full audit as a structured JSON file containing every score, all eight tabs of data, the AI recommendations block, and export metadata. The file is named website-analysis-{domain}-{date}.json.
The export is versioned: every file carries a schemaVersion field, currently 1.6.0. Versioning follows semver, and in practice that means new fields are added as optional (a minor bump) while removals and renames would require a major bump. Code written against any 1.x export keeps working.
Availability by Plan
| Feature | Starter | Pro | Agency |
|---|---|---|---|
| PDF Report Generation | Included | Included | Included |
| AI Recommendations (executive summary + ranked fixes) | Included | Included | Included |
| Content Section Selection (8 toggleable sections) | Included | Included | Included |
| White-Label Branding (agency name, logos, client name) | — | Included | Included |
| JSON Export (schema v1.6.0) | — | — | Included |
| REST API Access | — | — | Included |
See Plans & Pricing for full details.
What's Inside a PDF Report
A report opens with a cover header — your agency name and logo top right, the audited domain as the title, and a "Prepared for" line carrying the client name and logo when you set them. Below that come the sections you left switched on. Each one is independently toggleable, so a performance-only report and a full technical audit come off the same scan.
| Section | What it contains |
|---|---|
| Overview | Website summary, domain info, and general details |
| PageSpeed Insights | Performance scores, Core Web Vitals, and metrics |
| SEO & Meta Tags | Meta tags, Open Graph, and structured data |
| AI Readiness | GEO (Generative Engine Optimization) and AEO (Answer Engine Optimization) |
| Security | SSL certificate, security headers, and HTTPS status |
| Hosting & Infrastructure | Server information, DNS records, and IP geolocation |
| CSS Analysis | Stylesheet analysis, design tokens, and media queries |
| Accessibility | A11y issues, ARIA attributes, and semantic HTML |
The AI Recommendations block — an executive summary plus prioritized fixes — has its own toggle alongside those eight, and is included by default on every plan. Because that text is AI-generated from your audit's findings, read it before it goes to a client.
Everything renders through the same preview you see on the report customization page, so what you approve on screen is what the PDF contains. Layout is fixed: A4, portrait, no page numbers. The file downloads as website-analysis-{domain}-{date}.pdf.
JSON Export Structure
The JSON export (Agency plan) is the same audit as the PDF, without the presentation layer — one object with these top-level keys. Two of them are optional, so write consumers that check before they read.
| Field | Presence | What it holds |
|---|---|---|
schemaVersion | Always | The export schema version, currently 1.6.0. Check this first. |
exportedAt | Always | ISO 8601 timestamp for when the file was generated, which may be later than the scan. |
metadata | Always | The audited URL, when it was analyzed, whether the PageSpeed phase completed, and whether the scan ran authenticated. |
scores | Always | Every computed score for the audit, 0-100 where applicable. |
tabs | Always | The eight result tabs — overview, pagespeed, accessibility, seo, geo, security, css, hosting — each as cards of detailed findings. |
aiSuggestions | Optional | The executive summary and ranked recommendations, when a block exists for the audit. Internal accounting (cost, tokens, latency) is deliberately excluded. |
failures | Optional | Analyzers that did not complete, keyed by analyzer name with a status and error. Its absence means nothing is known to have failed; its presence is how you tell a degraded tab from one that was never part of the audit. |
The REST API returns this same structure on the Agency plan, with two differences: it adds id, status, and _links around the audit, and it does not carry the two optional blocks — aiSuggestions and failures — which only a download from the app can include.
Next Steps
- Website audit report example — a full sample audit with the scores, findings, and AI action plan a client actually reads.
- Website audit scores explained — what every number in the report actually measures.
- The 18 website audit checks we run — what every section of the report is actually measuring.