Free Open Graph Tag Previewer
Paste any URL. We fetch the page, parse the Open Graph and Twitter card meta tags, and show you exactly how the link will render when shared on Google, Facebook, LinkedIn, and Twitter/X. Free forever, no signup, no sign-in.
Why use this generator
- Marketer publishing a blog post — wants to verify the share-card image renders before tweeting it.
- Developer wiring up Next.js metadata — needs a fast way to confirm og:image, og:title, twitter:card are all set without testing on actual social platforms.
- Brand manager auditing an entire site — runs the homepage and 10 landing pages through the previewer to find missing tags.
- SaaS founder before a product launch — catches the og:image that's pointing at a 404'd image URL.
- Editor reviewing client work — confirms client's blog posts will show up cleanly in LinkedIn and Slack unfurls.
How it works
- 1Paste the URL you want to test. http or https — we'll add the protocol if you forget.
- 2Hit Check. We fetch the page server-side (so you don't run into CORS issues), parse the <head> for OG and Twitter meta tags, and read back the basic <title> + meta description as fallbacks.
- 3Review the three preview cards: Google (search result), Facebook/LinkedIn (large OG card), Twitter/X (summary or summary_large_image).
- 4Read the warnings panel — missing og:image, oversized titles, missing twitter:card all surface here with what platforms will fall back to.
- 5Fix any issues in your source code, deploy, and re-run. The endpoint is rate-limited but you can hit it as often as needed for normal work.
Frequently asked questions
- Why doesn't my Facebook share update after I fix the tags?
- Facebook aggressively caches OG metadata. Use the Sharing Debugger (developers.facebook.com/tools/debug/) and click 'Scrape Again' to force a refresh. Twitter/X has a similar caching layer at cards-dev.twitter.com/validator. Our previewer doesn't cache — every check fetches fresh.
- Does og:image need to be hosted on the same domain?
- No — it can be any absolute HTTPS URL. But Facebook requires the image to be at least 200×200 (1200×630 recommended) and to load in under 8 seconds. If you're serving it from a slow CDN or a domain that blocks Facebook's scraper, the card will fail silently.
- Twitter card 'summary' vs 'summary_large_image'?
- summary = small square thumbnail next to the text (older default). summary_large_image = full-width 1.91:1 image above the text (what most blogs and SaaS sites want). Set twitter:card to summary_large_image and provide an og:image or twitter:image at 1200×630.
- Why is my title getting truncated on LinkedIn?
- Facebook and LinkedIn truncate og:title around 60 characters. Twitter/X around the same. Google truncates the <title> tag around 60 chars in search results too. We warn you any time a title exceeds the limit.
- Can I check a localhost / staging URL?
- No — we refuse private and localhost addresses for security reasons (server-side fetches that could otherwise be used to scan internal infrastructure). Test on a public preview URL (Vercel preview deploy, Cloudflare Tunnel, ngrok).
- Are my checked URLs logged?
- We rate-limit by IP in process memory, which means we briefly count how many checks each IP has done in the last minute. Nothing is persisted, nothing is logged to disk, nothing is sent to analytics. The check itself doesn't touch our database.