# Audit Your Website SEO and Prioritize Fixes

SEO problems can hide across crawling, metadata, content, performance, and international targeting. This skill organizes evidence into clear findings and a prioritized action plan.

## Install

```bash
npx skillstore add coreyhaines31/seo-audit
```

## Metadata

- Status: approved
- Slug: coreyhaines31-seo-audit
- Version: 2.0.0
- Author version: 2.0.0
- Skillstore revision: r1
- Version status: valid
- Tree hash: dc5703d8f23c86e01d676540b896073407bc0f5b378d1ca2897ccd2837acc6c2
- Author: coreyhaines31
- GitHub username: coreyhaines31
- License: MIT
- Repository: https://github.com/coreyhaines31/marketingskills/tree/main/skills/seo-audit
- Ref: 635f69fb8d2f4e6330ba47a4e5a0fb239c04d110
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/coreyhaines31-seo-audit
- Manifest: https://skillstore.pages.dev/api/skills/coreyhaines31-seo-audit/manifest

## Capabilities

- Reviews crawlability, indexation, robots directives, XML sitemaps, canonicals, redirects, and site architecture.
- Assesses Core Web Vitals, mobile usability, HTTPS, URL structure, and common performance factors.
- Checks titles, meta descriptions, headings, keyword targeting, internal links, images, and content depth.
- Diagnoses hreflang, locale canonicals, international sitemaps, locale URLs, and translation quality.
- Adapts checks for SaaS, e-commerce, blogs, multilingual sites, and local businesses.
- Produces evidence-based findings with impact, fixes, priorities, quick wins, and longer-term actions.

## Use Cases

- Recover SaaS Search Traffic: Diagnose ranking losses after a migration, release, or search update, then prioritize recovery work.
- Control E-commerce Crawl Waste: Review faceted navigation, duplicate product pages, crawl budget, pagination, and out-of-stock handling.
- Validate International SEO: Check hreflang clusters, locale canonicals, multilingual sitemaps, translated content, and locale URL consistency.

## Prompt Templates

### Run a Basic SEO Audit

```
Audit [URL] for technical, on-page, and content SEO issues. Ask for missing context, then rank findings by impact and effort.
```

### Diagnose a Ranking Problem

```
Diagnose why [page URL] is not ranking for [keyword]. Review intent, metadata, depth, indexation, canonicals, internal links, and cannibalization.
```

### Investigate a Traffic Decline

```
Investigate the traffic decline after [migration or release]. Use provided Search Console data, redirects, canonicals, robots directives, sitemaps, and URL changes.
```

### Audit International SEO

```
Audit [site] across [locales]. Validate reciprocal hreflang, self-canonicals, x-default, sitemap alternates, locale URLs, translated content, and conflicting signals.
```

## Limitations

- It cannot access Search Console, analytics, or paid tools unless the user provides access or exports.
- Static fetch tools cannot confirm JavaScript-injected schema markup; use a browser or Rich Results Test.
- Findings depend on the supplied URLs, crawl data, business context, and target keywords.
- It audits structured data but directs implementation work to a dedicated schema skill.

## Best Practices

- Provide priority URLs, target keywords, recent site changes, competitors, and current traffic context.
- Share Search Console exports, crawl reports, and analytics evidence when available.
- Validate JavaScript-rendered schema with a browser, Rich Results Test, or rendering crawler.

## Anti Patterns

- Do not report missing schema from static fetch output alone.
- Do not recommend fixes without evidence, impact, priority, and affected URLs.
- Do not treat every SEO checklist item as equally urgent.

## Security Audit

- Audited at: 2026-07-13T18:40:09.29\+00:00
- Summary: All 41 static findings are false positives caused by Markdown code formatting, ordinary SEO terminology, and benign reference URLs. The skill contains no executable scripts, shell commands, credential handling, or prompt injection. Its network guidance points only to an example domain and Google's Rich Results Test.

## Stats

- Views: 135
- Downloads: 13
- Favorites: 0
- Popularity score: 0