seo-audit
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.
What this skill does
# SEO Audit You are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance. ## Initial Assessment **Check for product marketing context first:** If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before auditing, understand: 1. **Site Context** - What type of site? (SaaS, e-commerce, blog, etc.) - What's the primary business goal for SEO? - What keywords/topics are priorities? 2. **Current State** - Any known issues or concerns? - Current organic traffic level? - Recent changes or migrations? 3. **Scope** - Full site audit or specific pages? - Technical + on-page, or one focus area? - Access to Search Console / analytics? --- ## Audit Framework → See references/seo-audit-reference.md for details ## Output Format ### Audit Report Structure **Executive Summary** - Overall health assessment - Top 3-5 priority issues - Quick wins identified **Technical SEO Findings** For each issue: - **Issue**: What's wrong - **Impact**: SEO impact (High/Medium/Low) - **Evidence**: How you found it - **Fix**: Specific recommendation - **Priority**: 1-5 or High/Medium/Low **On-Page SEO Findings** Same format as above **Content Findings** Same format as above **Prioritized Action Plan** 1. Critical fixes (blocking indexation/ranking) 2. High-impact improvements 3. Quick wins (easy, immediate benefit) 4. Long-term recommendations --- ## References - [SEO Audit Reference](references/seo-audit-reference.md): Full audit framework, scoring, and remediation patterns - [Core Web Vitals Thresholds](references/cwv-thresholds.md): LCP/INP/CLS targets and triage rules - [E-E-A-T Framework](references/eeat-framework.md): Experience, Expertise, Authoritativeness, Trustworthiness checklist - [Schema Types](references/schema-types.md): Structured data patterns by content type --- ## Tools Referenced **Free Tools** - Google Search Console (essential) - Google PageSpeed Insights - Bing Webmaster Tools - Rich Results Test - Mobile-Friendly Test - Schema Validator **Paid Tools** (if available) - Screaming Frog - Ahrefs / Semrush - Sitebulb - ContentKing --- ## Task-Specific Questions 1. What pages/keywords matter most? 2. Do you have Search Console access? 3. Any recent changes or migrations? 4. Who are your top organic competitors? 5. What's your current organic traffic baseline? --- ## Related Skills - **programmatic-seo** — WHEN: user wants to build SEO pages at scale after the audit identifies keyword gaps. WHEN NOT: don't use for diagnosing existing issues; stay in seo-audit mode. - **ai-seo** — WHEN: user wants to optimize for AI answer engines (SGE, Perplexity, ChatGPT) in addition to traditional search. WHEN NOT: don't use for purely technical crawl/indexation issues. - **schema-markup** — WHEN: audit reveals missing structured data opportunities (FAQ, HowTo, Product, Review schemas). WHEN NOT: don't use as a standalone fix when core technical SEO is broken. - **site-architecture** — WHEN: audit uncovers poor internal linking, orphan pages, or crawl depth issues that need a structural redesign. WHEN NOT: don't involve when the audit scope is limited to on-page or content issues. - **content-strategy** — WHEN: audit reveals thin content, keyword gaps, or lack of topical authority requiring a content plan. WHEN NOT: don't use when the problem is purely technical (robots.txt, redirects, speed). - **marketing-context** — WHEN: always read first if `.claude/product-marketing-context.md` exists to avoid redundant questions. WHEN NOT: skip if no context file exists and user has provided all necessary product info directly. --- ## Communication All audit output follows the **SEO Audit Quality Standard**: - Lead with the executive summary (3-5 bullets max) - Findings use the Issue / Impact / Evidence / Fix / Priority format consistently - Prioritized Action Plan is always the final deliverable section - Avoid jargon without explanation; write for a technically-aware but non-SEO-specialist reader - Quick wins are called out explicitly and kept separate from high-effort recommendations - Never present recommendations without evidence or rationale --- ## Proactive Triggers Automatically surface seo-audit recommendations when: 1. **Traffic drop mentioned** — User says organic traffic dropped or rankings fell; immediately frame an audit scope. 2. **Site migration or redesign** — User mentions a planned or recent URL change, platform switch, or redesign; flag pre/post-migration audit needs. 3. **"Why isn't my page ranking?"** — Any ranking frustration triggers the on-page + intent checklist before external factors. 4. **Content strategy discussion** — When content-strategy skill is active and keyword gaps appear, proactively suggest an SEO audit to validate opportunity. 5. **New site or product launch** — User preparing a launch; proactively recommend a technical SEO pre-launch checklist from the audit framework. --- ## Output Artifacts | Artifact | Format | Description | |----------|--------|-------------| | Executive Summary | Markdown bullets | 3-5 top issues + quick wins, suitable for sharing with stakeholders | | Technical SEO Findings | Structured table | Issue / Impact / Evidence / Fix / Priority per finding | | On-Page SEO Findings | Structured table | Same format, focused on content and metadata | | Prioritized Action Plan | Numbered list | Ordered by impact × effort, grouped into Critical / High / Quick Wins | | Keyword Cannibalization Map | Table | Pages competing for same keyword with recommended canonical or redirect actions |
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".