January 31, 2019
If you follow us on Twitter, you would have seen that we recently posted a video showing a Google mobile SERP that features up to fourteen ads:
Google testing new Ads setup on mobile search. 11 ads with two organic listing then 7 organic listings and finally 3 further ads #Google #SEO #GoogleAds #PPC #GoogleUpdate #SERP pic.twitter.com/NInKxKm4Hd
— Fibre (@Fibre_Marketing) January 25, 2019
As you can see, there are four ads on the top of the page, followed by two organic listings. Seven more ads appear followed by six organic listings, and then the page ends with three final ads. That’s twice as many ads than usual, and our video kick-started a backlash across Twitter.
We believed that this was another test by Google concerning its search engine results pages, only this one focused solely on mobile searches.
From what we have seen, the SERPs are not still like this, but the discussion on Twitter is still ongoing:
— Chris Johnston (@chrisjohnston) January 25, 2019
Nah that many ads will turn users off — search is getting so irrelevant anyway– they forget what killed yahoo search.
— Kristine Schachinger (@schachin) January 28, 2019
Wow that’s a true garbage experience.
— Scott Wainner (@scottwww) January 29, 2019
It has been predicted for a while that Google would push its Ads, and the founder of Moz, Rand Fishkin, recently reported that, in 2018, there had been a decline in click-through rates yet an increase in no-click searches. This statistic reflects how Google SERP features, such as Google Ads and Featured Snippets, are competing for clicks.
However, Google Ads responded to our tweet, confirming that it was, in fact, a bug and not a test:
Thanks for catching this! We didn't intend to show these extra ads. This was a bug impacting a very small number of queries and it has already been fixed.
— Google Ads (@GoogleAds) January 29, 2019
While their reply has received some mixed responses, it is a relief to know that this is not likely to be the layout of mobile searches anytime soon.
See the rest of the Twitter discussion here.
