Over a year ago, we first started noticing Google showing featured snippets with one source for the snippet itself while using a second source for the image. Earlier this year, Google began to increase the likelihood of this happening, resulting in some upset webmasters who claimed the featured snippet, only to see a competitor’s thumbnail show up in the same featured snippet.
At SMX Advanced last week, Gary Illyes from Google was asked about this specific case, and unfortunately for those who hate this featured snippet implementation, it sounds unlikely Google will change this.
— Jennifer Slegg (@jenstar) June 13, 2017
From a searcher’s point of view, having a better image in the featured snippet makes for a better user experience, especially if none of the images on the page are suitable to be included. So the first step to score the image would be to have a suitable image on the landing page that could be used instead.
Now, if you have the image in a featured snippet, clicking on the image doesn’t automatically go to the source landing page for the image, nor does it go to the page that the actual featured snippet is taken from. Instead, it opens a Google image search for the query, meaning multiple clicks are required for someone to get on the site the image is sourced from. So these images do not have a lot of CTR value for landing on the actual site. However, some see it as a stepping stone for being able to claim the featured snippet itself, or as bragging rights for getting an image to show up in a competitor’s featured snippet.
But if you are waiting for Google to “fix” this, you will likely be waiting a long time for it.
Latest posts by Jennifer Slegg (see all)
- No Plans for Google to Mark HTTP as Insecure in Search Results - September 22, 2017
- Google: Do HTTPS Migrations Separate From Other Major Changes - September 22, 2017
- Google: Rankings Should Remain Stable With HTTPS Migrations - September 21, 2017
- Google: Value (or Not) of Doing Link Audits - September 20, 2017
- Google Indexes AMP Version for Mobile First When No Regular Mobile Page - September 19, 2017