SEO · live fetch

Open Graph checker

See exactly what social platforms read from your page's meta tags — title, description, image, card type — plus warnings about missing or oversized values.

Identifies itself as IPFerret/1.0 to the target site

What this tool checks

When someone shares a URL on Facebook, X/Twitter, LinkedIn, Slack, Discord, iMessage, WhatsApp, or any other platform that previews links, the platform fetches the page and reads its <meta> tags. Specifically: the Open Graph tags (RFC-ish protocol from Facebook, 2010), Twitter'stwitter:* equivalents, and a few standard meta tags. This tool fetches the same way and shows you exactly what they see.

What good OG tags look like

A solid set, in roughly priority order:

  • og:title — 30–60 characters. Will be truncated past ~70 on most platforms.
  • og:description — 100–200 characters. Treat as a tweet-length pitch.
  • og:image — 1200×630 PNG or JPEG, under 1 MB, hosted somewhere social crawlers can reach. Don't use a behind-auth image.
  • og:image:alt — alt text for accessibility; some platforms use it for screen readers and SEO.
  • og:type — usually website or article.
  • og:url — canonical URL. Important for share-cache key consistency.
  • og:site_name — your brand name; shows up as the small label above the title.
  • twitter:card — usually summary_large_image for the big image card on X.

Common mistakes the warnings catch

  • Missing image — social shares become plain text-only cards. Single most common cause of "my link looked plain when I shared it."
  • Image URL is relative (/og.png) — most social crawlers don't resolve relative URLs correctly. Always use absolutehttps:// URLs in OG image fields.
  • Title too long — gets truncated mid-word on some platforms. Lead with the most important phrase.
  • Same title across many pages — Facebook's debugger flags this. Each page should have a distinctive title.

Cache busting

Once you change OG tags, the platform that already cached the old preview won't see the new ones until either the cache TTL expires (days to weeks) or you manually force a refresh:

  • Facebook / Meta: the Sharing Debugger has a "Scrape Again" button.
  • X / Twitter: the Card Validator re-fetches when you re-submit.
  • LinkedIn: Post Inspector forces a refresh.
  • Slack / Discord / iMessage: no public cache buster. Workaround: append a no-op query string (?v=2) to bust the cache for new shares.

Adjacent tools