Facebook debugger (og metadata tester) reporting image problem
-
When I test a URL for an old blog post using the Facebook debugger (https://developers.facebook.com/tools/debug/) it claims “Provided og:image URL, https://mqgem.files.wordpress.com/2022/08/waves.jpg could not be processed as an image. It may be corrupted or may have an invalid format.”
However, there is nothing wrong with that image if you view it in your browser.
The blog post in question if you’d like to try it yourself is: https://mqgem.wordpress.com/2022/08/18/managing-notauth-type4-events/
This has happened for several older blog posts, but for a brand new post I wrote today (and added a new image to today) there is no such problem.
Are there issues with older images in a cache somewhere that needs to be refreshed or something?
The blog I need help with is: (visible only to logged in users)
-
I have heard from one of the other services seeing this problem that they are getting HTTP error 529 from WordPress – please can you look into this? My support request has been here for 4 days now with no response. Usually WordPress is a lot speedier at responding.
-
Is there anyone there? Can anyone tell me if there is a current issue with WordPress image serving giving out HTTP 529 errors?
-
Tried to edit my above reply to add this but when I try to edit it it refused to let me – says I can’t reply!
Anyway, just wanted to add that the blog post I saw this with before seems to work OK now, but this blog post doesn’t show the image https://mqgem.wordpress.com/2021/09/20/back-level-clients/ , doesn’t show the error either, so a bit weird, but the result is the same – picture is not served up to services using the metadata.
-
Hi there!
Thank you for reaching out. Here’s what’s happening: When you share a post on Facebook, Facebook scans the page for specific meta tags, known as Open Graph meta tags, to create a preview of the post. This preview typically includes an image, title, and description.
On WordPress.com, Jetpack generates these Open Graph meta tags for you automatically. To see what Facebook sees when it scans your posts, you can use the Facebook Debugger tool by entering one of your post URLs.
https://developers.facebook.com/tools/debug
Unfortunately, once this data is published on our end, we don’t have control over how Facebook scans or interprets it. From what we’ve gathered, this seems to be an intermittent issue that Facebook has been aware of for several months, as indicated by reports on their Meta Developers site.
We genuinely wish there were more we could do to resolve this for you, but ultimately, it’s an issue that Facebook needs to address on their end.
I hope this provides some clarity. If you have any further questions or need assistance with anything else, please don’t hesitate to let us know. We’re here to help.
-
Hi @staff-heroponriki Does Jetpack’s Social Previews in the Jetpack sidebar also display our post as it would appear on Facebook (and other social media)?
Posts are individual pieces of content on a blog. This guide will show you how to create and manage the posts on your site. Video Tutorial Video Transcript Welcome. In this video, we’ll take a look at posts, which are individual articles or other pieces of content that usually appear on the blog page of your site. To create a new post, click the “Right” button in the top toolbar,And, correct me if I’m wrong, but did we not at one point have minimum image sizes for each social media noted in this guide?
Connect your site to social media platforms and automatically share your posts to your connected accounts. This guide will show you how to share your posts on social media using Jetpack Social (formerly known as Publicize.) Set Up Jetpack Social To connect your site to your social networks, take the following steps: Visit your site’s dashboard. In the left side options, navigate to -
Hi Jen,
Does Jetpack’s Social Previews in the Jetpack sidebar also display our post as it would appear on Facebook (and other social media)?
Yes, but of course we do not control what Facebook does on their end, so the preview we share is based on what image you may have set in WordPress, such as your Featured image. But Facebook may pick a different image (they sometimes do this, even when their guidelines are followed) or there may be an error on their end that leads to a broken embed, which our preview would not be able to catch.
And, correct me if I’m wrong, but did we not at one point have minimum image sizes for each social media noted in this guide?
Yes, those can be found here:
When you share a post or page from your site on Facebook, Facebook selects a thumbnail image to display with your link. This page explains how to control the image shown on Facebook. Facebook Image Requirements To ensure Facebook recognizes the image you want displayed in Facebook feeds, make sure your image meets the following guidelines: Image dimensions: The minimum image size is 2Hope this helps!
-
Thank you @staff-totoro It might be helpful to link to those separate image guides from somewhere within https://wordpress.com/support/post-automatically-to-social-media/
-
Hi – thank you for your answer. Just to be clear, my question is not about how things look once they are posted on Facebook, they are about the fact that the Facebook debugger reports a bad image when the image is just fine. Also, it is not just Facebook that is seeing issues with images upon peeking at my blog posts, Buffer also sees them. They have told me that they get an HTTP 429 error at the times when the image can’t be obtained. I don’t know what the Facebook debugger sees as it doesn’t tell you the error it gets.
So is there anything you can do to sort out HTTP 429 errors seen (which may or may not be why Facebook debugger is having problems – seemed rather coincidental that both were having similar issues if they are not related). Can you whitelist Buffer so that they don’t see these? The requests would be being made with the HTTP header of “x-Bufferbot” I’m told.
Hoping you can help since no-one else thinks they can help either :-(
-
So we’re paying for Jetpack, Facebook Business and Twitter API and none of this works. Nice job everyone!!
- The topic ‘Facebook debugger (og metadata tester) reporting image problem’ is closed to new replies.
WordPress.com Forums 
