Facebook Link Preview Not Showing? 8 Causes and Fixes

Why Facebook shows a bare link, a blank image or an old card, how to fix each cause with the Sharing Debugger, and what changes for scheduled posts.

A Facebook Page post with a bare link next to the same post with a large preview card, image, domain and title

Guide · By PostBoost team · · Markdown

Short answer: Facebook builds a link card from the Open Graph tags in the page's <head>, mainly og:title, og:description, og:image and og:url, and keeps a copy of what it read. When the card is missing, blank or out of date, check eight things: no og:image, a relative image URL, an image Facebook hasn't fetched yet, an image it can't fetch, an image that is too small, a redirect, tags it can't read, or an old copy. Paste the link into the free link preview checker to see what your page says now, fix it, then press Scrape Again in Meta's Sharing Debugger so Facebook reads the page again.

Unlike LinkedIn, Facebook reads the page itself even when a scheduler or the API publishes the post. So the Sharing Debugger helps with scheduled posts too, as long as you use it before the post goes out. More on that below.

What Facebook needs to build the card

Meta lists og:url, og:title, og:description, og:image and fb:app_id as the basic tags (Meta). Add og:image:width and og:image:height too: Meta says they let the crawler render the image "without having to asynchronously download and process it" (Meta best practices).

<meta property="og:url" content="https://example.com/blog/link-preview" />
<meta property="og:title" content="Facebook link preview not showing? 8 fixes" />
<meta property="og:description" content="Why the card is missing and how to fix it." />
<meta property="og:image" content="https://example.com/og/link-preview.jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
rule value source
recommended image size at least 1200 × 630 px Meta, images in link shares
large card at least 600 × 315 px; smaller images show much smaller Meta, images in link shares
minimum image size 200 × 200 px Meta, images in link shares
ratio as close to 1.91:1 as possible, to avoid cropping Meta, images in link shares
image file size 8 MB at most Meta, images in link shares
URLs in og:url and og:image absolute, not relative Meta, link sharing FAQ
where the tags sit within the first 1 MB of the page Meta, web crawlers
automatic refresh about every 30 days Meta, changing link data

Meta documents no character limit for the card title or description. Around 60 characters for the title and 160 for the description keeps both readable on a phone.

The 8 causes, in the order to check them

Run the link through the link preview checker first. It loads the page once, the way a preview crawler does, lists the tags it found, draws the Facebook card and writes a warning for most of the problems below. The Facebook link preview checker shows only the Facebook card, with Meta's tag, og:url and image size checks. Then paste the same URL into the Sharing Debugger: the checker shows what your page says now, the debugger shows what Facebook has stored.

  1. No og:image. Facebook has nothing to put in the card, so the post shows a card without a proper image. The checker says "No og:image: most networks show a small or text-only card." Add the tag in the page template so every page gets one.
  2. A relative image URL. /og/post.jpg works in a browser but not in the tag. Meta's FAQ is blunt: "All URLs must be absolute." Write https://example.com/og/post.jpg. The checker flags this as "og:image is a relative URL".
  3. The image isn't fetched yet. "Images are cached asynchronously, so the image may not render the first time someone shares your content," says Meta's FAQ. That is why a brand-new page often goes out without its image. Add og:image:width and og:image:height, and run the URL through the Sharing Debugger once before anyone shares it.
  4. An image Facebook can't fetch. A white box where the image should be means "the original image is no longer available, is too big or could not be fetched due to a temporary issue" (Meta FAQ). Open the image URL in a private window, keep it under 8 MB, and check that your firewall or bot protection doesn't block Facebook's crawler, which identifies itself as facebookexternalhit/1.1 (Meta web crawlers).
  5. An image that is too small or the wrong shape. Meta's FAQ says images between 200 × 200 and 600 × 315 render "with a small, square image", and also that "Page posts always use a large, landscape image for link shares." An image far from 1.91:1 gets cropped. A 1200 × 630 image looks right in both cases. The checker reads the image size and warns below 1200 × 630; the image size guide has the sizes for every network.
  6. A redirect or a different og:url. Facebook treats og:url as the page's canonical address, and all shares and likes are tied to it. When og:url points to another address, the crawler follows it, and "the sharing details that Facebook uses are the ones at the final link in the redirect chain" (Meta, versioned links). A short link, an http:// to https:// hop or a tracking redirect can land the crawler on a page with other tags. The checker lists every redirect and warns when the canonical URL differs. If you add UTM parameters with the UTM builder, check that the tagged URL returns the same page.
  7. Tags Facebook can't read. Preview crawlers read the HTML your server sends. Tags written by JavaScript after the page loads are invisible to them. So are tags after the first 1 MB of the page, and pages that don't respond "within a few seconds" (Meta web crawlers). If the checker finds no tags but your browser's inspector does, render them on the server and move them to the top of <head>.
  8. An old copy. Facebook refreshes link data on its own roughly every 30 days (Meta, changing link data). Images are cached by their URL, so if you replace og.jpg with a new file under the same name, Facebook keeps showing the old one: give the new image a new URL.

One more case: if the debugger shows no preview at all and the link can't be shared, Meta's FAQ says "your link may have been flagged by our content filtering system". The tags are not the problem then.

How to use the Sharing Debugger

  1. Open developers.facebook.com/tools/debug and log in with your Facebook account.
  2. Paste the full URL and press Debug. The debugger shows the card Facebook would build, the tags it found and any warnings.
  3. Fix what it reports on your site, then press Scrape Again. Repeat until the card shows your image and title (HubSpot).

For many URLs at once, Meta's docs describe the same refresh as a Graph API call: POST /?id={url}&scrape=true with the URL percent-encoded.

Posts that are already live

A fresh scrape changes future shares, not old ones. Meta's FAQ: "Changing og:title, og:image, etc. only applies to future shares of that link." It mentions a Refresh share attachment option in the post's menu for an existing share; if your post doesn't offer it, delete the post and share the link again. The title is the exception: Facebook freezes it once the link has more than 50 interactions (comments, likes, shares). The image and description can change at any time.

Scheduled posts: Facebook still reads the page

LinkedIn makes apps send the card themselves, so its Post Inspector can't fix a scheduled post (see why LinkedIn link previews break). Facebook works the other way. When PostBoost publishes a link post to a Facebook Page, it sends the link in the Graph API link field and nothing else about the card. Facebook builds the card from its own copy of your Open Graph tags, the same as when you paste the link yourself (Graph API Page feed).

That gives scheduled posts two rules:

  • Scrape before the scheduled time. Fixing the tags is not enough while Facebook still holds an old copy. Press Scrape Again in the debugger after the fix and before the post goes out, and for a new page, at least once so the image is already fetched (cause 3).
  • Keep the page reachable. If Facebook holds no copy of the URL yet, it reads the page when the post goes out, and a page that is down, behind a login or blocking bots then gives it nothing to read. Scraping beforehand covers this too.

How PostBoost builds the Facebook card

  1. In the PostBoost editor, write the post and paste the full link, starting with https://. The first link in the text becomes the card.
  2. Leave the post without images or video. With media attached, Facebook publishes a photo or video post and the link stays in the text without a card.
  3. Check the Facebook preview in the editor. PostBoost reads the page and draws the card with its image, domain and title. This is PostBoost's own read of your page as it is now, not Facebook's stored copy. If the editor shows the new image and the debugger shows the old one, press Scrape Again.
  4. Schedule the post. When it goes out, Facebook builds the card from what it has stored for that URL.

Sending a link post through the API

Through the REST API, a content item's url field is the link card. If you leave url out and attach no media, PostBoost uses the first http(s) link in body, the same as the editor. Sending it yourself makes the choice explicit when the text holds more than one link:

curl -s -X POST "https://postboost.co/app/api/$WORKSPACE_UUID/posts" \
  -H "Authorization: Bearer $POSTBOOST_API_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "accounts": [21],
    "schedule": true,
    "date": "2026-10-30",
    "time": "15:00",
    "timezone": "Europe/London",
    "versions": [{
      "account_id": 0,
      "is_original": true,
      "content": [{
        "body": "Our Facebook previews kept showing last month'\''s image. Here is the fix: https://example.com/blog/link-preview",
        "url": "https://example.com/blog/link-preview",
        "media": []
      }]
    }]
  }'

Find the Facebook Page's account id with GET /{workspaceUuid}/accounts. Leave media empty, or Facebook gets a photo post instead of a link card.

  • og:url, og:title, og:description and og:image are in the HTML the server sends, near the top of <head>.
  • og:image is an absolute https:// URL, 1200 × 630 or larger, under 8 MB, with og:image:width and og:image:height set.
  • A changed image has a new file URL, not the old name.
  • The link you share is the final URL, and og:url points to itself.
  • The link preview checker shows the Facebook card with your image and no warnings.
  • The Sharing Debugger shows the same card after Scrape Again.
  • For scheduled posts: no media attached, the link starts with https://, and the page will be online at the scheduled time.

If a scheduled post didn't go out at all, that's a different problem: see why scheduled posts fail to publish.

Do this in PostBoost

Free tools for this guide

FAQ

Why is my Facebook link preview not showing?

Usually the page has no og:image (or a relative one), the image can't be fetched or is over 8 MB, the link redirects to a page with other tags, or Facebook still holds an older copy of the page. Run the URL through a link preview checker to find the cause, fix the tags, then press Scrape Again in Meta's Sharing Debugger.

How do I refresh a Facebook link preview?

Open the Sharing Debugger at developers.facebook.com/tools/debug, paste the URL, press Debug, then Scrape Again. Facebook reads the page again and new shares get the new card. Without that, Facebook refreshes its copy on its own about every 30 days.

What size should a Facebook link preview image be?

Meta recommends at least 1200 x 630 pixels, as close to 1.91:1 as possible, and no more than 8 MB. Images under 600 x 315 show much smaller, and the minimum Facebook accepts is 200 x 200. Use an absolute https:// URL and add og:image:width and og:image:height.

Why does my link preview show no image the first time I share it?

Facebook fetches images in the background, so the very first share of a new URL can go out without the image. Add og:image:width and og:image:height and run the URL through the Sharing Debugger before you share or schedule it, so the image is already fetched.

Can I change the preview of a Facebook post that is already published?

New tags only apply to future shares. Meta's FAQ describes a Refresh share attachment option in the post's menu that updates an existing share; if it isn't there, delete the post and share the link again. The title can't change once the link has more than 50 interactions.

Why does my scheduled Facebook post have no link preview?

In PostBoost a Facebook post gets a link card when its text contains a full https:// link and no image or video is attached. With media attached, Facebook publishes a photo or video post and the link stays plain text. Facebook reads the page itself when the post goes out, so fix the tags and press Scrape Again before the scheduled time.

Sources

Related guides

Try PostBoost free

API, webhooks and MCP on every plan, including Free. No credit card required.