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.
Warp's agent already runs commands, reads logs and edits code in your terminal. Add SEOmatic as an MCP server and it can also see which pages lose clicks on Google, which ones Google skipped, and where AI answers leave you out. Then it fixes the cause in your code, or on paid plans stages the fix in your CMS for your approval.

SEOmatic is a hosted MCP server that Warp adds by URL on its MCP servers page. The local agent signs in with OAuth in your browser; cloud agents send an API key header. Both call SEOmatic's SEO tools on one workspace.
October 2026
Warp with its agent turned on, and a free SEOmatic account. For Warp cloud agents, 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.
After a URL change, Warp checks which new pages Google indexed and tests the old URLs for the right redirect.
For pages Google skipped, Warp looks for the noindex header, robots rule or redirect in your config that explains it.
It reads the searches each page appears for and rewrites the 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, before you ship.
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, Warp stages fixes in SEOmatic on paid plans for your approval.
Warp's agent already runs commands, reads logs and edits files. Give it your search data too, and it can follow an SEO problem from Search Console into your server config.
An example on the Acme Plumbing demo site. You ask Warp:
“We moved to new URLs two weeks ago. Is Google picking them up, and are the old ones redirecting?”
Warp calls SEOmatic:
seomatic gsc_indexing: 3 new service URLsseomatic gsc_performance: Sep 28 to Oct 11 (14 days), by pagecurl -sI https://acme-plumbing.com/services/emergencyWarp answers:
Mostly yes, Sep 28 to Oct 11 (14 days):
The redirect lives in nginx/sites/acme.conf, line 42. I can change it to a permanent redirect for you to review, then ask SEOmatic to check the page again in a few days.
Also try:
Many SEO problems are not in the page copy. They sit in server config, redirects, headers and deploy scripts, which is exactly where a terminal agent works. With SEOmatic connected, Warp can check both sides in one go:
curl -I to find the 302 that should be a 301.X-Robots-Tag set by a proxy rule.Ask the Warp agent, from your site's repo or server:
Open Warp's MCP servers page to see SEOmatic's tools, and the SEO MCP server reference for every parameter.
About a minute, with Warp installed and its agent turned on.
// Settings > Agents > MCP servers > + Add >
// Streamable HTTP or SSE Server (URL)
{
"seomatic": {
"url": "https://app.seomatic.ai/api/mcp"
}
}
// Warp cloud agents: they cannot open a browser,
// so send an API key instead
{
"seomatic": {
"url": "https://app.seomatic.ai/api/mcp",
"headers": {
"Authorization": "Bearer smk_live_..."
}
}
}Warp stores the sign-in on your device and reuses it, so you sign in once. If the agent cannot see SEOmatic, open the MCP servers page, stop and start seomatic, and finish the sign-in if it asks again.
| Route | Best for | How |
|---|---|---|
| Local agent with sign-in | Most people: the Warp agent on your own machine | Settings, Agents, MCP servers, + Add, Streamable HTTP or SSE Server (URL), paste the config above, sign in. |
| Cloud agent with an API key | Warp cloud agents, which cannot open a browser | Add "headers": { "Authorization": "Bearer smk_live_..." } to the seomatic entry, or add SEOmatic as a managed MCP server under Integrations in the Oz web app. |
| Skills only | Running SEO checks through the SEOmatic CLI | npx skills add Minh42/seomatic-mcp -a warp, with SEOMATIC_API_KEY set. |
Pick the local agent with sign-in. It is one URL and one browser click, and Warp keeps the sign-in on your device. Add the API key header only for cloud agents.
Warp is a terminal with a built-in coding agent. SEOmatic connects to Warp as an MCP server, and the setup depends on where the agent runs.
This page covers both. For other terminal agents, see Claude Code or OpenCode.
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.
Warp's own agent usage is billed by Warp. SEOmatic questions count only the SEOmatic tool calls, not the terminal commands Warp runs.
Warp works in two places, and both keep you in charge. In your terminal, Warp asks before running commands that change things, according to your Warp settings, and you review code and config changes. In your CMS, it can only stage a fix in SEOmatic. 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.
Using another terminal agent? See Claude Code SEO, OpenCode, goose and Codex. 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 Claude Code, OpenCode, Goose, or every AI agent.
How do I connect SEOmatic to Warp?
In Warp, open Settings, Agents, MCP servers, click + Add and choose Streamable HTTP or SSE Server (URL). Paste a server named seomatic with the URL https://app.seomatic.ai/api/mcp. Warp opens the SEOmatic sign-in in your browser; sign in and pick your site.
Do I need an API key?
Not for the local Warp agent. It signs in with OAuth in your browser. Warp cloud agents cannot open a browser, so give them an API key in an Authorization header, or add SEOmatic once as a managed MCP server in the Oz web app.
Does SEOmatic work with Warp cloud agents?
Yes, with an API key. Create one in SEOmatic under Settings, AI Agents and add the header Authorization: Bearer followed by your key to the seomatic entry. A URL server that needs OAuth and has no header cannot be used by cloud agents.
What can Warp do that a chat assistant cannot?
Warp can run commands. When SEOmatic says Google skipped a page, Warp can test the redirect with curl, read your server config or check your access logs for crawler visits, then fix the cause and show you the change.
Can Warp fix SEO problems in my code?
Yes. It reads your Search Console data through SEOmatic, finds the cause in your code or server config, such as a noindex header or a temporary redirect, and edits the files. You review the change 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 28 to Oct 11, 14 days. SEOmatic tells the agent to state only numbers that came from a tool result.
Is SEOmatic for Warp 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.
The agent cannot see SEOmatic. What now?
Open Settings, Agents, MCP servers and check that seomatic is running. If it is stopped, click Start. If it asks you to sign in again, finish the sign-in in the browser. For cloud agents, check that the Authorization header is there and the key has not been deleted.
Do I need a Google Cloud project?
No. You connect Search Console to SEOmatic once with a normal Google sign-in, and Warp reaches it through SEOmatic. There is no service account to create.
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.