Hello,
Thank you for contacting the support, and sorry for any inconvenience that might have been caused due to that.
I was able to see the og:image tag applied to your website. Can you please clear your website and browser cache and try testing your website again in Facebook’s Sharing Debugger? https://developers.facebook.com/tools/debug
Let us know how that goes. Looking forward to helping you on this one.
Thank you for your response. yes, i can see the og:image too which is why i’m so confused. Tried clearing website and browser cache, but i am still seeing the same issue in facebook debugger, even after asking FB to scrape the site again:
‘The ‘og:image’ property should be explicitly provided, even if a value can be inferred from other tags.’
Hello,
The issue you are facing might be occurring due to the Gzip compression option within your caching plugin, disable this option from your cache plugin to confirm.
After that, please also clear the cache.
This should fix the issue.
Hope that helps and please do not hesitate to let us know if you need our assistance with anything else.
Thank you. I disabled the shotpixle CDN cache that serves images. When I check the facebook debugger now I do see an image, but it is not the image that I set via rank math, nor the page featured image. The same error is displayed in the debugger still “The ‘og:image’ property should be explicitly provided, even if a value can be inferred from other tags.”
Instead of showing the current image, the debugger shows:
og:image https://healnavigator.com/wp-content/uploads/2018/09/nature-works-best.jpg
The right image shows in html inspection:
<meta property=”og:image” content=”https://healnavigator.com/wp-content/uploads/2022/01/heal_navigator_best_alternative_cancer_clinics_fb1.png”>
Hello,
I checked your website’s source and the og:image tag is applied properly. I was also unable to find any duplicate tags that might cause issues. The image is of almost recommended dimensions and of the supported type.
However, I tested with a few more tools and the image is not getting fetched.
HeyMeta.com’s result: https://www.heymeta.com/url/healnavigator.com
Linkedin’s Post Inspector tool: https://www.linkedin.com/post-inspector/inspect/https:%2F%2Fhealnavigator.com
Could you please replace the underscores in the image URL with dashes and see if that fixes the issue.
Looking forward to hearing back from you.
Thank you.
Thank you for your response. Tried replacing the file name as you suggested, but still no luck.
Facebook still selects a different, seemingly random, image.
Hello,
Could you please try to use an image of 1200px X 630px dimension?
After changing the image, clear the website cache and Scrape the URL with the Facebook Sharing debugger.
Let us know how it goes.
We are here to assist you.
hey. replaced it with 1200px X 630px , still no luck 🙁
Hello,
We might need to take a closer look at the settings. Please edit the first post on this ticket and include your WordPress & FTP logins in the designated Sensitive Data section.
Please do take a complete backup of your website before sharing the information with us.
It is completely secure and only our support staff has access to that section. If you want, you can use the below plugin to generate a temporary login URL to your website and share that with us instead:
https://wordpress.org/plugins/temporary-login-without-password/
You can use the above plugin in conjunction with the WP Security Audit Log to monitor what changes our staff might make on your website (if any):
https://wordpress.org/plugins/wp-security-audit-log/
We really look forward to helping you.
Hello,
I have updated the sensitive data as requested. Can you please check further?
Thank you.
Hello,
After further troubleshooting, I noticed that your image sometimes returned an access error as you can see in my screenshot in the Sensitive Data section.
It is possible that bots are seeing the same thing.
Please try to check this one with your hosting provider and see if they are able to help with this.
Looking forward to helping you on this one.
The access error is due to hot linking blocked. this shouldn’t be a problem with the FB scrapper. Please note that the image you linked above is the wrong image that FB is showing – and since they display it I don’t believe the hotlinking is the problem. To double check, i disabled the hotlinking blocked and tried rescrapping but still no luck. wrong image still showing.
Hello,
If you check what the Facebook scrapper sees, you’ll notice that the meta tags are all after the opening body tag.
The debugger only checks the meta tags inside the head tag and as such is ignoring the ones on your website because they are outside that tag.
Here’s what the scrapper is seeing: https://developers.facebook.com/tools/debug/echo/?q=https%3A%2F%2Fhealnavigator.com%2F
This is usually an issue on how the theme is set up and we recommend getting in touch with the theme provider and seeing if they have ever experienced this before.
Don’t hesitate to get in touch if you have any other questions.
Hello,
Since we did not hear back from you for 15 days, we are assuming that you found the solution. We are closing this support ticket.
If you still need assistance or any other help, please feel free to open a new support ticket, and we will be more than happy to assist.
Thank you.
