Traffic 技能

Technical SEO Checker

Technical SEO Checker 是一套面向一人公司的流量 playbook,帮助你用更少的人力完成更稳的增长、交付与决策。

更新于 2026年4月4日 One Person Company 编辑团队 Traffic 执行系统

中文导读

Technical SEO Checker 是一套面向一人公司的流量 playbook,帮助你用更少的人力完成更稳的增长、交付与决策。

说明: 原始步骤、命令与 API 名称保留英文,以避免参数和接口名称失真。

概览

Technical SEO Checker is the skill of auditing the site conditions that determine whether good pages can actually be crawled, indexed, and trusted. For a one-person company, technical SEO should stay simple and ruthless: remove blockers, stabilize canonical paths, keep performance acceptable, and avoid avoidable crawl waste.

适用场景

Use this before and after major releases, when rankings drop unexpectedly, when answer-engine visibility falls despite strong content, or when you suspect crawl or canonical problems are distorting performance.

这个技能能做什么

This skill helps you check the few technical layers that actually matter for a lean content site: robots, sitemap, canonicals, redirects, indexability, basic performance, and structured data sanity.

如何使用

Step 1: Check crawl access. Confirm robots.txt, sitemap discovery, and that important paths are not blocked.

Step 2: Check canonical integrity. Every important page should point to its intended canonical URL, and redirects should support that choice.

Step 3: Check indexability. Look for accidental noindex, orphan pages, thin duplicates, and pages that exist in the site but not the sitemap.

Step 4: Check route hygiene. Legacy paths should resolve cleanly. Do not let old traffic fall back to the homepage or soft 404 behavior.

Step 5: Check performance basics. You do not need perfection, but you do need stable load behavior, readable markup, and mobile-safe layout.

Step 6: Check structured data and metadata. Article, FAQ, Organization, and canonical signals should reinforce the page instead of conflicting with it.

输出结果

The output should include:

  • A list of blockers by severity
  • Affected URLs or patterns
  • The fix recommendation
  • Whether the issue affects crawl, index, traffic, or citations

常见错误

Do not run a huge checklist without prioritizing impact. Do not spend weeks on micro-optimizations while canonical and redirect issues stay broken. Do not create multiple public URLs for the same page. Do not treat sitemap presence as proof that a page is healthy.

SKILL.md 原文件

内嵌文档查看器 SKILL.md
Markdown 源文件

预览原始 SKILL.md. 下面可以直接查看完整原文。可滚动阅读、检查结构,再下载精确的 SKILL.md 原文件。

# technical-seo-checker

Technical SEO Checker


Overview
Technical SEO Checker is the skill of auditing the site conditions that determine whether good pages can actually be crawled, indexed, and trusted. For a one-person company, technical SEO should stay simple and ruthless: remove blockers, stabilize canonical paths, keep performance acceptable, and avoid avoidable crawl waste.

When to Use This Skill
Use this before and after major releases, when rankings drop unexpectedly, when answer-engine visibility falls despite strong content, or when you suspect crawl or canonical problems are distorting performance.

What This Skill Does
This skill helps you check the few technical layers that actually matter for a lean content site: robots, sitemap, canonicals, redirects, indexability, basic performance, and structured data sanity.

How to Use
Step 1: Check crawl access. Confirm `robots.txt`, sitemap discovery, and that important paths are not blocked.
Step 2: Check canonical integrity. Every important page should point to its intended canonical URL, and redirects should support that choice.
Step 3: Check indexability. Look for accidental `noindex`, orphan pages, thin duplicates, and pages that exist in the site but not the sitemap.
Step 4: Check route hygiene. Legacy paths should resolve cleanly. Do not let old traffic fall back to the homepage or soft 404 behavior.
Step 5: Check performance basics. You do not need perfection, but you do need stable load behavior, readable markup, and mobile-safe layout.
Step 6: Check structured data and metadata. Article, FAQ, Organization, and canonical signals should reinforce the page instead of conflicting with it.

Output
The output should include:
A list of blockers by severity
Affected URLs or patterns
The fix recommendation
Whether the issue affects crawl, index, traffic, or citations

Common Mistakes
Do not run a huge checklist without prioritizing impact.
Do not spend weeks on micro-optimizations while canonical and redirect issues stay broken.
Do not create multiple public URLs for the same page.
Do not treat sitemap presence as proof that a page is healthy.

评论与讨论

添加评论