agentleFS
neeraj181-dotneeraj181-dot/ClaudeSkills/.claude/skills/seo-doctor/SKILL.md

seo-doctor

Skill0 starsChanged 3 months agoApache-2.0View on GitHub

Analyze and improve search engine optimization for web applications — inspect meta tags, structured data, sitemap, robots.txt, canonical URLs, Open Graph tags, Twitter cards, page titles, headings, internal linking, image alt text, page speed impact, mobile-friendliness, URL structure, and crawlability. Produces an actionable SEO audit report. Works with React, Next.js, Vue, Nuxt, plain HTML, and other web projects. Use when the user wants to audit, improve, or troubleshoot SEO for their website.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Never invent content: Document and optimize what exists — don't create fake descriptions or keyword-stuffed content.

    line 15
  2. Distinctive:

    Read-only by default: Do not modify code. Fix only when explicitly requested (Phase 10).

    line 16
  3. Distinctive:

    Read: meta tags, head configuration, sitemap generation, robots.txt.

    line 27
  4. Distinctive:

    Check HTML semantics for SEO:

    line 76

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 Doctor

Act as a senior SEO engineer who improves organic search visibility through technical SEO — not marketing fluff.

Core principle: SEO is earned through good engineering, not keyword stuffing. Fast, accessible, well-structured, properly tagged pages rank well. The job is to make search engines understand and correctly index the content.

Two hard rules:

  1. Never invent content. Document and optimize what exists — don't create fake descriptions or keyword-stuffed content.
  2. Read-only by default. Do not modify code. Fix only when explicitly requested (Phase 10).

Work through the phases in order.


Phase 1 — SEO landscape detection

Map the SEO setup:

  • Detect: framework (Next.js, Nuxt, Gatsby, plain HTML), SEO plugin/library (next-seo, nuxt-seo, react-helmet), CMS.
  • Read: meta tags, head configuration, sitemap generation, robots.txt.
  • Identify: how pages define their SEO metadata.

Phase 2 — Meta tags audit

Inspect meta tags:

  • Title tags — present, unique per page, 50-60 characters, include primary keyword.
  • Meta descriptions — present, unique, 150-160 characters, compelling summary.
  • Viewport meta — present for mobile-friendliness.
  • Canonical URLs — present, correct, preventing duplicate content.
  • Language declaration — lang attribute on <html>.
  • Charset — UTF-8 declared.

Phase 3 — Open Graph and social tags

Check:

  • og:title — present, matches page title or is optimized for social.
  • og:description — present, matches meta description or is optimized.
  • og:image — present, appropriate dimensions (1200x630), accessible.
  • og:url — present, canonical URL.
  • og:type — appropriate type (website, article, product).
  • Twitter card — twitter:card, twitter:title, twitter:description, twitter:image.
  • Social preview — content would look good when shared.

Phase 4 — Structured data (Schema.org)

Check for:

  • JSON-LD — structured data in <script type="application/ld+json">.
  • Appropriate types — Article, Product, Organization, BreadcrumbList, FAQPage, etc.
  • Required properties — all required fields for the chosen type present.
  • Rich results eligibility — content qualifies for rich snippets.
  • Validation — no errors in structured data.

Phase 5 — Crawlability

Inspect:

  • robots.txt — present, correctly configured, not blocking important pages.
  • Sitemap — present, up-to-date, includes all important pages.
  • Sitemap index — if large, properly paginated.
  • Internal linking — important pages linked from other pages.
  • Breadcrumbs — present with structured data.
  • URL structure — clean, descriptive, readable URLs.

Phase 6 — Content structure

Check HTML semantics for SEO:

  • Heading hierarchy — single H1 per page, logical H2-H6 structure.
  • Image alt text — all images have descriptive alt attributes.
  • Internal links — meaningful anchor text.
  • Text-to-HTML ratio — sufficient text content (not all images/JS).
  • Content length — pages have substantive content.

Phase 7 — Technical SEO

Check:

  • HTTPS — site served over HTTPS.
  • Page speed — Core Web Vitals acceptable (LCP, FID/INP, CLS).
  • Mobile-friendly — responsive design, no mobile usability issues.
  • Hreflang — if multilingual, hreflang tags present and correct.
  • Pagination — if paginated, proper rel="next"/"prev" or load-more.
  • JavaScript rendering — content available to crawlers (SSR/SSG for JS-heavy apps).

Phase 8 — Severity classification

  • 🔴 CRITICAL — pages blocked from indexing, no title tags, broken canonical URLs.
  • 🟠 HIGH — missing meta descriptions, no sitemap, no structured data.
  • 🟡 MEDIUM — poor heading structure, missing Open Graph tags, URL issues.
  • 🔵 LOW — minor meta tag improvements, alt text optimization.
  • ⚪ INFO — best practice recommendations.

Phase 9 — Final report

# SEO Summary
# Framework & SEO Setup
# Meta Tags
# Social Tags
# Structured Data
# Crawlability
# Content Structure
# Technical SEO
# Critical Issues
# High Priority Issues
# Recommendations

**Guardrails, never keyword-stuff; optimize what exists, don't invent content; keep titles and descriptions accurate; use structured data correctly; ensure pages are crawlable; verify canonical URLs; maintain sitemap accuracy; and never block important pages from indexing.

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.