Skip to content
Enjoy 20% off for 12 months on all plans. Use promo code: HYPERGROWTHClaim it
Help

Set audit scope and page caps

Learn how many pages an audit crawls, where the 200 and 500 limits come from, and how big sites resume across legs.

Open in the appUpdated 2026-10-12

Every audit crawls a set of your pages, and the scope setting controls how many. In the app you pick up to 200 pages. Through the API or the MCP connector the ceiling is 500 pages. Scheduled re-audits crawl 100 pages. Pages are discovered from your sitemap first, then from internal links, so the crawl spends its budget on the pages your own site points at.

Standard (100 pages) suits most sites, since it covers the complete page set of a typical business site. Pick Deep (200) when the site has more pages that matter, like a large blog or e-commerce categories. Pick Quick (50) when you want a faster first look. An API request above 500 is accepted but clamped to 500.

Choose your scope

To set the audit scope:

  1. Open your website's Site Audit → Report in the sidebar.
  2. Select Edit on the Crawl depth row and pick Quick (50 pages), Standard (100) or Deep (200). The row remembers your choice for the next run.
  3. Select Run SEO audit. The price is on the button, and the line under it shows your balance after the run.

Read the crawled count

The report shows how many pages were crawled against how many checks ran — the health strip at the top of your graded report carries both numbers. If the crawled count sits well below your scope, the crawler ran out of discoverable pages (a small site) or was blocked partway (see below).

Limits and usage

  • The depth picker goes up to 200 pages.
  • Through the API or the MCP connector the ceiling is 500 pages, and a request that names no number crawls 200. Values outside the range are clamped, not rejected: a request for 10,000 pages runs as 500.
  • Scheduled re-audits crawl 100 pages.
  • Big crawls resume across legs. An audit that can't finish inside one server window checkpoints its progress and continues in a fresh leg, up to 5 legs, picking up exactly where it stopped. You'll see this as the run reporting "Resuming crawl" with the pages already done.
  • Credits are charged once per completed audit, not once per leg. An audit that fails is not charged. The price per audit is in Plans and credits.

If something isn't working

The audit stops around the server time limit on a heavy site. Wait a few minutes — the resume system continues from the checkpoint automatically, including a background sweep that picks up a run whose tab closed. A manual re-run starts over.

Far fewer pages crawled than expected. Make sure your sitemap lists the pages you care about. The crawler discovers through the sitemap and internal links, so orphan pages with no links and no sitemap entry are invisible to it.

You need more than 500 pages. Split the work: audit sections of the site as separate runs, or rely on the sampled crawl — technical problems repeat across templates, so a 500-page sample almost always finds the same issues a full crawl would.

Was this page helpful?

Still stuck?

Email us and the team replies from the same address. If you're signed in, Ask anything in the app answers from these guides.

hello@searchblueprint.ioAsk in the app