← blog / SEO & GEO

How to Get Cited by ChatGPT and AI Overviews

·updated ·19 min readgeoai-searchseocontent-strategyai-overviews
How to Get Cited by ChatGPT and AI Overviews

Getting cited by ChatGPT and AI Overviews is decided at the paragraph level, not the domain level. A study of 1,000 AI Overviews collected in April 2026 found that the top 1% of domains capture 47% of all citations, while the remaining 90% of domains share 22%. The same study found that pages citing at least one named source inline in the body were cited 2.1× more often than pages that didn't. That second number is the one a 20-post niche blog can actually move. You will not out-cite Wikipedia, but the half of the citation market that isn't already spoken for is won by pages that are easy to lift a self-contained, evidence-dense passage out of. That is a writing decision, and it costs nothing.

TL;DR

  • Fix the technical floor first: server-rendered HTML, stable URLs, OAI-SearchBot allowed, no stray nosnippet, and a look at your Cloudflare bot rules.
  • Write one committed sentence per section (a definition, number, comparison or step), attach a named source and verify the link, and put it under an H2 that matches the question.
  • Keep a visible, honest last-updated date, measure in quarters using server logs and Search Console impressions, and hold the cadence.

Below is what actually holds up: the one controlled experiment, the crawler logs, the citation datasets that disagree with each other, and the technical floor that quietly disqualifies small sites before any writing advice matters.

The door is only half shut

Start with the ceiling, because pretending it isn't there makes everything after it less credible.

DigitalApplied analysed 1,000 AI Overviews (100 queries across 10 intent classes, roughly 30 verticals, US-English desktop, collected 8–22 April 2026), crawling 4,243 unique cited URLs against about 50,000 non-cited controls. The distribution is brutally top-heavy: the top 1% of domains capture 47% of citations, the next 9% capture 31%, and the long-tail 90% split the remaining 22%. Their own summary is the sentence worth pinning above your desk: "Twelve domains capture half of all AIO citations. The other half is the only addressable market for everyone else — and it is decided by page-level signals, not domain age."

Now the flip side, from the only controlled experiment anyone has run on this.

The GEO paper led by Princeton researchers (KDD 2024) built GEO-bench, a benchmark of 10,000 queries run through a two-stage generative engine: retrieve the top five sources, then synthesise a cited answer. The researchers tested nine content modifications. The headline result is well-travelled: the paper reports visibility gains "up to 40%". But the more interesting number is buried in the rank breakdown.

Applying the "Cite Sources" method (adding relevant citations to claims in the text) to the source ranked 5th in the retrieved set lifted its visibility by +115.1%. Applying the exact same method to the top-ranked source lowered its visibility by 30.3%. The paper frames this explicitly as GEO's democratising potential for smaller creators competing against established domains.

Carry two caveats: GEO-bench ran on GPT-3.5-turbo-era engines and nobody has publicly re-run it on 2026 frontier models, and "up to 40%" is a maximum on one metric, not an average. Keyword stuffing was among the worst-performing methods tested. Treat it as directional: attribution-dense prose helps most when you are not already the top result, which describes every small blog.

What actually changed: you are competing for a passage, not a page

The mechanism is not a secret. Google described it in its own words when it shipped AI Mode: "Under the hood, AI Mode uses our query fan-out technique, breaking down your question into subtopics and issuing a multitude of queries simultaneously on your behalf."

That single sentence rearranges the job. Your page is not being ranked against competitors for a keyword. It is being retrieved as one of several candidates for a sub-question you probably never targeted, then read for a passage that answers that sub-question cleanly.

An April 2026 measurement study (arXiv 2604.25707), covering 602 controlled prompts and 21,143 search-layer citations across ChatGPT, Google AI Overview/Gemini and Perplexity, separates citation selection from citation absorption: whether your page appears in the source list, versus whether your text actually shapes the answer's wording, reasoning and facts. Different games. Pages with high absorption shared three traits: extended length and structural organisation, strong semantic alignment with query intent, and rich extractable evidence, which the paper names as "definitions, numerical facts, comparisons, and procedural steps."

The engines also differ: Perplexity and Google reference more sources overall, while ChatGPT cites fewer with substantially higher influence per fetched page. If ChatGPT is your target, being one of the few sources selected matters more than being one of many.

The ranking connection is loosening too, though the data needs care. Ahrefs' July 2025 study of 1.9 million citations across 1 million AI Overviews found 76.10% of cited pages ranked in the top 10, and 14.40% ranked below position 100, with no visibility on the SERP (the ordinary search results page) at all. Their March 2026 re-run across 863,000 keywords and 4 million AI Overview URLs put the top-10 share at just 38%, with 31.2% from positions 11–100 and 31.0% from beyond position 100. Ahrefs attributes part of the shift to improved parsing, so the two studies are not directly comparable, but even the conservative reading says many citations come from pages that would never win the blue link. BrightEdge, measuring across nine industries over 16 months, found only 16.7% of AI Overview citations come from top-10 results and called positions 21–100 "the sweet spot."

Ahrefs' Si Quan Ong put the honest version best: "It's true that if you rank #1 in the SERPs, you're more likely to be cited in an AI Overview than if you were ranked lower. But that chance is a coin flip at best."

The four things AI answers reach for

The absorption study's list (definitions, numerical facts, comparisons, procedural steps) is the most useful finding in this space, because all four are paragraph-shaped. You don't need a domain, a budget or a decade. You need to put one of those four things in a chunk of text that survives being torn out of the page.

GEO-bench's primary metric is Position-Adjusted Word Count: how much of the generated answer a source contributes, weighted by where in the answer it appears. Cross-reference the absorption list with GEO-bench's per-method results on that metric and the four best-performing methods were:

Method Lift on Position-Adjusted Word Count Lift on Subjective Impression
Quotation Addition +41% +28%
Statistics Addition +31% +23%
Fluency Optimization +28% +13%
Cite Sources +27.5% +14%

Lifts derived from Table 1 absolute scores (baseline 19.3 on both metrics).

Three of those four are forms of attribution, which lines up with DigitalApplied's correlational finding that pages citing a named source inline were cited 2.1× more often. Two methods, same direction.

What that looks like in an actual paragraph

Here is the shape, using an illustrative rewrite rather than a real page.

Before:

There's been a lot of discussion lately about whether domain authority still matters for AI search. Many experts believe it's becoming less important, though opinions vary. We'll explore what this means for smaller publishers below.

That paragraph is unliftable. It contains no definition, no number, no named source, and no claim. Pulled out of the page it says nothing.

After:

Domain authority barely predicts AI citation. Surfer analysed roughly 20,000 prompts and about 5 million unique citation source URLs across Google AI Mode, AI Overviews, OpenAI and Perplexity, and found rank-order (Spearman) correlations of −0.065 for PageRank and −0.053 for Domain Score against AI Overview citation frequency — what they described as "close enough to zero to be noise." The relationship held near zero even after removing the top 5% of domains.

Same length. The second version has a committed claim in the first sentence, a named source, a sample size, two numbers with their metric named, and a direct quote. Torn out of the page, it still works. That is the entire test.

The pattern, minus the fake numbers

The dominant vendor prescription for this is the "answer capsule": a 40–60 word self-contained answer placed directly under an H2, structured as direct answer → qualifier → scope or exception, in plain paragraph prose, third person, with no hyperlinks inside the capsule itself. The named failure modes are preamble openers, link-laden capsules, hedging language, callout formatting, and capsules containing no numbers.

The pattern matches what the absorption study measured independently. One integrity note: the statistics that page and its peers attach to the pattern (things like "72.4% of cited pages use answer capsules") chain-cite other GEO vendor blogs rather than any traceable dataset. Use the pattern. Don't repeat the numbers.

One case study is worth reading for shape rather than proof: Growtika's, describing a bootstrapped client against well-funded competitors. The on-page work was unglamorous: 40–50 word answer blocks structured as direct answer → supporting details → differentiator, data tables with specific pricing and features, and comparison pages with exact numbers. The reported outcome was 172 citations across ChatGPT and Claude, third behind only Wikipedia and arXiv. The number to internalise is the timeline: zero citations for two months, first long-tail citations at months 3–4, consistent cross-platform citations at months 9–10. It's an agency's own unaudited case study, but the year-long arc matches everything else here.

Cite correctly, or don't cite

If the highest-leverage thing you can do to a paragraph is attach a named source to a number, the quality of that attribution becomes load-bearing. A dead or invented link is worse than no link — it costs a reader's trust the first time they click, and it's the most common failure mode of AI-drafted content.

That's the part of the workflow Magic Share's link verification and fact-checking is built around: the agent checks each claim against its cited source before handing over the draft, and a verification report ships attached so review takes a coffee rather than an afternoon. "Add more attributed statistics" is only good advice if the attributions hold.

Authority matters less than you'd think — and mentions matter more

This section comes with a warning label, because the two best datasets flatly disagree.

Surfer's study (roughly 20,000 prompts and about 5 million unique citation source URLs across AI Mode, AI Overviews, OpenAI and Perplexity, over roughly three months) found authority metrics correlate negatively but negligibly with citation frequency: AI Overviews at −0.065 (PageRank) and −0.053 (Domain Score) on full-dataset Spearman (a rank correlation: does higher authority go with higher citation frequency?). Strip out the top 5% of domains and everything collapses to within ±0.05 of zero. DigitalApplied, on its much smaller 4,243-URL sample, found the opposite: a +0.61 Pearson correlation (a straight-line fit on the raw values) between citation rate and its proxy for domain authority (DA, a third-party estimate of a site's link strength, not a Google metric).

Neither is peer-reviewed. Surfer's dataset is roughly a thousand times larger; DigitalApplied is more transparent about its controls. The honest synthesis is not "authority doesn't matter" — it is that authority is not the gate in AI citation that it is in classical rankings, and it explains far less of the variance than practitioners assume.

Ahrefs' 75,000-brand study from May 2025 splits the difference. Running Spearman correlations against AI Overview brand visibility, it ranked branded web mentions highest at 0.664, branded anchors at 0.527, branded search volume at 0.392, Domain Rating at 0.326, referring domains at 0.295, and raw backlinks at 0.218. Author Louise Linehan is explicit that "while the data shows statistical relationships, I should emphasize that correlation ≠ causation."

Read that table as a small publisher and it says something specific: being talked about in text correlates about three times more strongly than being linked to. A mention in a forum thread or a newsletter is something a niche blog can earn with one genuinely useful piece of research. A backlink profile is not.

Dates, updates, and the freshness question

Seer Interactive tracked 7,683 dated pages carrying 47,097 citations across ChatGPT, Gemini and Perplexity for four brands between March and June 2026. Seventy-five percent of cited pages had been updated within the past year and 88% within two years; content older than three years was, in their words, "basically non-existent."

The split that matters for a small library is this one: by last-update date, 72% of cited pages look fresh, but by original publish date, only 42% do. More than a quarter of the "fresh" cited content was originally published over two years ago (27% for Gemini, 28% for ChatGPT and Perplexity). Sonny Vasquez of Seer summarised it as "The freshness LLMs reward is being manufactured by updates, not by new publishing," and added the corollary: "Newest gets you the spike, established plus maintained gets you the staying power."

New content gets the burst; maintained content gets the annuity.

One conflict, stated plainly: DigitalApplied's sample found no correlation between page recency and citation, with a median cited page age of 14 months. Both findings can be true at once; 14 months sits comfortably inside "updated within two years." The defensible advice that survives both datasets is narrow and cheap to implement: keep a visible last-updated date on the page, and make sure it reflects an actual update, rather than running a publishing treadmill.

For a small library this reframes the job: you are not competing on volume against a content team, you are keeping a handful of pages accurate, dated and worth quoting. In citation terms, a blog compounds when it is tended year-round rather than in bursts.

The technical floor that quietly makes a blog uncitable

None of the paragraph craft matters if the crawler can't read the page. This is the part most GEO advice skips, and the part a technical founder can fix in an afternoon, starting with our crawler checklist to see if your blog is blocked from AI answers.

AI crawlers did not run JavaScript as of Vercel's December 2024 logs. Vercel and MERJ analysed a month of crawler traffic across their network (December 2024): Googlebot 4.5B fetches, GPTBot 569M, ClaudeBot 370M, AppleBot 314M, PerplexityBot 24.4M. They found none of GPTBot, ClaudeBot or PerplexityBot executed JavaScript, even though they fetched JS files. AppleBot and Google's Gemini do render. If your blog is client-side rendered, assume most AI crawlers see an empty shell.

They also pick URLs badly. In the same study, ChatGPT's crawler spent 34.82% of its fetches on 404s and Claude's 34.16%, versus 8.22% for Googlebot; GPTBot spent a further 14.36% following redirects. A clean sitemap, stable URLs and no dead internal links matter more for AI crawlers than for Google, not less.

For anyone publishing markdown to a static site, server-rendered HTML at a stable URL is exactly the shape these crawlers can read, by construction.

Check your OpenAI bot access separately from your training-bot policy. OpenAI's docs distinguish three crawlers: OAI-SearchBot surfaces content in ChatGPT search, GPTBot collects training data, and ChatGPT-User handles user-initiated fetches. The consequential line is explicit: "Sites that are opted out of OAI-SearchBot will not be shown in ChatGPT search answers." Blocking GPTBot to opt out of training is a defensible choice; blocking OAI-SearchBot removes you from ChatGPT search entirely, and plenty of sites have done the second while intending only the first.

Check your snippet directives too. Google's documentation states that to be eligible for generative AI features, a page must be indexed and eligible to be shown with a snippet, with noindex, nosnippet, data-nosnippet and max-snippet as the controls. (The Google-Extended token is a different lever: it governs Gemini training and grounding, not AI Overviews or AI Mode eligibility.) A privacy-minded nosnippet or an aggressive max-snippet opts you out of AI Overviews, quietly.

Cloudflare's defaults changed on 15 September 2026. In an announcement dated 1 July 2026, Cloudflare defined three crawler categories: Search ("any behavior that collects or indexes your content, so it can answer questions about it later"), Agent, and Training. Since 15 September 2026, new domains onboarding to Cloudflare are offered preset defaults: on a site that runs ads, Search stays allowed, Training is set to Disallow AI Training, and Agent bots are blocked on pages with ads. Sites without ads default to allowing all three, and existing domains keep their current settings. If you've put a domain on Cloudflare since then and run ads, check which categories your bot rules actually allow.

The one file you can skip

Ahrefs checked 137,210 domains in May 2026 using server-log data. Twenty-eight percent publish an llms.txt file. Ninety-seven percent of those files received zero requests that month. As Ahrefs put it: "it is not a robots.txt-style directive: it controls nothing and blocks nothing." Gary Illyes said on stage at Search Central Live Deep Dive in July 2025 that Google doesn't support llms.txt and isn't planning to, as reported by Search Engine Roundtable. John Mueller has said "To me, it's comparable to the keywords meta tag", and on Search Off the Record summarised the file's pitch as "It's basically you're telling these systems, like, I have the best website ever."

Which brings up the objection this audience will raise next.

"But Google says none of this is necessary"

It does. Google's official guide to optimizing for generative AI features states, verbatim: "You don't need to create new machine readable files, AI text files, markup, or Markdown to appear in Google Search (including its generative AI capabilities)." Also: "There's no requirement to break your content into tiny pieces for AI to better understand it." And most bluntly: "You don't need to write in a specific way just for generative AI search."

That is a direct primary-source contradiction of a lot of GEO advice, and the honest reconciliation is that Google is describing what's required, not what's advantaged. Meanwhile the GEO-bench experiment and the absorption study both show extraction-friendly prose gets used more heavily once a page is retrieved.

Both statements survive if you frame the work correctly: write for a reader, and make sure each section survives being lifted out of context. There's no secret format. There is such a thing as a paragraph that's easier to quote.

Schema sits in the same bucket. The same Google guide says "structured data isn't required for generative AI search, and there's no special schema.org markup you need to add." Microsoft's Fabrice Canel has said schema helps LLMs understand content for Copilot, but a December 2024 SearchAtlas study found no correlation between schema coverage and citation rates, and there are no controlled experiments here. Aimee Jurenka's framing in Search Engine Land is right: schema is infrastructure, not a magic bullet. Valid frontmatter, correct meta lengths and a clean slug keep a page eligible; they don't lift it. It's the same distinction we drew in our close reading of Google's scaled content abuse policy, where the offence was never the method but volume without value.

How to tell if it's working when the analytics lie

Attribution in AI search is genuinely broken, and you should know that before you run an experiment and misread the result.

Referrer data is incomplete. ChatGPT citation links carry utm_source=chatgpt.com, but free-tier traffic arrives with no referrer and lands in GA4 as Direct. Your dashboard is undercounting by an unknown amount. Server logs are the only free view of the crawlers: because AI bots have not been executing JavaScript, they're invisible to client-side analytics entirely, so grep your access logs for OAI-SearchBot and ChatGPT-User. It's a five-minute job that answers the crawler-access question definitively.

Search Console now shows AI impressions, and only impressions. Google launched its Search Generative AI performance reports on 3 June 2026, covering AI Overviews and AI Mode in Search plus generative AI features in Discover. It began with a subset of sites and, per Google's own note, has been rolled out to all websites worldwide as of 31 August 2026. The reports show impressions, pages, countries, devices and dates; there are no clicks, CTR or queries, and AI Overviews and AI Mode are blended inside the Search view. A directional signal, not a measurement instrument yet. For how to read it without mistaking platform noise for signal, see How to Read Search Console's AI Performance Report.

And the platforms themselves are unstable. seoClarity tracked ChatGPT citation patterns from 8 February to 27 April 2026 across five markets and found citation volumes fell 86–94% across all of them between February and April, then recovering toward pre-March levels in May. The practical consequence: any before/after test you run over four weeks is probably measuring platform noise, not your changes. Give a page-craft experiment a quarter at minimum.

What a citation is actually worth

Be clear-eyed about the prize. SparkToro's analysis of Similarweb's US panel found 68.01% of US Google searches ended without a click in January–April 2026, up from roughly 49% in 2019, and Pew Research Center found users clicked a traditional result in 8% of visits when an AI summary appeared versus 15% when it did not. AI tools collectively send less than 1% of traffic out. What does arrive converts unusually well: Ahrefs found AI search accounted for 0.5% of its traffic but 12.1% of signups, and Semrush put the average AI search visitor at 4.4 times the value of an organic one. The counterweight is Ahrefs' own 81,947-site study from May–June 2025, which found AI visitors less engaged on average (4.0 pages per visit versus 5.2 from search, 67.8% bounce versus 63.7%). We work through the traffic maths in Is a blog still worth it in a zero-click world?

Two further findings should shape what you write. Ahrefs looked at where its own AI search traffic lands: 80% went to free tools, product pages and the homepage, not to its blog. The synthesis: blog paragraphs win citations; product pages, tools and comparison pages win clicks. Do both, and don't confuse which one you're measuring. Content type is also industry-specific: DeltaV Digital's 90-day study of 25,337 citations found listicles earn 61% of AI citations in B2B technology services and 0% in healthcare, and comparison pages were cited about 45% above average per retrieval. Retrieval is not citation. Where the widest doors are, per DigitalApplied's intent breakdown: definitional queries average 5.6 citations per AI Overview and how-to queries 5.1, against 3.1 for commercial queries, so definitional and procedural posts on narrow topics have measurably more room.

The short version, in order

  1. Fix the floor first. Server-rendered HTML, clean sitemap, no dead internal links, OAI-SearchBot allowed, no stray nosnippet or tight max-snippet, and a check on your Cloudflare bot rules (since 15 September 2026, new ad-supported domains default to Disallow AI Training and block Agent bots on pages with ads).
  2. Write one committed sentence per section. Definition, number, comparison or step, under an H2 that matches the literal question, with no preamble above it.
  3. Attach a named source and a number to every claim that carries weight. Then verify the link actually resolves and the page actually says it.
  4. Publish original data where you have any. Your own logs, your own benchmarks, your own before/after. It is the one thing a model cannot generate for itself.
  5. Put a visible last-updated date on every post and honour it. A quarterly refresh pass on your existing posts beats the same number of new ones.
  6. Measure in quarters, in server logs and in Search Console impressions, not in four-week GA4 experiments.
  7. Keep a cadence. Citation accrues to pages that exist, stay accurate and stay maintained.

That last item is where most small blogs fail: not on craft, but on the sixth month.

FAQ

Do I need llms.txt to get cited by ChatGPT or AI Overviews?

No. Ahrefs' May 2026 server-log study found 97% of published llms.txt files received zero requests, Google says it doesn't support the file, and Google's optimization guide says no AI text files are needed. For the longer argument, see our analysis of llms.txt and its SEO impact.

Do I need to rank in the top 10 to appear in an AI Overview?

No. Ahrefs' March 2026 analysis found only 38% of AI Overview citations came from top-10 pages and 31% from beyond position 100. Ranking well helps; it isn't the gate.

Does schema markup get you cited?

The evidence is thin. One 1,000-AI-Overview analysis found pages with Article and BreadcrumbList schema were cited 2.3× more often, but that is correlational, and SearchAtlas's December 2024 study found no correlation at all. Treat schema as hygiene that keeps a page eligible.

How long before a small blog starts getting cited?

Plan in quarters. The one detailed public case study reported zero citations for two months and consistent cross-platform citations by months 9–10, and platform volatility makes any four-week test unreadable.

Should I update old posts or publish new ones?

Both, weighted toward updating if your library is small. Seer found 75% of cited pages were updated within the past year, but more than a quarter of those "fresh" pages were first published over two years ago.

Where this leaves a 20-post blog

The realistic promise is not that you will out-cite Wikipedia or Reddit inside AI answers. Twelve domains take roughly half the citations in AI Overviews, and that is not changing this year.

The realistic promise is the other half: the long-tail, definitional and procedural queries where AI Overviews cite five or six sources, and where the deciding factor is whether your paragraph committed to an answer, named its source, carried a number, and was reachable by a crawler that may not run JavaScript. Those are all page-level decisions, all inside your control, and none of them require a budget.

The hard part is doing it on every post as carefully as on the first, for four quarters, while running everything else. If that's the bottleneck, see Magic Share's plans — your first three posts are free. Or read our other notes on publishing AI-assisted content honestly and go check your robots.txt first. That one's free either way.

More on SEO & GEO →

by email

Get new posts in your inbox

A short digest when new posts go up. Confirm once, unsubscribe from any email.

We use your address only for this digest. Privacy

Keep reading

  1. ·17 min read

    Zero-Click Search 2026: Is a Blog Still Worth It?

    Only about 32% of Google searches still send a click. Here's what a blog is for in zero-click search 2026 — what to write, and what to measure instead.

    zero-click-searchai-overviewscontent-strategyseogeo

  2. ·20 min read

    Is Your Blog Blocked From AI Answers? A Crawler Checklist

    AI citations depend on bot policy you may not have set. Audit which crawlers reach your posts now that Cloudflare's Sept 15 AI bot defaults are live.

    ai-searchseocloudflaretechnical-seocrawlers

  3. ·16 min read

    How to Write a Fair SaaS Competitor Comparison Page

    How to write a competitor comparison page for SaaS that names rivals fairly, sources every claim, and converts — with the evidence and update cadence.

    content-strategyseosaas-marketingcomparison-pagesgeo

Want posts like this for your site?

Magic Share researches, writes and fact-checks posts like this for any site — point it at your URL and review your first draft today.

Plant your first post