agentleFS
Sign inStart free
UXMagicaiUXMagicai/seosorted-skills/skills/seo-audit/SKILL.md

seo-audit

Skill0 starsChanged 39 days agoMITView on GitHub

Run and explain a technical and on-page SEO audit of the user's website with SEOsorted. Use when the user asks for an SEO audit, site health check, "what's wrong with my site", technical SEO issues, broken pages, crawl errors, or wants a prioritized fix list. Starts an audit, waits for it, and turns the issues into a ranked action plan with step-by-step fixes.

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

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

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    When the user says a fix is done, operation: "update_issue" with issue_id (and step_id for one step) and done: true.

    line 19
  2. Distinctive:

    If the audit fails or times out, say so and offer to retry.

    line 35

“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

Audit before writing anything new. Adding pages to a site with indexing, speed or on-page problems wastes the content.

Steps

  1. audit_my_site with operation: "report" (no audit_id) to see whether a recent audit exists. If it is under 14 days old and the user has not changed the site since, use it.
  2. Otherwise tell the user an audit uses one audit credit, then audit_my_site with operation: "start". Poll check_job_status with wait_seconds: 45 until it completes (audits usually take a few minutes; keep the user posted).
  3. audit_my_site with operation: "report" for the finished audit. operation: "history" shows the score trend across past audits.

Track fixes

  • audit_my_site operation: "issues" with status: "open" (filter by severity, category) lists every issue with its id, fix-step ids and affected URLs.
  • When the user says a fix is done, operation: "update_issue" with issue_id (and step_id for one step) and done: true; done: false reopens it. Free.
  • To verify one fixed page without a new crawl, audit_any_page operation: "audit" with its url (free) — see page-seo-audit.

How to present it

  • One line: overall score and how it compares with the previous audit, if there is one.
  • Fix first table: critical issues, ordered by pages affected. Columns: issue, pages affected, why it matters (one plain sentence), fix steps.
  • Then table: warnings worth doing this month.
  • Ignore for now: low-impact notices, grouped in one line.
  • Competitor benchmarks, if returned: where the site is clearly behind.

Translate jargon. "Canonical points to a redirect" becomes "these pages tell Google the 'real' version is a page that redirects, so Google may index neither."

Guardrails

  • Report what the audit found. Do not invent issues it did not flag; if you spot something extra by fetching a page yourself, label it as your own observation.
  • If the audit fails or times out, say so and offer to retry; do not present a partial report as complete.

Next

Technical issues fixed → keyword-research. Many thin or duplicate pages → cannibalization-check. No Search Console connected → point the user to Settings → Integrations; performance work needs it.

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