Claude Code
One command connects your Search Console to the terminal, so Claude Code fixes SEO in the code.
Warp SEO: Ask Your Terminal Why Traffic Moved
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.
- Paste one URL in Warp's MCP servers page
- Browser sign-in for local agents, a key for cloud agents
- Server logs and Search Console in the same session
Warp
About SEOmatic for Warp
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.
Last Updated
November 2026
Requirements
Warp with its agent turned on, and a free SEOmatic account. Warp's Free plan includes no agent usage, so add usage or your own model key, or use Build or higher. For Warp cloud agents, create an API key in Settings, AI Agents, API Keys.
Pricing
Free to connect. Search Console, audits and page checks have no limit; market data uses 5 free questions a month (plus a one-time 10 when you connect Search Console). Paid plans add agents that stage fixes for your approval. See pricing.
Full Docs
Endpoint, auth, every tool and what it costs: SEOmatic MCP server docs.
Warp for SEO, Grounded in Your Search Console
What Warp Can Do for Your SEO
Migration and Redirect Checks
After a URL change, Warp checks which new pages Google indexed and tests the old URLs for the right redirect.
Index Problems Traced to the Server
For pages Google skipped, Warp looks for the noindex header, robots rule or redirect in your config that explains it.
Titles Rewritten From Real Queries
It reads the searches each page appears for and rewrites the title and description in your code to match.
Pre-Deploy Audit
An audit of up to 30 pages for missing titles, broken links, duplicate descriptions and slow pages, before you ship.
AI Answer Gaps
Which questions ChatGPT, Claude and Google AI Overviews answer without naming you, and who they name instead.
CMS Fixes You Approve
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.
Example: Ask Warp About Your Site
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/emergency
Warp answers:
Mostly yes, Sep 28 to Oct 11 (14 days):
- /water-heater-repair and /drain-cleaning-cost are indexed and already get 1,140 impressions between them.
- /emergency-plumber is “Discovered, currently not indexed”. Its old URL, /services/emergency, returns a 302 instead of a 301, so Google still treats the old page as the main one.
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:
- “Which pages has Google not indexed, and why?”
- “Audit the site before I deploy”
- “Which pages get impressions but few clicks?”
- “Do AI answers cite our pages?”
Where the Terminal Helps SEO
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:
- Redirects: Search Console says a page is not indexed, and Warp runs
curl -Ito find the 302 that should be a 301. - Robots and headers: a page drops out of Google, and Warp finds the
X-Robots-Tagset by a proxy rule. - Bot traffic: Warp reads your access logs for Googlebot and AI crawlers, while SEOmatic shows how those pages perform in search.
- Deploys: before you ship, an audit of up to 30 pages, then a recheck of indexing a few days after.
Warp SEO Prompts to Try
Ask the Warp agent, from your site's repo or server:
- “We moved to new URLs two weeks ago. Is Google picking them up, and do the old ones redirect?”
- “List the pages Google has not indexed and find the cause in our server config.”
- “I fixed the redirect for /emergency-plumber. Is the new URL indexed yet?”
- “Audit the site before I deploy and fix anything that would hurt rankings.”
- “Which pages get impressions on Google but few clicks? Rewrite their titles.”
- “Which questions do AI assistants answer without citing us?”
The SEO Tools Warp Gets
- Search Console performance and insights: clicks, impressions, CTR and position, period comparisons, CTR outliers and cannibalization, with exact date ranges.
- Indexing checks: whether Google indexed a URL, and why not.
- Site audit and page scores: up to 30 pages per crawl, or a 0 to 100 score for one URL.
- AI visibility and citations: where ChatGPT, Claude and Google AI Overviews mention or cite you.
- Keyword and backlink research, from your free questions or your paid plan's credits.
- Tasks and campaigns on paid plans: fixes for CMS sites, staged for your approval.
Open Warp's MCP servers page to see SEOmatic's tools, and the SEO MCP server reference for every parameter.
How It Works, Step by Step
- You ask the Warp agent a question about your site.
- Warp calls the SEOmatic tools it needs, such as an indexing check or a period comparison, and runs terminal commands where they help.
- SEOmatic returns your real data and its own analysis, with exact date ranges.
- Warp explains the cause and edits your code or config. You review every change before it ships.
- For CMS sites on a paid plan, Warp stages the fix in SEOmatic instead. You approve it, and SEOmatic applies it with a rollback point.
How to Connect SEOmatic to Warp
About a minute, with Warp installed and its agent turned on.
- Open MCP servers. In Warp, open Settings, then Agents, then MCP servers. You can also search for Open MCP Servers in the Command Palette, or open Warp Drive, Personal, MCP Servers.
- Add the SEOmatic URL. Click + Add, choose Streamable HTTP or SSE Server (URL), and paste a server named seomatic with the URL https://app.seomatic.ai/api/mcp.
- Click Start and sign in. Click Start on the seomatic server. Warp opens the SEOmatic sign-in in your browser. Sign in or create a free account, approve access and pick your site.
- Check the tools. On the MCP servers page, check that seomatic is running and lists its tools. If it lists only check_site and connect_seomatic, the sign-in has not run yet: stop and start seomatic to finish it, or use the API key header below. To let Warp call SEOmatic without asking, add seomatic to the MCP allowlist under Settings, Agents, Profiles.
- Ask about your site. Ask the agent: “How did my site do on Google over the last 28 days?” The answer should name the date range and your real numbers.
Warp setup
// 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, stored as a managed secret named SEOMATIC_API_KEY
// (pass with oz agent run-cloud --mcp, or under mcp_servers
// in an agent config file)
{
"seomatic": {
"url": "https://app.seomatic.ai/api/mcp",
"headers": {
"Authorization": "Bearer {{SEOMATIC_API_KEY}}"
}
}
}Warp stores the sign-in on your device and reuses it, so you sign in once per machine. If the agent cannot see SEOmatic, open the MCP servers page, stop and start seomatic, and finish the sign-in if it asks again; View Logs on the server shows the error. Still stuck on the sign-in? rm -rf /.mcp-auth clears Warp's stored MCP sign-ins (all servers), then start seomatic again. Warp can also pick up a SEOmatic entry made for Claude Code (/.claude.json) once you turn on Auto-spawn servers from third-party agents on the MCP servers page; a project .mcp.json needs a manual start each session.
Local Agent, Cloud Agent or Skills?
| 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, click Start, sign in. |
| Cloud agent with an API key | Warp cloud agents, which cannot open a browser | Add "headers": { "Authorization": "Bearer {{SEOMATIC_API_KEY}}" } to the seomatic entry and store the key as a Warp managed secret named SEOMATIC_API_KEY, or add SEOmatic once as a managed MCP server under Integrations in the Oz web app, authorize it, and reference it by its warp_id. |
| 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's Local Agent or Cloud Agents: Which One Is This?
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.
- The local agent runs on your machine, in the Warp app. It can open your browser, so it signs in to SEOmatic with OAuth.
- Cloud agents run on Warp's servers and cannot open a browser. Give them SEOmatic with an API key header from a managed secret, or authorize SEOmatic once as a managed MCP server in the Oz web app (Integrations) and reference it by its warp_id.
This page covers both. For other terminal agents, see Claude Code or OpenCode.
What Is Free and What Is Paid
Connecting is free, and so is the SEOmatic account behind it: no card. Free covers the diagnosis with no limit: 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, uses free questions: 5 a month, plus a one-time 10 bonus questions when you connect Google Search Console. One question covers up to 5 lookups.
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 Trial for $1, credited to your first payment. 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.
Nothing Changes on Your Site Without Your Approval
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 in Approval mode 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.
Keep Exploring
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.
Frequently Asked Questions
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 and click Start. 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 or Warp Factories.
Does SEOmatic work with Warp cloud agents?
Yes. Create an API key in SEOmatic under Settings, AI Agents, store it as a Warp managed secret, and add the header Authorization: Bearer {{SEOMATIC_API_KEY}} to the seomatic entry. Or add SEOmatic as a managed MCP server in the Oz web app, authorize it once, and reference it by its warp_id. 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. Search Console reports, site audits and page checks are free with no limit. Live market data (keyword volumes, competitors, backlinks) uses free questions: 5 a month, plus a one-time 10 when you connect Search Console. Paid plans remove the limit and add agents that stage fixes, with a 14-Day Trial for $1, credited to your first payment.
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. If seomatic lists only check_site and connect_seomatic, you are not signed in yet: stop and start it, or add the API key header. If it runs but the agent ignores it, start a new conversation, name SEOmatic in your request, or try another model. 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.
SEOmatic in other AI agents
Same server, same tools, same approval rules. Pick the agent that fits the job.
Codex
Two commands give Codex your Search Console data, so it fixes SEO where the bug lives: in your code.
Grok Build
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
Kimi K3 in Kimi Code CLI, reading your real Search Console and fixing what it finds in your repo.
DeepSeek
DeepSeek, working from your real Search Console data through the SEOmatic plugin for DeepSeek Harness.
Cursor
One mcp.json entry, and Cursor's agent works from your real Search Console data while it edits your code.