seo-site-health-audit
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseSEO Site Health Audit
SEO网站健康审计
Triage technical SEO findings from Ahrefs Site Audit (or any equivalent crawler) by impact on rankings and traffic, not by raw issue count or severity label. Stack-agnostic. Produces a prioritized backlog of fixes mapped to business impact.
根据对排名和流量的影响（而非原始问题数量或严重性标签），对Ahrefs Site Audit（或任何同类爬虫工具）的技术SEO发现进行分类排序。与技术栈无关，可生成映射到业务影响的优先修复待办清单。
When to use
使用场景
- After running an Ahrefs Site Audit or other site-wide crawl
- Reviewing a long list of technical issues and needing to prioritize
- Scoping a technical SEO sprint
- Pre-launch or post-migration technical verification
- Quarterly technical health check
- When developer time is limited and you must pick the highest-leverage fixes
- 完成Ahrefs Site Audit或其他全站爬取后
- 审查冗长的技术问题列表并需要确定优先级时
- 规划技术SEO冲刺阶段
- 上线前或迁移后的技术验证
- 季度技术健康检查
- 开发人员时间有限，必须选择最高收益的修复工作时
When NOT to use
不适用场景
- Running the crawl itself (use the crawler tool directly)
- Diagnosing specific traffic drops (use )
seo-traffic-diagnosis - Single-page audits (use )
seo-onpage - Pure technical strategy or schema design (use )
seo-technical
- 执行爬取操作本身（直接使用爬虫工具）
- 诊断特定流量下降问题（使用）
seo-traffic-diagnosis - 单页面审计（使用）
seo-onpage - 纯技术策略或Schema设计（使用）
seo-technical
Required inputs
必要输入
- Crawl results from Ahrefs Site Audit (or equivalent)
- Search Console coverage and Core Web Vitals data
- Property's organic traffic profile (which pages drive traffic)
- Stakeholder time and developer capacity available
- Confirmation Ahrefs MCP is connected
- Ahrefs Site Audit（或同类工具）的爬取结果
- Search Console覆盖范围和Core Web Vitals数据
- 网站的自然流量概况（哪些页面带来流量）
- 相关人员的时间和开发人员的可用产能
- 确认已连接Ahrefs MCP
The framework: triage by SEO impact, not severity
框架：根据SEO影响而非严重性进行分类排序
Crawlers label issues "critical", "warning", "notice". These labels are useful but not sufficient. Two issues both labeled "critical" can have wildly different actual impact on the property.
Triage on three axes.
爬虫工具会将问题标记为“严重”“警告”“通知”。这些标签有用，但并不足够。两个均标记为“严重”的问题，对网站的实际影响可能天差地别。
从三个维度进行分类排序。
Axis 1: Page-level traffic impact
维度1：页面级流量影响
Does the issue affect a page that drives meaningful organic traffic, or one that does not?
A "critical" issue on a tag archive with zero traffic is lower priority than a "warning" on a top-10-traffic landing page.
Tier the affected URLs:
- Tier 1: Top 10% of pages by organic traffic
- Tier 2: Pages that rank but do not yet drive significant traffic (page 2-3 results)
- Tier 3: Pages that exist but do not rank meaningfully
A fix on Tier 1 is worth 10x a fix on Tier 3 in most cases.
该问题是否影响带来可观自然流量的页面？
一个零流量标签归档页面上的“严重”问题，优先级低于流量TOP10的着陆页上的“警告”问题。
对受影响的URL进行分层：
- 第一层（Tier 1）： 自然流量排名前10%的页面
- 第二层（Tier 2）： 有排名但尚未带来显著流量的页面（搜索结果第2-3页）
- 第三层（Tier 3）： 存在但无有效排名的页面
大多数情况下，第一层页面的修复价值是第三层页面的10倍。
Axis 2: Mechanism of impact
维度2：影响机制
Does the issue actually move rankings or traffic? Some "critical" issues are aesthetic or theoretical.
Categories of real impact:
| Mechanism | Examples |
|---|---|
| Indexability | Accidental noindex, robots.txt blocks, canonical errors, X-Robots-Tag |
| Crawlability | Crawl traps, infinite redirects, 5xx errors, slow server response |
| Renderability | JS errors blocking critical content, blocked resources |
| Core Web Vitals | LCP, INP, CLS in the poor band |
| Structured data | Errors on rich-result-eligible pages (not warnings) |
| Internal link integrity | 404s on internally linked URLs, broken canonicals |
| Hreflang | Errors on multilingual deployments |
Categories of low or theoretical impact:
| Type | Why it is lower priority |
|---|---|
| Title tag length warnings | Not a ranking factor in itself |
| Meta description length | Not a ranking factor |
| H1 absence on low-traffic pages | Marginal impact |
| Alt text missing on decorative images | Accessibility issue, low SEO impact |
| Schema warnings (not errors) | Often best-practice nudges, not ranking issues |
Fix the high-mechanism categories first.
该问题是否真的会影响排名或流量？有些“严重”问题只是美观或理论层面的。
实际影响的类别：
| 影响机制 | 示例 |
|---|---|
| 可索引性 | 意外设置noindex、robots.txt拦截、规范标签错误、X-Robots-Tag |
| 可爬取性 | 爬取陷阱、无限重定向、5xx错误、服务器响应缓慢 |
| 可渲染性 | JS错误阻止关键内容加载、资源被拦截 |
| Core Web Vitals | LCP、INP、CLS处于较差区间 |
| 结构化数据 | 符合富结果条件的页面上出现错误（而非警告） |
| 内部链接完整性 | 内部链接URL出现404错误、规范标签失效 |
| Hreflang | 多语言部署中的错误 |
低影响或理论影响的类别：
| 类型 | 优先级较低的原因 |
|---|---|
| 标题标签长度警告 | 本身并非排名因素 |
| 元描述长度 | 并非排名因素 |
| 低流量页面缺少H1标签 | 影响微乎其微 |
| 装饰性图片缺少替代文本 | 属于可访问性问题，对SEO影响低 |
| Schema警告（非错误） | 通常是最佳实践提示，而非排名问题 |
优先修复高影响机制类别的问题。
Axis 3: Effort
维度3：修复工作量
Some issues are 5-minute fixes. Some are multi-sprint projects.
- S (small): Configuration change, single template edit, sitemap regeneration
- M (medium): Theme or component change, redirect map work, template-level fixes
- L (large): Architecture change, re-platform, framework migration, schema overhaul
有些问题只需5分钟即可修复，有些则是跨多个冲刺阶段的项目。
- S（小）： 配置更改、单个模板编辑、站点地图重新生成
- M（中）： 主题或组件更改、重定向映射工作、模板级修复
- L（大）： 架构更改、平台迁移、框架迁移、Schema全面整改
The triage matrix
分类排序矩阵
Combine the three axes into a priority score.
| Tier | Mechanism | Effort | Priority |
|---|---|---|---|
| Tier 1 | High mechanism | S | P0 (do this week) |
| Tier 1 | High mechanism | M | P1 (do this sprint) |
| Tier 1 | High mechanism | L | P2 (plan as project) |
| Tier 1 | Low mechanism | S | P3 (batch when convenient) |
| Tier 1 | Low mechanism | M-L | Park unless evidence emerges |
| Tier 2 | High mechanism | S | P1 |
| Tier 2 | High mechanism | M-L | P2 |
| Tier 3 | High mechanism | S | P3 |
| Tier 3 | Anything else | Anything | Park |
P0-P1 work earns the team's attention. P2 goes on the roadmap. P3 batches into routine maintenance. Park is honest about deprioritization.
结合三个维度得出优先级分数。
| 层级 | 影响机制 | 工作量 | 优先级 |
|---|---|---|---|
| Tier 1 | 高影响 | S | P0（本周完成） |
| Tier 1 | 高影响 | M | P1（本次冲刺完成） |
| Tier 1 | 高影响 | L | P2（作为项目规划） |
| Tier 1 | 低影响 | S | P3（方便时批量处理） |
| Tier 1 | 低影响 | M-L | 暂搁置，除非出现相关证据 |
| Tier 2 | 高影响 | S | P1 |
| Tier 2 | 高影响 | M-L | P2 |
| Tier 3 | 高影响 | S | P3 |
| Tier 3 | 其他任何情况 | 任何工作量 | 暂搁置 |
P0-P1级工作需要团队重点关注，P2级工作纳入路线图，P3级工作归入例行维护批量处理，暂搁置则明确表示优先级降低。
Workflow
工作流程
- Pull the crawl results. Ahrefs Site Audit + Search Console + Core Web Vitals.
- Tier the URLs. Use organic traffic data. Tag every affected URL as Tier 1, 2, or 3.
- Categorize each issue by mechanism. High or low impact mechanism.
- Estimate effort per fix type. Group similar fixes into one effort estimate.
- Apply the triage matrix. Assign P0-P3 or Park.
- Cluster the fixes. Group fixes that share an effort: one template change can resolve hundreds of issues.
- Build the backlog. P0 first, P1 next, etc. Add fix descriptions, owners, expected impact.
- Add measurement. What metric will confirm the fix worked? Define before shipping.
- Hand off. Output feeds the development backlog and .
seo-audit-orchestration - Re-crawl after fixes. Confirm resolution. Update the backlog.
- 获取爬取结果：Ahrefs Site Audit + Search Console + Core Web Vitals数据。
- URL分层：使用自然流量数据，将每个受影响的URL标记为Tier 1、2或3。
- 按影响机制分类问题：分为高影响或低影响机制。
- 估算每种修复类型的工作量：将类似修复归为一类进行工作量估算。
- 应用分类排序矩阵：分配P0-P3或暂搁置。
- 聚类修复任务：将共享同一修复方案的任务分组。
- 构建待办清单：按P0、P1等顺序排列，每个任务包含：问题、受影响URL、修复说明、工作量、预期影响、负责人。
- 添加衡量指标：确定哪些指标可以验证修复有效？在修复前明确。
- 移交任务：输出结果用于开发待办清单和。
seo-audit-orchestration - 修复后重新爬取：确认问题已解决，更新待办清单。
High-leverage clusters worth looking for
值得关注的高收益聚类任务
These patterns commonly produce outsized impact when fixed:
- Wholesale redirect chain cleanup. One sitemap update plus internal link updates can resolve thousands of "redirect chain" issues at once.
- Accidental noindex on a template. A single line of code change can re-index hundreds or thousands of pages.
- Sitemap freshness pipeline. A broken sitemap regeneration job affects every issue that depends on Search Console seeing the right URLs.
- Canonical inconsistencies on faceted navigation. A template-level canonical fix can resolve duplicate content issues across an entire ecommerce category tree.
- Robots.txt restored. A reverted production robots.txt can recover a sitewide drop in days.
- Hreflang block fix. One template change resolves hreflang issues across the whole multilingual site.
- Image optimization at the asset pipeline. Fixing the build process resolves thousands of individual asset issues.
When you spot one of these, prioritize even if individual issues look small. The cluster impact is large.
以下模式修复后通常能带来巨大影响：
- 全面清理重定向链：一次站点地图更新加内部链接更新即可解决数千个“重定向链”问题。
- 模板意外设置noindex：一行代码更改即可重新索引数百或数千个页面。
- 站点地图更新流程修复：站点地图重新生成任务故障会影响所有依赖Search Console识别正确URL的问题。
- 分面导航的规范标签不一致：模板级规范标签修复可解决整个电商分类树的重复内容问题。
- 恢复Robots.txt：恢复生产环境的robots.txt可在数日内挽回全站流量下降。
- 修复Hreflang拦截问题：一次模板更改即可解决整个多语言站点的hreflang问题。
- 资产管道层面的图片优化：修复构建流程可解决数千个单独的资产问题。
当发现这些模式时，即使单个问题看起来很小，也要优先处理，因为聚类后的影响很大。
Failure patterns
常见错误模式
- Severity worship. Treating every "critical" label as truly critical. Many are not. Triage by mechanism and traffic impact.
- Counting issues. Reporting "we fixed 1,200 issues" without showing traffic or ranking impact wastes engineering credibility.
- Skipping the tiering. Fixing 100 Tier-3 issues before 5 Tier-1 issues is busy work.
- Single-issue fixes. Most issues come in clusters. Fixing one redirect chain when 800 share the same root cause is the wrong unit of work.
- No re-crawl. "Fixed" without verification leaves doubt. Always re-crawl after major fixes.
- Ignoring Search Console. Ahrefs sees what its crawler finds. Search Console reflects what Google actually sees and indexes. Use both.
- Treating Core Web Vitals like a checklist. CWV is field data, not lab data. Optimize for real-user experience, not synthetic scores.
- Fixing low-mechanism issues for show. A clean technical report with no traffic gain helps no one.
- Not measuring. Define the metric that proves the fix worked before fixing.
- 过度依赖严重性标签：将每个“严重”标签都视为真正的严重问题。很多并非如此，应根据影响机制和流量影响进行分类排序。
- 只统计问题数量：报告“我们修复了1200个问题”却不展示流量或排名影响，会浪费工程可信度。
- 跳过URL分层：先修复100个Tier 3问题再处理5个Tier 1问题，属于无效工作。
- 单个问题修复：大多数问题都是成组出现的。当800个重定向链有相同根本原因时，只修复一个是错误的工作单元。
- 不重新爬取：未验证就声称“已修复”会留下疑问。重大修复后务必重新爬取。
- 忽略Search Console：Ahrefs只能看到其爬虫发现的内容，而Search Console反映的是Google实际看到和索引的内容。两者都要使用。
- 将Core Web Vitals视为检查表：CWV是真实用户数据，而非实验室数据。应针对真实用户体验优化，而非合成分数。
- 为了好看而修复低影响问题：一份干净的技术报告却没有流量增长，对任何人都没有帮助。
- 不设置衡量指标：修复前要明确能证明修复有效的指标。
Output format
输出格式
A site health triage document with:
- Summary. Total issues, top 3 fix clusters, expected impact.
- URL tiering. How URLs were classified and counts per tier.
- Issue categorization. Counts by mechanism category, by tier, by priority band.
- Prioritized backlog. P0-P3 ordered. Each item has: issue, affected URLs, fix description, effort, expected impact, owner.
- Fix clusters. Groups of issues that share a fix. Highest leverage at the top.
- Measurement plan. Per fix or cluster, what proves it worked.
- Methodology. Crawler used, date, scope, caveats.
Length: 5-12 pages plus a backlog spreadsheet.
一份网站健康分类排序文档，包含：
- 摘要：问题总数、TOP3修复聚类任务、预期影响。
- URL分层：URL分类方式及各层级数量。
- 问题分类：按影响机制类别、层级、优先级区间统计数量。
- 优先待办清单：按P0-P3排序。每个条目包含：问题、受影响URL、修复说明、工作量、预期影响、负责人。
- 修复聚类：共享同一修复方案的问题组，按收益从高到低排列。
- 衡量计划：针对每个修复或聚类任务，明确验证修复有效的指标。
- 方法论：使用的爬虫工具、日期、范围、注意事项。
篇幅：5-12页，外加待办清单表格。
Reference files
参考文件
- - Mapping table of common crawler issues to mechanism impact and typical fix effort, plus the triage matrix in detailed form.
references/issue-impact-table.md
- - 常见爬虫问题与影响机制、典型修复工作量的映射表，以及详细版分类排序矩阵。
references/issue-impact-table.md