agentleFS
Sign inStart free
bestdeejay-designbestdeejay-design/agent-skills/skills/seo-audit/SKILL.md

seo-audit

Skill6 starsChanged 3 months agoMITView on GitHub

Technical SEO audit and health: full technical audit (meta, headings, alt, broken links, sitemap, robots.txt, canonical, URL structure), Core Web Vitals (LCP/CLS/INP, blocking resources, unused CSS/JS, caching), a comprehensive scored report (7 dimensions, weighted 100%), and the autonomous fix agent (P1-P5 prioritization, diff-before-apply). Commands documented in commands/. Triggers: 'seo audit', 'technical audit', 'core web vitals', 'site speed', 'seo report', 'seo fix', 'технический аудит', 'проверка seo', 'скорость сайта'.

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

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

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 2

    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. Distinctive:

    Use this skill for the technical side of SEO: audit the site, measure Core Web Vitals, produce a scored report, and apply fixes safely.

    line 14
  2. Very specific:

    Do not use for content writing or JSON-LD generation.

    line 43
  3. Very specific:

    Run the technical checks documented in commands/, preserving page URLs and source file locations.

    line 48
  4. Distinctive:

    Every finding needs page/file, check, evidence, severity, recommended fix, and confidence.

    line 55

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

Use this skill for the technical side of SEO: audit the site, measure Core Web Vitals, produce a scored report, and apply fixes safely. This is the "measure and fix" layer of SEO.

Commands (documented in commands/)

CommandWhat it does
seo-auditFull technical audit: meta, headings, alt, broken links, sitemap, robots.txt, canonical, URL structure
seo-speedCore Web Vitals (LCP/CLS/INP), blocking resources, unused CSS/JS, caching
seo-reportComprehensive scored report — 7 dimensions, weighted 100%, weekly action plan
seo-fixAutonomous fix agent: P1–P5 prioritization, diff-before-apply, safety rules

Modes: URL (external sites) and File (local projects).

When to use

  • User asks for "seo audit", "technical audit", "core web vitals", "site speed", "seo report", "seo fix", "технический аудит", "проверка seo".
  • A site's technical health must be measured, scored and fixed.

Do NOT use

  • For structured data / meta tags / OG — that is seo-schema.
  • For content / keywords / headings / images — that is seo-content.
  • For crawlability / linking structure / competitors — that is seo-crawl.

Boundaries

  • Do not use for content writing or JSON-LD generation; use seo-content or seo-schema.

Audit workflow and evidence

  1. Inventory all routes/pages and declare whether the source is URL, static files, or a framework build.
  2. Run the technical checks documented in commands/, preserving page URLs and source file locations.
  3. Score only observed dimensions; mark unavailable Core Web Vitals or crawl data as not measured, not zero.
  4. Produce a prioritized remediation plan, then ask before applying changes.
  5. Re-run the affected checks after any fix and compare before/after results.

Output gate

Every finding needs page/file, check, evidence, severity, recommended fix, and confidence. Never claim a ranking improvement or a 100/100 score from static inspection alone. For seo-fix, show a diff and run the relevant build or test command before claiming success.

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.

Check your setup, free