Claude Code
One command connects your Search Console to the terminal, so Claude Code fixes SEO in the code.
Kilo Code SEO: Search Data Next to Your Code
Kilo Code works in VS Code, JetBrains IDEs and the terminal, and comes with agents for planning, coding and debugging. Add SEOmatic once and Kilo 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 kilo.jsonc entry for VS Code, JetBrains and the CLI
- Sign-in starts by itself, no key to copy
- Plan with one agent, fix with another, same data
Kilo Code
About SEOmatic for Kilo Code
SEOmatic is a hosted MCP server that Kilo Code adds as a remote server. Kilo signs in with OAuth on its own, or sends an API key header, and then calls SEOmatic's SEO tools on one workspace from any of its agents.
Last Updated
November 2026
Requirements
Kilo Code in VS Code, a JetBrains IDE or the CLI, and a free SEOmatic account. For CI or a machine with no browser, 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.
Kilo Code for SEO, Grounded in Your Search Console
What Kilo Code Can Do for Your SEO
A Page-by-Page SEO Plan
With the Plan agent, Kilo ranks the pages worth fixing, with the clicks, positions and indexing status behind each choice.
Page-Two Pages Pushed Up
Kilo finds pages ranking 8 to 20, scores each one, and adds the headings, FAQ or copy they are missing.
Index Problems Traced to the Code
For pages Google skipped, Kilo finds the noindex, canonical or redirect in your repo 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.
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, Kilo stages fixes in SEOmatic on paid plans for your approval.
Kilo Code already knows your codebase. Give it your search data too, and it can turn a Search Console number into a plan, then into a diff.
Example: Ask Kilo Code About Your Site
An example on the Acme Plumbing demo site. You ask Kilo Code:
“Which of our pages are close to page one, and what would move them up?”
Kilo Code calls SEOmatic:
seomatic gsc_insights: striking distance, Sep 13 to Oct 10 (28 days)seomatic site_pages: on-page score for /drain-cleaning-cost
Kilo Code answers:
Two pages are close, Sep 13 to Oct 10 (28 days):
- /drain-cleaning-cost ranks 11.4 for “drain cleaning cost” with 2,610 impressions. The page scores 64 out of 100: no H2 that answers the price question, and no FAQ section.
- /water-heater-repair ranks 9.1 for “water heater repair near me” with 1,980 impressions. The title and H1 never mention your city.
Switch me to the Code agent and I will add a price H2 and FAQ to the first page and put the city in the second page's title. You review the diff before anything ships.
Also try:
- “Which pages has Google not indexed, and why?”
- “Audit the site before I deploy”
- “Add LocalBusiness schema to /emergency-plumber”
- “Do AI answers cite our pages?”
Plan First, Then Fix: Kilo Agents for SEO
Kilo Code ships four agents (Ask, Plan, Code and Debug), and SEO work fits them well:
- Ask or Plan: Kilo pulls your Search Console data through SEOmatic and writes a plan, page by page, with the numbers behind each step.
- Code: Kilo makes the changes in your repo, like titles, headings, schema and internal links.
- Debug: when Google still skips a page, Kilo checks the indexing reason and hunts for the noindex, canonical or redirect that causes it.
Every agent sees the same SEOmatic tools, so the plan and the fix use the same data.
Coming From Roo Code
Roo Code closed on May 15, 2026. If SEOmatic was in your Roo Code MCP settings, moving it is quick:
- Install Kilo Code in VS Code or JetBrains.
- Add the seomatic entry from this page. Kilo uses
"type": "remote"and aurl. - Finish the browser sign-in and ask your usual questions. Your SEOmatic workspace and data have not changed.
Kilo Code SEO Prompts to Try
Try these in Kilo Code with your site's repo open:
- “Which of our pages are close to page one, and what would move them up?”
- “Write a 30-day SEO plan from our Search Console data, then fix the first item.”
- “List the pages Google has not indexed and find the cause in this repo.”
- “Which pages get impressions but few clicks? Rewrite their titles.”
- “Audit the site before I deploy and fix anything that would hurt rankings.”
- “Which questions do AI assistants answer without citing us?”
The SEO Tools Kilo Code Gets
- Search Console performance and insights: clicks, impressions, CTR and position, striking-distance queries, 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.
Every tool, with its parameters and cost, is in the SEO MCP server reference.
How It Works, Step by Step
- You ask Kilo Code a question about your site, with any of its agents.
- Kilo calls the SEOmatic tools it needs, such as striking-distance insights or a page score.
- SEOmatic returns your real data and its own analysis, with exact date ranges.
- Kilo reads the matching files, writes a plan or edits the code. You review the diff.
- For CMS sites on a paid plan, Kilo stages the fix in SEOmatic instead. You approve it, and SEOmatic applies it with a rollback point.
How to Connect SEOmatic to Kilo Code
About a minute, with Kilo Code installed and a model set up.
- Open Kilo's MCP config. Open ~/.config/kilo/kilo.jsonc (or .kilo/kilo.jsonc in one repo). In the terminal you can run kilo mcp add instead. In VS Code, Kilo's docs also list Settings, Agent Behaviour, MCP Servers, Add Server, Remote (HTTP).
- Add the seomatic server. Name it seomatic with the URL https://app.seomatic.ai/api/mcp. In kilo.jsonc, that is an entry under mcp with "type": "remote". Keep any servers already there.
- Sign in to SEOmatic. Kilo opens the SEOmatic sign-in in your browser when it connects; in VS Code, click the sign-in notification if seomatic shows needs_auth. If nothing opens, run kilo mcp auth seomatic. Sign in or create a free account, approve access and pick your site.
- Allow the tools. Kilo asks before each SEOmatic tool the first time. Click Approve Always in VS Code to save an allow rule, add "seomatic_*": "allow" under permission in kilo.jsonc, or in JetBrains use Settings, Tools, Kilo Code, Auto-Approve.
- Check the connection. In VS Code, open Settings, Agent Behaviour, MCP Servers and check that seomatic is turned on. In the CLI, run kilo mcp list, or /mcps inside a session, and check that seomatic is on. If seomatic lists only check_site and connect_seomatic, the sign-in has not run yet: run kilo mcp auth seomatic, or use the API key header below.
- 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.
Kilo Code setup
// ~/.config/kilo/kilo.jsonc (or .kilo/kilo.jsonc in one repo)
{
"mcp": {
"seomatic": {
"type": "remote",
"url": "https://app.seomatic.ai/api/mcp"
}
}
}
// or, from a terminal:
kilo mcp add
kilo mcp auth seomatic
kilo mcp list
// skip the per-tool prompts
"permission": {
"seomatic_*": "allow"
}
// CI or no browser: add an API key header instead
"seomatic": {
"type": "remote",
"url": "https://app.seomatic.ai/api/mcp",
"headers": {
"Authorization": "Bearer smk_live_..."
}
}A project file (.kilo/kilo.jsonc) wins over the global one, and the CLI also reads a legacy opencode.jsonc, so check those if Kilo seems to ignore a change. Do not commit an API key to a shared repo: keep keys in the global file. Kilo's MCP tools follow its permission system (allow, ask, deny) under the name seomatic_<tool>; Approve Always in VS Code saves the rule for you. If seomatic shows an error, turn it off and on again, or run kilo mcp auth seomatic, to retry the sign-in; kilo mcp debug seomatic shows what the connection returns. If kilo mcp auth says it succeeded but seomatic still lists only check_site and connect_seomatic, that is a known Kilo bug: add the API key header instead.
kilo.jsonc, kilo mcp add, Settings Screen or Skills?
| Route | Best for | How |
|---|---|---|
| kilo.jsonc | Most people: VS Code, JetBrains, the CLI, or a setup you want in the repo | Add the block above to ~/.config/kilo/kilo.jsonc or .kilo/kilo.jsonc. For CI, add an Authorization: Bearer smk_live_... header. |
| kilo mcp add | Terminal users who prefer a guided prompt | Run kilo mcp add, pick a remote server, name it seomatic and paste https://app.seomatic.ai/api/mcp. kilo mcp auth seomatic starts the sign-in if it did not open; kilo mcp list shows the status. |
| Settings, Agent Behaviour, MCP Servers | VS Code users who prefer a form to a file | Kilo's docs list Add Server, then Remote (HTTP), name it seomatic, paste https://app.seomatic.ai/api/mcp, then finish the sign-in. If your build has no Add Server button, use kilo.jsonc or ask the Kilo agent to add the entry. |
| Skills only | Running SEO checks through the SEOmatic CLI | npx skills add Minh42/seomatic-mcp -a kilo, with SEOMATIC_API_KEY set. |
Pick kilo.jsonc in your home folder. One entry reaches Kilo in VS Code, JetBrains and the CLI, and the sign-in starts by itself. Use kilo mcp add if you live in the terminal, or the Settings form if you only use VS Code and want to skip the file.
Kilo Code, Roo Code or Cline: Which One Is This?
Kilo Code is an open-source coding agent for VS Code, JetBrains IDEs and the terminal, now part of Anaconda (acquired in July 2026). SEOmatic connects to it as a remote MCP server.
- Roo Code shut down on May 15, 2026, and many of its users moved to Kilo Code. If you used SEOmatic in Roo Code, add it to Kilo with the block on this page.
- Cline is a separate coding agent with its own MCP setup and its own page.
This page covers Kilo Code in VS Code, JetBrains and the CLI. All three read the same kilo.jsonc files, so one seomatic entry reaches each of them.
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.
Your model provider bills Kilo's own work, like planning and writing code, separately. SEOmatic questions count only the SEOmatic tool calls.
Nothing Changes on Your Site Without Your Approval
Kilo Code works in two places, and both keep you in charge. In your repo, it edits files and you review the diff before anything ships. 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 editor agent? See Cline, GitHub Copilot and Cursor. Prefer the terminal? See OpenCode. 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 Cline, OpenCode, GitHub Copilot, or every AI agent.
Frequently Asked Questions
How do I connect SEOmatic to Kilo Code?
Add an entry named seomatic with "type": "remote" and the URL https://app.seomatic.ai/api/mcp under mcp in ~/.config/kilo/kilo.jsonc, or run kilo mcp add in the terminal. In VS Code, Kilo's docs also list Settings, Agent Behaviour, MCP Servers, Add Server, Remote (HTTP). Kilo opens the SEOmatic sign-in in your browser; kilo mcp auth seomatic starts it by hand.
Does it work in JetBrains and the Kilo CLI?
Yes. The CLI, the VS Code extension and the JetBrains plugin all read the same ~/.config/kilo/kilo.jsonc (and the project's kilo.jsonc), so one seomatic entry covers all three. In JetBrains, tool approvals live in Settings, Tools, Kilo Code, Auto-Approve.
Do I need an API key?
Not on your own machine. Kilo starts the OAuth sign-in on its own. For CI or a server with no browser, create an API key in SEOmatic and add an Authorization header with Bearer and your key to the seomatic entry.
I used SEOmatic in Roo Code. What do I do now?
Roo Code shut down on May 15, 2026. Install Kilo Code and add SEOmatic with the steps on this page. Your SEOmatic account, workspace and data stay the same; only the agent changes.
Can Kilo Code fix SEO problems in my code?
Yes. It 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 13 to Oct 10, 28 days. SEOmatic tells the agent to state only numbers that came from a tool result.
Is SEOmatic for Kilo Code 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.
Kilo does not show the SEOmatic tools. What now?
Check that seomatic is turned on: Settings, Agent Behaviour, MCP Servers in VS Code, or kilo mcp list and /mcps in the CLI. If it shows an error, toggle it off and on, or run kilo mcp auth seomatic, to retry the sign-in. If only check_site and connect_seomatic show up, you are not signed in: run kilo mcp auth seomatic, and if it reports success without opening a browser (a known Kilo bug), add the API key header to the seomatic entry instead. If you edited kilo.jsonc, check that a project file or a legacy opencode.jsonc is not overriding your global one. If the tools are there but Kilo asks every time, click Approve Always or add a seomatic_* allow rule under permission.
Do I need a Google Cloud project?
No. You connect Search Console to SEOmatic once with a normal Google sign-in, and Kilo 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.