research
The /research command analyzes SEO opportunities by investigating keyword demand, search results intent, competitor strategies, and content gaps. Use it to understand the search landscape before creating content, identify missing topics your site should target, map content architecture with pillar and supporting pages, or compare your presence against competitors across rankings and backlinks.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/aaron-he-zhu/seo-geo-claude-skills/HEAD/commands/research.md -o ~/.claude/commands/research.mdresearch.md
# Research Command Understand the opportunity and landscape: keyword demand, SERP intent, competitors, content gaps, and site/topic/entity architecture. ## Route - keyword-research - serp-analysis - content-gap-analysis - competitor-analysis - backlink-analyzer - entity-optimizer - internal-linking-optimizer ## Rules - Discover search demand, SERP intent, topic clusters, and content opportunities; keep AI-answer-inclusion diagnosis in `/aaron:audit --visibility`. - With `--competitors`, compare across rankings, content coverage, backlinks, authority, and AI citation visibility; return a battlecard, gaps, priority opportunities, and evidence mode. - With `--map` (or a known opportunity set), turn findings into a content architecture, topic/entity map, and internal-link plan: clusters, pillar/supporting pages, orphan risks, anchor guidance, and next briefs. - Keep evidence mode visible (tool vs. estimate); hand off to `/aaron:create` for production. ## Output Return inline artifacts by default. Files may be written only when the user explicitly asks and the runtime can write.
Use when the user asks to "optimize for AI citations"; improves citation readiness for ChatGPT, Perplexity, AI Overviews, Gemini, and Claude. Not for structural on-page SEO — use on-page-seo-auditor; not for net-new drafting — use seo-content-writer. AI引用优化/GEO优化/AI搜索
Use when the user asks to "optimize meta tags"; improves titles, descriptions, Open Graph, Twitter cards, and CTR test variants. Not for JSON-LD structured data — use schema-markup-generator; not for body copy — use seo-content-writer. 标题优化/元描述/CTR
Use when the user asks to "generate schema"; creates JSON-LD for FAQ, HowTo, Article, Product, and LocalBusiness rich-result candidates. Not for title/meta-description tags — use meta-tags-optimizer; not for crawl/index technical issues — use technical-seo-checker. Schema标记/结构化数据
Use when the user asks to "write SEO content"; drafts new posts, articles, and landing pages with keywords, headers, snippets, and evidence boundaries. Not for AI-citation/GEO readiness scoring — use geo-content-optimizer; not for updating decaying existing content — use content-refresher. SEO文章写作/内容优化
Evaluate and harden what exists: on-page SEO, content quality (CORE-EEAT), technical SEO, AI-visibility/GEO readiness, and domain authority (CITE). Not sure? Use /aaron:auto.
Run the SEO/GEO pack-local Aaron workflow implied by a natural-language goal, at the smallest safe depth. Add --deep for exhaustive, maximum-rigor, or stress-test runs.
Produce SEO/GEO content end-to-end: brief, draft one asset or a series, refresh stale content, and prepare a CMS-neutral publish package. Not sure? Use /aaron:auto.
Track and remember over time: rankings, alerts, performance reports, and project memory. Not sure? Use /aaron:auto.