seo-pimp

Active router for ALL SEO requests — classifies by SEO domain (technical, local, content, tracking, CRO) and routes to the correct SEO skill. Use when doing any SEO work, audits, rank tracking, schema markup, or content strategy.

Model	Source
sonnet	pack: seo

Full Reference

If the request involves SEO in ANY way — audits, rankings, local SEO, schema markup, link analysis, content strategy, AI visibility, tracking, reviews, or any organic search work — you MUST route through this skill FIRST.

This is not optional. This is not negotiable. You cannot skip this.

SEO Pimp

The orchestration layer for all SEO expertise. Not documentation — an active router. Every SEO request flows through this routing table before any response.

Mandatory Announcement — FIRST OUTPUT before anything else:

┏━ 🔎 seo-pimp ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ [one-line description of request/routing]       ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

No exceptions. Box frame first, then route.

Quick Context

The SEO pack is armadillo’s organic search ecosystem — 15 skills covering technical audits, local SEO, content strategy, link analysis, rank tracking, schema markup, reviews, AI visibility, and workflow orchestrators for client onboarding, monthly retainers, and growth pipelines.

Routing Table

Classify the request. Invoke the matching skill. No response before invocation.

Request Pattern	Skill
Full SEO audit, technical SEO, site-wide issues, crawl errors	`seo-audit`
Quick page-level check, single URL health, spot check	`seo-pulse`
Local SEO, Google Business Profile, NAP consistency, local rankings	`local-seo-audit`
Backlinks, link profile, toxic links, link building	`link-analysis`
Keyword rankings, SERP monitoring, position tracking	`search-rank`
Full site report, client-facing SEO report, executive summary	`site-report`
Schema.org, JSON-LD, structured data, rich results	`schema-markup`
Reviews, reputation management, review responses, star ratings	`review-management`
Content calendar, topic clusters, keyword strategy, editorial planning	`content-strategy`
AI citations, LLM visibility, llms.txt, AI search presence	`ai-visibility`
New client onboarding, initial audit, baseline setup	`master-performance-assessment` (standard mode)
Monthly retainer, ongoing SEO, recurring pulse check	`master-performance-assessment` (quick mode)
CRO iteration, conversion optimization tied to SEO	`cro-sprint` workflow
Local growth pipeline, multi-location SEO, local expansion	`local-growth` workflow
Analytics setup, GA4, GSC, tracking verification	`tracking-foundation` workflow

Cross-Cutting Rules

If a request spans multiple skills, invoke the PRIMARY skill first (closest to the core question)
“Audit my site” is always seo-audit first — never jump to individual checks
Local business questions → local-seo-audit before seo-audit
Content questions with ranking intent → content-strategy first, search-rank for measurement
If unclear which skill fits, default to seo-audit — it covers the broadest diagnostic surface

Chaining Patterns

User Says	Chain
”Audit my site”	`seo-audit` → `site-report`
”Set up a new client”	`master-performance-assessment` (standard) → `tracking-foundation`
”Improve local rankings”	`local-seo-audit` → `local-growth`
”Fix my schema markup”	`schema-markup` → `seo-pulse` (verify after)
“Track my keywords”	`search-rank` → `master-performance-assessment` (quick)
“Help with content strategy”	`content-strategy` → `search-rank` (baseline)
“Get cited by AI tools”	`ai-visibility` → `content-strategy`
”Monthly reporting”	`master-performance-assessment` (quick) → `site-report`

Hard Rules

Never respond about SEO before invoking the target skill
No summarizing, planning to invoke, or explaining what you’re about to do
If unclear, ask ONE clarifying question, then route
The skill’s content has the verified facts — always defer to it
“Help with SEO” is seo-audit territory — NEVER jump straight to tactical fixes