Awesome-omni-skill geo-fundamentals

Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).

install
source · Clone the upstream repo
git clone https://github.com/diegosouzapw/awesome-omni-skill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data-ai/geo-fundamentals-techwavedev" ~/.claude/skills/diegosouzapw-awesome-omni-skill-geo-fundamentals-a07707 && rm -rf "$T"
manifest: skills/data-ai/geo-fundamentals-techwavedev/SKILL.md
source content

GEO Fundamentals

Optimization for AI-powered search engines.


1. What is GEO?

GEO = Generative Engine Optimization

GoalPlatform
Be cited in AI responsesChatGPT, Claude, Perplexity, Gemini

SEO vs GEO

AspectSEOGEO
Goal#1 rankingAI citations
PlatformGoogleAI engines
MetricsRankings, CTRCitation rate
FocusKeywordsEntities, data

2. AI Engine Landscape

EngineCitation StyleOpportunity
PerplexityNumbered [1][2]Highest citation rate
ChatGPTInline/footnotesCustom GPTs
ClaudeContextualLong-form content
GeminiSources sectionSEO crossover

3. RAG Retrieval Factors

How AI engines select content to cite:

FactorWeight
Semantic relevance~40%
Keyword match~20%
Authority signals~15%
Freshness~10%
Source diversity~15%

4. Content That Gets Cited

ElementWhy It Works
Original statisticsUnique, citable data
Expert quotesAuthority transfer
Clear definitionsEasy to extract
Step-by-step guidesActionable value
Comparison tablesStructured info
FAQ sectionsDirect answers

5. GEO Content Checklist

Content Elements

  • Question-based titles
  • Summary/TL;DR at top
  • Original data with sources
  • Expert quotes (name, title)
  • FAQ section (3-5 Q&A)
  • Clear definitions
  • "Last updated" timestamp
  • Author with credentials

Technical Elements

  • Article schema with dates
  • Person schema for author
  • FAQPage schema
  • Fast loading (< 2.5s)
  • Clean HTML structure

6. Entity Building

ActionPurpose
Google Knowledge PanelEntity recognition
Wikipedia (if notable)Authority source
Consistent info across webEntity consolidation
Industry mentionsAuthority signals

7. AI Crawler Access

Key AI User-Agents

CrawlerEngine
GPTBotChatGPT/OpenAI
Claude-WebClaude
PerplexityBotPerplexity
GooglebotGemini (shared)

Access Decision

StrategyWhen
Allow allWant AI citations
Block GPTBotDon't want OpenAI training
SelectiveAllow some, block others

8. Measurement

MetricHow to Track
AI citationsManual monitoring
"According to [Brand]" mentionsSearch in AI
Competitor citationsCompare share
AI-referred trafficUTM parameters

9. Anti-Patterns

❌ Don't✅ Do
Publish without datesAdd timestamps
Vague attributionsName sources
Skip author infoShow credentials
Thin contentComprehensive coverage

Remember: AI cites content that's clear, authoritative, and easy to extract. Be the best answer.


Script

ScriptPurposeCommand
scripts/geo_checker.py
GEO audit (AI citation readiness)
python scripts/geo_checker.py <project_path>

AGI Framework Integration

Qdrant Memory Integration

Before executing complex tasks with this skill:

python3 execution/memory_manager.py auto --query "<task summary>"

Decision Tree:

  • Cache hit? Use cached response directly — no need to re-process.
  • Memory match? Inject
    context_chunks
    into your reasoning.
  • No match? Proceed normally, then store results:
python3 execution/memory_manager.py store \
  --content "Description of what was decided/solved" \
  --type decision \
  --tags geo-fundamentals <relevant-tags>

Note: Storing automatically updates both Vector (Qdrant) and Keyword (BM25) indices.

Agent Team Collaboration

  • Strategy: This skill communicates via the shared memory system.
  • Orchestration: Invoked by
    orchestrator
    via intelligent routing.
  • Context Sharing: Always read previous agent outputs from memory before starting.

Local LLM Support

When available, use local Ollama models for embedding and lightweight inference:

  • Embeddings:
    nomic-embed-text
    via Qdrant memory system
  • Lightweight analysis: Local models reduce API costs for repetitive patterns