agentleFS
jazzpujols34jazzpujols34/claude-skills/skills/seo-audit/SKILL.md

seo-audit

Skill0 starsChanged 5 months agoMITView on GitHub

SEO audit and optimization for web projects. Trigger on "SEO", "search ranking", "audit my site", "schema markup", "meta tags", "sitemap", "search console", "organic traffic", or when optimizing a site for search engines. Works for any web project.

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

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 12 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 165 edited versions we read keep these.

  • 12

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before launching a new site or page

    line 14
  2. Distinctive:

    When organic traffic matters (personal site, product landing pages)

    line 15
  3. Distinctive:

    When publishing articles (any blog or publication platform)

    line 16
  4. Distinctive:

    When the user says "SEO", "search ranking", "why isn't my site showing up"

    line 17
  5. Distinctive:

    Run these checks against the target URL:

    line 23
  6. Distinctive:

    Check for and recommend JSON-LD structured data:

    line 68
  7. Distinctive:

    When you don't have paid SEO tools, use these free approaches:

    line 96
  8. Distinctive:

    Check if AI crawlers can access your site:

    line 149
  9. Distinctive:

    If robots.txt blocks these, you're invisible to AI search.

    line 163
  10. Very specific:

    Create a /llms.txt file at your site root — a machine-readable site summary for AI crawlers:

    line 167
  11. Distinctive:

    If you're one person, focus on these high-ROI link strategies:

    line 194
  12. Distinctive:

    New sites take 3-6 months to rank: Don't check daily. Set a monthly review cadence.

    line 262
  13. Distinctive:

    Google Search Console is free and essential: If it's not set up, that's the first fix.

    line 263

“Common” is measured: kept by at least 6 in 10 of the 165 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

Adapted from claude-seo by Daniel Agrici (see README Credits).

Full-site SEO analysis with actionable fixes. From meta tags to structured data to content strategy and AI-search (GEO).

When to Use

  • Before launching a new site or page
  • When organic traffic matters (personal site, product landing pages)
  • When publishing articles (any blog or publication platform)
  • When the user says "SEO", "search ranking", "why isn't my site showing up"

Phase 1: Technical SEO Audit

1.1 Crawlability Checklist

Run these checks against the target URL:

# Check if robots.txt exists and what it allows
curl -s https://[domain]/robots.txt

# Check sitemap
curl -s https://[domain]/sitemap.xml | head -50

# Check response headers
curl -sI https://[domain]/

# Check page load speed (if lighthouse available)
# npx lighthouse https://[domain] --only-categories=performance,seo --output=json
CheckStatusFix
robots.txt exists and doesn't block important pages
sitemap.xml exists and is up-to-date
All pages return 200 (no 404s, no redirect chains)
HTTPS everywhere (no mixed content)
Mobile responsive (viewport meta tag)
Page load < 3s (LCP)
No orphan pages (every page linked from at least one other page)

1.2 On-Page SEO Checklist

For each important page, check:

ElementRuleCurrentFix
<title>50-60 chars, keyword near front
<meta description>150-160 chars, includes CTA
<h1>Exactly one per page, contains primary keyword
<h2>-<h6>Logical hierarchy, no skipped levels
ImagesAll have alt text, compressed, proper format (WebP)
Internal linksKey pages linked from homepage/nav
URL structureShort, readable, hyphens not underscores
Canonical tag<link rel="canonical"> on every page
Open Graphog:title, og:description, og:image set
Twitter Cardtwitter:card, twitter:title, twitter:image set

1.3 Structured Data (Schema Markup)

Check for and recommend JSON-LD structured data:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",  // or Person, Article, Product, etc.
  "name": "...",
  "url": "...",
  ...
}
</script>
Page TypeRecommended SchemaPriority
Homepage (personal site)Person + WebSiteHigh
Blog post / ArticleArticle + BreadcrumbListHigh
Product / pricing pageProduct + OfferHigh
Portfolio / GalleryCreativeWork or ImageGalleryMedium
FAQ pageFAQPageMedium

Validate at: https://search.google.com/test/rich-results

Phase 2: Content SEO

2.1 Keyword Research (Manual Method)

When you don't have paid SEO tools, use these free approaches:

  1. Google autocomplete — Type the topic, note suggestions
  2. "People also ask" — Search the topic, expand all PAA boxes
  3. Related searches — Bottom of Google results page
  4. Google Trends — Compare keyword variants (especially across languages/locales)
  5. Answer the Public (answerthepublic.com) — Question-based keywords

2.2 Content Audit

For existing content, check:

Page/PostPrimary KeywordWord CountLast UpdatedInbound LinksAction
...............Keep/Update/Merge/Delete

Rules:

  • < 300 words → too thin. Expand or merge with another page
  • > 12 months since update → refresh or add "Updated YYYY-MM" note
  • No inbound links → orphan content. Link from other pages or delete
  • Multiple pages targeting same keyword → merge (keyword cannibalization)

2.3 Content Gap Analysis

Compare what you have vs what your audience searches for:

## Keywords We Rank For
(Check Google Search Console → Performance → Queries)

## Keywords We Should Target
1. [keyword] — monthly search volume estimate, difficulty
2. [keyword] — ...

## Content to Create
1. [topic] targeting [keyword] — format: [article/guide/comparison]
2. ...

Phase 3: GEO — AI Search Optimization

Google AI Overviews, ChatGPT, Perplexity are now sending traffic. Optimize for them too.

3.1 Citability Score

AI models cite content that is:

  • Self-contained passages — 134-167 words per key section (optimal for AI citation)
  • Factual and specific — numbers, dates, comparisons (not vague claims)
  • Structured — clear headings, lists, tables (easy to extract)
  • Authoritative — author bio, credentials, sources cited

3.2 AI Crawler Access

Check if AI crawlers can access your site:

# Check robots.txt for AI bot rules
curl -s https://[domain]/robots.txt | grep -i "GPTBot\|ClaudeBot\|PerplexityBot\|ChatGPT\|Google-Extended"
CrawlerUser-AgentRecommendation
Google AI OverviewGoogle-ExtendedAllow (you want AIO citations)
ChatGPTGPTBotAllow (free traffic)
ClaudeClaudeBotAllow
PerplexityPerplexityBotAllow

If robots.txt blocks these, you're invisible to AI search.

3.3 llms.txt

Create a /llms.txt file at your site root — a machine-readable site summary for AI crawlers:

# [Site Name]

> [One-line description]

## Docs
- [Page title](URL): [one-line description]
- [Page title](URL): [one-line description]

## API
- [Endpoint](URL): [description]

3.4 Content Optimization for AI Citations

ElementTraditional SEOAI SEO (GEO)
HeadlinesKeyword-firstQuestion-first ("How to...", "What is...")
Content length1500-2500 words134-167 word self-contained passages within longer content
StructureH2/H3 hierarchyDefinitive statements early in each section
ProofBacklinksNamed sources, specific numbers, comparison tables
FreshnessAnnual updatesDated facts, "as of [date]" markers

Phase 4: Link Building (Solo Builder Edition)

If you're one person, focus on these high-ROI link strategies:

  1. Personal profiles — GitHub, LinkedIn, dev.to, and other publishing platforms. All link back to your site.
  2. Guest posts — Write for communities you're already in (company blogs, developer communities)
  3. Build-in-public content — "How I built X" posts naturally attract links
  4. Open source — Repos link to your site in README/docs
  5. Directories — Product Hunt, Indie Hackers, relevant niche directories

Don't waste time on:

  • Link exchanges / reciprocal linking
  • Buying links
  • Spamming forums
  • PBNs (private blog networks)

Phase 5: Site-Type Recommendations

Personal site / portfolio

  • Schema: Person with sameAs linking to GitHub, LinkedIn
  • Target keywords: your name, your specialty + location, signature topics you publish about
  • Content: guides, project case studies, speaking/presentation links

Product / SaaS landing page

  • Schema: Product + Offer with pricing
  • Target keywords: the job-to-be-done, "[category] generator/tool", problem-phrased queries
  • Content: how-to guides, sample output, pricing comparison vs the manual alternative

Web app / tool

  • Schema: WebApplication + SoftwareApplication
  • Target keywords: "[task] online", "[task] tool", the workflow it replaces
  • Content: featured use cases, how it works, accuracy/quality comparisons

Output Template

# SEO Audit: [domain]

**Date:** YYYY-MM-DD
**Overall Score:** X/10

## Critical Issues (fix immediately)
1. ...
2. ...

## Warnings (fix soon)
1. ...
2. ...

## Opportunities (growth potential)
1. ...
2. ...

## Technical Checklist: X/Y passed
[Table from Phase 1]

## Content Recommendations
[From Phase 2]

## Next Steps (prioritized)
1. [action] — impact: high/med/low, effort: high/med/low
2. ...

Gotchas

  • Client-side rendered SPAs need special SEO handling. Pages rendered only in the browser are invisible to crawlers that don't execute JS. Use SSR/SSG (e.g. Next.js) or prerender routes. Check with curl — if the returned HTML is empty, search engines see nothing.
  • Multi-locale SEO is a different game. Results on a country-specific Google domain (e.g. google.com.tw) differ from google.com. Test both. Traditional Chinese keywords have different search volumes than Simplified — same lesson applies to any locale split.
  • Don't obsess over meta descriptions. Google rewrites them ~70% of the time anyway. Make them good but don't spend hours perfecting them.
  • Schema markup doesn't directly improve rankings but it gets you rich snippets (stars, prices, FAQ dropdowns) which improve click-through rate, which DOES improve rankings.
  • New sites take 3-6 months to rank. Don't check daily. Set a monthly review cadence.
  • Google Search Console is free and essential. If it's not set up, that's the first fix. Everything else is guessing without data.

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.