Geo Optimization

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