Claude Code
One command connects your Search Console to the terminal, so Claude Code fixes SEO in the code.
Kimi K3 SEO: Search Data and Code Fixes in One Session
Kimi Code CLI runs Kimi K3 in your terminal, and it can add SEOmatic to its own config. Paste one prompt, sign in once, and Kimi can 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.
- One paste-in prompt: Kimi writes its own mcp.json
- OAuth sign-in, no key to copy
- Finds the problem in Search Console, fixes it in the code
Kimi K3
About SEOmatic for Kimi K3
SEOmatic is a hosted MCP server that Kimi Code CLI adds to its mcp.json. Kimi signs in with OAuth in the browser, or uses an API key from an environment variable, and then calls SEOmatic's SEO tools on one workspace.
Last Updated
November 2026
Requirements
Kimi Code CLI (curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash, then /login) and a free SEOmatic account. The kimi.com web and mobile apps do not document custom MCP servers. For CI, 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.
Kimi K3 for SEO, Grounded in Your Search Console
What Kimi K3 Can Do for Your SEO
Titles and Descriptions From Real Queries
Kimi reads the searches each page shows up for and rewrites its metadata in your code to match them.
Index Problems Traced to the Code
For pages Google skipped, Kimi finds the noindex, canonical or redirect in your repo that explains it.
Pre-Deploy Audit
Before you ship, an audit of up to 30 pages for missing titles, broken links, duplicate descriptions and slow pages.
Structured Data Where It Counts
FAQ, LocalBusiness or Product schema added to the pages that already get impressions, not to every page at once.
AI Answer Check
Which AI assistants cite your pages, which competitors they cite instead, and what those pages have that yours lack.
CMS Fixes You Approve
For WordPress, Shopify, Webflow and other CMS sites, Kimi stages fixes in SEOmatic on paid plans for your approval.
Kimi Code works across your whole repo. Give it your search data too, and it can trace an SEO problem from a Search Console number to the line of code that causes it.
Example: Ask Kimi K3 About Your Site
An example on the Acme Plumbing demo site. You ask Kimi K3:
“Which pages get seen on Google but rarely clicked? Fix their titles in this repo.”
Kimi K3 calls SEOmatic:
seomatic gsc_insights: CTR outliers, Sep 12 to Oct 9 (28 days)read app/(services)/*/page.tsx
Kimi K3 answers:
Two pages stand out, Sep 12 to Oct 9 (28 days):
- /water-heater-repair: 3,410 impressions, 1.2% CTR at position 7.8. The title is “Water Heaters | Acme Plumbing”, and most searches include “repair” and “same day”.
- /drain-cleaning-cost: 2,760 impressions, 0.9% CTR at position 10.6. The title never mentions a price, and the top queries ask “how much”.
I updated the metadata.title and description in both page.tsx files. The diff is ready for you to review. Nothing changes on the live site until you merge and deploy.
Also try:
- “Which pages has Google not indexed, and why?”
- “Audit the site before I deploy”
- “Add FAQ schema to /emergency-plumber”
- “Do AI answers cite our pages?”
Fix SEO in the Code, Not in a Spreadsheet
Most SEO audits end in a list someone has to turn into code. With Kimi Code and SEOmatic, the same session does both:
- Find the problem with real data. Kimi asks SEOmatic which pages lose clicks, which ones Google did not index, or which titles get seen and skipped.
- Find the cause in the repo. A stray noindex in a layout, a canonical built from the wrong env variable, a title template that drops the keyword.
- Change the code. Kimi edits the files and shows you the diff.
- Check after deploy. Ask Kimi to inspect the URL again in Search Console a few days later.
For sites in a CMS like WordPress or Shopify, the fix goes the other way: on paid plans Kimi stages it in SEOmatic, and you approve it before it goes live.
Kimi K3 SEO Prompts for Kimi Code
Run these in Kimi Code from the root of your site's repo:
- “Which pages get impressions on Google but few clicks? Rewrite their titles in the code.”
- “List the pages Google has not indexed and find the cause in this repo.”
- “Audit the site before I deploy and fix anything that would hurt rankings.”
- “My organic clicks fell this month. Which pages lost them, and did a recent commit cause it?”
- “Add LocalBusiness schema to the service pages that get the most impressions.”
- “Which questions do AI assistants answer without citing us?”
The SEO Tools Kimi K3 Gets
- Search Console performance and insights: clicks, impressions, CTR and position, CTR outliers, cannibalization and period comparisons, 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.
The tools appear as mcp__seomatic__<tool> in new sessions. Kimi asks for approval on each call unless you allow them once in ~/.kimi-code/config.toml:
[[permission.rules]]
decision = "allow"
pattern = "mcp__seomatic__*"
If you installed the plugin, use mcp__plugin-seomatic_seomatic__* as the pattern instead. Run /mcp in Kimi Code to see the connection, and the SEO MCP server reference for every tool.
How It Works, Step by Step
- You ask Kimi Code a question about your site, from the repo.
- Kimi K3 calls the SEOmatic tools it needs, such as Search Console insights or an indexing check.
- SEOmatic returns your real data and its own analysis, with exact date ranges.
- Kimi reads the matching files in your repo, explains the cause and edits the code. You review the diff.
- For CMS sites on a paid plan, Kimi stages the fix in SEOmatic instead. You approve it, and SEOmatic applies it with a rollback point.
How to Connect SEOmatic to Kimi K3
About two minutes, with Kimi Code CLI installed and signed in.
- Start Kimi Code. Install Kimi Code CLI with curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash, start kimi and run /login if you have not yet.
- Paste the setup prompt. Copy the setup prompt from this page into Kimi Code. Kimi adds the seomatic server to ~/.kimi-code/mcp.json.
- Start a new session. Run /new. MCP servers load when a session starts. Then run /mcp and check that seomatic is listed.
- Sign in to SEOmatic. Ask Kimi to connect SEOmatic. SEOmatic asks for a sign-in, and Kimi opens it in your browser. Sign in or create a free account, approve access and pick your site. If /mcp shows seomatic as needs-auth, run /mcp-config login seomatic. Kimi asks before each SEOmatic call unless you add an allow rule for mcp__seomatic__* in ~/.kimi-code/config.toml.
- Ask about your site. Ask: “How did my site do on Google over the last 28 days?” The answer should name the date range and your real numbers.
Kimi K3 setup
// ~/.kimi-code/mcp.json (what the setup prompt writes)
{
"mcpServers": {
"seomatic": {
"url": "https://app.seomatic.ai/api/mcp"
}
}
}
// then, in Kimi Code: run /new, ask Kimi to connect SEOmatic
// and sign in. If /mcp shows needs-auth:
/mcp-config login seomatic
// CI or headless: use an API key instead of OAuth
{
"mcpServers": {
"seomatic": {
"url": "https://app.seomatic.ai/api/mcp",
"bearerTokenEnvVar": "SEOMATIC_API_KEY"
}
}
}Put the server in .kimi-code/mcp.json inside a repo instead if you only want SEOmatic in that project; Kimi then lists it in the workspace trust prompt the first time you open that folder. Config changes apply to new sessions, so use /new rather than /reload: right after /reload the first message can go out before the SEOmatic tools load. If /mcp shows seomatic as needs-auth, run /mcp-config login seomatic and finish the browser sign-in. Sign in from Kimi Code in the terminal: the Kimi Code desktop app and kimi web UI can fail to show the sign-in link.
Setup prompt, plugin, mcp.json or skill?
| Route | Best for | How |
|---|---|---|
| Setup prompt | Most people: no file to edit by hand | Paste the prompt above into Kimi Code. It writes the server into ~/.kimi-code/mcp.json. Run /new, ask Kimi to connect SEOmatic and sign in. |
| Kimi Code plugin | People who want SEOmatic's skills and server in one install | /plugins install https://github.com/Minh42/seomatic-mcp in Kimi Code (it installs the latest release), then /new. The server shows in /mcp as plugin-seomatic:seomatic, and its tools as mcp__plugin-seomatic_seomatic__<tool>. |
| Edit mcp.json yourself | Project-level setups, CI, or an API key instead of OAuth | Add "seomatic": { "url": "https://app.seomatic.ai/api/mcp" } under mcpServers. For a key, add "bearerTokenEnvVar": "SEOMATIC_API_KEY". |
| Skills only | Running SEO checks through the SEOmatic CLI | npx skills add Minh42/seomatic-mcp -a kimi-code-cli, with SEOMATIC_API_KEY set. |
Pick the setup prompt. Kimi edits its own config correctly, keeps your other servers, and tells you when to start the new session. Use the plugin if you also want SEOmatic's ready-made SEO workflows.
Kimi K3, Kimi Code CLI or the Kimi App: Which One Is This?
Kimi K3 is Moonshot AI's model. Kimi Code CLI is Moonshot's coding agent that runs it in your terminal, and that is where SEOmatic connects.
- The Kimi app at kimi.com, and the Kimi mobile apps, do not document a way to add custom MCP servers, so this page does not cover them.
- Kimi K3 inside another agent, for example through an API key in Cline or another open agent, uses that agent's own MCP setup: see Cline or Hermes Agent SEO.
This page covers Kimi Code CLI with Kimi K3.
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.
Code edits Kimi makes in your repo are its own work and do not use SEOmatic questions; only the SEOmatic tool calls do.
Nothing Changes on Your Site Without Your Approval
Kimi works in two places, and both keep you in charge. In your repo, Kimi edits files and you review the diff before anything ships. In your CMS, Kimi 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 coding agent? See Claude Code SEO, Codex and Cursor. Running an open model elsewhere? See DeepSeek. 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 DeepSeek, Claude Code, Codex, or every AI agent.
Frequently Asked Questions
How do I connect SEOmatic to Kimi K3?
Use Kimi Code CLI. Paste the setup prompt from this page, and Kimi adds a server named seomatic with the URL https://app.seomatic.ai/api/mcp to ~/.kimi-code/mcp.json. Then run /new, ask Kimi to connect SEOmatic, sign in in the browser and pick your site.
Can I use SEOmatic in the Kimi app at kimi.com?
Not that we can document. Moonshot's docs describe custom MCP servers for Kimi Code CLI only, so this page covers Kimi Code CLI, which runs Kimi K3 in your terminal. If the kimi.com app gains an MCP setting, the same URL will work there.
Why paste a prompt instead of editing a file?
Kimi Code can edit its own config, so the prompt saves you finding the file and getting the JSON right. Kimi keeps any servers you already have and then tells you to start a new session. Editing mcp.json by hand works too.
Do I need an API key?
Not for normal use. Kimi signs you in with OAuth in the browser the first time you ask it to connect SEOmatic. For CI or a server with no browser, create an API key in SEOmatic, set it as SEOMATIC_API_KEY, and add bearerTokenEnvVar to the seomatic entry in mcp.json.
Can Kimi fix SEO problems in my code?
Yes. Kimi reads your Search Console data through SEOmatic, finds the cause in your repo, such as a noindex tag or a weak title template, and edits the files. You review the diff 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 12 to Oct 9, 28 days. SEOmatic tells Kimi to state only numbers that came from a tool result.
Is SEOmatic for Kimi K3 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.
Kimi says it cannot see SEOmatic. What now?
Run /mcp to check the server status. If seomatic is missing, paste the setup prompt again or add it to ~/.kimi-code/mcp.json yourself, then run /new: tools load when a session starts. If Kimi only sees check_site and connect_seomatic, you are not signed in yet: ask Kimi to connect SEOmatic, or run /mcp-config login seomatic once /mcp shows needs-auth. If the tools are listed but Kimi never calls them, start a fresh session with /new instead of /reload. If Kimi asks for approval on every call, add an allow rule for mcp__seomatic__* in config.toml.
Does it work with Kimi K3 in other agents?
Yes, through that agent's own MCP setup. SEOmatic connects to the agent, not the model, so Kimi K3 running in Cline, Hermes Agent or another MCP client uses the steps for that client.
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.
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.
GitHub Copilot
Add SEOmatic to .mcp.json and Copilot works from your real SEO data.