Open Graph checker

What is the Open Graph checker?

The Open Graph checker inspects the Open Graph and Twitter card tags on a page URL and shows you what is declared. You paste the address of a page, and the tool fetches it and reads the social sharing metadata in its markup, so you can see exactly which tags are present and what they contain.

Those tags are what turn a bare link into a rich, card-like preview when it is shared on social platforms and messaging apps. Facebook, LinkedIn, and X read the Open Graph and Twitter card data to decide the title, description, and image that appear next to your link. When the tags are missing or wrong, the platform falls back to guesswork, and your carefully written copy gets replaced with a scraped fragment and the wrong picture.

What the Open Graph checker checks

You enter a page URL, and the tool retrieves the page and scans its head section for social sharing metadata. It looks for the standard Open Graph tags, including og:title, og:description, og:image, og:url, and og:type, and for the Twitter card tags such as twitter:card, twitter:title, twitter:description, and twitter:image.

The output reports which tags the page declares and what values each one holds. That matters because a preview is only as good as the weakest tag: a perfect title with a missing image still renders as a plain, unappealing card. Seeing the full set at once makes it easy to spot the gaps.

The check reads the live page, so the result reflects the metadata that a social platform would receive when a link is shared. If your site serves different markup to different visitors, or a cache is holding onto an old version, the checker shows what is actually being emitted for the URL you tested.

Each tag has a specific job in constructing the preview. og:title supplies the headline, og:description supplies the summary, og:image supplies the visual, og:url tells the platform which address the card should link to and own, and og:type declares the kind of content, from article and website to product and video. Getting each role right is straightforward when you know what the tag is for, and the checker makes the roles visible by showing what the page currently declares for each one.

Beyond the basics, pages can carry further Open Graph fields that refine the card. og:site_name supplies the site-wide name shown beside the preview, og:locale identifies the language and region of the content, and image dimensions attached to og:image help platforms render the picture correctly. These extra tags are worth including on the pages people share most, and seeing whether your page carries them is part of understanding how complete its social setup is.

Twitter cards come in a few flavours declared by twitter:card. The summary card shows a compact preview, summary_large_image displays a wide image with text beneath it, and further types drive richer experiences such as video or app promotion on the platform. Choosing the right card type is a small decision with a large visual effect, and verifying the value actually declared on the page is how you confirm the choice is in place.

When social metadata is missing entirely, platforms improvise. They scrape the visible title of the page, dip into whatever text or image looks representative, and produce a preview that often has the wrong headline or an irrelevant picture. The checker exists precisely to prevent that improvisation, since the difference between a deliberate, well-formed card and a scraped guess is entirely visible in the tags the page declares.

One of the most common frustrations is a preview that will not update. The reason is usually the same: sharing platforms cache metadata when a link is first seen, and they refresh it on their own schedule or after a re-scrape is requested. A current check of the live page tells you whether the metadata itself is correct now, which separates the two distinct problems, bad data on the page and stale data in the platform's cache, so you know exactly what has to be fixed.

Larger sites face a consistency challenge that makes routine checks worthwhile. Themes add the tags to every template, ecommerce systems generate them for every product, and a single mistake in a partial or a plugin repeats across thousands of pages. Spot-checking the main templates and a sample of product and article pages keeps the risk contained, because a metadata bug that reaches a whole catalogue is exactly the problem you want to find in a sample rather than in the wild.

How to use the Open Graph checker

Verifying a page's social metadata takes seconds. The steps are:

1. Copy the full URL of the page you want to inspect, making sure it is the address people actually share.
2. Paste the URL into the checker's input field.
3. Submit the form so the server can fetch the page and read its head section.
4. Wait while the tool locates the Open Graph and Twitter card tags in the returned markup.
5. Read the result, noting which tags are present, which are missing, and what each declared value says.

How to get better results

• Test the exact URL that circulates, including any tracking parameters, since a different address may carry different or missing tags.
• Make sure og:url and og:image use absolute, fully qualified addresses, because relative values are frequently misinterpreted when the card is built. The og:url in particular should point at the exact address you want the card to own, including its canonical form.
• Give og:image a real image at a sensible size, around 1200 by 630 pixels, since an image that is too small or fails to load degrades the entire preview. A missing image turns a rich card into a plain, forgettable link.
• Re-check after changing titles, images, or templates, and remember that sharing platforms cache old metadata, so a fresh check may show new tags even while a pasted link still shows the old card.
• Fill in the description tag as well as the title, because platforms show both, and a missing description leaves an awkward blank in the card.
• When you rely on a platform-specific feature, verify the matching tag, such as twitter:card, so each network receives the metadata it expects rather than falling back to a generic preview.

Why the Open Graph checker matters

Social shares are a real source of traffic and brand exposure, and the preview is the first thing people see before they click. A polished card with a sharp image and a clear headline earns clicks, while a broken preview quietly suppresses them. Because the tags are invisible on the page itself, the only way to know what you are sending is to check them, which is exactly what this tool does.

The value compounds with regular use. Marketing pages, product pages, and articles all carry social metadata, and any template or plugin change can strip it out without anyone noticing. Running a quick check before launching a campaign means catching those problems while they are still easy to fix, instead of after an underperforming link has already been shared widely.

When to use the Open Graph checker

• Before launching a new campaign, article, or landing page that will be shared across social media.
• When a shared link renders with the wrong title, description, or image, to find which tag is missing or wrong.
• After a theme, template, or plugin update that could have removed the social metadata from your pages.
• When auditing an ecommerce catalogue, since product pages each need their own correct tags for good previews.

Frequently asked questions

What is the difference between Open Graph and Twitter card tags?

Open Graph is the metadata format used by Facebook, LinkedIn, and many other platforms, while Twitter card tags are X's variant. The checker inspects both sets, so you can see the full picture of what every major network will use.

Why does my preview not update after I change the tags?

Sharing platforms cache the metadata they have already seen. Even after your page is fixed, a previously shared link can keep showing the old preview until the platform re-fetches the page, so give it time and re-share the link. Running a check meanwhile tells you whether the page itself is already correct, which isolates the cache as the only remaining cause.

What image size should I use for og:image?

An image around 1200 by 630 pixels is the commonly recommended size for Open Graph previews. Whatever you use should be a real, loadable image with a sensible aspect ratio.

Do social tags affect search engine rankings?

They are not a direct ranking factor, but they influence how your content looks when shared, which affects click-through rates and social reach. The checker is about presenting your content well on social platforms, not about search position.

Does the checker change or modify the page in any way?

No. It only fetches the URL and reads its markup to report the declared tags. Nothing about the page is altered by running the check.