Audit Types Overview
The three audit types in SitePulse and when to use each one.
SitePulse supports three audit types. Each targets a different surface and produces a different kind of report.
At a glance
| Type | What it audits | Best for |
|---|---|---|
| URL | A single publicly accessible web page | Diagnosing one page in depth |
| Sitemap | Every URL listed in your sitemap | Bulk health check across the whole site |
| GitHub | A public or private GitHub repository | Code quality, dependency risk, best practices |
| — | Retired as a separate type — now runs automatically inside sitemap audits (details) |
Choosing the right type
Use a URL audit when you have a specific page you want to improve — a landing page, a product page after a redesign, or any page flagged as underperforming. URL audits produce the most detailed per-page breakdown.
Use a Sitemap audit for a regular health pulse across your entire site. SitePulse crawls your sitemap.xml, audits each URL in a background queue, and produces a parent audit with rolled-up scores plus per-URL drill-downs.
Use a GitHub audit when you are evaluating code quality or onboarding onto a new codebase. The agent clones the repo, reads the structure, and assesses dependency risk and code best practices — no deploy needed.
Competitor analysis happens automatically as part of every sitemap audit — SitePulse works out who your competitors are, where they beat you, and what to do about it. See Competitor Analysis.
Audit limits by plan
| Plan | URL audits/mo | Sitemap audits/mo |
|---|---|---|
| Free | 5 | 0 |
| Agency | Per plan limits | Per plan limits |
| Enterprise | Per plan limits | Per plan limits |
Quota counters reset on your billing period start date. Current usage is visible on Settings → Billing → Usage.
Note
GitHub audits count against your URL audit quota.