Starting Your First Audit

Your first site audit takes a few minutes to set up and gives you a scored, prioritized snapshot of your site's technical health. This walkthrough uses the Site Audit tab inside a project; the standalone tool page works the same way (see Starting Your First Site Audit for that route).

Before You Start

You need a project (its domain pre-fills the audit) and enough credits: a full site audit costs 5 credits plus 1 credit per crawled page, so the default 50-page crawl is 55 credits. A single page audit is 6 credits.

Running the Audit

1. Open your project and go to the Site Audit tab.
2. Check the URL field - it should point at the site you want crawled.
3. Choose Full Site Audit (crawl the whole site) or Single Page Audit (one URL).
4. For a full audit, set Pages to Scan (1-500, default 50) and Crawl Depth (1-10, default 3). Defaults are right for a first run on most sites.
5. Click start and let the crawl run - progress displays while pages are fetched and checked. Larger crawls take longer; you can leave the page and come back, since the finished audit lands in the audit list either way.

Reading Your First Results

Start at the top: the overall score (0-100) and the split of issues, warnings, and passed checks. Then work the grouped results in this order:

1. Errors first - missing titles or descriptions, missing H1s, 4xx/5xx responses, HTTPS problems. These are the checks weighted hardest and usually the cheapest to fix.
2. Warnings next - title and description lengths, duplicates, alt text, page speed flags. Expand each check group to see exactly which pages are affected.
3. Skim the passed checks - it tells you what's already healthy so you don't re-solve it.

If a check doesn't apply to your site, use Skip this check so future audits stay focused (restorable any time from the skipped/hidden panel).

Make It Your Baseline

This first audit is your reference point. It's stored in the audit list with its date, score, and issue count; later audits line up next to it so improvement is visible without any spreadsheet work. Two follow-ups worth doing immediately:

• Re-run a Single Page Audit (6 credits) on a page after you fix it, to confirm the fix landed without paying for a full crawl.
• Set up Schedule Audits so the next full audit happens automatically - see Scheduling Regular Audits.

FAQ

How long does an audit take?
It depends on pages crawled and how fast your server responds - small crawls finish in minutes. The audit continues in the background if you navigate away.

Why were fewer pages audited than my limit?
The crawler found fewer pages within your crawl depth. Pages with no internal links only get included if they're in your sitemap.

Do I pay for pages that fail to load?
Crawled pages count toward the per-page cost; 4xx/5xx responses are themselves findings the audit reports.

Related Documentation

• Site Audit Overview
• Crawl Settings & Configuration
• Scheduling Regular Audits