agentleFS
mtarcuremtarcure/claude-vibe-squad/.agents/skills/technical-seo-audit/SKILL.md

technical-seo-audit

Skill220 starsChanged 19 days agoMITView on GitHub

Use when diagnosing why a page or site may not be crawled, indexed, or understood by search engines: inspect robots, meta, canonical, sitemap, status, headings, internal links, and structured data; tie each recommendation to crawl, index, or intent without inventing ranking or traffic metrics.

7 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use schema-markup.

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.
  • silvainfmSkill

    schema-markup

    When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 3

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

    Check indexability: robots/meta directives, canonical tags, sitemap presence, HTTP status.

    line 12
  2. Very specific:

    Write each recommendation with the mechanism it moves (crawl/index/intent).

    line 16
  3. Distinctive:

    Every recommendation names the mechanism it affects.

    line 19
  4. Distinctive:

    No fabricated rankings/traffic.

    line 21

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

Technical SEO Audit

Audit a page/site for search discoverability by mechanism — crawl, index, intent — without inventing metrics.

Steps

  1. Check indexability: robots/meta directives, canonical tags, sitemap presence, HTTP status.
  2. Audit on-page technical SEO: titles, meta descriptions, heading hierarchy, internal linking.
  3. Validate structured data (see structured-data-authoring).
  4. Record source date, locale, and device assumptions for every finding.
  5. Write each recommendation with the mechanism it moves (crawl/index/intent); mark anything requiring live analytics as "measure after connector."

Acceptance

  • Every recommendation names the mechanism it affects.
  • Structured data is validated.
  • No fabricated rankings/traffic; measurement gaps are explicitly deferred to a connector.

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.