Claude Code
One command connects your Search Console to the terminal, so Claude Code fixes SEO in the code.

Each local area page used to take us half a day to create and optimize.
With SEOmatic, we can create hundreds of pages in the same time, which helps our clients make the best use of their budget.
It's transformed how we deliver scalable SEO solutions.
Will Hawkins
Marketing Director, Digi-Business UK
Agents read your Search Console data, do the work, and prove what actually moved. You decide what ships.
14-Day Free Trial. $1 today, credited to your first payment.
Antigravity runs several agents at once across your editor, a desktop app and the agy terminal. Add SEOmatic with one API key, and those agents can see which pages lose clicks on Google, which ones Google skipped, and where AI answers leave you out. Then they fix the cause in your code, or on paid plans stage the fix in your CMS for your approval.

SEOmatic is a hosted MCP server that Antigravity reads from its mcp_config.json. The IDE, the desktop app and agy send your SEOmatic API key with each request and call SEOmatic's SEO tools on one workspace.
October 2026
Google Antigravity (IDE or desktop app) or the agy CLI, signed in with your Google account, and a free SEOmatic account. Create an API key in Settings, AI Agents, API Keys.
Free to connect, with 5 questions a month from your own data (plus 10 once you connect Search Console). Paid plans add agents that stage fixes for your approval. See pricing.
Endpoint, auth, every tool and what it costs: SEOmatic MCP server docs.
Antigravity ranks the pages worth fixing first, using clicks, positions and indexing status, then splits the work across agents.
For pages Google skipped, an agent finds the noindex, canonical or redirect in your repo that explains it.
Antigravity reads the searches each page appears for and rewrites its title and description in your code to match.
An audit of up to 30 pages for missing titles, broken links, duplicate descriptions and slow pages, run from the agy terminal.
Which questions ChatGPT, Claude and Google AI Overviews answer without naming you, and who they name instead.
For WordPress, Shopify, Webflow and other CMS sites, Antigravity stages fixes in SEOmatic on paid plans for your approval.
Antigravity is built to hand work to several agents in parallel. With SEOmatic connected, one agent can read the search data while others fix titles, templates and schema in your code.
An example on the Acme Plumbing demo site. You ask Google Antigravity:
“Plan this sprint's SEO work: which three pages should we fix first, and why?”
Google Antigravity calls SEOmatic:
seomatic gsc_insights: striking distance, Sep 14 to Oct 11 (28 days)seomatic gsc_indexing: /emergency-plumberread src/routes/**/+page.svelteGoogle Antigravity answers:
Three pages, in this order, Sep 14 to Oct 11 (28 days):
I can give each fix to its own agent and show you one diff per page. Nothing goes live until you merge and deploy.
Also try:
Most agents sign in to SEOmatic with OAuth: a browser window, one click, done. Antigravity has an open upstream bug with that flow for remote MCP servers (issue 25 on the Antigravity CLI repo). Each launch registers a new client and the sign-in page never opens, so the tools never load.
An API key sidesteps it. Antigravity sends the key on every request, so there is no sign-in step to fail. The key belongs to one SEOmatic workspace, you can create one in a few seconds, and you can delete it in SEOmatic at any time. Once Google fixes OAuth, you can drop the headers block and sign in instead.
If your SEOmatic setup lived in Gemini CLI on a personal Google account, it stopped working on June 18, 2026. Moving it takes a minute:
serverUrl, so an old httpUrl entry will not load as is.Workspace accounts and paid Cloud keys can keep Gemini CLI: see Gemini SEO.
Ask these in the Antigravity agent panel or in agy, from your site's repo:
Every tool, with its parameters and cost, is in the SEO MCP server reference.
About two minutes, with Antigravity or agy installed and signed in to Google.
// ~/.gemini/config/mcp_config.json
// (or .agents/mcp_config.json for one workspace)
{
"mcpServers": {
"seomatic": {
"serverUrl": "https://app.seomatic.ai/api/mcp",
"headers": {
"Authorization": "Bearer smk_live_..."
}
}
}
}
// or, from a terminal:
agy mcp add -H "Authorization: Bearer smk_live_..." \
seomatic https://app.seomatic.ai/api/mcpUse serverUrl, not url or httpUrl: Antigravity does not load remote servers written with the older keys. If the tools do not appear, reopen Manage MCP Servers and check that seomatic is listed without an error. Keep the key out of shared repos: use the global file, not .agents/mcp_config.json, unless the repo is private to you.
| Route | Best for | How |
|---|---|---|
| Config file with an API key | Most people: one block covers the IDE, the desktop app and agy | Paste the config above into ~/.gemini/config/mcp_config.json (or View raw config in the agent panel). The key must be serverUrl. |
| agy mcp add | Terminal users who would rather run one command | agy mcp add -H "Authorization: Bearer smk_live_..." seomatic https://app.seomatic.ai/api/mcp |
| Skills only | Running SEO checks through the SEOmatic CLI | npx skills add Minh42/seomatic-mcp -a antigravity (or -a antigravity-cli), with SEOMATIC_API_KEY set. |
Pick the config file with an API key. Antigravity's OAuth sign-in for remote MCP servers has an open upstream bug, and the key avoids it completely. One block in one file gives every Antigravity surface the same SEOmatic tools.
Google Antigravity is Google's agent-first coding tool. It comes as an IDE, a desktop app and a terminal CLI called agy, and they share one MCP config, which is where SEOmatic connects.
This page covers Antigravity: the IDE, the desktop app and agy.
Connecting is free, and so is the SEOmatic account behind it: no card. A free account answers 5 questions a month from your own data, plus 10 bonus questions once you connect Google Search Console. Each tool call counts as one question, so a big request can use a few.
Free covers the diagnosis: Search Console reports and insights, site audits of up to 30 pages, live page analysis, and your AI visibility results. Live market data, like keyword volumes, backlink profiles and competitor domains, is part of paid plans, with one free keyword preview per workspace.
Paid plans remove the question limit and add the treatment: agents stage fixes on your site (titles, descriptions, content updates, technical fixes, internal links) and run campaigns and fresh AI visibility scans. Every paid plan starts with a 14-day free trial. See pricing.
Code edits Antigravity makes in your repo are its own work and do not use SEOmatic questions; only the SEOmatic tool calls do. Running several agents at once can use several questions in one request.
Antigravity can work in your repo and in SEOmatic, and both keep you in charge. In your repo, agents edit files and you review the diffs before anything ships. In your CMS, an agent can only stage a fix in SEOmatic. The API key you give Antigravity can be deleted in SEOmatic at any time. A staged change is a proposal: it says what will change and why, and nothing touches your site until you approve it. The assistant records your decision, and it is told never to approve anything on its own judgment. Approved fixes start within seconds, the page's previous state is stored, and any applied change can be rolled back. Changes that could take a page out of Google, like a noindex, need an extra explicit confirmation.
Still on Gemini CLI through Workspace? See Gemini SEO. Using another coding agent? See Claude Code SEO, Cursor and Kiro. Learn what powers the answers: page indexing checks, technical SEO fixes and meta tags. All agents: AI SEO agents in every assistant. Full reference: SEO MCP server docs.
Using another agent? See Gemini, Claude Code, Cursor, or every AI agent.
How do I connect SEOmatic to Antigravity?
Create an API key in SEOmatic under Settings, AI Agents. In Antigravity, open the … menu in the agent panel, then MCP Servers, Manage MCP Servers, View raw config, and add a server named seomatic with serverUrl https://app.seomatic.ai/api/mcp and the header Authorization: Bearer followed by your key. In the terminal, agy mcp add with the same header does the same thing.
Why use an API key instead of signing in?
Antigravity has an open upstream bug with OAuth sign-in for remote MCP servers (issue 25 on the google-antigravity/antigravity-cli repo). Each launch registers a new client and the sign-in page never opens, so the connection never finishes. An API key in the headers avoids that step. When Google fixes it, you can remove the headers and sign in with OAuth.
Does one setup cover the IDE, the desktop app and agy?
Yes. They read the same MCP config file, ~/.gemini/config/mcp_config.json, so adding SEOmatic once makes it available in all three. A workspace file at .agents/mcp_config.json limits it to one project.
I used SEOmatic in Gemini CLI. What changed?
Gemini CLI stopped serving free, Google AI Pro and Ultra personal accounts on June 18, 2026, and Antigravity's agy CLI replaced it. Add SEOmatic to Antigravity with the config on this page. Note the key name: Antigravity needs serverUrl, so an old httpUrl entry will not load. Workspace accounts can keep using Gemini CLI.
Why does Antigravity ignore my server?
Check the key name first. Remote servers must use serverUrl; url and httpUrl are not accepted. Then check that the file is valid JSON, that the Authorization value starts with Bearer and a space, and that the key has not been deleted in SEOmatic.
Can Antigravity fix SEO problems in my code?
Yes. It reads your Search Console data through SEOmatic, finds the cause in your repo, such as a noindex tag or a weak title template, and edits the files. You review the diffs and deploy when you are ready.
Are the numbers real?
Yes. They come from your own Google Search Console through SEOmatic, with exact date ranges such as Sep 14 to Oct 11, 28 days. SEOmatic tells the agent to state only numbers that came from a tool result.
Is SEOmatic for Antigravity free?
Yes. Connecting and the SEOmatic account are free, with no card. A free account answers 5 questions a month from your own data, plus 10 bonus questions once you connect Search Console. Paid plans remove the limit and add agents that stage fixes, with a 14-day free trial.
Can it change my site without asking?
No. By default every change SEOmatic proposes waits for your approval before it touches your site, and your assistant is told never to approve on its own. Approved changes are stored with the page's previous state, so any edit to an existing page can be rolled back. If you later want low-risk fixes to go ahead on their own, you can turn that on in your autonomy settings; changes to your URLs or indexing, and new content, still wait for you.
Is my API key safe in the config file?
The key sits in a file on your own machine. Use the global config rather than a workspace file in a shared repo, and never paste the key into a chat. Each key belongs to one SEOmatic workspace, and you can delete it in Settings, AI Agents at any time.
Does SEOmatic measure how I show up in Gemini?
SEOmatic checks your visibility in ChatGPT, Claude and Google AI Overviews by default, and you can add other engines. That is separate from connecting Antigravity, which is about giving Google's coding agent access to your SEO data.
Same server, same tools, same approval rules. Pick the agent that fits the job.
One command connects your Search Console to the terminal, so Claude Code fixes SEO in the code.
Two commands give Codex your Search Console data, so it fixes SEO where the bug lives: in your code.
Two commands give Grok Build your real Search Console data, so it can find what costs you clicks and fix it in the code.
Kimi K3 in Kimi Code CLI, reading your real Search Console and fixing what it finds in your repo.
DeepSeek, working from your real Search Console data through the SEOmatic plugin for DeepSeek Harness.
One mcp.json entry, and Cursor's agent works from your real Search Console data while it edits your code.