Google's AI Overviews images are back for some searchers as of November 13, four months after a similar test got pulled over publisher backlash. Nobody at Google has confirmed what's running or why. It's inconsistent right now: some people get a generated image, others get an AI Overview that says it "cannot generate images directly." If you publish recipe, how-to or tutorial content, pay attention this week. If you don't, this one's a watch-item, not a fire drill.
What actually happened#
Barry Schwartz at Search Engine Roundtable reported on November 13 that AI-generated images are appearing inside AI Overviews for some searches, spotted first by Derek Hobson on LinkedIn. Schwartz says he could reproduce it in some browsers and not others: a coin-flip, not a rollout.
This follows Google's July 14, 2026 announcement, tied to Google Images turning 25, that AI Overviews would generate custom images from a prompt using Nano Banana when a real photo didn't exist. Visual search was already up 65% year over year by then, per Google VP Robby Stein, and AI Overviews had crossed 2.5 billion monthly users.
At WebEpex we pulled the ranking history on every recipe and tutorial page we manage for AEO clients the day this story surfaced, specifically to see which ones still depend on being the only visual answer to their query. Three did, and we're watching those closest.
Is this the same AI Overviews images feature Google paused in August?#
Probably not the same one, and that's the part worth getting right. I'll be straight about it: I don't know yet which version is back, and neither does anyone I've read on this. In August, Google quietly tested auto-generating recipe illustrations directly in AI Overviews, without anyone asking for an image. Recipe publisher Inspired Taste flagged it on X, arguing it replaced the work of people who actually cook and photograph the dish, and risked readers assuming the linked site made the image.
Stein killed it fast: "This was a small experiment we're no longer running." He added it wasn't "the Nano Banana feature we announced in July, which only triggers when users explicitly ask to generate an image."
So there are two different features that both got called "AI images in AI Overviews" by different people, four months apart, with no public line connecting them. Schwartz's own guess is that November's reappearance is tied to the Gemini 4 Hydrogen update landing in Search around the same week, his word, "probably," not Google's.
Who This Actually Hits (and Who It Doesn't)#
If your traffic depends on being the visual source for how-to, recipe or tutorial content, this is squarely about you. Google generating its own illustration on the results page is one more reason someone never clicks through to yours, on top of what's already measured: Ahrefs found the first organic result loses an average of 34.5% of its clicks once an AI Overview shows up, and a later Ahrefs pass put the CTR hit at 58% for top-ranking pages.
If you're a service business, a SaaS founder or a D2C brand running paid alongside organic, this doesn't change your numbers today. Nobody's generating an image of your product inside an Overview, and nothing here touches commercial or transactional queries. It's a leading indicator, not a current threat, which is exactly why it's worth 90 seconds of your attention now instead of a scramble later.
The honest trade-offs#
The upside, for Google and for users: a faster answer, no extra click. A query that used to send someone three places for a visual now gets one, instantly.
The downside is attribution and trust. Nobody in either rollout has said how the model decides what to draw, whose work it's drawing from, or how a reader knows an answer-page image is generated rather than sourced. The August incident shows Google will pull a feature fast once a publisher makes noise about it. Enforcement here runs on public pressure, not a published policy.
How we're handling it#
At WebEpex we don't publish a single AI-generated image across any client blog or landing page, including this one: every photo we run is a real, licensed shot we source and credit by hand. We made that call before this story broke, specifically because an auto-generated image can't earn the kind of trust a dentist's actual waiting room or a founder's actual product shot does.
For the handful of recipe, tutorial and process-documentation clients we support across our content-strategy service line, we rewrote the content brief this month: fewer generic "how-to" pages competing for a query Google can now illustrate itself, more named-process and behind-the-scenes pages that show a specific person doing a specific thing a certain way. That's harder for a model to summarize into one picture, and it's the kind of page AI answer engines actually cite instead of replacing.
What I'd tell a client this week#
Honestly, not much needs doing yet. Three things, if you want to be thorough:
- If you run recipe, how-to or tutorial content, screenshot your top five queries in an incognito window today, since Google's dashboard doesn't log this one and that's your only before-picture
- Everyone else, spend the time on the actual core-update timeline instead, since that one has a real deadline this month
- If image generation in your AI Overviews is still live next week, the CTR data behind all of this gets a lot more relevant, fast
If you want a read on whether any of this touches your specific pages, send me what you're seeing and I'll tell you straight, no deck attached. [cal.com/webepex/growth-review]