If you ship the marketing site, SEO is your problem whether or not it is your job. And every tool for it is built for somebody who does not use an editor.
The usual loop is: a marketer runs an audit in a dashboard, exports a PDF, pastes three screenshots into a ticket, and two sprints later you are guessing which of the forty items still apply.
The tool goes where the code is
ContextBolt SEO is an MCP server. It is one URL in your client’s config and then the tools are in the agent, next to the file you have open.
That changes the loop rather than the data. The audit runs against the page you just edited, the agent already has the file, and the fix lands in the same session. Nothing gets transcribed into a ticket and nothing goes stale on the way.
Decisions that are cheap now and expensive later
Slugs, H1s and route names are almost free to choose well at the moment you are writing them, and painful to change once Google has indexed them.
Asking “what do people actually search for this” before you name /features/team-inbox takes one lookup. It is the highest-leverage SEO work a developer does, and it happens entirely inside the editor.
Findings that behave like code
Every lookup mirrors to a ./seo-findings/ folder as markdown. That is the part that fits how you already work: the research diffs, it reviews, it goes in the PR, and it has history. The same lookups fill your SEO Board, a private page at a URL, which is what you send to the person who asked for the numbers but does not want a repo.
Six months later, “why is this H1 phrased like that” has an answer in the repo rather than in somebody’s memory.
The honest edges
The page audit is the on-page layer. It is not Lighthouse and it is not a rendering crawl, so Core Web Vitals and render-blocking work still belong to the tools built for them. There is no CI mode, so it will not fail a build.
And there is no scheduled crawler or rank tracker. Everything happens because you asked for it in a session. The Ahrefs comparison sets out where a suite is genuinely the right answer instead.
For everything else, it is $35 a month and it lives where you already are. Setup for Cursor, VS Code, Claude Code, Codex, Windsurf and JetBrains is a couple of minutes each.
How ContextBolt SEO works for Developers
-
Audit the page in the diff you are about to open
Point page_audit at the URL you just changed and it checks the mechanical things: H1 present, title length, meta description, thin content, broken links, heading order. The agent has the fix list and your file open at the same time, so the fix happens in the same session rather than in a ticket next sprint.
-
Check a term before you name the route
You are adding /features/team-inbox. Ask what people actually search for it first. A slug and an H1 chosen against real volume cost nothing extra at the point you are writing them, and are expensive to change once they are indexed.
-
Run a site audit on a branch preview
site_audit takes a domain and reports the on-page problems across it. Run it against production before a release to see what you are shipping into, rather than finding out from a Search Console email three weeks later.
-
Commit the findings with the change
Every lookup writes markdown into a ./seo-findings/ folder in the repo. It diffs, it reviews, and it goes into the PR next to the code that caused it. SEO stops being a screenshot in Slack and becomes a file with history.
What that gets you
Stays in Cursor, VS Code, Claude Code, Codex, Windsurf or JetBrains
Audit a page and fix it in the same session
Findings are markdown in the repo, so they diff and review like anything else
Free Google Search Console connection, real numbers not estimates
One URL to set up, no SDK, no crawler to run, nothing to self-host
$35/mo flat, no seat that has to be justified to anyone