One question I hear a lot from business owners right now goes like this: “Should my pages be longer so AI tools quote them, or shorter so AI can grab the answer quickly?” Some people have read that AI only cites 10,000-word mega guides. Others have read the exact opposite, that AI prefers tiny 300-word answers because it “can’t read” long pages.
Both camps can’t be right. And if you are paying writers by the word, or cutting good pages down to fit a rule, the answer matters for your budget.
The good news is that we now have real data on this, plus clear statements from Google. Let me explain what the numbers say, why both short and long pages get cited, and how I suggest you decide the right length for each page. In brief: length is not the lever. Intent is.
Where the “write longer for AI” and “write shorter for AI” ideas came from
The long-content belief mostly comes from old SEO habits. For years, people noticed that top-ranking blog posts were often long, and “longer is better” became a rule of thumb. When AI search arrived, some marketers simply carried that rule across.
One widely shared example was a Reddit post in r/content_marketing claiming that pages needed 10,000+ words to be cited by AI. The problem is the sample. As Ahrefs pointed out, it looked at only 20 brands. That is far too small to tell you anything about how AI tools behave across millions of searches.
The short-content belief comes from a different idea: that AI models have small “context windows.” A context window is simply how much text a model can read at once. If the window is small, the theory goes, a long page gets cut off, so short pages win.
That theory is out of date. Google’s own Gemini long-context documentation (last updated October 2026) says many Gemini models have context windows of 1 million or more tokens, which Google says is roughly eight average-length English novels. A 3,000-word blog post is a tiny fraction of that. So “AI can’t read long pages” is not a good reason to write short ones.
What 174,000 cited pages tell us about length and AI Overviews
The most useful study I have seen on this is from Ahrefs. In Short vs. Long Content in AI Overviews (December 3, 2025), Despina Gavoyannis and the Ahrefs data team looked at 560,346 AI Overviews containing about 1.68 million cited URLs. They were able to extract clean text from 174,048 pages, stripped out menus and boilerplate, and counted the words.
“Spoiler alert: there’s almost no correlation between word length and being cited in AI Overviews.”
— Despina Gavoyannis, Ahrefs, Short vs. Long Content in AI Overviews
Here are the headline numbers, summarised in my own words:
- Correlation is basically zero. The Spearman correlation between word count and being cited was 0.04. A correlation of 0 means no relationship and 1 means a perfect one, so 0.04 is noise.
- Cited pages are only slightly longer than ranking pages. Cited pages averaged 1,282 words. The average page ranking in Google’s organic results averaged 1,188 words.
- More than half of citations go to pages under 1,000 words. 16.6% were under 350 words and 36.8% were 350–1,000 words, which adds up to 53.4%.
- Short pages still land the top spots. Over 95% of citations to pages under 350 words appeared in positions one to three of the AI Overview.
| Word count band | Share of AI Overview citations | What usually sits in this band |
|---|---|---|
| Under 350 words | 16.6% | Listings, product and service pages, tool pages |
| 350–1,000 words | 36.8% | Short answer pages, forum threads, video pages, tools |
| 1,000–2,000 words | 30.6% | Typical articles and guides |
| Over 2,000 words | 16.0% | Long guides, transcripts, reports |
Source: Ahrefs, December 2025. The “what usually sits here” column is my reading of their page-type data, not a separate measurement.
The page-type breakdown is the part I find most useful. Ahrefs reported median lengths of about 315 words for listings, 317 for core pages (like homepages and service pages), 387 for user-generated content, 507 for interactive tools and 1,166 for articles. In other words, each type of page has its own natural length, and AI Overviews cite all of them.
The limits of this data
I want to be fair about what this study can and can’t tell you. It covers Google AI Overviews only, not ChatGPT, Perplexity or AI Mode. And it is correlational. It shows that length and citation don’t move together, but it can’t prove why a page was picked. So I treat it as strong direction, not a law. Still, it is 174,000 pages, not 20 brands, and it lines up with what Google itself says.
What Google says about page length for AI search
Google has been unusually direct about this. Its guide on optimizing for generative AI in Google Search (updated July 2026) addresses length head-on:
“There’s no ideal page length, and in the end, make pages for your audience, not just for generative AI search.”
— Google Search Central, Optimizing for generative AI
The same guide adds that shorter or longer pages can both work, depending on your audience and subject. It also says there is no requirement to break content into tiny pieces for AI to understand it.
This matches Google’s long-standing guidance on creating helpful, reliable, people-first content, which asks whether you are writing to a particular word count because you heard Google prefers one. Google’s answer is that it doesn’t. And Google’s page on AI features and your website says there are “no additional requirements” to appear in AI Overviews or AI Mode beyond being indexed and eligible to show with a snippet.
So the official line and the data agree. Nobody is grading your word count.
Why a 300-word page and a 3,000-word guide can both get cited
If length doesn’t matter, what does? Let me explain it simply. When an AI system builds an answer, it is looking for the passage that best answers a specific sub-question. It doesn’t care how much text surrounds that passage, as long as it can find it and trust it.
That is why both extremes work:
- A short page wins when the whole page is the answer. “What are your opening hours?”, “How much does a tyre change cost?” or “Is this product in stock?” A 250-word page with the exact fact, clearly stated, is perfect.
- A long page wins when the question has many parts. Google says AI Overviews and AI Mode may run several related searches across subtopics, which it calls query fan-out. I explain this in my guide on how one prompt turns into many web searches. A thorough guide can answer several of those sub-questions at once, so it has more chances to be picked.
Notice that the long page is not winning because it is long. It is winning because it covers more of the questions people actually ask. If you added 2,000 words of fluff, you would get the length without the coverage, and nothing would improve.
Freshness and trust also play a part. Ahrefs found in a separate study, Do AI Assistants Prefer to Cite “Fresh” Content? (July 2025, updated April 2026), that pages cited by AI assistants were on average about 25.7% fresher than pages in organic results. A short page that is current can beat a long page that is three years stale.
Matching length to search intent, page type by page type
Search intent is the goal behind a search: to learn something, to compare options, to buy, or to find a specific site. I cover the basics in my guide to search intent. For AI citations, intent is the best predictor of the right length.
Here is the length range I suggest as a starting point for common page types. These are my working ranges, informed by the Ahrefs medians above. They are not rules from Google.
| Intent / question type | Best page type | Starting length range | What the AI is looking for |
|---|---|---|---|
| Quick fact (“How long does X take?”) | Answer page or FAQ block on a service page | 250–600 words | One clear sentence with the number or fact |
| Local or transactional (“tyre change near me”) | Service or location page | 300–800 words | Price range, area served, hours, proof |
| Product or tool (“mortgage calculator”) | Product page or interactive tool | 300–700 words plus the tool | Specs, a working tool, short explanation |
| Definition (“what is a backflow test?”) | Short explainer | 500–1,000 words | A crisp definition, then context |
| Comparison (“X vs Y”) | Comparison article | 1,000–2,000 words | A table, clear verdicts per use case |
| Complex how-to or decision (“how to choose a heat pump”) | Full guide | 1,800–3,500 words | Steps, trade-offs, worked examples |
If you are unsure, look at what already gets cited. Search your main question in Google, open the AI Overview’s sources, and note the page types. If every source is a short service page, a 4,000-word guide is the wrong tool for that query. My post on when long-form content wins (and when it doesn’t) covers the same thinking for classic Google rankings.
How to make a long guide easy for AI to quote
Long pages are fine. Long pages where the answer is buried are the problem. If you are writing a 2,500-word guide, here is how I would structure it so each section can stand on its own.
- Write one question per section. Each H2 should match a sub-question a real person would ask, in their words. “How long does a heat pump last?” beats “Lifespan considerations.”
- Answer in the first two sentences under each heading. Put the direct answer first, then the detail. I explain this approach in my guide to answer-first writing.
- Make each section self-contained. Avoid “as mentioned above.” If a section only makes sense after reading three others, it is hard to quote on its own.
- Use tables for comparisons and numbers. A table of prices, specs or timelines is easy for both people and machines to scan.
- Name things fully. Write “the Ahrefs study of 174,048 pages” rather than “the study.” A quoted passage loses its surrounding context.
- Keep the facts current. Update numbers, prices and dates when they change, and show a real “last updated” date.
A note on chunking. You will see advice to split every page into tiny AI-friendly “chunks.” Google says this is not required:
“There’s no requirement to break your content into tiny pieces for AI to better understand it.”
— Google Search Central, Optimizing for generative AI
I agree with that, with one nuance. Clear sections with direct answers help readers as much as machines, so they are worth doing anyway. Just don’t chop a good page into fragments that no longer make sense. My guide on writing passages AI can quote goes into the sensible middle ground.
When a short answer page beats your big guide
Sometimes the best move is to add a short page, not lengthen a long one. This happens more often than people think.
Look for these signs:
- People keep asking one narrow question that your big guide answers only in paragraph 14.
- The question has a single factual answer, like a price, a time, a size or a yes/no.
- The AI Overview for that question cites short pages from competitors, directories or forums.
- The answer changes often, so a small page is easier to keep current.
Example: a dental clinic with one guide and many questions
This is a hypothetical example to show the thinking. Imagine a clinic with one 3,000-word guide called “Everything About Dental Implants.” It covers cost, pain, recovery, materials and aftercare. Search Console shows the guide getting impressions for 40 different queries, but the clinic’s own name rarely appears in AI Overviews for “how long does implant recovery take.”
The clinic could do two things. First, rewrite the recovery section so the first sentence answers directly: “Most patients return to normal eating within 7–10 days, and full healing takes three to six months.” (In a real page, those figures should come from the clinic’s dentists and be reviewed.) Second, create a separate 500-word “implant recovery timeline” page with a simple week-by-week table, and link it from the guide.
The guide keeps serving the broad, research-type questions. The short page gives the AI a clean, single-purpose source for the narrow one. Neither page is padded.
Padding: the habit that hurts both readers and citations
Padding is anything you add to reach a word count rather than to help the reader. It is the biggest risk when people hear “longer pages get cited.” Common forms include:
- Long intros that restate the title three ways before answering.
- History sections nobody asked for (“Since ancient times, people have…”).
- The same point repeated under three different headings.
- Generic definitions of terms your audience already knows.
- Auto-generated FAQ blocks that repeat the body text word for word.
Padding pushes your real answer further down and makes each section less clear. It also costs money if you pay per word. Google’s helpful content guidance lists writing to a word count as a warning sign, and its spam policies cover pages made mainly to manipulate rankings.
A quick padding test
Here is a simple test I suggest. Take any section and delete it. If a reader would not miss it, and no question goes unanswered, it was padding. If you can cut 20% of a page without losing a single fact, step, example or number, cut it. A content audit using these rules often finds more to trim than to add. My content editing checklist has more checks like this.
A length decision checklist you can use before writing
Before you brief a writer, run through these questions. They take five minutes and save a lot of wasted words.
| Question | If the answer is yes | If the answer is no |
|---|---|---|
| Does the main question have one factual answer? | Short page or a section on an existing page | Consider a fuller guide |
| Do the cited sources in the AI Overview tend to be short pages? | Match that format and length | Look at what the long sources cover that others don’t |
| Are there five or more related sub-questions people ask? | A guide with one section per sub-question | Keep it focused and short |
| Will a table, tool or calculator answer it better than prose? | Build the tool, add a short explainer | Write prose with a clear answer up front |
| Can every section stand alone if quoted? | Publish | Rewrite openings to answer directly |
| Could you cut 20% without losing a fact? | Cut it | The length is probably right |
If you want the data side of this, it helps to know where AI Overviews show up for your keywords in the first place. I break that down in my guide on which query types trigger AI Overviews. And because getting cited is not the same as getting linked, my piece on how often AI assistants link to the brands they name is worth a read too.
Questions people ask about content length and AI citations
Do AI Overviews prefer long-form content?
No. In Ahrefs’ study of 174,048 cited pages, the correlation between word count and citation was 0.04, which is effectively zero. More than half of citations went to pages under 1,000 words.
Is there an ideal word count for getting cited by ChatGPT or Gemini?
Nobody has shown one, and Google says there is no ideal page length for its AI features. The Ahrefs data covers AI Overviews only, so I treat other assistants as unknown, but the logic of matching the answer to the question applies everywhere.
Should I split my long guides into lots of small pages?
Usually not. Google says you don’t need to break content into tiny pieces. Split only when a narrow question deserves its own page, and keep the guide for the broad topic.
Can AI models read very long pages?
Yes. Google’s Gemini documentation says many Gemini models accept 1 million or more tokens of context. A normal blog post is nowhere near that limit.
Does adding more words help if my page isn’t being cited?
Only if the new words answer questions the page was missing. Adding coverage helps. Adding filler makes the answer harder to find.
Where I would start with your page lengths this month
If you want one practical step, pick your ten most important pages and ask a simple question of each: “Does the first paragraph under every heading answer a real question directly?” Fix the ones that don’t. Then look for narrow questions buried in long guides and decide whether they deserve their own short page.
Stop paying for words and start paying for answers. That is the whole shift. If you want help planning pages that match what your customers actually ask, our content writing team and SEO services can do the research and the writing with you. For a wider look at what else drives AI visibility, see my guide on which AI citation sources you can actually influence and how much traffic AI Overviews take. When you are ready, get in touch for a free quote.
Further reading on content length for AI citations
- Do AI Answers Cite AI-Written Content?
- Do LLMs Flatten Original Ideas? Keeping Your Brand's Point of View in AI Answers
- MCP for Marketers: Connecting AI Assistants to Your Data and Tools
Sources for this content length and AI citations guide
- Ahrefs — Short vs. Long Content in AI Overviews (December 2025)
- Google Search Central — Optimizing for generative AI in Google Search
- Google Search Central — Creating helpful, reliable, people-first content
- Google Search Central — AI features and your website
- Google AI for Developers — Gemini long context
- Ahrefs — Do AI Assistants Prefer to Cite “Fresh” Content?
- Reddit r/content_marketing — the “10,000+ words” claim discussed above
