How to write AI-citable claims: evidence patterns that get cited

TL;DR

Write each claim as if a model will paste it verbatim. That means: lead the section with a one-sentence direct answer, follow it with a numbered or named fact tied to a primary source, and only then add narrative depth. Use the Answer-Evidence-Depth (AED) pattern at every H2; spell out entities and dates; link evidence to authoritative sources, not your own marketing pages. Brands that ship this pattern systematically see meaningful citation lift in ChatGPT, Perplexity, and Google AI Overviews within a quarter.

Why claim-level writing matters for AEO

Answer engines do not cite pages; they cite passages. The retriever scores chunks of ~150-500 tokens for relevance; the generator picks the cleanest chunk that addresses the user query and inserts a citation alongside the paraphrased claim. Anything that obscures the claim — buried answers, vague subjects, missing numbers, or unsourced opinions — lowers the chance that chunk wins the citation slot.

This is why "clear, simple, definition-style content" gets cited more than higher-ranking but fluffier pages, as practitioners report on r/AI_Agents (Reddit, 2026). It also explains why the same content distributed in different formats produces different citation rates by platform: ChatGPT skews toward Wikipedia-style authoritative summaries, Perplexity toward community and review content, and Claude toward technically precise sources (Discovered Labs, 2025).

What makes a claim citable

A citable claim has four properties:

1. Standalone. A reader (or a model) can quote it without surrounding context and have it still mean the same thing.
2. Attributable. The subject is a named entity, not a pronoun or a vague "we".
3. Verifiable. It contains at least one specific element — a number, a date, a named source, a defined term.
4. Linked. It is anchored to evidence: an inline citation, a hyperlink to a primary source, or a referenced internal document.

If a claim fails any of these, rewrite it. Failures are correlated: an unattributable claim is usually unverifiable too.

The Answer-Evidence-Depth pattern

Every H2 (and most H3s) should follow the AED pattern:

• Answer (first 30-60 words). A direct, complete response to the implied question of the heading. If a reader stops after this sentence, they have what they came for.
• Evidence (next 100-200 words). One or two sourced facts that prove the answer. Numbers, dates, names, links.
• Depth (remainder). Caveats, examples, edge cases, related concepts, opinions. This is where you build semantic density without diluting the citable lead.

Advocated as the Answer-Evidence-Depth (AED) template by ZipTie and others (ZipTie, 2026), the pattern fits how reranker-driven retrieval scores chunks: leading sentences are weighted higher, and chunks that contain both the answer and the evidence inside one window are preferred over chunks that scatter them.

Before / after example

Before (low citation-readiness):

A lot of teams wonder how often they should refresh their content for AI search. The answer depends on a lot of things, but generally you should think about doing it more often than you used to.

After (high citation-readiness):

Refresh evergreen AI-search content every 90 days and time-sensitive content every 30 days. AI rerankers promote pages with last_reviewed_at dates within the last quarter; SE Ranking's 2026 study of 25,000 ChatGPT citations found cited pages were 2.3× more likely to have been updated within the last 90 days than uncited peers.

The second version is one sentence longer but contains a discrete answer ("every 90 days / every 30 days"), a specific entity ("SE Ranking's 2026 study"), and a verifiable claim ("2.3× more likely").

Eight evidence patterns AI engines reward

These are the patterns that consistently appear in cited passages across ChatGPT, Perplexity, Google AI Overviews, and Claude:

1. Number + source

{Specific number} of {entity} {verb} {object} according to {source, year}.

Example: "87% of ChatGPT responses include at least one citation according to Averi's 2026 dataset."

2. Direct definition

{Term} is {short noun-phrase definition}. It {distinguishing property}.

Example: "Citation rate is the share of tracked AI answers that include a clickable link to your domain. It differs from mention rate, which counts your brand name with or without a link."

3. Comparative claim

Unlike {alternative}, {entity} {verb} {distinguishing behavior}.

Example: "Unlike traditional SEO, AEO rewards passages that include a self-contained answer in the first sentence under each heading."

4. Step claim

To {goal}, {imperative verb} {object} in {ordered steps}.

Example: "To audit AI Overviews visibility, capture screenshots of 50 priority queries weekly, log citations and mentions per query, and compare share-of-voice month over month."

5. Named-source quote

“{Direct quote}” — {named person, role, organization, year}.

Example: "‘Indexing still comes first. If search engines can't find your content, AI tools won't either,’ Semrush noted in a February 2026 industry post."

6. If-then rule

If {condition}, then {outcome / recommendation}.

Example: "If your page lacks an FAQ section that answers questions in 40-60 words, AI engines are more likely to cite a competitor's FAQ answer instead."

7. Contrast pair

{Misconception} is wrong; {accurate statement} — {evidence}.

Example: "FAQ schema alone does not guarantee citations; AI engines cite the answer text, and the schema only helps them parse it. Google explicitly limits FAQ rich results to authoritative sites in its 2023 update."

8. Dated benchmark

As of {month, year}, {entity} {metric} reached {value}.

Example: "As of April 2026, ChatGPT serves over 200 million weekly active users, per OpenAI's public statements."

Treat these as templates, not formulas. Mix them across a section so the writing reads naturally to humans.

Sentence-level rules

• Lead with the subject. "Citation rate measures…" not "What is measured by citation rate is…".
• Resolve every pronoun. Replace "it", "they", and "this" with the noun if a model could lose context in a 200-token window.
• Define every acronym on first use. Spell out "Answer Engine Optimization (AEO)" the first time, then use AEO. Animalz recommends a mini-glossary for jargon-heavy pages (Animalz, 2025).
• Prefer concrete nouns to abstract ones. "Schema.org's FAQPage type" is more citable than "FAQ markup".
• Date the data. "…as of Q1 2026" beats an undated number, because models down-weight stale facts.
• Avoid hedging stacks. "It might be…" or "some experts argue…" reduces citation-readiness even if technically accurate. State the claim, then add the caveat as a separate sentence.

Sourcing tactics

• Cite primary sources whenever possible. Official docs (OpenAI, Anthropic, Google), peer-reviewed papers, government data, named industry studies.
• Use inline links, not footnotes only. Inline links live inside the chunk and travel with the citable claim.
• Add the publication date in the source mention. "…per Google's March 2026 Search Central post." gives the AI a freshness signal.
• Link to the deepest relevant URL. Not the homepage; the section, the heading anchor, the specific dataset row.
• Diversify across platforms. ChatGPT favors authoritative editorial domains, Perplexity favors community sources (Reddit alone accounted for ~24% of Perplexity citations in January 2026 per Tinuiti via almcorp), Claude favors technical and academic sources. Build distribution beyond your blog.

Page-level support for citable claims

Claim writing only works inside a page that AI engines can extract from cleanly:

• Each H2 frames an extractable question.
• The first sentence under each H2 contains the AED Answer.
• Schema.org Article, FAQPage, and HowTo markup mirrors what the body says.
• Author bio, publication date, and last_reviewed_at are visible to crawlers.
• Internal links connect to the topic hub and to evidence pages, supporting the entity coverage map.

For more on the surrounding structure, see our companion guide on citation-ready page anatomy.

Common mistakes

• Burying the answer. A two-paragraph windup before the actual claim costs you the citation.
• Vague subjects. "Many companies" or "a lot of teams" cannot be attributed.
• Round numbers without sources. "Around 80% of…" with no citation reads as opinion.
• Self-citing only. AI engines weight third-party citations more heavily than self-references.
• Marketing language inside claims. "Best-in-class" or "industry-leading" rarely gets cited; specific differentiators do.
• Missing dates. Undated claims get downranked as the model assumes they may be stale.
• Long, multi-clause sentences. Models prefer short claims they can quote without trimming.

How to apply this guide

1. Audit your top 20 pages: count how many H2 sections lead with a one-sentence answer, and how many of those answers contain a sourced number or named entity.
2. Pick 5 sections that get the most AI-engine traffic (per GA4 source/medium) and rewrite them using the AED pattern and at least two evidence patterns from the list above.
3. Replace marketing adjectives with concrete differentiators; date every statistic.
4. Track citation rate per page weekly using your AI visibility tool (compare options here).
5. Re-baseline after 30 days; expand the rewrite to the next 20 pages.

FAQ

Q: How long should an AI-citable claim be?

The answer sentence should be 15-40 words. Long enough to convey the full claim with subject, verb, object, and qualifier; short enough to fit cleanly into an AI-generated answer without trimming.

Q: Do I need citations on every claim?

No. Cite specific facts (numbers, dates, third-party studies, regulatory statements). Definitions, opinions you own, and procedural steps usually do not need citations — but they should still be attributable to your byline and published with a clear date.

Q: Which is better: a screenshot or a quoted statistic?

Both, when possible. AI engines cite the text, so the quoted statistic with its source link is what wins the citation slot. The screenshot helps human readers verify; add descriptive alt text so crawlers can index it.

Q: How do I write citable claims about my own product without sounding promotional?

Replace adjectives with measurable differentiators. "Our search returns results in 80 ms p95" is citable; "our search is blazing fast" is not. Pair the measurable claim with a verifiable artifact (a status page, a benchmark report, a customer case study with named numbers).

Q: Do AI engines penalize content that links out to competitors?

Generally no — outbound links to authoritative sources improve citation-readiness. AI engines treat your willingness to cite primary sources as a trust signal. Selective competitor mentions in comparison contexts can also be cited if you frame them with sourced facts rather than disparagement.

Q: How quickly can I expect to see citation lift after rewriting?

AI engines re-index on rolling cycles (days to weeks for major surfaces). Most teams see measurable lift in citation rate within 30-60 days of systematic rewrites, with the largest gains on pages that previously had high SEO ranking but low citation rate — those pages are already discoverable; they just needed claim-level cleanup.