Aeo Geo Writing

AEO/GEO Writing — Structuring Content for AI Citation

[!NOTE] Core Philosophy (Mantra): Do not write generalities; write checkable facts. Write content to be the single context-dense sentence that survives RAG retrieval and gets cited by name.

Traditional SEO writes to rank a link. AEO/GEO (Answer/Generative Engine Optimization) writes to be the sentence an AI model extracts, repeats, and attributes to your brand.

AI retrieval systems (RAG) do not read your page top-to-bottom to form an impression. They segment your page into isolated text chunks, evaluate each chunk's relevance and authority in isolation, and either cite it or discard it. This skill enforces rules to ensure your claims survive this extraction process.

Cross-Reference: Always pair this skill with web-ai-slop. AEO copy ensures AI engines find and cite your content, while web-ai-slop guarantees the copy remains engaging, fresh, and free from robotic tropes for human readers.

Rule of application: Apply this skill whenever drafting, editing, or auditing web content, documentation, blog posts, or marketing copy. If the text matches 2 or more patterns in Section 2 (Vagueness) or fails Section 1 (Structure), discard the draft and rewrite.

Apply this silently. Do not narrate "I am optimizing this for generative engine visibility" to the user.

Section 1 — Structural Architecture (AI Crawler Friendly)

AI crawlers and extraction tools require specific layouts to parse and attribute content correctly.

1a. The "Answer Capsule" Pattern

• Direct Answer Placement: Directly under every H2 or H3 heading, place a 40–60 word capsule that answers the heading's question directly.
• No Preamble: Do not begin with "In this section we will discuss..." or "That is a great question...". Start with the answer.
• Isolation Test: If an AI model extracted only this capsule and discarded the rest of the page, would it still represent a complete, correct, and attributable claim? If not, rewrite.

1b. Schema and Semantics

• FAQPage Schema: Always bundle FAQ blocks with structured JSON-LD FAQPage schema. This is the single highest-leverage technical element for Google AI Overviews.
• Data Tables Over Prose: When comparing statistics, specifications, or pricing, use semantic HTML <table> elements instead of narrative text. Retrieval models extract tabular data with significantly higher confidence.
• The Summary Hook: On long-form pages, write a concise 100–150 word summary paragraph before the very first H2. Search engines weight the beginning of documents heavily during retrieval.
• Credibility Signals: Ensure a visible, named author with a real bio and a visible "Last updated on [Date]" metadata field is present. Models use freshness and authorship as ranking weights.

1c. Dynamic FAQ & Question Logic

Different models favor different formats. Provide a variety of structures to cover multiple engine biases:

• FAQ Lists: Bulleted question-and-answer accordions with FAQPage schema (favored by ChatGPT and Google AI Overviews).
• How-To Listicles: Ordered steps (<ol> or H3s with step numbers) containing specific actions (favored by task-oriented assistants).
• Definition Summaries: H3 + short definition under 30 words for direct snippet panels.

1d. Multimodal Integration (Visual RAG)

AI engines don't just index text; they match queries to images based on contextual intent.

• Intent-Based Descriptive Alt-Text: Alt-text must describe the functional purpose and conclusions of the visual, not just its objects.
  • Bad: alt="A graph showing sales"
  • Good: alt="Line chart showing a 42% decrease in checkout page abandonment rates after integrating single-click checkout"
• Surrounding Text Context: Keep core metrics described in the adjacent paragraph. Retrieval bots evaluate text blocks surrounding the image tags.

Section 2 — Copywriting & Tone (Credibility Signals)

AI models are risk-averse; they prefer to skip exciting claims they cannot verify in favor of boring, checkable facts.

2a. E-E-A-T & Credibility Expansion

Experience, Expertise, Authoritativeness, and Trustworthiness are heavily weighted signals:

• First-Person Experience Verbs: Use active verbs showing physical interaction ("We audited 140 codebases...", "I tested the API performance...", "We measured the transition delay..."). Bots filter for primary sources over secondary synthesis.
• Expert Verification labels: Include clear "Expert-Verified by [Name]" badges linking to authoritative author profiles or schema credentials.
• Eliminating Hedging: Phrases like "we believe," "in our opinion," "we think," or "potentially" lower a model's confidence score. State claims declaratively.
• Attributable Sourcing: Avoid vague authority. "Many developers agree that..." is uncitable. "According to Stack Overflow's 2025 Developer Survey, 76% of developers..." is highly citable.
• Concrete Metrics: Replace adjectives with numbers. Do not write "a significant performance increase." Write "a 42% decrease in page load times."
• One Claim per Sentence: Split compound sentences. If a model extracts only half of a compound sentence, the context is lost and the citation fails.

2b. AEO Copywriting Examples

Section 3 — Technical & Off-Page Prerequisites

Perfect prose is useless if crawlers cannot access it or if search indexes do not list it.

3a. Indexing and Crawling

• Server-Side Render (SSR) Critical Copy: Crawlers prioritize speed and often skip executing JavaScript. If your core claims are injected client-side (SPA), they are invisible to AI models.
• Allow bots in robots.txt: Do not block GPTBot, ClaudeBot, Google-Extended, or Bingbot unless explicitly directed.
• Deploy llms.txt: Place an llms.txt file at the root of your domain. This serves as a plain-markdown dictionary of your site's structure and purpose for models.
• Bing Index Priority: ChatGPT's web search relies on the Bing index. Ensure your site is fully indexed in Bing Webmaster Tools; Google indexation alone is insufficient.

3b. Off-Page Credibility

• Community Footprint: Models rely heavily on community platforms (e.g., Reddit, Stack Overflow, GitHub) for sentiment and real-world recommendations. A presence in discussions is as important as on-page content.
• Proprietary Data Moats: Publish original, first-party data audits, benchmark results, or survey findings with methodology and dates. Original numbers are highly cited.

Section 4 — Platform Targeting Matrix

Customize the structure of the content based on which engine you want to prioritize.

Section 5 — The AEO/GEO Self-Check

Before submitting copy, verify against this checklist:

1. Answer Capsule Check: Can the lead sentence of each H2 section be read completely alone and still make sense?
2. Attribution Check: Is there a checkable source, number, or name for every claim of fact?
3. No Hedging Check: Have words like "believe", "opinion", "think", "probably" been removed?
4. Formatting Check: Are comparisons formatted as semantic <table> elements and list questions as FAQPage schema?
5. Technical Check: Is the copy server-rendered, and is the Bing index verified?
6. EEAT & Visual Check: Are alt-texts intent-based, and are first-person experience verbs used where appropriate?

Section 6 — Case Studies: AEO/GEO Failure vs. Success

Failure Case 1: Hedged & Fluffy Copy (AI-Default Slop)

"We believe that improving databases is vital. Our team feels that custom indexing could potentially speed up query resolution. Many users have reported a seamless performance shift after optimization."

Why it fails: "We believe", "feels", "potentially" trigger high uncertainty scores. "Many users" is uncitable. There are no metrics.

Success Case 1: Declarative & Sourced (AEO-Optimized)

"Custom indexing optimizes SQL queries. We audited 140 database instances and recorded a 64% reduction in query latencies after implementing partial indexes. A 2026 PostgreSQL benchmark study confirms that partial indexing cuts disk write overhead by 30%."

Why it works: Declarative statement leads. Uses first-person experienced verbs ("We audited", "recorded"). Names checkable study/benchmark and reports exact metrics (64%, 30%).