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

seo-audit

Skill0 starsChanged 21 days agoMITView on GitHub

Use when you need a comprehensive technical SEO audit with prioritized findings, evidence, and proposed fixes using Ahrefs, Semrush, or public web data.

185 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use openseo-release-notes, community-led-growth 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-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

  • 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

  • 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

  • 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 14 projects that use this

  • +4 more from nicepkg
  • +3 more from Jwuthri

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 165 edited versions we read keep these.

  • 5

    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:

    Run a technical SEO audit using the existing audit procedure.

    line 10
  2. Distinctive:

    Verify platform facts, tool schemas, crawler behavior, thresholds, and structured-data eligibility against current documentation.

    line 15
  3. Distinctive:

    Treat numerical CTR ranges, traffic projections, and impact scenarios as assumptions.

    line 17
  4. Distinctive:

    Only add statistics, ratings, prices, or other factual markup that the page and evidence support.

    line 18
  5. Distinctive:

    Use the procedure's report format: executive summary, section results, prioritized actions, proposed fixes, and relevant search-visibility …

    line 22

“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

Run a technical SEO audit using the existing audit procedure. It contains the tool-selection workflow, audit sections, report template, execution batches, and optional stack-specific fixes.

Before running

  • Reuse inputs already provided. Identify the domain, available data sources, conversion goal, and audit scope.
  • Verify platform facts, tool schemas, crawler behavior, thresholds, and structured-data eligibility against current documentation. The procedure's tool names and examples may need adaptation.
  • Distinguish measured first-party data from third-party estimates and missing evidence. Do not report an unchecked section as a pass.
  • Treat numerical CTR ranges, traffic projections, and impact scenarios as assumptions. Prefer the site's own comparable data and state the basis for any estimate.
  • Only add statistics, ratings, prices, or other factual markup that the page and evidence support.

Deliver

Use the procedure's report format: executive summary, section results, prioritized actions, proposed fixes, and relevant search-visibility deliverables. Attach evidence and disclose unavailable checks.

An audit authorizes analysis. Apply external changes only within the user's explicit authorization, with a reviewable diff, rollback path, and readback verification.

Follow-on work

  • seo-quick-wins: existing-page opportunities and priorities.
  • internal-linking: contextual links and target verification.
  • seo-ops: research, content, metadata, and schema procedures.
  • verified-seo-article-writing: a sourced article from an approved brief.

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.