Help us improve
Share bugs, ideas, or general feedback.
From aaron-seo-geo
Optimizes content for citation by AI engines (ChatGPT, Perplexity, Gemini, Claude, AI Overviews). Improves structure, factual density, quotable statements, and source attribution for generative engine visibility.
npx claudepluginhub aaron-he-zhu/seo-geo-claude-skills --plugin aaron-seo-geoHow this skill is triggered — by the user, by Claude, or both
Slash command
/aaron-seo-geo:geo-content-optimizer <content URL or text> [target AI engine]When to use
Use when optimizing content for AI engines like ChatGPT, Perplexity, AI Overviews, Gemini, Claude, or Copilot. Also for AI citation optimization, generative engine visibility, AI引用优化, AI搜索优化, GEO优化, or 让AI引用我.
<content URL or text> [target AI engine]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Optimizes content for AI-generated answers and citation surfaces such as ChatGPT, Perplexity, Gemini, Claude, and AI Overviews.
Audits content for GEO, rewrites for AI citation, and generates per-engine strategies to rank in ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews.
Rewrites content using empirically-validated GEO tactics (citations, quotes, statistics, fluency, authoritative tone) to boost visibility in generative engine responses.
Provides GEO fundamentals for optimizing content to be cited by AI search engines (ChatGPT, Claude, Perplexity, Gemini). Covers RAG factors, checklists, crawlers, and measurement.
Share bugs, ideas, or general feedback.
Optimizes content for AI-generated answers and citation surfaces such as ChatGPT, Perplexity, Gemini, Claude, and AI Overviews.
Improves structure, authority signals, factual density, quotable statements, source attribution, and overall GEO readiness.
Optimize this content for GEO/AI citations: [content or URL]
Make this article more likely to be cited by AI systems
Write content about [topic] optimized for both SEO and GEO
Audit this content for GEO readiness and suggest improvements
AI Overview is eating clicks on 12 head queries — build a recovery plan
See references/ai-overview-recovery.md for the 4-phase playbook (measure → diagnose → rewrite → monitor) tailored to recovery scenarios (as opposed to generic GEO optimization).
Expected output: a ready-to-use asset or implementation-ready transformation plus a short handoff summary ready for memory/content/.
memory/entities/<slug>.md (per the entity-geo handoff schema) to populate display_name, description_short, ai_resolution_status and decide whether disambiguation boilerplate is needed. If the profile is missing or stale (>90 days), declare DONE_WITH_CONCERNS and recommend entity-optimizer as an open loop.memory/content/.memory/hot-cache.md and memory/open-loops.md; propose durable decisions as pending-decision items.Next Best Skill below when the asset is ready for review or deployment.Emit the standard shape from skill-contract.md §Handoff Summary Format.
Use ~~AI monitor and ~~SEO tool when connected; otherwise ask for target queries, content, engines, competitor examples, and known AI-citation gaps. See CONNECTORS.md.
When a user requests GEO optimization, run these five steps:
Reference: See references/instructions-detail.md for the full CORE-EEAT GEO target tables, AI engine preferences, analysis templates, optimization report template, self-check matrix, and examples.
User: "Optimize this paragraph for GEO: 'Email marketing is a good way to reach customers. It's been around for a while and many businesses use it.'"
Output adds a clear definition, dated/source-backed facts, structured list, quotable statements, and a before/after GEO score. See the full pattern in references/instructions-detail.md.
Reference: See the GEO Readiness Checklist in references/geo-optimization-techniques.md for the full checklist covering definitions, quotable content, authority, structure, and technical elements.
Answer first, be specific, cite dated sources, stay current, match query format, and build authority. Full list in references/instructions-detail.md.
On user confirmation, save a dated summary to memory/content/YYYY-MM-DD-<topic>.md and promote key conclusions to memory/hot-cache.md.