Home/SEOAgent for GitHub Copilot

The SEO Skill for GitHub Copilot

Copilot agent mode can run commands and edit files in your repo. One paste gives it the SEO procedure and the data: audits, fixes, keyword research, articles — reviewed as diffs in VS Code before anything ships.

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

Free forever · runs locallyWorks in your repo — no dashboardYou approve every diff
01 — What it is

What is the SEO Skill for GitHub Copilot?

Copilot in VS Code has an agent mode that plans multi-step work, runs terminal commands with your approval, and edits files across the workspace. What it lacks is an SEO playbook. The SEOAgent Skill is that playbook plus a CLI: a technical audit with a fix per finding, keyword research with real volume, briefs and articles written as files in your repository, and a sync loop that keeps a queue of detected work. Copilot reads the Skill through your repository's custom instructions, runs the `seoagent` commands in the integrated terminal, and shows every change in the editor's diff review. Nothing is published on its own.

Three steps, about three minutes

  1. Choose how you work. The card above asks once; pick Coding agent, then Other and type your site.
  2. Paste the prompt. One paste into your coding agent installs the Skill, binds the site to your account and runs the first audit.
  3. 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.
02 — How it works

How to use SEOAgent with GitHub Copilot

1/ 6

Create the prompt on this page

Type your site in the card above and choose Coding agent → Other. The paste block carries a one-time setup code: it installs the CLI, runs `seoagent init --code <code>`, and tells the agent where the Skill lives. The code is bound to your account and works once, so the paste is the whole signup.

2/ 6

Paste it into Copilot agent mode, in the repo

Open the repository that builds your site in VS Code, switch Copilot Chat to Agent mode, and paste the block. Copilot asks to run the terminal commands — approve them. `seoagent init` writes the Skill bundle (`.agents/skills/seoagent/` when the repo uses `.agents/`, otherwise `.claude/skills/seoagent/`), adds a SEOAgent section to `AGENTS.md`, and prints the path.

3/ 6

Point custom instructions at the Skill

Copilot reads `.github/copilot-instructions.md` on every request. Add one line — `For SEO work, read the SEOAgent SKILL.md that seoagent init installed and follow it` — or a scoped `.github/instructions/seo.instructions.md` with `applyTo` for your content folders. Every future session then finds the procedure without being told.

4/ 6

Ask for an audit and review the diffs

Say "audit my site". The Skill fetches the homepage, sitemap and robots.txt, runs the technical checks, and reports findings with the exact fix. Copilot proposes the fixes as edits — metadata, schema, canonicals, internal links — and VS Code shows them file by file. Keep what makes sense.

5/ 6

Write content and let Copilot open the PR

Ask for keyword research and an article or landing page; the Skill writes the files where your framework expects them, internally linked into the cluster. If your team uses the Copilot coding agent on GitHub, assign it the brief as an issue and review the pull request it opens — the same Skill, the same files.

6/ 6

Give it a weekday routine

Copilot has no scheduler of its own, so the block adds a cron line — `0 9 * * 1-5 cd <repo> && seoagent sync --silent` — that keeps `.seoagent/inbox/` fresh. Open agent mode in the repo each weekday morning and say "process the inbox"; it works the items and runs `seoagent ack` for each. What it learns is written to `.seoagent/` for the next session.

03 — Capabilities

What SEOAgent does in Copilot

01

Technical audits with the fix attached

Every finding names the file and the change, so agent mode can apply it rather than describe it.

02

Edits reviewed in VS Code

Fixes arrive as proposed edits in the editor; accept or reject per file, like any Copilot change.

03

Keyword research with real numbers

`seoagent keywords` pulls volume and difficulty so content targets queries you can win.

04

Content as files, not a CMS post

Articles and landing pages are written into your repo with metadata and internal links already set; a reviewed commit ships them.

05

Search Console grounding

`seoagent login` connects Google Search Console once; the Skill then reads your real queries and pages.

06

Works with the Copilot coding agent

Briefs can be handed to the GitHub-side coding agent as issues; it opens pull requests you review, using the Skill checked into the repo.

07

Approval on every command

Agent mode asks before running anything in the terminal, and the block tells it to stop and report if the bind fails.

08

AI search readiness

`seoagent llms` builds an `llms.txt` from your page inventory; `seoagent okf` serves an Open Knowledge Format bundle at `/.well-known/okf/`.

04 — FAQ

Frequently asked questions

How do I add SEO to GitHub Copilot?

Create the prompt on this page and paste it into Copilot agent mode 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. Add one line to `.github/copilot-instructions.md` so later sessions find the Skill.

Does it need Copilot agent mode?

Yes. Ask mode answers questions; agent mode runs commands and edits files, which the Skill needs. Edit mode can apply individual changes but cannot run `seoagent` commands.

Is the SEO Skill for Copilot free?

Yes. The Skill runs on your Copilot subscription and 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.

Will Copilot publish content on its own?

No. Every change is a diff you review in VS Code or a pull request you merge. SEOAgent never publishes to a CMS itself.

Where does the Skill install?

`seoagent init` writes the bundle to `.agents/skills/seoagent/` if your repo already uses `.agents/`, otherwise `.claude/skills/seoagent/`, and adds a SEOAgent section to `AGENTS.md`. The files are tracked in git, so a teammate who clones the repo gets the same Skill.

What if the paste fails?

The block tells Copilot to stop and report the exact error rather than continue unbound. The card waits for the bind and, after three minutes, asks what you saw and routes you. Codes live 14 days and work once.

Can I use it on a site without a repository?

If the site is on a hosted platform (WordPress.com, Shopify, Webflow, Wix and others) the block says so and the agent runs the setup in an empty folder; delivery goes through the platform’s API or the editor. With no agent at all, the "Just my website" door is for you.

How do I update the Skill?

Run `npm install -g @seoagent-official/seoagent@latest`, then `seoagent init` again. It refreshes the bundle and leaves `.seoagent/` untouched.

Give Copilot the SEO procedure

Enter your site, create the prompt, and paste it into Copilot agent mode — 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