seo-audit

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.

26 stars

Best use case

seo-audit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.

Teams using seo-audit should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/seo-audit/SKILL.md --create-dirs "https://raw.githubusercontent.com/TerminalSkills/skills/main/skills/seo-audit/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/seo-audit/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How seo-audit Compares

Feature / Agentseo-auditStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# SEO Audit

## Overview

You are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.

**Check for product marketing context first:**
If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

## Instructions

### Initial Assessment

Before auditing, understand:

1. **Site Context** - What type of site (SaaS, e-commerce, blog)? Primary business goal for SEO? Priority keywords/topics?
2. **Current State** - Known issues or concerns? Current organic traffic level? Recent changes or migrations?
3. **Scope** - Full site or specific pages? Technical + on-page, or one focus area? Access to Search Console / analytics?

### Audit Priority Order

1. **Crawlability & Indexation** (can Google find and index it?)
2. **Technical Foundations** (is the site fast and functional?)
3. **On-Page Optimization** (is content optimized?)
4. **Content Quality** (does it deserve to rank?)
5. **Authority & Links** (does it have credibility?)

### Technical SEO Audit

**Crawlability:**
- Robots.txt: Check for unintentional blocks, verify important pages allowed, check sitemap reference
- XML Sitemap: Exists and accessible, submitted to Search Console, contains only canonical indexable URLs
- Site Architecture: Important pages within 3 clicks of homepage, logical hierarchy, no orphan pages
- Crawl Budget (large sites): Parameterized URLs controlled, faceted navigation handled, no session IDs in URLs

**Indexation:**
- Run site:domain.com check, review Search Console coverage, compare indexed vs. expected page count
- Check for: noindex on important pages, canonicals pointing wrong, redirect chains/loops, soft 404s, duplicate content
- Canonicalization: All pages have canonical tags, HTTP to HTTPS, www vs. non-www consistency, trailing slash consistency

**Core Web Vitals:**
- LCP (Largest Contentful Paint): < 2.5s
- INP (Interaction to Next Paint): < 200ms
- CLS (Cumulative Layout Shift): < 0.1
- Speed factors: TTFB, image optimization, JavaScript execution, CSS delivery, caching, CDN, font loading

**Mobile & Security:**
- Responsive design, proper tap targets, viewport configured, no horizontal scroll, same content as desktop
- HTTPS everywhere, valid SSL, no mixed content, HTTP to HTTPS redirects

### On-Page SEO Audit

**Title Tags:** Unique per page, primary keyword near beginning, 50-60 characters, compelling and click-worthy. Watch for duplicates, truncation, keyword stuffing, or missing titles.

**Meta Descriptions:** Unique per page, 150-160 characters, includes primary keyword, clear value proposition with call to action.

**Heading Structure:** One H1 per page containing primary keyword, logical hierarchy (H1 > H2 > H3), headings describe content not just styling.

**Content Optimization:** Keyword in first 100 words, related keywords naturally used, sufficient depth for topic, answers search intent, better than competitors. Flag thin content, doorway pages, and duplicate content.

**Image Optimization:** Descriptive file names, alt text on all images, compressed sizes, modern formats (WebP), lazy loading, responsive images.

**Internal Linking:** Important pages well-linked, descriptive anchor text, no broken links, no orphan pages.

### Content Quality Assessment

**E-E-A-T Signals:**
- Experience: First-hand experience, original data, real examples
- Expertise: Author credentials visible, accurate detailed information
- Authoritativeness: Recognized in space, cited by others
- Trustworthiness: Accurate info, transparent about business, contact info, privacy policy, HTTPS

### Common Issues by Site Type

**SaaS:** Product pages lack depth, blog not integrated with product pages, missing comparison pages, thin feature pages.

**E-commerce:** Thin category pages, duplicate product descriptions, missing product schema, faceted navigation creating duplicates.

**Content/Blog:** Outdated content, keyword cannibalization, no topical clustering, poor internal linking.

### Output Format

Structure the audit report as:
1. **Executive Summary** - Overall health, top 3-5 priority issues, quick wins
2. **Technical SEO Findings** - Each issue with: Issue, Impact (High/Medium/Low), Evidence, Fix, Priority
3. **On-Page SEO Findings** - Same format
4. **Content Findings** - Same format
5. **Prioritized Action Plan** - Critical fixes, high-impact improvements, quick wins, long-term recommendations

### References

- [AI Writing Detection](references/ai-writing-detection.md): Common AI writing patterns to avoid
- [AEO & GEO Patterns](references/aeo-geo-patterns.md): Content patterns optimized for answer engines and AI citation

### Tools Referenced

**Free:** Google Search Console, PageSpeed Insights, Bing Webmaster Tools, Rich Results Test, Schema Validator

**Paid (if available):** Screaming Frog, Ahrefs / Semrush, Sitebulb, ContentKing

## Examples

### Example 1: Technical SEO Audit for a B2B SaaS Marketing Site

**User prompt:** "Our website acmeanalytics.com dropped 35% in organic traffic after a Next.js migration last month. Can you audit what went wrong?"

The agent will check for product marketing context, then systematically audit the migration:
- Review robots.txt and XML sitemap for blocking issues introduced during migration
- Check for broken redirect chains from old URLs to new URL structure
- Verify canonical tags are correctly self-referencing and not pointing to old domain paths
- Audit Core Web Vitals since JS-heavy frameworks often introduce LCP and CLS regressions
- Check that server-side rendering is working (view source vs. rendered DOM)
- Verify meta tags, H1s, and structured data survived the migration intact
- Deliver a prioritized report: critical indexation fixes first, then technical performance, then on-page recovery items

### Example 2: On-Page SEO Review for an E-commerce Category Page

**User prompt:** "Our 'wireless earbuds' category page on techgearshop.com ranks on page 3. Competitors are on page 1. What's wrong with our page and how do we fix it?"

The agent will perform a focused on-page audit comparing the page against top-ranking competitors:
- Audit the title tag, meta description, and H1 for keyword placement and compelling copy
- Assess content depth: top-ranking pages for "wireless earbuds" typically have 1,500+ words with buying guides, comparison tables, and FAQ sections
- Check for proper product schema markup on individual listings and category-level BreadcrumbList schema
- Review internal linking: is the category page linked from the homepage nav, related categories, and blog content?
- Flag thin content issues: if the page is just a product grid with no editorial content, recommend adding a buying guide intro, comparison chart, and FAQ section
- Provide a content brief with specific sections to add, target word count, and internal linking opportunities

## Guidelines

- Always check `.claude/product-marketing-context.md` before asking discovery questions
- Start every audit with crawlability and indexation before moving to on-page issues, since nothing else matters if Google cannot find the pages
- Provide specific, actionable fixes rather than vague recommendations like "improve your content"
- Prioritize findings by impact: critical indexation blockers first, then high-impact performance issues, then incremental on-page improvements
- Always compare against top-ranking competitors for target keywords to identify content gaps
- Flag quick wins separately so the user can get early results while working on larger fixes
- Include evidence for every finding: show the specific URL, the specific issue, and how you identified it
- For site migrations, always check redirect mapping completeness as the first diagnostic step
- Reference free tools (Search Console, PageSpeed Insights) before paid tools since not every user has Ahrefs or Semrush access

Related Skills

swiftui-performance-audit

26
from TerminalSkills/skills

Audit and optimize SwiftUI runtime performance. Use when: diagnosing slow rendering, janky scrolling, excessive view updates, or high CPU/memory usage in SwiftUI apps.

security-audit

26
from TerminalSkills/skills

Scan code for security vulnerabilities, misconfigurations, and exposed secrets. Use when a user asks to audit security, find vulnerabilities, check for OWASP issues, scan for secrets, review dependencies for CVEs, detect SQL injection, find XSS vulnerabilities, or harden an application. Covers OWASP Top 10, dependency auditing, secrets detection, and generates fix recommendations with severity ratings.

project-skill-audit

26
from TerminalSkills/skills

Analyze a project and recommend highest-value skills to create or update. Use when: auditing project skills, getting skill recommendations, or reviewing existing skill coverage.

audit-logging

26
from TerminalSkills/skills

Implement tamper-evident audit logs for compliance (SOC 2, HIPAA, PCI DSS). Use when building compliance audit trails, tracking who did what and when, or implementing immutable event logs that satisfy regulatory retention requirements.

accessibility-auditor

26
from TerminalSkills/skills

Audit web pages and components for WCAG 2.2 accessibility compliance. Use when a user asks to check accessibility, find a11y issues, audit for WCAG compliance, fix screen reader problems, check color contrast, ensure keyboard navigation works, or prepare for accessibility regulations like the European Accessibility Act or ADA.

zustand

26
from TerminalSkills/skills

You are an expert in Zustand, the small, fast, and scalable state management library for React. You help developers manage global state without boilerplate using Zustand's hook-based stores, selectors for performance, middleware (persist, devtools, immer), computed values, and async actions — replacing Redux complexity with a simple, un-opinionated API in under 1KB.

zoho

26
from TerminalSkills/skills

Integrate and automate Zoho products. Use when a user asks to work with Zoho CRM, Zoho Books, Zoho Desk, Zoho Projects, Zoho Mail, or Zoho Creator, build custom integrations via Zoho APIs, automate workflows with Deluge scripting, sync data between Zoho apps and external systems, manage leads and deals, automate invoicing, build custom Zoho Creator apps, set up webhooks, or manage Zoho organization settings. Covers Zoho CRM, Books, Desk, Projects, Creator, and cross-product integrations.

zod

26
from TerminalSkills/skills

You are an expert in Zod, the TypeScript-first schema declaration and validation library. You help developers define schemas that validate data at runtime AND infer TypeScript types at compile time — eliminating the need to write types and validators separately. Used for API input validation, form validation, environment variables, config files, and any data boundary.

zipkin

26
from TerminalSkills/skills

Deploy and configure Zipkin for distributed tracing and request flow visualization. Use when a user needs to set up trace collection, instrument Java/Spring or other services with Zipkin, analyze service dependencies, or configure storage backends for trace data.

zig

26
from TerminalSkills/skills

Expert guidance for Zig, the systems programming language focused on performance, safety, and readability. Helps developers write high-performance code with compile-time evaluation, seamless C interop, no hidden control flow, and no garbage collector. Zig is used for game engines, operating systems, networking, and as a C/C++ replacement.

zed

26
from TerminalSkills/skills

Expert guidance for Zed, the high-performance code editor built in Rust with native collaboration, AI integration, and GPU-accelerated rendering. Helps developers configure Zed, create custom extensions, set up collaborative editing sessions, and integrate AI assistants for productive coding.

zeabur

26
from TerminalSkills/skills

Expert guidance for Zeabur, the cloud deployment platform that auto-detects frameworks, builds and deploys applications with zero configuration, and provides managed services like databases and message queues. Helps developers deploy full-stack applications with automatic scaling and one-click marketplace services.