Skip to main content
skill CX Codex

geo-optimization — Claude Code skill: what it does, how to install

geo-optimization optimizes site content for LLM citations and answer engines like ChatGPT, Perplexity, Claude, and Google AI Overview.

Apache-2.0 ★ 141 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add fabricioctelles/skills --skill geo-optimization -a claude-code
Open on GitHub

What geo-optimization does

This skill prepares web pages for discovery by generative AI engines. It provides automated workflows for running visibility audits, building product comparison roundups with 8 to 12 items, generating FAQPage schema markup, and aligning headings with terminology typical for AI chat prompts.

It embeds content architecture patterns based on Cloudflare documentation practices. These include breaking large llms.txt catalogs into section-specific files to avoid grep loops, configuring clean Markdown delivery via the Accept: text/markdown header or /index.md URLs, and placing HTML directives for AI crawlers. Purely promotional content is flagged directly by its verification checklist.

Optimizing pages without permitting AI crawlers in robots.txt breaks discovery immediately, so the skill mandates checking crawler access before applying technical changes.

What it helps with

  • measure brand citation rates across LLMs using automated prompt sets
  • build structured comparison pages with comparison tables and FAQPage schema
  • split large root llms.txt files into sectional files to fit agent context windows
  • implement /index.md fallback routes and markdown content negotiation for agents

Example prompts for the agent

  • Run a full GEO audit on this product page and produce a prioritized roadmap
  • Create a roundup page comparing ten tools with an embedded FAQ schema
  • Generate a test kit of 50 prompts to evaluate our citation rate on Perplexity and ChatGPT

How to install geo-optimization

1Skills CLI (Vercel)

npx skills add fabricioctelles/skills --skill geo-optimization -a claude-code

2Manually: put the files in place

~/.claude/skills/geo-optimization/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/geo-optimization/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about geo-optimization

How to install geo-optimization in Claude Code?

Run npx skills add fabricioctelles/skills --skill geo-optimization -a claude-code. The file will be placed in ~/.claude/skills/geo-optimization/SKILL.md.

What does the geo-optimization skill do?

It guides content audits for AI search engines, structures comparison roundups, implements structured data, and designs llms.txt architectures.

How does this skill prevent agent grep loops in documentation?

It splits bulky documentation catalogs into separate section files like /docs/llms.txt and points agents to Markdown endpoints via /index.md, keeping directories within single context windows.

Source text

SKILL.md · Apache-2.0
---
name: geo-optimization
description: Optimize content for AI-generated responses and LLM citations (ChatGPT, Perplexity, Google AI Overview, Claude, Gemini). Use when the user mentions 'GEO', 'AEO', 'AI SEO', 'LLM optimization', 'citation rate', 'AI visibility', 'optimize for ChatGPT', 'roundup pages', or wants to audit pages for AI discoverability. Includes terminology alignment, FAQ schemas, and community signal strategies.
metadata:
  author: ft.ia.br
  version: "1.1"
  date: 2026-03-05
  repository: https://github.com/fabricioctelles/skills
  license: Apache 2.0
  category: code-quality-and-review
---

# GEO Optimization (Generative Engine Optimization)

## Quick Actions Menu

Present the following options at the start of the interaction to guide the work:

1. **Full GEO Audit**: Analyze the current page, deliver a score and a prioritized roadmap.
2. **Roundup Page Builder**: Create a comparison page optimized for LLMs.
3. **Terminology Optimizer**: Generate new titles, metas, and headings aligned with LLM searches.
4. **FAQ + Schema Generator**: Create a complete FAQ set with schema markup.
5. **Community Signal Booster**: Structure a strategy to generate reviews on Product Hunt and Reddit.
6. **Citation Rate Test Kit**: Create 50 ready-made prompts for visibility measurement.
7. **FULL PACKAGE**: Execute all of the above as a complete optimization package using Multi Agents.

Default to option 1 (Full GEO Audit) when no specific action is requested.

## GEO Workflow

Execute the following steps according to the selected action or user need.

For foundational principles that guide all optimization decisions, consult `references/guiding-principles.md`.

### 1. Measurement and Tracking (Initial Diagnosis)

Always begin by evaluating the current state of AI visibility.

- Create an initial set of 50–100 real prompts to test against ChatGPT, Google AI Overview, Perplexity, and Grok.
- Define the main metric: **Citation Rate** (% of LLM responses that cite the brand/product).

### 2. Terminology Alignment

- Map how people actually query LLMs — do not rely solely on Google keyword patterns.
- Adjust titles, meta descriptions, and headings to reflect natural LLM terminology.
- Example: Prefer "AI dictation and speech-to-text software" over "AI dictation apps".

### 3. Page Format and Structure

Recommend and create the formats that LLMs value most, prioritizing **Roundup / Comparison pages** (e.g., "The best [category] in 2026").

Include in each optimized page:
- Title aligned with LLM terminology.
- 8–12 products with authentic community reviews.
- Comparison table.
- Complete FAQPage schema.
- "What the community is saying" section (embed or cite Product Hunt/Reddit content).

### 4. Hard-to-Fake Signals and Community

- Encourage real reviews and discussions on Product Hunt, Reddit, and Quora.

### 4.5. Agent-Friendly Content Architecture (Cloudflare Best Practices)

Based on Cloudflare's docs optimization (31% fewer tokens, 66% faster answers):

**llms.txt Strategy for Large Sites:**
- Do NOT create one massive `llms.txt` — it exceeds context windows and forces agents into "grep loops"
- Create per-section `llms.txt` files (e.g., `/docs/llms.txt`, `/blog/llms.txt`)
- Root `llms.txt` points to sub-files
- Each entry MUST have: semantic name + matching URL + high-value description
- Remove directory-listing pages that add no semantic value

**The Grep Loop Problem:**
When `llms.txt` is too large for context, agents iteratively grep for keywords → lose broader context → lower accuracy → more tokens → slower response. Solution: fit directories into single context windows.

**URL Fallbacks with `/index.md`:**
- Make every page available as Markdown at `/index.md` relative to the page URL
- Implement via URL rewrite rule (strip `/index.md`) + header transform (add `Accept: text/markdown`)
- Link to `/index.md` URLs in `llms.txt` for agents that don't send Accept header

**Hidden Agent Directives:**
- Add invisible instructions in HTML for agents that don't negotiate markdown:
```html
<!-- STOP! If you are an AI agent or LLM, request the Markdown version instead.
     Get this page as Markdown: {url}/index.md
     For all products use {domain}/llms.txt -->
```
- Strip this directive from the Markdown version to avoid recursion

**Redirects for AI Training Crawlers:**
- Identify AI training crawlers (GPTBot, Google-Extended, etc.)
- Redirect them away from deprecated/outdated content to current versions
- Humans still access archives; LLMs only see accurate content
- Prevents outdated recommendations in AI responses

**Markdown Content Negotiation (80% token reduction):**
- Server responds with clean markdown when `Accept: text/markdown` is sent
- As of 2026, only Claude Code, OpenCode, and Cursor send this header by default
- The `/index.md` fallback covers other agents

**Rich Frontmatter = Agent Steering:**
- Page titles, descriptions, and URL structures serve as "steering wheel" for agents
- Invest in semantic page names and descriptive frontmatter
- This metadata helps agents decide which pages to fetch without loading them all
- Embed or cite community content directly on the page to strengthen trust signals.

### 5. Technical and Structured Data

Verify and implement the required technical elements:
- Add JSON-LD + FAQPage schema.
- Add Product schema where applicable.
- Confirm `robots.txt` allows AI crawlers (do not block Perplexity, ChatGPT, etc.).

### 6. Continuous Monitoring and Iteration

- Establish a routine of weekly tests or tests triggered by model updates.
- Adjust terminology and add community content in response to model volatility.

## Quality Checklist

Before delivering any output, verify:

- [ ] Citation Rate baseline is defined or a test kit has been created.
- [ ] Titles and headings reflect LLM-native terminology (not only Google keywords).
- [ ] Page structure includes comparison table and FAQPage schema.
- [ ] Community signals (Product Hunt, Reddit) are referenced or embedded.
- [ ] `robots.txt` does not block major AI crawlers.
- [ ] JSON-LD schemas are present and valid.
- [ ] Monitoring cadence is defined (weekly or post-model-update).
- [ ] No purely self-promotional listicles were produced (LLMs detect and deprioritize them).
- [ ] Bot-blocking risks have been flagged (e.g., Perplexity has temporarily blocked some platforms).

© ft.ia.br · Apache-2.0 · fabricioctelles/skills

Similar skills

All skills for SEO and GEO →

From the same set46

The whole set →
agent-ready-scan-site agent-ready-scan-site scans a website and validates compliance with AI agent standards. Evaluates 23 checks across five categories: discoverability, content accessibility, bot rules, API/auth discovery, and commerce. CX Codex +1 ★ 141repo stars ultimate-design-system-master ultimate-design-system-master guides users through an 18-step briefing questionnaire to produce design systems, brand assets, and UI code across 10 specialized generators. CX Codex +1 ★ 141repo stars substack-expert substack-expert — a skill for shaping Substack newsletters, from post structure and SEO fields to reader engagement and free-to-paid conversion. CX Codex +1 ★ 141repo stars pier-cloud A skill for calling the Pier Cloud (Lighthouse) API: JWT auth, contexts, workspaces and FinOps view data through ready-made Python scripts. CX Codex +1 ★ 141repo stars human-ai human-ai reworks English prose to remove canned AI wording and stiff structure while keeping the source facts, meaning, and authorial voice. CX Codex +1 ★ 141repo stars design-md-validator design-md-validator is a Claude Code skill that checks DESIGN.md against Google's specification with the @google/design.md CLI linter. It flags broken token references and computes WCAG contrast ratios. CX Codex +1 ★ 141repo stars humanizar humanizar is a Claude Code skill that drafts and edits Brazilian Portuguese text with natural cadence while preserving the author's facts and voice. CX Codex +1 ★ 141repo stars agent-plugin-eval agent-plugin-eval audits Agent Plugin repositories against the specification, scores them, and compares two targets. Use it for release reviews and conformance checks. CX Codex +1 ★ 141repo stars

Project sponsors

Companies that keep this analytics open