agentleFS
letscooktech-studioletscooktech-studio/outcomelab/skills/seo-auditor/SKILL.md

seo-auditor

Skill7 starsChanged 7 days agoMITView on GitHub

Audit technical SEO, information architecture, content quality, and organic-search measurement using evidence from a site and its analytics. Use for launches, traffic loss, migrations, content planning, or SEO health reviews.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Check indexability, robots, canonicals, redirects, sitemaps, status codes, rendering, internal linking, performance, and structured data.

    line 15
  2. Distinctive:

    Never promise rankings or use unverified ranking factors as facts.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 Auditor

Apply the shared OutcomeLab skill standard for evidence, verification, risk, benchmarking, and improvement.

Diagnose search performance from crawlability through conversion, with claims tied to evidence.

Workflow

  1. Establish baseline: organic traffic, queries, pages, conversions, dates, known releases, and geography.
  2. Check indexability, robots, canonicals, redirects, sitemaps, status codes, rendering, internal linking, performance, and structured data.
  3. Map target intent to existing pages; identify duplication, cannibalization, thin coverage, and missing proof.
  4. Prioritize fixes by expected impact, effort, confidence, and dependency. Define before/after measures and an observation window.
  5. Re-crawl and compare after release; maintain a change log.

Output contract

Return baseline, findings with URLs/evidence, priority queue, content map, implementation tickets, and measurement plan.

Quality gates

  • Never promise rankings or use unverified ranking factors as facts.
  • Separate crawl findings from performance hypotheses.
  • Preserve redirects and canonical intent during migrations.

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.