geo-fundamentals
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
Best use case
geo-fundamentals is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
Teams using geo-fundamentals should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/geo-fundamentals/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How geo-fundamentals Compares
| Feature / Agent | geo-fundamentals | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# GEO Fundamentals > Optimization for AI-powered search engines. --- ## 1. What is GEO? **GEO** = Generative Engine Optimization | Goal | Platform | |------|----------| | Be cited in AI responses | ChatGPT, Claude, Perplexity, Gemini | ### SEO vs GEO | Aspect | SEO | GEO | |--------|-----|-----| | Goal | #1 ranking | AI citations | | Platform | Google | AI engines | | Metrics | Rankings, CTR | Citation rate | | Focus | Keywords | Entities, data | --- ## 2. AI Engine Landscape | Engine | Citation Style | Opportunity | |--------|----------------|-------------| | **Perplexity** | Numbered [1][2] | Highest citation rate | | **ChatGPT** | Inline/footnotes | Custom GPTs | | **Claude** | Contextual | Long-form content | | **Gemini** | Sources section | SEO crossover | --- ## 3. RAG Retrieval Factors How AI engines select content to cite: | Factor | Weight | |--------|--------| | Semantic relevance | ~40% | | Keyword match | ~20% | | Authority signals | ~15% | | Freshness | ~10% | | Source diversity | ~15% | --- ## 4. Content That Gets Cited | Element | Why It Works | |---------|--------------| | **Original statistics** | Unique, citable data | | **Expert quotes** | Authority transfer | | **Clear definitions** | Easy to extract | | **Step-by-step guides** | Actionable value | | **Comparison tables** | Structured info | | **FAQ sections** | Direct 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 | Action | Purpose | |--------|---------| | Google Knowledge Panel | Entity recognition | | Wikipedia (if notable) | Authority source | | Consistent info across web | Entity consolidation | | Industry mentions | Authority signals | --- ## 7. AI Crawler Access ### Key AI User-Agents | Crawler | Engine | |---------|--------| | GPTBot | ChatGPT/OpenAI | | Claude-Web | Claude | | PerplexityBot | Perplexity | | Googlebot | Gemini (shared) | ### Access Decision | Strategy | When | |----------|------| | Allow all | Want AI citations | | Block GPTBot | Don't want OpenAI training | | Selective | Allow some, block others | --- ## 8. Measurement | Metric | How to Track | |--------|--------------| | AI citations | Manual monitoring | | "According to [Brand]" mentions | Search in AI | | Competitor citations | Compare share | | AI-referred traffic | UTM parameters | --- ## 9. Anti-Patterns | ❌ Don't | ✅ Do | |----------|-------| | Publish without dates | Add timestamps | | Vague attributions | Name sources | | Skip author info | Show credentials | | Thin content | Comprehensive coverage | --- > **Remember:** AI cites content that's clear, authoritative, and easy to extract. Be the best answer. --- ## Script | Script | Purpose | Command | |--------|---------|---------| | `scripts/geo_checker.py` | GEO audit (AI citation readiness) | `python scripts/geo_checker.py <project_path>` |
Related Skills
marketing-fundamentals
Core marketing concepts, psychology, and frameworks for effective marketing. Use for foundational knowledge on funnels, customer journey, positioning, value propositions, and marketing psychology.
routeros-fundamentals
RouterOS v7 domain knowledge for AI agents. Use when: working with MikroTik RouterOS, writing RouterOS CLI/script commands, calling RouterOS REST API, debugging why a Linux command fails on RouterOS, or when the user mentions MikroTik, RouterOS, CHR, or /ip /system /interface paths. Scope: RouterOS 7.x (long-term and newer) only — v6 is NOT covered and accuracy for v6 problems will be low.
testing-fundamentals
Auto-invoke when reviewing test files or discussing testing strategy. Enforces testing pyramid, strategic coverage, and stack-appropriate frameworks.
seo-fundamentals
Auto-invoke when reviewing HTML head, meta tags, or Next.js page components. Enforces semantic HTML and search optimization.
security-fundamentals
Auto-invoke when reviewing authentication, authorization, input handling, data exposure, or any user-facing code. Enforces OWASP top 10 awareness and security-first thinking.
performance-fundamentals
Auto-invoke when reviewing loops, data fetching, rendering, database queries, or resource-intensive operations. Identifies N+1 queries, unnecessary re-renders, memory leaks, and scalability issues.
fundamentals-gate
Verify code quality standards are met - naming, structure, DRY principles. Issues result in SUGGESTIONS for improvement.
frontend-fundamentals
Auto-invoke when reviewing React, Vue, or frontend component code. Enforces component architecture, state management patterns, and UI best practices.
error-handling-fundamentals
Auto-invoke when reviewing try/catch blocks, API error responses, async operations, or user feedback patterns. Enforces graceful degradation and meaningful error messages.
engineering-fundamentals
Auto-invoke for general code quality review. Enforces naming conventions, function size, DRY principles, SOLID principles, and code organization.
documentation-fundamentals
Auto-invoke when reviewing README files, JSDoc comments, or inline documentation. Enforces "WHY not WHAT" principle.
database-fundamentals
Auto-invoke when reviewing schema design, database queries, ORM usage, or migrations. Enforces normalization, indexing awareness, query optimization, and migration safety.