Google's free service for monitoring your own site's indexing and Google Search queries, clicks and impressions. Its official API supports reporting and site/sitemap operations; a separate daily export can send performance data to BigQuery.
Semrush
SEOIndependent review. Unpaid; no partnership with Semrush. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
SEO and competitive research suite: keyword research, backlinks, site audits and AI-search visibility. Its MCP server, included from the Starter plan, lets agents pull Semrush data using API units.
The five-point review
Judgment, not a score. Documentation checked 2026-10-18.
- Value
- SEO and competitive research suite: keyword research, backlinks, site audits and AI-search visibility. Its MCP server, included from the Starter plan, lets agents pull Semrush data using API units.
- Differentiation
- Documented fit: Keyword and competitor research; Agencies and content teams. Uniqueness is not established.
- Replaceability and switching
- Compare Google Search Console. Not drop-in replacements. Export completeness and migration effort remain unverified.
- Ease and technical aptitude
- Consider the fit limits: Teams expecting all datasets or unlimited API usage in one entry-level subscription. Setup effort has not been scored.
- Interoperability and portability
- See documented MCP, API and import routes below. Import does not prove export; API access does not prove a complete migration path. Check action scope, plans and portability.
Connections: MCP connections · APIs · Portability and vendor lock-in.
- Keyword and competitor research
- Agencies and content teams
- Teams expecting all datasets or unlimited API usage in one entry-level subscription
Top use cases
- Keyword and backlink research source ↗
- Research keyword opportunities and draft an SEO report in a connected assistant source ↗
- Import tagged keyword files into Position Tracking source ↗
In depth
Dataset access and units
Starter, Pro+, SEO Classic Pro and Guru include 50,000 Standard API units per renewal. Classic Business and Advanced require a units package. Traffic and Market data requires a separate Trends API subscription. MCP access does not make all datasets available or provide an automatic scheduler. source ↗
Client setup
Developer guides cover Claude, ChatGPT, Cursor and Antigravity. The marketing page still names Gemini, while its linked developer section directs users to Antigravity instead of Gemini CLI. A current Gemini-app setup is unverified. source ↗
Plans
SEO is $139 monthly or $117.33/month with annual billing. Starter is $199 or $165.17; Pro+ is $299 or $248.17. Advanced is custom. Free tools have usage limits. source ↗
How to use it with AI
How Semrush connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.
| Platform | MCP / connector | API (agent-written code) | Browser | Upload / export |
|---|---|---|---|---|
| Claude (incl. Claude Code) | Not documented Claude and Claude Code setup sections. A named plugin, skill or CLI does not by itself establish an MCP/native connector pairing. Verify the route and client setup. Semrush named integration docs ↗Claude (incl. Claude Code) MCP docs ↗ | Not documented Claude (incl. Claude Code): Claude Code edits files and runs commands Semrush publishes an API, but this pairing still needs network, authentication and execution-scope checks. Semrush API ↗Claude (incl. Claude Code) docs ↗ | Inferred Claude Code with the Claude in Chrome extension (Chrome, Edge and other Chromium browsers). Semrush is a web app; the pairing itself is not documented. Claude (incl. Claude Code) browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Semrush's recorded upload/import status is yes; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route. Semrush file docs ↗Claude (incl. Claude Code) file docs ↗ |
| OpenAI Codex | Not documented Semrush has an official MCP server and OpenAI Codex supports MCP, but Semrush's docs don't name this pairing. Auth setup may differ. Semrush MCP docs ↗OpenAI Codex MCP docs ↗ | Not documented OpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces Semrush publishes an API, but this pairing still needs network, authentication and execution-scope checks. Semrush API ↗OpenAI Codex docs ↗ | Inferred Only in the ChatGPT desktop app; not in the Codex CLI or IDE extension. Semrush is a web app; the pairing itself is not documented. OpenAI Codex browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Semrush's recorded upload/import status is yes; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route. Semrush file docs ↗OpenAI Codex file docs ↗ |
| Google Antigravity | Not documented Antigravity 2.0 and CLI setup sections. A named plugin, skill or CLI does not by itself establish an MCP/native connector pairing. Verify the route and client setup. Semrush named integration docs ↗Google Antigravity MCP docs ↗ | Not documented Google Antigravity: Agents edit code and run tasks Semrush publishes an API, but this pairing still needs network, authentication and execution-scope checks. Semrush API ↗Google Antigravity docs ↗ | Inferred The /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. Semrush is a web app; the pairing itself is not documented. Google Antigravity browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Semrush's recorded upload/import status is yes; Google Antigravity's file status is yes. These flags do not establish a file-transfer route. Semrush file docs ↗Google Antigravity file docs ↗ |
Semrush's docs also name: ChatGPT.
Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.
To verify Gemini marketing mention differs from developer setup, which directs Google CLI users to Antigravity. Current Gemini-app setup is unverified.
Agent compatibility
| Level | Status | Detail / source |
|---|---|---|
| Native connector / MCP | Yes | Official docs ↗ |
| API / CLI | Yes | Official docs ↗ |
| Browser / manual | No | Browser access is recorded alongside a documented programmatic route. |
| File upload / import | Yes | Official docs ↗ |
Recorded Oct 18, 2026. Setup and plan limits vary; check the vendor's docs. How levels are assigned.
Appears in these proposed stacks
Research & market intelligence Search & competitors
Paid media & ads Search insight
An official MCP server is documented for this tool. These platforms separately document MCP client support: ChatGPT, Claude, Cursor, Gemini (Google), Google Antigravity, Grok, Grok Bot, Lindy, LM Studio, Mistral Vibe, OpenAI Codex. This inventory does not establish compatible transport, authentication or actions for a pairing. Check the connection matrix and linked sources.
Automation hubs to assess for a custom API connection: Gumloop, Make, n8n, Zapier. Verify credentials, supported requests, limits and error handling; no configured integration is implied.
Workflows using this tool
- Turn keyword research into a content plan and tasks
- Write a monthly SEO and product report
- Fix site-audit issues as pull requests
- Take your site multilingual
- Make press releases easy for AI answers to quote
Explained in the wiki
Related skills
Review
No long-form review yet. Verdict is based on research, not hands-on testing.