What Claude SEO skills should I install first?

Install a small set of Claude SEO skills matched to weekly jobs - page brief, on-page QA, outline from SERP notes. Stabilize with Projects and prompts first.

Install few Claude SEO skills tied to jobs you already repeat weekly - page briefs, on-page checks, outlines from SERP notes - not a marketplace dump on day one. Start with categories that have stable inputs (URL, target query, search notes, brand voice). Keep prompts in a Project until the loop stops changing, then graduate winners into skills. The install-order pattern matches What Claude marketing skills to install first; the broader Growth map starts at Claude for marketing. Deeper SEO systems belong on Claude for SEO (planned) (planned) and Claude SEO skills (planned) (planned) - this page is install order only.

TL;DR. Pick 3-5 job slots (page brief, on-page QA, outline from SERP notes, optional internal-link pass, optional claims/source gate). Install marketplace/plugin skills only when names match those jobs today. Otherwise stay on prompts + Projects. Cap day one at three.

Criteria - what earns an “install first” slot

Use this bar before you add anything:

Criterion	Pass when…
Repeat weekly	You run the job ≥1×/week (brief, on-page pass, outline)
Has inputs	You can load a URL, target query, SERP notes, or draft - not blank chat
QA bar	You know what “good” means (no invented rankings, no fake citations, one primary intent)
Stable loop	The prompt/spec barely changes between runs

Fail any row - keep it as a prompt in a Project, not a skill yet. Same rule as the marketing install-order spoke.

Starter set (3-5 job slots)

These are categories, not a scraped marketplace directory. Marketplace skill names change; verify on the official marketplace / plugin browser the day you install. Do not treat the labels below as product SKUs.

Page / content brief - query + SERP notes + audience - brief with intent, outline angles, must-cover entities, and what not to claim. Highest leverage if briefs are still fuzzy.
On-page QA pass - draft or live URL notes - checklist against title/H1 alignment, intent match, thin sections, weak CTAs. Not a full technical crawl.
Outline from SERP notes - pasted competitor headings / snippet themes - structured outline with gaps called out. Useful once you actually collect SERP notes.
Internal-link / structure pass (optional) - existing sitemap or URL list + draft - candidate links and section order. Add only if that job is weekly.
Claims / source gate (optional) - strip invented traffic numbers, rankings, and “studies.” Add when drafts keep hallucinating SEO metrics.

Install order: (1) - (2) - (3), then at most one of (4)/(5). Cap day-one installs at three.

Install path (high-level)

Skills reach Claude through several paths (personal ~/.claude/skills/, project .claude/skills/, plugins/marketplace, claude.ai sync). For SEO workflows:

Prefer a Project with brand docs, example briefs, and a pasteable prompt pack first.
When a job is stable, either author a thin SKILL.md for that job or install a matching plugin/marketplace skill after you confirm the name and description same-day.
In Claude Code, use /plugin browse/install (or documented /plugin install …@… forms) - don’t trust third-party “top 50 SEO skills” lists as product truth.
Prune unused skills when the listing gets heavy - unused skills still cost context.

This page will not list unverified skill titles. The deeper inventory belongs on Claude SEO skills (planned) (planned).

When not to install yet

Day zero with no SERP or page inputs - skills won’t invent keyword research you refuse to paste.
One-off spikes - chat + a pasteable prompt is enough; skills earn their keep through repetition.
“Install everything SEO” packs - every skill description competes for listing budget; bloat makes the right skill less likely to trigger.
Jobs you don’t own yet - full technical audits, link-building ops, and CMS migrations stay out of the first three slots. See the Growth map: Claude for marketing. For the same install-order discipline on marketing jobs, use What Claude marketing skills to install first.

Default stack for week one: Projects + prompts. Skills after the loop is boring (in a good way).

FAQ

What’s the best Claude SEO skill to install first?
The one that matches your highest-frequency job with real inputs - usually page/content brief or on-page QA. There is no universal #1 marketplace name that stays true forever.

Should I install skills before writing prompts?
Usually no. Stabilize the prompt/spec, then graduate. Same pattern as marketing skills - install first.

Where’s the full list of SEO skills?
Claude SEO skills (planned) (planned). This URL owns install order + criteria, not a catalog - and it does not replace Claude for SEO (planned) (planned).

Can skills replace a keyword research Project?
No. Skills load instructions when relevant; they don’t replace loading SERP notes, briefs, and proof into a Project.

How many skills is too many on day one?
If you can’t name the weekly job each skill serves, you’ve overshot. Start ≤3.

Sources (checked 2026-09-13)

Live pattern mirror: What Claude marketing skills to install first · Growth map: Claude for marketing
Planned SEO spokes (do not cannibalize depth here): Claude for SEO (planned) (planned) · Claude SEO skills (planned) (planned)
Skills mechanics / marketplace pattern: code.claude.com/docs/en/skills · anthropics/skills README - verify skill names same-day

Field note, checked 2026-09-13: claims above follow dated primary sources linked in-body; re-verify product surfaces before you change permissions or install skills.

Packaging patterns: Claude Skills. Marketing install-order twin: What Claude marketing skills should I install first?.