Check my websiteGuidesAbout
Fecto / Guides / SEO with Claude Code

SEO with Claude Code

Doing SEO with Claude Code works best as a loop rather than a prompt: read what the live site serves, pick one failing check, fix it in the repo, prove it on the dev server, open a pull request. The quickest way to see what fails first is a free scan of your address, which gives Claude Code the check ids to work from.

Free, about ten seconds, no account.

What one session looks like

Here is the order a Fecto session runs in, so you know what Claude Code will ask and when. Nothing in it needs you to copy commands around: the button below opens Claude Code with the first instruction already typed.

First it shows your score. Claude Code calls get_onboarding with your domain and reads back the scan you already ran, or runs scan_site if there isn’t one. It names the three findings that matter most, each in a sentence about what it costs the business, not in crawler jargon.

Then it asks what you want more of: visits from search, visits from AI assistants, or enquiries and bookings. If you have Search Console or analytics open on this computer, it reads the numbers first and tells you which result they favour. You agree a price (you pay only if the result is reached) and save a card with $0 due. Only then does anything touch your site: one line, the Fecto tag, in its own pull request.

The work comes as steps. next_step hands Claude Code a single change with the check ids it touches. Claude Code makes it on a branch named fecto/<playbook-id>, runs run_checks against your local dev server (HTML per path, robots.txt, the sitemap) and opens the pull request only when the checks pass. You review and merge; it never merges for you.

Common causes, and the fix for each

Step: missing pages answer 404

Fecto check index.soft-404 · Missing pages return 404

A typical early step. Claude Code requests a path that doesn’t exist on your dev server. If the answer is your home page with status 200, it adds a real not-found route and re-runs the check until the status is 404 or 410. The pull request says which route it added and why.

Step: a sitemap the site actually serves

Fecto check index.sitemap · A sitemap exists

The check passes when /sitemap.xml, or the sitemap robots.txt declares, is valid. Claude Code generates it from your routes, starts the dev server, fetches the file and validates it before reporting the step done.

Step: landmarks and one h1

Fecto check read.semantic-html · Semantic structure

Generated layouts are often nested divs. The check wants header, nav, main and footer landmarks and a single h1. It is hygiene and never priced, so it is a good one to fold into a pull request that touches the layout anyway rather than one of its own.

Step: share tags that match the page

Fecto check index.open-graph · Sharing tags

og:title, og:description and og:image decide how a link looks when someone pastes it into a chat. Claude Code fills them from the same title and description the page already uses, so the two never disagree.

Let your agent do it

If Claude Code stops halfway, ask it to continue: next_step with your plan id picks up the step that’s open. If a step needs something only you can change, such as a DNS record or a setting in your host’s dashboard, Claude Code reports it as blocked with the exact setting and tells you rather than guessing.

At the deadline Fecto counts the result with its own tag. Claude Code, which did the work, never decides whether it succeeded.

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

Don’t ask for a whole-site SEO rewrite in one go

A single prompt that touches every page produces a diff nobody reviews and no way to tell which change helped. One check per pull request is slower to read about and faster to merge.

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

Can I do SEO with Claude Code without paying for anything?

Yes. The scan is free and needs no account, and each finding names the check behind it and what passes it, which is enough for Claude Code to fix it with no plan at all. A plan is for when you want Fecto to set a target, hand over the steps in order and count the result. You pay only if that result is reached.

What about GEO, getting into AI answers?

The same session covers it. Choose more visits from AI assistants as your result and the steps lean on access for AI search bots, text in the HTML, and pages that answer what your buyers ask. Fecto never sells a single AI answer as the result: mentions vary from one run to the next, so they are reported with ranges.

Related guides

  • Claude Code SEO
  • Next.js SEO
  • Single page app SEO
  • Cursor SEO
  • Codex SEO
  • All guides

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