Kiro SEO: Turn Search Console Data Into a Spec

Kiro is built to plan before it codes. Give it your search data, and its plans start from the pages that actually lose traffic.

An example on the Acme Plumbing demo site. You ask Kiro:

“Write a spec to fix the SEO on our three service pages, based on our Search Console data.”

Kiro calls SEOmatic:

• seomatic gsc_performance: Jul 14 to Oct 11 (90 days), by page
• seomatic gsc_indexing: /emergency-plumber
• write .kiro/specs/service-page-seo/requirements.md

Kiro answers:

I wrote the spec in .kiro/specs/service-page-seo/, from Jul 14 to Oct 11 (90 days):

1. /emergency-plumber is “Crawled, currently not indexed”. Requirement: fix the canonical, which points to the home page.
2. /water-heater-repair has 9,860 impressions and a 1.4% CTR at position 7.6. Requirement: a title that matches “water heater repair” and “same day”.
3. /drain-cleaning-cost ranks 10.9 and never states a price. Requirement: a price range section and an FAQ.

Review the requirements and I will write the design and tasks. 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 a hook that checks titles when I save a page”
• “Do AI answers cite our pages?”

Kiro's specs break work into requirements, a design and tasks before any code changes. With SEOmatic connected, the requirements come from your data instead of a hunch:

1. Requirements: Kiro asks SEOmatic which pages lose clicks, rank on page two or are not indexed, and writes one requirement per page, with the numbers and date range.
2. Design: Kiro reads your templates and decides where each fix belongs, such as a title template, a canonical helper or a schema component.
3. Tasks: Kiro works through the fixes one by one, and you review each change.

A few days after you deploy, ask Kiro to check the same pages again in Search Console.

Kiro supports OAuth sign-in for MCP servers, and in many setups it works. The Kiro CLI has an open issue (issue 11084) where it rejects the sign-in with an “issuer mismatch” when a server's MCP address and its sign-in address differ. SEOmatic is set up that way, as the MCP standard allows.

An API key avoids the sign-in step, so the same block works in the IDE and the CLI. The key belongs to one SEOmatic workspace, and you can delete it in SEOmatic at any time.

Ask these in Kiro's chat, with your site's repo open:

• “Write a spec to fix the SEO on our three service pages, based on our Search Console data.”
• “List the pages Google has not indexed and find the cause in this repo.”
• “Which pages get impressions on Google but few clicks? Rewrite their titles.”
• “Audit the site before I deploy and fix anything that would hurt rankings.”
• “My organic clicks fell this month. Which pages lost them, and why?”
• “Which questions do AI assistants answer without citing us?”

• 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 on paid plans, with one free keyword preview.
• 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.

1. You ask Kiro a question about your site, or ask it for a spec.
2. Kiro calls the SEOmatic tools it needs, sending your API key with each call.
3. SEOmatic returns your real data and its own analysis, with exact date ranges.
4. Kiro writes the plan, reads the matching files and edits the code. You review each change.
5. For CMS sites on a paid plan, Kiro stages the fix in SEOmatic instead. You approve it, and SEOmatic applies it with a rollback point.

About two minutes, with Kiro installed and signed in.

1. Create an API key. In SEOmatic, open Settings, AI Agents and create an API key. Copy it; it starts with smk_live_.
2. Open Kiro's MCP config. In the Kiro IDE, open the Command Palette and run Kiro: Open user MCP config (JSON). For the CLI, open ~/.kiro/settings/mcp.json in any editor.
3. Paste the SEOmatic block. Add the seomatic entry under mcpServers with the URL https://app.seomatic.ai/api/mcp and your key in the Authorization header. Keep any servers already there, and save.
4. Check the connection. In the Kiro panel, check that seomatic shows as connected and lists its tools.
5. 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.

A workspace file (.kiro/settings/mcp.json) wins over the user file when both exist, so check both if Kiro seems to ignore a change. Keep API keys in the user file, not in a shared repo. If the Kiro CLI shows an issuer mismatch error, you are on the OAuth route: add the API key header instead.

Pick mcp.json with an API key. It works the same in the IDE and the CLI, and it avoids a known Kiro CLI sign-in issue. You can switch to OAuth later by removing the headers.

Kiro is AWS's agentic coding tool: an IDE that plans work as specs, plus the Kiro CLI. SEOmatic connects to both through the same mcp.json file.

• Amazon Q Developer stopped taking new signups on May 15, 2026, and Kiro is its successor. If you set up MCP servers in Q, add SEOmatic to Kiro with the block on this page.
• Other agentic IDEs, like Cursor or Google Antigravity, have their own setup on their own pages.

This page covers Kiro, in the IDE and the CLI.

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.

Kiro's own usage is billed by Kiro. SEOmatic questions count only the SEOmatic tool calls, not the specs or code Kiro writes.

Kiro works in your repo and in SEOmatic, and both keep you in charge. In your repo, Kiro writes specs and code that you review before anything ships. In your CMS, it can only stage a fix in SEOmatic. The API key you give Kiro can be deleted in SEOmatic at any time. 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.

Using another agentic IDE? See Google Antigravity, Cursor and Kilo Code. Prefer the terminal? See Claude Code SEO. 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 Google Antigravity, Cursor, Claude Code, or every AI agent.