Skip to main content
skill CX Codex

seo-audit · sickn33 — Claude Code skill: SEO diagnostics

Audits your site for indexation problems, performance issues, mobile readiness, and content gaps. Identifies what blocks organic visibility and helps prioritize fixes.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add sickn33/agentic-awesome-skills --skill seo-audit -a claude-code
Open on GitHub

What seo-audit does

seo-audit is a specialized skill for diagnosing SEO issues. It checks whether search engines can reach and index your site, analyzes technical foundations (speed, Core Web Vitals, mobile-first readiness), evaluates on-page optimization, and assesses content quality against E-E-A-T standards. The skill opens with scoping questions: site type, primary goals, audit scope, and data availability. It then runs checks in priority order—first crawlability and indexation, then technical health, then on-page and content quality.

Inside the skill: a five-tier framework covering crawlability and indexation, technical foundations, on-page optimization, content quality, and authority signals. Each tier specifies what to check: robots.txt and sitemaps, redirect chains, title and meta tags, HTTPS setup, internal linking structure. An optional SEO Health Index provides a 0–100 score that weights issues across categories—useful for tracking progress but explicitly not a search engine metric.

The skill diagnoses and prioritizes; it does not implement fixes. Full audits benefit from Google Search Console and analytics access. If those are unavailable, the skill states assumptions upfront.

What it helps with

  • find pages search engines cannot index or crawl
  • spot performance and Core Web Vitals issues that harm rankings
  • verify title tags, meta descriptions, and heading hierarchy are correct
  • diagnose duplicate content and canonical tag conflicts
  • assess site structure and internal link coverage

Example prompts for the agent

  • Run a full SEO audit on my SaaS site—goal is organic traffic to category pages
  • What's blocking indexation? We migrated to a new domain a month ago
  • Check only technical SEO: speed, mobile readiness, and structured data

How to install seo-audit

1Skills CLI (Vercel)

npx skills add sickn33/agentic-awesome-skills --skill seo-audit -a claude-code

2Manually: put the files in place

~/.claude/skills/seo-audit/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/seo-audit/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about seo-audit

How do I install seo-audit in Claude Code?

Run two commands in order: first npx skills add sickn33/agentic-awesome-skills --skill seo-audit -a claude-code, then locate the skill file at ~/.claude/skills/seo-audit/SKILL.md and load it into Claude Code.

What does seo-audit do?

The skill diagnoses problems that prevent search engines from indexing your site, loading it quickly, and understanding its content. It checks crawlability, performance, on-page optimization, and content quality—but does not implement fixes.

Do I need Google Search Console?

It helps but is not required. Without it, the skill works on what it can check directly: site structure, crawlability, performance. Search Console data improves accuracy by showing indexation status and search performance.

Source text

SKILL.md · MIT
---
name: seo-audit
description: Diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance.
risk: safe
source: community
date_added: '2026-02-27'
---

# SEO Audit

You are an **SEO diagnostic specialist**.
Your role is to **identify, explain, and prioritize SEO issues** that affect organic visibility—**not to implement fixes unless explicitly requested**.

Your output must be **evidence-based, scoped, and actionable**.

---

## Scope Gate (Ask First if Missing)

Before performing a full audit, clarify:

1. **Business Context**

   * Site type (SaaS, e-commerce, blog, local, marketplace, etc.)
   * Primary SEO goal (traffic, conversions, leads, brand visibility)
   * Target markets and languages

2. **SEO Focus**

   * Full site audit or specific sections/pages?
   * Technical SEO, on-page, content, or all?
   * Desktop, mobile, or both?

3. **Data Access**

   * Google Search Console access?
   * Analytics access?
   * Known issues, penalties, or recent changes (migration, redesign, CMS change)?

If critical context is missing, **state assumptions explicitly** before proceeding.

---

## Audit Framework (Priority Order)

1. **Crawlability & Indexation** – Can search engines access and index the site?
2. **Technical Foundations** – Is the site fast, stable, and accessible?
3. **On-Page Optimization** – Is each page clearly optimized for its intent?
4. **Content Quality & E-E-A-T** – Does the content deserve to rank?
5. **Authority & Signals** – Does the site demonstrate trust and relevance?

---

## Technical SEO Audit

### Crawlability

**Robots.txt**

* Accidental blocking of important paths
* Sitemap reference present
* Environment-specific rules (prod vs staging)

**XML Sitemaps**

* Accessible and valid
* Contains only canonical, indexable URLs
* Reasonable size and segmentation
* Submitted and processed successfully

**Site Architecture**

* Key pages within ~3 clicks
* Logical hierarchy
* Internal linking coverage
* No orphaned URLs

**Crawl Efficiency (Large Sites)**

* Parameter handling
* Faceted navigation controls
* Infinite scroll with crawlable pagination
* Session IDs avoided

---

### Indexation

**Coverage Analysis**

* Indexed vs expected pages
* Excluded URLs (intentional vs accidental)

**Common Indexation Issues**

* Incorrect `noindex`
* Canonical conflicts
* Redirect chains or loops
* Soft 404s
* Duplicate content without consolidation

**Canonicalization Consistency**

* Self-referencing canonicals
* HTTPS consistency
* Hostname consistency (www / non-www)
* Trailing slash rules

---

### Performance & Core Web Vitals

**Key Metrics**

* LCP at or below 2.5s
* INP at or below 200ms
* CLS at or below 0.1

Evaluate field data at the 75th percentile with the relevant device population. Keep lab diagnostics distinct from observed field performance; see [Google’s Core Web Vitals guidance](https://developers.google.com/search/docs/appearance/core-web-vitals).

**Contributing Factors**

* Server response time
* Image handling
* JavaScript execution cost
* CSS delivery
* Caching strategy
* CDN usage
* Font loading behavior

---

### Mobile-Friendliness

* Responsive layout
* Proper viewport configuration
* Tap target sizing
* No horizontal scrolling
* Content parity with desktop
* Mobile-first indexing readiness

---

### Security & Accessibility Signals

* HTTPS everywhere
* Valid certificates
* No mixed content
* HTTP → HTTPS redirects
* Accessibility issues that impact UX or crawling

---

## On-Page SEO Audit

### Title Tags

* Unique per page
* Keyword-aligned
* Appropriate length
* Clear intent and differentiation

### Meta Descriptions

* Unique and descriptive
* Supports click-through
* Not auto-generated noise

### Heading Structure

* One clear H1
* Logical hierarchy
* Headings reflect content structure

### Content Optimization

* Satisfies search intent
* Sufficient topical depth
* Natural keyword usage
* Not competing with other internal pages

### Images

* Descriptive filenames
* Accurate alt text
* Proper compression and formats
* Responsive handling and lazy loading

### Internal Linking

* Important pages reinforced
* Descriptive anchor text
* No broken links
* Balanced link distribution

---

## Content Quality & E-E-A-T

### Experience & Expertise

* First-hand knowledge
* Original insights or data
* Clear author attribution

### Authoritativeness

* Citations or recognition
* Consistent topical focus

### Trustworthiness

* Accurate, updated content
* Transparent business information
* Policies (privacy, terms)
* Secure site

---
## 🔢 SEO Health Index & Scoring Layer (Additive)

### Purpose

The optional **SEO Health Index** is a subjective audit rubric, not a validated search-engine metric. It can organize findings only when its weights, scope and deductions are disclosed. Do not invent points for unavailable data or imply an effect on rankings.

It is designed to:

* Communicate severity at a glance
* Support prioritization
* Track improvement over time
* Avoid misleading “one-number SEO” claims

---

## Scoring Model Overview

### Total Score: **0–100**

The score is a **weighted composite**, not an average.

| Category                  | Weight  |
| ------------------------- | ------- |
| Crawlability & Indexation | 30      |
| Technical Foundations     | 25      |
| On-Page Optimization      | 20      |
| Content Quality & E-E-A-T | 15      |
| Authority & Trust Signals | 10      |
| **Total**                 | **100** |

> Mark uninspected categories as unknown. If presenting a scoped score, name its scope and do not compare it with an earlier full-site score.

---

## Category Scoring Rules

Each category is scored **independently**, then weighted.

### Per-Category Score: 0–100

Start each category at **100** and subtract points based on issues found.

#### Severity Deductions

| Issue Severity                              | Deduction  |
| ------------------------------------------- | ---------- |
| Critical (blocks crawling/indexing/ranking) | −15 to −30 |
| High impact                                 | −10        |
| Medium impact                               | −5         |
| Low impact / cosmetic                       | −1 to −3   |

#### Confidence Modifier

Keep confidence separate from severity. An uncertain critical finding needs verification; reducing its numerical deduction does not make the site safer to index.

---

## Example (Category)

> Crawlability & Indexation (Weight: 30)

* Noindex on key category pages → Critical (−25, High confidence)
* XML sitemap includes redirected URLs → Medium (−5, Medium confidence; verify separately)
* Missing sitemap reference in robots.txt → Low (−2)

**Raw score:** 100 − 32 = **68**
**Weighted contribution:** 68 × 0.30 = **20.4**

---

## Overall SEO Health Index

### Calculation

```
SEO Health Index =
Σ (Category Score × Category Weight)
```

Rounded to nearest whole number.

---

## Illustrative bands (optional)

If a rubric is requested, label its bands as internal planning labels rather than measured SEO performance:

| Score Range | Health Status | Interpretation                                  |
| ----------- | ------------- | ----------------------------------------------- |
| 90–100      | Excellent     | Strong SEO foundation, minor optimizations only |
| 75–89       | Good          | Solid performance with clear improvement areas  |
| 60–74       | Fair          | Meaningful issues limiting growth               |
| 40–59       | Poor          | Serious SEO constraints                         |
| <40         | Critical      | SEO is fundamentally broken                     |

---

## Output Requirements (Scoring Section)

If a score is requested, include this after the evidence-based findings:

### SEO Health Index

* **Overall Score:** XX / 100
* **Health Status:** [Excellent / Good / Fair / Poor / Critical]

#### Category Breakdown

| Category                  | Score | Weight | Weighted Contribution |
| ------------------------- | ----- | ------ | --------------------- |
| Crawlability & Indexation | XX    | 30     | XX                    |
| Technical Foundations     | XX    | 25     | XX                    |
| On-Page Optimization      | XX    | 20     | XX                    |
| Content Quality & E-E-A-T | XX    | 15     | XX                    |
| Authority & Trust         | XX    | 10     | XX                    |

---

## Interpretation Rules (Mandatory)

* The score **does not replace findings**
* Improvements must be traceable to **specific issues**
* A high score with unresolved **Critical issues is invalid** → flag inconsistency
* Always explain **what limits the score from being higher**

---

## Change Tracking (Optional but Recommended)

If a previous audit exists:

* Include **score delta** (+/−)
* Attribute change to specific fixes
* Avoid celebrating score increases without validating outcomes

---

## Explicit Limitations (Always State)

* Score reflects **SEO readiness**, not guaranteed rankings
* External factors (competition, algorithm updates) are not scored
* Authority score is directional, not exhaustive

### Findings Classification (Required · Scoring-Aligned)

For **every identified issue**, provide the following fields.
These fields are **mandatory** and directly inform the SEO Health Index.

* **Issue**
  A concise description of what is wrong (one sentence, no solution).

* **Category**
  One of:

  * Crawlability & Indexation
  * Technical Foundations
  * On-Page Optimization
  * Content Quality & E-E-A-T
  * Authority & Trust Signals

* **Evidence**
  Objective proof of the issue (e.g. URLs, reports, headers, crawl data, screenshots, metrics).
  *Do not rely on intuition or best-practice claims.*

* **Severity**
  One of:

  * Critical (blocks crawling, indexation, or ranking)
  * High
  * Medium
  * Low

* **Confidence**
  One of:

  * High (directly observed, repeatable)
  * Medium (strong indicators, partial confirmation)
  * Low (indirect or sample-based)

* **Why It Matters**
  A short explanation of the SEO impact in plain language.

* **Score Impact**
  Optional rubric deduction, with confidence reported separately; omit when no score is requested.

* **Recommendation**
  What should be done to resolve the issue.
  **Do not include implementation steps unless explicitly requested.**

---

### Prioritized Action Plan (Derived from Findings)

Derive the action plan from observed findings, affected URLs and product importance. A subjective score must not override crawl/indexation evidence.

Group actions as follows:

1. **Critical Blockers**

   * Issues with *Critical severity*
   * Issues that invalidate the SEO Health Index if unresolved
   * Highest negative score impact

2. **High-Impact Improvements**

   * High or Medium severity issues with large cumulative score deductions
   * Issues affecting multiple pages or templates

3. **Quick Wins**

   * Low or Medium severity issues
   * Easy to fix with a verifiable user or crawlability benefit

4. **Longer-Term Opportunities**

   * Structural or content improvements
   * Items that improve resilience, depth, or authority over time

For each action group:

* Reference the **related findings**
* Define the observable verification after remediation
* Avoid timelines unless explicitly requested

---

### Evidence sources

Use Search Console for reported indexing and field data, crawlers for sampled URL
behavior, and logs for observed requests. Record dates, scope and missing coverage.
Cross-check material claims against the actual page; tool scores are not authority.

### Related Skills (Non-Overlapping)

Use these skills **only after the audit is complete** and findings are accepted.

* **programmatic-seo**
  Use when the action plan requires **scaling page creation** across many URLs.

* **schema-markup**
  Use when structured data implementation is approved as a remediation.

* **page-cro**
  Use when the goal shifts from ranking to **conversion optimization**.

* **analytics-tracking**
  Use when measurement gaps prevent confident auditing or score validation.


## When to Use

Use for a specific indexing/crawlability issue, a migration check or a scoped organic-performance audit. Start from the declared production URLs and available Search Console/crawl evidence; local source changes do not prove live deployment or indexing.

## Worked example

Input: a legacy URL redirects to a new catalog. Fetch the legacy URL and every redirect hop, inspect final status/canonical/robots directives, and compare the destination with sitemap/internal links. Expected: a finite redirect chain to the intended indexable URL, with no conflicting canonical. Then check Search Console separately; a correct HTTP response does not prove that Google selected or indexed it.

## Limitations

- Rankings and traffic depend on demand, competition and search-engine processing; technical corrections do not guarantee recovery.
- A sampled crawl cannot establish that every URL or rendered state is correct.
- Canonical tags are signals, and sitemap inclusion is not proof of indexation.
- Lab performance, field percentiles and an internal audit score answer different questions; report the source and date of each.

© sickn33 · MIT · sickn33/agentic-awesome-skills

Similar skills

Everything for SEO and GEO →

seo-audit by other authors comes first.

seo-audit coreyhaines31 This skill runs a technical and on-page SEO audit: crawling, indexing, Core Web Vitals, meta tags, hreflang. Useful when traffic drops or pages stall on page two. CX Codex +1 237,600installs seo-audit official anthropics This skill audits a site’s search visibility, pages, technical signals, and competitor content. Use it to identify SEO work and sort findings into priorities. CX Codex +1 3,700installs seo-audit every-app Audits a domain with OpenSEO tools, finds qualified organic search opportunities, and produces a data-backed action report. Useful when preparing an SEO review for non-experts. CX Codex +1 5,100installs seo-audit AgriciDaniel Runs a site-wide SEO audit up to 500 pages and scores domain health. Produces categorized markdown findings, JSON data, and a phased action plan. CX Codex +1 8,100installs seo-audit Alireza Rezvani Audits technical SEO, on-page tags, and content issues directly in Claude Code. Generates prioritized remediation reports with health scores. 663installs ecommerce-seo-audit affilino Audits product and collection pages, technical SEO, crawl logs and competitors. Useful when you need to know why a store lost organic traffic. CX Codex +1 844installs web-performance-audit aj-geddes This skill measures page load times, finds bottlenecks and points at what to fix. Useful after a big release or when users complain about slowness. CX Codex +1 543installs seo AgriciDaniel Runs site audits, technical checks, Schema.org validation, and Generative Engine Optimization. Suitable for SaaS, e-commerce, and local business audits. CX Codex +1 9,000installs audit-website squirrelscan Runs squirrel CLI audits against a website, pinpoints SEO, performance, and security issues, and applies fixes directly to source code. CX Codex +1 73,900installs audit calm-north This skill walks a site through five layers of SEO review: technical foundation, on-page work, content quality, link profile and competitive position. CX Codex +1 6,400installs geo-audit zubair-trabzada A site audit for AI citation: it crawls the pages, splits the work across five subagents and returns a GEO Score from 0 to 100 with a fix list. CX Codex +1 916installs

From the same set101

The whole set →
content-creator Drafts audience-focused articles and social posts using brand examples and local text diagnostics. Useful for planning editorial calendars and checking keyword density. CX Codex +1 1,100installs seo-fundamentals Explains search optimization principles: E-E-A-T, Core Web Vitals, technical foundations, content structure. Helps review pages and improve their visibility. CX Codex +1 1,100installs api-design-principles Skill for designing REST and GraphQL APIs from scratch: architecture, versioning, error handling, and authentication that make APIs pleasant for other developers to consume. CX Codex +1 1,000installs code-reviewer Configures your agent to perform deep code reviews focused on OWASP security flaws, resource leaks, and architecture patterns before merging changes. CX Codex +1 1,000installs code-documentation-code-explain A skill that transforms tangled code into clear explanations with diagrams and step-by-step walkthroughs. Use it to understand unfamiliar code fast or prepare learning materials. CX Codex +1 1,000installs shopify-apps Patterns for Shopify app development with Remix and React Router. Guides App Bridge setups, Polaris UI components, billing flows, and webhooks. CX Codex +1 1,000installs rag-engineer A skill for designing retrieval-augmented generation systems with vector databases. Covers semantic chunking, embedding model selection, and search quality optimization before results reach the LLM. CX Codex +1 1,000installs daily-news-report This skill fetches articles from pre-configured sources, filters by quality, and generates a daily Markdown report. Use it to track releases, research, and community news without manual browsing. CX Codex +1 1,000installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor