OG Meta Checker
Enter any page URL to preview its social share card and get a pass/warn/fail checklist of Open Graph and Twitter Card tags.
OG Meta Checker
Enter a page URL to check its Open Graph and Twitter Card tags.
About OG Meta Checker
Enter a URL and see exactly what social platforms will see when the link is shared. Our server fetches the page the same way a crawler does, and the checker extracts the title, meta description, canonical URL, and every Open Graph and Twitter Card tag, renders an approximate share card, and runs each tag through a checklist based on the Open Graph protocol and the platforms' published requirements: is og:image an absolute https URL, are its dimensions declared and at least 1200×630, does og:url match the canonical, is twitter:card a valid type, and a dozen more.
Common uses
- Debug why a link shows no image or the wrong title when shared on Facebook, LinkedIn, or X
- Review the full checklist before shipping a new page template
- Verify a fix went live before re-scraping the URL in a platform's own debugger
Example
Input
https://your-site.com/blog/launch-post
Output
✗ og:image — "/og.png" is not an absolute URL. Crawlers require a full https:// URL, not a relative path.
Frequently asked questions
Why doesn't my image show when I share a link, even though og:image is set?
The usual causes, in order: the URL is relative instead of absolute, the image is smaller than the platform's minimum (Facebook needs at least 200×200 pixels), the image URL is behind authentication or blocked by robots.txt, or the platform cached an older version of the page. This checker catches the first two; for cache problems, re-scrape the URL in the platform's own debugger.
What size should my og:image be?
1200×630 pixels (a 1.91:1 ratio) is the size every major platform recommends — it renders as a sharp full-width card on Facebook, LinkedIn, and X. Below roughly 600×315 the image is demoted to a small thumbnail, and below 200×200 Facebook won't show it at all.
Can I check a localhost or staging page?
Only if it's publicly reachable. The page is fetched by our server — just like a real social crawler would fetch it — so localhost, private IP ranges, and internal hostnames are blocked. Deploy the page to a public preview URL first, which is also what you'd need for the platforms' own debuggers.
What happens to the URLs I check?
The URL is sent to our server, which fetches the page once, returns its HTML to your browser for analysis, and stores neither the URL nor the page. Results are never cached, so every check reflects the page as it is right now.
Why does the tool say my page has no tags when I can see them in the browser?
Your meta tags are probably injected by client-side JavaScript. Social crawlers read the raw HTML the server sends and most don't execute scripts, so tags added at runtime are invisible to them — and to this checker, which reads the page the same way. Render the tags server-side or at build time.
Do I need Twitter Card tags if I already have Open Graph tags?
Mostly no: X falls back to og:title, og:description, and og:image. The one tag worth adding is twitter:card with the value "summary_large_image" — without it X may render a small summary card instead of a full-width image.
Why does the checker warn that og:url and my canonical URL differ?
Share counts and engagement signals accumulate against og:url, while search engines consolidate ranking signals on the canonical. When the two disagree, those signals split across URL variants — query strings, trailing slashes, http vs https. Pointing both at the same absolute URL keeps everything counted together.
How is the share preview generated, and is it exactly what platforms show?
It's built from the tags found in your HTML using the same fallbacks crawlers use — og:title falling back to <title>, twitter:image falling back to og:image. It's a close approximation, but each platform applies its own cropping, fonts, and truncation, so use their official debuggers for a pixel-exact preview.