Metadata completeness
Which Open Graph and Twitter Card tags are present.
See how your website will look when shared on social media. Check Open Graph tags, images and metadata.
The tags this page returned, the values that survive the fallback chain, and the image as actually fetched.
Which Open Graph and Twitter Card tags are present.
How close the title and description sit to the usual cut-off points.
Its own tag, the other network's tag, the page HTML, or nothing.
The fetched image measured, and checked against what the page declares.
Sharing is where a page meets an audience that has not read it yet.
Confirm the title, description and image are the ones you intended, before the link is out of your hands.
Meta tags are easy to lose in a template refactor, and nothing on the page itself looks broken when they go.
See exactly which tag a value came from, which is usually enough to explain a card nobody expected.
These cards are representative renderings of the fetched metadata, not a copy of any platform's renderer.
Facebook, X, LinkedIn, Slack and Discord each lay a card out differently, change it without notice and cache aggressively. This tool shows the metadata they would read and how a card built from it would look; it does not reproduce their layout and cannot flush their caches. The final URL, the canonical link and og:url are reported separately because they disagree more often than people expect.
What comes up once a preview renders.
Almost always a cache. Networks store the metadata they scraped the first time a link was posted. Use the platform's own debugging or scraping tool to force a refresh after you fix the tags.
Usually not for the text: X falls back to Open Graph. A twitter:card value is still worth setting, because it decides whether you get a small thumbnail or a large image.
1200 x 630 is the safe default across networks. Keep the file under a few hundred kilobytes and declare og:image:width and og:image:height so the card can be laid out before the image loads.
The page and its share image are fetched by our server to be read, then discarded. Nothing is stored, published or forwarded to any social network.