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.
The DeepSeek chat app cannot connect to outside tools, but DeepSeek Harness can. Add the SEOmatic plugin, set one API key, and DeepSeek can read your Google Search Console, explain traffic drops, check indexing and audit pages. On paid plans it stages fixes that wait for your approval.

SEOmatic is a hosted MCP server. In DeepSeek Harness, the dsh-seomatic plugin connects to it with your API key and adds an SEO skill, so DeepSeek can call SEOmatic's tools on one workspace.
October 2026
DeepSeek Harness (npx @deepseek-ai/dsh web, with Node.js installed) and a free SEOmatic account with an API key from Settings, AI Agents, API Keys. The DeepSeek chat app cannot connect.
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.
Which pages lost clicks, whether last year had the same dip, and the most likely cause for each page.
Queries where two of your pages compete, and which one should own each query.
Which of your important URLs Google skipped, with the reason Search Console gives for each.
A crawl of up to 30 pages with issues ranked by severity, from noindex tags to slow pages.
Ideas picked from the searches that already show your site, rather than from generic keyword lists.
On paid plans, DeepSeek stages title, description, content and internal link fixes in SEOmatic.
DeepSeek is a capable, low-cost model, and DeepSeek Harness gives it tools. With SEOmatic plugged in, it can do the slow part of SEO: pulling the numbers, comparing periods and reading pages to explain what changed.
An example on the Acme Plumbing demo site. You ask DeepSeek:
“Why did /drain-cleaning-cost lose traffic, and is it seasonal?”
DeepSeek calls SEOmatic:
mcp__seomatic__gsc_performance: /drain-cleaning-cost, Jul 12 to Oct 9 (90 days)mcp__seomatic__gsc_insights: seasonality, 16 monthsDeepSeek answers:
Mostly not seasonal. Over Jul 12 to Oct 9 (90 days), /drain-cleaning-cost went from about 41 clicks a week to 17.
/emergency-plumber is unaffected.
Want me to stage a fix: trim the drain section from /water-heater-repair and link it to /drain-cleaning-cost? Nothing changes until you approve it.
Also try:
DeepSeek Harness builds each profile from rows, and the plugin adds two:
SEOMATIC_API_KEY from your environment (or $DSH_HOME/.env) and registers an SEO skill that tells DeepSeek how to use the tools well: quote exact date ranges, never invent numbers, and never call a staged change live.https://app.seomatic.ai/api/mcp over streamable HTTP with your key as a Bearer header.The tools appear as mcp__seomatic__*, for example mcp__seomatic__gsc_performance and mcp__seomatic__site_pages. The list comes from SEOmatic when dsh connects, so new tools show up without a plugin update. Without a key, dsh still starts; it just loads no SEOmatic tools.
Ask these in the dsh browser UI once the plugin is loaded:
Every tool and its cost is in the SEO MCP server reference.
About three minutes. You need Node.js and an SEOmatic API key; a free account works.
# Start DeepSeek Harness (needs Node.js)
npx @deepseek-ai/dsh web
# Add the SEOmatic plugin to the web profile
npx @deepseek-ai/dsh plugin --profile web add \
"github:Minh42/seomatic-mcp#path:/plugins/dsh-seomatic"
# Give it your key, then restart dsh web
export SEOMATIC_API_KEY=smk_live_...
npx @deepseek-ai/dsh webNo SEOmatic tools after restarting? The key is missing: dsh starts without it and logs a warning. Set SEOMATIC_API_KEY in the same shell that starts dsh, or in $DSH_HOME/.env, and restart.
| Route | Best for | How |
|---|---|---|
| dsh-seomatic plugin | Running DeepSeek in DeepSeek Harness, in the browser UI or headless | npx @deepseek-ai/dsh plugin --profile web add "github:Minh42/seomatic-mcp#path:/plugins/dsh-seomatic", then export SEOMATIC_API_KEY=smk_live_... and restart. |
| DeepSeek models in another agent | People who run DeepSeek models in Claude Code, Cline or another MCP client | Use that agent's own MCP setup: see Claude Code SEO or Cline. The model does not change the steps. |
| DeepSeek chat app | Not possible | chat.deepseek.com and the DeepSeek mobile apps have no MCP or connector support, so SEOmatic cannot connect there. |
Pick the dsh plugin if you use DeepSeek Harness. It wires the SEOmatic server, the key and an SEO skill in one install. If DeepSeek runs inside another agent you already use, follow that agent's page instead.
DeepSeek means three different things here:
dsh) is DeepSeek's open-source agent, with a browser UI and plugins. This page covers it.In every case, SEOmatic connects to the agent, not the model.
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.
DeepSeek's own model costs are separate from SEOmatic. SEOmatic counts tool calls, not tokens, so a long explanation does not use more questions.
DeepSeek can stage work in SEOmatic, never publish it. 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. Your API key stays in your environment or $DSH_HOME/.env, never in the chat, and you can revoke it in SEOmatic at any time.
Using DeepSeek in another agent? See Claude Code SEO and Cline. Trying another open model? See Kimi K3. Learn what powers the answers: keyword cannibalization, page indexing checks and the Google Search Console integration. All agents: AI SEO agents in every assistant. Full reference: SEO MCP server docs.
Using another agent? See Kimi K3, Claude Code, Cline, or every AI agent.
How do I connect SEOmatic to DeepSeek?
Use DeepSeek Harness. Run npx @deepseek-ai/dsh plugin --profile web add with the SEOmatic plugin from github.com/Minh42/seomatic-mcp, export SEOMATIC_API_KEY with a key from SEOmatic's Settings, AI Agents, API Keys, and restart dsh web. Then ask DeepSeek about your site.
Can I use SEOmatic in the DeepSeek chat app?
No. The DeepSeek chat app at chat.deepseek.com and the mobile apps have no connectors or MCP support. SEOmatic connects to DeepSeek Harness, or to another agent that runs a DeepSeek model.
Why does the plugin use an API key and not a sign-in?
The dsh-seomatic plugin sends your key as a Bearer header, which works the same in the browser UI and on a headless server. Keep the key in your environment or $DSH_HOME/.env, and revoke it in SEOmatic whenever you want.
I added the plugin but DeepSeek has no SEOmatic tools. Why?
dsh starts without the key and loads no SEOmatic tools. Set SEOMATIC_API_KEY in the shell that starts dsh, or in $DSH_HOME/.env, then restart dsh web. The tools appear with names starting mcp__seomatic__.
I use DeepSeek models in Claude Code or Cline. What do I do?
Follow that agent's setup. SEOmatic connects to the agent, not the model, so Claude Code, Cline or any other MCP client running a DeepSeek model uses its normal SEOmatic steps.
Are the numbers real?
Yes. They come from your own Google Search Console through SEOmatic, with exact date ranges such as Jul 12 to Oct 9, 90 days. The plugin's SEO skill tells DeepSeek to state only numbers a tool returned.
Is SEOmatic for DeepSeek free?
Yes. The plugin 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.
Do I need Ahrefs or Semrush data for DeepSeek SEO?
No. Most answers come from your own Search Console, which is free to connect. Keyword volumes, backlinks and competitor data are part of SEOmatic's paid plans, with one free keyword preview per workspace.
Do approved fixes go live on my site?
Yes. After you approve a staged fix in SEOmatic, it goes live through your connected CMS, such as WordPress, Shopify, Webflow or Wix. The previous version is stored so you can roll it back.
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.
One mcp.json entry, and Cursor's agent works from your real Search Console data while it edits your code.
Add SEOmatic to .vscode/mcp.json and Copilot's Agent mode works from your real SEO data.