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.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
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) |
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
The English summary is being prepared. Showing the original description.
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
The English summary is being prepared. Showing the original description.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
The English summary is being prepared. Showing the original description.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
The English summary is being prepared. Showing the original description.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
The English summary is being prepared. Showing the original description.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
The English summary is being prepared. Showing the original description.