on-page-seo-auditor

Overview of on-page-seo-auditor skill

What the on-page-seo-auditor skill does

The on-page-seo-auditor skill evaluates a single page’s on-page SEO and turns the review into a scored report with prioritized fixes. It focuses on the elements teams usually need first when a page is underperforming: title tag, meta description, headers, content quality, keyword usage, internal links, images, and basic technical signals.

Who should use it

This skill is best for SEO specialists, content marketers, editors, growth teams, and site owners who want a structured page audit without manually building a rubric every time. It is especially useful when the real question is not “teach me SEO,” but “tell me why this page is not ranking and what to fix first.”

Job to be done

Most users adopt on-page-seo-auditor to diagnose one URL against one target keyword, then leave with an action list they can hand to a writer, editor, or developer. The value is not just a checklist. It is the combination of:

• a repeatable scoring model
• section-by-section analysis
• fix priorities
• output templates that keep audits consistent across pages

What makes this skill different

Compared with a generic “audit this page” prompt, the on-page-seo-auditor skill has stronger operating structure. The repository includes:

• a worked audit example in references/audit-example.md
• reusable output patterns in references/audit-templates.md
• a scoring system in references/scoring-rubric.md

That matters if you need audits that are comparable over time or across URLs, not just one-off commentary.

Best-fit and misfit cases

Best fit:

• auditing a landing page, blog post, roundup, product page, or similar URL
• checking whether a page aligns with a primary keyword and search intent
• creating a practical optimization brief for content updates

Less ideal:

• full-site crawling
• deep technical SEO audits
• log-file analysis, indexation debugging, or backlink work
• situations where you cannot provide the page URL or page content

How to Use on-page-seo-auditor skill

Install context for on-page-seo-auditor

The repository does not expose a skill-specific install command in SKILL.md, so most users install from the parent skill collection, then call this skill by name from their AI skill environment. The common install pattern is:

npx skills add aaron-he-zhu/seo-geo-claude-skills --skill on-page-seo-auditor

The skill declares compatibility with Claude Code, skills.sh marketplace, ClawHub, and the Vercel Labs skills ecosystem. No system packages are required. WebFetch is the key allowed tool, and optional network/MCP access can help if your setup supports external SEO tooling.

What inputs the skill needs

For useful output, give the skill more than a URL. At minimum, provide:

• the page URL
• the primary target keyword
• page type, if known
• any important secondary keywords
• business goal or conversion goal

Strong optional inputs:

• country or language target
• audience segment
• known competitors
• whether the page is informational, commercial, transactional, or navigational
• recent ranking drop context

Without a target keyword, the audit can still review page quality, but the scoring around intent match and keyword placement becomes less decisive.

Turn a rough request into a good prompt

Weak prompt:

• “Check my page SEO”

Better prompt:

• “Use the on-page-seo-auditor skill to audit https://example.com/best-noise-cancelling-headphones for the keyword best noise cancelling headphones. Page type is commercial roundup. Secondary keywords: wireless noise cancelling headphones, ANC headphones. Evaluate title, meta, H1-H3 structure, content gaps, internal links, image alt text, and technical basics. Give me a scored report and top 5 fixes by impact.”

This works better because it gives the skill the target query, likely intent, and output expectations.

Suggested prompt format for SEO Content teams

If you are using on-page-seo-auditor for SEO Content workflows, use a prompt shape like this:

• URL: ...
• Primary keyword: ...
• Secondary keywords: ...
• Page type: blog post / product page / landing page / comparison / roundup
• Audience: ...
• Market: ...
• Main conversion goal: ...
• Known issue: not ranking / rankings dropped / low CTR / weak engagement
• Output needed: scored audit + prioritized fixes + rewrite suggestions

This reduces ambiguity and improves prioritization.

What the audit output usually covers

Based on the references and rubric, the on-page-seo-auditor skill is designed to score eight main sections:

• title tag
• meta description
• header structure
• content quality
• keyword optimization
• internal links
• images
• technical elements

The repository’s scoring rubric assigns weights, which is useful if you need consistent audits rather than impressionistic advice.

Read these repository files first

If you want to understand how the skill thinks before you rely on it, read these in order:

1. SKILL.md
2. references/scoring-rubric.md
3. references/audit-example.md
4. references/audit-templates.md

Why this order:

• SKILL.md shows scope and workflow
• the rubric tells you how scores are derived
• the worked example shows the final report shape
• the templates help you adapt output for your own process

Practical workflow for a single-page audit

A reliable on-page-seo-auditor usage flow looks like this:

1. Choose one URL and one primary keyword.
2. Identify the page type and likely search intent.
3. Run the audit with the URL, keyword, and context.
4. Review the weighted scores, not just the total score.
5. Fix the highest-impact weaknesses first, usually title, intent alignment, content gaps, and internal linking.
6. Re-run the audit after updates to check whether the score and priority issues improved.

This is better than auditing many pages loosely, because the skill is strongest as a focused page diagnosis tool.

Tips that materially improve output quality

A few inputs noticeably change result quality:

• Tell the skill whether the page targets informational or commercial intent.
• Provide the exact keyword, not a topic label.
• Mention if the page is a refresh of older content.
• Ask for fix priority by impact and effort, not just issue listing.
• Ask it to separate “quick wins” from “requires rewrite” items.

These details help the model avoid generic SEO advice and produce implementation-ready recommendations.

How to use it when rankings dropped

If your real use case is “this page used to rank,” say so directly. Include:

• approximate date of decline
• what changed on the page, if anything
• whether impressions, clicks, or CTR fell
• whether competitors updated their content

The on-page-seo-auditor skill is still not a replacement for Search Console or crawl diagnostics, but this context helps it frame the page-level audit around probable causes instead of static best practices only.

Boundaries to know before install

This is not a crawler or a complete Screaming Frog replacement. It is closer to a structured page-review framework. That means:

• excellent for one-page diagnosis and editorial fixes
• weaker for sitewide duplicate-title detection
• weaker for JavaScript rendering issues and advanced technical SEO
• dependent on access to the page content or URL fetchability

If your need is portfolio-wide QA, this skill is best used alongside a crawler, not instead of one.

on-page-seo-auditor skill FAQ

Is on-page-seo-auditor skill good for beginners?

Yes, if you already know what page you want to audit. The templates and scoring rubric reduce guesswork. Beginners may still need help interpreting tradeoffs, but the skill is more usable than a blank-page prompt because it imposes an audit structure.

What is the main advantage over a normal prompt?

The main difference is consistency. A normal prompt might give decent advice once. The on-page-seo-auditor skill gives you a repeatable audit pattern, weighted scoring, and examples you can reuse across multiple content reviews.

Can I use on-page-seo-auditor for any page type?

Mostly yes, but results are best when you state the page type. A blog article, product page, landing page, and roundup page should not be judged exactly the same way. The references explicitly point toward page-type-aware auditing.

Does it require external SEO tools?

No. The skill can operate as a structured audit without external tools. Optional network or MCP integrations may help in some environments, but they are not required to get useful page-level recommendations.

Is this a full technical SEO audit?

No. on-page-seo-auditor focuses on on-page factors and light technical elements visible in a page audit. It is not the right tool for crawl budget, log analysis, canonicalization at scale, or indexation troubleshooting.

Is it useful for SEO Content teams?

Yes. This is one of the better fits for on-page-seo-auditor for SEO Content because it converts a vague quality review into a content optimization brief. Writers and editors can act on recommendations around headings, topic coverage, keyword placement, internal links, and missing content elements.

When should I not use this skill?

Do not use it as your only workflow when:

• you need sitewide audits
• rankings problems are likely caused by authority, links, or indexing
• you cannot specify a target keyword
• you need a competitive SERP analysis rather than a page audit

How to Improve on-page-seo-auditor skill

Give the skill a tighter search target

The fastest way to improve on-page-seo-auditor results is to narrow the target. Use one primary keyword, not a bundle of loosely related phrases. If you have multiple intents, run separate audits or clearly label the main one.

Provide page type and intent explicitly

A common failure mode is scoring a page against the wrong intent. For example, a product page evaluated like an informational guide will get misleading content recommendations. Tell the skill whether the page is:

• informational
• commercial investigation
• transactional
• local
• branded/navigation-focused

This changes what “good” looks like.

Ask for evidence-backed recommendations

If the first output feels generic, refine the next prompt:

• ask it to cite the exact page element causing the score
• ask for rewrite suggestions for title, meta, H1, and weak sections
• ask for a before/after optimization table
• ask it to separate observed issues from inferred issues

That pushes the skill from “SEO commentary” toward “actionable audit.”

Improve scoring usefulness, not just score accuracy

Users often focus too much on the final number. A better use of on-page-seo-auditor is to improve decision quality:

• which issues are blocking relevance
• which issues are depressing CTR
• which issues are weakening depth or trust
• which fixes are fastest to ship

Request priorities by impact, confidence, and effort to make the report more operational.

Use the references to calibrate your expectations

The support files are not filler. They materially improve usage:

• references/scoring-rubric.md helps you understand why a page scored poorly
• references/audit-example.md shows the expected specificity level
• references/audit-templates.md helps you standardize outputs across a team

If your first run looks too shallow, compare it to the worked example and tighten your prompt to match that structure.

Common failure modes to watch for

Typical weak outputs come from weak inputs:

• no target keyword
• no page type
• no audience or market context
• asking for “everything wrong” instead of prioritized fixes
• expecting sitewide conclusions from one URL

Most bad outcomes are prompt-shaping problems, not repository problems.

How to iterate after the first audit

A good second pass prompt is often better than a longer first prompt. After the initial report, ask:

• “Re-rank the issues by likely ranking impact.”
• “Rewrite the title, meta description, and H1 based on this audit.”
• “Turn the content gaps into an editor brief.”
• “Give me only quick wins I can ship today.”
• “Re-audit after these edits and compare score changes.”

This turns the on-page-seo-auditor skill into a revision workflow rather than a one-time diagnosis.

Best way to use on-page-seo-auditor with other skills

This skill pairs well with keyword research, content brief, and rewrite-oriented skills. Use it after keyword targeting is decided but before or during page revisions. In practice:

1. choose the keyword
2. audit the page
3. rewrite the weak on-page elements
4. re-audit for consistency

That sequence is usually more productive than trying to audit before the page’s target query is clear.