Search for "generative engine optimization" and you'll find plenty of guides promising that a few schema tweaks will get your recipes cited by ChatGPT and Google's AI answers. So we read Google's own guidance, checked the studies behind the headlines, and left out every number we couldn't trace to a source.
The short version: Google says optimizing for AI search is still SEO, the traffic coming from AI answers is small so far, and what seems to help looks a lot like what already worked. Here is the detail, written for food bloggers.
What Google says about generative engine optimization
"GEO" (generative engine optimization) and "AEO" (answer engine optimization) are names for the work of showing up inside AI answers: Google's AI Overviews and AI Mode, ChatGPT, Perplexity and similar tools.
On May 15, 2026, Google published an official guide to optimizing for generative AI features. Its position is that, from Google Search's point of view, optimizing for AI search is optimizing for the search experience, which means it is still SEO.
The guide also lists things you don't need to do for Google's AI features:
- Create llms.txt files or any other special markup for AI.
- Rewrite your content in a special way for AI systems.
- "Chunk" your content into pieces for AI.
- Go looking for fake or inauthentic mentions of your brand.
- Obsess over structured data. It isn't required for generative AI search, and there is no special schema for it. Recipe markup still matters for rich results, just not as an AI trick.
What you do need is simple. The page has to be indexed and eligible to show a snippet, and the content has to be unique and genuinely helpful. Google's own advice is to publish unique, non-commodity content. A good gut check: could an AI model write an equally useful version of your page? A basic sugar cookie ingredient list fails that test. Your own testing notes, process photos and fixes for what went wrong pass it.
How AI answers get built: query fan-out
Google says AI Overviews and AI Mode may use a technique it calls "query fan-out": issuing several related searches across subtopics and data sources, then combining the results into one response. Other tools such as ChatGPT and Perplexity behave in a similar way, although they haven't published the details the way Google has.
For recipes, those sub-questions tend to be practical: substitutions, timing, storage, what went wrong. One recipe post rarely answers all of them. A set of connected posts covers many more, which is the logic behind a content cluster.
Be careful with that last step. We haven't seen a study proving that clusters get you cited more often. It is an inference from how the system is described, plus Google's statement that its AI features are built on its core ranking and quality systems.
How much traffic is at stake?
Less than the hype suggests, and in a different place. The best-documented effect is on clicks. Pew Research tracked what happened when Google showed an AI summary:
Pew also found that people clicked a link inside the AI summary itself in only about 1% of visits. So even a citation brings a small trickle of visits today.
The wider picture comes from Chartbeat. Over two years, search referral traffic fell for every size of publisher, and the smaller the site, the bigger the drop:
Chartbeat also reported that traffic from AI chatbots and AI search is nowhere near making up for the loss, while referrals from email, apps and messages are growing as a share of the total. Keep in mind that this is a panel of publishers in general, not recipe sites.
For food specifically, there are two data points. A Semrush study of more than 10 million keywords found that Food & Drink had the biggest increase in AI Overviews of any category between March and November 2025. And a Search Engine Journal test found that searches containing the word "recipe" still showed the regular recipe rich results, while food searches without that word were the ones getting AI Overviews. In other words, exposure is growing, but your recipe card still matters.
What we would actually do
- Get the basics right. Make sure your recipes are indexed, not blocked, and eligible for snippets, and that your Recipe markup is valid for rich results.
- Publish what a model can't invent. Your own process photos, testing notes, failed attempts and fixes. This is where original photography pays off, as we explain in our food photography tips for recipe bloggers.
- Answer the follow-up questions. Add variations, substitutions, storage and troubleshooting, and link those posts to each other.
- Don't depend on one channel. Build your email list and use Pinterest, as in our guide to Pinterest pin size for food bloggers. Our post on zero-click searches covers more of this.
- Skip the magic. No llms.txt file, and no service promising guaranteed AI placement. Google's guide says neither is needed for its features.
- Measure, don't guess. Watch your impressions, click-through rate and referral traffic over time.
What we left out on purpose
You will see studies claiming that AI engines prefer a certain answer length, that freshness boosts citations, or that certain formats get lifted verbatim. Most come from software vendors, use small samples, and disagree with each other. We aren't building advice on them. If solid evidence appears, we'll update this post.
Cover the whole topic
Our content clusters give you a pillar recipe plus five variations, with the photos and keyword research already done.
See how clusters work →Want ready-made photos for a single recipe instead? Browse the shop.