Skip to content

LinkedIn · Aug 7, 2026

Why LinkedIn Post Inspector finds no image

LinkedIn Post Inspector is the official way to see what LinkedIn stored for a URL. “No image found” means their crawler did not get a usable og:image, not that your designer forgot the Figma frame.

Inspect the live HTML (view source, not the React tree in DevTools). Then paste the same URL into the OG image checker. If our checker already reports a missing, HTTP, or invalid image, Post Inspector will too.

Why LinkedIn disagrees with your browser

  • Relative paths. content="/og.png" is a fail.
  • HTTP. LinkedIn wants HTTPS.
  • Auth walls. If the crawler gets a login HTML page, there is no image.
  • Bot filters. Blocking datacenter IPs or unnamed user-agents can hide tags.
  • Cache. Post Inspector shows the last successful scrape until you run it again.

LinkedIn is also strict about image size. Give it 1200×630 and og:image:width / og:image:height. Tiny images become “no image” or a sad thumbnail. See OG image size.

The rest of the “blank card” checklist: why your OG image is not showing.

After you replace the file

  1. Change the image URL if the old one was cached (new path or cache-buster query).
  2. Open Post Inspector, paste the canonical https:// page URL, inspect.
  3. Share from a fresh post, not an old draft that still embeds the previous card.

Our checker does not call LinkedIn. It shows an approximate LinkedIn-style card from the tags we fetched. Use both: checker for the HTML, Post Inspector for LinkedIn’s cache.

When you need a file that is actually 1200×630, generate it with the OG image generator, save it, and point og:image at the /u/… URL. PNG is free. Then inspect again.

Need the actual image?

Open the OG image generator — PNG export is free. Pro is $19.99/mo for JPEG/WebP, CDN URLs, and an API key. Or paste a live URL into the checker first.