Multi-page audits

Multi-page audits & sitewide scores

Updated Jun 2, 20265 min read
Examples
On this page

How we pick pages

When you audit a URL, PageReflect looks for other pages on the same origin to include. It reads the sitemap, respects robots.txt, and does a shallow crawl of links from the starting page. Only same-origin pages are considered; we do not follow links off your domain.

How many pages

Each run audits up to a fixed number of pages: 5 on the free plan and 15 on a paid plan. Pages beyond the cap are not gathered for that run. If a site has fewer pages than the cap, the audit simply covers what it finds. See Plans & quotas.

From pages to a score

All of the gathered pages go into a single scoring pass. The sitewide score is the model's aggregate judgment over them, not a configurable average; there is no per-page weighting knob to tune.

A practical consequence: because the set of pages can change between runs (a sitemap grows, a link appears), the sitewide score can move even if no single page changed. The per-page detail in the report tells you what drove it.

Partial results

If some pages fail to load or time out, the run does not fail. It scores what it could gather and notes the reduced coverage. If a report covered fewer pages than you expected, see Troubleshooting.

Feedback

Was this page helpful?

Multi-page audits & sitewide scores — PageReflect docs