Post to Facebook with scheduled post

Hello @wireduk,

I’m sorry to hear about the trouble, but thanks for reaching out.

Could you post your site URL here, so I can have a look?
?
If you want it to remain private, you can also contact us via this contact form:
Contact Support. Thanks a lot!

Hi @erania-pinnera,

Site is: https://www.skeptic.org.uk/
And an example Facebook post is: https://www.facebook.com/theskepticmag/posts/10158400429014482

Thanks!

• This reply was modified 3 years, 6 months ago by wireduk.
• This reply was modified 3 years, 6 months ago by wireduk.

Hi @wireduk,

Thanks for sharing the post URL ??

Jetpack adds Open Graph tags to a blog’s posts when the Publicize module is active. Those OG tags can be found in the source by looking for
!-- Jetpack Open Graph Tags --.

I checked the page source for the post you linked, and I can’t see Jetpack’s Open Graph tags in the source, while I can see Yoast’s OG tags. Since Facebook will give an error if there are duplicate Open Graph tags, Jetpack automatically deactivates its Open Graph tag generation when it detects one of these plugins.

To fix that you have two options:

– use the Always Use Open Graph with Jetpack plugin, which has been created by one of our developers:
https://www.ads-software.com/plugins/always-use-jetpack-open-graph/

– deactivate Yoast to see if that helps

Let me know how you tried it out and how it went!

Thanks for that info @erania-pinnera. I’m still a little confused though. Because if I post the exact same message manually, it works fine?

Hello, there!

This is due to the difference in the way that Jetpack sends out content to social networks automatically through an API versus going to the actual social media site and just having it crawl your link to find out the end result of the OG tags after all conflicts have already been worked out.

Please let us know the results of this troubleshooting and we can go from there. Thanks!

If I install the “Always use Jetpack” plugin, it now gives me duplicate OG tags, I thought that was something we were trying to avoid?

Yes, we only want one set of OG tags, so if you’ve activated “Always use Jetpack” you should also disable the OG tags from Yoast, by going to SEO > Social > Facebook, and switching “Add Open Graph meta data” to “Disabled”.

Let us know if that helps at all.

OK, I’ve done that, will update when the next scheduled post goes out. Thanks!

Hello again. So we’ve had 2 scheduled posts go out now. The first one worked perfectly but the second one didn’t. Any more ideas?

Second post: https://www.facebook.com/theskepticmag/posts/10158409438259482

Hi there, is there anything else we can do?

Hi @wireduk

I see your latest post worked ok too.

As for the one that didn’t work, it’s hard for us to tell what caused that. All we know is that when Facebook’s bot first crawled the page on May 21 after it was published, it wasn’t able to find an image. It could be because the site was slow at the time and the image wasn’t able to be fetched by the Facebook bot in time, for example. Or it could be Facebook’s bot that was having issues.

For more information, you could look at the site’s raw access logs around the time that post was published. If you look at the user agents of the different sources that accessed the post right after publication, you’ll see a few accesses from facebook/ or facebookexternalhit/1.1 and you should be able to see if there were any errors associated with those requests.

Nothing weird in the logs. All requests were HTTP 200, but there is no request for the image file (as there are when the requests work fine)

I guess what is really confusing me is that if we edit the FB post immediately after, the image comes up fine. It’s certainly confusing. It even shows as fine in the FB sharing debugger.

Please let us know what happens with the next post and we can take a look from there.

One thing we might check is the filesize of the next post’s featured image – just to make sure it’s not so large that it is intermittently taking too long for Facebook to scrape it.