SEOBolt exposes audit, issues, fix-plan, and checkout tools over MCP. Your agent can inspect the crawl, update your repo, and trigger another crawl to verify the result.
Create an API key and configure the SEOBolt MCP server.
Run seo_start_crawl from the agent session.
Call seo_fix_plan and let the coding agent patch the repo.
Run seo_audit after deployment to confirm the health score moved.
Traditional SEO still matters, but AI search adds new failure modes: blocked AI crawlers, missing entity context, thin llms.txt files, and pages that answer engines cannot cite.
{
"mcpServers": {
"seobolt": {
"command": "node",
"args": ["/absolute/path/to/seotools/mcp/dist/index.js"],
"env": {
"SEOBOLT_API_KEY": "sk_live_your_key",
"SEOBOLT_URL": "https://seobolt.app"
}
}
}
}Every MCP tool maps to an authenticated API endpoint with API-key rate limits.
The agent does not need to interpret a PDF; it receives snippets and affected URLs.
SEOBolt is built around re-crawling after fixes, not stopping at the audit.
Check your homepage for AI search access, llms.txt quality, crawler rules, structured data, Open Graph, canonical tags, and the first fixes to apply.
Run the audit