agentleFS
nisarthnisarth/claude-skills-store/skills/seo/seo-audit/SKILL.md

seo-audit

Skill1 starsChanged 7 months agoMITView on GitHub

Run a comprehensive SEO audit covering crawl issues, on-page optimization, PageSpeed performance, technical SEO health, and content gaps. Use when assessing a site's SEO health, onboarding a new client, preparing a quarterly review, or diagnosing a traffic drop. Trigger with "SEO audit", "audit this site", "check SEO health", or "site audit".

185 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use openseo-review-web-content, openseo-release-notes and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JwuthriSkill

    openseo-review-web-content

    Write and review content for the OpenSEO website (web/) — blog posts, guides, feature pages, FAQs. Distills the philosophy for on-brand, useful, accurate content. Use whenever adding or editing user-facing prose in web/content or web/src.

    Also in 5 projects that use this

  • JwuthriSkill

    openseo-release-notes

    Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.

    Also in 6 projects that use this

  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • xfstudioSkill

    micro-saas-launcher

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.

    Also in 5 projects that use this

  • akii-technologies-ltdSkill

    keyword-clustering

    Cluster and organize keywords into topical groups for SEO. Use when the user asks to "cluster keywords", "group keywords", "organize keywords", "keyword mapping", "topic clusters", "keyword grouping", "build a content plan", "pillar pages", "topical authority", "semantic clustering", or pastes a list of keywords.

    Also in 12 projects that use this

  • +4 more from nicepkg
  • +2 more from Jwuthri

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 166 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Robots.txt: Check for overly restrictive directives blocking important pages.

    line 33
  2. Distinctive:

    XML sitemap: Verify existence, accuracy, and submission status.

    line 34
  3. Distinctive:

    Canonical tags: Check for missing, self-referencing, or conflicting canonicals.

    line 37
  4. Distinctive:

    Always check mobile and desktop separately.

    line 141
  5. Distinctive:

    Run PageSpeed tests on representative pages, not just the homepage.

    line 143
  6. Distinctive:

    Check both Google Search Console and third-party tools for a complete picture.

    line 144
  7. Distinctive:

    Document the site's current state as a baseline for measuring future improvements.

    line 147

“Common” is measured: kept by at least 6 in 10 of the 166 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SEO Audit

Perform a comprehensive SEO audit covering crawl health, on-page optimization, page speed, technical infrastructure, and content gaps. Produce a prioritized findings report with actionable fixes.

Workflow

Step 1: Crawl Analysis

Assess how search engines can access and understand the site:

  • Robots.txt: Check for overly restrictive directives blocking important pages.
  • XML sitemap: Verify existence, accuracy, and submission status.
  • Crawl errors: Identify 404s, 5xx errors, redirect chains, and redirect loops.
  • Index coverage: Pages indexed vs. submitted, excluded pages and reasons.
  • Canonical tags: Check for missing, self-referencing, or conflicting canonicals.
  • Hreflang: Validate international targeting markup if applicable.

Step 2: On-Page Optimization

Evaluate page-level SEO elements across key pages:

  • Title tags: Length (50-60 chars), keyword placement, uniqueness, click-worthiness.
  • Meta descriptions: Length (150-160 chars), call to action, uniqueness.
  • Heading hierarchy: Proper H1 usage (one per page), logical H2-H6 nesting.
  • Content quality: Thin pages, duplicate content, keyword stuffing indicators.
  • Image optimization: Alt text presence, file size, modern formats (WebP, AVIF).
  • Internal linking: Orphan pages, link depth, anchor text distribution.

Step 3: Page Speed and Core Web Vitals

Measure performance metrics that impact rankings:

  • Largest Contentful Paint (LCP): Target under 2.5 seconds.
  • Interaction to Next Paint (INP): Target under 200 milliseconds.
  • Cumulative Layout Shift (CLS): Target under 0.1.
  • Time to First Byte (TTFB): Server response time.
  • Resource optimization: Unused JavaScript, render-blocking CSS, image compression.
  • Mobile vs. desktop: Performance gap analysis.

Step 4: Technical SEO Infrastructure

Review the technical foundation:

  • HTTPS: Certificate validity, mixed content issues, HTTP-to-HTTPS redirects.
  • Mobile-friendliness: Responsive design, viewport configuration, tap targets.
  • Structured data: Schema markup presence, validation errors, rich result eligibility.
  • URL structure: Clean URLs, parameter handling, pagination.
  • JavaScript rendering: Client-side rendering issues, dynamic content accessibility.
  • Log file analysis: Crawl budget utilization if server logs are available.

Step 5: Content Gap Analysis

Identify opportunities the site is missing:

  • Competitor comparison: Topics competitors rank for that this site does not cover.
  • Search intent alignment: Pages targeting informational queries with commercial content or vice versa.
  • Content freshness: Pages with outdated information that need updates.
  • Topical authority: Missing subtopics within the site's core themes.

Output Format

## SEO Audit Report: <domain>

**Audit Date**: <date>
**Pages Analyzed**: <count>
**Overall Health Score**: <score>/100

### Executive Summary
<3-4 sentences covering the most impactful findings>

### Critical Issues (fix immediately)
| # | Issue | Pages Affected | Impact | Fix |
|---|-------|---------------|--------|-----|
| 1 | <issue> | <count> | High | <action> |

### Warnings (fix within 30 days)
| # | Issue | Pages Affected | Impact | Fix |
|---|-------|---------------|--------|-----|
| 1 | <issue> | <count> | Medium | <action> |

### Opportunities (prioritize by ROI)
| # | Opportunity | Estimated Impact | Effort |
|---|-------------|-----------------|--------|
| 1 | <opportunity> | <traffic/ranking gain> | <level> |

### Core Web Vitals
| Metric | Mobile | Desktop | Status |
|--------|--------|---------|--------|
| LCP | <time> | <time> | Pass/Fail |
| INP | <time> | <time> | Pass/Fail |
| CLS | <score> | <score> | Pass/Fail |

### Content Gaps
| Topic | Competitor Coverage | Search Volume | Priority |
|-------|-------------------|---------------|----------|
| <topic> | <count> competitors | <volume> | High/Med/Low |

### Prioritized Action Plan
1. <highest impact action with timeline>
2. <second priority>
3. <third priority>

Examples

User: "Run a full SEO audit on example.com" Action: Crawl the site, check on-page elements, run PageSpeed analysis, review technical setup, identify content gaps, produce a prioritized report.

User: "Our organic traffic dropped 20% -- audit the site to find out why" Action: Focus on recent changes (new robots.txt rules, lost pages, Core Web Vitals regressions), compare pre/post traffic data, identify likely causes.

User: "Technical SEO audit only for our staging site before launch" Action: Focus on crawlability, indexation controls, redirects, structured data, and mobile readiness. Skip content gap analysis.

Best Practices

  • Prioritize findings by impact, not by quantity. Ten missing alt tags matter less than one blocked section in robots.txt.
  • Always check mobile and desktop separately. Google uses mobile-first indexing.
  • Correlate technical issues with traffic data when possible to demonstrate business impact.
  • Run PageSpeed tests on representative pages, not just the homepage.
  • Check both Google Search Console and third-party tools for a complete picture.
  • Note which issues are quick wins (high impact, low effort) to build momentum.
  • Schedule regular audits (monthly or quarterly) rather than treating them as one-off events.
  • Document the site's current state as a baseline for measuring future improvements.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.