AI SEO Agents for Claude Code

Most SEO problems on a code-built site live in a template, a layout or a routing rule, not in one page. Claude Code with SEOmatic is best for developers who want to find those problems from real data and fix them at the source in the same session.

Run these inside a Claude Code session in your site's repo. SEOmatic's starter prompts (SEO audit, striking-distance keywords, traffic drop) also show up as slash commands.

• “Audit https://example.com with SEOmatic, then find the code responsible for each issue.”
• “Which pages have high impressions and low CTR? Open their title logic and suggest better titles.”
• “Check whether any page ships a noindex or a canonical pointing elsewhere, and fix it in the code.”
• “Inspect these URLs in Google's index and tell me why the excluded ones are excluded.”
• “Analyze the preview deploy at https://preview.example.com and compare it with production.”

1. You add SEOmatic with one command and sign in once in the browser.
2. You ask Claude Code an SEO question from your repo.
3. Claude Code calls SEOmatic to audit the live site, read Search Console or inspect indexing, and gets real results back as text.
4. It maps each finding to the file that produces it and proposes the code change, which you review like any other diff.
5. After you ship, it re-runs the check on the live URL to confirm the fix.

Claude Code follows SEOmatic's server instructions closely, which makes it the most reliable place to run multi-step SEO work over MCP.

One command, then a one-time sign-in from inside a session.

1. Add the server. In your terminal, run: claude mcp add --transport http seomatic https://app.seomatic.ai/api/mcp
2. Authenticate. Inside a Claude Code session, type /mcp, select seomatic and choose Authenticate. Sign in or create a free SEOmatic account in the browser and pick your site.
3. Run your first check. Ask “Audit my site with SEOmatic and rank the fixes by impact.”

Running headless, in CI or in a container? The server also accepts a workspace API key as a Bearer token; create one in Settings, AI Agents, API Keys.

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.

For code changes you make yourself, the free lane is often enough: diagnosis is free, and the fix happens in your repo. Paid plans matter when you want SEOmatic's agents to write changes into a CMS for you.

Claude Code edits your code the way it always does, with your review. On the SEOmatic side, anything that would change your live site through a connected CMS is staged, never pushed. 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.

Chatting instead of coding? See Claude. Other coding agents: Cursor and GitHub Copilot. Explore the site audit, technical SEO fixes and the MCP server. All assistants: AI assistants. Full reference: MCP docs.