See how your link renders on every platform — each one fetched separately, with its real crawler. Catches the cards that break on iMessage and Bluesky while looking perfect on Facebook.
We fetch server-side as each platform (a browser can't set a User-Agent) using our open-source engine. Nothing is stored.
Every other Open Graph checker fetches your URL once and re-renders that single response inside different card frames. The tabs look convincing, but they are all showing you the same fetch.
That works right up until a site answers different crawlers differently — through a redirect, a CDN rule, a bot filter, or preview middleware that only recognises some user-agents. Then the tool reports a card that nobody will actually see.
We found this in our own product: a link served a complete Open Graph page to Facebook while iMessage, Reddit and Bluesky were redirected to the destination site and rendered its metadata instead. Every single-fetch validator called the link fine. This tool asks as each platform, so the disagreement shows up as the headline finding rather than staying invisible.
Every tag reports pass, warn, or error — graded, because a missing image guts the card and a missing canonical does not.
Almost always a redirect. If your link redirects and the destination has its own Open Graph tags, the scraper reads those instead of yours. Check the redirect chain on each tab — if some platforms redirect and others do not, that is the cause.
Different platforms use different crawlers, and some servers answer them differently — often unintentionally, through user-agent gating in a CDN, a bot filter, or preview middleware. This is exactly the case a single-fetch checker cannot see, because it only ever asks as one of them.
The image URL must be absolute, publicly reachable, and served over HTTPS without authentication. Relative paths and images behind a login will not render. Aim for 1200×630 — the 1.91:1 ratio every major platform crops to.
Most platforms truncate around 60 characters. The inspector flags titles outside 50–60 so you can see the trim before your audience does.
Platforms cache aggressively. Facebook and LinkedIn both offer a manual re-scrape. Bluesky does not — its CardyB service bakes the card into the post record permanently, so a post that captured a wrong card keeps it forever. That makes Bluesky the one worth checking before you share, not after.
Open Graph is the set of meta tags — og:title, og:description, og:image and friends — that tell social platforms how to render a link as a card. Without them, a shared link renders as a bare URL, which measurably reduces clicks.
Most tools fetch your URL once and re-render that single response inside different card frames. This one fetches it once per platform, using each platform’s real user-agent, so it can tell you when platforms disagree with each other. That is a real and common failure that single-fetch tools cannot detect.
A lot of sites sit behind a bot filter that refuses crawlers it does not recognise, answering with a 401, 403 or 429. That is reported separately and left out of the comparison, because it says nothing about your metadata.
Yes. It runs on LinkForty’s open-source engine, and no sign-up is required. Nothing you check is stored.
LinkForty gives every short link its own share card — set the title, description and image once, and every platform gets the same answer. Plus deep linking, Universal Links and attribution on web and mobile.
Start free