[Review] I have early access to Google’s Search Generative Experience (SGE). Here’s what you need to know

Google has now opened up access to their generative AI labs test to a small portion of testers. This means a select handful of users are now able to test Google’s highly anticipated AI-powered results.

In the past, I have reviewed Google’s Bard chatbot and felt as though Bing was doing a better job overall. My biggest gripe with Bard has been the lack of citations, something that generative AI within Search is designed to do a better job of.

Once I saw access was rolling out to users, I was very eager to jump in and run some tests for a selection of queries where I’ve been wondering how generative AI would present their search results. Thanks to the help of Brendan OConnell, Senior Manager of Organic Search at The New York Post, I was all set to go.

Here are my initial thoughts on generative AI in Google’s search results with the Search Generative Experience (SGE).

How to gain access to SGE

Similar to how Bard was first made available, there is a waitlist that you’ll need to sign up to. You’ll need to be located in the US (or at least using a VPN) to be added to the list, along with not having a Workspace account, which can be a roadblock for many. Tip: use an old gmail address or sign up for a new one if you’re eager.

At the time of writing this article, Google has only sent out invites to test their Search Generative Experience (SGE) to a small portion of testers. So if you haven’t received an invite just yet, I would expect an email within the next week or so letting you know that access has been granted.

Moving on, now for the information that you’re most interested in. Beyond the previews shown at Google’s I/O event, here are some examples of how Google’s search results have changed, how it will impact publishers, my feedback for Google, along with some additional insights.

Search Generative Experience (SGE) vs. normal Google

The most surprising aspect to me about Google’s Search Generative Experience is that featured snippets are still available alongside AI answers. I was previously under the impression that featured snippets would be replaced by AI answers, so this is already a better case scenario for publishers.

It is also interesting to note that users seem to need to ask the generative AI to provide the answer by clicking ‘generate’ if it isn’t showing by default. While it isn’t currently showing for some queries (such as for queries about politics), it does appear to show quite broadly.

Based on the approach to featured snippets and allowing users to select ‘generate’ to show the AI answers, Google is trying their best to not shake up the ecosystem too much. If Google were to launch the SGE available to beta testers, it would create far less volatility than we previously thought.

Here’s what this looks like to generate an AI answer within the SGE:

The SGE showing the ‘Converse’ tab and the ‘Generate’ button

Another good example of Google’s SGE in action is for a query where I currently rank within the featured snippet for an article in the US. All of the content within my article is unique to my expertise (I have a ton of experience in Marketplace SEO), so I’m confident that I’m the original source of information.

When searching for the query ‘”what is marketplace seo” within the SGE, I’m provided with the generative AI answer at the top of search results with quite an extensive summary, along with 3 links to articles that are supposedly the source for the AI component of the SERP.

SGE example showing a featured snippet below the AI answer with incorrect attribution

The issue here is that the 3 links are seemingly presented as the source for the AI answer. While this may be true to some extent, this is not the full truth. Google’s SGE is taking content from my article and presenting it as their own. The reason I know this to be true is that I have explicitly experimented with the wording and Google only started using that text in the featured snippet recently.

The content in itself could seem as fairly generic for anyone that knows SEO (it includes content, links and technical), and Google seems to be using that to their advantage. But I would bet that Google wouldn’t use that exact same wording if it wasn’t on my web page.

Update: Google has now actually made a change to the SGE example shown above. Previously, Google was not showing my website within the sources list in the carousel at the top, only in the featured snippet below. Google was clearly using content from my website, so it is good to see that they have updated this specific result. Attribution for exact match text usage needs to become more precise however.