Ship checklist
Debug One Page Before You Tweet It
Paste the URL, confirm og:title, og:image and og:description all resolve to the live values you meant to publish.
Validate Any Link Preview in Seconds
Paste a link, read every Open Graph and Twitter tag it exposes, preview the unfurl per platform, and get a plain-English fix list.
Missing or weak tags?Generate Open Graph images with AIin seconds.
Where the Validator Fits
Paste a URL, see exactly what Facebook, X, LinkedIn and Slack unfurl — plus a list of what's missing or malformed.
Migration QA
Regression-Test After a Redeploy
Run the validator on the top pages after a framework migration — catches the tags that dropped when SSR moved.
Competitor scan
See What Competitors Actually Share
Point at a rival landing, read their tag set — decide whether to match the format or deliberately stand apart.
Handoff gate
Sign Off Client Work Without Guessing
Agencies running the final handoff QA attach the validator screenshot to the delivery email as proof the tags render.
How to Validate an Open Graph Card End to End
Paste any live URL, read a full crawl of og:*, twitter:* and JSON-LD tags, and see what LinkedIn, Slack and X would render before you ship.
- Step 1
Paste the URL to inspect
The validator fetches the page server-side with a real User-Agent so redirects, cache headers and hidden meta tags all surface honestly.
- Step 2
Read the per-platform breakdown
Every og:, twitter: and article: tag is graded against six preview contracts; missing fields, wrong dimensions and slow images flag in red.
- Step 3
Fix, re-check, and confirm the crawl
Ship the corrected tags, re-paste the URL, and watch every crawler read the same 1200×630 image, title and description on the next hit.
Frequently Asked Questions
How the validator crawls your URL, what it checks, and how to fix the most common failures.
How do I check if my Open Graph tags are set up correctly?
Paste your URL. The validator fetches the page server-side, parses every og:* and twitter:* tag, downloads the referenced images, verifies dimensions and MIME type, and returns a checklist of pass/fail states in under 5 seconds. No signup, no daily cap.
Which tags does the validator check?
The 10 tags that actually change how platforms render: og:title, og:description, og:image, og:image:width, og:image:height, og:image:alt, og:url, og:type, twitter:card and twitter:image. Plus canonical, favicon, and the resolved final URL after redirects — the crawler view, not just source.
Why does the validator show my og:image as broken when it works in my browser?
The two most common reasons: the image URL is relative (og:image should be absolute — https://…), or it's blocked to non-browser user agents in robots.txt or by a CDN rule. Social crawlers hit with 'facebookexternalhit', 'Twitterbot' and 'Slackbot' UAs; the validator uses the same set.
How does this compare to Meta's Sharing Debugger and X's Card Validator?
Meta's Sharing Debugger and X's Card Validator each check one platform's rendering. The Oginify validator combines the checks into a single report and adds the image spec verification (dimensions, MIME, aspect ratio) both platforms omit. Use ours first, then re-scrape the two platform validators to force cache refresh.
Does the validator work on pages behind auth or a paywall?
No — the crawler receives whatever your public origin returns. For staging environments, use a preview URL with token auth (the token is sent as a query param and honored by the fetcher), or run the validator against a public preview deployment.
How often should I run the validator on my site?
After every marketing-page redesign, every rebrand, and every CMS or framework upgrade. Those three events break OG tags most often — usually by changing the meta template or breaking a relative image path. A quarterly sweep of your top 20 pages catches the rest.
Fix What the Validator Just Flagged
If the score above flagged a missing or off-brand og:image, this is the shortest path to fixing it — same tab, same URL, four fresh variants.