Skip to content
tech-seo.de

Built for AI agents

Technical SEO checks for AI agents

tech-seo.de runs the checks an LLM cannot do with a normal fetch: raw HTTP headers, every redirect hop, responses per user agent, parser-correct robots.txt evaluation and consistency checks across many URLs.

  • Same result everywhereMCP · REST · Web UI
  • Machine-readableStructured JSON, OpenAPI 3.1
  • Built for agentsTool descriptions written for LLMs
redirect_matrix

> techseo.redirect_matrix("example.com")

http://example.com/301→ https://example.com/http://www.example.com/301→ https://www.example.com/301→ https://example.com/https://www.example.com/301→ https://example.com/https://example.com/200https://example.com/index.html301→ https://example.com/https://example.com/?utm=1200

warn13 requests · 2.1 s

redirect.chain_too_long http://www.example.com/ needs 2 hops

For agents

Connect tech-seo.de to your workflow

Every check is available as an MCP tool, a REST endpoint and a web form, with the same structured result.

MCP endpoint
https://tech-seo.de/api/mcp/mcp

Stateless Streamable HTTP. One tool per check plus list_checks. Add the URL as a remote MCP server in Claude, ChatGPT, Cursor or VS Code.

Client setup
POST /api/v1/checks/redirect_matrix
curl -X POST https://tech-seo.de/api/v1/checks/redirect_matrix \
  -H 'content-type: application/json' \
  -d '{"domain":"example.com"}'
  • Anonymous use20 requests per 10 minutes per IP. Rendering is 5 per 10 minutes.
  • Consistent formatstatus, summary, findings, data
  • OpenAPI 3.1Machine-readable spec for integration
  • LLM-friendlyAlso available as llms.txt

Built for real-world technical SEO

What the checks look at

  • Multiple user agentsBrowser, Googlebot, Bingbot, GPTBot, ClaudeBot, PerplexityBot
  • Raw HTTP dataStatus codes, headers, every redirect hop, compression, caching
  • Standards-compliantRFC 9309 robots.txt matching, ISO language and region codes
  • Large sitesSitemap indexes, URL samples, budget-capped runs