technical-seo-checker

Technical SEO Checker

SEO & GEO Skills Library · 20 skills for SEO + GEO · ClawHub · skills.sh

<details> <summary>Browse all 20 skills</summary>

Research · keyword-research · competitor-analysis · serp-analysis · content-gap-analysis

Build · seo-content-writer · geo-content-optimizer · meta-tags-optimizer · schema-markup-generator

Optimize · on-page-seo-auditor · technical-seo-checker · internal-linking-optimizer · content-refresher

Monitor · rank-tracker · backlink-analyzer · performance-reporter · alert-manager

Cross-cutting · content-quality-auditor · domain-authority-auditor · entity-optimizer · memory-management

</details>

This skill performs comprehensive technical SEO audits to identify issues that may prevent search engines from properly crawling, indexing, and ranking your site.

When to Use This Skill

• Launching a new website
• Diagnosing ranking drops
• Pre-migration SEO audits
• Regular technical health checks
• Identifying crawl and index issues
• Improving site performance
• Fixing Core Web Vitals issues

What This Skill Does

1. Crawlability Audit: Checks robots.txt, sitemaps, crawl issues
2. Indexability Review: Analyzes index status and blockers
3. Site Speed Analysis: Evaluates Core Web Vitals and performance
4. Mobile-Friendliness: Checks mobile optimization
5. Security Check: Reviews HTTPS and security headers
6. Structured Data Audit: Validates schema markup
7. URL Structure Analysis: Reviews URL patterns and redirects
8. International SEO: Checks hreflang and localization

How to Use

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]

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:

1. Site URL(s) to audit
2. PageSpeed Insights screenshots or reports
3. robots.txt file content
4. sitemap.xml URL or file

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:

1. Audit Crawlability

   ## 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
   

2. Audit Indexability

   ## 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
   

3. Audit Site Speed & Core Web Vitals — CWV metrics (LCP/FID/CLS/INP), additional performance metrics (TTFB/FCP/Speed Index/TBT), resource loading breakdown, optimization recommendations

   Reference: See references/technical-audit-templates.md for the performance analysis template (Step 3).

4. Audit Mobile-Friendliness — Mobile-friendly test, responsive design check, mobile-first indexing verification

   Reference: See references/technical-audit-templates.md for the mobile optimization template (Step 4).

5. Audit Security & HTTPS — SSL certificate, HTTPS enforcement, mixed content, HSTS, security headers (CSP, X-Frame-Options, etc.)

   Reference: See references/technical-audit-templates.md for the security analysis template (Step 5).

6. Audit URL Structure — URL patterns, issues (dynamic params, session IDs, uppercase), redirect analysis (chains, loops, 302s)

   Reference: See references/technical-audit-templates.md for the URL structure template (Step 6).

7. Audit Structured Data — Schema markup validation, missing schema opportunities. CORE-EEAT alignment: maps to O05.

   Reference: See references/technical-audit-templates.md for the structured data template (Step 7).

8. Audit International SEO (if applicable) — Hreflang implementation, language/region targeting

   Reference: See references/technical-audit-templates.md for the international SEO template (Step 8).

9. Generate Technical Audit Summary — Overall health score with visual breakdown, critical/high/medium issues, quick wins, implementation roadmap (weeks 1-4+), monitoring recommendations

   Reference: See references/technical-audit-templates.md for the audit summary template (Step 9).

Validation Checkpoints

Input Validation

• Site URL or domain clearly specified
• Access to technical data (robots.txt, sitemap, or crawl results)
• Performance metrics available (via ~~page speed tool or screenshots)

Output Validation

• Every recommendation cites specific data points (not generic advice)
• All issues include affected URLs or page counts
• Performance metrics include actual numbers with units (seconds, KB, etc.)
• Source of each data point clearly stated (~~web crawler data, ~~page speed tool, user-provided, or estimated)

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

1. Prioritize by impact - Fix critical issues first
2. Monitor continuously - Use ~~search console alerts
3. Test changes - Verify fixes work before deploying widely
4. Document everything - Track changes for troubleshooting
5. Regular audits - Schedule quarterly technical reviews

Technical reference

---

Content truncated.