Run Technical SEO audits

Start a crawl, inspect affected pages, prioritize findings with search evidence, and compare results after a fix.

Product guide · Updated October 2026

Before your first audit

Technical SEO audits are available on unlocked, active websites with full workspace access. Open Technical SEO inside the site. The page shows audit history, current activity, and the account allowance when available.

  • Only one audit can run at a time for a website.
  • Check the allowance shown in the app before starting. A run can stop at its configured or account limit.
  • Keep robots.txt and bot protection from blocking the pages you intend to audit.
  • Read findings as checks to investigate. The audit does not edit your site or guarantee rankings.

Free reporting shows a locked panel. See plans and the Pro trial for access options.

Confirm crawler access and start a run

  1. 1

    Select Start audit

    After an earlier run, the control is called Run new audit. It opens Before you run an audit.
  2. 2

    Review Let CrawlRaven reach your pages

    Follow the app’s robots.txt and firewall guidance for the pages you want checked. Coordinate access changes with the person who manages the site.
  3. 3

    Confirm the access checks

    Select the confirmation checkbox only after checking robots.txt and bot protection, then select Run audit.
  4. 4

    Follow progress

    The activity panel follows the queued crawl and result processing. You can inspect an earlier completed audit while the new run is working.

Find the issue and inspect affected pages

  1. Start with Critical and Warning findings. Use severity, category, and the issue search to narrow the list.
  2. Open an issue to read what was found, the suggested fix, and why the check matters.
  3. Review affected URLs and any linked-page evidence. One issue type can produce findings on many pages.
  4. When Search Console traffic is available, sort by search clicks to help choose which pages deserve attention first.
  5. Make and test the change in your website’s editor or code, then run another audit.

Compare runs after a fix

Open the completed run from Audit history. When a comparison is available, review new, fixed, and unchanged findings, use New since last audit, and inspect Resolved since last audit.

  • A partial audit may not recrawl pages from the previous run. Absence alone does not confirm a fix.
  • Changes to the audit engine or checks can make findings appear new or fixed without a website change. Read the comparison notice.
  • Record the work in a manual note so the change has context beside later search movement.

Schedule weekly audits and export evidence

  • Use Turn on beside Weekly audits off to enable the schedule. The page shows the next run when available; Turn off disables it.
  • The schedule remains subject to site access, crawler availability, and the account allowance.
  • Use Download CSV above the findings list to export its current scope.
  • Inside Issue details, Download CSV exports affected-page evidence for that issue.

For traffic investigation, use Queries and Pages. Inspect in GSC opens Google’s URL Inspection separately; it does not start another CrawlRaven audit.