Free Tool

Free Open Graph & Meta Tag Checker

Inspect Open Graph and Twitter Card meta tags on any URL. Preview how your link renders on Facebook, X, LinkedIn, Slack, Discord, and iMessage before publishing. Free, instant, no signup.

Enter URL to inspect

No signup required

Free forever

GDPR compliant

Quick Answer

An OG tag checker fetches a URL and parses its Open Graph (og:title, og:description, og:image), Twitter Card, and standard meta tags so you can preview how the link will render when shared on social platforms. The U2L checker is free, server-side, SSRF-protected, and shows a live preview of how the card looks on Facebook, X, and LinkedIn.

Quick Facts

Open Graph (OG) is Facebook's 2010 protocol for describing how URLs render in shared previews. Adopted by Twitter, LinkedIn, Slack, Discord, iMessage, and every other major platform.
Required minimum: og:title, og:description, og:image, og:url, og:type. Without these, social platforms fall back to extracting from <title> and <meta name='description'> with mixed results.
og:image must be at least 200x200px; the recommended size is 1200x630px (1.91:1 aspect ratio). Smaller images get cropped or scaled poorly in previews.
Twitter Cards extend OG with twitter:card (summary, summary_large_image, app, player) and platform-specific overrides via twitter:title, twitter:image.
LinkedIn aggressively caches OG tags. After updating, post the URL once into LinkedIn's Post Inspector to flush the cache; otherwise old previews persist for weeks.
Discord, Slack, and iMessage strictly follow OG. WhatsApp and Telegram extract from OG with fallbacks to body text and the first <img> tag.
Pages without OG tags still get rich previews on most platforms by extracting from <title>, <meta name='description'>, and the first sizable <img>. Quality varies wildly.

How to check OG tags on a URL

Three steps. Paste, fetch, inspect.

1
Paste the URL
Any public URL: a blog post, product page, landing page, or shortened URL. The checker follows up to 20 redirects to reach the final HTML and parses meta tags from there.
2
Click Check
U2L's server-side fetcher runs at Cloudflare edge with a Chrome User-Agent. The destination behaves identically to a real browser visit. Up to 256KB of HTML is parsed; meta tags appear in the result.
3
Read the previews
Three preview cards (Facebook / X / LinkedIn) show how your URL will render. Below them, a full meta dump lets you debug any missing or incorrect tags. Look for og:image dimensions, missing og:description, or stale Twitter card type.

What is a OG / Metatag Checker?

OG / Metatag Checker is a tool that fetches a URL, parses its meta tags, and shows you how the link will render when shared on social platforms. The U2L checker reads Open Graph (og:*), Twitter Card (twitter:*), and standard meta tags (title, description, canonical, favicon), follows redirects to the final URL, and renders preview cards so you can visualize the experience your audience will see.

Open Graph is the dominant social-share protocol. Facebook introduced it in 2010 to give URL shares better-looking previews; Twitter, LinkedIn, Slack, Discord, iMessage, WhatsApp, and Telegram all later adopted it. The protocol is simple: a few <meta property='og:*'> tags in the HTML head describe the page's title, description, image, type, and URL. Social platforms scrape these tags when a URL is shared and use them to render the preview card.

Wrong or missing OG tags are the #1 source of ugly social previews. A page missing og:image gets a generic gray placeholder; a wrong og:title gets shared as the literal HTML <title>, which often differs from the intended share copy; an og:image that's too small gets aggressively cropped. Checking before publishing or before launching a campaign saves the embarrassment of broken-looking shares.

The U2L checker is also useful for debugging: a stakeholder reports 'the LinkedIn preview is wrong' and you need to see the live OG state to know whether the issue is your tags, LinkedIn's cache, or a CDN misconfiguration. Run the checker, see the actual tags being served, and you isolate the problem in seconds.

How does a OG / Metatag Checker work?

When you submit a URL, U2L's server-side fetcher runs at the closest Cloudflare edge. It issues an HTTP GET request with a Chrome desktop User-Agent and Accept: text/html headers, follows up to 20 redirects, and reads the response body. The fetcher caps body size at 256KB to protect against denial-of-service from huge pages; meta tags always live in the first 32KB or so, well within the cap.

The HTML parser extracts every <meta> tag that carries og:*, twitter:*, name, itemprop, or http-equiv attributes, plus the <title> tag, <link rel='canonical'>, and the first <link rel='icon'>. Image URLs (og:image, twitter:image) are absolutized using the page's URL as base, so relative paths like /og.png become https://yoursite.com/og.png in the output.

Three social-platform preview cards are rendered client-side from the parsed tags. Facebook uses og:image + og:title + og:description + the canonical domain. Twitter (X) uses twitter:image with og:image fallback, twitter:title with og:title fallback, and similar for description. LinkedIn uses OG tags exclusively (it doesn't read Twitter Card tags). The previews mirror each platform's actual rendering rules including image cropping and text truncation.

SSRF protection is built in. Requests to loopback (127.0.0.1, ::1), private IPv4 ranges (10.x, 192.168.x, 172.16-31.x), private IPv6 (fc00::/7, fe80::/10), link-local (169.254.x), and cloud metadata endpoints are blocked. This prevents the public checker from being weaponized to scan internal corporate networks. Only http: and https: schemes are allowed; data: and file: are rejected.

Use Cases

How marketers, businesses, and developers use og / metatag checker.

Pre-publish QA for blog posts

Before publishing a blog post, run the URL through the checker to verify the OG tags render correctly. Catches missing og:image, mistyped og:title, or stale data from CMS template defaults that didn't get overridden.

Campaign launch QA

Marketing campaigns push new landing pages. Each page needs unique OG copy. The checker confirms the tags are set correctly before ad spend hits the page; broken previews on day-one ads waste budget.

LinkedIn cache debugging

LinkedIn caches OG tags for weeks. After updating, run the checker to verify your OG state, then submit the URL to LinkedIn's Post Inspector to force a refresh. The checker confirms what LinkedIn should be seeing.

Social media manager pre-share check

Before posting a URL to a brand account on X, LinkedIn, or Facebook, run it through the checker. The preview cards show exactly what followers will see; if it's broken, you fix the tags before posting (not after).

Affiliate link compliance review

Affiliate marketers must verify that their disclosed affiliate URLs render with correct merchant branding (not the affiliate network's branding). The checker reveals what social previews will show.

SEO audits for stale meta tags

Old blog posts often have stale or default meta descriptions that hurt CTR. Run a sample of top-traffic URLs through the checker; pages with missing or generic descriptions are first candidates for refresh.

E-commerce product page launches

Each product page should have a product-specific og:image (the product photo) and a product-specific og:description. Default storefront OG tags propagating to product pages is a common e-commerce CMS bug.

Newsletter and email-pre-flight QA

Newsletters reference URLs that get previewed in Gmail, Outlook, and Apple Mail (which all use OG). The checker confirms previews work before send; broken previews look like phishing to recipients.

Customer support: 'why does my link look broken?'

When a user reports a broken share preview, the checker reveals whether the issue is missing tags, a CDN cache problem, or a platform-specific issue. Diagnosis goes from minutes to seconds.

Phishing investigation

Security analysts inspect suspicious URLs to see what cloaking or impersonation is happening at the meta-tag layer. OG tags often reveal a different brand than the URL pretends to be.

OG / Metatag Checker vs Alternatives

Side-by-side feature and pricing comparison with the top alternatives.

Feature	U2L	OpenGraph.xyz	Metatags.io	Iframely	Facebook Debugger
Free, no signup				Limited	Sign-in required
Multi-platform preview	FB/X/LinkedIn				FB only
Follows redirects	Up to 20 hops	Limited	Limited
SSRF-protected backend		Unclear	Unclear	Unclear	Yes
Cloudflare edge fetcher					Meta CDN
Forces platform-cache flush
Shows full meta dump
Twitter Card detection

OG / Metatag Checker vs OpenGraph.xyz

OpenGraph.xyz is the most-trafficked free OG checker. Clean UI, multi-platform previews, free for typical use. The fetcher runs from a single region and the rate limit is undocumented.

U2L's checker offers identical core functionality with sub-200ms edge response from Cloudflare and explicit SSRF protection. For one-off checks, either works; for repeat use under known network conditions, U2L is more predictable.

OG / Metatag Checker vs Facebook Sharing Debugger

Facebook's official debugger is the canonical tool for Facebook OG tags. The 'Scrape Again' button forces Facebook to refresh its cache - critical when you've updated tags and the old version is still showing in shares.

U2L's checker shows what tags are CURRENTLY being served. Facebook's tool shows what FACEBOOK has cached and lets you flush its cache. Use both: U2L to validate your tags, Facebook's debugger to push the update.

Best Practices

Always set og:image to 1200x630px

1200x630 is the sweet spot for Facebook, LinkedIn, X, Slack, and Discord. Smaller gets cropped; larger gets scaled. Use the same aspect ratio (1.91:1) and PNG or JPEG format.

Set og:image:width and og:image:height

Without explicit dimensions, some platforms wait for the image to load before showing the preview, increasing time-to-render. Setting dimensions lets platforms reserve space and render text immediately.

Use absolute URLs for og:image

Relative URLs like /og.png break on some platforms (especially older Facebook crawler behavior). Always use absolute https://yoursite.com/og.png.

Set og:url to the canonical URL

If your page has multiple URLs (UTM-tagged variants, www vs non-www), point og:url at the canonical URL so all share counts aggregate to one place. Mismatched og:url splits social-share metrics.

Always include twitter:card

Without twitter:card, X falls back to og:image but often picks a tiny preview. twitter:card='summary_large_image' explicitly requests the large preview format.

Set article-specific OG tags for blog posts

og:type='article' plus article:published_time, article:author, article:section give blog posts richer previews on Facebook (with the author and timestamp visible). Worth the 4 extra tags.

Test on the actual platforms before launch

Even with the checker showing correct tags, paste the URL into Facebook, X, and LinkedIn directly to confirm the live preview matches expectations. Platform-specific quirks (caching, image cropping) only show up live.

Force cache refresh after updates

Facebook (Sharing Debugger), LinkedIn (Post Inspector), and Twitter (Cards Validator) all have refresh tools. Use them whenever you update OG tags so old previews don't persist for weeks.

Monitor og:image broken-link rate

Periodically check that your og:image URLs return 200 OK. Broken og:image (404, slow load) eviscerates social CTR. Quarterly OG audit catches stale image URLs from CMS or CDN changes.

Common Mistakes to Avoid

Using a generic site-wide og:image

All pages sharing the same og:image (typically your logo) makes every share look identical. Configure your CMS to set page-specific og:image (post hero, product photo, dashboard screenshot) for each URL.

Forgetting twitter:card

X falls back to og:image without twitter:card, but often picks the tiny 'summary' format instead of 'summary_large_image'. Always set twitter:card explicitly.

Setting og:image to a relative path

/images/og.png works in some platforms and fails in others. Always use absolute https:// URLs for OG images.

Mismatched og:title and document <title>

Wildly different titles between og:title and the page <title> looks suspicious to search engines and platforms. Keep them within minor variation: og:title can be more conversion-focused, but should not be an entirely different concept.

Truncating og:description at 60 characters

Some platforms (Slack, iMessage) show 200+ characters; Facebook truncates at ~150. Aim for 150-200 chars in og:description so platforms can show the most they comfortably display.

Forgetting cache invalidation

Facebook, LinkedIn, and Twitter cache OG tags for hours to weeks. Updating tags doesn't update existing shares. Use each platform's cache-flush tool after important changes.

Loading og:image from a slow or unreliable host

If og:image takes 5+ seconds to load, the social platform's crawler often times out and either skips the image or marks the share as 'pending'. Use a CDN-backed image host with sub-200ms response.

Technical Specifications

Maximum HTML body parsed	256 KB (meta tags always live in the first 32 KB)
Maximum redirect hops	20 (matches major browser limits)
Request method	GET with Chrome desktop User-Agent and Accept: text/html
Timeout	8 seconds; fails to 504 timeout response
SSRF protection	Loopback, private IPv4/IPv6, link-local, cloud metadata endpoints blocked
Tag types parsed	<title>, <link rel=canonical\|icon>, <meta property=og:>, <meta name=twitter:\|description\|>, <meta itemprop=>, <meta http-equiv=*>
Image URL handling	og:image, og:url, twitter:image absolutized via base URL
Entity decoding	& < > " '   decoded in extracted values
Edge location	Cloudflare global network (closest to user)

Industry-Specific Use Cases

Content marketing teams

Daily blog publishing requires per-post OG tag validation. The checker is part of the standard pre-publish QA checklist alongside spelling, fact-checking, and internal-link verification.

Performance marketing and ad ops

Landing-page launches push new URLs daily. Ad spend hitting a page with broken OG previews wastes a portion of every click. The checker is part of the campaign launch runbook.

Web development and CMS engineering

Engineers building CMS templates verify that OG fields propagate correctly per page type (posts, pages, products, categories). The checker confirms templates work end-to-end without crawling the live site manually.

Customer support and trust & safety

Support tickets reporting 'broken preview on Facebook' get diagnosed quickly with the checker - it reveals whether the issue is the user's tags, a CDN issue, or a Facebook cache problem.

SEO agencies

OG audits are part of any SEO health check. Pages with missing or generic OG tags lose social share CTR; the checker enables bulk audit across a client's top URLs.

Security and brand monitoring

Investigating phishing or brand-impersonation URLs starts with the OG tags. The checker reveals whether the URL claims to be a legitimate brand via og:title, og:image, etc., even if the actual URL is hostile.

Frequently Asked Questions

What does the OG tag checker do?

It fetches a URL, parses its Open Graph and Twitter Card meta tags, and shows you how the link will render when shared on social platforms. Useful for pre-publish QA, debugging broken previews, and verifying that shared URLs look correct on Facebook, X, LinkedIn, Slack, and Discord.

What are Open Graph tags?

OG tags are HTML <meta> tags Facebook introduced in 2010 to control how URLs look when shared. They specify title, description, image, type, and URL. Twitter, LinkedIn, Slack, Discord, iMessage, WhatsApp, and Telegram all read OG tags when generating link previews.

Why is my OG image not showing on Facebook?

Three common causes: (1) the og:image URL returns 404 or 5xx, (2) the image is smaller than 200x200px (Facebook's minimum), or (3) Facebook has cached an old/missing version. Run the checker first to confirm the tag exists, then use Facebook's Sharing Debugger to flush the cache.

What's the recommended og:image size?

1200x630 pixels at 1.91:1 aspect ratio. This is the sweet spot for Facebook, LinkedIn, X, Slack, and Discord. PNG or JPEG format. File size under 5MB; under 1MB is faster.

What's the difference between OG tags and Twitter Cards?

OG is Facebook's open protocol; Twitter Cards is X's variant that adds a few X-specific fields (twitter:card type, twitter:image overrides). Both protocols share most fields, and X reads OG tags as fallback for missing twitter:* tags.

Why do my LinkedIn previews keep showing the old image?

LinkedIn caches OG tags for up to 7 days. Updates to your tags don't refresh existing shares. To flush LinkedIn's cache, paste the URL into LinkedIn Post Inspector (linkedin.com/post-inspector). After re-scraping, new shares show the updated image.

Does the checker support Twitter Cards?

Yes. The checker parses both og:* and twitter:* tags and shows them in the meta dump. The Twitter preview card uses twitter:image with og:image fallback, twitter:title with og:title fallback, etc.

Will it work for paywalled or login-gated URLs?

The checker uses an anonymous request. If the URL requires login (e.g. paywalled news, subscription portal), the response shows the login page's OG tags - not your protected content's tags. To check protected content, the page needs server-side OG tags rendered before auth.

Can it scan internal/private URLs?

No. The checker has SSRF protection: requests to loopback, private IP ranges, link-local, and cloud metadata endpoints are blocked. Use a local OG checker tool (or your browser's view-source) to inspect internal-network URLs.

Does the checker run JavaScript on the page?

No. The fetcher reads the static HTML response. JavaScript-injected OG tags (added by client-side scripts) won't be visible to the checker - and won't be visible to social-platform crawlers either, which is why you should always render OG tags server-side.

What if the page has no OG tags at all?

The checker shows that no og:* tags were found and falls back to <title>, <meta name='description'>, and <link rel='canonical'>. Social platforms also fall back to these when OG is missing, but with mixed quality. Adding proper OG tags is a 10-minute fix that materially improves share CTR.

Will the checker bypass robots.txt or meta noindex?

No. The fetcher uses a normal User-Agent that respects no special crawl directives. It doesn't bypass robots.txt rules, but neither does it add a special crawl-bypass header. The checker behaves exactly like a regular browser.

Does it work for AMP and embedded content?

AMP pages have their own meta-tag conventions; the checker reads OG tags from the AMP HTML. For embedded content (oEmbed, iframely), the checker fetches the HTML wrapper, not the embedded source. For oEmbed-specific data, use Iframely or a dedicated tool.

How fresh are the results?

Real-time. The checker fetches fresh on every check - no caching of OG tags on our side. The result reflects exactly what's live at the moment you click Check.

Can I check URLs in bulk?

The free tool checks one URL at a time. For bulk OG audits (50+ URLs in one run), use the U2L API or upload a CSV via the paid Bulk URL Status Checker. Both tools share the same fetcher backend.

Will it detect Schema.org / JSON-LD markup?

The current version focuses on OG, Twitter Card, and standard meta tags. Schema.org JSON-LD detection is on the roadmap; for now, use Google's Rich Results Test or Schema.org Validator for JSON-LD inspection.

Why is og:image showing as a relative URL?

Sites set og:image to a relative path like /og.png. The checker absolutizes it to https://yourdomain.com/og.png using the page's URL. Facebook and most platforms also absolutize, but some older crawlers fail on relative URLs. Always use absolute URLs in your tags.

Does my OG content need to match my SEO meta tags?

Not exactly, but they should be consistent. og:title can be more share-optimized (compelling, click-driving) than <title> (search-optimized, keyword-rich). og:description can be slightly different from <meta name='description'>. Wildly different content reads as spam.

Will the checker work for redirect chains?

Yes. The fetcher follows up to 20 redirects and reads the final destination's HTML. The result shows the final URL alongside the input URL, so you can verify the redirect chain works as expected.

Are there fees for using this?

No. The checker is free with no rate limits for normal use. Heavy automated use (1000+ requests per minute) may be throttled to keep the service stable for everyone.

Related Free Tools

WhatsApp Link Generator

Create wa.me click-to-chat links with prefilled messages. Add to your bio, ads, or QR codes for instant WhatsApp customer chats.

Redirect Checker

Trace the full redirect chain of any URL. See every hop, status code, response time, and final destination.

URL Encoder / Decoder

Encode or decode any URL. Handle special characters, query strings, and percent-encoding. Pure browser, instant.

Schema Markup Generator

Generate valid JSON-LD schema for FAQ, HowTo, Article, Product, and Organization. Boost rich results and AI Overview citations.

URL Expander

Reveal the full destination behind any shortened URL. Check where a short link leads before clicking it.

Bulk URL Status Checker

Check status codes for hundreds of URLs at once. Find broken links, redirects, and slow pages. CSV export.

See all 50 free tools

Key Terms

Open Graph (OG): Facebook's protocol for describing how URLs render in shared previews. Defined as <meta property='og:*'> tags in the HTML head. Adopted by Twitter, LinkedIn, Slack, Discord, iMessage, WhatsApp, and Telegram.
og:title: The title shown in the share preview. Should be compelling and click-driving; can differ from the document <title>. Maximum length varies (Facebook ~95 chars, X ~70 chars).
og:description: Short description shown in the share preview. Aim for 150-200 characters; some platforms show more.
og:image: URL of the preview image. Recommended 1200x630 pixels at 1.91:1 aspect ratio. PNG or JPEG. Always use absolute URLs.
Twitter Card: X's variant of OG with X-specific fields (twitter:card, twitter:image, etc.). X reads og:* tags as fallback for missing twitter:* tags.
twitter:card: Specifies the card layout. Common values: 'summary' (small image), 'summary_large_image' (large image), 'app', 'player'. Most use cases want 'summary_large_image'.
Canonical URL: The preferred URL for a page. Set via <link rel='canonical'>. Helps consolidate ranking signals and share metrics across URL variants (with/without UTMs, www/non-www, etc.).
SSRF (Server-Side Request Forgery): A vulnerability where an attacker tricks a server into making requests to internal addresses. The checker has SSRF protection: requests to loopback, private IPs, link-local, and cloud metadata endpoints are blocked.

Customize OG previews for every shortened link

U2L Pro lets you set custom og:image, og:title, and og:description for every short link, so even shared u2l.ai URLs render with your brand's preview. Free for the first 30 days.

Upgrade to Pro