agentleFS
samsam007bsamsam007b/claude-code-standards-kit/skills/seo-audit/SKILL.md

seo-audit

Skill2 starsChanged 8 months agoMITView on GitHub

Complete technical SEO audit: Core Web Vitals, Open Graph metadata, JSON-LD structured data, sitemap, robots.txt, crawlability. Sources: Google Search Central, schema.org, OGP.

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

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 165 edited versions we read keep these.

  • 1

    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:

    Before putting a page or site into production

    line 12

“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: Technical SEO Audit

When to use

  • Before putting a page or site into production
  • Complete SEO audit of a Next.js project
  • Open Graph verification for social sharing
  • Implementing structured data

Audit criteria

Metadata (per page)

  • Unique <title>, 50-60 characters, main keyword first
  • Unique <meta description>, 150-160 characters, call-to-action
  • og:title, og:description, og:image (1200×630px min), og:url
  • twitter:card, twitter:title, twitter:description, twitter:image
  • canonical URL to avoid duplicate content
  • hreflang if multilingual

Structured Data (schema.org + JSON-LD)

Priority types depending on content:

  • Product/service pages → Product, Service, Organization
  • Articles/blog → Article, BlogPosting
  • FAQ → FAQPage + Question + Answer
  • Profiles → Person
  • Lists → ItemList

Core Web Vitals (Google ranking factor)

  • LCP < 2.5s: hero image with priority, fonts preload
  • CLS < 0.1: explicit dimensions on images, no asynchronous DOM injection
  • INP < 200ms: non-blocking events, defer non-critical JS

Crawlability

  • robots.txt: Allow: / + Disallow on private pages + Sitemap: pointer
  • sitemap.xml generated dynamically, submitted in Search Console
  • No noindex on pages that must be indexed
  • Internal links to all orphan pages
  • URL slug in kebab-case, descriptive, without stopwords

Actual HTML delivered to the crawler (Next.js App Router, CRITICAL)

The sitemap/robots.txt/meta can be perfect and the page can still remain invisible if the server HTML does not contain the actual content. A crawler without JS (and Googlebot's first pass) only sees what is in the DOM, not what is waiting to be hydrated.

Real incident (Next.js project): a provider loaded via dynamic(() => import(...), { ssr: false }) wrapped {children} in the root layout → all of the app's content (homepage + deep pages) bailed out of server rendering, with a flawless sitemap/robots, yet near-zero indexing for months.

  • curl -s <url> | grep -A2 '<body' → the visible text (outside <script>/<style>) must match the actual page content, not a skeleton/loading state
  • Count the actual <a href= in the body (outside script tags): it must reflect the real navigation, not just 0-1 links (skip-link)
  • Look for BAILOUT_TO_CLIENT_SIDE_RENDERING in the raw HTML: if present right after the opening <body> or before <main>, an upstream ssr:false blocks everything that follows
  • Audit every dynamic(..., { ssr: false }) that accepts children and check that it does not wrap them (<Comp>{children}</Comp>): only leaf components (modals, maps, charts, with no children passed by the parent) should use ssr:false
  • Compare HTML size with a browser UA vs curl without UA: they must be identical (a minimal shell served to bots is a red flag)

Internationalization

  • lang on <html> (e.g. lang="fr-BE")
  • hreflang on each language variant
  • URLs like /fr/page or fr.domain.com

Output format (Next.js)

// generateMetadata example
export async function generateMetadata({ params }): Promise<Metadata> {
  return {
    title: '[Title 50-60 chars]',
    description: '[Description 150-160 chars]',
    openGraph: {
      title: '[OG Title]',
      description: '[OG Description]',
      images: [{ url: '/og-image.png', width: 1200, height: 630 }],
    },
  }
}
## SEO Audit: [page/site]

### Score : [0-100]
### 🔴 Blocking | 🟡 Important | 🟢 Suggestion
### JSON-LD to add
[structured data code]

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.