agentleFS
donatassimkusdonatassimkus/claude-ai-skills/skills/seo/SKILL.md

seo

Skill1 starsChanged 4 months agoMITView on GitHub

SEO strategy, audits, and frameworks: keyword research, content strategy, technical SEO, programmatic pages, link building architecture. Use for SEO audits, site structure planning, keyword strategy, and systematic SEO work.

159 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-agentic, seo-maps 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.
  • AgriciDanielSkill

    seo-agentic

    Audit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Use when the user asks whether AI agents can use or browse the site, or about llms.txt or WebMCP. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).

    Also in 5 projects that use this

  • timruebenachSkill

    seo-maps

    Maps intelligence for local SEO — geo-grid rank tracking, GBP profile auditing via API, review intelligence across Google/Tripadvisor/Trustpilot, cross-platform NAP verification (Google/Bing/Apple/OSM), competitor radius mapping, and LocalBusiness schema generation from API data. Three-tier capability: free (Overpass + Geoapify), DataForSEO (full intelligence), DataForSEO + Google (maximum coverage). Use when user says "maps", "geo-grid", "rank tracking", "GBP audit", "review velocity", "competitor radius", "maps analysis", "local rank tracking", "Share of Local Voice", or "SoLV".

    Also in 17 projects that use this

  • megastepSkill

    seo-images

    Image optimization analysis for SEO and performance. Checks alt text, file sizes, formats, responsive images, lazy loading, and CLS prevention. Use when user says "image optimization", "alt text", "image SEO", "image size", or "image audit".

    Also in 24 projects that use this

  • timruebenachSkill

    seo-image-gen

    AI image generation for SEO assets: OG/social preview images, blog hero images, schema images, product photography, infographics. Powered by Gemini via nanobanana-mcp. Requires banana extension installed. Use when user says \"generate image\", \"OG image\", \"social preview\", \"hero image\", \"blog image\", \"product photo\", \"infographic\", \"seo image\", \"create visual\", \"image-gen\", \"favicon\", \"schema image\", \"pinterest pin\", \"generate visual\", \"banner\", or \"thumbnail\".

    Also in 15 projects that use this

  • megastepSkill

    seo-sitemap

    Analyze existing XML sitemaps or generate new ones with industry templates. Validates format, URLs, and structure. Use when user says "sitemap", "generate sitemap", "sitemap issues", or "XML sitemap".

    Also in 26 projects that use this

  • renepfSkill

    orch-pipeline

    Shared orchestration engine for the orch-* skill family. Defines the gated Research-Plan-TDD-Review-Commit pipeline, the size classifier, the agent map, and the two human gates that the orch-* operation skills delegate to. Not usually invoked directly.

    Also in 4 projects that use this

  • +3 more from timruebenach
  • +1 more from megastep

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 148 edited versions we read keep these.

  • 4

    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:

    If $ARGUMENTS is provided, treat it as the target (URL, page, topic, or focus area).

    line 18
  2. Distinctive:

    If no arguments, ask one question: what is the target and goal?

    line 19
  3. Distinctive:

    Every page needs a unique title and meta description.

    line 40
  4. Distinctive:

    Never report "no schema found" from a static fetch alone — JavaScript-injected schema won't appear in static HTML.

    line 47

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

You are operating at principal SEO level. Think in systems, not single pages. Every recommendation must connect to traffic, conversion, or revenue.

Project context is loaded from the active CLAUDE.md. Apply all SEO work to that specific project, audience, and goals.


When invoked

If $ARGUMENTS is provided, treat it as the target (URL, page, topic, or focus area). If no arguments, ask one question: what is the target and goal?


Reference files

Load the relevant reference file(s) based on the task. Read only what you need.

Task typeReference file
Technical audit, schema, crawl budget, Core Web Vitals, site speed, canonical, noindex, redirects, instant indexing, HTTPSreferences/technical.md
Keyword research, SERP analysis, cannibalization, topical authority, GSC setupreferences/keywords.md
Content briefs, E-E-A-T, blog pipeline, page-type patterns, programmatic SEO, international SEO, content lengthreferences/content-strategy.md
Internal linking, outbound links, anchor text, backlink buildingreferences/link-building.md

For a full site audit: load all four.


Core principles (always apply)

  1. Every page needs a unique title and meta description. No exceptions.
  2. Canonical tags must self-reference every indexable page.
  3. Internal links are the most powerful on-site SEO lever. Hub-and-spoke architecture. Bi-directional.
  4. SERP analysis before writing any content brief. The SERP is the spec.
  5. E-E-A-T signals matter most on YMYL topics.
  6. Crawl budget = prioritize indexable pages, noindex thin/duplicate content.
  7. Site speed targets: LCP < 2.5s, INP < 200ms, CLS < 0.1.
  8. Never report "no schema found" from a static fetch alone — JavaScript-injected schema won't appear in static HTML.

Default output format

For a site audit:

  1. Critical issues (fix now — indexation blockers, crawl errors, broken redirects)
  2. High-impact opportunities (ranked by traffic potential)
  3. Technical debt (lower urgency, schedule for later)

For a content brief:

  • Target keyword + intent
  • SERP composition summary
  • Content type and format recommendation
  • Required sections (based on Perfect Page analysis)
  • Internal links to include
  • Schema markup required

For a keyword research task:

  • Keyword clusters mapped to page types
  • Funnel stage (TOFU / MOFU / BOFU)
  • Estimated difficulty and traffic potential
  • Recommended priority order

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.