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 Trial for $1, credited to your first payment.
Devin takes a task and works it through. With SEOmatic as an MCP server, the SEO tasks you hand it start from real data: your Search Console, a live audit of your site and Google's index status, so Devin fixes the problems that cost you traffic.

SEOmatic is a hosted MCP server that Devin connects to over HTTP. Devin Desktop is where Windsurf went, Devin CLI shares the same agent and config, and the setup is one config entry.
November 2026
A Devin account and a free SEOmatic account. On Devin Enterprise, an admin has to enable Devin Local first, and if your enterprise uses an MCP allowlist, app.seomatic.ai has to be on it. In Devin's config the key is url; the old serverUrl key only worked in the retired Cascade agent.
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.
Crawl the live site, then have Devin turn each issue into a fix in the codebase.
Pages that earn impressions but not clicks, with their queries, so Devin writes titles that match real searches.
URL Inspection data for up to 50 URLs per call, so Devin fixes the robots, canonical or redirect rule behind each exclusion.
Found in a live crawl and fixed at the source, in the templates or content files.
After a redirect or URL change, Devin checks which old URLs Google still has indexed and which still return a 404.
Re-audit the changed pages on the live site to confirm each fix landed.
Devin is at its best with a well-scoped task and room to finish it. SEOmatic turns vague SEO asks into those tasks: a list of concrete issues, each with the page, the evidence and the fix, that Devin can work through.
An example on the Acme Plumbing demo site. You ask Devin:
“Audit the live site with SEOmatic and turn what you find into a fix plan, one commit per issue.”
Devin calls SEOmatic:
site_audit: crawl of 30 pages on the live sitegsc_performance: clicks by page, Sep 12 to Oct 9 (28 days)Devin answers:
The crawl of 30 pages found 4 issues worth a commit, ordered by the clicks at stake (Sep 12 to Oct 9, 28 days):
ServicePage template hardcodes the site name as the whole title.I will open one commit per issue on a branch and re-run the audit on the preview URL before you merge.
Also try:
Give Devin tasks like these:
One config entry in Devin Desktop or the CLI, or a form in Devin on the web.
// ~/.config/devin/mcp_config.json (or .devin/mcp_config.json in one repo)
{
"mcpServers": {
"seomatic": { "url": "https://app.seomatic.ai/api/mcp" }
}
}
# or: devin mcp add -s user seomatic https://app.seomatic.ai/api/mcp
# (without -s user it is saved for this repo only)
# Devin on the web: Customize > MCPs > Add MCP > Add custom MCP > HTTP > OAuth > Save > ConnectDevin prompts for the sign-in the first time it uses the server, not when you save the config, so give it a SEOmatic task to finish the setup. Devin Local asks you before every MCP tool call: allow one tool or every SEOmatic tool, for the session or for good, or add mcp__seomatic__* to permissions.allow in your Devin config. Run devin mcp list to see the server and its state. Older Devin Desktop builds kept MCP servers in the main config file; current builds migrate them to mcp_config.json on their own.
| Route | Best for | How |
|---|---|---|
| Desktop and CLI config | Most people, in Devin Desktop or Devin CLI | A seomatic server with "url": "https://app.seomatic.ai/api/mcp" under mcpServers in ~/.config/devin/mcp_config.json or .devin/mcp_config.json, or devin mcp add -s user seomatic https://app.seomatic.ai/api/mcp (without -s user it saves to this repo only). Devin prompts for the OAuth sign-in when it first uses the server; devin mcp login seomatic runs it by hand. |
| Devin on the web | Devin at app.devin.ai, shared with your organization | Customize > MCPs > Add MCP > Add custom MCP. Transport HTTP, Server URL https://app.seomatic.ai/api/mcp, authentication method OAuth. Save, click Connect to finish the sign-in, then Test tools to check the list. Pick Personal access so each teammate signs in to their own SEOmatic workspace. Needs the Manage MCP Servers permission; without it you get Suggest MCP Integration instead. |
| Skills | Repos where you want Devin to follow the same SEO playbook every run | npx skills add Minh42/seomatic-mcp --full-depth -a devin. Adds SEOmatic's 21 SEO skills to .devin/skills: the CLI skill runs with SEOMATIC_API_KEY, the other 20 use SEOmatic's MCP server. All of them: SEO skills. |
| SEOmatic CLI | Headless runs where no browser can open | npx -y seomatic login --device signs in from any terminal, or set SEOMATIC_API_KEY. Then npx -y seomatic tools lists every tool. |
Pick the Desktop and CLI config. It is one entry, it signs in with OAuth so no key sits in a file, and Devin asks you before each SEOmatic tool call. Working in Devin on the web? Use Customize > MCPs; it is the same server and the same sign-in.
This page is about Devin Desktop and Devin CLI, the coding agent from Cognition.
All of them connect to 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 Trial for $1, credited to your first payment. See pricing.
Search Console reads and audits are free with no limit, however many tools a Devin task calls. Free questions only cover live market data, and one question covers up to 5 lookups. Start a trial when you want SEOmatic's agents to stage fixes for a bigger backlog.
Devin's code changes go through 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 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.
Other coding agents: Claude Code, Codex, Cursor and Gemini CLI. Explore the site audit, technical SEO fixes and page indexing. Headless runs: the SEOmatic CLI. All assistants: AI assistants. Full reference: MCP docs.
Using another agent? See Claude Code, Codex, Cursor, or every AI agent.
How do I connect SEOmatic to Devin?
Add a seomatic entry with the url https://app.seomatic.ai/api/mcp under mcpServers in ~/.config/devin/mcp_config.json, or run devin mcp add -s user seomatic https://app.seomatic.ai/api/mcp. Then ask Devin to use a SEOmatic tool; it opens the sign-in the first time, so approve it and pick your site. In Devin on the web, use Customize > MCPs > Add MCP > Add custom MCP with transport HTTP and auth OAuth, then Connect.
Can Devin do SEO?
Devin can change the code behind your SEO. With SEOmatic connected, it also sees your Search Console data, a live audit of your site and Google's index status, so the SEO tasks you give it start from real problems.
SEOmatic is in the config but nothing works. Why?
Devin only prompts for the sign-in the first time it uses the server. Ask it to call a SEOmatic tool, or run devin mcp login seomatic, and approve the sign-in. If the server shows Needs auth in Devin Desktop, click Authenticate. If you added it with devin mcp add and no -s user, it only loads in that one repo; run devin mcp list to check, and add it again with -s user. If a sign-in keeps failing, run devin mcp logout seomatic, then devin mcp login seomatic.
Devin keeps asking before it uses SEOmatic. Can I stop that?
Yes. When Devin asks, allow every SEOmatic tool for the session or for good. Or add mcp__seomatic__* to permissions.allow in your Devin config. SEOmatic tools show up as mcp__seomatic__ followed by the tool name.
I used Windsurf. Is this the same setup?
Nearly. Windsurf became Devin Desktop in June 2026, and its Cascade agent, the one that used serverUrl in ~/.codeium/windsurf/mcp_config.json, was removed in September 2026. Follow the steps on this page: the key is url, and the file is ~/.config/devin/mcp_config.json.
Is SEOmatic for Devin free?
The SEOmatic 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. One question covers up to 5 lookups. Paid plans remove the limit and add agents that stage changes in your CMS.
Are the numbers Devin quotes real?
Yes. They come from your own Search Console property through SEOmatic, and each answer names its exact date range and day count, so you can check every figure.
Do I need a Google Cloud service account?
No. You connect Search Console to SEOmatic with one Google sign-in in about a minute. Devin never needs Google credentials.
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 SEOmatic skills to Devin?
Yes. Run npx skills add Minh42/seomatic-mcp --full-depth -a devin in your repo. The 21 skills give Devin step-by-step playbooks like the SEO audit and striking distance keywords; the CLI skill runs with SEOMATIC_API_KEY and the other 20 use SEOmatic's MCP server.
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.