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

SEO command line toolkit

The seohead command exposes every core tool for scripts, CI and terminal work. Commands shown in the docs are checked in CI.

SEO command line toolkit

Scriptable

JSON output, explicit budgets and exit codes for automation.

SEO command line toolkit

Tool catalogue

tool-catalog lists what each command does, whether it uses the network, writes files or costs money.

How it works

Three steps, one saved scan

  1. Pick a command

    Run seohead --help or search with tool-catalog. Each command has one job and a single entry in the catalog.

  2. Read JSON and the exit code

    Output is always JSON on stdout. Exit code 0 means the command completed. Exit code 1 means it could not finish, and the reason is in the JSON.

  3. Same commands for AI agents

    seohead mcp starts a local MCP server. Every command is also a tool named seo_<command>, for example seo_crawl_site.

What it checks

Checks in this feature

CheckWhat it meansSeverityEvidence
BROKEN_PAGE_4XXThe page returns a 4xx response.CriticalResponse code per URL from crawl-site
SERVER_ERROR_5XXThe page returns a 5xx response.CriticalResponse code per URL from crawl-site
BLOCKED_BY_ROBOTSrobots.txt blocks the URL.Importantrobots.txt rule matched for the URL from crawl-site
SITEMAP_URL_4XX_5XXThe sitemap lists a URL that returns 4xx or 5xx.CriticalSitemap entries from sitemap-crawl
SITEMAP_DESYNCThe sitemap URL set and the crawled URL set do not match.ImportantSitemap from sitemap-crawl compared with crawl-site
URL_NOT_IN_SITEMAPAn indexable page is missing from the sitemap.TipCrawl result compared with the sitemap URL set
How to run it

One command

bash
seohead tool-catalog --query redirect --limit 5

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

FAQ

Questions

SEO command line toolkit
No. The CLI runs on your machine. Offline commands, such as tool-catalog and the saved-scan commands, read local data only. Commands marked network send requests to the site or to a data provider.
Run tool-catalog. Each entry shows whether the command uses the network, writes files or costs money. Paid semantic commands need explicit confirmation, and the MCP version refuses to run without confirm_paid=true.
No. Crawls send read-only requests. Files are written only to the path you give, such as --scan-out or --out-dir.
Exit code 1 means the command could not complete. Its JSON has ok set to false, or an error line goes to stderr if the process crashed. Exit code 2 is used only by log-scan.

Check your redirects locally