301→302
A temporary redirect where a permanent one belongs. Found by Redirect checker →
redirect loop
The URL redirects back to itself and never settles. Found by Redirect checker →
Audit

Technical SEO audit with 182 checks

A generated registry of 182 checks is shared by native crawls and Screaming Frog exports. Severity, evidence and fix come from the same registry the rule engine reads.

Technical SEO audit with 182 checks

Evidence, not guesses

Each finding names the URL, the observation and where on the page it happened, with a fix next to it.

  • Critical, warning and notice
  • DOM position and XPath for links

Technical SEO audit with 182 checks

Honest coverage

The report says how many checks could run on the evidence available, and the score is withheld or marked not comparable when coverage is low.

How it works

Three steps, one saved scan

  1. Point it at your exports

    Give it a folder of Screaming Frog CSV or XLSX exports. Every check reads the same registry, whichever way the evidence was collected.

  2. Run every check the evidence allows

    Each check either reports findings, comes back clean, or is skipped with a reason when the data it needs is missing.

  3. Get fixes as a task list

    Add --tasks to get tasks.json and tasks.md, a prioritized backlog for developers with the fix next to each finding.

What it checks

Checks in this feature

CheckWhat it meansSeverityEvidence
BROKEN_PAGE_4XXThe page answers with a 4xx statusCriticalResponse Codes 4xx export, URL and status
SERVER_ERROR_5XXThe page answers with a 5xx statusCriticalResponse Codes 5xx export, URL and status
TITLE_MISSINGThe page has no title elementCriticalURL of the page
BROKEN_INTERNAL_LINKAn internal link points to a 4xx URLCriticalSource page and link position from the inlinks export
H1_MISSINGThe page has no H1 headingImportantURL of the page
CANONICAL_MISSINGAn indexable page has no canonical URLImportantURL of the page
THIN_CONTENTThe page has a low word countImportantURL and word count
HEADING_BEFORE_H1Headings appear before the page's first H1TipHeading outline of the page
How to run it

One command

bash
seohead sf run --exports-dir ./exports --out ./report --tasks

Install first: installation guide. Every command also runs as an MCP tool for AI agents.

Related checks

From the check registry

BROKEN_PAGE_4XXTITLE_MISSINGCANONICAL_MISSINGH1_MISSINGTHIN_CONTENT
FAQ

Questions

Technical SEO audit with 182 checks
The exports path reads existing Screaming Frog CSV or XLSX files. Crawling through the Screaming Frog CLI itself needs a licensed Screaming Frog install.
It is reported as skipped with a reason. It is never shown as a pass.
No. It reads exports or saved scans. A crawl sends requests at the rate you set with --max-urls-per-second; 1 to 2 requests per second is the suggested start.
Yes. The same audit runs as MCP tools: sf_audit_run, sf_audit_issues and sf_audit_tasks.
Yes. --fail-on critical returns a non-zero exit code when critical issues are present; --fail-on warning and --fail-on none are also accepted.

Check your redirects locally