Install
openclaw skills install @aaron-he-zhu/geo-content-optimizerUse 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 content-writer. AI引用优化/GEO优化/AI搜索
openclaw skills install @aaron-he-zhu/geo-content-optimizerOptimizes 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 AI Overview Recovery 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.
Measuring whether GEO work paid off: the changes this skill makes (extractable, quotable, answer-shaped content) move citability — testable in minutes by handing a live-fetch engine the URL and asking the target query. That is a proxy. Whether an engine then cites you unprompted (surfacing) is gated by its crawl/index refresh — week-scale and confounded, not minute-level. Do not conflate the two or promise fast surfacing. The latency of each signal, and why outcome deltas need a control group, are defined in references/measurement-protocol.md.
Keyless AI-citation probe (Tavily): python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/tavily.py" search "<target query>" --answer --limit 10 runs that citability test against a real AI answer engine, no key needed — check whether the synthesized answer cites your URL/domain and where the page ranks among the scored sources. This is Measured for Tavily's own layer and an Estimated proxy for ChatGPT/Perplexity/Google AI Overviews (different indexes, different retrieval). Re-run after shipping changes for a minutes-scale citability read; unprompted surfacing stays week-scale per the paragraph above. See scripts/connectors/README.md.
When a user requests GEO optimization, run these five steps:
Label every metric Measured (tool/export), User-provided, or Estimated (model inference); never present an estimate as measured; if a required metric is unavailable, mark it N/A — do not invent it.
Reference: See Instructions Detail 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 Instructions Detail — Example.
Reference: See the GEO Readiness Checklist in GEO Optimization Techniques for the full checklist covering definitions, quotable content, authority, structure, and technical elements.
On user confirmation, save to memory/content/YYYY-MM-DD-<topic>.md — see Skill Contract §Save Results Template.
Termination note: keep a visited-set this session; if the recommended skill was already invoked, stop and report the chain complete rather than re-running it. Honor a max handoff depth of 3 to avoid loops (per skill-contract.md §Termination rules).