The best SEO skills for Claude cover ten jobs: a full technical audit, AI search visibility, competitor gap analysis, keyword clustering, content briefs, E-E-A-T content review, schema markup, Search Console click-through fixes, cannibalization checks and local SEO. Install them once and Claude follows the same checklist every time you ask, instead of improvising a new one in every chat.
We use Claude for SEO work every week, and the difference between a good prompt and a good skill is consistency. A prompt depends on whoever typed it. A skill is a written method that Claude loads when the task calls for it, with the same steps, checks and output format each run.
Below are the ten we’d install first, what each one does, where the free versions come from, and the places where you still need a human looking at the output.
What a Claude skill is
A Claude skill is a folder with a SKILL.md file inside it. The file starts with a short name and description, then lists instructions, examples and, if needed, scripts or reference files. Anthropic’s Agent Skills documentation explains that Claude only reads the name and description at first. It opens the full instructions when your request matches, and pulls in scripts or reference files only when a step needs them.
That staged loading matters for SEO. You can keep twenty skills installed without stuffing every chat with instructions, and Claude picks the audit skill when you ask for an audit and the schema skill when you ask about structured data.
Skills work in three places. In Claude Code, you drop them into ~/.claude/skills/ for personal use or .claude/skills/ inside a project. In the Claude apps, you upload a custom skill as a zip file in Settings under Features. Developers can also upload them through the Claude API.
The 10 SEO skills worth installing
Most of the named commands below come from Claude SEO, an MIT-licensed pack on GitHub that lists 26 skills in version 2.4.1. Where a skill isn’t in that pack, we’ve noted a good source or the prompt that does the same job.
1. Full-site technical audit
Command: /seo audit <url>, with /seo technical for the deeper crawl checks. It crawls the site, checks crawlability, indexability, mobile rendering, security headers and Core Web Vitals, then returns a 0 to 100 health score and a fix list sorted by impact. The audit hands specific findings to specialist sub-skills, so a missing-schema finding goes to the schema skill and a slow template goes to the performance checks.
Our note: treat the score as a conversation starter. The fix list is where the value is, and you should sanity-check the top five items against Search Console before anyone opens a ticket.
2. AI search and GEO visibility
Command: /seo geo <url>. It checks whether AI crawlers can reach your pages, whether your content renders in raw HTML, whether you have an llms.txt file, and how easy your passages are to quote. The goal is getting cited in ChatGPT, Perplexity and Google AI Overviews.
Our note: the fixes it suggests are mostly old-fashioned good writing. Clear definitions near the top of the page, one idea per paragraph, real numbers with their source. That’s good for human readers too.
3. SERP and competitor gap analysis
This skill looks at the pages that already rank for your topic, pulls the subtopics and keywords they share, and lists what your site is missing. Metaflow‘s version labels each gap as create, update or skip, which is the most useful output format we’ve seen, because it turns a long list into a work queue.
Our note: Claude can’t see live search results on its own. Feed it exported SERP data or connect a data source such as the DataForSEO extension in the Claude SEO pack, or the gap list will be built on guesses.
4. Keyword research and intent clustering
Command: /seo cluster <seed keyword>. It groups keywords by search intent and by how much the ranking pages overlap, then maps them into a hub page with supporting articles around it. Give it volumes and difficulty from your keyword tool and it will rank the clusters for you.
Our note: this is where Claude saves the most time on a new site. Sorting a few hundred keywords by intent by hand takes an afternoon. The skill does a first pass in minutes, and you spend your time correcting the edge cases.
5. SEO content brief generator
Command: /seo content-brief. It builds a brief from the ranking pages: suggested title, H1 to H3 outline, questions to answer, internal links to add and draft meta tags. A writer, human or AI, can work straight from it.
Our note: always add one thing the ranking pages don’t have, such as your own process, a local detail or a worked example. A brief built only from competitors produces an average page.
6. E-E-A-T content review and research writing
Command: /seo content <url> scores a page for experience, expertise, authority and trust, plus thin content and readability. For drafting, the community content-research-writer skill (listed in ComposioHQ’s awesome-claude-skills collection) runs several rounds of research and writes a sourced article section by section.
Our note: use the review skill on every draft, including the ones Claude wrote. It catches missing author details, unsourced claims and padded sections that a quick read misses.
7. Schema markup generator and validator
Command: /seo schema <url>. It detects the structured data already on a page, flags errors and drafts JSON-LD for the types that fit, with more than 30 types covered in the Claude SEO pack. FAQ, Article, LocalBusiness, Product and Service are the ones most small sites need.
Our note: paste the output into Google’s Rich Results Test before it ships. Valid code and eligible code aren’t the same thing.
8. Search Console click-through gap analyzer
Command: /seo google connects to Search Console, PageSpeed Insights, CrUX and GA4. The most useful report finds pages with plenty of impressions and few clicks, then rewrites their title tags and meta descriptions. Pair it with a rule like “55 to 60 characters, target keyword first” and Claude can rewrite titles for a whole category in one run.
Our note: change titles in batches and note the date. Give each batch three to four weeks before you judge it.
9. Cannibalization detector
This one looks for queries where two or more of your own pages rank in the top 20 and split the clicks between them. For each case it suggests whether to merge the pages, redirect one, or sharpen each page toward a different intent.
Our note: there’s no famous packaged skill for this yet, so we keep it as a saved prompt run on Search Console exports. It’s one of the quickest wins on older blogs with years of overlapping posts.
10. Local SEO and Maps intelligence
Commands: /seo local <url> for Google Business Profile completeness, name, address and phone consistency, citations and reviews, and /seo maps for geo-grid rank checks and competitor radius mapping. If you serve customers in a set area, this is the skill that tells you why you show up on one side of town and not the other.
Our note: pair it with our local SEO checklist so the findings land on a list someone actually works through.
Search Console prompts that do the heavy lifting
A widely shared LinkedIn post listed ten Search Console prompts that work well as small skills or saved prompts. These are the ones we’d keep:
- Declining pages: pull 90 days of impressions, grouped by page, query and the date the drop started.
- Striking distance: find queries where you rank 5 to 15 and click-through rate is below 2%.
- Crawled but unused: list pages with under 10 clicks in 90 days that Google still crawls often.
- Internal links: add a link to the pillar page wherever its topic is mentioned, with the exact anchor text and placement.
- Topical support: for your top 20 topics by impressions, suggest three supporting articles based on the queries that appear together.
Each of these is a few lines of instructions. Save the ones you run monthly as their own skills so the date ranges and output columns stay the same each time.
How to set them up
- Pick a home. Claude Code suits audits and anything that touches files. The Claude apps suit briefs, reviews and rewrites.
- Install the pack. For Claude SEO, the project’s install script clones the repo and copies the skills into place. For a single skill, put its folder in your skills directory, or zip it and upload it in the Claude app settings.
- Connect your data. Search Console and PageSpeed access turn the audit and click-through skills from opinions into findings. Keyword volumes come from your existing SEO tool.
- Read before you install. Anthropic’s documentation warns that a malicious skill can direct Claude to run code or call tools in ways the description doesn’t mention. Open every file in a third-party skill, the same way you’d check any software before running it.
- Run one skill end to end. Start with the audit on your own site, act on the top fixes, then add the next skill.
Where skills fall short
Skills give Claude a method. They don’t give it data. Without Search Console, a crawler or SERP exports, the best audit skill will reason about your site from whatever it can fetch, and it will sound more confident than it should.
They also don’t replace judgment. A skill can tell you two pages are cannibalizing each other. Deciding which one to keep depends on which one brings leads, and that’s in your CRM, not in Search Console.
If you’d like this set up and running on your site, our SEO team uses these workflows every week, and our Claude for Business setup service installs and tests skills for your own team. Want to see what an audit turns up first? Start with a free SEO audit.
