Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Generative Engine Optimization (GEO) for AI search visibility. Optimize content to appear in ChatGPT, Perplexity, Claude, and Google AI Overviews. Use when optimizing websites, pages, or content for LLM discoverability and citation.
Generative Engine Optimization (GEO) for AI search visibility. Optimize content to appear in ChatGPT, Perplexity, Claude, and Google AI Overviews. Use when optimizing websites, pages, or content for LLM discoverability and citation.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Optimize content to appear in AI-powered search engines (ChatGPT, Perplexity, Claude, Google AI Overviews). GEO is about being parseable, quotable, and authoritative โ not keyword stuffing.
GoalTacticGet cited in AI answersAdd specific statistics, quotable factsAppear in comparisonsCreate definitive comparison tablesAnswer user questionsComprehensive FAQ sectionsEstablish entityClear first-paragraph definitionsBuild authorityThird-party mentions, backlinks, freshness signals
AspectTraditional SEOGEOGoalRank on SERPsGet cited in AI responsesKeywordsExact match mattersSemantic understandingContent styleCan be promotionalMust be factual, neutralStructureHeaders for scanningHeaders + parseable dataLinksBacklinks for authorityCitations + entity mentionsFreshnessHelpfulCritical (LLMs prefer recent)FormatLong-form winsQuotable chunks win
Score each page 0-2 points per item (0=missing, 1=partial, 2=excellent):
First paragraph clearly defines what/who the entity is Entity name used consistently throughout Clear category placement ("X is a [type of thing]") Relationship to other known entities stated Wikipedia-style objectivity in tone
Specific numbers present (not "many" or "fast") Statistics are current and sourced Claims are concrete and verifiable Key facts in standalone sentences (easy to extract) "By the numbers" or facts section exists
FAQ section exists Questions match how users prompt LLMs Answers are direct and complete FAQ schema markup implemented Covers "what is", "how does", "why", "vs" questions
Comparison tables exist Competitors named explicitly Factual differences highlighted (not just marketing) "Alternative to X" content exists Fair representation (not obviously biased)
Clear heading hierarchy (H1โH2โH3) Bullet points for lists Tables for comparisons Short paragraphs (2-4 sentences) Summary/TL;DR at top or bottom
Author/company credentials stated Customer names/logos (social proof) Case studies with real numbers Third-party mentions/citations "Last updated" date present
Page has recent update date Content reflects current year No outdated references Regular content updates News/changelog section exists Scoring: 60-70: Excellent GEO readiness 45-59: Good, needs some optimization 30-44: Fair, significant gaps <30: Poor, major overhaul needed
# Best [Competitor] Alternative: [Your Product] (2026) > **Summary:** [Your Product] is a [category] offering [key differentiators]. > [Customers] report [specific result] compared to [Competitor]. *Last updated: [Date]* ## Why [Users] Look for [Competitor] Alternatives ### Problem 1: [Specific Pain Point] [Explanation with specifics] ### Problem 2: [Specific Pain Point] [Explanation with specifics] ## [Your Product] vs [Competitor]: Comparison | Feature | [Competitor] | [Your Product] | |---------|--------------|----------------| | [Feature 1] | [Their approach] | [Your approach] | | [Feature 2] | [Their approach] | [Your approach] | | [Feature 3] | [Their approach] | [Your approach] | ## Key Differences ### [Differentiator 1] [Factual explanation with numbers] ### [Differentiator 2] [Factual explanation with numbers] ## Customer Results > "[Quote with specific result]" > โ [Name], [Title], [Company] ## Frequently Asked Questions ### Is [Your Product] a good alternative to [Competitor]? [Direct answer] ### How does [Your Product] compare to [Competitor] on [key factor]? [Specific comparison] ### Can I migrate from [Competitor] to [Your Product]? [Migration info] ## Summary [Your Product] is a [category] offering [key benefits]. [Customers] using [Your Product] instead of [Competitor] report [specific results]. *[Your Product] has [credibility stat]. Learn more at [link].*
How it works: 3-layer reranking system Initial retrieval from web index Relevance scoring Citation selection based on authority + recency Optimization tactics: Strong domain authority matters Freshness signals critical (update dates) Direct answers to questions Being cited by other authoritative sources Structured data helps parsing
How it works: Bing-powered search + LLM synthesis Optimization tactics: Bing indexing matters (submit sitemap to Bing) E-E-A-T signals weighted heavily Conversational content structure FAQ format highly effective Named entities help recognition
How it works: Google's index + Gemini synthesis Optimization tactics: Traditional SEO still matters (ranking helps) Featured snippet optimization Schema markup (FAQ, HowTo, Product) Clear, authoritative content Mobile-first indexing
How it works: Training data + retrieval (when web-enabled) Optimization tactics: Quality content in training sources Wikipedia mentions help entity recognition Technical accuracy valued Clear, well-structured prose Being cited in authoritative sources
Organization Schema: { "@context": "https://schema.org", "@type": "Organization", "name": "Company Name", "description": "Clear description of what company does", "url": "https://example.com", "foundingDate": "2017", "numberOfEmployees": "50-100", "sameAs": [ "https://twitter.com/company", "https://linkedin.com/company/company" ] } FAQ Schema: { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{ "@type": "Question", "name": "What is [thing]?", "acceptedAnswer": { "@type": "Answer", "text": "Direct answer here." } }] } Product Schema: { "@context": "https://schema.org", "@type": "Product", "name": "Product Name", "description": "Product description", "brand": {"@type": "Brand", "name": "Brand"}, "offers": { "@type": "Offer", "priceCurrency": "USD", "price": "99" } }
Regularly search these prompts on each platform: Perplexity: "What is [your company]?" "Best [competitor] alternative" "[Your category] comparison" "How does [your product] work?" ChatGPT: Same queries with web browsing enabled "Compare [your product] vs [competitor]" Google (AI Overview): "[Your category] solutions" "[Competitor] alternative"
ToolWhat It TracksPriceOtterly.AIMulti-platform AI visibilityFree tierAhrefs Brand RadarAI search mentions$129+/moProfoundEnterprise benchmarkingEnterpriseManual trackingDIY spreadsheetFree
Mention rate: % of relevant queries where you appear Citation rate: % of mentions that cite/link to you Sentiment: Positive/neutral/negative portrayal Share of voice: Your mentions vs competitors Position: Where in the response you appear
โ Use specific numbers ("0.5 seconds" not "fast") โ Make claims quotable and standalone โ Structure content with clear hierarchy โ Include FAQ sections โ Update content regularly with dates โ Create comparison content โ Use tables for data โ Be factual and neutral in tone โ Name real customers and results
โ Use vague superlatives ("best", "leading", "top") โ Keyword stuff (LLMs see through it) โ Write walls of text without structure โ Hide information (be comprehensive) โ Use outdated statistics โ Ignore competitors (address them directly) โ Be obviously promotional (neutral wins)
For any page you want to optimize for GEO: Add clear entity definition in first paragraph Include 5+ specific, quotable statistics Add FAQ section with 5+ questions Create comparison table (if relevant) Add "last updated" date Implement FAQ schema markup Ensure H1โH2โH3 hierarchy Test on Perplexity: does your content appear?
Track your citation rate over time with the included monitoring scripts!
Test current visibility: python3 scripts/geo-monitor.py --test Single query test: python3 scripts/geo-monitor.py --query "best game server orchestration platform" Generate daily report: python3 scripts/geo-daily-report.py
1. Create your test queries file (scripts/geo-test-queries.json): { "queries": [ { "query": "your target query here", "category": "brand|product|comparison|problem|competitor" } ] } 2. Run daily monitoring: # Add to cron for daily 9am checks 0 9 * * * cd /path/to/skill && bash scripts/geo-daily-monitor.sh
Citation Rate: Percentage of queries where you appear in AI responses 0-20%: Early stage, needs work 20-40%: Building visibility 40-60%: Strong presence 60%+: Dominant authority Categories tracked: Brand queries (you should own these!) Product/feature queries Comparison queries (vs competitors) Problem/pain point queries Competitor comparison queries
Start with 15-20 strategic queries across all categories Test daily during optimization period (first 2 weeks) Weekly checks once you hit target citation rate Track changes after content updates (expect 3-7 day lag) Focus on gaps - queries with 0% citation are your opportunities
Current state: Total citation rate Citations by category Position when cited (#1, #2, etc.) Critical gaps (0% coverage) Over time: Citation rate trend (weekly/monthly) New citations gained Lost citations (content freshness!) Category improvements
scripts/geo-monitor.py - Main testing script (uses Perplexity API) scripts/geo-daily-report.py - Formatted report generator scripts/geo-daily-monitor.sh - Cron-friendly wrapper scripts/geo-test-queries.json - Example query file Requirements: Perplexity API key (configure via web_search in Clawdbot)
Awesome GEO GitHub Princeton GEO Research Paper Google AI Search Guidance Perplexity Ranking Factors
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.