agentleFS
brayandiazcbrayandiazc/project-starter-template-en-ai/.claude/skills/seo-audit/SKILL.md

seo-audit

Skill2 starsChanged 2 months agoMITView on GitHub

Audits a page or route's SEO metadata (title, description, canonical, Open Graph, robots) against the project's SEO conventions and lists what is missing or wrong. Use this when the user asks to check/audit SEO, review meta tags, or verify a page is search-ready (e.g. "audit SEO on the pricing page", "check meta tags for this route").

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

3 rules. 0 are common, 1 is distinctive, and 2 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read docs/conventions/seo.md for the project's required tags, value formats (e.g.

    line 8
  2. Distinctive:

    Check each required item against the convention doc:

    line 10
  3. Very specific:

    Do NOT silently rewrite metadata unless the user asks — report findings first.

    line 21

“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

Audit the SEO metadata of the page/route the user names.

  1. Read docs/conventions/seo.md for the project's required tags, value formats (e.g. title length, description length), per-page-type rules, and which pages should be indexed vs. noindex.
  2. Identify the page/route's source file(s) and where its metadata is defined.
  3. Check each required item against the convention doc:
    • <title> — present, unique, within the length rule.
    • meta description — present, within length, descriptive.
    • canonical URL — present and correct.
    • Open Graph / social tags — og:title, og:description, og:image, etc. as required.
    • robots directives — correct for this page type (e.g. noindex on private/utility pages).
    • Structured data, if the convention requires it.
  4. Produce a checklist report: each item marked Present / Missing / Incorrect, with the file:line and a concrete fix suggestion for each problem.

Example finding: Missing canonical — add to app/pricing/page.tsx; convention requires one on every indexable page.

Do NOT silently rewrite metadata unless the user asks — report findings first. Always defer to docs/conventions/seo.md over generic SEO advice.

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.