SEO integrations for your whole stack
Your SEO and AI-visibility data, wherever you build.
Connect Google Search Console, rank and AI Tracker data to your product, your AI agents or your terminal — all reading from one canonical data layer. Pull it over the REST API, query it in plain language through the MCP server, or script it from the command line. Same numbers, every surface.
One data layer · Bearer auth · No scraping · Same numbers everywhere
Pick how you connect
SEOcrawl AI exposes the same data three ways. Build a product on the REST API, wire your AI agents to the MCP, or automate from your terminal.
SEO API
A Bearer-authenticated REST v1 for your own product, dashboard or data warehouse. Typed JSON, documented rate limits, one key.
- GSC, rank & AI Tracker over HTTP
- sca_live_ Bearer keys from your dashboard
- Same data layer as the MCP
MCP server
Connect Claude, ChatGPT or any MCP client and ask your SEO and AI-visibility data questions in plain language. ~59 tools, one endpoint.
- Natural-language access to your data
- One endpoint for every account
- OAuth sign-in, no keys to paste
Terminal & CLI
Drive your data from any MCP-capable terminal agent — Claude Code, Codex, Cursor. Automate reports and wire checks into CI/CD.
- Pull data from the command line
- Script reports & scheduled checks
- Built for automation and CI/CD
The data behind every integration
Whichever surface you choose, it reads from the same canonical layer — so your dashboard and your agents never disagree.
Search Console
LiveClicks, impressions, CTR and position by query, page and date range — with period-over-period comparisons.
Rankings
LivePosition data and winners/losers derived from your Search Console history, ready to drop into your reports.
AI Tracker
LiveThe prompts you monitor for brand mentions across ChatGPT, Claude, Gemini and Perplexity.
Tasks
LiveRead and write your SEO task board — sync it with your own project-management stack.
GA4 traffic
SoonSessions, conversions and AI referrers. The data layer is ready; REST endpoints are rolling out.
Site audit
SoonCrawl health, on-page and technical issues — the full audit dataset, exposed over the API next.
What you can build
The surfaces are the how. Here's the what.
Custom dashboards & BI
Pipe live SEO metrics into Looker Studio, Google Sheets, Power BI or your own portal via the REST API — no manual exports, always fresh.
AI agents & copilots
Give Claude, ChatGPT or your internal assistant direct, grounded access to your SEO and AI-visibility data through the MCP.
Data warehouse pipelines
Schedule pulls of GSC, rank and AI Tracker data into BigQuery, Snowflake or Postgres and join it with your revenue data.
Automation & CI/CD
Script checks, alerts and reports from your terminal or pipeline, and sync tasks with the tools your team already uses.
Frequently asked questions
What are SEOcrawl AI's integrations?
Three ways to connect your data to your own stack: a Bearer-authenticated REST API for products and dashboards, an MCP server for AI agents, and terminal/CLI access for scripts and CI/CD. All three read from one canonical data layer, so the numbers match everywhere.
Is there an API?
Yes — a REST `/v1` API is live in early access, with Bearer `sca_live_` keys you mint from your dashboard. It covers Search Console performance, properties, AI Tracker prompts and tasks today, with GA4 and site-audit export rolling out. See the SEO API page for endpoints and auth.
What's the difference between the API, MCP and CLI?
Same data, different surface. The REST API is for code — products, dashboards, pipelines. The MCP is for AI agents that query in natural language. The CLI/terminal path drives that same MCP from your command line for scripting and CI/CD. Pick whichever fits how you build.
Can I connect it to Looker Studio or Google Sheets?
Yes — through the REST API. Pull typed JSON on a schedule into Looker Studio, Sheets, Power BI or a warehouse and build whatever reporting layer you like. These are outcomes you build on the API, not one-click native connectors.
Do the API and MCP share one key?
They do. The same `sca_live_` Bearer token authenticates both the REST API and the MCP server, because both sit over one canonical data layer. One credential, two surfaces, identical numbers.
Connect your SEO data today
Start with the REST API, wire up the MCP for your AI agents, or automate from your terminal — all from one data layer.