Closed beta · waitlist open

An SEO agent
that opens pull requests.

Connect your repo. The agent scans your site on a schedule, detects SEO issues, and opens a pull request with the exact code fix — already in the right file, in the right framework, ready to review and merge.

Powered by SEOLint scan memory and framework-aware fix instructions.

How it works

Three steps. No prompt required.

1

Scan on a schedule

Daily, weekly, or on every deploy. Same scanner as the MCP server, same memory.
2

Detect what changed

Issues labelled NEW, PERSISTING, REGRESSED. Acts only on mechanical fixes the agent is allowed to ship.
3

Open the pull request

Branch, edit, commit, PR. You review and merge like any other change. CI runs against the branch.

Sample pull request

What lands in your inbox.

Open

SEO: add <title> to /pricing #42

seolint-bot wants to merge 1 commit into main from seolint-bot/fix-missing-title-pricing

SL
seolint-bot commented just now

Detected by SEOLint scan. The /pricing page has no <title>, so Google's SERP shows the URL slug instead of a headline.

app/(marketing)/pricing/page.tsx+4 −3
8- export const metadata: Metadata = {9-   description: "Pricing"10- }8+ export const metadata: Metadata = {9+   title: "Pricing | SEOLint",10+   description: "From $19/mo. AI-powered SEO audits inside Claude."11+ }
All checks passed· build · lint · typecheck
1 commit·1 file changed

Why this works

No other SEO tool can do this.

It knows your stack

Detects 14 frameworks from your rendered HTML to find the right file path.

It has memory

Only fixes issues broken across multiple scans. Flaky one-shots get ignored.

It only ships mechanical fixes

Hard-coded allowlist of safe fixes. Won't touch UX copy or design choices.

It runs on your schedule

Nightly, weekly, or every deploy. Set scope per repo. Pause anytime.

Approved by Anthropic

This uses the official Anthropic API the same way Cursor background agents, Devin and Replit Agent do. Different from the OpenClaw situation, which reverse-engineered the consumer web app. Building on the API isn't a TOS violation.

Closed beta

Join the waitlist

Tell us where to send the invite. Drop your repo URL and you'll jump the queue when the closed beta opens.

No spam. We'll only email you when the agent ships.

Common questions

How is this different from the regular MCP server?
The MCP server runs when you ask Claude to scan something. The autonomous agent runs on a schedule (daily, weekly, on every push) without any prompt. When it finds something fixable, it opens a pull request with the code change ready to review and merge — no copy-pasting, no agent in the loop.
What does a pull request actually look like?
A real diff. The agent uses the same framework-aware fix instructions the MCP tool generates today, but instead of giving you the steps to apply manually, it applies them itself in a branch and opens a PR. Title, description, file paths, and the actual code change. You review it like any other PR.
What kinds of fixes can it ship?
Anything the scanner currently finds where the fix is mechanical: missing title tags, meta descriptions, alt text, canonical URLs, structured data, hreflang, robots.txt rules, Open Graph tags. It will NOT touch anything ambiguous — content rewrites, design changes, anything requiring product decisions. Those still come back as a regular issue you handle yourself.
Is this safe? Will it break my site?
Every change goes through your existing PR review. Nothing merges automatically. CI runs against the branch. You can configure scope (only certain paths, only certain issue types) and the agent respects every guardrail.
Is using a Claude agent for this against Anthropic's terms of service?
No. This uses the official Anthropic API the way it's designed to be used — paid API access, agentic workflow, transparent service. Cursor's background agents, Devin, Replit Agent, and many other tools work the same way with Anthropic's full blessing. The OpenClaw situation was different: that was reverse-engineering claude.ai's consumer web app, which violated terms. Building on the API isn't.
How does it know what files to edit?
SEOLint already detects your framework from the rendered HTML — Next.js App Router, Pages Router, Nuxt, Astro, SvelteKit, Vue, React, WordPress, Shopify, Webflow, and more. The agent uses that detection to find the right file (e.g. app/layout.tsx for a Next.js site, header.php for WordPress) and apply the change in the right place.
When will it ship?
Closed beta opens Q2. Waitlist users with a GitHub repo on file go first. Pricing TBD — likely a separate add-on tier on top of Pro/Team.

While you wait, the manual workflow is already live — connect SEOLint to Claude Code and ask the agent what to fix next.