rome-os
rome-os/rome-apps
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/rome-os/rome-apps --skill on-page-seo-auditor命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use for creative/product/design work before implementation. Guides the guardian from rough idea to approved design spec.
Senior engineer code review workflow — whole-picture understanding, mandatory beyond-the-diff verification, architecture-level review (SSOT, Occam's razor), SOLID, security, performance, and code quality, with P0-P3 severity classification.
Fetch GitHub pull request diffs with gh CLI, including large-PR fallback strategies.
正在显示 SKILL.md
| name | on-page-seo-auditor |
| description | Audit on-page SEO: titles, headers, images, links with scored report and fix priorities. 页面SEO审计/排名诊断 |
| version | 6.0.0 |
| license | Apache-2.0 |
| compatibility | Claude Code ≥1.0, skills.sh marketplace, ClawHub marketplace, Vercel Labs skills ecosystem. No system packages required. Optional: MCP network access for SEO tool integrations. |
| homepage | https://github.com/aaron-he-zhu/seo-geo-claude-skills |
| tools | ["WebFetch"] |
| metadata | {"author":"aaron-he-zhu","version":"6.0.0","geo-relevance":"medium","tags":["seo","on-page-audit","page-optimization","seo-score","content-audit","h1-optimization","meta-audit","seo-checklist","yoast-alternative","screaming-frog-alternative","页面SEO","网页优化","ページSEO","페이지감사","auditoria-seo"],"triggers":["audit page SEO","on-page SEO check","SEO score","page optimization","on-page audit","SEO page analysis","content audit","what SEO issues does this page have","check my page","score my page","why isn't this page ranking","what's wrong with this page's SEO","is my page optimized","my rankings tanked","why did my rankings drop","why is my page not ranking","how do I improve my page SEO","what SEO problems does this page have","Screaming Frog alternative","Yoast SEO alternative","页面SEO审计","网页优化检查","SEO评分","页面诊断","页面优化分析","页面有什么问题","为什么排不上去","检查一下我的页面","SEO打分","排名上不去怎么办","网页收录问题","ページSEO監査","オンページSEO","ページ最適化","SEOスコア","페이지 SEO 감사","온페이지 SEO","SEO 점수","이 페이지 뭐가 문제야?","왜 순위가 안 올라가?","SEO 점수 확인해줘","auditoría SEO on-page","análisis de página SEO","puntuación SEO","auditoria SEO on-page","on page SEO aduit","SEO scroe"]} |
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.
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 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]
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.