Hi @peoniesforspring1 ,
Thank you for reaching out to us.
Facebook is actually quite picky about images. They generally prefer images that are 1200 pixels wide by 630 pixels tall, and they only accept standard formats like JPEG, PNG, or GIF. They do not support SVG files or any image smaller than 200 pixels by 200 pixels.
We’ve also covered this in our documentation:
https://aioseo.com/docs/setting-a-default-image-for-facebook/
Since the Debugger is seeing an SVG, it sounds like AIOSEO might be falling back to a default setting (like a site logo) because it is having trouble detecting or processing your Featured Image right now. You can also review your default Facebook image settings here: https://aioseo.com/docs/setting-a-default-image-for-facebook/#setting-the-default-facebook-image
Could you please share the URL of the specific post or page where you are seeing this issue?
Once I have that link, I can inspect the page source to see exactly which image tag AIOSEO is generating and help you get your previews back to normal.
Thanks.
Thanks for the quick response.
This issue only started immediately after updating the AIOSEO plugin. Before the update, Facebook was correctly pulling the featured image for each post with these same settings.
Now the Debugger only sees an SVG as the og:image, even though every post has a proper featured image in JPG/PNG format. Nothing else on my site changed except the plugin update.
Is there a form I can share the post link privately here?
Hi @peoniesforspring1 ,
Thank you for your follow-up!
Could you please confirm if you are using Hostinger hosting?
What we’re currently seeing suggests that Facebook appears to be rate-limiting servers, specifically impacting Hostinger servers in some cases. This can cause Facebook’s crawler to fail intermittently when attempting to access your site’s OpenGraph data, resulting in blank previews or missing images, as you’re experiencing.
This doesn’t seem to be an isolated incident. There’s an ongoing discussion within the Facebook developer community that points to similar experiences from other users, suggesting a broader issue on Facebook’s side regarding crawling or rate limiting. You can find more details and follow the discussion here: https://developers.facebook.com/community/threads/1282981940366598/
As this appears to be a crawling or rate-limiting issue originating from Facebook and potentially affecting hosting providers like Hostinger, there is unfortunately nothing actionable within AIOSEO to resolve it directly. We recommend monitoring the situation. If the problem persists, you may want to contact Hostinger support regarding Facebook’s interaction with their servers.
However, if you are not using Hostinger and require further assistance, please get in touch with us directly via our free Basic Question form here so we can investigate further:
https://aioseo.com/contact/
Thanks!
Indeed, it is Hostinger. Thanks for the clarification and help.