Check my websiteGuidesAbout
Fecto / Guides / Claude Code SEO

Claude Code SEO

Claude Code is good at editing your repo, but on its own it can’t see what search engines and AI assistants get from your live site, so most SEO prompts end in guesses about tags. Give it the Fecto plugin: a skill that says what to do and an MCP server that scans the live site, so every fix is tied to a check that passes or fails.

Free, about ten seconds, no account.

What the Fecto plugin adds to Claude Code

Claude Code loads skills from three places: ~/.claude/skills for you, .claude/skills in a repo for the team, and the skills/ folder of an installed plugin. Only a skill’s description sits in context until the task calls for it, which is why a good SEO skill says plainly when to use it. Fecto ships as a plugin from the makloai/plugins marketplace, carrying the remote MCP server plus the fix-site, ai-search and move-to-code skills, invoked as /fecto:fix-site or picked up when you ask Claude Code to fix or audit your site.

The skill is a short fallback. At the start of every session it calls get_skill("fix-site") and follows what the server returns, so the instructions stay current without you updating anything. The MCP server is where the checks live: scan_site reads your pages the way a crawler does, next_step hands over one change at a time, and run_checks grades the change against the same rules the final verifier uses.

That split matters for SEO in particular. A prompt such as “improve my SEO” gives Claude Code nothing to test against, so it adds meta tags and calls it done. With a check id attached, it can run the check on your local dev server, see it fail, change the code and see it pass before opening the pull request.

Common causes, and the fix for each

Main text that only appears after JavaScript runs

Fecto check read.main-text-needs-js · Main text is in the HTML

Projects Claude Code scaffolds quickly are often client-rendered: a Vite app whose HTML is an empty div#root. Googlebot renders JavaScript, so Fecto doesn’t apply this rule to it, but the AI search bots and user-fetch bots read the HTML as served. The fix step names the pages that fail and asks Claude Code to prerender or server-render them, then re-runs the check against the built HTML.

One title for every page, no description, no canonical

Fecto check index.meta-tags · Title and description

The check wants a title, a meta description and a canonical link on each page. Claude Code tends to set them once in a layout and stop. The step asks for a title and description written from each page’s own content, and a canonical that points at the page itself rather than the home page.

Pages that exist but aren’t in the sitemap

Fecto check index.not-in-sitemap · Page is in the sitemap

A hand-written sitemap.xml falls behind the routes within a few commits. Fecto checks each page you care about against the sitemap the site actually serves, so Claude Code generates the file from the route list instead of maintaining it by hand.

robots.txt that turns AI search bots away

Fecto check access.robots-blocks-bot · robots.txt lets AI search bots in

Copied robots.txt templates often disallow everything except Googlebot. Fecto’s rule only looks at search and user-fetch bots (OAI-SearchBot, Claude-SearchBot, PerplexityBot, ChatGPT-User, Claude-User and the like). Whether to block training bots such as GPTBot stays your call, and the scan never counts it against you.

No structured description of the business

Fecto check record.no-business-schema · Business described in structured data

Claude Code will happily write JSON-LD, but without facts it invents them. The Fecto step only uses what the site already states (name, URL, contact details) and asks you for anything missing, so the Organization block never carries a made-up address or rating.

Let your agent do it

The Claude Code button opens a new session with the instructions typed in. If the plugin isn’t installed yet, Claude Code installs it, asks you to start a new session and sign in with /mcp, then picks up where it left off: your score, what you want more of, and the price. Every change after that arrives as a pull request on a branch named after the fix.

Claude CodeClaude appCodexCursor

No coding agent yet? Install the Claude app, sign in, then come back and choose Claude app.

Set it up by hand
curl -fsSL https://fecto.ai/install | sh

Then tell it

Use Fecto to check and fix my site.

For reference, the Claude Code install command: claude plugin marketplace add makloai/plugins && claude plugin install fecto@makloai

Not worth your time: a hand-rolled SEO prompt library

Collections of “SEO prompts for Claude Code” are mostly lists of tags to add. They don’t know what your live site serves, and Claude Code has no way to tell whether they worked. Spend the effort on checks that fail before the fix and pass after it.

What it costs

You pay only when the result shows up on your site: +20% more visits or enquiries is $30, +50% is $60, double is $100, and anything below +20% costs $0. Never more than $100 a site a month.

Questions

Is there a Claude Code SEO agent, or do I need a separate tool?

Claude Code is the agent. What it lacks is a view of your live site and a rule to test each change against. The Fecto plugin adds both without a second app: the work happens in the Claude Code session you already have, on your repo, and every change is a pull request you review.

Does it work in the Claude app as well as the terminal?

Yes. The Claude app button opens Claude Code in the desktop app with the same instructions, and the Claude Code button opens the terminal version. Both use the same plugin, the same skill and the same checks.

Related guides

  • SEO with Claude Code
  • Cursor SEO
  • Codex SEO
  • Vibe coded website SEO issues
  • AI SEO audit, free
  • All guides

Checked against Claude Code docs: skills on 18 November 2026.