SEO Specialist — Claude AI Skill for Complete SEO Strategy & Implementation

Without SEO Specialist

With SEO Specialist

Ask about a rankings drop — get a generic list of possible causes with no diagnosis

Applies the diagnostic framework — identifies the 2–3 most likely root causes, explains how to confirm each, and gives the resolution path

Ask about fixing a canonical issue — get a paragraph explanation with no actual code

Applies the implementation framework — copy-paste-ready code with comments, edge cases flagged, and a verification step included

Ask about technical SEO for a JavaScript SPA — get surface-level advice about prerendering

Deep knowledge of JS SEO — rendering modes, dynamic rendering, GSC fetch and render checks, and whether your specific SPA framework needs intervention

Ask about AI Overviews and zero-click — get a generic “optimize for featured snippets” response

Specific, current guidance on citation signals, zero-click resilience strategies, and which content types are most at risk vs. most defensible

Ask for a content strategy — get a listicle of generic tips about keyword research

A specific strategy: topical cluster design, intent mapping, hub-and-spoke structure, and priority order by impact and feasibility for your site

GSC drop in impressions — no idea where to start, no framework for diagnosis

Walks through the drop systematically: algorithm update, indexation issue, cannibalization, SERP feature change — and tells you exactly which GSC report to check for each

When you ask for a fix, the skill diagnoses the likely root cause first, then gives you the exact solution — actual code, robots.txt syntax, redirect maps, hreflang tags, JSON-LD schema — not a description of what to write. Edge cases are flagged. Every implementation answer closes with how to verify it’s working.

Example: "How do I fix duplicate content across /blog/ and /blog/page/1/?"
→ Root cause: pagination generating indexable duplicates
→ Fix: rel="canonical" on /blog/page/N/ pointing to /blog/ (with code)
→ Edge case: if page 2+ has unique content worth indexing, use noindex instead
→ Verify: GSC Coverage report — confirm /blog/page/N/ moves to Excluded

Traffic drops, ranking changes, indexation issues, crawl errors — the skill names the 2–3 most probable causes in order of likelihood, tells you exactly which report or test to run to confirm which one it is, and gives the fix for each scenario. No guessing. No “could be many things.”

Example: "Organic traffic dropped 30% in the last 4 weeks."
→ Cause 1 (most likely): algorithm update — check HCU / March 2025 core update dates
→ Cause 2: technical regression — check GSC Coverage for new crawl errors
→ Cause 3: SERP feature change — check if AI Overview now dominates your top keywords
→ Confirmation: compare GSC clicks by page to isolate where the drop is concentrated

Strategy questions get a direct recommendation — what the skill would actually do — backed by reasoning and data. Trade-offs are acknowledged briefly if they’re material. When there are multiple actions, they come in priority order by impact. No both-sidesing. No wishy-washy “consider whether.”

Highest-impact issues first. Grouped by theme: technical, content, on-page, authority. For each issue: what it is, why it matters, exact fix. Closes with a P1/P2/P3 prioritized action list.

Short, direct questions get short, direct answers — no framework needed. “Should I use 301 or 302?” gets the right answer in one sentence, not a 500-word explainer.