How the Scan Works
The scanner fetches your pages over HTTP, the way a visitor or search engine sees them, and runs every enabled check. A scan only reads - nothing is changed.
Before You Scan
- The site should be reachable and not in maintenance mode
- Check your server limits under Settings → Scanning: it shows PHP max_execution_time and memory_limit, and a recommended batch size and timeout. Ask your host for 60 seconds or more of execution time if the value is low
Starting the Scan
- Go to Site Auditor → Issues and click Run scan
- Site-wide checks (robots.txt, sitemaps, server headers, database, plugin and theme status) run once per scan
- Pages are then fetched in batches - up to 5,000 URLs per scan by default (the
wtsa_max_discovered_urlsfilter)
A manual scan is driven from the admin page: if you leave the page, it continues when you open it again.
Scan Completeness
When the scan is done, the Overview and Issues pages show how many URLs were scanned and, if some could not be read, how many and why (timeouts, HTTP errors, pages that could not be parsed). A page that crashes twice is skipped.
After the Scan
- Review issues by page or by check, under the Open, Fix active, still detected, Ignored and Resolved tabs
- Filter by severity, category, fix type, text and "New since the last scan"; active filters are shown as chips you can remove one by one
- Use "Re-check this URL" to verify one page again without a full scan
- Export the current, filtered list to CSV