---
title: "Content that gets cited (GEO writing patterns) (seo)"
description: "These are writing and layout patterns for pages that AI engines (Google AI Overviews/AI Mode, ChatGPT search, Perplexity, Copilot, Claude) quote and link to."
canonical: https://void-design.vercel.app/docs/seo/content-for-citation
lastModified: 2026-09-16
---
# Content that gets cited (GEO writing patterns)
These are writing and layout patterns for pages that AI engines (Google AI Overviews/AI Mode, ChatGPT search, Perplexity, Copilot, Claude) quote and link to. Every pattern also helps human readers, and none replaces indexability (see the `seo` SKILL).
## 1. What the evidence supports
| Source | Finding | Implication |
|---|---|---|
| Aggarwal et al., *GEO*, KDD 2024 (10K queries; also tested on Perplexity) | **Cite sources, add quotations, add statistics** raised visibility 30–40%. At rank 5: citations +115%, quotations +100%, statistics +98%. At rank 1 the same edits *lost* 20–30%. Keyword stuffing and "authoritative" tone: no gain | Add evidence, especially on pages that aren't already #1 |
| Puerto et al., *C-SEO Bench*, NeurIPS 2025 | Most content-rewriting tricks are ineffective or harmful, and gains shrink as competitors adopt them. **Traditional SEO is significantly more effective** | Don't "rewrite for AI". Rank first |
| Chen et al., 2025 (arXiv 2509.08919) | AI search strongly favors **earned media** (third-party, authoritative) over brand-owned pages. Big-brand bias | Get covered, reviewed and cited elsewhere (off-site) |
| *Citation Selection to Citation Absorption*, 2026 (21K citations) | High-influence cited pages are **longer, more structured, and rich in definitions, numerical facts, comparisons and procedural steps** | Structure plus facts |
| Microsoft Ads, "Optimizing content for AI search answers" (2025-10) | Title/description/H1 alignment; descriptive H2/H3; Q&A pairs ("lifted word for word"); lists and tables; self-contained 1–2 sentence answers. Avoid walls of text, answers hidden in tabs, facts only in images or PDFs, decorative symbols | Snippable sections |
| Bing Webmaster (2025-12, 2026-02) | Near-duplicate URLs get clustered and one is chosen. Freshness via IndexNow. Evidence, examples and cited sources | Consolidate, stay fresh |
| Google, "Optimizing for generative AI features" (2026-05) | No special requirements. **Non-commodity content** and a unique point of view win. llms.txt, chunking, "AI rewriting" and special schema are unnecessary | Be genuinely useful and original |
## 2. Patterns
### 2.1 Answer first (every page and every question-style section)
The first paragraph after the h1 (and after each h2 phrased as a question) answers in **1–2 self-contained sentences, ≤ 320 characters**, naming the entity instead of using a pronoun.
```html
Welcome to the future of builds
We're passionate about helping teams move faster. It's built for you.
Acme: incremental TypeScript builds for monorepos
Acme is an open-source build tool that caches TypeScript compilation per package, cutting CI builds in a
200-package monorepo from 14 minutes to 90 seconds. It is MIT licensed and runs on Node 22+ and Bun.
```
### 2.2 Numbers with units, dates and sources
```html
Median mobile JavaScript is 646 KB per page
(HTTP Archive Web Almanac, 2025).
Acme's landing page ships 142 KB, measured on 2026-09-10 with Lighthouse 13.
```
- Every claim that could be doubted gets a number, a unit, a date or a link to a primary source (docs, papers, standards, official statistics). No links to aggregator blogs.
- Roughly **1 outbound primary-source link per ~300 words** of factual prose.
- Own benchmarks: state the method (hardware, versions, runs) next to the number.
### 2.3 Quotations from named people
```html
"We replaced three CI jobs with one Acme cache and cut our monthly runner bill by 38%."
```
Real, attributable and permissioned. No invented testimonials.
### 2.4 Question headings + Q&A blocks (plain HTML, no FAQPage schema)
```html
How much does Acme cost?
Acme is free for open-source projects. The Team plan costs $12 per seat per month billed annually, and includes remote caching.
```
Use the questions real users ask (support tickets, sales calls, search console queries). Keep the answers **visible**, not collapsed. If you use ``, set `open` for the key facts.
### 2.5 Comparison and spec tables
```html
Acme vs. tsc --build (200-package monorepo, cold CI, 2026-09)
Metric
Acme 3.2
tsc 5.9
Cold build
6 min 10 s
14 min 2 s
Warm build (1 file changed)
1.5 s
38 s
License
MIT
Apache-2.0
```
Real `
` with `
`, never a grid of divs. Compare fairly and name what the competitor does better.
### 2.6 Definitions and steps
- "X is a Y that Z." definitions near the top of concept pages.
- Procedures as `` with one action per step and the expected result.
### 2.7 Entity clarity
The exact same name everywhere: ``, h1, `og:site_name`, JSON-LD `Organization.name` and `WebSite.name`, the llms.txt H1, footer. Keep a "What it is / Who it's for / Pricing / License / Status" fact block on the home or about page. Link official profiles through `sameAs`.
### 2.8 Freshness
- A visible `<time dateTime="2026-09-01T09:00:00Z">Updated 1 Sep 2026</time>` that matches JSON-LD `dateModified` and sitemap `lastmod`.
- Change the date only when the facts change (a copyright-year bump doesn't count).
- Ping IndexNow on publish (see `next-metadata.md` §9).
### 2.9 Visible text, not pictures of text
- Key facts must not live only in images, canvas, video, carousels, PDFs, or tabs closed on load.
- Hero sections have ≥ 20 words of real text.
- Charts: a caption or table with the numbers next to the image. Videos: a transcript or summary.
### 2.10 Readable chunks
- Paragraphs ≤ ~150 words. Descriptive headings every 200–400 words.
- No decorative symbols as meaning (→ ★ !!!). No emoji bullets.
- Content pages ≥ ~150 words of main content (tools and app pages are exempt).
## 3. Page templates
**Product home:** h1 (what + for whom) → answer paragraph → primary CTA → 3–5 benefit sections, each an h2 claim + a measured proof → comparison table → pricing summary in text → named customer quotes → FAQ-style h2 questions → footer fact block.
**Docs page:** h1 = task or concept → one-sentence definition or outcome → prerequisites list → numbered steps with code → expected output → troubleshooting h2 questions → "Updated" date → `.md` mirror.
**Article:** h1 → byline + updated date → TL;DR answer (2–3 sentences) → sections with question or claim headings → data with sources → quotes → conclusion restating the answer → author bio linked to a ProfilePage.
## 4. Don't
- Generate keyword-variant or city-variant pages for query fan-out. Google treats this as scaled content abuse, and Bing clusters them.
- Rewrite in a "persuasive" or "authoritative" tone, or stuff keywords. It had no effect in controlled tests.
- Chunk content into many thin micro-pages "for LLMs".
- Add FAQPage/HowTo schema for rich results, or `speakable` spam.
- Fake mentions, reviews or ratings.
- Hide answers in accordions, or serve different content to bots.
## 5. Off-site (outside the codebase, tell the owner)
AI engines lean on third-party sources. Maintain accurate profiles (GitHub, LinkedIn, Crunchbase, Wikipedia where notable), get listed in credible comparisons and directories, publish benchmarks others can cite, and answer in communities.
## 6. Measure
- Google Search Console → "Generative AI performance" report.
- Bing Webmaster Tools → "AI Performance" (citations, cited pages, grounding queries).
- Analytics: referrals with `utm_source=chatgpt.com`, and from perplexity.ai, copilot.microsoft.com, claude.ai.
- `void geo <url>` reports these heuristics as `info` findings (answer-first, citation density, question headings, tables, entity consistency). They are review prompts, never CI failures.
## Sources
- https://arxiv.org/abs/2311.09735 (GEO, KDD 2024)
- https://arxiv.org/abs/2506.11097 (C-SEO Bench)
- https://arxiv.org/abs/2509.08919 (earned media bias)
- https://arxiv.org/abs/2604.25707 (citation absorption)
- https://about.ads.microsoft.com/en/blog/post/october-2025/optimizing-your-content-for-inclusion-in-ai-search-answers
- https://blogs.bing.com/webmaster/December-2025/Does-Duplicate-Content-Hurt-SEO-and-AI-Search-Visibility
- https://blogs.bing.com/webmaster/February-2026/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview
- https://developers.google.com/search/docs/fundamentals/ai-optimization-guide
- https://developers.google.com/search/docs/appearance/ai-features