Seven platform previews
Google, Facebook, X, LinkedIn, Slack, Discord, and WhatsApp cards are rendered from the tags on the page using the same fallback order each platform applies.
Open Graph & Meta Tag Checker
Paste a URL to read every Open Graph, Twitter Card, and SEO meta tag on the page, see the unfurl on seven platforms, and get the missing tags as a paste-ready snippet.
Seven platform previews built from the real fallback order each network uses.
The share image is probed for actual pixel size, ratio, weight, and reachability.
- Live unfurl previews for seven platforms.
- Graded audit of every meta signal.
- Missing tags returned as a snippet.
How to check Open Graph and meta tags on a URL
Paste a public page URL, read the graded audit, switch between platform previews, then copy the tags you need to add.
- 1
Paste the page URL
Enter the exact URL you plan to share, including the path, because Open Graph tags are per page rather than per site. The checker adds https when you leave the protocol off and follows redirects to whatever URL finally answers.
- 2
Read the score and the audit
The score summarises how many signals passed. The audit groups findings into search essentials, Open Graph, X cards, share image, and technical tags, and every row explains what a platform will do with the value it found or the value it could not find.
- 3
Switch between platform previews
Google, Facebook, X, LinkedIn, Slack, Discord, and WhatsApp each build a card differently. The previews apply the real fallback order, so you can see where a missing twitter:title quietly drops back to og:title and where a small image forces a compact card.
- 4
Copy the tags you need to add
The tags panel lists every tag found on the page with a copy button per row, and the snippet below it contains only the tags that were missing, with placeholder values ready to replace. Paste the block into the head and check the URL again.
Graded tag audit
Around thirty checks cover title and description length, canonical, robots, viewport, language, the full Open Graph set, X card validity, and duplicate tags.
Real share image probe
The declared og:image is fetched from a server to report its true pixel width, height, aspect ratio, format, and weight rather than trusting the numbers in the markup.
Missing tag snippet
Every tag the page lacks is assembled into one paste-ready block with sensible placeholder values, so a gap in the markup turns straight into a fix.
Full tag inventory
Each tag found in the head is listed with its group, its raw value, a duplicate marker where relevant, and a copy button that returns properly escaped HTML.
Copy or export the report
Copy one tag, copy the whole set as HTML, or download the complete result as JSON for a ticket, an audit spreadsheet, or a migration checklist.
Open Graph Checker privacy and processing
These notes cover which server performs the page fetch, how long a result stays in the shared cache, and whether an account is needed to check a URL or copy its tags.
Server-side page fetch
A Rune server requests the URL the way a social crawler would, follows redirects, reads only the head of the returned HTML, probes the declared share image for its real dimensions, and sends the parsed tags back to your browser.
No saved reports
Results live in the open tab and in a short shared fetch cache that expires on its own. Nothing you check is written to an account, a history list, or a permanent record.
Open Graph Checker account access
Checking a URL, switching between platform previews, and copying tags all work without an account, and no sign-in prompt interrupts the normal flow.
Before You Use Open Graph & Meta Tag Checker
These notes explain what a server-side crawl can and cannot see, and why a platform may still show an older card.
Access
Only public pages can be read, since the fetch carries no cookies, session, or login credentials.
Staging URLs behind basic auth, IP allowlists, or a paywall will come back as a failed fetch rather than a report.
Rendering
Tags injected by client-side JavaScript after load are not visible to this fetch or to most social crawlers.
If your framework renders meta tags on the client only, move them into the server-rendered head before sharing the link.
Caching
Facebook, LinkedIn, and Slack cache an unfurl for a long time after the first person shares a link.
Fixing a tag does not refresh an existing card, so re-scrape the URL in the platform debugger after you deploy.
Blocking
Sites behind aggressive bot protection can answer a server request with a challenge page instead of the real markup.
A page that blocks this checker often blocks social crawlers too, which is worth investigating on its own.
Limits
Open Graph & Meta Tag Checker reads one public HTTP or HTTPS page per check and only parses head-level tags, so login walls and bot protection can block the fetch.
Checks are rate limited per address to keep the shared fetcher responsive, and each result is cached briefly so a repeat check of the same URL can return the earlier read.
Questions about Open Graph & Meta Tag Checker
What are Open Graph tags and what do they control?
Open Graph tags are meta tags in the head of a page that tell social platforms what headline, summary, and image to show when someone shares the link. Without them a shared URL usually appears as a bare line of text with no card.
What size should an og:image be?
Use 1200 by 630 pixels for a large card. The absolute minimum most platforms accept is 200 by 200, and files above 8 MB are rejected by Facebook. This checker reports the real dimensions rather than the declared ones.
Why does my link still show an old preview after I fixed the tags?
Platforms cache an unfurl the first time a URL is shared and hold it for days or weeks. Use the Facebook Sharing Debugger, the LinkedIn Post Inspector, or a fresh query string to force a re-scrape once your new tags are deployed.
Do I need both Open Graph and Twitter Card tags?
X falls back to Open Graph when a twitter tag is missing, so the minimum useful addition is twitter:card. Setting twitter:title, twitter:description, and twitter:image is still worth doing when you want different copy on X than on other networks.
Why did the checker fail on my page?
The most common causes are a login wall, a firewall or bot protection challenge, a server that rejects unknown user agents, a non-HTML response, or a page that only renders its meta tags in the browser after JavaScript runs.
Is the URL I check stored anywhere?
The fetch runs on a Rune server and the parsed result is held in a short in-memory cache so a repeated check is fast. Nothing is attached to an account, and the report itself only exists in the tab you are working in.
4.6 (367 ratings)