Sitemap Audit
Bulk-audit every page in your sitemap with a single job.
A sitemap audit reads your sitemap.xml, queues each URL as a child audit, and produces a parent report with rolled-up scores across all pages.
When to use
- Regular site-wide health pulse (weekly or monthly)
- Identifying which pages have the lowest scores across a category
- Checking a batch of recently published pages after a content sprint
- Validating a site migration by auditing all pages before and after
How to run
Open Run audit
From your project page, click Run audit.
Select Sitemap
Choose Sitemap from the audit type options.
Enter sitemap URL
Enter the URL of your sitemap (e.g.
https://acme-coffee.com/sitemap.xml). SitePulse supports standard XML sitemaps and sitemap index files (sitemaps of sitemaps).Submit
Click Start audit. The parent audit is created immediately. Child URL audits are queued and run in parallel.
Live progress during processing
While the sitemap audit runs, the progress bar on the parent audit shows:
- Total URLs discovered
- URLs completed
- URLs failed
Each child URL appears in the list as it completes. You do not need to wait for all pages to finish before reading the first results.
What it returns
- Parent audit — rolled-up scores (average across all child pages) for all 6 categories
- Per-URL child audits — full detail for each individual page, accessible by clicking any row in the URL list
- Score distribution — histogram showing how many pages fall into good/needs-improvement/poor bands per category
Processing time
Sitemap audits run child audits in parallel, but queue depth and site response time affect total duration:
| Site size | Typical time |
|---|---|
| < 25 URLs | 2–5 minutes |
| 25–100 URLs | 5–15 minutes |
| > 100 URLs | 15–45 minutes |
Sitemap limits
Sitemap audits are available on Agency and Enterprise plans only (0 per month on Free). The maximum number of URLs per sitemap audit is determined by your plan limits.
Tips for best results
- Make sure your sitemap is up to date. SitePulse audits exactly the URLs it finds — orphan pages not in the sitemap will not be included.
- Use a sitemap index file to audit a subset: point SitePulse at one sub-sitemap (e.g.
/sitemap-blog.xml) to limit the crawl to a specific section. - If pages require cookies to load fully, the PSI-based checks will still run, but server-side rendered content is always accessible.