Optimize Growth

What it does

The skill evaluates a project's web presence for search engine optimization (SEO) and answer-engine optimization (GEO). It analyzes critical aspects such as rendering, crawlability, metadata, sitemap configuration, and structured data. The process identifies areas for improvement in internal linking, AI-crawler policy, and content strategy for better citability. It can operate in an audit-only mode, providing a report, or an optimize mode to apply suggested fixes.

When it fits

Before deploying a new web project or significant updates to ensure optimal search engine and answer-engine performance.
During the development cycle to integrate SEO and GEO best practices early and maintain a strong online footprint.
When aiming to grow the project's overall visibility, improve its ranking, and enhance its presence in AI-driven answer engines.

Setup

Copy the skill definition file to the repository path .claude/skills/optimize-growth/SKILL.md.
Invoke the skill within Claude Code by typing /optimize-growth.
For an audit report, use /optimize-growth audit, and to apply fixes, use /optimize-growth optimize.

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 -d app/sitemap.xml app/sitemaps app/sitemap.ts app/robots.ts src/app/sitemap.xml src/app/sitemaps src/app/sitemap.ts src/app/robots.ts scripts/generate-sitemap.mjs public/sitemap.xml public/sitemaps 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).