Google this week began testing showing multiple contextual links within a single featured snippet result. In short, a featured snippet would have not just a single link to the publisher that Google used for this content, but would augment that featured snippet to provide links on phrases that Google feels needs more explanation. The catch is, those links would not link to the place Google grabbed the featured snippet from, but to other web sites.
What it looks like. Brodie Clark spotted this in action earlier this week and posted about it on Twitter. I was able to replicate it and here is a high resolution screen shot of this in action:
How it works. When you hover your mouse cursor over the dotted lines in the featured snippet, Google will overlay content from a third-party site. If you click on that dotted line or overlay, Google will take you to that third-party site, not the site Google uses for the featured snippet result.
Here is a video from Brodie Clark of it in action:
Google confirmed this as a test. A Google spokesperson confirmed with Search Engine Land that this is indeed something the company is testing. Google told us this is still a small experiment and the example we showed the company was not triggering the result in an ideal fashion. Google promises to continue to experiment and refine this feature.
Google’s goal is to help searchers understand jargon or technical terms they might not fully understand, by giving them this additional context without having to leave the page. But again, they can leave the page, by clicking on it, if they want to.
As you can see, Google is clearly giving searchers a quick snapshot of the information in this overlay so the searcher does not have to leave the search result page. But the issue still is, these links and overlays are not coming from the source of that snippet of content and Google is adapting and augmenting that content with the goal of benefiting the searcher but potentially hurting the publisher.
The problem. When featured snippets first launched, Google was called out as being a scraper site for stealing content from hard working publishers. Google did adapt the results over time but initially said publishers will deal with it. But truth is, most SEOs I know would prefer to have the featured snippet over a normal snippet, as they tend to drive more traffic than the normal snippets below it. But this depends and you need to test it.
Now, in this case, you win the featured snippet and you are super excited. But now, Google is overlaying additional links, to sites that the publisher of this featured snippet did not link to in the source, but rather to other parties. Who knows, maybe Google even links to a competitor of yours. You wrote this content, Google is adding links on this content to other sites that are not yours. This can, and likely will, result in less clicks to your site.
Yes, this is useful to the searcher but this is your content, not Google’s. Does Google have a right to add additional links on your content that does not go to your site?
Google will keep testing. As I said above, Google said it is a small experiment. This may never really fully launch and if it does launch, it might launch in a different form. So hopefully, if it does launch, Google will do it in a way that not just helps searchers, but also helps the source of the featured snippet – the publisher.
Web stories in desktop search results. The other part here is that this snippet is not from any specific publisher. This is automatically created using Google’s AI system to build web stories. So Google took content from around the web, put together this web story and the company is using its own web story as a featured snippet. Will Google eventually just do away with content on the web and build and link to its own content? That strategy cannot work in the long run, so why tease it?
The web story leads to a mobile user interface – and Google has confirmed with us isn’t a great experience on desktop and the company look into what the most appropriate improvements might be for this feature. If you want to see where this featured snippet goes, it goes to https://www.google.com/search/static/gs/m016kjs.html (now showing a 404 error).
Why we care. In this form, Google is doing two things that can hurt publishers.
First, Google is taking publisher’s featured snippets and adding links to sites that are not yours – links you did not add.
Second, Google is using their own AI to build these web stories and sourcing them as some featured snippets. Google’s AI builds this content based on numerous sources of content on the web, possibly partially from your own site. Are you getting credit?
The final aspect is that the web stories experience is really mobile-centric and it feels awkward on desktop.
Postscript: As of around 1am ET on November 25th, all the web stories that we were tracking (about 22,000 of them) are returning a 404, page not found error. Maybe Google is deleting all of their AI created web stories? We asked Google for more details and will update you when we hear more.
Postscript 2: Google has confirmed that it was unintentional that Google was showing Google-generated web stories as featured snippets and thus decided to 404 those results. Google does not want to show autogenerated Google web stories in the featured snippets. Google has thus decided to block these pages from being indexed.