Bulk up to 100 • OG + Twitter basics

OG Tags Checker

Paste URLs — we’ll extract Open Graph meta tags (og:*) and flag missing essentials that break social previews.

Paste up to 100 URLs (one per line)
Tip: missing og:image is the #1 reason previews look broken in messengers and social networks.

Results

URL OG preview data HTTP Time Issues
Run a check to see results here.
This is a technical check. Real previews may vary if platforms cache or block images.

What “good” looks like

OG should be complete and consistent with the canonical URL.

  • OK all essentials present, image loads, og:url matches final URL
  • Warning missing essentials, duplicates, og:url mismatch, image errors
  • Error HTTP/fetch errors or redirect loops
Social previews

OG Tags Checker: fix broken link previews

Open Graph tags control how your pages look when shared on social platforms and messengers. If essentials are missing, you can get the wrong title, empty description, or no image in previews.

Essentials you usually want

  • og:title and og:description for readable text.
  • og:image for the preview thumbnail.
  • og:url for a stable identity (should match canonical/final URL).
  • twitter:card for Twitter/X previews.

FAQ

What are Open Graph (OG) tags?

Open Graph tags are meta tags used by social platforms and messengers to generate link previews. They control the preview title, description, image, and the canonical share URL via og:url.

Which OG tags matter most for previews?

In most cases, these decide whether the preview looks “right”:

  • og:title — preview headline
  • og:description — preview text
  • og:image — thumbnail/image
  • og:url — identity of the shared page
  • og:type — usually website or article

og:site_name is optional but often improves branding in previews.

Why is “missing og:image” such a big deal?

Without og:image, many platforms show a poor preview (no thumbnail, a random image, or a generic icon). That usually reduces clicks and makes shares look “broken”.

Make sure the image is publicly accessible and returns HTTP 200.

What does “og:url mismatch” mean?

It means og:url doesn’t match the final resolved page URL (after redirects). Platforms often use og:url as the page identity, so mismatches can cause:

  • wrong preview cached for the wrong URL
  • duplicate previews for the same page
  • inconsistent share counters and metadata

Best practice: og:url should match your canonical/final URL exactly.

Why does the tool warn about duplicate OG tags?

Multiple og:title / og:description / og:image tags can confuse parsers. Some platforms take the first value, some take the last, some behave inconsistently.

You want one clean set of OG tags per page.

Why do I see “missing twitter:card”?

Twitter/X uses Twitter Card tags. The minimum is usually twitter:card (for example summary_large_image).

Even if OG tags exist, adding Twitter tags can improve how links render on Twitter/X.

Can previews stay “old” after I fix OG tags?

Yes. Social platforms cache previews aggressively. After updates, you may still see old titles/images until the cache refreshes.

In practice: use the platform’s share/debug tools (where available) or wait for cache expiry.

What should I do if og:image returns 403/404?

Common causes and fixes:

  • 403 — hotlink protection, auth, bot blocks, or CDN rules → allow public access for that file
  • 404 — wrong path or removed image → update the tag to a valid URL
  • Redirects — too many hops or cross-domain issues → use a direct final image URL

Also ensure the image uses https:// and is reachable without cookies/session.