Does Google punish images hosted on Webflow?

Our site is dependant on the Google Image Search, although we created an image sitemap and all images are submitted, no image is indexed still. At first we thought the issue was with the background-images (no support for object-fit) we use entirely to embed our images, even for important ones that are content-relevant. The then submitted image-sitemap did not help very much (look at our search console screenshot).
The next things I would have tried would be to exclude our images from the Webflow Assets and to embed them on an own CDN/private webserver because maybe the Webflow Assets gained some sort of bad reputation or the obfuscated image names get somehow punished. The problem is, we cannot include external images with tags on Webflow.

Our main concern is that it takes just too long to show our images up on Google (search for brandengates select), even we have this site for at least an half year. Even if we had images of much higher quality or much more beautiful ones, it wouldn’t result in any benefit without the search results on the images tab.

Thank you for any help you can offer,
Calvin R.
Branden Gates Studios

https://www.brandengates-select.art/sitemap.xml
https://preview.webflow.com/preview/brandengates-select?preview=304cbbd5cb32a14492566bc1b47f2a25

2 Likes

Hi,

please let me know if someone has any idea :slight_smile:

I have the same question actually. I wonder if @brandengates or anyone else has figured this out? Webflow’s autogenerated sitemap doesn’t include images, which is already unhelpful.

There’s very little help when it comes to image SEO! Anyone making a portfolio or image-based website relies very heavily on image indexing. I’ve tried making my own sitemap that included images, but no amount of tweaking changes anything :confused:

Any help appreciated!

Any help or suggestion on this topic please

Hello @brandengates

The first thing I see is that all images you have are divs with background. I think Google can’t really index those properly. From what I know from Google’s point of view Images that are background are part of the design and images that use the tag are part of the content.

Change your images with the actual Image element.

Here’s something useful:

When to use <img />

  1. When Your Image needs to be indexed by search engine
  2. If it has a relation to content not to design.
  3. If your image is not too small ( not iconic images ).
  4. Images where you can add alt and title attribute.

When to use CSS background-image

  1. Images Purely Used to Design.
  2. No Relation With Content.
  3. Small Images which we can play with CSS3.
  4. Repeating Images ( In blog author icon , date icon will be repeated for each article etc.,).

Based on the list above and some observations we have these reasons to use an img tag:

  1. A logo image has semantic meaning and has relation to the content. So this is just the right thing to do from a semantical point of view.
  2. Google does not automatically index background images, otherwise the image search results would be filled with image sprites. Google hasn’t officially made a statement about this but it will most likely add more value to the div with an aria label, although an image will most likely still have more value. (Bing supposedly doesn’t do anything with this though)

Hope it helps

Piter

1 Like

For example here’s the logo

Add a link block with a class of logo (you’re already using this class) Remove the background image and add an image element inside of the link block.

If you’re using actual images you can put SEO description in the alt field

If you need more help let me know :blush:.

Piter

2 Likes