Facebook Share Image or Property Info Does Not Show on the First Share
In some cases, Facebook may not show the correct property title, description, or image the first time a property link is shared.
This usually happens when Facebook has not yet scraped the page, when Facebook has cached old information, or when the Meta/Facebook crawler cannot access the page correctly from your server.
This is not always a theme issue. Facebook reads the page using Open Graph metadata and stores a cached version of that information for future shares.
How to Test the Property Link
Go to the Facebook Sharing Debugger:
https://developers.facebook.com/tools/debug/sharing
Paste the property page URL and click Debug.
If Facebook cannot read the page correctly, you may see an error similar to:
Error parsing input URL, no data was cached, or no data was scraped.
This means Facebook could not scrape the page information at that moment.
How to Force Facebook to Read the Page Again
After debugging the URL, click the Scrape Again button.
This asks Facebook to fetch the page again and refresh the cached Open Graph information.
If the first scrape does not show the correct image or text, click Scrape Again one more time and check the preview again.
When This Can Happen
This can happen for several reasons:
- Facebook has not scraped the property page before.
- Facebook cached old information for that URL.
- The property image was changed after Facebook already cached the page.
- The server, firewall, CDN, or security plugin blocks the Meta/Facebook crawler.
- The page is temporarily slow or unavailable when Facebook tries to read it.
- The Open Graph image is too large, missing, blocked, or not accessible directly.
- The website cache serves old metadata to Facebook.
Recommended Steps
- Open the Facebook Sharing Debugger.
- Paste the property page URL.
- Click Debug.
- Check the warnings and the link preview.
- Click Scrape Again.
- If needed, click Scrape Again a second time.
- Check if the correct title, description, and image are displayed in the debugger preview.
If Facebook Still Cannot Scrape the Page
If the debugger still shows an error, please check the following:
- Make sure the property page is public and not password protected.
- Make sure the property page URL opens correctly in an incognito browser window.
- Clear your website cache, server cache, and CDN cache if used.
- Check if a security plugin or firewall blocks external bots or crawlers.
- Ask your hosting provider if Meta/Facebook crawlers are allowed to access your website.
- Make sure the property featured image is accessible directly by URL.
- Make sure the image URL is not blocked by hotlink protection, CDN rules, or server restrictions.
Important Note About Caching
Facebook stores the information it reads from your page. If you change the property title, description, or image after the page was already shared, Facebook may continue showing the old cached version.
Using the Scrape Again button forces Facebook to refresh the cached information for that URL.
Before Sharing a New Property Link
For best results, you can pre-cache the property page before sharing it on Facebook:
- Publish or update the property page.
- Clear website and CDN cache.
- Open the property URL in the Facebook Sharing Debugger.
- Click Debug.
- Click Scrape Again.
- Confirm that the correct preview is shown.
- Then share the link on Facebook.
Final Note
If Facebook cannot scrape the page even after using the debugger, the issue is usually related to server access, firewall/CDN rules, page availability, image accessibility, or cached metadata.
In this case, please ask your hosting provider to verify that Meta/Facebook crawlers can access the property page and the property image URL.
