Google Not Indexing XML Sitemap Images

[edlondon]

Thought I had them on email but must be within our fairly cumbersome Skype thread... let me have a dig through when I get chance and I'll post them up here.

[edlondon]

Found one of the sites with the same Cloudinary URLs with commas - apartable.com

See Google image results: https://www.google.co.uk/search?q=site:apartable.com&tbm=isch

Their images appear to be well indexed.  One thing I have noticed, however, is that we often have .jpg twice in the image URL.  E.g.:

• http://res.cloudinary.com/greenplantswap/image/upload/c_crop,g_north,h_0.9,w_1.0/c_fill,d_no_image_icon-720x720**.jpg**,g_center,h_900,q_80,w_900/v1352574983/oyfos82vwvmxdx91hxaw**.jpg**
• http://res.cloudinary.com/greenplantswap/image/upload/c_crop,g_north,h_0.9,w_1.0/c_fill,d_no_image_icon-720x720**.jpg**,g_center,h_900,q_80,w_900/v1352574989/s09cv3krfn7gbyvw3r2y**.jpg**
• http://res.cloudinary.com/greenplantswap/image/upload/c_crop,g_north,h_0.9,w_1.0/c_fill,d_no_image_icon-720x720**.jpg**,g_center,h_407,q_80,w_407/v1352575010/rl7cl4xi0timza1sgzxj**.jpg**

Wonder if that is confusing Google?  If so, none of this is consistent, as they do have a few images indexed with exactly the same kind of URL as those listed above.

[FedeEinhorn]

Hmmm I step off here, never used cloudinary.com or even heard of them. I personally use NetDNA, with pull zones (which means that they load the image/css/js from your origin and store a version on their servers) while handling cropping/resizing from my own end (via PHP and then loading that image, example: http://cdn.fulltraffic.net/blog/thumb/58x58/youtube-video-xQmQeKU25zg.jpg try changing the 58x58 to another size and my server will handle the crop/resize while NetDNA will serve it and store for future loads).

[Everett]

Hello Edlondon,

I think you're probably answering your own question here. Google typically doesn't have any problem indexing images served from a CDN. However, I've seen Google have problems with commas in the URL at times. Typically it happens when other elements in the URL are also troublesome, such as your double file extension.

Are you able to rename the files to get rid of the superfluous .jpg extension? If so, I'd recommend trying it out on a few dozen images. We could come up with a lot of hypothesis, but that would be the one I'd test first.

[edlondon]

Thanks for the responses guys, much appreciated.

In terms of the commas, that was something that I put to the developer, however he was able to come back with examples where this has clearly not been an issue - e.g. apartable.com have commas in their URLs and use the same CDN (Coudinary).

However, I agree with you that double file extension could be the issue.  I may have to wait until next week to find out as the developer is working on another project, but will post the outcome here once I know.

Thank you again for the help!

[mattbeswick]

Ignore the developer - what worked for one doesn't mean it'll work for you

The easiest way to test this is to manually create a sitemap with 100 or so 'clean' image URLs. Just pull the messy ones into excel and use the formula below to create a clean version (Use A1 for messy, B1 for formula).

Good luck mate.

=CONCATENATE("image:imageimage:lochttp://res.cloudinary.com/greenplantswap/image/upload/",RIGHT(A1,LEN(A1)-(FIND("*",(SUBSTITUTE(A1,"/","*",(IF(LEN(TRIM(A1))=0,0,LEN(TRIM(A1))-LEN(SUBSTITUTE(A1,"/",""))))))))),"</image:loc></image:image>")

[edlondon]

Cheers for that mate - especially the useful Excel formula.

I am going to try a few things in isolation so that we can accurately say which element/s caused the issue.

Thanks again, mate.

[Everett]

It isn't always that simple. Maybe commas don't present a problem on their own. Maybe double file extensions don't present a problem on their own. Maybe a CDN doesn't present a problem on its own. Maybe very long, complicated URLs don't present a problem on their own.

You have all of these. Together, in any combination, they could make indexation of your images a problem for Google.

Just test it out on a few. Get rid of the file extension. If that doesn't work, get rid of the comma. That is all you can do. Start with whatever is easiest for the developer to implement, and test it out on a few before rolling it out across all of your images.

[edlondon]

Thanks Everett - that's exactly what I intend to do.

We will be testing two new sitemaps with 100 x URLs each. 1. With just the file extension removed and 2. With the entire cropping part of the URL removed, as suggested by Matt.

Will be interested to see whether just one or both of the sitemaps are successful.  Will of course post the outcome here, for anyone who might have this problem in future.

[bogdan_c]

Hi Mark,

I'm just following the thread as I have a similar problem. Would you mind sharing your results from the tests?

Thanks,
Bogdan