SEO Audit
SEO Audit skill from Corey Haines’ Marketing Skills collection.
Overview
SEO Audit is a growth/marketing skill from Corey Haines’ Marketing Skills collection (github.com/coreyhaines31/marketingskills). SEO Audit skill from Corey Haines’ Marketing Skills collection. The skill is structured around practical workflows—covering Initial Assessment, Audit Framework, Technical SEO Audit, International SEO & Localization, On-Page SEO Audit, Content Quality Assessment—so Claude can move from context gathering to concrete artifacts (briefs, copy, checklists, or audit reports) instead of generic advice. Pair it with related skills in the same collection: `ai-seo`, `schema`, `site-architecture`, `content-strategy`.
Work with LimeDock
Using this skill? LimeDock can wire it into a durable automation you own.
Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.
We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.
Link
Installation guide
Option A — Install just this skill (recommended)
npx skills add coreyhaines31/marketingskills --skill seo-auditOption B — Install the full Marketing Skills collection
npx skills add coreyhaines31/marketingskillsThat unlocks related skills like `cro`, `copywriting`, `emails`, `ads`, and `seo-audit`.
Option C — Manual install (Claude Code)
git clone https://github.com/coreyhaines31/marketingskills.git /tmp/marketingskills
mkdir -p ~/.claude/skills
cp -R /tmp/marketingskills/skills/seo-audit ~/.claude/skills/seo-auditClaude.ai
Customize → Skills → Upload the `seo-audit` folder as a zip / `SKILL.md` → enable the skill.
Always skim `SKILL.md` before first use so you know its triggers and related skills.
How to use it
1. **Trigger it with seo audit language** — mention the job by name or ask for the deliverable this skill owns. 2. **Share product context up front** — ICP, offer, URL, constraints, and any metrics. If `.agents/product-marketing.md` (or `.claude/product-marketing.md`) exists, the skill will read it first. 3. **Let it run the assessment** — answer clarifying questions before asking for final copy/strategy. 4. **Request a concrete artifact** — brief, audit, page outline, sequence, scorecard, or launch checklist. 5. **Close the loop** — feed performance data back so the next iteration compounds.
**Typical sections it covers:** Initial Assessment, Audit Framework, Technical SEO Audit, International SEO & Localization, On-Page SEO Audit, Content Quality Assessment, Common Issues by Site Type, Output Format.
If Claude does not auto-select it, say: “Use the SEO Audit skill (`seo-audit`)…”.
Example prompts
- “Use the SEO Audit skill to assess our current state and produce a prioritized action plan.”
- “Walk me through how SEO Audit would approach this step by step, then execute on our product.”
- “Create a reusable checklist and prompt template for running SEO Audit monthly.”
- “Review my draft plan and improve it with SEO Audit. Call out assumptions and risks.”
Use cases and examples
- Technical SEO health audit with prioritized fixes
- On-page SEO pass for commercial landing pages
- Internal linking and cannibalization review
- Schema and indexation checklist before a migration
- Content quality audit against search intent
- Competitor SERP gap snapshot for a keyword cluster
Prerequisites
- Claude Code, Claude.ai Skills, or another Agent Skills–compatible host
- Product/brand context (ICP, offer, URLs, constraints) for grounded outputs
- Optional: `.agents/product-marketing.md` or `.claude/product-marketing.md` in the repo
- Permission to install third-party skills — audit SKILL.md first
- Optional: analytics or ad-platform access when the task needs real performance data
Tips
- Keep triggers specific so SEO Audit fires only when that job is requested (avoids context tax).
- Load product-marketing context (ICP, voice, offer) before asking for final copy or strategy.
- Prefer one sharp deliverable per turn—brief, audit, or draft—then iterate with data.
- Audit `SKILL.md` and any scripts before production use; treat community skills as code.
- Pair with `ai-seo` and `schema` when the workflow spans channels.