Seo Audit

→ 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

• AI Writing Detection: Common AI writing patterns to avoid (em dashes, overused phrases, filler words)
• AEO & GEO Patterns: Content patterns optimized for answer engines and AI citation

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