SEO诊断审计

SKILL内容创作
内容创作 未标注权限 许可证不明确
安装这个技能

网站SEO体检:抓取指定页面或读取本地HTML文件,逐项检查标题/描述/标题层级/内链/图片alt/结构化数据等SEO要素,输出可执行优化清单与健康评分。当用户说'SEO检查/网站诊断/搜索排名上不去/SEO优化建议/收录问题'时使用。支持本地HTML文件或指定URL两种分析方式。

一句话选型结论

按资料字段整理

SEO诊断审计是内容创作类的 Agent Skill,安装方式未标注,权限级别未标注,许可证不明确,有可直接复制的安装命令。技能本质是给模型读的说明书,效果取决于模型与客户端;装完先用一个小任务验证,再放进正式流程。

分类内容创作 安装方式未标注 权限级别未标注权限 许可证许可证不明确
累计安装 未标注 本周 未标注
GitHub 星标 未标注 仓库 未标注
下载量 未标注 技能市场下载数
权限级别 未标注权限 安装前请确认风险范围
许可证 许可证不明确 未说明

安装

未标注
在支持 Skills 的客户端里执行,装完问一句「你有哪些技能」验证
skillhub install user_de9e22a1/seo-health-scan
  1. 1
    确认客户端支持

    确认你的客户端支持 Skills(Claude、Codex、Cursor 等),并升级到较新的版本。

  2. 2
    拿到技能文件

    执行上面的命令安装;也可以把仓库里的 SKILL.md 手动放进客户端的 skills 目录。

  3. 3
    刷新技能列表

    重新打开客户端,或刷新技能列表,让新放进来的技能被加载。

  4. 4
    验证是否生效

    问一句「你有哪些技能」,确认列表里出现它,再拿一个小任务试跑。

技能档案

内容创作
字段来自技能仓库与公开索引,中文说明由本站标注
作者 / 维护方user_de9e22a1仓库 未标注 · 版本 未标注
宿主客户端未标注技能可被这些客户端加载
安装方式未标注安装包 community
权限级别未标注权限安装前请确认风险范围
许可证未说明许可证不明确,商用前请自行确认条款
仓库可用性available技能仓库当前是否可访问
最近核验2026-11-06上游最后核验时间 · 数据更新 2026-11-06
正文体量7.8 KBSKILL.md 原文大小,越大说明说明书写得越细

典型使用场景

3 类
按分类整理的常见用法,具体以 SKILL.md 为准
写文章与脚本

按主题产出初稿与分镜脚本。

改稿与润色

把草稿改顺、统一语气。

多平台文案改写

同一内容按平台改成长短不同的版本。

选择建议

装之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有可直接复制的安装命令,不用自己翻文档找入口。

先想清楚的地方

  • 没有标注权限级别,实际能做什么要装好后确认。
  • 许可证不明确,商用或二次分发前先到仓库确认条款。
  • 没有做站内核验,内容以作者仓库为准。
  • 技能只是说明书,实际效果取决于模型与客户端,装完先用小任务试一遍。

更适合

  • 需要在内容创作场景里给模型补一套做法的人。
  • 愿意先读一遍 SKILL.md、确认它会让模型做什么的人。

不太适合

  • 对许可证要求很严、必须明确可商用的人。
  • 只想装完就自动变强、不打算看说明书的人。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
技能权限级别安装方式累计安装宿主客户端安装命令
SEO诊断审计当前 未标注权限 未标注 未标注 未标注 有
AI 视频生成 调用外部服务 GitHub 仓库 431.3 万 Codex、Claude、Cursor 有
视频帧 联网访问 ClawHub 市场 262.1 万 OpenClaw 有
Markdown 转换器 写入文件 ClawHub 市场 135.3 万 OpenClaw 有
哔哩哔哩全合一 接触敏感数据 ClawHub 市场 64.1 万 OpenClaw 有
Remotion video toolkit 命令行 浏览器控制 ClawHub 市场 63.9 万 OpenClaw 有

SKILL.md 全文

7.8 KB
模型实际读到的说明书原文,来自技能仓库

> 移植说明:本 Skill 收录于 alirezarezvani/claude-skills(MIT 协议),移植到 SkillHub/WorkBuddy 供中文用户使用,正文方法论保持原样,输出可要求用中文呈现。
> 脚本会按用户指令抓取待审计页面URL,仅此一处联网行为。

SEO Audit

You are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.

Initial Assessment

Check for product marketing context first:
If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before auditing, understand:

  1. Site Context
    - What type of site? (SaaS, e-commerce, blog, etc.)
    - What's the primary business goal for SEO?
    - What keywords/topics are priorities?

  2. Current State
    - Any known issues or concerns?
    - Current organic traffic level?
    - Recent changes or migrations?

  3. Scope
    - Full site audit or specific pages?
    - Technical + on-page, or one focus area?
    - Access to Search Console / analytics?


Audit Framework

The audit walks three layers — technical (crawl/indexation/speed), on-page (titles, headings, internal links, keyword targeting), content (intent match, E-E-A-T, thin/duplicate pages). Full framework: references/seo-audit-reference.md.

Core Web Vitals pass/fail thresholds (75th percentile of real-user data; full triage in references/cwv-thresholds.md):

Metric Good Needs improvement Poor
LCP (Largest Contentful Paint) ≤ 2.5s 2.5-4.0s > 4.0s
INP (Interaction to Next Paint) ≤ 200ms 200-500ms > 500ms
CLS (Cumulative Layout Shift) ≤ 0.1 0.1-0.25 > 0.25

Tools

Tool Invocation Output
On-page checker python3 scripts/seo_checker.py --file page.html (or --url https://...; --json) Scores a single page 0-100: title/meta/headings/links/images
Health scorer python3 scripts/seo_health_scorer.py --checks checks.json --industry saas (no arg = --demo; industries: saas/ecommerce/local/publisher; --json) Weighted 0-100 site health score across 7 categories

Run seo_checker.py on the key templates/pages during the on-page layer, and seo_health_scorer.py on the completed check matrix to produce the audit's headline score.

Output Format

Audit Report Structure

Executive Summary
- Overall health assessment — lead with the seo_health_scorer.py score and its weakest categories
- Top 3-5 priority issues
- Quick wins identified

Technical SEO Findings
For each issue:
- Issue: What's wrong
- Impact: SEO impact (High/Medium/Low)
- Evidence: How you found it
- Fix: Specific recommendation
- Priority: 1-5 or High/Medium/Low

On-Page SEO Findings
Same format as above

Content Findings
Same format as above

Prioritized Action Plan
1. Critical fixes (blocking indexation/ranking)
2. High-impact improvements
3. Quick wins (easy, immediate benefit)
4. Long-term recommendations


References

  • SEO Audit Reference: Full audit framework, scoring, and remediation patterns
  • Core Web Vitals Thresholds: LCP/INP/CLS targets and triage rules
  • E-E-A-T Framework: Experience, Expertise, Authoritativeness, Trustworthiness checklist
  • Schema Types: Structured data patterns by content type

Tools Referenced

Free Tools
- Google Search Console (essential)
- Google PageSpeed Insights
- Bing Webmaster Tools
- Rich Results Test
- Mobile-Friendly Test
- Schema Validator

Paid Tools (if available)
- Screaming Frog
- Ahrefs / Semrush
- Sitebulb
- ContentKing


Task-Specific Questions

  1. What pages/keywords matter most?
  2. Do you have Search Console access?
  3. Any recent changes or migrations?
  4. Who are your top organic competitors?
  5. What's your current organic traffic baseline?

Related Skills

  • programmatic-seo — WHEN: user wants to build SEO pages at scale after the audit identifies keyword gaps. WHEN NOT: don't use for diagnosing existing issues; stay in seo-audit mode.
  • aeo — WHEN: user wants to optimize for AI answer engines (SGE, Perplexity, ChatGPT) in addition to traditional search. WHEN NOT: don't use for purely technical crawl/indexation issues.
  • schema-markup — WHEN: audit reveals missing structured data opportunities (FAQ, HowTo, Product, Review schemas). WHEN NOT: don't use as a standalone fix when core technical SEO is broken.
  • site-architecture — WHEN: audit uncovers poor internal linking, orphan pages, or crawl depth issues that need a structural redesign. WHEN NOT: don't involve when the audit scope is limited to on-page or content issues.
  • content-strategy — WHEN: audit reveals thin content, keyword gaps, or lack of topical authority requiring a content plan. WHEN NOT: don't use when the problem is purely technical (robots.txt, redirects, speed).
  • marketing-context — WHEN: always read first if .claude/product-marketing-context.md exists to avoid redundant questions. WHEN NOT: skip if no context file exists and user has provided all necessary product info directly.

Communication

All audit output follows the SEO Audit Quality Standard:
- Lead with the executive summary (3-5 bullets max)
- Findings use the Issue / Impact / Evidence / Fix / Priority format consistently
- Prioritized Action Plan is always the final deliverable section
- Avoid jargon without explanation; write for a technically-aware but non-SEO-specialist reader
- Quick wins are called out explicitly and kept separate from high-effort recommendations
- Never present recommendations without evidence or rationale


Proactive Triggers

Automatically surface seo-audit recommendations when:

  1. Traffic drop mentioned — User says organic traffic dropped or rankings fell; immediately frame an audit scope.
  2. Site migration or redesign — User mentions a planned or recent URL change, platform switch, or redesign; flag pre/post-migration audit needs.
  3. "Why isn't my page ranking?" — Any ranking frustration triggers the on-page + intent checklist before external factors.
  4. Content strategy discussion — When content-strategy skill is active and keyword gaps appear, proactively suggest an SEO audit to validate opportunity.
  5. New site or product launch — User preparing a launch; proactively recommend a technical SEO pre-launch checklist from the audit framework.

Output Artifacts

Artifact Format Description
Executive Summary Markdown bullets 3-5 top issues + quick wins, suitable for sharing with stakeholders
Technical SEO Findings Structured table Issue / Impact / Evidence / Fix / Priority per finding
On-Page SEO Findings Structured table Same format, focused on content and metadata
Prioritized Action Plan Numbered list Ordered by impact × effort, grouped into Critical / High / Quick Wins
Keyword Cannibalization Map Table Pages competing for same keyword with recommended canonical or redirect actions

常见问题

5 问
答案由本站依据条目字段整理
SEO诊断审计怎么安装?

在支持 Skills 的客户端里执行:skillhub install user_de9e22a1/seo-health-scan。安装方式为未标注。装完刷新技能列表或重开客户端。

SEO诊断审计支持哪些客户端?

资料没有标注宿主客户端,但只要客户端支持 Skills(Claude、Codex、Cursor 等),一般都能加载。

SEO诊断审计权限高吗,安全吗?

权限级别为未标注权限。安装前先看它会读取或写入哪些内容。

SEO诊断审计收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于技能本身和所用的模型或客户端,正式使用前按作者说明确认。

SEO诊断审计用什么许可证?

许可证标注为 未说明(许可证不明确)。商用或二次分发前请到仓库确认条款原文。

热门专题

按场景挑技能
全部专题 →

技能内容以作者仓库为准;分类、权限级别与许可证状态的中文说明为中文整理,最近核验 2026-11-06。