Catalog
coreyhaines31/seo-audit

coreyhaines31

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," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.

global
version:1.1.0
0installs0uses~2.7k
v1.1Saved Apr 20, 2026

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 .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), 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

Schema Markup Detection Limitation

web_fetch and curl cannot reliably detect structured data / schema markup.

Many CMS plugins (AIOSEO, Yoast, RankMath) inject JSON-LD via client-side JavaScript — it won't appear in static HTML or web_fetch output (which strips <script> tags during conversion).

To accurately check for schema markup, use one of these methods:

  1. Browser tool — render the page and run: document.querySelectorAll('script[type="application/ld+json"]')
  2. Google Rich Results Testhttps://search.google.com/test/rich-results
  3. Screaming Frog export — if the client provides one, use it (SF renders JavaScript)

Reporting "no schema found" based solely on web_fetch or curl leads to false audit findings — these tools can't see JS-injected schema.

Priority Order

  1. Crawlability & Indexation (can Google find and index it?)
  2. Technical Foundations (is the site fast and functional?)
  3. On-Page Optimization (is content optimized?)
  4. Content Quality (does it deserve to rank?)
  5. Authority & Links (does it have credibility?)

Technical SEO Audit

Crawlability

Robots.txt

  • Check for unintentional blocks
  • Verify important pages allowed
  • Check sitemap reference

XML Sitemap

  • Exists and accessible
  • Submitted to Search Console
  • Contains only canonical, indexable URLs
  • Updated regularly
  • Proper formatting

Site Architecture

  • Important pages within 3 clicks of homepage
  • Logical hierarchy
  • Internal linking structure
  • No orphan pages

Crawl Budget Issues (for large sites)

  • Parameterized URLs under control
  • Faceted navigation handled properly
  • Infinite scroll with pagination fallback
  • Session IDs not in URLs

Indexation

Index Status

  • site:domain.com check
  • Search Console coverage report
  • Compare indexed vs. expected

Indexation Issues

  • Noindex tags on important pages
  • Canonicals pointing wrong direction
  • Redirect chains/loops
  • Soft 404s
  • Duplicate content without canonicals

Canonicalization

  • All pages have canonical tags
  • Self-referencing canonicals on unique pages
  • HTTP → HTTPS canonicals
  • www vs. non-www consistency
  • Trailing slash consistency

Site Speed & Core Web Vitals

Core Web Vitals

  • LCP (Largest Contentful Paint): < 2.5s
  • INP (Interaction to Next Paint): < 200ms
  • CLS (Cumulative Layout Shift): < 0.1

Speed Factors

  • Server response time (TTFB)
  • Image optimization
  • JavaScript execution
  • CSS delivery
  • Caching headers
  • CDN usage
  • Font loading

Tools

  • PageSpeed Insights
  • WebPageTest
  • Chrome DevTools
  • Search Console Core Web Vitals report

Mobile-Friendliness

  • Responsive design (not separate m. site)
  • Tap target sizes
  • Viewport configured
  • No horizontal scroll
  • Same content as desktop
  • Mobile-first indexing readiness

Security & HTTPS

  • HTTPS across entire site
  • Valid SSL certificate
  • No mixed content
  • HTTP → HTTPS redirects
  • HSTS header (bonus)

URL Structure

  • Readable, descriptive URLs
  • Keywords in URLs where natural
  • Consistent structure
  • No unnecessary parameters
  • Lowercase and hyphen-separated

On-Page SEO Audit

Title Tags

Check for:

  • Unique titles for each page
  • Primary keyword near beginning
  • 50-60 characters (visible in SERP)
  • Compelling and click-worthy
  • No brand name placement (SERPs include brand name above title already)

Common issues:

  • Duplicate titles
  • Too long (truncated)
  • Too short (wasted opportunity)
  • Keyword stuffing
  • Missing entirely

Meta Descriptions

Check for:

  • Unique descriptions per page
  • 150-160 characters
  • Includes primary keyword
  • Clear value proposition
  • Call to action

Common issues:

  • Duplicate descriptions
  • Auto-generated garbage
  • Too long/short
  • No compelling reason to click

Heading Structure

Check for:

  • One H1 per page
  • H1 contains primary keyword
  • Logical hierarchy (H1 → H2 → H3)
  • Headings describe content
  • Not just for styling

Common issues:

  • Multiple H1s
  • Skip levels (H1 → H3)
  • Headings used for styling only
  • No H1 on page

Content Optimization

Primary Page Content

  • Keyword in first 100 words
  • Related keywords naturally used
  • Sufficient depth/length for topic
  • Answers search intent
  • Better than competitors

Thin Content Issues

  • Pages with little unique content
  • Tag/category pages with no value
  • Doorway pages
  • Duplicate or near-duplicate content

Image Optimization

Check for:

  • Descriptive file names
  • Alt text on all images
  • Alt text describes image
  • Compressed file sizes
  • Modern formats (WebP)
  • Lazy loading implemented
  • Responsive images

Internal Linking

Check for:

  • Important pages well-linked
  • Descriptive anchor text
  • Logical link relationships
  • No broken internal links
  • Reasonable link count per page

Common issues:

  • Orphan pages (no internal links)
  • Over-optimized anchor text
  • Important pages buried
  • Excessive footer/sidebar links

Keyword Targeting

Per Page

  • Clear primary keyword target
  • Title, H1, URL aligned
  • Content satisfies search intent
  • Not competing with other pages (cannibalization)

Site-Wide

  • Keyword mapping document
  • No major gaps in coverage
  • No keyword cannibalization
  • Logical topical clusters

Content Quality Assessment

E-E-A-T Signals

Experience

  • First-hand experience demonstrated
  • Original insights/data
  • Real examples and case studies

Expertise

  • Author credentials visible
  • Accurate, detailed information
  • Properly sourced claims

Authoritativeness

  • Recognized in the space
  • Cited by others
  • Industry credentials

Trustworthiness

  • Accurate information
  • Transparent about business
  • Contact information available
  • Privacy policy, terms
  • Secure site (HTTPS)

Content Depth

  • Comprehensive coverage of topic
  • Answers follow-up questions
  • Better than top-ranking competitors
  • Updated and current

User Engagement Signals

  • Time on page
  • Bounce rate in context
  • Pages per session
  • Return visits

Common Issues by Site Type

SaaS/Product Sites

  • Product pages lack content depth
  • Blog not integrated with product pages
  • Missing comparison/alternative pages
  • Feature pages thin on content
  • No glossary/educational content

E-commerce

  • Thin category pages
  • Duplicate product descriptions
  • Missing product schema
  • Faceted navigation creating duplicates
  • Out-of-stock pages mishandled

Content/Blog Sites

  • Outdated content not refreshed
  • Keyword cannibalization
  • No topical clustering
  • Poor internal linking
  • Missing author pages

Local Business

  • Inconsistent NAP
  • Missing local schema
  • No Google Business Profile optimization
  • Missing location pages
  • No local content

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)
  • For AI search optimization (AEO, GEO, LLMO, AI Overviews), see the ai-seo skill

Tools Referenced

Free Tools

  • Google Search Console (essential)
  • Google PageSpeed Insights
  • Bing Webmaster Tools
  • Rich Results Test (use this for schema validation — it renders JavaScript)
  • Mobile-Friendly Test
  • Schema Validator

Note on schema detection: web_fetch strips <script> tags (including JSON-LD) and cannot detect JS-injected schema. Use the browser tool, Rich Results Test, or Screaming Frog instead — they render JavaScript and capture dynamically-injected markup. See the Schema Markup Detection Limitation section above.

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?

  • ai-seo: For optimizing content for AI search engines (AEO, GEO, LLMO)
  • programmatic-seo: For building SEO pages at scale
  • site-architecture: For page hierarchy, navigation design, and URL structure
  • schema-markup: For implementing structured data
  • page-cro: For optimizing pages for conversion (not just ranking)
  • analytics-tracking: For measuring SEO performance
Files3
3 files · 17.0 KB

Select a file to preview

Overall Score

87/100

Grade

A

Excellent

Safety

92

Quality

88

Clarity

85

Completeness

82

Summary

An SEO audit skill that guides agents through comprehensive website optimization analysis. It provides a structured framework for evaluating crawlability, indexation, technical SEO, on-page elements, and content quality, then synthesizing findings into prioritized action plans. The skill emphasizes context-aware assessment (reading product-marketing-context.md first) and includes important limitations (e.g., schema markup detection via web_fetch).

Detected Capabilities

Crawlability and indexation assessment (robots.txt, sitemap, site architecture)Technical SEO evaluation (speed, Core Web Vitals, mobile-friendliness, HTTPS, URL structure)On-page SEO analysis (title tags, meta descriptions, headings, content optimization, internal linking)Content quality assessment (E-E-A-T signals, depth, user engagement)Site-type-specific frameworks (SaaS, e-commerce, blog, local business)Search Console and Google tools integrationCompetitive benchmarking contextPrioritized action plan generationAI writing pattern detection (via referenced file)

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

seo audittechnical seowhy am i not rankingorganic traffic droppedseo health checkcore web vitalssite migration seokeyword ranking issuesmeta tags reviewindexing problems

Risk Signals

INFO

References to external domains (example.com, search.google.com) are for illustration and tool reference only; no credential access or data exfiltration

SKILL.md: Throughout (examples and tool references)
INFO

Schema markup detection limitation is explicitly documented; skill warns against false negatives from web_fetch and directs to JavaScript-rendering alternatives

SKILL.md: Schema Markup Detection Limitation section
INFO

File reads (product-marketing-context.md) are scoped to project context and are non-destructive

SKILL.md: Initial Assessment section

Referenced Domains

External domains referenced in skill content, detected by static analysis.

example.comsearch.google.com

Use Cases

  • Comprehensive SEO audit of a website to identify ranking barriers
  • Post-migration SEO diagnostic (e.g., WordPress to Next.js)
  • Traffic drop investigation and recovery planning
  • Site-type-specific SEO analysis (SaaS, e-commerce, blog, local business)
  • On-page optimization review for specific keywords
  • Technical SEO assessment for large catalogs or complex architectures

Quality Notes

  • Excellent structure with clear priority ordering (crawlability → technical → on-page → content → authority); agents will follow a logical diagnostic path
  • Comprehensive technical SEO section with specific thresholds (CWV targets, title tag length 50-60 chars, etc.); actionable and measurable
  • Strong acknowledgment of tool limitations (web_fetch cannot detect JS-injected schema); prevents false audit findings
  • Well-documented site-type frameworks (SaaS, e-commerce, blog, local business) with type-specific issues; reduces generic advice
  • Each finding structured with Issue, Impact, Evidence, Fix, and Priority fields; agent output will be consistent and professional
  • References to related skills (ai-seo, schema-markup, programmatic-seo) are appropriate and reduce scope creep
  • Audit report format is well-defined with clear sections (Executive Summary, Technical, On-Page, Content, Action Plan)
  • AI writing detection reference file provides practical guardrails for content quality assessment
  • Task-specific questions guide initial information gathering and scope clarification
  • Minor: Could benefit from explicit examples of how to document findings (e.g., sample output for a specific page type)
Model: claude-haiku-4-5-20251001Analyzed: Apr 20, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

v1.1

Content updated

2026-04-20

Latest
v1.0

No changelog

2026-04-19

Add coreyhaines31/seo-audit to your library

Command Palette

Search for a command to run...