No Image or Desc using Publisize

When you share a post on Facebook, or when Jetpack Publicize publishes a post to your Facebook page, Facebook crawls the page and looks for Open Graph meta tags in the head to build a complete post preview (with an image, title, description, …).

Jetpack automatically creates these Open Graph Meta tags for you unless you already use another Open Graph plugin, in which case we let the other plugin handle things. Looking at your site, you seem to be using the Yoast SEO plugin to handle Open Graph Meta Tags.

The tags seem correct, but for some reason Facebook isn’t able to access your posts when it first tries to crawl them:

• https://i.wpne.ws/cDLU
• https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww.fanboynation.com%2Fmatt-ryan-to-appear-on-arrow-next-season-as-john-constantine%2F

That may happen when your posts’ first loading time is too slow. Since you use Jetpack’s Publicize module, Facebook is often among the first to visit a newly published post. If it takes too long to load that post, Facebook gives up and returns the error you can see above:

Error parsing input URL, no data was cached, or no data was scraped.

I’d suggest checking your site’s performance, especially the first time a page or post is loaded. It might be worth installing a caching plugin as well, as it may help with your site’s performance.

I hope this clarifies things a bit.

No it really doesn’t clarify things at all considering we use a cache program W3 Total Cache, we use cloudfare and our page speed using GTMetrix is around 90%. Like I said with those plugins in place it all worked like a champ until a few weeks ago

we use a cache program W3 Total Cache, we use cloudfare and our page speed using GTMetrix is around 90%.

Although your GTMetrix results are good, what matters in this case is the loading time of your posts right after they’ve been published, the first time they are accessed. That’s the key here: Facebook’s bot is the first to access your post after it’s been published, and as we can see by looking at Facebook’s Debugger, it can’t parse the URL. However, it has no problems parsing it later on, when you go to Facebook’s Debugger and force Facebook’s bot to do another pass and crawl the post again.

I’d consequently suggest looking at anything that may cause issues with loading time right after a post has been published. Caching can help, as I mentioned earlier, but it’s also worth looking at all the actions that automatically happen when you publish a post. It too many things happen at the same time, it may cause load issues on your server, thus causing the problem.

I hope this helps.

Actually the issue seems to be Yoast SEO. I have it on several sites that are having this problem and the second I deactivate it it works fine, turn it back on and its back to the issue we are having.