Sites and reports

Who this is for

Teams tracking client domains over time and sharing public audit landing pages or exports.

When to use Sites

To manage the canonical list of domains your workspace measures. The list feeds Benchmark ("Your site") and many Intelligence dropdowns.

When to use Reports

To find completed runs only, copy public links, download Markdown or PDF, or jump back into the full audit detail.

Before you start

• Add domains under Sites, or rely on audits to create sites automatically where the product does so.
• Site detail needs at least one audit; trend charts need two or more.

In the app: Sites

1. Under Audit & Analysis, choose Sites.
2. Click Add Site to open the Add site dialog. Submit a URL; the app normalises the domain. Duplicate submissions toast that the site is already tracked (sites-list.tsx).
3. Open a domain row to load /sites/<id> (Site detail).

Each row also shows the site's Client Group (Admins and Editors can assign one; hidden from the client role) and its last audit.

Removing and restoring a site

Owners and Admins can remove a site. Removal is reversible: it hides the site from lists and pickers and stops auditing it, but keeps every existing audit and report. Re-adding the same domain under Add Site restores it. There is no permanent site delete in the product.

Site detail (/sites/<id>)

• Header. Shows the domain, with subtitle "Score trends across N audit(s)".
• Delta cards (when there are two or more audits). SEO, Performance, Security, UX current score plus the change against the earliest point (green plus or red minus icons).
• Score Trends. A line chart for the four scores over time. With fewer than two audits the page shows "Need at least 2 audits to show trends. Run another audit to see changes."
• Audit History. Newest-first rows linking to /audits/<auditId> with date, pages count, scores, and a grade badge when present.
• Connections. Owners and Admins can connect this site's own Google Search Console and Google Analytics 4 so its audits use real search and traffic data. Choose Connect with Google, pick a property, then Test connection. The panel is hidden from the read-only client role. Full detail in Per-site Google connections.
• Errors. A red card with the API message and a Back button to Sites when getSiteTrends fails.

In the app: Reports

1. Under Audit & Analysis, choose Reports.
2. Subtitle: "Generated audit reports and landing pages".

The Reports table (completed audits only):

Use the Refresh control to reload after new runs finish.

Empty and error states

• Reports. "No reports yet" with a Run an audit button that opens /audits/new.
• Reports load failure. Refresh; check API connectivity.
• Sites empty. Use Add Site or run an audit that creates the site.

Common pitfalls

• Site detail shows an error string. Verify the site ID and the active workspace.
• Missing View on Reports. The run may not have generated a report or slug yet. Open Details on the audit row to investigate.

Related

• Reading audit run results.
• Competitor benchmark.
• Lead detail when audits link from outreach.
• Per-site Google connections to feed real GA4 and Search Console data into a site's audits.