agentleFS
gerson-cloudgerson-cloud/claude-skills/skills/seo-page/SKILL.md

seo-page

Skill0 starsChanged 6 months agoMITView on GitHub

SEO page analysis tool

34 other projects use a version of this, 27 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-agentic, seo-sxo 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-sxo

    Search Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says "SXO", "search experience", "page type mismatch", "SERP analysis", "user story", "persona scoring", "why isn't my page ranking", "intent mismatch", or "wireframe".

    Also in 20 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

  • indranilbanerjeeSkill

    seo-drift

    Compare two SEO exports (Search Console, two dates): gainers, losers, drift classes. \"what moved after the core update\"

    Also in 22 projects that use this

  • mangollcSkill

    seo-backlinks

    Backlink analysis and link building strategy: competitor backlink profiling, outreach plan generation, monthly SEO reporting framework, toxic link identification, link opportunity scoring, and unlinked mention discovery.

    Also in 16 projects that use this

  • mangollcSkill

    seo-local

    Local SEO optimization: Google Business Profile post generation, 30-day posting calendars, NAP consistency checks, local citation audits, review response templates, local keywords.

    Also in 19 projects that use this

  • +6 more from timruebenach

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 33 edited versions we read keep these.

  • 14

    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:

    NEVER provide short summary-style SEO audits

    line 12
  2. Distinctive:

    ALWAYS analyze every section listed in this skill

    line 13
  3. Distinctive:

    NEVER skip sections even if issues are not found

    line 14
  4. Distinctive:

    Use structured formatting exactly as defined below

    line 17
  5. Distinctive:

    When possible, provide examples from the page

    line 18
  6. Distinctive:

    If target keyword is provided, optimize analysis around that keyword

    line 20
  7. Distinctive:

    If keyword is not provided, infer the primary keyword from title, headings, URL, and body content

    line 21
  8. Distinctive:

    If a keyword is provided, compare optimization against ranking intent for that keyword

    line 22
  9. Distinctive:

    Avoid generic recommendations unless supported by findings from the analyzed page

    line 23
  10. Distinctive:

    NEVER recommend HowTo (deprecated) or FAQ (restricted to gov/health)

    line 76
  11. Distinctive:

    ALWAYS provide optimized Title Tag, Meta Description, and H1 recommendations

    line 105
  12. Distinctive:

    Every scoring category MUST include a numeric score

    line 106
  13. Distinctive:

    Avoid generic SEO advice unless directly relevant to the page

    line 112
  14. Distinctive:

    Search intent to conversion alignment

    line 122

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

Single Page Analysis

Audit Behavior Rules

  • Base findings on actual observed page elements whenever possible
  • Analyze the actual live page content before generating recommendations
  • NEVER provide short summary-style SEO audits
  • ALWAYS analyze every section listed in this skill
  • NEVER skip sections even if issues are not found
  • Provide detailed findings, not short summaries
  • Include both strengths and weaknesses
  • Use structured formatting exactly as defined below
  • When possible, provide examples from the page
  • Prioritize actionable SEO recommendations
  • If target keyword is provided, optimize analysis around that keyword
  • If keyword is not provided, infer the primary keyword from title, headings, URL, and body content
  • If a keyword is provided, compare optimization against ranking intent for that keyword
  • Avoid generic recommendations unless supported by findings from the analyzed page

Analysis Priority

Prioritize findings in this order:

  1. Indexation & crawlability
  2. Search intent alignment
  3. Content quality & topical coverage
  4. Internal linking
  5. Technical SEO
  6. Structured data
  7. Media optimization
  8. Conversion optimization

What to Analyze

On-Page SEO

  • Title tag: 50-60 characters, includes primary keyword, unique
  • Meta description: 150-160 characters, compelling, includes keyword
  • H1: exactly one, matches page intent, includes keyword
  • H2-H6: logical hierarchy (no skipped levels), descriptive
  • URL: short, descriptive, hyphenated, no parameters
  • Internal links: sufficient, relevant anchor text, no orphan pages
  • External links: to authoritative sources, reasonable count
  • Anchor text distribution: branded / exact match / generic balance
  • Internal link depth: estimated crawl distance from homepage
  • Internal link equity flow: distribution of authority across pages

Content Quality

  • Word count vs page type minimums (see quality-gates.md)
  • Readability: Flesch Reading Ease score, grade level
  • Keyword density: natural (1-3%), semantic variations present
  • Primary keyword: detected or provided input
  • Secondary keywords: supporting terms identified
  • Semantic keyword clusters: related topic groupings
  • Keyword cannibalization: detect competing pages targeting same term
  • E-E-A-T signals: author bio, credentials, first-hand experience markers
  • Content freshness: publication date, last updated date
  • Topical depth vs SERP average: coverage compared to top-ranking pages
  • Missing subtopics: topics competitors cover but page does not include
  • AI content risk signals: generic or low-depth pattern detection

Technical Elements

  • Canonical tag: present, self-referencing or correct
  • Meta robots: index/follow unless intentionally blocked
  • Open Graph: og:title, og:description, og:image, og:url
  • Twitter Card: twitter:card, twitter:title, twitter:description
  • Hreflang: if multi-language, correct implementation

Schema Markup

  • Detect all types (JSON-LD preferred)
  • Validate required properties
  • Identify missing opportunities
  • NEVER recommend HowTo (deprecated) or FAQ (restricted to gov/health)

Images

  • Alt text: present, descriptive, includes keywords where natural
  • File size: flag >200KB (warning), >500KB (critical)
  • Format: recommend WebP/AVIF over JPEG/PNG
  • Dimensions: width/height set for CLS prevention
  • Lazy loading: loading="lazy" on below-fold images

Core Web Vitals (reference only, not measurable from HTML alone)

  • Flag potential LCP issues (huge hero images, render-blocking resources)
  • Flag potential INP issues (heavy JS, no async/defer)
  • Flag potential CLS issues (missing image dimensions, injected content)

Internal Linking Intelligence (NEW)

  • Link depth from homepage (crawl accessibility)
  • Contextual vs navigational link ratio
  • Anchor text quality distribution
  • Internal link equity flow (authority distribution analysis)
  • Orphan page risk detection

Competitor & SERP Gap Analysis (NEW)

  • Top 3 SERP competitor comparison
  • Content gap summary vs competitors
  • Missing sections vs ranking pages
  • SERP feature opportunities (snippets, rich results, etc.)
  • Differentiation opportunities for ranking improvement

Response Depth Requirements

  • ALWAYS provide optimized Title Tag, Meta Description, and H1 recommendations
  • Every scoring category MUST include a numeric score
  • Scores should reflect severity and quantity of issues found
  • Minimum audit depth: medium-detail
  • Include explanations for why each issue matters
  • Include recommended fixes for every major issue
  • Include SEO impact estimation when possible
  • Avoid generic SEO advice unless directly relevant to the page
  • Include direct examples from the page when possible
  • Quote titles, headings, or metadata when relevant
  • Prioritize issues based on estimated SEO impact and crawl/indexation importance

Conversion SEO

  • CTA visibility and clarity
  • Above-the-fold messaging alignment
  • Trust signals (reviews, guarantees, proof elements)
  • UX friction impacting conversions
  • Search intent to conversion alignment

Required Output Format

Page Score Card

Overall Score: XX/100

  • On-Page SEO: XX/100
  • Content Quality: XX/100
  • Technical: XX/100
  • Schema: XX/100
  • Images: XX/100
  • SERP Alignment: XX/100
  • Conversion SEO: XX/100

Strengths

  • List what the page already does well

Critical Issues

  • Highest priority SEO problems

High Priority Improvements

  • Important ranking improvements

Medium Priority Improvements

  • Secondary optimizations

Low Priority Improvements

  • Minor enhancements

SERP & Competitor Analysis

  • Compare page structure vs top-ranking competitors
  • Identify missing sections or content gaps
  • Identify SERP differentiation opportunities

Recommended Metadata

Title Tag: [optimized version]

Meta Description: [optimized version]

H1: [optimized version]


Schema Recommendations

  • Recommended structured data opportunities
  • Include JSON-LD examples when applicable

Internal Linking Recommendations

  • Suggested parent collections
  • Suggested related collections
  • Suggested anchor text opportunities

Final SEO Summary

  • Summarize biggest opportunities for ranking improvements |

Single Page Analysis

Audit Behavior Rules

  • Base findings on actual observed page elements whenever possible
  • Analyze the actual live page content before generating recommendations
  • NEVER provide short summary-style SEO audits
  • ALWAYS analyze every section listed in this skill
  • NEVER skip sections even if issues are not found
  • Provide detailed findings, not short summaries
  • Include both strengths and weaknesses
  • Use structured formatting exactly as defined below
  • When possible, provide examples from the page
  • Prioritize actionable SEO recommendations
  • If target keyword is provided, optimize analysis around that keyword
  • If keyword is not provided, infer the primary keyword from title, headings, URL, and body content
  • If a keyword is provided, compare optimization against ranking intent for that keyword
  • Avoid generic recommendations unless supported by findings from the analyzed page

Analysis Priority

Prioritize findings in this order:

  1. Indexation & crawlability
  2. Search intent alignment
  3. Content quality & topical coverage
  4. Internal linking
  5. Technical SEO
  6. Structured data
  7. Media optimization
  8. Conversion optimization

What to Analyze

On-Page SEO

  • Title tag: 50-60 characters, includes primary keyword, unique
  • Meta description: 150-160 characters, compelling, includes keyword
  • H1: exactly one, matches page intent, includes keyword
  • H2-H6: logical hierarchy (no skipped levels), descriptive
  • URL: short, descriptive, hyphenated, no parameters
  • Internal links: sufficient, relevant anchor text, no orphan pages
  • External links: to authoritative sources, reasonable count
  • Anchor text distribution: branded / exact match / generic balance
  • Internal link depth: estimated crawl distance from homepage
  • Internal link equity flow: distribution of authority across pages

Content Quality

  • Word count vs page type minimums (see quality-gates.md)
  • Readability: Flesch Reading Ease score, grade level
  • Keyword density: natural (1-3%), semantic variations present
  • Primary keyword: detected or provided input
  • Secondary keywords: supporting terms identified
  • Semantic keyword clusters: related topic groupings
  • Keyword cannibalization: detect competing pages targeting same term
  • E-E-A-T signals: author bio, credentials, first-hand experience markers
  • Content freshness: publication date, last updated date
  • Topical depth vs SERP average: coverage compared to top-ranking pages
  • Missing subtopics: topics competitors cover but page does not include
  • AI content risk signals: generic or low-depth pattern detection

Technical Elements

  • Canonical tag: present, self-referencing or correct
  • Meta robots: index/follow unless intentionally blocked
  • Open Graph: og:title, og:description, og:image, og:url
  • Twitter Card: twitter:card, twitter:title, twitter:description
  • Hreflang: if multi-language, correct implementation

Schema Markup

  • Detect all types (JSON-LD preferred)
  • Validate required properties
  • Identify missing opportunities
  • NEVER recommend HowTo (deprecated) or FAQ (restricted to gov/health)

Images

  • Alt text: present, descriptive, includes keywords where natural
  • File size: flag >200KB (warning), >500KB (critical)
  • Format: recommend WebP/AVIF over JPEG/PNG
  • Dimensions: width/height set for CLS prevention
  • Lazy loading: loading="lazy" on below-fold images

Core Web Vitals (reference only, not measurable from HTML alone)

  • Flag potential LCP issues (huge hero images, render-blocking resources)
  • Flag potential INP issues (heavy JS, no async/defer)
  • Flag potential CLS issues (missing image dimensions, injected content)

Internal Linking Intelligence (NEW)

  • Link depth from homepage (crawl accessibility)
  • Contextual vs navigational link ratio
  • Anchor text quality distribution
  • Internal link equity flow (authority distribution analysis)
  • Orphan page risk detection

Competitor & SERP Gap Analysis (NEW)

  • Top 3 SERP competitor comparison
  • Content gap summary vs competitors
  • Missing sections vs ranking pages
  • SERP feature opportunities (snippets, rich results, etc.)
  • Differentiation opportunities for ranking improvement

Response Depth Requirements

  • ALWAYS provide optimized Title Tag, Meta Description, and H1 recommendations
  • Every scoring category MUST include a numeric score
  • Scores should reflect severity and quantity of issues found
  • Minimum audit depth: medium-detail
  • Include explanations for why each issue matters
  • Include recommended fixes for every major issue
  • Include SEO impact estimation when possible
  • Avoid generic SEO advice unless directly relevant to the page
  • Include direct examples from the page when possible
  • Quote titles, headings, or metadata when relevant
  • Prioritize issues based on estimated SEO impact and crawl/indexation importance

Conversion SEO

  • CTA visibility and clarity
  • Above-the-fold messaging alignment
  • Trust signals (reviews, guarantees, proof elements)
  • UX friction impacting conversions
  • Search intent to conversion alignment

Required Output Format

Page Score Card

Overall Score: XX/100

  • On-Page SEO: XX/100
  • Content Quality: XX/100
  • Technical: XX/100
  • Schema: XX/100
  • Images: XX/100
  • SERP Alignment: XX/100
  • Conversion SEO: XX/100

Strengths

  • List what the page already does well

Critical Issues

  • Highest priority SEO problems

High Priority Improvements

  • Important ranking improvements

Medium Priority Improvements

  • Secondary optimizations

Low Priority Improvements

  • Minor enhancements

SERP & Competitor Analysis

  • Compare page structure vs top-ranking competitors
  • Identify missing sections or content gaps
  • Identify SERP differentiation opportunities

Recommended Metadata

Title Tag: [optimized version]

Meta Description: [optimized version]

H1: [optimized version]


Schema Recommendations

  • Recommended structured data opportunities
  • Include JSON-LD examples when applicable

Internal Linking Recommendations

  • Suggested parent collections
  • Suggested related collections
  • Suggested anchor text opportunities

Final SEO Summary

  • Summarize biggest opportunities for ranking improvements |

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.