Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Seo Site Auditor

ASecurity

Audit websites for SEO: crawling, technical checks, metadata, Core Web Vitals, structured data, and prioritized fixes. Use when diagnosing search visibility problems.

2 stars
0 votes
0 copies
5 views
Added 9/29/2026
ai-agentsgobashperformance

Works with

cli

Security Analysis

A96/100
mediumUses curl or wget to download content

Pro shows the line behind each finding and how to fix it

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill seo-site-auditor --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Seo Site Auditor?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Seo Site Auditor
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-seo-site-auditor/badge)](https://www.skillsdirectory.com/skills/aicodedecode-seo-site-auditor)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: seo-site-auditor
description: Audit websites for SEO: crawling, technical checks, metadata, Core Web Vitals, structured data, and prioritized fixes. Use when diagnosing search visibility problems.
category: web-development
---

# SEO Site Auditor

A systematic approach to technical SEO audits: crawling a site, checking indexability, metadata, structured data, performance, and content signals — then prioritizing fixes by impact and effort.

## Overview

SEO audits fail when they're 200-line checklists with no priorities. This skill is a **triage method**: crawl → identify what's blocking indexing/ranking → verify the high-impact basics (titles, canonicals, sitemaps, speed, structured data) → prioritize by (traffic at stake × effort). Most sites' SEO problems are a handful of fixable technical issues, not mysterious algorithm behavior.

## When to use

- Traffic drops or pages not appearing in search.
- Pre-launch SEO review of a new site or migration.
- Periodic technical health checks.
- Evaluating an agency/freelancer SEO proposal (know what good looks like).

## Core concepts

- **Crawlability.** Can bots fetch and render pages? Check robots.txt, meta robots, HTTP status codes, redirect chains, and JS-rendering (view-source vs rendered DOM for key content).
- **Indexability.** `noindex` tags, canonical tags (self-referencing where appropriate), sitemap.xml accuracy, Search Console coverage report.
- **Metadata.** Unique `<title>` (50–60 chars, keyword-front-loaded naturally), meta descriptions (compelling, ~150 chars — they don't rank you but earn clicks), one H1 per page, logical heading hierarchy.
- **Structured data.** JSON-LD schema.org (Article, Product, FAQ, BreadcrumbList, Organization) — validates in Rich Results Test; enables rich snippets.
- **Core Web Vitals.** LCP < 2.5s, INP < 200ms, CLS < 0.1 — measured via PageSpeed Insights / CrUX (field data beats lab data).
- **Content signals.** Thin/duplicate content, keyword cannibalization (multiple pages targeting the same query), internal linking depth (important pages ≤ 3 clicks from home).
- **Migration risks.** URL changes without 301s, lost metadata, staging `noindex` leaking to production.

## Practical workflow

**1. Crawl.**
```bash
# CLI crawl for status codes, titles, canonicals, noindex
npx broken-link-checker https://example.com --ordered
# or: screaming-frog-style desktop crawler for full audits
curl -sI https://example.com/robots.txt
curl -s https://example.com/sitemap.xml | head -50
```
Check: 200s where expected, no redirect chains (>2 hops), noindex only where intended, canonicals absolute and self-consistent.

**2. Indexation check.** Search Console: coverage errors, "discovered not indexed" (crawl budget/content quality signal), sitemap submission status. `site:example.com` for a rough indexed-page count.

**3. Page-level audit (top 20 pages).**
- Title unique and descriptive? Meta description present and click-worthy?
- H1 present, single, matching intent? Headings hierarchical?
- Canonical correct? Open Graph/Twitter cards render (test with validators)?
- JSON-LD valid? (Rich Results Test)
- Images: descriptive alt, compressed, modern formats, width/height set (CLS)?

**4. Performance.** PageSpeed Insights per template (not just homepage): LCP element identified, INP interactions, CLS sources. Fix images/fonts/JS bloat first — they're usually the cause.

**5. Content.** Identify: thin pages (< few hundred useful words), duplicates/near-duplicates, cannibalization (Search Console: two pages ranking for the same query — consolidate).

**6. Prioritize.** Score each finding: impact (traffic at stake) × effort (dev hours). Fix order: blocking (noindex leaks, 5xx) → high-impact quick wins (titles, canonicals) → structural (internal linking, speed) → content (consolidation, new content).

## Common pitfalls

- **`noindex` on production.** Staging configs leaking to prod — the single most expensive one-line SEO bug. Check after every deploy.
- **JS-rendered critical content.** If the title, headings, or body text only exist after JS runs, crawlers may miss or delay them. SSR critical content.
- **Canonical chaos.** Canonicals pointing to wrong URLs, chains, or http/https mismatches. Every indexable page: self-referencing absolute canonical.
- **Sitemap fiction.** Sitemaps listing 404s, noindexed pages, or missing new content. Regenerate automatically; keep under 50k URLs per file.
- **Title/description duplication.** Same title on 500 product pages = missed clicks. Templates with unique variables (product name, category).
- **Chasing scores over users.** Perfect Lighthouse 100 with thin content ranks worse than useful content at 85. Technical SEO is table stakes; content wins.
- **Ignoring Search Console.** The only source of truth for how Google sees your site. Check coverage, enhancements, and manual actions regularly.
- **Migration without redirects.** Relaunching with new URLs and no 301 map = traffic cliff. Map every old URL → new (or closest equivalent) before launch.
- **Keyword stuffing.** 2010 called. Write for the query's intent; use the keyword naturally in title/H1/early body.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →