What is the SEO Skill for Windsurf?
Windsurf's Cascade is an agent with a terminal, a file system and a memory of your codebase — everything an SEO engineer needs except the playbook. The SEOAgent Skill is that playbook plus a CLI: an audit protocol with a fix for every finding, keyword research with real volume and difficulty, briefs and articles written as files in your repo, and a daily loop that keeps the work moving. Cascade reads the Skill the way it reads any rule in your workspace, runs `seoagent` commands in its terminal, and shows you each change before it lands. Nothing is published on its own.
Three steps, about three minutes
- Choose how you work. The card above asks once; pick Coding agent, then Other and type your site.
- Paste the prompt. One paste into your coding agent 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.
How to use SEOAgent in Windsurf
Create the prompt on this page
Type your site in the card above and choose Coding agent → Other. You get a paste block with a one-time setup code. The block installs the CLI, runs `seoagent init --code <code>`, and points the agent at the Skill; the code works once and is bound to your account, so the paste is the whole signup.
Paste it into Cascade, in the repo
Open the repository that builds your site in Windsurf, open Cascade, and paste the block. Cascade runs the two commands in its terminal and asks you to approve them the first time — say yes. `seoagent init` writes the Skill bundle (`.agents/skills/seoagent/` when the repo already uses `.agents/`, otherwise `.claude/skills/seoagent/`), adds a SEOAgent section to `AGENTS.md`, and prints the path it used.
Let Cascade find the Skill on its own
Windsurf reads workspace rules from `.windsurf/rules/`. Add one line there — `Before SEO work, read the SEOAgent SKILL.md that seoagent init installed` — or ask Cascade to add it. From then on every new Cascade session knows where the procedure lives without you repeating it.
Ask for an audit and accept the fixes
Say "audit my site". The Skill fetches the homepage, sitemap and robots.txt, runs the technical checks, and reports findings with the exact fix for each. Cascade proposes the fixes as edits — titles, meta descriptions, schema, canonicals, internal links — and Windsurf shows them in the diff view. Accept what makes sense; reject the rest.
Write content into the repo
Ask Cascade to research keywords and write an article or a landing page. The Skill builds a topic cluster with internal links and writes the files where your site expects them, so a reviewed commit puts them live. `seoagent content track` tells the dashboard what shipped.
Give it a weekday routine
Windsurf has no scheduler, so the block adds a cron line — `0 9 * * 1-5 cd <repo> && seoagent sync --silent` — that keeps `.seoagent/inbox/` fresh with detected work. Open Cascade in the repo each weekday morning and say "process the inbox"; it does the work and runs `seoagent ack` for each item. Everything it learns is written to `.seoagent/`, so the next session starts where the last one stopped.
What SEOAgent does in Windsurf
Technical SEO audits with fixes attached
Indexing, canonicals, metadata, render, internal links — each finding names the file and the change, so Cascade can apply it instead of describing it.
Edits you review in the diff view
Mechanical fixes land as proposed edits in Windsurf. You accept or reject per file, exactly like any other Cascade change.
Keyword research with real numbers
`seoagent keywords` pulls volume and difficulty so content targets queries you can actually win, not guesses.
Articles and landing pages as files
Briefs turn into pages written where your framework expects them, with internal links into the cluster and the metadata already set.
Search Console grounding
Run `seoagent login` once and the Skill reads your real queries and pages, so refreshes go to pages that are slipping and briefs target queries already on page two.
Terminal-first, approval always
Every command runs in Cascade's terminal with your approval; nothing publishes behind your back, and the block tells the agent to stop and report if the bind fails.
AI search readiness
`seoagent llms` builds an `llms.txt` from your real page inventory and `seoagent okf` serves an Open Knowledge Format bundle at `/.well-known/okf/`.
A daily loop that compounds
The inbox, `seoagent sync` and `seoagent ack` turn SEO from one good afternoon into a routine the agent can run every weekday.
Frequently asked questions
How do I add SEO to Windsurf?
Create the prompt on this page (site in, one-time code out) and paste it into Cascade in the repository that builds your site. It installs the SEOAgent CLI and Skill, binds the site to your account and runs the first audit. Then ask Cascade to "audit my site".
Is the SEO Skill for Windsurf free?
Yes. The Skill runs locally inside Windsurf on the model you already pay Windsurf for, and it is free forever. Autopilot ($49 per site per month, 7-day free trial at the first bind) adds Search Console measurement, keyword and competitor research, and briefs and articles written for you.
Does Cascade need a special rule for the Skill?
Not to run it: the paste block tells Cascade to read the SKILL.md that `seoagent init` installed, and `AGENTS.md` carries a pointer. A one-line rule in `.windsurf/rules/` that says the same makes every future Cascade session find it without being told.
Will Windsurf publish content without me?
No. Cascade proposes edits and you accept them in the diff view; articles are files that go live when you commit and deploy. SEOAgent never publishes to a CMS itself.
What if the paste fails?
The block says to stop and report the exact error, never to continue unbound. The card on this page waits for the bind and, if nothing happens in three minutes, asks what you saw — a printed error, nothing ran, or you will do it later — and routes you from there. Codes live 14 days and work once.
Does it work with Windsurf on a site with no repo?
If your site is on WordPress.com, Shopify, Webflow, Wix or another hosted platform, the block says so and Cascade runs the setup in an empty folder: the audit runs against the live site and delivery goes through the platform’s API or the editor. If you have no agent at all, the "Just my website" door is for you.
How is this different from asking Cascade to "do SEO"?
Cascade can edit any file, but it has no audit checklist, no keyword data and no Search Console access. The Skill supplies the procedure and the CLI supplies the data, so "audit my site" produces a real technical report with fixes instead of generic advice.
How do I update the Skill in Windsurf?
Run `npm install -g @seoagent-official/seoagent@latest`, then `seoagent init` again in the project. It refreshes the Skill bundle in place and leaves `.seoagent/` — your audits, keywords, briefs and roadmap — untouched.
See also
Give Cascade the SEO playbook
Enter your site, create the prompt, and paste it into Windsurf — the Skill installs, the site binds, and the first audit runs 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.
You get a prompt with a one-time code. Paste it into your coding agent; it installs the Skill, binds the site, and runs the first audit.
Free for your own agent. Autopilot is the paid part.
Start your 7-day free trial, no card · $49/site/month after · we stop if nothing improves