Audit on-page SEO: titles, headers, images, links with scored report and fix priorities. 页面SEO审计/排名诊断
60
71%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.cursor/skills/on-page-seo-auditor/SKILL.mdSEO & 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.
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.
Start with one of these prompts. Finish with a short handoff summary using the repository format in Skill Contract.
Audit the on-page SEO of [URL]Check SEO issues on this page targeting [keyword]: [URL/content]Compare on-page SEO of [your URL] vs [competitor URL] for [keyword]Pre-publish SEO audit for this content targeting [keyword]: [content]Expected output: a scored diagnosis, prioritized repair plan, and a short handoff summary ready for memory/audits/.
memory/audits/.memory/open-loops.md and memory/decisions.md.Next Best Skill below when the repair path is clear.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:
Proceed with the full audit using provided data. Note in the output which findings are from automated crawl vs. manual review.
When a user requests an on-page SEO audit:
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]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]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)Audit Header Structure
## Header Structure Analysis
### Current Header HierarchyH1: [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]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).
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).
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).
Audit Images — Alt text, file names, sizes, formats, lazy loading
Reference: See references/audit-templates.md for the image optimization template (Step 8).
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).
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.
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).
Reference: See references/audit-example.md for a full worked example (noise-cancelling headphones audit) and page-type checklists (blog post, product page, landing page).
Scoring details: For the complete weight distribution, scoring scale, issue resolution playbook, and industry benchmarks, see references/scoring-rubric.md.
After delivering audit or optimization findings to the user, ask:
"Save these results for future sessions?"
If yes, write a dated summary to memory/audits/on-page-seo-auditor/YYYY-MM-DD-<topic>.md containing:
If any veto-level issue was found (CORE-EEAT T04, C01, R10 or CITE T03, T05, T09), also append a one-liner to memory/hot-cache.md without asking.
3b319ce
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.