
An SEO skill can read the page you paste and tell you what looks wrong with it. It cannot tell you whether that page is winning or losing this month. Which of those two jobs do you actually get paid for?
Somewhere in the last few weeks the question stopped being whether Claude can do SEO work and became which SEO work to hand it. You can see the turn on the results page for Claude SEO skills itself. The top of that query is a GitHub repository, two single-purpose skill sites, one Reddit thread and a vendor page from a company that sells a full SEO suite. Your version of this is quieter. A skill runs clean on a page audit, you fix what it flags, and the quarterly numbers land unchanged, because the pages it told you to fix were never the ones losing traffic. Nothing in that folder knows how much traffic any page has. That is not a flaw in the skill. It is a fact about what a folder of instructions is.
What Claude SEO Skills Are, and the Two Piles They Fall Into
Google's AI Overview answers this query with a definition that is accurate and incomplete: Claude SEO skills are "specialized prompts, scripts, or plugins that turn Claude into an expert SEO and AI search consultant." That covers the shape and leaves out the constraint.
A skill is a folder on your machine, holding a SKILL.md file plus whatever reference material the author included. Claude reads the description, and when your request matches it, the folder loads and Claude follows it. We covered how that differs from agents, commands and MCP servers in Claude Skills explained. For an SEO practitioner the part that matters is what the folder holds: instructions, checklists, reference text. No web index. No ranking data. No crawler.
Searches for "claude skills vs commands" come from this same confusion, and the answer is short. A command is what you type. A skill is the procedure that loads once the request matches. In the packs ranking here the two arrive together. Neither one carries data.
So the useful question is not "is this skill good" but "what does it need to read." That question sorts the entire market into two piles:
- Pile one: jobs whose only input is something you can paste. A URL, a page's HTML, a draft, an outline, a list of your own published URLs. If you can put everything the job needs into a message, a skill finishes it today, offline, for free.
- Pile two: jobs that need a fact from a database you do not own. Which pages rank for what. The search volume of a term. Who links to a competitor. Whether a URL is indexed right now. The skill can write the query. It cannot produce the answer.
Check the input, not the promise. That check is also why the AI Overview's own capability list (complete site audits, GEO and AEO optimization, content strategy) reads like an inventory rather than a decision.
What an SEO Skill Can Genuinely Do: Four Jobs Worth Installing
Four jobs come back clean from a folder of instructions, and all four share one property: you supply the material. Each is described by its output, because that is what you can verify.

1. On-page recommendations from a URL you hand over. Paste a page or a full HTML export. You get a prioritized fix list: a title that runs too long, a missing H1, headings that skip a level, alt text that says nothing, internal links pointed at the wrong page. This replaces the checklist pass most specialists do by hand, faster. It does not know whether the page ranks. A connected on-page SEO optimizer supplies the missing half, which is whether the fixes moved anything.
2. Content briefs from a SERP you paste. Give the skill the headings of the pages currently ranking and the term you want to win. It returns an outline with the gaps named: what four of five ranking pages cover, what none of them answer, which questions belong in a FAQ block. The brief is solid. Gathering the raw material stays your job.
3. Internal-link candidates from your own inventory. Export your published URLs and titles, paste them in, and the skill proposes anchor and target pairs, flagging the pages nothing links to. This is one of the few SEO jobs where the data genuinely lives on your own site, which is why it works so well. The judgment about whether a phrase means the same thing in both places stays with you, and this is where SEO automation alone usually stops being enough.
4. Schema and metadata drafts. Article schema, FAQPage markup, sixty-character title variants, a meta description with the term in the first half. Output you can paste into a CMS without editing. Low ceiling, high reliability.
What all four share: the skill never needs to know something that changed this morning. That is the whole of pile one.
What an SEO Skill Cannot Do, and Why Not
Here is the honest list, and it is not a criticism of any particular pack. A folder of instructions cannot crawl your site at scale, read every status code, see a backlink index, report whether a URL is indexed, measure Core Web Vitals from field data, track where you rank today or last month, tell you the search volume of a term, find the keywords a competitor ranks for that you do not, or tell you whether a fix worked after you shipped it.
The structural reason fits in one sentence: a skill is instructions, and instructions cannot supply data they do not have. Every SEO skill's real limit is its data source, not its prompt. You do not have to take that from us, because the sources competing for this query say it themselves.
SE Ranking ships a first-party SEO skill pack and answers the obvious objection on its own page: "Without it, Claude can still follow instructions, but it cannot use live SE Ranking data inside those workflows." The "it" there is the company's MCP server, and that sentence is the entire argument for the subscription. The position 1 GitHub repository concedes the same thing in its Limitations section: Core Web Vitals without Google credentials are lab estimates, and competitive plus AI-citation data "requires their respective accounts" for Ahrefs, DataForSEO, SE Ranking or Profound. The strongest editorial guide in the top ten states it as a warning: "Do not cancel Surfer or Semrush on day one. Use them as data sources." And a consultant's library page cited by the AI Overview headlines the claim that skills replace "$410/month in SEO tool subscriptions," then qualifies it in the same block, because "data gathering still needs Screaming Frog or a paid crawler."
Four sources conceding the same boundary, in their own words. The category's own marketing admits where the instructions stop before it asks you to pay for the other side. If you are planning a technical SEO audit around a free skill, that is the wall, and you meet it the moment the audit has to know something true about the live web.
The Data-Layer Problem, Worked Through One Real Task
Take the request every SEO team eventually makes: find the keywords my competitor ranks for that I do not.
Run it through pile one logic and watch where it breaks. The skill needs a list, and that list must contain the competitor's ranking keywords, their estimated volume and your own position on each. Three fields, all facts about the live index.
With instructions only, you have two options. Export the list from a paid tool and paste it in, at which point the skill is formatting data you already bought. Or ask the model to recall it, at which point you get plausible keywords with invented positions. The second option is the dangerous one, because the output looks identical to the first. You cannot tell a real volume column from a generated one by reading it.
Connect a data source and the picture changes. The competitor's ranking set comes from an index, not from memory. Your own positions come from the same index. The gap, the one list you actually wanted, gets computed instead of guessed. Only then does the instruction layer earn its keep, because sorting 4,000 rows into clusters and writing the briefs is exactly what a folder of instructions does well.
The division of labor is worth stating plainly: the data layer decides what is true, and the skill decides what to do about it. Both halves are necessary, and neither substitutes for the other. This is the job Allable's keyword research module and backlink gap analysis were built for, connected to real indexes rather than a pasted export.

What Is Already Built: The SEO Skill Landscape in September 2026
The field is lopsided in a way its own directories do not show. Six assets hold the page, four of them free, and not one was written for an SEO who does not live in a terminal.
Asset | Position | What it actually is | Who it is written for |
|---|---|---|---|
github.com/AgricIDaniel/claude-seo | 1 | "Universal SEO skill for Claude Code." 25 sub-skills, 18 specialist agents, 32 commands, MIT licensed. Self-reported 16.7k stars, 2.4k forks (repo, Sep 10, 2026), 306 commits, 763 passing tests at v2.3.1 | Developers. Needs Python 3.10+ and the Claude Code CLI |
claudeseoskill.com | 2 | Single-purpose skill site, roughly 600 words of product copy. Output is a scored DOCX plus PDF report "designed to look like a premium agency deliverable you'd charge for" | Buyers who want a deliverable. No editorial argument on the page |
AI Overview | 3 | Inventory-shaped answer. Cites six free assets with no assessment of whether any of them can get data | The searcher who never clicks |
Reddit, r/ClaudeAI | 4 | "My New Claude Skill - SEO consultant - 13 sub-agents, 17" and rising, built by a practitioner who shows no verification of the output | Other builders. Enthusiasm, no quality filter |
claude-seo.md | 6, then 5 | Documentation surface for a "Free AI SEO Audit Tool for Claude Code" (Feb 21, 2026). Eight optional MCP extensions, a Tier 0 to 3 credential model | Operators. Its own docs admit indexation is inferred without credentials |
seranking.com | 9, then 7 | "SEO Skills for Claude, Built by SE Ranking." Seven pre-built skills wired to 180+ MCP tools, public GitHub repo, installs into Claude Desktop or Claude Code | The non-technical buyer, the only route here that does not want a terminal |
The movement in that table is the story. When this cluster's research began, SE Ranking sat at position 9. Two days later it held position 7, and the same URL ranks on seo skills for claude at 5 and claude code seo skills at 8. Three top-10 placements across four related queries is a deliberate content position from a tracked competitor, and it is climbing while the free assets hold still. It is also the one commercial asset Google is not citing in the AI Overview, which is the opening for anyone willing to answer the boundary question head on.
Then there is the price of the missing half. SE Ranking's subscription starts at Core, $129/month or $103.20 billed annually, with Growth at $279/month and the AI Search add-on billed separately. "Start with 100K credits" sits next to a 14-day trial, and the tier names have already changed once, so verify the plan before you commit. The free repository's route costs Google API credentials plus a Claude Code subscription, and its release notes say a full audit became more expensive at v2.3.1 because five judgment-heavy agents moved to a costlier model.
One more thing belongs here and no ranking page mentions it. This ecosystem has a security problem. Snyk's ToxicSkills audit, published February 5, 2026, scanned 3,984 skills from ClawHub and skills.sh and found 13.4% carried at least one critical-level security issue, with 36.82% flawed at any severity. Three lines of markdown in a SKILL.md file were enough to exfiltrate SSH keys. The OWASP ClawHavoc campaign in January 2026 used 1,184 malicious skills across 12 publisher accounts pointing at one command-and-control IP, and five of the top seven most-downloaded ClawHub skills at peak infection were confirmed malware. A USENIX Security 2026 study of 98,380 skills found 73.2% of the malicious ones hid features from the user.
That lands harder for SEO than for a developer buying a prompt library. An SEO skill's natural inputs are Search Console access, analytics credentials and a site crawl, which is precisely what these attacks target. When you are weighing packs, best SEO tools and best AI SEO tools belong in the same decision, because a free download carries a risk paid software does not.
How to Evaluate an SEO Skill in Five Minutes
Five questions. A pack that fails any of them does not get installed, whatever its prompt quality.
1. What does it read, and where does that come from? Name the input file or data source behind every job it claims. If the answer is "the model's knowledge," the output is a guess with good grammar.
2. Does it need data, and do you already have it? A skill built for a Surfer or Semrush subscriber is a fine skill, and a bad one for your team if nobody holds those seats.
3. Does it produce an artifact or an opinion? A prioritized fix list, a schema block, a cited brief you can hand to a writer: those are artifacts. "Your content could be more engaging" is not worth an install.
4. Can you verify one output in ten minutes? Pick a page you know cold, run the skill and check three of its claims against reality. This is the step everyone skips and the one that tells you whether the pack is honest.
5. Who wrote it, and do they sell the other half? A vendor-authored skill that routes you to that vendor's data layer is not a neutral recommendation, it is a funnel. That is a legitimate business, and it should change how you read the install guide.
Three phrases in this cluster need one line each rather than a section. Lists promising top claude skills mostly rank the author's own repository, so treat any leaderboard as a vendor page. Queries like superpowers claude skills and claude skills download describe the same folder of instructions and inherit the same boundary. And claude skills best practices comes down to one thing: check the data source before you check the prompt.
If a pack passes all five and you still cannot place it in your week, the problem is upstream of the skill. It usually means the process itself was never written down, which is a fix you can make without installing anything.
Where SEO Skills Are Heading
Something unusual happened here. A tracked competitor shipped a product into a brand new surface before that surface had a written buyer's guide. SE Ranking built seven skills, wired them to 180+ tools and put them in front of a non-technical buyer while the top ten was still repositories and Reddit threads.
The next six months look predictable from there. Expect more vendor packs, because the playbook works: give away the instruction layer, sell the data layer. Expect the free packs to keep splitting along developer and practitioner lines. Expect the security conversation to reach marketing teams late, because it lives in engineering feeds right now.
The split will not move. Instructions keep getting better at deciding what to do, and data stays the thing you buy. If you are weighing AI SEO services options, or running AI SEO for agencies delivery across client accounts, that split is the question to put to any vendor or any pack you consider: which side of it are you actually on?
Frequently Asked Questions
What are SEO skills for Claude?
Folders of instructions that give Claude a repeatable process for one SEO job, usually a SKILL.md file plus reference material. Claude loads a folder when your request matches the description inside it. They carry process, not data, which is why they can audit a page you paste and cannot tell you where that page ranks.
Are SEO skills for Claude free?
Free to install, rarely free to run. Most packs on this SERP are open source or MIT licensed. The cost sits behind them: the position 1 repository needs Google API credentials for real Core Web Vitals plus third-party accounts for competitive data, and SE Ranking's skills require its subscription, from $129/month on Core. Its own page says that without the MCP server Claude "cannot use live SE Ranking data inside those workflows."
Do I need Claude Code to use an SEO skill?
No, and this is where the market quietly split. Skills are a Claude feature, not a Claude Code feature, and some packs run inside Claude.ai on a free account. SE Ranking's pack installs into Claude Desktop or Claude Code, the only non-technical install path in the top ten. The friction is the route rather than the tool, so ask who on your team will run that step before you plan around it.
Can Claude Skills replace an SEO tool?
Not the data layer, and no pack on this SERP claims otherwise once you read its FAQ. A skill can audit a page, draft a brief, propose internal links and write schema. It cannot crawl your site at scale, track rankings, read a backlink index or measure search volume. Treat a skill as the methodology layer and keep a data source underneath it.
What is the best Claude SEO skill?
The one whose data source you already have. If you run a terminal and hold Google API credentials, the position 1 repository is the deepest free option here and the only one that publishes its own limitations. If you want a report you can hand a client without touching Python, claudeseoskill.com is built for that. If you already pay for an SEO suite, start with that vendor's first-party pack, because the skills only reduce the clicking. Judge every candidate on question one: what does it read, and where does that come from?
Run the jobs a folder of instructions cannot.
Connect your search, analytics and ads accounts and let the agent work from your real rankings, real backlinks and real traffic instead of a pasted export. Free during the 7-day trial at studio.allable.ai.