Link Sharing FAQ

When your website content is shared on Facebook, Messenger and other places, the Sharing Debugger helps you understand what type of information is used to create link previews. This document covers many of the more common questions developers ask while troubleshooting their links and working with the Open Graph metatags on their websites.

Problems with image

Images are cached asynchronously, so the image may not render the first time someone shares your content. You can avoid this by either:

The original image is no longer available, is too big or could not be fetched due to a temporary issue. Ensure the image URL is accessible to our crawler, is no bigger than 8mb and is served with less than a few seconds of latency.

When you change the og:image for a page, make sure that you do not remove the old image from your site, as then existing shares will show this white area.

Images smaller than 600 x 315 pixels but larger than 200 x 200 pixels will be rendered with a small, square image.

Many factors go into how an image may be cropped. For example, we try to center the image around faces that we can detect.

For large images, try to keep your images as close to 1.91:1 aspect ratio as possible to display the full image in News Feed without any cropping.

Page posts always use a large, landscape image for link shares. This is the same across desktop and mobile News Feed. Try to keep your images as close to 1.91:1 aspect ratio as possible to display the full image in News Feed without any cropping.

Your link may have been flagged by our content filtering system. If you believe this is in error, please submit a report on our Help Site; be sure to include the relevant URL.


Sharing Debugger Errors

All URLs must be absolute as they represent the canonical location of a resource (page/image), so that we can attribute shares and likes to the correct URL and cache images properly.

We freeze titles after a number of actions are taken against that object (described here: Updating URLs.


Updating URL and og:tags

All shares and likes are tied to a specific URL (what we call a Canonical URL). Changing the site structure to use new URLs with therefore begin attributing likes and shares to that new URL.

Please see Updating URLs for more information.

All shares and likes are tied to a specific URL (what we call a Canonical URL). Changing the site structure to use new URLs with therefore begin attributing likes and shares to that new URL.

Please see Updating URLs for more information.

The crawler will look for a AAAA record and return a response code 0 if it is not found. Ensure that your AAAA record is updated correctly when you change your URL or server.

Please see Updating URLs for more information.

We consider all image URLs immutable, since these are used to cache the resources at different layers, so if you need to replace an image, you need to also use a new URL. As the caches age, we will fetch the new image and the issue will fix itself.

If you are using a different URL but still seeing the old image, you can also go to the Sharing Debugger and rescrape the URL:

Changing og:title, og:image, etc. only applies to future shares of that link.

Once a person or page shares a link, no properties of that link attachment can be changed. This is to make sure that a site can't make it look like you shared something other than what you originally shared.

The only way to get a post with the link's new information is to delete the original post with the old link, force a rescrape of the URL with the Sharing Debugger, and create a new post with the link attached.


Facebook Developer Community Group

Get help from community members and Facebook staff.

If your question is not answered here, get help in the Facebook Developer Community group. The group is active with both our talented community members and also Facebook staff.