Hi Ed,

I suspect the reason why the image it get for the xml image without the http: is because the image was get from background image (which is this will happen if you enable the cropping of the image-use for image responsive).
I've disable the image cropping for this module, can you try it again http://take.ms/n5xKt ?
By the way, it is possible for you give us some screenshot of errors that has been reported by google?

As you can see, the blog is not adding the image url correctly to the page, cutting off the http and starting the image url with //www. This is very bad for imagemap and SEO. Can you please tell me how to fix this?

Hey Ed,

What you have shown is only the errors within JSitemap and it shouldn't have any errors at all on Google because their crawlers and web browsers are aware of protocol relative urls which is based on RFC986, https://tools.ietf.org/html/rfc3986

You can read more about it from, https://webmasters.stackexchange.com/questions/77246/how-do-search-engines-handle-protocol-relative-links

Why is EasyBlog not adding https:// to the image as it should? I have never seen a link start with //www? This is not a sitemap issue, easyblog is not generating the link correctly and Google Webmaster Tools is proving it. I need to have https added to the front of //www to get rid of these errors.

Why is EasyBlog not adding https:// to the image as it should? I have never seen a link start with //www? This is not a sitemap issue, easyblog is not generating the link correctly and Google Webmaster Tools is proving it. I need to have https added to the front of //www to get rid of these errors.

Firstly, i would like to clarify that you never seen a link start with //www or //site.com without protocol before, it doesn't mean that other domain webpage didn't use this method Protocol Relative URLs to populate their link on the site.

The reason why we use this method Protocol Relative URLs to populate image is because we do not want to store these protocol with the link from the blog content into database to prevent this following issue.

All these will caused these following warning on the site and affected with the SEO as well.

“This page contains both secure and nonsecure items” or “This page has insecure content.”. This happens when we are viewing a HTTPS site and some content on the site is loaded from HTTP.

This warning message is very common, when someone try to view a site let said https://www.mysite.com and we get this above warning message, that means some of the content (link) on the site is getting loaded from a non https site, like http://www.oneoftheexample.com.

These warning messages can be fixed by using protocol relative URLs.

Imagine if the page content having this following code to populate one of the image under this domain site https://example.com.
[gist type="php"]
<img src="//http://www.site.org/images/example.jpg" />
[/gist]
So this image link will automatically convert to use https:// (https://www.site.org/images/example.jpg) to populate this image on the site without hitting any warning message as what i described at above.

Imagine if the page content hardcoded that image link on this domain site https://example.com.
[gist type="php"]
<img src="http://www.site.org/images/example.jpg" />
[/gist]
So this image link unable to automatically convert this http to https, so it will caused this warning message.

By the way, regarding with your current issue, Google Webmaster tool shouldn't return you any warning message regarding this if you re-submit again with your sitemap. Because if you access this sitemap link again :
[gist type="php"]
https://www.deermeadowshomehealth.org/index.php?option=com_jmap&view=sitemap&format=images&xslt=1
[/gist]
You no longer see any image link without protocol now is because my colleague Fadhli already help you turn off that 'Cropping image' setting from that Easyblog latest blog post module, so it will populate those image link on the page using img tag instead of use CSS background: url(//site.com/images/example.jpg).

By the way, keep us update if Google webmaster tool still return you those error after you re-submit your sitemap.

Ok, thanks. I also have an issue with easyblog giving me pagespeed 404 errors internally. I contact siteground support and they think it's something in easyblog. is there a setting to shut off pagespeed?

Hey Ed,

May I know what errors are you getting on Pagespeed? We have Pagespeed running on our site too but did not encounter any issues.

Hey, so I figured out what the issue was. Siteground removed pagespeed from its servers for good. So easyblog was looking for the .pagespeed images, which had reverted back to the regular urls, I must have installed easyblog and uploaded the images when pagespeed was active.

So, when pagespeed got removed, the sh404sef was looking for the .pagespeed urls, but they were gone. I had to go through every easyblog post and remove all the images, then re-add them so the correct urls were there. Just letting you know for future reference. The images showed correctly on the front end,somehow, but the backend, when you looked in to each post, the images were showing as broken. very weird.

Also, how can I take - EASYBLOG out of the posts to facebook etc. THis started happening after the recent software update.

Hey Ed,

Ah I see. Thanks for the input on this. By the way, I am just wondering why would Siteground be removing Pagespeed eh? It's much better for sites.

To disable auto posting to Facebook, you can do so under EasyBlog > Auto Posting > Facebook, http://take.ms/OZapl

I have disabled auto posting, but when a blog gets posted to facebook it has "- EasyBlog" attached to the Blog Post Title. Is there a place to disable this? Sorry, just started really getting into learning about this blog, sorry for all the requests.

Hey Ed,

No worries at all, and this is what you have paid for, which is our support By the way, it is most likely that Facebook is caching the "title" of your blog and this is why you are still seeing "- EasyBlog" in the title of the post.

I tried to place one of the latest post into Facebook's debugger tool, but I don't seem to see the "EasyBlog" prefix on the link, http://take.ms/WLAuE

May I know which post is showing up with "EasyBlog"?

Hello, Can you please tell me the correct setting for jsitemap in order to have the blog show up correctly in the sitemap? I know you are no affiliated with that software but I figured you may know. Thanks.

Are you referring those Easyblog image link without protocol from the sitemap page?

If yes, I've help you add this https: from your JSitemap configuration setting 'CDN images protocol', it seems it did a tricky, it should populate for all the image link on your sitemap page.

But currently I am not really sure if that is the correct configured, perhaps you can consult with this JSitemap support and see how it goes?

You can ask them something like this :

1. Easyblog generated those image link without protocol e.g. //http://www.deermeadowshomehealth.org/images/easyblog_articles/122/b2ap3_small_godshall1.jpg

2. Then sitemap didn't append those protocol into image link when sitemap crawl Easyblog page so caused Google webmaster tool return those warning error.

3. After that, you added https: from this 'CDN images protocol' from JSitemap setting, it seems like every link seems generated correctly into sitemap page, is it the correct setting i set?