Check the live Open Graph and Twitter card tags of any URL and see what is missing
Checked from our server in India. Only the address you type is sent to us; nothing else leaves your device. Updated on 18 Oct 2026.An Open Graph checker reads the share tags of a live page, the og: and twitter: tags that decide the card for a posted link. This one fetches the page from our server, reads its head, draws the card for 5 networks (Facebook, LinkedIn, X, WhatsApp and Slack), and lists missing or broken tags such as a relative og:image.
Type the page address.
Press Check tags.
Choose a network to see its card, then read the problems and missing tags.
When a link is shared, the network's server fetches the page and builds a card from tags in its <head>: og:title, og:description, og:image, og:url and og:type, plus twitter:card for X. This checker does the same fetch from our server, following redirects, and reads the head it gets back. Nothing has to be copied or pasted, and relative values such as og:image are resolved against the page's real final address.
The tags are read by the same analyser as the Open Graph Preview on this site. For each network it shows which tag supplied the headline, description and image, because each falls back differently: X reads twitter: tags first, Facebook and LinkedIn read og: tags, and Slack also tries oEmbed. Missing core tags are listed, and so are the problems that break cards in practice: a relative og:image (networks fetch it from their own servers, so it must be absolute), an image on plain http, a missing twitter:card, repeated tags, an og:url that disagrees with the canonical link, and headlines or descriptions long enough to be cut.
Networks cache cards, often for days. If the tags here are right but a network still shows the old card, ask it to scrape the page again with its own sharing debugger. A page that answers an error, or that blocks unknown visitors, gives networks the same trouble, and the fetch result here says so.
Only the head is read, and only the first 256 KB of it; the image itself is not downloaded, so a broken image address is not detected. Sites that serve different HTML to each network's crawler are not imitated.
Type the page address and press Check tags. Our server fetches the page, follows any redirects and reads its head, then the checker shows the og: and twitter: tags it found, the card each network would draw from them, and which core tags are missing. Nothing needs to be copied from the page source.
The most common causes are no og:image tag, an og:image written as a relative path such as /img/card.png, or an image on plain http. Networks fetch the image from their own servers, so it needs a full https address. The checker flags each of these and shows the resolved address.
Five Open Graph tags: og:title, og:description, og:image, og:url and og:type. For X add twitter:card, usually summary_large_image for a wide image. og:image:width, og:image:height and og:image:alt are optional but help the first share render quickly and accessibly.
Networks cache the card they built the first time a link was shared, sometimes for weeks. Once this checker shows the right tags, use the network's own sharing debugger or post inspector to ask it to fetch the page again. WhatsApp refreshes on its own after a while.
The Open Graph Preview reads HTML you paste, so it works on drafts, local pages and pages behind a login. This checker fetches a public page from the internet itself, resolves relative addresses against the real URL and reports fetch problems, such as an error status or a redirect.
No. It reads the image address from the tags and checks that it is absolute and on https, but it does not fetch the image, so a missing file or a wrong size is not detected. Open the image address in a browser to confirm it loads.
Still stuck? Ask about Open Graph Checker and anybody who knows can answer. No account needed.
On the related tools: IP to ASN Lookup – Map an IP address to the ASN that announces it, with the BGP prefix · DNSKEY Lookup – List a zone’s DNSKEY records with key tags, KSK or ZSK roles, algorithms and key sizes.