Why a half-baked AI search experience was rushed out the door — and won’t cut it for today’s searcher.


We’ve been closely watching the development of new generative AI search features — both Bing’s AI-generated “stories” and Google’s “Search Generative Experiences” (SGEs).

Our first priority is to make sure we’re prepared for any possible courses of action from Google in particular, as it’s the search engine our clients care most about.

That said, while we have to be ready for any eventuality, we’re not expecting SGE in its current form to ever see a full rollout, and in this post I want to explain why.

Wait, what’s an SGE?

Search Generative Experiences are basically Google’s answer to “the New Bing” in Spring of 2023. Here’s what they both look like:

Screenshots comparing AI generative search results in both Bing and Google.
Screenshots comparing AI generative search results in both Bing and Google.

Same same, but different

You’ll see some similarities across early iterations of AI in both Bing and Google search.

Share This

In both cases, this is basically a big block of content at the top of a SERP that is written by a large language model.

Most SEOs are naturally more concerned about the Google version, owing to Google’s overwhelming market share.

To see Google’s SGEs right now, you need to:

SGEs for every search?

Before we get into the crux of the argument here, it’s worth sharing some background on what SGEs are typically like right now. All this data is taken from the top few keywords in every MozCast vertical, totalling 100 US desktop keywords.

One thing we’ve noticed in our testing is that Google is not showing SGEs by default as much as it was initially. There’s now often a “generate” button.

A screenshot showing an SGE 'generate' button in Google search results.
A screenshot showing an SGE 'generate' button in Google search results.

An SGE ‘generate’ button in the wild

It seems Google is allowing users the option to opt for an AI-generated result for some queries.

Share This

In fact, this was the case for the majority of the SERPs we tested.

A graph showing the breakdown of SGEs showing up in Google search results via a "generate" button or not.
A graph showing the breakdown of SGEs showing up in Google search results via a "generate" button or not.

For now, the ‘generate’ button rules Google SGEs.

In our testing, SGEs needed to be triggered by clicking the ‘generate’ button more than half the time.

Share This

Organic overlap

If you do see (or choose to see) an SGE, as an SEO your eye might be drawn to the prominent three links in the top right. Those are what the AI-generated snippet is supposedly based on.

A screenshot showing three source links for an AI-generated snippet in search results.
A screenshot showing three source links for an AI-generated snippet in search results.

These three links

Currently, SGEs can include source links that the AI-generated snippet is based on.

Share This

You’d be forgiven for assuming these are pages that also appear in the organic top 10, but in fact that isn’t the case. Indeed, in over 40% of cases, there was no overlap whatsoever between these links and the organic top 10, which suggests they’re built on a different system altogether.

A graph showing the breakdown of how often SGEs source links from the top 10 organic listings for that SERP.
A graph showing the breakdown of how often SGEs source links from the top 10 organic listings for that SERP.

SGEs seem to be pulling from lower down the SERP

The source links cited in our test SGEs were all pulled from the top 10 organic results only 13% of the time.

Share This

What about the content within SGEs?

A graph showing the breakdown of different features that appear in SGEs.
A graph showing the breakdown of different features that appear in SGEs.

Taking a closer look at the content in SGEs

SGEs were most commonly made up of raw text, and the next most common feature within was a “Places” (or, map) result.

Share This

Within the SGE itself, overwhelmingly we just saw text — reminiscent of a featured snippet. The most common feature besides text is a map result, but often this is done quite clumsily.

Take a look at this example:

A screenshot showing map results integrated into SGEs.
A screenshot showing map results integrated into SGEs.

Maps within SGEs

An example of maps making themselves comfortable in an SGE result and taking up a lot of extra space.

Share This

Two main issues immediately appear:

  1. The three results in the top right overlap completely with the top three map results in the top left. This is a waste of space.
  2. There’s also a conventional local pack immediately beneath. This is a further waste of space.

Which brings me to the next point…

Executional problems

If, like me, you’ve jumped through hoops and spent some time playing around with this feature, you’ll have noticed that SGEs are just… not very good.

Firstly, there’s the overlap problem mentioned above.

A graph showing how often maps appeared within and below SGEs in search results.
A graph showing how often maps appeared within and below SGEs in search results.

When it came to maps and SGEs, we were sometimes left seeing double

When analyzing our SERPs that contained maps, they appeared both within the SGE and below it 35% of the time.

Share This

This functional overlap is fairly common. If you look at SERPs which have some sort of map (either kind), 35% have both. There doesn’t seem to be any good reason for that since the functionality and intent is nearly identical.

Indeed, SGEs are basically just bolted onto the top of existing SERPs regardless of issues like this. We compared SGE-enabled SERPs to their opted out (i.e. logged out) equivalents, and saw basically identical features beneath SGEs to what would appear on an equivalent SGE-free SERP.

A graph comparing the appearance of different search features in results when opted in for SGEs and not.
A graph comparing the appearance of different search features in results when opted in for SGEs and not.

Comparing SGE results with non-SGE SERPs

Looking at equivalent results when opted into SGEs or not, there didn’t seem to be a ton of difference in what appeared outside the SGE.

Share This

This makes it seem like this feature was potentially pushed out in a rush, and perhaps more to the point for Google, it’s also not well monetized (yet).

A graph showing that currently Google Ads are only present on 30% of SGE SERPs.
A graph showing that currently Google Ads are only present on 30% of SGE SERPs.

SGEs are not yet highly monetized by Google

In our testing, we noticed only 30% of SGE SERPs contained Google Ads, and the ads were never actually within the SGE itself.

Share This

SGE SERPs are often not monetized, and when they are, the ads are relegated way down the SERP from where you’d normally find them.

A screenshot showing how far down the SERP ads are pushed when an SGE is present.
A screenshot showing how far down the SERP ads are pushed when an SGE is present.

How low can you go?

We noticed in the instances that Google Ads did appear on SGE SERPs, that they were pushed much farther down the page than usual.

Share This

This is without going into the numerous accuracy and plagiarism issues highlighted by many in the SEO industry.


To be fair, Google is still iterating and testing new features on SGEs — they’re not done yet. But progress is slow. Ultimately this has been in testing for months, and still feels like there’s a long way to go.

Conceptual problems

It’s not just execution problems, though. My colleague Pete sums it up well here:

And he’s not the only one.

The fact is that SGE, for now, mostly shows similar or worse information to existing Google SERP features, but with a perhaps 5-10 second loading time (Cumulative Layout Shift, anyone?), added cost to Google, and all sorts of monetization and legal issues to solve.

Bing seems to have run into the same UX concerns. The screenshot above of a Bing AI-generated “story” in the SERP is actually from much earlier this year. Here’s what it looks like now:

A screenshot showing Bing AI-generated stories on the SERP.
A screenshot showing Bing AI-generated stories on the SERP.

Bing AI-generated stories

It looks like over time, Bing has moved their AI-generated stories further down the results page.

Share This

Bing is still going to the trouble of generating these “stories,” but I really struggled to find a Bing SERP now that put it at the top of the results, like they all were back in March. This won’t be an accident — Bing has realized that their original results were a better answer.

Lastly, I’ve not even gotten into the legal problems in this post, but Google has been successfully legislated against in France for featured snippets, and in both France and Australia to force revenue sharing with news publishers.

Arguably the featured snippets case was a pyrrhic victory for French publishers, but that is a fraction of the challenge posed by either the plagiarism or disinformation aspect of SGEs down the road.

Right now it’s kind of lawless, but eventually regulation will come. (It’s likely not a coincidence that this feature is currently not available in the EU.)

So, why did they do it then?

Under huge pressure from investors, competitors, and the media, keen to portray Google as losing an AI arms race and at risk of losing its dominance of search, Google had to do something — so they pushed out a rush job.

If SGE was really how they wanted to use LLMs, they’d have done it years ago. Instead, we suspect the way this technology will be utilized by Google is far more subtle, as with AI tech in the Google algorithm for years. (My former colleague Tom Anthony spoke about this recently at MozCon.)

For SEOs, then, that means a likely less radical departure than some are fearing right now. SERPs will continue to evolve, gaining sophistication, new features, and ever more nuanced ranking signals.

They’ll also almost certainly wipe out more and more of the low-end, commodity organic results that featured snippets, knowledge graph results, and now, generative AI responses, handle well.

But a huge block of nonsense appearing after a lengthy delay at the top of every SERP? Unlikely.