Loading
Because it returns thousands of issues with no sense of importance. Severity is judged by issue type rather than by whether the affected page has ever earned a visit.
The crawl walks your site, creating or updating a record per URL with its status, content, metadata and links.
The crawl updates page records rather than producing a document. Because those records already carry impressions and revenue, issues are ranked by the value of the page they sit on.
Five hundred pages crawled produce eleven issues on pages that earn something and four hundred on pages that do not. The eleven are the list.
It will not reach what it cannot see. Pages behind a login, blocked in robots, or rendered only after interaction are reported as unreachable rather than assumed fine.
It creates the page records everything else in Growth reads, detects content changes for the timeline, and feeds the technical, metadata and structured data checks.
On a schedule you set, plus on demand.
Yes, so client-rendered content is seen.
Yes, by pattern, and exclusions are visible in the report.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.