Documentation Menu↓
Getting Started
How to Run a Website Scan
Initiating scans and choosing crawl paths.
Difficulty:
|Beginner
Est: 9 mins
|Updated July 2026
Overview
Running an audit directs the CrawlSage bots to scan your website sitemap, check headers metadata, test loading metrics, and isolate technical SEO issues. This guide details how to configure and execute your first scan.
Screenshot PlaceholderPriority: High
Initialize New Operation Form
The Audits view containing the Initialize New Operation card, URL input field, optimization type select, and platform integration fields.
Prerequisites
- A registered website entry with a verified domain address.
- Available usage credits in your dashboard account balance.
Step-by-Step Guide
- Open the Audits Panel: Log in to your workspace. Click the "Audits" tab in the left sidebar navigation panel.
- Configure Scan Scope & Operation: Set up the crawler fields on the main form:
- Initialize New Operation: Click either Run SEO Audit or Run AI SEO Fixes.
- Website Target URL: Enter the website URL you want to scan (e.g.
https://example.com). - Operation Scope (Audit / Optimization Type):
- If running an SEO Audit, select Single Page SEO Audit or Full Site SEO Audit from the dropdown.
- If running AI SEO Fixes, select AI Single Page Optimization or AI Full Site Optimization from the dropdown.
- Platform Integration: Choose your target platform (currently WordPress is supported).
- Launch Operation: Click the primary "Launch Audit" or "Launch AI Optimizer" button. The task is initialized and sent to the queue.
- Monitor Progress: The page will load the execution console. Review the live logs stream (e.g.,
[crawler] Fetching sitemap.xml,[parser] Validating HTML on /about) to track progress.
Expected Result
Once completed, the logs view is replaced by the completed report. Your dashboard KPIs (Health Score, Issues Found, Pages Crawled) will instantly populate with updated parameters, and the recommendations grid will display generated tag suggestions.
Background Scan Processing
You do not need to keep the browser tab open while an audit is running. The CrawlSage server processes crawls asynchronously in the background. You can safely close the tab; we will email you when the report is compiled.
Best Practices
- Schedule Weekly Baselines: Enable scheduled scans in website settings to run automatically during off-peak hours (e.g., Sunday at 02:00 UTC).
- Audit After Code Changes: Always run a Quick Scan immediately after updating your website templates, plugins, or redirects to ensure no rendering issues occurred.
Common Mistakes
- Exceeding Credit Quotas: Running large crawls (10,000+ pages) consumes credits relative to the number of pages successfully scanned. Ensure your balance has adequate credits before initiating deep audits.
- Double Scanning: Do not click "Launch Audit" or "Launch AI Optimizer" repeatedly if a scan is already running. Parallel crawls on the same domain are blocked to prevent overloading your host server.
Troubleshooting
- Audit remains "Queued" or "Failed":
- Verify that your site host is online and responsive.
- Check if your firewalls (Cloudflare, AWS WAF) are blocking requests from User-Agent:
CrawlSageBot. - Confirm your robots file has not blocked our crawler. See the Failed Audit Troubleshooting manual.
Related Guides
Was this page helpful to your workflow?