What is the SEO Skill for Cursor?
The SEOAgent Skill turns Cursor's Agent into an SEO engine for your codebase. Once installed, you can ask Cursor to audit your site, fix technical issues, research keywords, and write landing pages and articles — and it does the work as real files in your repo. Nothing publishes on its own: every change comes back as a normal diff in Cursor's review pane to approve. It is the opposite of an auto-blogging tool — it is SEO that lives where you already ship.
Three steps, about three minutes
- Choose how you work. The card above asks once; pick Coding agent, then Cursor and type your site.
- Paste the prompt. One paste into Cursor installs the Skill, binds the site to your account and runs the first audit.
- Watch it bind. The card turns green the moment the code is redeemed; if nothing happens in three minutes it asks what you saw and routes you.
seoagent init --code, then “Logged in as” — the site is bound.How to use SEOAgent in Cursor
Install the Skill globally
Run `npm install -g @seoagent-official/seoagent` once, then `seoagent init` in your project. It installs the Skill bundle (`.agents/skills/seoagent/` when your repo already uses `.agents/`, otherwise `.claude/skills/seoagent/`), adds a SEOAgent section to `AGENTS.md`, and — when the repo has a `.cursor/` directory — writes `.cursor/rules/seoagent.mdc` so Cursor’s Agent picks the Skill up on its own. `init` prints the exact path it used.
Ask Cursor’s Agent to audit your site
Open the Agent panel and say "audit my site." The Skill fetches your homepage, sitemap, and robots.txt, runs a full technical-SEO check, and reports the biggest issues with the exact fix for each — not a vague to-do list.
Approve the fixes
Cursor proposes changes — metadata, schema, canonicals, internal links — as edits you review in the diff pane. Accept what makes sense and reject the rest. Safe, reversible, shipped through your normal pipeline.
Write content in your repo
Ask it to research keywords and write articles or landing pages. It builds a topic cluster with internal linking and writes the files straight into your repo (or your CMS), so a reviewed commit puts them live.
Connect Search Console (optional)
Run `seoagent login` in Cursor’s integrated terminal to connect Google Search Console. Now the Skill grounds its suggestions in your real traffic data — which queries sit on page two, which pages are slipping — instead of guessing.
Give it a cadence
SEO compounds on a schedule, not on one good afternoon. A weekday cron line — `0 9 * * 1-5 cd /path/to/repo && seoagent sync --silent` — keeps the queue of detected work fresh; then open Cursor’s Agent in the repo and say "process the inbox" to do the work. Everything it learns is written to `.seoagent/`, so the next session starts where the last one stopped instead of re-auditing from zero.
What SEOAgent does in Cursor
Technical SEO audits
Crawls your pages and flags indexing, canonical, metadata, render, and internal-link issues — with the fix attached to each finding.
In-repo fixes
Applies safe, mechanical fixes (titles, meta descriptions, schema, alt text) directly in your source, and proposes the rest for review.
Keyword & competitor research
Pulls real volume and difficulty and finds the queries you can realistically win, so content targets terms that matter.
Content that ranks and gets cited
Writes landing pages and articles structured for both readers and AI answer engines, with automatic internal linking into a topic cluster.
Search Console grounding
Reads your real GSC performance and suggests evidence-backed updates, so the work compounds instead of going stale.
Human-in-the-loop, always
Every change lands in Cursor’s diff pane for you to accept. No autopilot, no AI slop published behind your back.
Orphan and internal-link analysis
`seoagent internal-links` reads the repo, not a crawl, and reports which pages have no inbound internal links and which have exactly one — the pages Google discovers and then declines to index.
AI search readiness
Generates the machine-readable layer answer engines actually read: an `llms.txt` built from your real page inventory (`seoagent llms`) and an Open Knowledge Format bundle served at `/.well-known/okf/` (`seoagent okf`).
Frequently asked questions
How do I add SEO to Cursor?
Install the SEOAgent Skill: run `npm install -g @seoagent-official/seoagent`, then `seoagent init` in your project. Cursor’s Agent detects the Skill automatically — then just ask it to "audit my site" to start.
Is the SEOAgent Skill for Cursor free?
Yes. The Skill is free forever and runs locally. An optional cloud tier ($49 per site per month) adds Google Search Console analysis, competitor research, and cloud review of suggested updates.
Does it publish content automatically?
No. SEOAgent proposes every change as a diff you review in Cursor and approve. It writes files into your repo or CMS, but you decide what ships — it is intentionally not an auto-publishing blog spammer.
What can Cursor actually do with the Skill?
Run technical SEO audits, fix metadata/schema/canonicals/internal links in your source, research keywords and competitors, and write optimized landing pages and articles into your codebase — grounded in your Search Console data once connected.
What is the best SEO skill for Cursor?
SEOAgent is the highest-scoring SEO skill on the public SEO Skill Benchmark, and the only one built as a full harness: audits, fixes, keyword research, content, and Search Console grounding in one install. It is free, runs locally, and never publishes without your approval.
Can Cursor do SEO on its own?
Cursor can edit any file, but out of the box it has no SEO playbook: no audit checklist, no keyword data, no Search Console access. The Skill supplies that missing harness, so "audit my site" produces a real technical-SEO report instead of generic advice.
Where does the SEO skill install in Cursor?
`seoagent init` writes the Skill bundle to `.agents/skills/seoagent/` if your repo already uses `.agents/`, and to `.claude/skills/seoagent/` otherwise; it also adds a SEOAgent section to `AGENTS.md` and, when the repo has a `.cursor/` directory, a `.cursor/rules/seoagent.mdc` rule that points Cursor at the bundle. The files are tracked in git, so a teammate who clones the repo gets the same Skill without installing anything.
Is the SEO skill for Cursor different from a Cursor rule?
Yes, and they do different jobs. A rule is context — it nudges how the Agent writes. The Skill is a procedure plus a CLI: an audit protocol with per-check instructions, reference files for each page type, and commands that fetch real data (`seoagent crawl` for live evidence, `seoagent keywords` for volume and difficulty, `seoagent indexing` for Search Console verdicts). SEOAgent installs a small `.cursor/rules/seoagent.mdc` whose only job is to route Cursor to that bundle.
How do I update the Cursor SEO skill?
Run `npm install -g @seoagent-official/seoagent@latest`, then `seoagent init` again in the project. Re-running `init` refreshes the Skill bundle and the sync hook in place and leaves everything under `.seoagent/` — your audits, keywords, briefs and roadmap — untouched.
Does it work with Claude Code and Codex too?
Yes. The same Skill works in Claude Code and Codex, plus a standalone CLI. See the SEO Skill for Claude Code and for Codex.
See also
Give Cursor the SEO tools
Enter your site, create your prompt, and paste it into Cursor — it installs the Skill, binds your account, and runs your first audit in minutes.
Want measurement on top? See Autopilot pricing.
What do you use to work on your site?
Claude Code, Cursor, Codex or another terminal agent, in the repo that builds your site.
Cursor: paste into the Agent chat (not Ask), in the repo, and approve the terminal command when it asks.
You get a prompt with a one-time code. Paste it into Cursor; it installs the Skill, binds the site, and runs the first audit.
Free for your own agent. Autopilot is the paid part.
Start your 14-day free trial, no card · $49/site/month after · we stop if nothing improves