Open Graph Preview
Paste your meta tags and see the card Facebook, X, LinkedIn, Slack and Discord will each render, cut at the exact character each one cuts at. Nothing is fetched, so it works on staging and on tags you have not deployed yet.
Your tags
Parsed values drop into the fields below. Edit any of them to try a fix before you ship it.
7 findings · 2 breaks the card
No og:title and no <title>. Every platform will show the bare URL
No og:description and no meta description. Facebook and Slack will render the card with a blank body
No og:image. LinkedIn and Slack render a link with no card at all, which is the single largest click-through loss here
No og:url. Shares of the same page with different query strings accumulate as separate URLs
No og:type. It defaults to website, which is right for most pages but wrong for an article
No twitter:card. X and Discord both default to a small thumbnail rather than the wide image
No og:site_name. The card labels itself with the bare domain instead of your brand
Caches the image on first scrape. Change it and you have to re-scrape
X (Twitter)
Falls back to Open Graph when twitter: tags are absent
Drops the description in the feed entirely. Title and image only
Slack
Renders a left-bar unfurl. No image means a bare link
Discord
Needs twitter:card set to summary_large_image for a wide image
Short answer
Open Graph tags are meta tags in the head of a page that tell social platforms how to render a link to it: og:title, og:description, og:image and og:url. The image should be 1200 by 630 pixels at an absolute HTTPS URL, because relative paths fail silently on every platform. Titles get cut at roughly 70 characters on X, 88 on Facebook and 119 on LinkedIn, and LinkedIn drops the description entirely. None of these tags is a ranking factor. What they decide is whether a shared link arrives as a card or as a bare URL.
Where each platform cuts your text
These are render widths, not documented maximums. Nothing rejects a long title, it simply disappears mid-word in the feed.
| Platform | Title shown | Description shown | Reads twitter:card |
|---|---|---|---|
| X | ~70 chars | ~125 chars | Yes, and prefers twitter: tags |
| Slack | ~75 chars | ~190 chars | No |
| Discord | ~82 chars | ~190 chars | Yes, for the image size |
| ~88 chars | ~200 chars | No | |
| ~119 chars | Not shown in feed | No | |
| ~65 chars | ~80 chars | No |
Write to the shortest number that matters to you rather than to an average. A 68 character title survives everywhere on this list except WhatsApp, which is usually the right trade.
- Front-load the meaning. Whatever is in the first 65 characters is the part that is guaranteed to be read.
- Do not reuse the SEO title. A brand suffix that earns a click in a search result is dead weight in a card that already shows the brand.
- Treat LinkedIn as title-only. If the description carries the hook, LinkedIn gets none of it.
Why your card still shows the old version
This is the second most common problem here, and unlike a relative path it is not a defect in your markup at all.
- Facebook and LinkedIn cache aggressively. They fetch the card once and keep serving it. Changing the tag changes nothing until you force a refetch in their own sharing debugger.
- Slack and Discord expire sooner. They usually catch up on their own within a day, which is why a card can look right in one place and stale in another.
- A changed image filename is the reliable fix. A new URL has no cache entry, so it renders immediately everywhere.
- Blocked crawlers cache nothing. If robots.txt or a firewall rule stops the platform fetching the page, you get a bare link and no explanation.
That last one is worth checking before you rewrite any tags. The robots.txt tester shows which user-agents your file blocks, and the page indexability checker confirms the page returns a 200 to a crawler rather than a redirect.
How to preview your Open Graph tags
Seven steps. The sixth is the one a fetch-based checker cannot do, because it lets you test the fix before it exists anywhere.
- 01
Copy the head of the page you are about to share
View source, or open the network tab and copy the response body. A fragment is fine: the parser reads loose meta tags without needing a full document around them.
- 02
Paste it and read the findings first
The two that break a card outright are a missing og:image and a relative image path. Both render as a bare link on LinkedIn and in Slack, which is the largest single click-through loss on this page.
- 03
Check the title against the shortest limit
X cuts around 70 characters and Facebook around 88. A title that survives on Facebook and dies mid-word on X is the usual outcome of writing to one platform.
- 04
Confirm og:url matches your canonical
When they disagree, share counts accumulate on one address and ranking signals on the other. The tool compares them for you and ignores a trailing slash difference.
- 05
Set twitter:card explicitly
X and Discord both read it, and without it they default to a small thumbnail. Setting summary_large_image is the difference between a wide image and a postage stamp in a feed.
- 06
Edit the fields to test a fix
The parsed values drop into editable inputs, so you can shorten a title or make an image path absolute and watch every card re-render before you touch the codebase.
- 07
Re-scrape after you deploy
Facebook and LinkedIn cache the first version they fetch. Changing the tag is not enough: you have to ask each platform's own debugger to fetch the page again before the new card appears.
If you are writing the tags rather than auditing them, start from the meta tags generator, which emits the full block with og:url wired to your canonical. The SERP snippet preview covers the other place the same title has to fit.
Check the tags you already shipped, at scale
One page at a time is right for a launch. For the other nine hundred, the meta tag checker reads a live URL, and a crawl is what finds the whole set of pages that never had an og:image in the first place.
What this preview shows
Five platform cards
Facebook, X, LinkedIn, Slack and Discord, each with its own chrome
Real cut points
Titles truncated where each platform truncates, not at one shared limit
Loose tag parsing
A full head or a handful of meta tags, in either attribute order
Fallback chains
Shows the <title> and meta description platforms fall back to
Canonical comparison
Flags og:url and rel=canonical disagreeing, ignoring trailing slashes
Editable fields
Change a value and every card re-renders before you ship it
Card-breaking errors
Relative paths and missing images called out separately from warnings
Nothing is fetched
Works on staging, on gated pages, and on undeployed markup
This parses what you paste, and that is deliberate
Frequently asked questions
What are Open Graph tags?
Meta tags in the head of a page that tell social platforms how to render a link to it. Facebook introduced the protocol in 2010, and og:title, og:description, og:image and og:url are now read by almost every platform that unfurls a link, including Slack, LinkedIn, WhatsApp and Discord.
Do Open Graph tags affect SEO?
Not directly. They have never been a ranking factor and Google does not use them for search results. What they affect is the click-through you get from every surface that unfurls a link, which is why a page with no og:image quietly loses traffic that never shows up as a ranking problem.
What size should an og:image be?
1200 by 630 pixels, which is the 1.91:1 ratio every platform crops toward. Keep it under 5MB and serve it over HTTPS at an absolute URL. Smaller than 600 by 315 and some platforms downgrade the card to a small thumbnail instead of the wide image.
Why is my og:image not showing?
Almost always caching or a relative path. The platform fetched your page before the tag existed and is serving the cached card, or the image URL starts with a slash rather than https, which fails silently everywhere. Re-scrape in the platform's own debugger after checking the path is absolute.
Do I need Twitter card tags if I already have Open Graph?
Mostly no. X falls back to og:title, og:description and og:image when the twitter: equivalents are absent. The one tag worth setting explicitly is twitter:card, because it decides between a small thumbnail and a wide image, and Discord reads it too.
What is the difference between summary and summary_large_image?
Summary renders a small square thumbnail beside the text. Summary_large_image renders the full 1200 by 630 image above it and takes several times more space in a feed. Unless the image is genuinely a logo, the large variant is the one you want.
Should og:url match my canonical tag?
Yes. The canonical tells search engines which URL to index, and og:url tells social platforms which URL to attribute shares to. When they disagree, your share signals accumulate on one address while your ranking signals accumulate on another.
How long can an Open Graph title be?
No platform rejects a long one, they just cut it. X shows around 70 characters, Slack around 75, Facebook around 88 and LinkedIn around 119. Writing to the shortest of those means the title survives intact everywhere it lands.
Does LinkedIn show the og:description?
Not in the feed. LinkedIn renders the image and the title and drops the description entirely, so a page relying on the description to explain itself gets nothing across there. Put the hook in the title if LinkedIn is a real channel for you.
Why does my share card show the old title after I changed it?
Facebook and LinkedIn cache the card from the first successful scrape and do not refetch on their own. Use the platform's own sharing debugger to force a fresh fetch. Slack and Discord cache for a shorter period and usually catch up without help.
Can I use a relative path in og:image?
No. Social crawlers do not resolve relative URLs, so a path like /images/card.png produces a card with no image and no error message anywhere. It has to be the full absolute URL including the protocol and domain.
Does this tool fetch my page?
No. It parses markup you paste, entirely in your browser, so it works on staging sites, on pages behind a login, and on tags you have written but not deployed yet. Nothing is uploaded and no request is made to the page.
What is og:type and does it matter?
It says what kind of thing the page is: website, article, product, video. It defaults to website when absent, which is right for most pages. Setting article on a blog post unlocks published time and author properties that a few platforms display.
Other on-page SEO tools
Canonical Tag Checker
Validate canonical tags for self-referencing, protocol mismatches, trailing slash conflicts, noindex conflicts, and og:url consistency.
Use toolHreflang Validator
Validate hreflang tags for international SEO: self-referencing, return tags, x-default, language codes, and duplicate detection.
Use toolSchema & JSON-LD Validator
Validate structured data markup: required properties, date formats, nested entities, and JSON syntax. Supports all major schema types.
Use toolMeta Tag Checker
Check title tags, meta descriptions, Open Graph tags, Twitter cards, canonical URLs, robots directives, and viewport settings.
Use toolMeta Tags Generator
Write the title, description, and social share tags every page needs. Live character counts plus previews of how it will look in Google and on social.
Use toolKeyword Density Checker
See which words and phrases your copy actually leans on. Single word, two word and three word counts with density and first-mention position.
Use toolSERP Snippet Preview
See your title and meta description the way Google renders them, measured in pixels. Desktop and mobile, with the exact character your snippet is cut at.
Use toolURL Slug Generator
Turn a list of page titles into clean, readable URL slugs. Accents transliterated, filler words optional, and duplicates caught across the whole list.
Use toolAnchor Text Generator
Build branded, partial, long tail and naked URL anchor variations for any page, then audit the anchors you already have against a natural distribution.
Use toolReadability Checker
Score any text on six readability formulas at once, then see which sentences are dragging the grade up. Passive voice and long sentences broken out separately.
Use toolPerfect cards on pages nobody shares
A share card matters once the page has readers. CrawlRaven crawls the site, joins it to Search Console and GA4, and ranks every technical issue by the traffic it is actually costing you, so the rewrite goes to the page that will notice.