skills/strategies/structure/seo-audit/SKILL.md
When the user wants to run an SEO audit, technical SEO audit, or site health check. Also use when the user mentions "SEO audit," "technical audit," "site audit," "crawl audit," "indexing audit," "SEO health," or "fix SEO issues." For prioritization and organic strategy, use seo-strategy. For GSC data analysis, use google-search-console.
npx skillsauth add kostja94/marketing-skills seo-auditInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Guides end-to-end SEO audit: technical foundation, on-page, content, and off-page. Execute in order—technical blockers prevent indexing; on-page limits rankings; content and off-page build authority. Use when auditing an existing site or planning fixes.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
| Phase | Focus | Skills | |-------|-------|--------| | 1. Technical | Crawl, index, sitemap | robots-txt, xml-sitemap, canonical-tag, indexing, site-crawlability | | 2. On-Page | Metadata, structure, schema | title-tag, meta-description, page-metadata, schema-markup, internal-links, heading-structure | | 3. Content | Gaps, intent, optimization | keyword-research, content-strategy, content-optimization | | 4. Off-Page | Backlinks, authority | link-building, backlink-analysis |
Principle: Fix foundation before optimizing pages. See seo-strategy for workflow and prioritization.
| Item | Check | Skill | |------|-------|-------| | robots.txt | Syntax; not blocking important pages | robots-txt | | Sitemap | Submitted to GSC; indexable pages only; ≤50K URLs per sitemap | xml-sitemap | | HTTPS | Sitewide; valid certificate | canonical-tag | | 404/5xx | Proper status codes; fix or redirect | site-crawlability | | noindex | No accidental noindex on key pages | indexing | | Canonical | Correct; no conflicts | canonical-tag | | Core Web Vitals | LCP ≤2.5s, INP ≤200ms, CLS <0.1 | core-web-vitals | | Mobile | Mobile-first; content parity; no intrusive interstitials | mobile-friendly | | Crawlability | Redirect chains, broken links, orphan pages | site-crawlability |
| Item | Check | Skill | |------|-------|-------| | Title | Unique; 50–60 chars; keyword in first 10 words | title-tag | | Meta description | 150–160 chars; CTA | meta-description | | Headings | One H1; H1→H2→H3 hierarchy | heading-structure | | Images | Alt text; no decorative alt for decorative images | image-optimization | | Schema | Valid; Rich Results Test | schema-markup | | Internal links | From strong pages; descriptive anchors | internal-links | | Duplicate content | Canonical; consolidate or differentiate | canonical-tag |
| Phase | Focus | Skill | |-------|-------|-------| | Content gap | Missing topics vs competitors | content-strategy, competitor-research | | Intent match | Content matches search intent | content-optimization | | Backlinks | Toxic links; link gap vs competitors | backlink-analysis, link-building |
| Cadence | Use | |---------|-----| | Full audit | Quarterly | | Check-ins | Monthly (GSC, indexing, Core Web Vitals) |
data-ai
When the user wants to add or optimize Twitter Card metadata for X (Twitter) link previews. Also use when the user mentions "Twitter Card," "twitter:card," "twitter:image," "twitter:title," "X preview," or "tweet preview." For Facebook/LinkedIn previews, use open-graph.
testing
When the user wants to add or optimize Open Graph metadata for social sharing. Also use when the user mentions "Open Graph," "og:tags," "og:title," "og:image," "og:description," "Facebook preview," "LinkedIn preview," or "social share preview." For X (Twitter) link previews, use twitter-cards. For SERP title/description, use title-tag and meta-description.
tools
When the user wants to create, optimize, or structure Terms of Service page. Also use when the user mentions "terms of service," "terms and conditions," "terms of use," "user agreement," "ToS," "legal terms," "service agreement," or "terms page." For legal overview page, use legal-page-generator.
development
When the user wants to create or optimize a shipping or delivery information page. Also use when the user mentions "shipping," "delivery," "shipping policy," "delivery times," "shipping page," "free shipping," "shipping rates," "delivery options," "shipping info," "cross-border shipping," "international delivery," or "order tracking." For legal overview, use legal-page-generator.