From null-to-hero
Use when the user wants to audit a website, analyze a page, plan an SEO strategy, fix technical SEO, add schema markup, improve content quality, optimize for AI search engines, build local SEO, handle hreflang/i18n, generate sitemaps, optimize images, run programmatic SEO, build competitor comparison pages, cluster keywords, optimize for Search Experience (SXO), monitor SEO drift, analyze backlinks, handle e-commerce SEO, or export a client report. Covers full site audits with parallel sub-agents, single-page analysis, SEO strategy with industry templates, robots.txt, sitemaps, Core Web Vitals, JSON-LD, E-E-A-T, content quality, GEO, llms.txt, AI crawler access, local SEO, hreflang, programmatic SEO, keyword clustering, SXO, drift monitoring, backlink analysis, e-commerce SEO, and PDF report export. Use for any request containing: SEO, rank, Google, search engine, schema, sitemap, robots.txt, meta tags, keywords, AI search, local SEO, hreflang, backlinks, programmatic, ecommerce, or visibility.
How this skill is triggered — by the user, by Claude, or both
Slash command
/null-to-hero:seo [audit|page|plan|technical|schema|content|geo|sitemap|images|local|hreflang|programmatic|competitor-pages|cluster|drift|backlinks|ecommerce|indexnow] [url | business-type | keyword][audit|page|plan|technical|schema|content|geo|sitemap|images|local|hreflang|programmatic|competitor-pages|cluster|drift|backlinks|ecommerce|indexnow] [url | business-type | keyword]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Complete SEO toolkit for websites — from zero to ranking. Run a full audit, fix technical issues, generate schema markup, optimize content, get found by AI search engines, and deliver polished client reports.
references/action-plan.mdreferences/audit.mdreferences/backlinks.mdreferences/cluster.mdreferences/competitor-pages.mdreferences/content.mdreferences/drift.mdreferences/ecommerce.mdreferences/geo.mdreferences/head-meta.mdreferences/hreflang.mdreferences/images.mdreferences/indexnow.mdreferences/local.mdreferences/page.mdreferences/performance.mdreferences/plan-assets/agency.mdreferences/plan-assets/ecommerce.mdreferences/plan-assets/generic.mdreferences/plan-assets/local-service.mdComplete SEO toolkit for websites — from zero to ranking. Run a full audit, fix technical issues, generate schema markup, optimize content, get found by AI search engines, and deliver polished client reports.
Three doors cover most requests: /seo audit [url] to learn where you stand
(bare /seo [url] runs it), /seo plan [business-type] for the strategy, and
/audit full [url] when the whole site (design and defects included) should be
checked in one pass. Everything else in the table below is a specialist pass.
| Command | What it does | Reference |
|---|---|---|
audit [url] | Full site SEO audit — crawls up to 500 pages, scores 7 dimensions, outputs ACTION-PLAN.md | references/audit.md |
page [url] | Deep single-page analysis — title, meta, H1-H6, schema, images, content quality, search-experience alignment (intent, page-type match), score | references/page.md + references/sxo.md |
plan [business-type] | Complete SEO strategy — architecture, content pillars, keyword plan, 4-phase roadmap | references/plan.md + references/plan-assets/ |
technical [url] | Technical audit — robots.txt, sitemaps, Core Web Vitals, mobile, security, JS rendering | references/technical.md |
schema [url] | Detect, validate, and generate Schema.org JSON-LD — Organization, Article, Product, etc. | references/schema.md |
content [url] | E-E-A-T analysis, readability, keyword density, AI citation readiness | references/content.md |
geo [url] | AI search optimization — Google AI Overviews, ChatGPT, Perplexity, llms.txt, brand signals | references/geo.md |
sitemap [url] | XML sitemap validation and generation with industry-specific templates | references/sitemap.md |
indexnow [url] | Instant-indexing pings to Bing, Yandex, Naver and Seznam — key setup, single/batch/sitemap submission; the fast lane into the indexes that feed AI answers | references/indexnow.md |
images [url] | Image SEO audit — alt text, formats (WebP/AVIF), lazy loading, CLS, LCP | references/images.md |
local [business] | Local SEO — Google Business Profile, NAP consistency, citations, reviews, LocalBusiness schema | references/local.md |
hreflang [url] | Hreflang validation and generation for multilingual and multi-region sites | references/hreflang.md |
programmatic [url] | Programmatic SEO — URL patterns, quality gates (warn 100+, hard stop 500+), deduplication | references/programmatic.md |
competitor-pages [url] | "X vs Y" and "alternatives to X" pages with feature matrices, FAQ schema, conversion hooks | references/competitor-pages.md |
cluster [keyword] | Semantic keyword clustering — intent-based grouping, content architecture, gap analysis | references/cluster.md |
drift [url] | SEO drift monitoring — baseline capture, change detection, history tracking | references/drift.md |
backlinks [url] | Backlink profile analysis via free data sources (Moz, Bing, Common Crawl, GSC) | references/backlinks.md |
ecommerce [url] | E-commerce SEO — product pages, category pages, faceted navigation, Product schema | references/ecommerce.md |
Legacy name: report (the retired /seo sub-command) now routes to /audit report
(../audit/references/report.md holds the SEO-scope
skeleton). Accepted names are registered in tools/data/intents.csv.
If PRODUCT.md or DIRECTION.md exist at the project root, read them first: brand names, entities, tone and anti-references committed there drive schema name/sameAs, content voice and keyword framing.
When the user invokes a command:
Load the matching reference file using the Read tool
Follow the instructions in that reference exactly Every command that produces recommendations formats them per references/action-plan.md.
If no command is specified:
auditplan| User says | Run |
|---|---|
| "audit my site" / "check my SEO" | audit |
| "analyze this page" / "on-page SEO" | page |
| "SEO strategy" / "I'm building a new site" | plan |
| "technical SEO" / "robots.txt" / "sitemap issues" | technical |
| "schema markup" / "structured data" / "rich results" | schema |
| "content quality" / "E-E-A-T" / "improve my article" | content |
| "AI search" / "ChatGPT visibility" / "AI Overviews" | geo |
| "generate sitemap" / "sitemap validation" | sitemap |
| "index this now" / "ping Bing" / "instant indexing" | indexnow |
| "image SEO" / "alt text" / "WebP conversion" | images |
| "local SEO" / "Google Business Profile" / "NAP" | local |
| "hreflang" / "multilingual SEO" / "i18n SEO" | hreflang |
| "programmatic SEO" / "scale pages" / "template pages" | programmatic |
| "vs page" / "alternatives to X" / "comparison page" | competitor-pages |
| "keyword clusters" / "content architecture" / "gap analysis" | cluster |
| "search experience" / "intent alignment" / "SXO" | page |
| "SEO drift" / "baseline" / "track ranking changes" | drift |
| "backlinks" / "link profile" / "link building" | backlinks |
| "e-commerce SEO" / "product pages" / "faceted nav" | ecommerce |
| "SEO report" / "client report" / "export PDF" | /audit report |
The plan command uses industry-specific templates in references/plan-assets/:
saas.md — SaaS / softwareecommerce.md — E-commercelocal-service.md — Local service businessespublisher.md — Content publishers / mediaagency.md — Agenciesgeneric.md — General / unknown business type (fallback)New site from scratch: plan → build the site → technical → schema → audit
Existing site needs help: audit → technical (fix blockers) → content → geo
Page not ranking: page → content → schema
Invisible to AI search: geo → content → technical
International expansion: hreflang → technical → content
E-commerce launch: ecommerce → schema → technical → audit
Programmatic site: programmatic → cluster → plan → audit
Client deliverable: audit → /audit report
Local business: local → schema → technical
npx claudepluginhub mariusyvard/nulltohero --plugin null-to-heroGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.