agentleFS
ZachArticulateVZachArticulateV/designer-pro-and-seo/skills/seo-audit/SKILL.md

seo-audit

Skill10 starsChanged 27 days agoMITView on GitHub

Orchestrates a multi-specialist SEO audit — detects business type, dispatches the available specialist skills, and aggregates one weighted health score with a prioritized, deduped fix list. Crawls up to ~500 pages when seo-firecrawl is connected; otherwise audits the key URLs you provide and says so. Trigger when the user says "seo audit", "full site audit", "comprehensive seo review", "analyze my site for seo", "website health check", or "audit my site for 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

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:

    Use it as the baseline, then dispatch the agents below for live URLs and for the judgement the engines can't make.

    line 43

“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

Family: seo Status: Stable

Purpose

The orchestrator and public face of the SEO family. Runs the available specialist skills against your target, then aggregates their findings into one weighted health score with a prioritized fix list — so the user gets a single answer, not eight disconnected reports.

Scope note (honest): it audits the URLs you provide out of the box. Full-site crawling (up to ~500 pages, business-type auto-detect at scale) activates when the seo-firecrawl skill is installed; without it, point it at the key URLs.

Triggers

  • "seo audit" / "full site audit" / "comprehensive seo review"
  • "analyze my site for SEO" / "website health check"
  • "audit [domain]"

Inputs

  • A domain, a URL, or a small list of key URLs
  • Optional: business-type override; specialist include/exclude

Steps

  1. Scope. Take the URL(s). If seo-firecrawl is available, crawl to discover pages; otherwise audit the provided URLs and say so. For a local static build, the whole free path is one command — every applicable engine, per-specialist scores, the re-normalized health score, a covered / not-covered list, and one fix list merged across pages:
    python3 "${CLAUDE_PLUGIN_ROOT}/scripts/workflow/site_audit.py" --dir dist/ --base-url https://site.com --human
    Use it as the baseline, then dispatch the agents below for live URLs and for the judgement the engines can't make.
  2. Profile. Infer business type (SaaS / e-commerce / local / publisher / agency) from the content to decide which conditional specialists apply.
  3. Dispatch the specialist agents in parallel — real Agent-tool sub-agents, each a dispatched leaf under agents/ (one-directional, no back-edges). The full roster and the dispatch conditions are in references/seo-audit/dispatch-matrix.md. Always fan out the five always-on agents:
    • seo-page — per-URL on-page review
    • seo-technical — technical dimensions (tech_audit.py)
    • seo-schema — structured-data validation
    • seo-sitemap — sitemap structure + gates
    • seo-image-audit — image SEO Then add the conditional agents the profile and connected tooling call for: seo-content (content depth / E-E-A-T) and seo-geo (AI-citability) by default, plus seo-local-unified for a local business or seo-ecommerce for a store; when their tools are connected, also seo-google (real CWV / rankings) and seo-backlinks. Each agent obeys the plugin's tier cascade and returns its machine-parseable ## Output contract block for deterministic fan-in. Record which specialists ran and which were skipped (and why) rather than implying coverage you didn't run.
  4. Aggregate + score. Collect each agent's Output-contract score and feed the per-specialist map to scripts/workflow/audit_aggregate.py, which computes one weighted health score (0–100) re-normalized over the specialists that actually ran — a skipped specialist is excluded from the denominator, never zeroed. The weight table (anchors seo-technical and seo-page at 20; seo-content 15; the mid band at 10; seo-geo 5) and the grade bands are in references/seo-audit/scoring-weights.md. Report the weighting used.

    python3 "${CLAUDE_PLUGIN_ROOT}/scripts/workflow/audit_aggregate.py" --file scores.json --human
  5. Prioritize. Merge findings into one list: Critical → High → Medium → Low, deduped, each with the owning specialist and a specific fix.
  6. Render the health score, the prioritized fix list, and per-specialist appendices. State explicitly which specialists ran and which were skipped.

Outputs

  • Weighted health score (0–100) with the weighting shown
  • One prioritized, deduped fix list (Critical/High/Medium/Low)
  • Per-specialist detail appendices + an explicit "covered / not covered" list

Dependencies

  • Core specialists (always): seo-page, seo-technical, seo-schema, seo-sitemap, seo-image-audit — each dispatched as its agents/<name>.md leaf
  • Conditional specialists (by business type / connected tooling): seo-content, seo-geo, seo-local-unified, seo-ecommerce, seo-google, seo-backlinks
  • references/seo-audit/dispatch-matrix.md (required) — the always/conditional roster
    • dispatch conditions the Steps fan out over
  • references/seo-audit/scoring-weights.md (required) — the health-score weight table
    • re-normalization + grade bands
  • scripts/workflow/audit_aggregate.py (required) — re-normalized health-score fan-in
  • scripts/workflow/site_audit.py (required) — the local one-command engine run + fan-in
  • scripts/seo/business_type.py (required) — business-type classification for conditional dispatch
  • Optional: seo-firecrawl (full-site crawl)

Notes

Current-state facts every specialist relies on (AI Overviews / AI Mode sourcing, retired rich results, crawl limits, spam policies) are dated in references/shared/search-landscape-2026.md; cite it rather than restating a fact.

Most SEO requests should land here first; it routes to specialists. It dispatches real Agent-tool sub-agents in parallel (agents/), one per specialist leaf, and never claims coverage it didn't run — the "covered / not covered" list plus the re-normalized denominator keep the health score honest. Adding a new specialist agent auto-joins this socket (see references/seo-audit/dispatch-matrix.md).

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.