Whatsapp issue

Each service handles Open Graph tags how they want and there's only limited control we have to fix issues with one service over another. Yes, Whatsapp is owned by Facebook, but it's not always the case that if it works on Facebook or Instagram it will work on Whatsapp (or any combination of those 3).

Here are the suggestions I can provide:
* Make sure your website uses an SSL certificate
* Check that the og:image URL inserted is using https
* Try from different whatsapp apps (desktop, android and iOS) to see if the tags works anywhere
* Check your server security settings and logs. I'm unsure if whatsapp uses a different crawling bot from Facebook & Instagram, but make sure you don't have anything that would prevent their bot from crawling your site and fetching the tags

Beyond that, if you'd like us to take a look, feel free to use the Contact Us link at the top of the page and send us your URL. The only things we'd really look for are that the tags are properly inserted and that there's no egregious HTML formatting issues that may prevent the bot from properly parsing the site.

I hope that helps,
Alex

Actually.. I just looked at your Autotune history and looked at a website that starts with a 'q'.

On that site, there's a few possible issues I'd recommend looking at:
* The og:image tags are incorrect. They are using schemeless URLs (without the http or https) which is not recommended. I'd update the image tags to explicitly use https://
* There is something compressing and reformatting the HTML. I'd recommend disabling that, temporarily, to make sure that isn't inserting or re-ordering tags in a way that the crawlers don't like.

Please note that the crawlers only scan periodically and their results get cached, so changes you make may not have any effect for days. It's irritating as it's hard to know what works and doesn't, but that's how it works and necessary to know.

Thanks,
Alex

I just looked again and noticed another probably bad issue on the home page at least. If you open the source of the page, the og:description tag is at the end of the first line and looks like:I changed the text, but the formatting with lots of spaces and, what looks like javascript code, is a good overview of it.

JFBConnect does take the opening text of an article, try to strip some tags and format it properly. However, it's doing a terrible job there. You may want to try setting your own description tags in the content of specific pages to test as well with:You can put that directly in the article contents and JFBConnect will strip it out and use it properly. It gives more control of the description used when sharing and prevents some issues with the automation based on the actual content.

I hope that helps, again, but if you need anything else, just let us know!

Thanks,
Alex

JFBConnect will take the tags and insert them into the response of the page directly. Depending on where JCH Optimize is ordered in your system plugins, the 'optimization' may occur before JFBConnect does its work.

I'd recommend moving JCH Optimize to the last ordering position within the system plugin group. To do so, filter by System plugins, then click the up/down arrow and then drag JCH to the bottom of the list.

Beyond that, check that the {SCOpenGraph description=...} tag is all on one line. You should not have line breaks within the description you put there.

As for the repeated tags, that's ok to have them, as Facebook and other sources will use what they think is best. However, some of those do not look to be generated by JFBConnect at all. The image tags that are followed by og:image:height (or width) are not set by JFBConnect. We do not set the additional fields for images as they can cause parsing problems for some social networks. Most networks ignore those additional tags anyways as they'll just load the image and find the size automatically.

You may want to look at your template settings or other extensions to determine which may be setting the additional og:image tags or disable JFBConnect's og:image tags from being set to remove the duplicates.

I hope that helps,
Alex