technical-seo-checker
技术SEO审计：核心网络指标（Core Web Vitals）、抓取、索引、移动端、速度、架构、重定向。技术SEO/网站速度
分类
SEO安装
下载并解压到你的 skills 目录
复制命令，发送给 OpenClaw 自动安装：
Technical SEO Checker
> 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 comprehensive technical SEO audits to identify issues that may prevent search engines from properly crawling, indexing, and ranking your site.
System role: Optimization layer skill. It turns weak pages, structures, and technical issues into prioritized repair work.
When This Must Trigger
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.
What This Skill Does
Quick Start
Start with one of these prompts. Finish with a short handoff summary using the repository format in Skill Contract.
Full Technical Audit
Perform a technical SEO audit for [URL/domain]Specific Issue Check
Check Core Web Vitals for [URL]Audit crawlability and indexability for [domain]Pre-Migration Audit
Technical SEO checklist for migrating [old domain] to [new domain]Skill Contract
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.Data Sources
> See CONNECTORS.md for tool category placeholders.
With ~~web crawler + ~~page speed tool + ~~CDN connected:
Claude can automatically crawl the entire site structure via ~~web crawler, pull Core Web Vitals and performance metrics from ~~page speed tool, analyze caching headers from ~~CDN, and fetch mobile-friendliness data. This enables comprehensive automated technical audits.
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.
Instructions
When a user requests a technical SEO audit:
## Crawlability Analysis
### Robots.txt Review
**URL**: [domain]/robots.txt
**Status**: [Found/Not Found/Error]
**Current Content**:[robots.txt content]
| Check | Status | Notes |
|-------|--------|-------|
| File exists | ✅/❌ | [notes] |
| Valid syntax | ✅/⚠️/❌ | [errors found] |
| Sitemap declared | ✅/❌ | [sitemap URL] |
| Important pages blocked | ✅/⚠️/❌ | [blocked paths] |
| Assets blocked | ✅/⚠️/❌ | [CSS/JS blocked?] |
| Correct user-agents | ✅/⚠️/❌ | [notes] |
**Issues Found**:
- [Issue 1]
- [Issue 2]
**Recommended robots.txt**:User-agent: *
Allow: /
Disallow: /admin/
Disallow: /private/
Sitemap: https://example.com/sitemap.xml
---
### XML Sitemap Review
**Sitemap URL**: [URL]
**Status**: [Found/Not Found/Error]
| Check | Status | Notes |
|-------|--------|-------|
| Sitemap exists | ✅/❌ | [notes] |
| Valid XML format | ✅/⚠️/❌ | [errors] |
| In robots.txt | ✅/❌ | [notes] |
| Submitted to ~~search console | ✅/⚠️/❌ | [notes] |
| URLs count | [X] | [appropriate?] |
| Only indexable URLs | ✅/⚠️/❌ | [notes] |
| Includes priority | ✅/⚠️ | [notes] |
| Includes lastmod | ✅/⚠️ | [accurate?] |
**Issues Found**:
- [Issue 1]
---
### Crawl Budget Analysis
| Factor | Status | Impact |
|--------|--------|--------|
| Crawl errors | [X] errors | [Low/Med/High] |
| Duplicate content | [X] pages | [Low/Med/High] |
| Thin content | [X] pages | [Low/Med/High] |
| Redirect chains | [X] found | [Low/Med/High] |
| Orphan pages | [X] found | [Low/Med/High] |
**Crawlability Score**: [X]/10
## Indexability Analysis
### Index Status Overview
| Metric | Count | Notes |
|--------|-------|-------|
| Pages in sitemap | [X] | |
| Pages indexed | [X] | [source: site: search] |
| Index coverage ratio | [X]% | [good if >90%] |
### Index Blockers Check
| Blocker Type | Found | Pages Affected |
|--------------|-------|----------------|
| noindex meta tag | [X] | [list or "none"] |
| noindex X-Robots | [X] | [list or "none"] |
| Robots.txt blocked | [X] | [list or "none"] |
| Canonical to other | [X] | [list or "none"] |
| 4xx/5xx errors | [X] | [list or "none"] |
| Redirect loops | [X] | [list or "none"] |
### Canonical Tags Audit
| Check | Status | Notes |
|-------|--------|-------|
| Canonicals present | ✅/⚠️/❌ | [X]% of pages |
| Self-referencing | ✅/⚠️/❌ | [notes] |
| Consistent (HTTP/HTTPS) | ✅/⚠️/❌ | [notes] |
| Consistent (www/non-www) | ✅/⚠️/❌ | [notes] |
| No conflicting signals | ✅/⚠️/❌ | [notes] |
### Duplicate Content Issues
| Issue Type | Count | Examples |
|------------|-------|----------|
| Exact duplicates | [X] | [URLs] |
| Near duplicates | [X] | [URLs] |
| Parameter duplicates | [X] | [URLs] |
| WWW/non-WWW | [X] | [notes] |
| HTTP/HTTPS | [X] | [notes] |
**Indexability Score**: [X]/10> Reference: See references/technical-audit-templates.md for the performance analysis template (Step 3).
> Reference: See references/technical-audit-templates.md for the mobile optimization template (Step 4).
> Reference: See references/technical-audit-templates.md for the security analysis template (Step 5).
> Reference: See references/technical-audit-templates.md for the URL structure template (Step 6).
> Reference: See references/technical-audit-templates.md for the structured data template (Step 7).
> Reference: See references/technical-audit-templates.md for the international SEO template (Step 8).
> Reference: See references/technical-audit-templates.md for the audit summary template (Step 9).
Validation Checkpoints
Input Validation
Output Validation
Example
> Reference: See references/technical-audit-example.md for a full worked example (cloudhosting.com technical audit) and the comprehensive technical SEO checklist.
Tips for Success
> Technical reference: For issue severity framework, prioritization matrix, and Core Web Vitals optimization quick reference, see references/http-status-codes.md.
Save Results
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/technical-seo-checker/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.