I recently stated a huge difference between the traffic monitored in the Search Console and what I could find in the log files using Kelogs log analyzer. My first hypothesis is that Google Image could be at the origin of this difference, with a preload in background. Second hypothesis is that the first results in Google Web is preloaded if the page is usually too slow.
Protocol to check the first hypothesis:
I’ll try to get the image below indexed for this website, despite it is hosted on amazon, and I will live check the impact on log files when I search for it in Google.
Let’s come back in few days when Googlebot will have indexed this page and display the image in Google Image (I’ll use “site:quentinadt.com” to check it).
So here is the picture of someone swimming:
To check the second hypothesis, Ill make a page which is very slow but ranks on a specific unique keyword.
In this post, there is a background image. It is the picture of my 3 years old Macbook Pro 2016 which is already dying… The screen is sometimes not usable, and most of the time there is just one line, vertical.
The idea is to check if either of not Google will index an image which is accessible only from a background CSS call.
John Muller, from Google, in 2018:
And as far as I know we don’t use CSS images at all for image search.
If you’ve read my last blog post, you will see that it didn’t help to use the title of an image to rank in the SERPs.
So I decided to push the test a little bit further, until I manage to get the image indexed.
So here is the picture of a very rare – endemic – fish that you can found only in Croatian rivers. I’m note passionate about fish, but I thought it’s an ok picture for testing the ranking capacities of the title element.
So again, I’ve added a title, but this time, it contains what most probably is the name of this endemic fish.