Use SEOmatic in Kimi K3

Connect Kimi K3#

1. 1Start 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.
2. 2Paste the setup prompt. Copy the setup prompt from this page into Kimi Code. Kimi adds the seomatic server to ~/.kimi-code/mcp.json.
3. 3Sign in to SEOmatic. Run /mcp-config login seomatic, sign in or create a free SEOmatic account in the browser, approve access and pick your site.
4. 4Check the connection. Start a new session, then run /mcp and check that seomatic shows as connected. Kimi asks before each SEOmatic call unless you add an allow rule for mcp__seomatic__* in ~/.kimi-code/config.toml.
5. 5Ask 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-code/mcp.json (what the setup prompt writes)
{
  "mcpServers": {
    "seomatic": {
      "url": "https://app.seomatic.ai/api/mcp"
    }
  }
}

// then, in Kimi Code:
/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"
    }
  }
}

Setup Prompt, Plugin, mcp.json or Skill?

Pick the setup prompt. Kimi edits its own config correctly, keeps your other servers, and walks you to the sign-in. Use the plugin if you also want SEOmatic's ready-made SEO workflows.

Try Asking#

• “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?”

What It Costs#

Connecting is free. Reading your own data never uses credits: Search Console performance and insights, index status, rankings, site audits, AI citations, traffic and your tasks. Only live market lookups (keyword metrics, search results, backlinks), AI visibility scans and the fixes you approve use AI credits; every tool is labelled free or billed. On the Free plan, market lookups count against 5 free questions a month. The workspace Owner sees every credit spent, by feature, in Settings > Usage. Kimi K3 itself is billed by its maker, not by SEOmatic: nothing on our side counts tokens.

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 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.

Kimi K3 says SEOmatic is connected but answers without my data.

Start a new chat and check that SEOmatic is enabled for that conversation in the tools menu. This is the step most people miss.

The SEOmatic page says "This connection request expired".

Start the connection again from Kimi K3, or paste the setup prompt again.

The Authorize page shows the wrong email or no workspace.

Click Switch account on that page and sign in with the SEOmatic account that owns the site.

Why does Kimi K3 say it cannot change my site?

Fixes need a live paid plan or trial. On the Free plan, or when billing is paused or failed, your assistant can read and answer only.

How do I disconnect?

Open Settings > AI Agents, scroll to API Keys and delete the row named OAuth: Kimi K3. See disconnect an assistant.