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.
Zed is built for speed, and so is fixing SEO when the data is already in the editor. Add SEOmatic as a custom context server and Zed's agent can audit your live site, read your Search Console data and fix SEO issues in the code you have open.

SEOmatic is a hosted MCP server that Zed adds as a custom context server by URL. Zed's agent calls SEOmatic's tools while it works in your project.
October 2026
Zed and a free SEOmatic account. Nothing extra: the connection signs in with OAuth.
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.
Endpoint, auth, every tool and what it costs: SEOmatic MCP server docs.
Clicks, impressions, CTR and top queries for the page you are working on.
Up to 30 pages crawled for duplicate titles, thin content, noindex leaks, canonical problems and broken internal links.
Titles and descriptions rewritten in the code, matched to the queries each page already shows up for.
Why Google excluded a page, from URL Inspection data, in the same panel.
Queries sitting just off page 1, so you know which file to open first.
A 0 to 100 score for one page with its issues by severity, from missing schema to a vague H1.
Zed suits developers who want the SEO answer without the context switch. With SEOmatic, the agent panel becomes the place to check how a page performs in search and fix what is wrong with it.
An example on the Acme Plumbing demo site. You ask Zed:
“How is the page I have open doing on Google? It's /water-heater-repair.”
Zed calls SEOmatic:
gsc_performance: /water-heater-repair by query, Jul 13 to Oct 10 (90 days)site_pages: analyze /water-heater-repairZed answers:
Over Jul 13 to Oct 10 (90 days), /water-heater-repair earned 412 clicks from 9,860 impressions (4.2% CTR, average position 8.7).
In this file, I would change the H1 to "Water Heater Repair, Same Day" and add the schema block. Want the edit?
Also try:
Try these in Zed's agent panel:
One entry in settings.json under context_servers. Pick OAuth or a header, never both.
// settings.json -> context_servers
{
"seomatic": {
"source": "custom",
"url": "https://app.seomatic.ai/api/mcp"
}
}Setting an Authorization header here makes Zed skip the OAuth flow entirely. Use one or the other, never both.
| Route | Best for | How |
|---|---|---|
| Context server with OAuth | Most people, on a machine with a browser | "seomatic": { "source": "custom", "url": "https://app.seomatic.ai/api/mcp" } under context_servers. Approve the sign-in Zed opens. |
| Context server with a key | Remote dev boxes where no browser can open | Same entry plus "headers": { "Authorization": "Bearer smk_live_..." }. Zed then skips OAuth. |
| Skills | Repos where you want the same SEO playbooks every time | npx skills add Minh42/seomatic-mcp --full-depth -a zed. Installs SEOmatic's 20 SEO skills: the CLI skill runs with SEOMATIC_API_KEY, the other 19 use SEOmatic's MCP server. All of them: SEO skills. |
Pick OAuth. No key sits in your settings file, the sign-in takes a minute, and you can revoke access from SEOmatic at any time.
This page is about Zed's own agent, which reads SEOmatic through a context server in settings.json.
Every route reaches the same SEOmatic server, so your workspace, your free questions and your approvals carry across.
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 free trial. See pricing.
Zed's code edits stay under your review. Anything SEOmatic would change on a live site through a connected CMS is staged, never pushed. 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.
Other coding agents: Cursor, Cline, Claude Code and Codex. Explore the site audit, technical SEO fixes and the MCP server. Terminal first? The SEOmatic CLI. All assistants: AI assistants. Full reference: MCP docs.
Using another agent? See Cursor, Cline, Claude Code, or every AI agent.
How do I connect SEOmatic to Zed?
In settings.json, add a seomatic entry under context_servers with source custom and the URL https://app.seomatic.ai/api/mcp. Zed opens the SEOmatic sign-in; approve it and pick your site.
Can Zed do SEO?
Zed's agent can edit the code behind your SEO. With SEOmatic added as a context server, it also audits your live site, reads your Search Console data and checks index status, so its fixes target real problems.
Why does Zed skip the sign-in screen?
If you set an Authorization header on the context server, Zed uses it and skips OAuth. Remove the header to sign in with OAuth, or keep it with a valid SEOmatic API key.
Can I use an API key instead of OAuth?
Yes. Add a headers entry with Authorization set to Bearer plus a key from SEOmatic's Settings, AI Agents, API Keys. This suits remote machines with no browser. Keep the key out of shared settings.
Is SEOmatic for Zed free?
Yes. The account is 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 changes in your CMS.
Are the numbers real?
Yes. They come from your own Search Console property, and every answer names its exact date range and day count, so you can check any figure in Search Console.
Do I need a Google Cloud project?
No. You connect Search Console to SEOmatic with one Google sign-in, which takes about a minute.
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.
Can I add the SEOmatic skills to Zed?
Yes. Run npx skills add Minh42/seomatic-mcp --full-depth -a zed in your project. The 20 skills give the agent step-by-step playbooks like the SEO audit and striking distance keywords; the CLI skill runs with SEOMATIC_API_KEY and the other 19 use SEOmatic's MCP server.
I run Claude Code inside Zed. Which setup do I follow?
Connect SEOmatic in Claude Code itself with claude mcp add --transport http seomatic https://app.seomatic.ai/api/mcp. This page covers Zed's own agent.
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.