AI Search and GEO · How to
How to write for AI Overviews: format and sourcing that get quoted
Part of the guide Generative engine optimization (GEO): a practical guide for 2026
To write for AI Overviews, write a page a person would quote: one question per heading, the answer in the first two or three sentences, named things instead of categories, numbers with units and a date, and sources a reader can check. Google says there is no special format or markup required, so these are writing habits that make a passage easy to lift, not technical tricks.
Start from what Google says, then write for the reader
Google's position is that AI Overviews need no special optimization. Its AI features page says "there are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary", and its AI optimization guide (May 2026) says you can ignore tactics like "chunking" content for Google Search.
That rules out gimmicks, not good writing. An AI Overview is assembled from passages Google finds on indexed pages, so a page with clear, specific, verifiable passages simply has more usable material. Eligibility rules and opt-out controls are covered separately in how to rank in Google AI Overviews; this guide is about the words on the page. For the wider strategy, see the GEO guide.
Step 1: Pick the question each section answers
Each H2 should map to one question a searcher actually asks, phrased the way they ask it. AI Overviews often appear for questions that break into several smaller searches, and each of your sections can match one of them.
Practical ways to find the questions:
- Search Console's Performance report, filtered to queries containing "how", "what", "why", "vs", "cost" or "best".
- The "People also ask" box for your main keyword.
- The questions customers send you by email, chat or phone.
A page about robots.txt for AI crawlers might carry H2s for "Does blocking GPTBot remove me from ChatGPT?", "Which bot does Perplexity use for search?" and "How long does a robots.txt change take to apply?" Each heading is a separate, liftable unit.
Step 2: Put the answer in the first two or three sentences
The sentence directly under a heading should answer it without needing the rest of the page. Context, caveats and examples come after.
Weak opening: "AI crawlers are an important consideration for site owners, and there are several factors to think about."
Liftable opening: "Blocking GPTBot does not remove you from ChatGPT search. GPTBot collects training data; ChatGPT search relies on OAI-SearchBot, and OpenAI says sites that block OAI-SearchBot will not be shown in ChatGPT search answers."
The second version names both bots, states the effect and cites who says so. Our guide to answer-first writing has more before and after rewrites.
Step 3: Use names, numbers and dates
Vague statements are hard to quote because they say nothing a reader can use. Replace categories with names and estimates with sourced figures.
| Instead of | Write |
|---|---|
| "Works with several popular platforms" | "Publishes natively to WordPress, Shopify, Webflow, Ghost and Notion; Wix and Framer need a webhook" |
| "Prices vary" | "Paid plans start at $29 a month as of November 2026" |
| "Recently updated" | "Last updated November 16, 2026" |
| "Many experts recommend" | "Google's SEO Starter Guide recommends" |
| "It can take a while" | "Allow about 24 hours after a robots.txt change (per OpenAI's crawler docs)" |
Every number needs a unit and, if it can change, a date. Prices without "as of" go stale and an AI system has no way to know which version is current.
Step 4: Build real tables for comparisons
When you compare more than two named things, use an HTML table with a header row, not a paragraph and not an image of a table. A table states the comparison in a structure that survives being quoted in part, and a screenshot cannot be read as text at all.
Good table habits:
- One row per option, one column per attribute that matters to the decision.
- Units in the header ("Price, USD per month, Nov 2026").
- A notes or source column when values come from different places.
- At least one row where your own product or recommendation is weaker, if you are on the list.
Step 5: Source like a careful journalist
Cite primary sources for any figure: the vendor's own pricing page, the official documentation, the original study. Link neutral authorities directly and name the date you checked.
Sourcing affects trust in two ways. Readers can verify you. And honest sourcing avoids a known failure: Lily Ray's June 2026 study of 100 B2B "best software" queries found that when an AI Overview cited a brand's own "best" listicle, it left that brand out of the recommendation 69% of the time. Self-serving claims get used as evidence for someone else.
If you cannot verify a claim, cut it. "Not verified" is better than a confident wrong number that gets repeated.
Step 6: Say what something does not do
Constraint statements are some of the most quotable sentences on the web, because many questions are binary: "Does X work with Y?", "Can I do Z without W?". Write them plainly:
- "The plugin does not support multisite installs."
- "This method does not work on Shopify's Basic plan" (only if true and sourced).
- "We do not offer phone support."
This is the constraint page type applied inside an article.
Step 7: Keep the page current and readable by crawlers
A passage can only be quoted if Google can read it and trusts that it is current.
- Make sure the full text is in the HTML Google receives, not loaded later by a script.
- Check that no
nosnippetor lowmax-snippetvalue is set on the page; Google says these limit use of the content in AI Overviews. - Show a visible "Last updated" date, and change it only when you make a real edit.
- Review any page with prices or statistics at least every 90 days.
A worked example
Here is one section from a page about getting new pages discovered faster.
Does IndexNow notify Google? No. An IndexNow submission is shared with the participating search engines listed on the IndexNow FAQ, such as Bing, Naver, Seznam.cz, Yandex and Yep, and Google is not among them as of November 2026. For Google, list your sitemap in robots.txt or submit it in Search Console's Sitemaps report.
What makes it liftable: the question is the heading, the first word answers it, the second sentence names the engines and dates the claim, and the third tells the reader what to do instead. Nothing depends on earlier paragraphs, and every fact traces to the IndexNow FAQ or Google's sitemap documentation.
Mistakes to avoid
- Writing a 150-word introduction before the first answer.
- FAQ sections that repeat the body word for word with no new questions.
- Splitting text into tiny fragments for "AI chunking", which Google says is unnecessary.
- Unsourced statistics, or figures from a study you did not read.
- Listicles that put your own product first on every list.
FAQ
Do I need special formatting or schema to appear in AI Overviews?
No. Google says there are no additional requirements or special optimizations for AI Overviews and no special schema.org markup to add. Clear headings, direct answers and accurate content are about making passages useful, not about meeting a technical rule.
How long should an answer under each heading be?
Put the core answer in the first two or three sentences, then add detail below. The opening should make sense if it is the only part a reader sees.
Should I write differently for AI Overviews than for regular search?
Mostly no. The same people-first content that ranks in Google is what AI Overviews draw on. The difference is emphasis: more direct answers, more specific numbers with dates, and tables for comparisons.
Does adding an FAQ section help with AI Overviews?
It can help readers when the questions are real and not already answered above. Google no longer shows FAQ rich results (removed in 2026), so an FAQ is for readers and for quotable answers, not for a special search feature.
Sources
- Google Search Central, AI features and your website: no additional requirements or special schema, accessed 16 November 2026
- Google Search Central, AI optimization guide: chunking not needed, accessed 16 November 2026
- Google Search Central, robots meta tag: nosnippet and max-snippet effect on AI Overviews, accessed 16 November 2026
- Google Search Central, documentation updates: FAQ rich result removal in 2026, accessed 16 November 2026
- OpenAI, overview of OpenAI crawlers: about 24 hours for robots.txt changes, accessed 16 November 2026
- IndexNow FAQ: participating search engines, submissions shared across them, accessed 16 November 2026
- Google Search Central, build and submit a sitemap: robots.txt and Search Console submission, accessed 16 November 2026
- Postbing product documentation, checked 16 November 2026: native publishing targets and starting price used in the table example
- Lily Ray, "Why calling yourself the best could be helping your competitors" (Substack, 17 June 2026): 69% figure, accessed 16 November 2026
Related reading
Last updated: November 16, 2026. Spotted an error? Email support@postbing.com and we will fix it. Editorial policy.
Try Postbing free
Postbing reads your site, plans a month of topics from what your customers search for, writes in your voice and publishes to WordPress, Shopify, Webflow or Ghost. Your first article is free.
Try Postbing freeNo card needed. No link exchanges, ever.