home / skills / madappgang / claude-code / technical-audit

technical-audit skill

/plugins/seo/skills/technical-audit

This skill performs a technical SEO audit, identifying crawlability, indexability, and Core Web Vitals issues to improve site performance.

npx playbooks add skill madappgang/claude-code --skill technical-audit

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.5 KB
---
plugin: seo
updated: 2026-01-20
name: technical-audit
description: Technical SEO audit methodology including crawlability, indexability, and Core Web Vitals analysis. Use when auditing pages or sites for technical SEO issues.
---
plugin: seo
updated: 2026-01-20

# Technical Audit

## When to Use

- Auditing pages for technical SEO issues
- Analyzing Core Web Vitals performance
- Checking schema markup implementation
- Validating crawlability and indexability

## Audit Categories

### 1. Indexability

| Check | Requirement | Severity |
|-------|-------------|----------|
| Title Tag | Present, 50-60 chars, contains keyword | CRITICAL |
| Meta Description | Present, 150-160 chars | HIGH |
| Canonical Tag | Present, self-referencing or correct | HIGH |
| Robots Meta | No noindex on important pages | CRITICAL |
| Robots.txt | Not blocking important content | CRITICAL |

### 2. Content Structure

| Check | Requirement | Severity |
|-------|-------------|----------|
| H1 Tag | Exactly 1, contains keyword | CRITICAL |
| Heading Hierarchy | H1 -> H2 -> H3 (no skips) | HIGH |
| Word Count | Meets or exceeds competitor benchmark | MEDIUM |
| Content Uniqueness | No duplicate content issues | HIGH |

### 3. Core Web Vitals

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

**Measurement Methods:**
1. Chrome DevTools MCP (preferred)
2. PageSpeed Insights API
3. Lighthouse CLI
4. Manual measurement via web.dev

### 4. Schema Markup

| Page Type | Recommended Schema |
|-----------|-------------------|
| Article/Blog | Article, BlogPosting |
| FAQ page | FAQPage |
| How-to guide | HowTo |
| Product page | Product |
| Local business | LocalBusiness |
| Person/Author | Person |

### 5. Links

| Check | Requirement | Severity |
|-------|-------------|----------|
| Internal Links | Minimum 3 per page | HIGH |
| Broken Links | 0 | CRITICAL |
| External Links | At least 1 authoritative | LOW |
| Orphan Pages | 0 (all pages linked from somewhere) | MEDIUM |

## Audit Process

### Step 1: Fetch Page
```bash
# Use WebFetch or curl
curl -s "$URL" > page.html
```

### Step 2: Parse Structure
- Extract title, meta description, canonical
- Map heading hierarchy
- Count words
- List all links

### Step 3: Analyze Performance
- Use PageSpeed Insights API or Chrome DevTools MCP
- Document all Core Web Vitals
- Note specific issues (large images, render-blocking JS)

### Step 4: Check Schema
- Look for JSON-LD in page source
- Validate using Google Rich Results Test
- Note missing or incomplete properties

### Step 5: Score and Report
- Calculate overall score (0-100)
- List all issues by severity
- Provide specific fix recommendations

## Output Format

```markdown
## Technical SEO Audit Report

**URL**: {url}
**Date**: {date}
**Overall Score**: {score}/100

### Core Web Vitals
| Metric | Value | Status |
|--------|-------|--------|
| LCP | {value}s | GOOD/NEEDS IMPROVEMENT/POOR |
| INP | {value}ms | GOOD/NEEDS IMPROVEMENT/POOR |
| CLS | {value} | GOOD/NEEDS IMPROVEMENT/POOR |

**Measurement Method**: {Chrome DevTools MCP | PageSpeed API | Lighthouse | Manual}

### Issues Found

**CRITICAL ({count})**:
1. {issue} - {location} - {fix recommendation}

**HIGH ({count})**:
1. {issue} - {location} - {fix recommendation}

**MEDIUM ({count})**:
1. {issue} - {location} - {fix recommendation}

### Recommendations
1. {priority fix 1}
2. {priority fix 2}
3. {priority fix 3}
```

Overview

This skill provides a repeatable technical SEO audit methodology focused on crawlability, indexability, schema, internal linking, and Core Web Vitals. It guides auditors through structured checks, scoring, and prioritized fixes so you can turn findings into action. The approach is practical for single pages or full-site audits and produces an actionable report format.

How this skill works

The audit fetches a page, parses HTML for title, meta, canonical, headings, schema, and links, then measures Core Web Vitals with DevTools, PageSpeed, or Lighthouse. It validates robots directives and robots.txt, detects broken or orphaned links, and scores issues by severity. The output is a concise report with an overall score, Vitals table, categorized issues, and prioritized remediation steps.

When to use it

  • Performing a site or page-level technical SEO assessment before migration or redesign
  • Diagnosing drops in search visibility that may be caused by indexability problems
  • Evaluating Core Web Vitals and page performance for ranking impact
  • Validating schema markup for eligibility in rich results
  • Checking internal linking, broken links, and orphan pages

Best practices

  • Start with robots.txt and robots meta checks to ensure important pages are crawlable
  • Measure Core Web Vitals with Chrome DevTools MCP and validate with PageSpeed API for repeatability
  • Prioritize CRITICAL issues (noindex, blocked content, broken links) before cosmetic fixes
  • Use JSON-LD checks and Google Rich Results Test to confirm schema completeness
  • Provide specific, implementable fixes and re-test after changes

Example use cases

  • Full-site audit before a CMS migration to prevent indexability regressions
  • Page-level audit for top-traffic landing pages with poor conversion or rankings
  • Performance triage to reduce LCP and INP using image and JS optimizations
  • Pre-launch review of product and FAQ pages to ensure correct schema for rich results
  • Ongoing QA for a content refresh to ensure headings, canonical, and meta tags meet SEO standards

FAQ

Which tools are recommended to measure Core Web Vitals?

Use Chrome DevTools MCP for lab testing, PageSpeed Insights API and Lighthouse CLI for automated measurements, and web.dev for manual checks.

How are issues prioritized in the report?

Issues are classified by severity: CRITICAL (must-fix), HIGH (important), MEDIUM (useful), and LOW (nice-to-have); remediation order follows that priority.