Facebook-style card · layout sketch, not the real client
No og:image found in the HTML
Use this link preview checker on a public URL. We send only that URL to our server, fetch the first HTML response, read Open Graph and Twitter tags, and sketch how a link card may look. After a result you can copy a shareable?url= link (no storage) — opening it prefills the form and focuses Run check; it never fetches until you click.
Fetching the public HTML…
Final URL after redirects:
Cards below are layout sketches, not the real client. Real feeds can crop, recode and cache differently.
Facebook-style card · layout sketch, not the real client
No og:image found in the HTML
X-style large card · layout sketch, not the real client
No og:image found in the HTML
LinkedIn-style card · layout sketch, not the real client
No og:image found in the HTML
WhatsApp-style bubble · layout sketch, not the real client
No image
Bluesky-style card · layout sketch, not the real client
Threads-style card · layout sketch, not the real client
Telegram-style preview · layout sketch, not the real client
Reddit-style card · layout sketch, not the real client
Slack-style unfurl · layout sketch, not the real client
Discord-style embed · layout sketch, not the real client
iMessage-style bubble · layout sketch, not the real client
Mastodon-style card · layout sketch, not the real client
Open vendor debuggers with your URL prefilled where supported. Also try a versioned link or a renamed image path when a client keeps an old card.
Versioned URL suggestion
Rename image path
Pass, warn and fail are publishing checks, not a vendor score. Failed items link to the matching guide when one exists.
Create a missing or correctly sized OG imageRepair OG tags
Filled from what we found, with 1200×630 placeholders where a tag was empty.
Planned features only — nothing to buy. Join the list for launch updates. No payment is taken. Details on the Pro waitlist page.
When someone pastes a URL into Facebook, LinkedIn, Slack, iMessage or WhatsApp, the app does not screenshot your page. It asks a crawler to download the HTML and look for a small set of tags: usually og:title,og:description andog:image. Those values become the card. If a tag is missing, the crawler guesses — a random image, a truncated title, or a blank box.
The card is not your homepage design. It is a separate object you control with meta tags in the first HTML response. Client-side frameworks that inject tags after load will look fine in a browser and empty to a bot. This checker fetches as a bot: one GET, no cookies, no login.
Facebook popularised Open Graph. LinkedIn and WhatsApp still read those tags. X adds Twitter Cards (twitter:card should besummary_large_image for a wide picture). The image is downloaded separately. If that second request fails — relative URL, blocked hotlink, 4 MB PNG — the card has text and no picture.
Each client then crops. A 1200×630 file is the usual landscape. WhatsApp shows it smaller. X may use a slightly taller large card. Pinterest is a different object entirely; do not treat a pin as og:image. For sizes, use thesize cheat sheetand theOG image size guide.
Crawlers do not re-download your page on every share. They store the tags and often the image bytes. Replacing og.png in place is the most common reason a “fixed” preview still shows last month’s artwork. Change the image path or add a query string, deploy, then force a scrape.
This checker caches a successful JSON result for five minutes so repeats are cheap. Use “Recheck (bypass cache)” after you deploy. That only bypasses our cache, not Facebook’s.
After the tags look right here, scrape the canonical https URL in the vendor tool:
WhatsApp has no public debugger. If Facebook’s scrape works and WhatsApp does not, wait, then paste the URL into a new chat. Old bubbles keep the empty card.
If the image is missing or the ratio is wrong, generate a 1200×630 PNG in theOG Image Generator, host it, and check again. Guides for stubborn caches live underGuides.
We will not fetch localhost, private networks, or metadata addresses. That is not a preview problem — it is how the function stays safe. Read what the bot sends on theSocialImageKitBot page.
Pass, warn and fail are publishing checks, not a vendor score. A missing og:image is a fail because most feeds will then guess. A relative image URL is a fail because crawlers resolve against the page URL poorly or not at all. A title over about 70 characters is a warn: the tag is present, but a mobile card will truncate it. twitter:card is a warn when absent because X often falls back to Open Graph, but summary_large_image is the clearer contract for a wide picture.
File size uses Content-Length from a HEAD request to the image URL, with the same SSRF rules as the HTML fetch. If the host omits Content-Length we warn instead of guessing bytes from a download. We do not run Facebook’s or LinkedIn’s own scrapers. After this page looks healthy, still hit their debugger on the live canonical URL.
This checker does not execute JavaScript, fill forms, or follow links on the page. It does not log in. It does not store the URL you typed. If your preview only appears after a client-side router paints the head, the function will report missing tags — that is the same view a crawler has. Render the meta tags in the first HTML response, then check again.
Seestatic example resultsfor missing og:image, relative URLs and healthy tags.
Answers about this checker: cost, storage, blocked URLs and caches.
Yes. You can paste a public URL and see the tags we read from the HTML without creating an account. The check runs on a small server function so we can fetch the page the way a crawler would. There is a per-network rate limit so the function stays usable for everyone.
No. The function fetches the URL, parses the HTML in memory, and returns JSON to your browser. We do not write the URL or the result to a database. Short-lived cache and rate-limit counters may exist at the edge so repeats are cheap and abuse is limited. They are not a history of your checks.
The cards on this page are layout sketches using the title, description and image we found. Each app crops, recodes and caches on its own schedule. Use this tool to confirm the tags exist, then scrape the live URL in that platform’s debugger if the real feed still looks wrong.
The function only fetches public http and https pages. Private, loopback, link-local and metadata addresses are rejected, as are unusual ports and URLs that include a username and password. That is to stop the server being used to scan your home network.
No. If the HTML is not returned to an anonymous GET, we cannot see the tags — and neither can Facebook or LinkedIn. Publish a public URL, or temporarily allow the crawler, then check again.
Requests use SocialImageKitBot/1.0 and a link to the bot page on this site. If you block unknown bots, allow that user agent for the pages you want to test, or temporarily allow all crawlers while you debug a preview.