Why doesn’t my website show a preview image when I share the link?

01 · Understand the handoff

The sharing platform builds the card from page metadata

LinkedIn says its share box relies on oEmbed and/or Open Graph metadata to retrieve an accurate title, description, and image. The page’s visible hero image is not automatically the link preview. The service usually reads machine-readable tags in the document head.

The Open Graph protocol defines four basic properties: og:title, og:type, og:image, and og:url. A useful implementation also supplies a concise description and image dimensions. These tags describe the shared object; they do not guarantee that every platform will render an identical card.

02 · Check the complete set

A polished card needs four accurate parts

1. Title: a specific description of the destination, not a stuffed list of keywords.
2. Description: a brief reason the right person would open the page.
3. Canonical URL: the stable public address represented by the card.
4. Image: an absolute, public image URL that returns a real supported file.

Page-specific metadata matters. If every article inherits the homepage title and image, the cards become indistinguishable. If a route overrides the Open Graph object but omits its image, the result can vary by framework and platform. Inspect the rendered production HTML rather than assuming a template or CMS field created the expected tags.

Use one canonical host consistently. Mixing www and non-www addresses can create separate cache entries or fail when one hostname is not configured. Redirects should resolve predictably, but the declared URL and image should point to the final public destination.

03 · Design for the card

Choose a representative image with a useful crop

LinkedIn’s current sharing guidance recommends a 1.91:1 landscape image and lists 1200 × 627 pixels for the sharing module, with a maximum file size of 5 MB. A brand can use that canvas to show the page topic clearly without turning the image into a dense flyer.

Keep important wording and marks away from the outside edges because interfaces may crop or resize. Use high contrast, limited copy, and a topic-specific visual hierarchy. The title and description still belong in metadata and visible page content; the image should support the page, not carry every detail.

Google’s image guidance recommends images that are relevant and representative, avoids extreme aspect ratios, and favors high resolution. Social preview design and Google image presentation are different consumers, so use accurate page metadata and avoid treating one card as a ranking tactic.

04 · Verify the file

Make the image retrievable without a visitor session

Open the exact og:image URL in a private browser window. It should return the image itself with a successful HTTP status and the correct content type. A path that exists only in a local development folder, requires authentication, returns HTML, or produces a 404 cannot become a reliable preview.

Check crawler access, but do not weaken site security indiscriminately. Firewalls, hotlink controls, bot challenges, newly registered domain policies, and authentication layers can affect different requesters differently. Diagnose the exact failed request before allowlisting broad traffic.

Keep the file stable after publication. Replacing an image at the same URL can work, but platform caching means the old creative may persist. A versioned filename is useful when the change must be unmistakable; the page metadata then needs to reference that new public URL.

05 · Refresh deliberately

A correct repair may still show an older cached card

LinkedIn’s Post Inspector guidance explains that previously shared URLs may keep an older image in cache. Enter the page URL in Post Inspector after the production metadata and image are live, then confirm that its preview shows the current content.

LinkedIn notes that refreshing affects new posts containing the URL; it does not rewrite previews on existing posts. A Featured-section item created before the repair may need to be removed and added again after inspection. Do that only after the source page passes, or the service may cache another incomplete result.

Do not add random query parameters as the permanent fix. They can force a distinct fetch, but they also create needless URL variants. Repair the canonical page, use a deliberate asset version when needed, and keep campaign parameters for attribution on external promotional links.

If the old wording appears in Google rather than a social card, use the Google title-and-description update guide; Google’s title links and snippets follow a different process.

06 · Validate production

Test the metadata, file, and real sharing path

1. Load the canonical page over HTTPS and confirm the final URL.
2. Inspect rendered HTML for title, description, canonical, and Open Graph tags.
3. Open the exact image URL and verify dimensions, file type, and status.
4. Check the page and image without a logged-in session.
5. Run LinkedIn Post Inspector after deployment.
6. Create a new test share or Featured link and inspect desktop and mobile crops.
7. Record the page, image filename, publication date, and next review trigger.

A screenshot of the website is not proof that a crawler received the image. Likewise, a correct HTML tag is not proof that the referenced asset exists. The production test must cover both.

07 · Keep outcomes honest

A thumbnail supports presentation; it does not guarantee traffic

A clearer card may help a person understand the destination before clicking. It does not guarantee impressions, clicks, rankings, leads, or sales. Measure the shared link with approved UTM parameters, then review sessions and meaningful customer actions separately.

Do not count a preview render as a website visit. Platform crawlers may request the page and image while analytics blocks or filters automated traffic. A real visit, a CTA interaction, and a confirmed inquiry are different events.

Maintain the card when the page changes materially. Update the title, description, and image when the offer or article intent changes—not merely to make an old page look recent. Keep claims, dates, prices, and service boundaries aligned with the visible destination.

08 · Owner’s handoff

The link-preview checklist

1. Give each important page a specific title and description.
2. Declare a stable canonical URL and matching og:url.
3. Publish a representative 1200 × 627 image below LinkedIn’s file limit.
4. Use generous safe margins and readable contrast.
5. Confirm the exact image URL returns a real public image.
6. Keep the canonical hostname and asset host working over HTTPS.
7. Inspect rendered production metadata—not only CMS settings.
8. Refresh LinkedIn’s cache with Post Inspector after deployment.
9. Recreate older Featured links if they retain a missing preview.
10. Track resulting visits and inquiries without promising outcomes.