Guide
Claude SEO Skills: Free and Paid SKILL.md Playbooks Compared (2026)
Free and paid SEO skill packs for Claude Code, Cursor and Codex side by side: what each GitHub repo covers, its license, and how to choose one for your work.
Search GitHub for SEO skills for Claude Code and you get many repos with similar names. They differ more than the names suggest: some are audit plugins with their own sub-agents, some are broad marketing libraries, one runs on a hosted data connector, and a few are narrow playbooks. This page puts the open-source projects we checked next to our own free and paid Claude SEO skills, described from each project's own README. It lists no star counts or rankings, because those change every week.
Short answer: for a broad, free SEO audit inside Claude Code, start with claude-seo. For a wide marketing library, try marketingskills or kostja94's marketing-skills. For GEO-first audits, geo-seo-claude or gtm-engineer-skills. For skills on top of your own Search Console data, open-seo-mcp-skills. Our paid pack is narrower: dated 2026 search changes, AI-search playbooks and review gates that stop at a decision. Try its two free skills first.
Which Claude SEO skills are on GitHub in 2026?
Every repo below existed on 4 November 2026, was not archived and had a license file. Each line paraphrases the repo's own description.
| Skill | What it does | Free or paid | Link |
|---|---|---|---|
| claude-seo | SEO audit plugin for Claude Code: sub-skills and sub-agents for technical SEO, E-E-A-T, schema, GEO/AEO, local and e-commerce SEO. | Free (MIT) | GitHub |
| marketingskills | Marketing skills for AI agents: CRO, copywriting, SEO, analytics and growth engineering. | Free (MIT) | GitHub |
| marketing-skills | A large library of marketing and SEO agent skills: technical and on-page SEO, content, page types, paid ads and channels. | Free (MIT) | GitHub |
| geo-seo-claude | GEO-first SEO skill for Claude Code: citability scoring, AI crawler analysis, brand authority, schema markup and PDF reports. | Free (MIT) | GitHub |
| gtm-engineer-skills | Agent workflows for AEO and GEO: brand and keyword research, content planning, website AEO audits and fixes. | Free (MIT) | GitHub |
| open-seo-mcp-skills | SEO and GEO skills for Claude that run on a hosted MCP connector reading your Search Console, GA4 and ads data. | Free (MIT) | GitHub |
| claude-blog | Blog writer for Claude Code: researches sources, writes answer-first posts, has a reviewer agent score each one and runs delivery gates. | Free (MIT) | GitHub |
| fire-your-seo-agency | A Claude Code skill that audits and optimizes for SEO, AEO, GEO, LLMO and Naver search, with a content pipeline. | Free (MIT) | GitHub |
| agent-skills-pack-free | Our two free skills: skill-review (audit any SKILL.md) and search-change-triage (a weekly wait, watch or act call). | Free (MIT) | GitHub |
| The 2026 SEO & AI-Search Skill Pack | Our 11 skills: 2026 technical SEO changes, AI-answer and GEO citation playbooks, a programmatic SEO gate, an agent safety contract and a review rubric. | Paid ($29 one-time) | Pack overview |
Where are the other packs broader than ours?
In most directions, and on purpose. Be clear about it before you buy anything:
- Agents and commands. claude-seo and claude-blog ship sub-agents, slash commands and optional extensions for live data. Our skills are plain Markdown folders with no agents, scripts or install step.
- Marketing beyond search. marketingskills and kostja94's marketing-skills cover CRO, copywriting, ads and channels. Ours covers search only. One of our skills,
programmatic-seo-gate, builds on marketingskills (MIT) and credits it in the skill and in the notices. - Live data. open-seo-mcp-skills connects the agent to your real Search Console and GA4 data through an MCP server. Ours ships no MCP server; the agent works from exports and pages you give it.
- Reports. geo-seo-claude and claude-seo can produce PDF reports. Ours end in a table, a note or a decision.
- Markets. fire-your-seo-agency covers Naver search for Korea. Ours does not.
What does the paid pack focus on instead?
Three things the broad packs treat as one item among many:
- What changed in 2025 and 2026.
technical-seo-2026-deltachecks only the recent changes, with evidence URLs, instead of re-running a classic audit. The facts are dated, so you can tell when one is stale. - AI-search playbooks with honest measurement.
geo-citation-playbookworks on being cited by ChatGPT Search, Copilot, Perplexity, Claude, Gemini and AI Mode, and never reports a rate without its sample size. - Gates that stop at a decision.
programmatic-seo-gatesays yes or no to pages at scale,search-change-triageends in wait, watch or act, andseo-agent-designkeeps a human on every publish.skill-reviewis the rubric to audit any of them, or any skill in the table above.
How do you choose a Claude SEO skill pack?
Start from the job, not the repo:
- One command, full audit report: claude-seo or geo-seo-claude.
- Your own Search Console and GA4 data inside the agent: open-seo-mcp-skills, if you are happy to connect its hosted connector.
- Copy, CRO and ads as well as SEO: marketingskills or kostja94's marketing-skills.
- A pipeline for blog posts: claude-blog.
- The Korean market: fire-your-seo-agency.
- Dated 2026 rules, AI-search playbooks and decisions that stop before changes: our pack. Install the two free skills first; if they fit how you work, the other nine follow the same pattern.
Whichever you pick, read a few SKILL.md files before you install the whole set. The description and the constraints tell you more than the README.
Can you use several skill packs together?
Yes. Skills are folders, so packs mix freely. Two things to watch:
- Name collisions. If two packs ship a skill with the same folder name, the agent has to pick one. Keep one copy per name.
- Overlapping descriptions. Two audit skills that both claim "any SEO task" will fight over requests. Run
skill-reviewon the set; it scans sibling skills for overlapping descriptions.
The install guide has each agent's skills folder, and the skill-writing guide covers how to tighten a description that triggers too often.
How did we check these repos?
On 4 November 2026 we ran gh repo view on each candidate to confirm that it exists, is not archived and has a license, then read its README and counted its SKILL.md files. We describe each project only from its own README and description, and we print no star counts, since they change daily.
We dropped one candidate: seomachine, a full Claude Code workspace for long-form blog content. Its README lists a DataForSEO account as a prerequisite, so it does not compare like for like with drop-in skill folders. Repos change quickly: check the README and license yourself before you install.