The Claude Code SEO Stack 2026: Skills, MCP, Agents, Hooks

The Claude Code skills layer, the load-bearing entry point

The 30-second rule: the Claude Code SEO stack composes four layers (skills, MCP, agents, hooks) across four cited operator playbooks (backlink gap audit, 100-day GEO ranking roadmap, 4-layer LinkedIn outreach OS, 6-tool minimum viable cold-email stack) into one operator surface running from a single terminal. Cited results $1.8M+ revenue from AI-search organic, 1,700% organic visibility lift, 0 to 2,100 daily clicks against Duolingo-scale competitors, 1M+ cold emails per month from a 6-tool stack. The stack-anchor cluster carries 19,300 monthly US searches across 4 PASS keywords on LIVE DataForSEO 2026-05-20 (claude code skills 9,900, mcp 3,600, agents 2,900, hooks 2,900) at blended KD 25.

Claude Code skills are packaged prompt-plus-workflow artifacts that live in your local .claude/skills folder and tell Claude how to solve a class of problems. Each skill is a markdown-plus-prompt artifact with three load-bearing fields: SDK reference (what tools and MCP servers the skill needs), positive outcome definition (what success looks like), and input shape (what the operator hands the skill at invocation time). The canonical reference for the skill format lives at the Anthropic agent skills repo and the Claude API agent skills docs. Skills are the load-bearing entry point because they package the recurring SEO motions (keyword research, backlink gap audit, content brief generation, technical audit, GEO sprint design, outreach personalization) so the same prompt does not get rewritten on every campaign. Composability is the moat: the same skill can call any MCP server, dispatch any subagent, and fire any hook without rewrite.

The cluster around claude code skills on LIVE DataForSEO 2026-05-20 carries 9,900 monthly US searches at KD 32 with LOW competition. The four operator playbooks documented in this post (backlink gap audit, 100-day GEO ranking roadmap, 4-layer LinkedIn outreach OS, 6-tool cold-email MVS) each ship as a Claude Code skill in the FORKOFF stack today. The recurring pattern: one skill, one MCP source, one subagent, one hook. Compose them and the entire SEO motion runs from a single terminal.

Claude Code MCP servers in the FORKOFF stack

The MCP layer is where Claude Code reaches outside its own runtime. Each MCP server (Model Context Protocol server) is an external process that provides a single capability surface: a data source, an API wrapper, a file system bridge, a browser surface. The Model Context Protocol specification defines the runtime contract; the skill declares the workflow, the MCP servers provide the data. The cluster around claude code mcp on LIVE DataForSEO 2026-05-20 carries 3,600 monthly US searches at KD 27 with LOW competition.

The FORKOFF default Claude Code MCP stack runs six servers. Ahrefs MCP (or DataForSEO MCP as the cheaper substitute) provides keyword volume, KD, SERP, and backlink data. DataForSEO MCP is the cost wedge here: roughly $0.025 per SERP pull is 30 to 40 times cheaper than per-query Ahrefs rates at the same depth. Firecrawl MCP provides web fetch and enrichment, which doubles as the technical-SEO crawler when paired with a hook that fires on URL changes. Google Search Console MCP provides query, indexing, and click data, closing the loop from ranking to traffic. Reddit data infrastructure provides thread-level demand signals across r/AskSEO, r/SEO, r/aeo, r/ClaudeAI, r/aiagents, which is where operator-receipt content originates before it surfaces in Google search. Unipile MCP handles LinkedIn, WhatsApp, and email outreach as the channel layer for the 4-layer LinkedIn OS documented below. Filesystem MCP persists local artifacts (skill outputs, audit ledgers, brief drafts, sequence templates) so the stack runs offline-first.

The composition principle: each MCP server provides one capability surface, the skill layer composes them. A backlink gap audit calls Ahrefs MCP (or DataForSEO MCP) plus Firecrawl plus Filesystem in one workflow; the skill bundles the orchestration and writes the tier-counted output to disk. The point of the layered architecture is replaceability: each layer does one thing well, so when Claude Code absorbs another layer (or a cheaper MCP shows up), you swap it in without breaking the rest of the stack.

What gets replaced (and what survives)

@nick_zv runs his entire SEO operation through Claude Code. Here is the explicit before-and-after he posted on X on 2026-05-09:

Out:

• Ahrefs the dashboard for keyword research
• Human prospecting for links
• Surfer for content optimization
• Screaming Frog for technical SEO
• 2 to 3 content writers for blogs

In:

• Claude Code plus API keys for everything

The thesis is not that the SEO category dies. It is that the SaaS subscription layer collapses into one agent that orchestrates the data sources directly. Ahrefs the data lake survives. Ahrefs the dashboard goes away. Surfer, Screaming Frog, and the 2-to-3-writer brief team are absorbed into per-task skills that compose MCP data sources, subagents, and hooks into one operator workflow.

r/ClaudeAI• u/

What are Claude Skills really?

Claude Code agents that compound

The agents layer is where parallel reasoning happens. Claude Code supports both agents (LLM-driven subprocesses that handle a task end-to-end and report back) and subagents (dispatched-by-the-main-agent worker LLMs that run in parallel and merge results). The cluster around claude code agents on LIVE DataForSEO 2026-05-20 carries 2,900 monthly US searches at KD 22 with LOW competition; claude code subagents carries KD 18 on null volume as a first-mover claim play.

The agents that compound for SEO are the ones that run recurring research in parallel. A content brief agent dispatches three subagents simultaneously: one to summarize the top-10 SERP, one to pull the PAA + related queries cluster, one to scan the relevant Reddit and X threads for operator-receipt content. The main agent then merges the three streams into a brief that already carries the structural fixes the writer would have surfaced manually. The same pattern runs for backlink gap audits (one subagent per top-10 competitor, all in parallel), for technical SEO crawls (one subagent per site section), and for outreach personalization (one subagent per prospect). The pattern aligns with Princeton's GEO citation research (KDD 2024) showing that statistics-density and authoritative-source signals lift AI-search citation rates by 41% and 115% respectively when added to a content piece.

The 10-minute backlink gap audit is the canonical proof of the agents-compound thesis. Every SEO has done this exercise; it takes 1 to 2 days manually. Run from inside Claude Code with the Ahrefs MCP (or Chrome-driven Semrush) and a subagent per competitor, the same audit takes 10 to 15 minutes. The exact Alentra Marketing prompt:

You are my senior SEO analyst.

Access Ahrefs in Chrome (or Ahrefs MCP if available).

Go to Keywords Explorer for keyword: <KW>
e.g. "roof replacement Austin"

Run a Backlink Gap analysis between my domain <MY_DOMAIN>
and the top-10 organic results for <KW>.

For the top-10 organic competitors:
  - Skip YouTube videos and irrelevant sites (intent mismatch)
  - For each competitor, drill into referring-domain backlink list
  - Apply filters:
      dofollow only
      one-link-per-domain
      referring-domain DR >= 40
      referring-domain monthly organic traffic >= 2,000
  - Sort by DR descending
  - Categorize links into DR tiers:
      DR 70+
      DR 50-69
      DR 30-49
      DR 0-29 (flag as PBN/spam if applicable)

Output the aggregate metrics per tier across the top-10 competitors:
  - Average count per tier
  - Median count per tier
  - Recommended target count per tier to rank top-5

Highlight any competitor with high spam score or black-hat-network signal.

The output reframes the entire conversation with the SEO team. "We need 2,000 backlinks" becomes "we need 12 DR70+ links, 18 DR50-69, and 24 DR30-49 to rank top-5 for <KW>". One is a budget headache. The other is a scoped sprint. The canonical "high-quality backlink" gate is two filters, both required: referring domain DR >= 40, and referring domain receives >= 2,000 monthly organic search traffic from Google. Apply dofollow plus one-link-per-domain on top. A typical 2,000-link competitor profile collapses to 30 to 50 real links after this filter. Rank against that real number, not the inflated count. A useful weighting rule from the same source: 1 DR70+ link is worth roughly 5 DR30-49 links in most niches.

Claude Code hooks for SEO automation

The hooks layer is where deterministic, code-level interceptors fire on Claude Code events. The cluster around claude code hooks on LIVE DataForSEO 2026-05-20 carries 2,900 monthly US searches at KD 19 with LOW competition. The cluster around claude code automation carries KD 9 (the lowest in the stack) on null volume as a first-mover claim play.

The hook types in Claude Code today: pre-tool-use (fires before a tool call), post-tool-use (fires after), on-stop (fires when the agent ends a session), on-subagent-start, on-subagent-stop. Hooks are deterministic Python or bash that the runtime invokes; they are not LLM-driven. For SEO automation, hooks are the right primitive for quality gates and ship triggers. A pre-tool-use hook on a git commit call runs an llms.txt validator and blocks the commit if the file is malformed. A post-tool-use hook on a content write runs a Princeton GEO citation density check and surfaces a warning if the article ships with under 3 dated statistics. An on-stop hook runs the IndexNow ping + GSC URL inspection after every blog ship so the index propagation closes without manual intervention.

The compounding pattern: hooks ship structural fixes without human triage. The agentic-seo CLI scorecard the FORKOFF audit ledger documents (Discovery, Content Structure, Token Economics, Capability Signaling, UX Bridge categories) is hook-deliverable end to end. A pre-deploy hook runs the CLI, gates the deploy on a passing score, and writes the failed-check log to the audit ledger. The deploy either passes the gate or kicks back a remediation task; either way no human runs the audit by hand.

r/aiagents• u/

I replaced my entire SEO workflow with a 4-agent pipeline, 3 months of production

The 100-day GEO ranking roadmap (run as a 4-layer Claude Code sprint)

Trailblazer Marketing published a 3-phase roadmap to rank on ChatGPT in 100 days. Cited results: Musicfy at 692K clicks and $1M+ revenue, a language-learning brand from 0 to 2,100 daily clicks against Duolingo, and an aggregate $30.52M in client outcomes. The roadmap compresses end to end into the Claude Code stack as a single skill that orchestrates three subagents per phase.

Days 1 to 30, solution validation. Goal, find the 3 to 5 winning angles, not write 50 articles. The Claude Code skill orchestrates three subagents in parallel. Subagent A extracts pain points from the last 10 sales calls (Fathom or Fireflies transcripts via filesystem MCP), Reddit threads via site:reddit.com inurl:comments "<your topic>" plus the Reddit data infrastructure MCP, X competitor mentions, and support tickets. Subagent B ranks the dump by frequency and groups themes. Subagent C drafts 10 to 15 answer-first pieces, each structured as 50 words direct answer to a head question, then 100 to 200 words of why-and-how, then comparison charts and FAQ. The skill ships the drafts to a content queue and tracks time-on-page, session length, and site clicks. By day 30 you have 3 to 5 clear winners surfaced by the agent.

Days 31 to 70, programmatic coverage. LLMs pull from patterns across many sources. A partial coverage profile reads as a partial source, not an authority. For each of the 3 to 5 winning angles, fan out into 5 dimensions: definitions, comparisons, use cases, common mistakes, advanced tactics. Example, "LLM SEO" expands to "what is LLM SEO", "LLM SEO vs traditional SEO", "LLM SEO for SaaS", "common LLM SEO mistakes", "LLM SEO case studies". The Claude Code skill dispatches one subagent per dimension per winning angle, runs all the briefs in parallel, and ships them to the content queue. Build pillar-plus-cluster, not standalone pieces. Keep the same definitions, frameworks, and terminology across every piece. The goal is topic surface ownership: every variation of every question, you are the answer.

Days 71 to 100, entity velocity. Even with full topic coverage, AI search filters on "who should I trust?". The signal is, is this person mentioned elsewhere? Do multiple sources reference them? Is the name tied to this topic repeatedly? Brands with strong sites get ignored in AI answers because they are only visible on their own site. Three Claude Code agents close that gap. Agent A drafts guest-post pitches, podcast invites, founder-interview asks, and partner-platform case-study submissions. Agent B creates referenceable assets, original frameworks (named, citable), data points, contrarian takes. AI prefers original wording. Agent C runs entity-mention tracking across the surfaces from Phase 1 to verify the entity velocity loop is closing.

The 4-layer LinkedIn outreach OS

@MichLieben documented a 4-layer Claude Code LinkedIn outreach OS built with Othmane Khadri (Earleads founder) that runs an entire campaign from one prompt. The OS maps 1-to-1 onto the Claude Code stack layers documented above.

The 4 layers

1. Input. The campaign is the query, "scrape engagers of post X, qualify against ICP, draft personalized outreach, send 10". One sentence per major step, written like a senior SDR brief. This is the skill invocation surface.
2. CLAUDE.md at repo root. The constitution. Examples, default to plan mode, never send a message without showing the draft first, exclude existing customers, cap LinkedIn connection requests at 25 per day per inbox. CLAUDE.md is the per-repo memory layer that scopes how every skill runs.
3. Skills. One container per action. Scrape engagers, qualify a lead, push to a unified database, send an outreach message. Each skill bundles three things, SDK reference, positive outcome definition, input shape.
4. memory.md. ICP, value prop, outreach hypotheses tested, and what actually worked. Travels with you across campaigns. memory.md is the cross-campaign persistence layer that compounds across runs.

External environments plug in via Unipile (LinkedIn, WhatsApp, email), Apify (scraping), Firecrawl (web fetch and enrichment), Reddit data infrastructure (thread-level demand signals). Each external environment is wired in as an MCP server, which means the same OS works for LinkedIn this week and Twitter next week without rewriting the skills layer.

The 7-gate qualification pipeline kills bad leads as cheaply as possible before any expensive call. Each gate is a subagent that runs in parallel where possible. A small handful of leads survive all 7 gates and get the personalized message. The rest die quietly. The cost of a bad message in your prospect's inbox is much higher than the cost of dropping a borderline lead.

The 6-tool minimum viable cold-email stack

If you are starting from zero today, @coldemailchris documented the 80/20 reduction of his 36-tool 1M-emails-per-month stack on X 2026-05-09. The 6-tool MVS is the floor; the full 36-tool stack adds layers for multi-channel (HeyReach, Trigify), AI orchestration (n8n, cheap classification models), and ABM video (Tella). The Claude Code role in the MVS is layer-7 reasoning: ICP modeling, signal scoring, message generation. Each external tool is wired in as an MCP server where possible (Ocean.io and Prospeo.io via their public APIs, ScaledMail via Unipile, EmailBison via webhook), so the same orchestration skill works as Claude Code absorbs more capability layer by layer.

The point of the layered architecture: each tool does one thing well, and replacement is layer-by-layer instead of full-stack rip-out. When Claude Code absorbs another layer, you swap it in without breaking the rest. Cited result, 1M+ cold emails per month from this floor stack at roughly $500 to $800 per month total, which is an order of magnitude more output than the full SaaS-only stack at the same total cost.

The full Claude Code SEO motion, where the 4 layers meet the 4 playbooks

The full Claude Code SEO motion is what happens when the 4 stack layers (skills, MCP, agents, hooks) compose across the 4 cited operator playbooks (backlink gap audit, 100-day GEO ranking roadmap, 4-layer LinkedIn outreach OS, 6-tool cold-email MVS) inside one repo. The pivot from claude code seo (50 monthly searches, null KD on LIVE DataForSEO 2026-05-20) to the stack-anchor cluster (19,300 monthly searches at blended KD 25) reframes the conversation. The reader who searches claude code skills does not want a generic Claude Code SEO essay; they want the canonical four-playbook stack composed inside a single CLAUDE.md plus memory.md repo, with each skill calling the right MCP, dispatching the right subagent, and firing the right hook.

That is what the four operator playbooks above describe services-as-software: an outcome that used to require an agency now runs from one operator inside one terminal. This is the FORKOFF agency thesis exactly. We do not sell access to a tool. We sell the outcome (rankings, qualified replies, traffic) and run the Claude Code stack internally. What that looks like in practice on a current engagement, backlink gap delivered same-day instead of a 1-to-2-day SEO-team turnaround; GEO playbook (3-phase 100-day) running as a single roadmap with weekly check-ins; LinkedIn outbound through the 4-layer Claude Code OS so personalization stops being a junior task; cold email at 1M+ scale through the 7-layer stack with Claude doing the layer-7 reasoning. The pricing is on outcome, not seat or tool subscription. That is the only billing model that survives when the SaaS dashboard layer collapses.

r/SEO• u/

Anyone using Claude Code for technical SEO?

The bottom line

The Claude Code SEO stack in 2026 is four layers composed across four operator playbooks. Skills package the recurring SEO workflows so the same prompt is not rewritten every campaign. MCP servers provide live data so the agent reaches outside its runtime. Agents and subagents reason in parallel so a 1-to-2-day backlink gap collapses to 10 to 15 minutes. Hooks ship structural fixes deterministically so the audit-ledger closes without human triage. The 4 PASS keywords in the stack-anchor cluster (claude code skills 9,900, mcp 3,600, agents 2,900, hooks 2,900) carry 19,300 monthly US searches at blended KD 25 on LIVE DataForSEO 2026-05-20.

For SEO and outreach teams deciding between a full SaaS stack and the Claude Code composition: the decision is a 3-axis framework (recurring-motion frequency, data-source reach, automation appetite). High-frequency recurring motions (weekly backlink gap, monthly content brief refresh, daily outreach personalization) collapse into skills first. Wide-reach data needs (Ahrefs + DataForSEO + Firecrawl + GSC + Reddit infrastructure) plug in as MCP servers. Compound reasoning across many sources runs as parallel subagents. Quality gates and ship triggers fire as hooks. The whole stack compounds in CLAUDE.md plus memory.md so the next campaign starts with everything the last campaign learned.

For protocol, infrastructure, and consumer-app teams running outcome-priced AI-search optimization, the FORKOFF service surface ships the full Claude Code stack as a single engagement. The two productized lanes are /services/ai-search-optimization (skills + agents for the search-and-discovery surface) and /services/answer-engine-optimization (hooks + MCP for the AI Overview citation surface). The 4-week sprint installs the skills repo, wires the MCP stack, builds the agent compositions, and lays in the deterministic hook layer. Three sequenced moves to start this week, even before the FORKOFF engagement: run the backlink gap recipe on your top 5 keywords using the exact Alentra prompt above; pick 3 winning angles from your last 10 sales calls plus Reddit search and draft an answer-first piece for each in the 50-words-direct-answer plus 100-to-200-words-why structure; audit your CLAUDE.md and memory.md if you already run Claude Code, since the OS layer is the thing teams skip and it is the layer that compounds across every future campaign.

The next 24 months are the highest-leverage window to lock the Claude Code SEO stack before the broader market closes the gap. AI-chat buyer routing keeps shifting share away from search, which lifts the value of multi-layer agent stacks that produce founder-attributed content compounding across surfaces. The 4-layer stack (skills, MCP, agents, hooks) running across the 4 operator playbooks (backlink gap, GEO 100-day, LinkedIn 4-layer, cold email 6-tool) is the only operating system that captures both the search-and-discovery surface and the multi-month brand-surface compounding. For the deep-dive companion reads: /blog/ecosystem/agentic-seo-forkoff-audit-2026 carries the 14-site agentic-SEO audit and the 10-check scorecard; /blog/founder-growth/agentic-seo-explained-addyosmani-toolkit-2026 walks through the agentic-seo CLI from Addy Osmani; /blog/founder-growth/agent-ready-site-audit-2026 is the per-site agent-ready scorecard. Pick the skill set, wire the MCP servers, dispatch the agents, fire the hooks, and let the stack run.