on-page-seo-auditor

aaron-he-zhu/seo-geo-claude-skills · updated May 7, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/aaron-he-zhu/seo-geo-claude-skills --skill on-page-seo-auditor
0 commentsdiscussion
summary

Comprehensive on-page SEO audits identifying title tags, meta descriptions, headers, content quality, keywords, internal links, and image optimization.

  • Analyzes 8+ on-page elements with scoring rubrics: title tags, meta descriptions, header hierarchy, content depth, keyword placement, internal linking structure, image alt text, and technical factors like canonicals and mobile optimization
  • Supports single-page audits, competitor comparisons, and pre-publish content reviews with actionabl
skill.md

On-Page SEO Auditor

SEO & GEO Skills Library · 20 skills for SEO + GEO · ClawHub · skills.sh System Mode: This optimization skill follows the shared Skill Contract and State Model.

This skill performs detailed on-page SEO audits to identify issues and optimization opportunities. It analyzes all on-page elements that affect search rankings and provides actionable recommendations.

System role: Optimization layer skill. It turns weak pages, structures, and technical issues into prioritized repair work.

When This Must Trigger

Use this when the conversation involves any of these situations — even if the user does not use SEO terminology:

Use this whenever the task needs a diagnosis or repair plan that should feed directly into remediation work, not just a one-time opinion.

  • Auditing pages before or after publishing
  • Identifying why a page isn't ranking well
  • Optimizing existing content for better performance
  • Creating pre-publish SEO checklists
  • Comparing your on-page SEO to competitors
  • Systematic site-wide SEO improvements
  • Training team members on SEO best practices

What This Skill Does

  1. Title Tag Analysis: Evaluates title optimization and CTR potential
  2. Meta Description Review: Checks description quality and length
  3. Header Structure Audit: Analyzes H1-H6 hierarchy
  4. Content Quality Assessment: Reviews content depth and optimization
  5. Keyword Usage Analysis: Checks keyword placement and density
  6. Internal Link Review: Evaluates internal linking structure
  7. Image Optimization Check: Audits alt text and file optimization
  8. Technical On-Page Review: Checks URL, canonical, and mobile factors

Quick Start

Start with one of these prompts. Finish with a short handoff summary using the repository format in Skill Contract.

Audit a Single Page

Audit the on-page SEO of [URL]
Check SEO issues on this page targeting [keyword]: [URL/content]

Compare Against Competitors

Compare on-page SEO of [your URL] vs [competitor URL] for [keyword]

Audit Content Before Publishing

Pre-publish SEO audit for this content targeting [keyword]: [content]

Skill Contract

Expected output: a scored diagnosis, prioritized repair plan, and a short handoff summary ready for memory/audits/.

  • Reads: the current page or site state, symptoms, prior audits, and current priorities from CLAUDE.md and the shared State Model when available.
  • Writes: a user-facing audit or optimization plan plus a reusable summary that can be stored under memory/audits/.
  • Promotes: blocking defects, repeated weaknesses, and fix priorities to memory/open-loops.md and memory/decisions.md.
  • Next handoff: use the Next Best Skill below when the repair path is clear.

Data Sources

See CONNECTORS.md for tool category placeholders.

With ~~SEO tool + ~~web crawler connected: Claude can automatically pull page HTML via ~~web crawler, fetch keyword search volume and difficulty from ~~SEO tool, retrieve click-through rate data from ~~search console, and download competitor pages for comparison. This enables fully automated audits with live data.

With manual data only: Ask the user to provide:

  1. Page URL or complete HTML content
  2. Target primary and secondary keywords
  3. Competitor page URLs for comparison (optional)

Proceed with the full audit using provided data. Note in the output which findings are from automated crawl vs. manual review.

Instructions

When a user requests an on-page SEO audit:

  1. Gather Page Information

    ### Audit Setup
    
    **Page URL**: [URL]
    **Target Keyword**: [primary keyword]
    **Secondary Keywords**: [additional keywords]
    **Page Type**: [blog/product/landing/service]
    **Business Goal**: [traffic/conversions/authority]
    
  2. Audit Title Tag

    ## Title Tag Analysis
    
    **Current Title**: [title]
    **Character Count**: [X] characters
    
    | Criterion | Status | Notes |
    |-----------|--------|-------|
    | Length (50-60 chars) | ✅/⚠️/❌ | [notes] |
    | Keyword included | ✅/⚠️/❌ | Position: [front/middle/end] |
    | Keyword at front | ✅/⚠️/❌ | [notes] |
    | Unique across site | ✅/⚠️/❌ | [notes] |
    | Compelling/clickable | ✅/⚠️/❌ | [notes] |
    | Matches intent | ✅/⚠️/❌ | [notes] |
    
    **Title Score**: [X]/10
    
    **Issues Found**:
    - [Issue 1]
    - [Issue 2]
    
    **Recommended Title**:
    "[Optimized title suggestion]"
    
    **Why**: [Explanation of improvements]
    
  3. Audit Meta Description

    ## Meta Description Analysis
    
    **Current Description**: [description]
    **Character Count**: [X] characters
    
    | Criterion | Status | Notes |
    |-----------|--------|-------|
    | Length (150-160 chars) | ✅/⚠️/❌ | [notes] |
    | Keyword included | ✅/⚠️/❌ | [notes] |
    | Call-to-action present | ✅/⚠️/❌ | [notes] |
    | Unique across site | ✅/⚠️/❌ | [notes] |
    | Accurately describes page | ✅/⚠️/❌ | [notes] |
    | Compelling copy | ✅/⚠️/❌ | [notes] |
    
    **Description Score**: [X]/10
    
    **Issues Found**:
    - [Issue 1]
    
    **Recommended Description**:
    "[Optimized description suggestion]" ([X] chars)
    
  4. Audit Header Structure

    ## Header Structure Analysis
    
    ### Current Header Hierarchy
    
    

    H1: [H1 text] H2: [H2 text] H3: [H3 text] H3: [H3 text] H2: [H2 text] H3: [H3 text] H2: [H2 text]

    
    | Criterion | Status | Notes |
    |-----------|--------|-------|
    | Single H1 | ✅/⚠️/❌ | Found: [X] H1s |
    | H1 includes keyword | ✅/⚠️/❌ | [notes] |
    | Logical hierarchy | ✅/⚠️/❌ | [notes] |
    | H2s include keywords | ✅/⚠️/❌ | [X]/[Y] contain keywords |
    | No skipped levels | ✅/⚠️/❌ | [notes] |
    | Descriptive headers | ✅/⚠️/❌ | [notes] |
    
    **Header Score**: [X]/10
    
    **Issues Found**:
    - [Issue 1]
    - [Issue 2]
    
    **Recommended Changes**:
    - H1: [suggestion]
    - H2s: [suggestions]
    
  5. Audit Content Quality — Word count, reading level, comprehensiveness, formatting, E-E-A-T signals, content elements checklist, gap identification

    Reference: See references/audit-templates.md for the content quality template (Step 5).

  6. Audit Keyword Usage — Primary/secondary keyword placement across all page elements, LSI/related terms, density analysis

    Reference: See references/audit-templates.md for the keyword optimization template (Step 6).

  7. Audit Internal Links — Link count, anchor text relevance, broken links, recommended additions

    Reference: See references/audit-templates.md for the internal linking template (Step 7).

  8. Audit Images — Alt text, file names, sizes, formats, lazy loading

    Reference: See references/audit-templates.md for the image optimization template (Step 8).

  9. Audit Technical On-Page Elements — URL, canonical, mobile, speed, HTTPS, schema

    Reference: See references/audit-templates.md for the technical on-page template (Step 9).

  10. CORE-EEAT Content Quality Quick Scan — 17 on-page-relevant items from the 80-item CORE-EEAT benchmark

    Reference: See references/audit-templates.md for the CORE-EEAT quick scan template (Step 10). Full benchmark: CORE-EEAT Benchmark.

  11. Generate Audit Summary — Overall score with visual breakdown, priority issues (critical/important/minor), quick wins, detailed recommendations, competitor comparison, action checklist, expected results

    Reference: See references/audit-templates.md for the full audit summary template (Step 11).

Validation Checkpoints

Input Validation

  • Target keyword(s) clearly specified by user
  • Page content accessible (either via URL or provided HTML)
  • If competitor comparison requested, competitor URL provided

Output Validation

  • Every recommendation cites specific data points (not generic advice)
  • Scores based on measurable criteria, not subjective opinion
  • All suggested changes includ
how to use on-page-seo-auditor

How to use on-page-seo-auditor on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add on-page-seo-auditor
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/aaron-he-zhu/seo-geo-claude-skills --skill on-page-seo-auditor

The skills CLI fetches on-page-seo-auditor from GitHub repository aaron-he-zhu/seo-geo-claude-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/on-page-seo-auditor

Reload or restart Cursor to activate on-page-seo-auditor. Access the skill through slash commands (e.g., /on-page-seo-auditor) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.652 reviews
  • Chaitanya Patil· Dec 28, 2024

    Keeps context tight: on-page-seo-auditor is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Emma Robinson· Dec 28, 2024

    Keeps context tight: on-page-seo-auditor is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Ama Ndlovu· Dec 16, 2024

    Solid pick for teams standardizing on skills: on-page-seo-auditor is focused, and the summary matches what you get after install.

  • Neel Haddad· Dec 4, 2024

    Registry listing for on-page-seo-auditor matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Ira Agarwal· Nov 23, 2024

    Useful defaults in on-page-seo-auditor — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Piyush G· Nov 19, 2024

    on-page-seo-auditor has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Ama Yang· Nov 19, 2024

    on-page-seo-auditor has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Evelyn Thompson· Nov 15, 2024

    on-page-seo-auditor fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Aditi Reddy· Nov 7, 2024

    on-page-seo-auditor is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Hana Sanchez· Nov 3, 2024

    Solid pick for teams standardizing on skills: on-page-seo-auditor is focused, and the summary matches what you get after install.

showing 1-10 of 52

1 / 6