Crawl Stats

Crawl Stats helps you analyse how search engines crawl your site. Review crawl requests, response times, and crawl errors to identify crawl budget issues, server performance problems, and URL-level anomalies using Site Audit data.

Summary

What this is

Crawl Stats helps you understand how search engines interact with your website. It provides insights into crawl requests, response times, and crawl errors so you can identify issues affecting crawl efficiency.

What you can do

  • Monitor crawl requests and crawl activity trends.
  • Identify slow responses, timeouts, and crawl-related errors.
  • Analyse anomalies using status code and performance filters.
  • Investigate affected URLs using page-level details.
  • Export crawl data for reporting and team collaboration.
Good to know

Crawl Stats depends on Site Audit crawl data. If crawl coverage is incomplete or required data sources are unavailable, some crawl activity and anomaly information may not appear.

Prerequisites

Before using Crawl Stats

  • A Wranker project exists for the website you want to review.
  • A Site Audit has been completed for the selected project.
  • You have access to the Site Audit module.
  • Required crawl data sources are available for your setup.
  • Export permission is available if downloading crawl statistics.
Tip

Review crawl coverage before analysing trends so your findings are based on complete audit data.

Where to find it

  1. Open SEO Dashboard.
  2. Select Site Audit.
  3. Open Crawl Stats from the Tab Index or Site Audit navigation.
  4. Choose the correct project and reporting period.
Breadcrumb check

Confirm the navigation path: SEO → Site Audit → Crawl Stats

Step-by-step: Review Crawl Stats

  1. Open Site Audit

    Open the Site Audit module for the website you want to analyse.
    check connecion

    Capture: check connecion

  2. Open Crawl Stats

    Navigate to SEO Dashboard → Site Audit → Crawl Stats from the navigation or Tab Index.
    check connecion

    Capture: check connecion

  3. Confirm project and reporting period

    Verify the selected website and reporting period before reviewing crawl trends.
  4. Review crawl activity

    Analyse crawl request charts to identify increases, decreases, or unusual crawl behaviour.
    check connecion

    Capture: check connecion

  5. Analyse response times and errors

    Review response time trends, timeouts, and 4xx/5xx errors that may affect crawl efficiency.
    check connecion

    Capture: check connecion

  6. Investigate anomalies

    Open anomaly records and use filters to review affected URLs, response times, and crawl sources.
    check connecion

    Capture: check connecion

  7. Export crawl data

    Download Crawl Stats as CSV when available for reporting and collaboration with technical teams.
    check connecion

    Capture: check connecion

Expected result

  • Crawl activity trends are clearly understood for the selected project.
  • Slow responses, crawl errors, and anomalies are identified.
  • Problematic URLs are prioritised for investigation and fixes.
  • Crawl findings can be shared with technical teams using exported reports.

Key Features

Crawl Request Trends
Monitor crawl activity and request volume over time.
Response Time Analysis
Identify slow pages and performance bottlenecks.
Anomalies Table
Review URLs with crawl errors, timeouts, or unusual behaviour.
Advanced Filters
Filter crawl data by status code, response time, or crawl source.
Page Details Drawer
View detailed crawl information for individual URLs.
Trend Charts
Compare crawl requests and response performance across reporting periods.
CSV Export
Download crawl statistics for reporting and collaboration.
Issue Investigation
Prioritise crawl issues affecting indexing and crawl efficiency.
Best Practice

Review crawl request trends together with response times and crawl errors to identify the root cause of crawling problems.

What you'll see

Crawl Requests Chart
Visualises crawl activity and request volume over time.
Response Time Chart
Displays response performance and page speed trends.
Anomalies Table
Lists URLs with crawl errors, slow responses, or unusual activity.
Filters
Filter results by status code, response time, crawl source, or user agent.
Page Details Drawer
Review URL-level crawl information and recommendations.
Export Action
Download crawl statistics and anomaly data as CSV when available.

Common workflows

Diagnose server performance issues

  1. Filter performance issues

    Use filters to identify URLs with slow response times, timeouts, or 5xx server errors.
  2. Review affected URLs

    Open page details to investigate repeated performance problems.
  3. Share findings

    Provide crawl insights to development or operations teams for resolution.

Investigate crawl budget issues

  1. Review crawl trends

    Analyse crawl request charts to identify unusual increases or decreases in crawl activity.
  2. Identify crawl waste

    Look for repeated redirects, error responses, or unnecessary URL patterns.
  3. Prioritise important pages

    Ensure valuable pages remain accessible and efficiently crawled.

Analyse crawl anomalies

  1. Apply filters

    Filter anomaly records by issue type, response time, or status code.
  2. Review affected URLs

    Investigate URLs showing crawl errors or unusual activity.
  3. Inspect page details

    Open the details drawer to understand the cause of crawl issues.

Export crawl reports

  1. Confirm project

    Verify the correct website and reporting period are selected.
  2. Apply filters

    Narrow the report to the required crawl issues if needed.
  3. Export data

    Download crawl statistics as CSV for reporting or further analysis.

Tips and best practices

  • Review Crawl Stats regularly to detect server issues early.
  • Compare the same reporting period when analysing crawl trends.
  • Prioritise investigating 5xx errors and timeouts before minor crawl issues.
  • Use filters gradually to isolate the cause of crawl anomalies.
  • Export reports before and after major website releases to measure impact.
  • Include the project scope and reporting period when sharing crawl findings.
Avoid this mistake

Don't investigate individual URLs without first checking whether the issue is part of a larger crawl pattern. Always review overall crawl trends before focusing on page-level problems.