What it does

This skill performs a comprehensive audit and optimization of your web project's visibility for search engines (SEO) and answer engines (GEO). It evaluates rendering, crawlability, metadata, sitemaps, structured data, internal linking, and content strategy, specifically addressing how AI models consume and cite your information. The skill leverages the seo-geo-optimizer agent for its deep analysis and remediation capabilities.

When to use it

Use this skill during development, before deploying a new feature or site, or regularly to improve your project's search engine ranking and answer-engine citability. It supports both audit mode (report only) and optimize mode (applies fixes), making it suitable for both analysis and active improvement cycles. Invoke it with /optimize-growth audit or /optimize-growth optimize.

How to set it up

To use this skill, place its definition file into your repository at .claude/skills/optimize-growth/SKILL.md. Once the skill is integrated, you can invoke it directly within Claude Code by typing /optimize-growth followed by an argument like audit or optimize. This will trigger the seo-geo-optimizer agent to perform the defined actions on your codebase.

Optimize Growth (SEO + GEO)

Run a combined SEO and GEO optimization pass on this project. SEO governs ranked-link visibility; GEO governs retrievability and citability by answer engines (Google AI Overviews, ChatGPT Search, Perplexity, Gemini, Copilot, Claude). GEO layers on top of SEO — it never overrides it.

Mode: $ARGUMENTS (default: audit — report only; optimize also applies fixes)

Context

Framework: ![ -d app ] && echo "Next (app router)" || ([ -f vite.config.ts ] || [ -f vite.config.js ] && echo "Vite exception (SPA)" || echo "unknown") Sitemap wiring: !ls app/sitemap.ts app/robots.ts scripts/generate-sitemap.mjs public/sitemap.xml 2>/dev/null || echo "none found" Dev-docs/API surface (for llms.txt relevance): !ls app/api 2>/dev/null; ls docs/api.yaml openapi.* 2>/dev/null || echo "no obvious API/docs surface" Site URL env: !grep -rl "NEXT_PUBLIC_SITE_URL\|APP_URL" .env.example .env.local next.config.* 2>/dev/null | head -3 || echo "not found in checked files"

Instructions

You are running as the seo-geo-optimizer agent. Follow that agent's full process against .claude/ref/growth/seo.md and .claude/ref/growth/geo.md:

Load both contracts and detect the stack + public content surface.
Run the SEO audit (seo.md) and the GEO audit (geo.md).
Prioritize findings BLOCKER → HIGH → MEDIUM → LOW.
If mode is optimize, apply fixes in dependency order (rendering → sitemap/robots incl. AI-crawler policy → metadata/JSON-LD → answer-first + citability content → entity hooks → funnel/analytics + GEO measurement → generate missing supporting pages to the §18 minimum), then run typecheck/lint/build and fix what your changes broke. Add llms.txt ONLY for a dev-docs/API product (geo.md §4) — never for a marketing site.
Report using the agent's summary template, ending with PASS / NEEDS ATTENTION / BLOCK DEPLOYMENT.

Do not commit, push, or open PRs. Do not add a crawler-blocking rule on your own — surface it as a recommendation for a human decision (geo.md §6, §14).

Optimize Growth