CrawlPodScan your site

Bulk Site Scan

Bulk Site Scan runs the AI Readiness Audit across every page and post on a WordPress site at once, processing in batches with pause and resume support, and keeps a history of past scans so score changes over time are visible rather than only a single snapshot.

What it does

Instead of running the 9-check audit one page at a time, Bulk Site Scan queues every published page and post and works through them in batches, applying the same checks used by the single-page audit. The scan can be started, paused, and resumed without losing progress, which matters on sites with hundreds or thousands of pages.

Each completed scan is stored, so the current run can be compared against the previous one — which pages improved, which regressed, and which issues are new.

Why it matters

One page isn't enough. AI models evaluate site-wide authority and consistency, not a single well-optimized page in isolation — a site with one strong page and a hundred poorly structured ones still struggles to earn broad citation. Bulk scanning surfaces exactly which pages are dragging a site's overall AI visibility down, instead of leaving that judgment to page-by-page spot checks.

How it works

  1. Open Bulk Site Scan from the CrawlPod dashboard.
  2. Choose which post types and taxonomies to include.
  3. Start the scan — it processes pages in batches in the background.
  4. Pause and resume at any time without losing completed results.
  5. When finished, review the site-wide summary and the diff against the previous scan.

Key concepts

  • Batch processing — pages are scanned in groups rather than all at once, keeping the site responsive during a scan.
  • Pause/resume — a scan can be stopped and continued later from where it left off, rather than restarting from the beginning.
  • Historical diffing — each scan is compared against the previous one to show which pages and scores changed.

Limitations & fair usage

Bulk Site Scan is available on the Pro plan and above. Scans run on a fair-use schedule to keep response times reasonable for all customers — very large sites may take longer to complete a full pass, which is part of why pause and resume exist.