agentleFS
reescalderreescalder/claude-skills/seo/SKILL.md

SEO

Skill0 starsChanged 4 months agoMITView on GitHub

Optimize pages for search rankings with on-page rules, technical audits, content strategy, and structured data.

156 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

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

  • 0

    Common

    Most of the 145 edited versions we read keep these.

  • 2

    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:

    Only one H1 per page — must differ from title but include primary keyword

    line 24
  2. Distinctive:

    Search intent match: informational, navigational, transactional, commercial

    line 38

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

Quick Reference

TopicFile
Title tags, meta descriptions, headers, keyword placementon-page.md
Core Web Vitals, crawlability, mobile, indexingtechnical.md
Search intent, E-E-A-T, content freshnesscontent.md
Google Business, NAP consistency, local keywordslocal.md
JSON-LD, Article, LocalBusiness, FAQ, Product schemaschema.md
Internal linking, anchor text, backlink principleslinks.md

Critical Rules

On-Page Fundamentals

  • Title: 50-60 chars, primary keyword in first 30 chars, unique per page
  • Meta description: 150-160 chars, benefit-focused, call-to-action
  • Only one H1 per page — must differ from title but include primary keyword
  • H1 → H2 → H3 strict hierarchy — never skip levels
  • Primary keyword in: title, H1, first 100 words, URL
  • Keyword density under 3% — stuffing triggers penalties

Technical Essentials

  • Core Web Vitals: LCP < 2.5s, INP < 200ms, CLS < 0.1
  • Mobile-first indexing: Google indexes mobile version — test mobile rendering
  • Canonical URL on every page — prevents duplicate content penalties
  • robots.txt: don't block CSS/JS, Google needs them to render
  • XML sitemap: max 50K URLs per file, submit in Search Console
  • HTTPS required — mixed content breaks security indicators

Content Signals

  • Search intent match: informational, navigational, transactional, commercial
  • E-E-A-T for YMYL: Experience, Expertise, Authoritativeness, Trustworthiness
  • Thin content penalty: pages under 300 words with no unique value
  • Content freshness: update dates matter for time-sensitive queries

Penalties to Avoid

  • Hidden text with CSS or font-size:0 — immediate penalty
  • Duplicate title tags across pages — wastes crawl budget
  • Keyword stuffing in alt text — unnatural patterns detected
  • Cloaking: showing different content to users vs bots
  • Link schemes: buying links, excessive link exchanges

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.