Hello, I hope you are fine
when i am sharing my link to social media my post images not showing in social media
Thank you!
Hi,
To share a post with a featured image, please follow this guide: https://forum.tagdiv.com/facebook-share/ use SEO Yoast (in this guide you will know how to display the og image using Yoast plugin).
Also, you can check your website links using this tool -> https://cards-dev.twitter.com/validator
-> https://developers.facebook.com/tools/debug/
Thank you!
Hi Anamaria, I appreciate your “stock” answer, but both of my Newspaper themed sites stopped showing the images yesterday. See https://www.facebook.com/TFCLiving/
Hello,
The problem is not caused by the theme, because as you mentioned, the issue appeared yesterday. However, I checked and found that even older posts no longer have a featured image, which means the problem is caused by Facebook -> https://i.imgur.com/EVcN3r5.png
Also, please check this topic
https://forum.tagdiv.com/topic/the-post-image-no-longer-appears-when-shared-to-facebook/
Thank you!
Theme does not control FB scraping images from your OG tags. If you look at the header for your posts, and you have proper OG (open graph) tags for FB to scrape, then that is how they grab stuff. Sometimes they have caching issues due to billions of images at a time. Sometimes the only way to get them to recapture image is go to your post on FB, click the little … or drop down for post and do “refresh share attachment.”
This is not new issue and happens from time to time with FB, as you should probably know by now. Not theme related. Theme does not control your featured image on server – if it’s readable by FB, then it’s an issue with FB showing a captured image not cached on their end properly.
As to ‘stock answers’ (I don’t work here), but TagDiv go out of their way to help folks and have for many many years, even when it’s nothing to do with their product.
This image issue is ONLY with my sites that use the Newspaper Theme. Our team has disabled all plugins, looked through every setting, etc. This problem IS SPECIFIC to the NEWSPAPER theme, and there are MANY reports of this issue from NEWSPAPER Theme users. As a web developer, the 100+ sites we have work just fine! Only the three NEWSPAPER THEME sites are giving us the Forbidden 403 error on social media for photos. The same social sites pages take images from other websites just fine. AGAIN, this is SPECIFIC TO NEWSPAPER THEME!
So, you can load the images in the browser? When you look at the page source for the posts, the link to your OG (open graph) featured image is correct, and in a public folder?
So, looking at this page:
https://www.texasforestcountryliving.com/event/cheers-with-the-chamber-angelina-county-4/
Your image is
<meta property="og:image" content="https://www.texasforestcountryliving.com/wp-content/uploads/2024/08/455641862_1043608027767687_8948949854303820277_n.jpg" />
This loads in browser so is public image. So, any issue on the side of FB is their issue and nothing to do with the theme.
It might be related to your URL where you have a -4 on the end which is not normal. That implies you have three prior stories with the same name and this is the 4th version and so might be considered stale/duplicate content and FB might skip if they have already captured a story with -1 -2 -3. Dunno.
Anyway. Good luck in sorting it. I’ve been using TagDiv themes on numerous sites since they launched, and the FB issue is always as I have described in my prior post, unless there is some technical issue on your site, like blocking FB, or the image is too large or the wrong format.
Cheers.
Thanks for the try – but that’s not it. The theme is not allowing the Facebook scraper to run. It sees the NEWSPAPER Themed sites as non existent – https://developers.facebook.com/tools/debug/?q=https%3A%2F%2Fwww.texasforestcountryliving.com
This is what Facebook is seeing –
<!DOCTYPE HTML PUBLIC “-//IETF//DTD HTML 2.0//EN”>
<html>
<head>
<meta http-equiv=”content-type” content=”text/html; charset=utf-8″>
<title>403 Forbidden</title>
</head>
<body>
<h1>Forbidden</h1>
<p>You don’t have permission to access this resource.</p>
<p>Additionally, a 403 Forbidden
error was encountered while trying to use an ErrorDocument to handle the request.</p>
</body>
</html>
The Robots file returns this message with Yoast –
# START YOAST BLOCK
# —————————
User-agent: *
Disallow:
Sitemap: https://www.texasforestcountryliving.com/sitemap_index.xml
# —————————
# END YOAST BLOCK
Without Yoast –
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Sitemap: https://www.texasforestcountryliving.com/sitemap_index.xml
We have checked all of our .htaccess files for code that would block.
We have disabled every plugin. Rolled back one version of Newspaper Theme. We have totally reloaded WordPress.
We have changed themes, and posting works just fine!
The only thing in common with this is our three sites with something in the NEWSPAPER Theme code blocking robots/scrapers.
If it were me, I’d probably overwrite the theme and tagdiv composer with updated copy of the Newspaper theme, and do it via FTP not zip upload.
Sorry – not sure how that is happening. Would drive me nuts too 🙂
Still an issue on both of our sites that use the newspaper theme. Works fine with other themes. Newspaper Theme is the only commonality in both of these websites. Yes, you say it is a Facebook issues. But Facebook engineers says the THEME is actually blocking their scraper. He would not give me the details. We run 40 other websites on the server that have no issues. Of those that have posted this issue in the past, none have found a solution.
we do not have this issue on our sites
Hello,
@msgpr You can test our prebuilt website to check because on the demos this issue doesn’t appear -> https://prnt.sc/1gg-0gQKQGUy -> https://prnt.sc/p6TqHCGn4ctd -> https://prnt.sc/x5s0HJSKgCbm -> https://prnt.sc/-VJ6aCa-MMcT
Thank you!
Good day.
Have you resolved your issue? I have a similar one…
Hi malmed_wp, can you please let me know some details about the problems you are facing? Do you have problems sharing articles on Facebook?
Description of the problem with image display on Facebook
When sharing content from the Malyn.Media website on Facebook, the main image of the post sometimes does not appear.
Problem details:
Occurs selectively: under the same conditions, some posts display the image while others do not.
The issue affects both new publications and previously published ones (where the image used to appear but later disappeared).
The site runs on WordPress and uses the Yoast SEO plugin.
Sometimes, in the desktop version of Facebook, the image is displayed, but in the mobile version it is not. The debugger does not help — it returns code 200, but the image is still missing. I have observed a similar issue on another website using the same template.
Hello,
What I recommend is to ensure that you have an original image. Also you can use this tool https://developers.facebook.com/tools/debug/
https://forum.tagdiv.com/facebook-share/
https://developers.facebook.com/docs/sharing/webmasters/images/
Thank you!
All the tools fail to give a reliable result. The Facebook debugger can display the image without errors, and Yoast also shows the image correctly in its settings. However, when you share the post on a Facebook page, the image may be missing. We try to solve the problem by reposting several times, clearing the cache, waiting, and trying again. It’s exhausting.
The image size is correct, and all attributes are set. It’s still hard to see a clear pattern, but it’s obvious that this issue appears with the Newspaper theme — I’ve seen similar cases on other sites.
The author of that discussion confirms this as well. That’s why I wanted to ask him again whether he found a solution.
Hi,
The theme is not interfering with the image, and if an extra plugin is used and the og: image is added, it should be working correctly. The image was displayed in the Facebook debugger without displaying any error or warning? – https://www.youtube.com/watch?v=MTN-x3xKK78
Thank you!
It seems to be a problem with Yoast.
Hi malmed_wp, we hope that the next Yoast update will fix this problem.
