Skip to main content

Open Graph & Social Preview Analyzer

Available
Networking

Check Open Graph tags, Twitter/X Cards, social images, canonical metadata, and social sharing previews for any public webpage, with plain-language fixes for every issue found.

Open Graph & Social Preview Analyzer tool

How this works: when you click Analyze, the URL is sent to DevCraftKit's server, which downloads that public page (and its social images) once and reads its metadata. Pages on private, local or internal networks are refused, JavaScript on the page is never run, and the URL is not stored, logged in full, or sent to analytics.

Only http:// and https:// URLs on public websites (default web ports). Without a protocol, https:// is assumed. Analyze fetches the page from the server.

Enter a public webpage URL to inspect Open Graph tags, social images, Twitter/X Cards, canonical metadata, and social sharing previews.

  • Open Graph and Twitter/X tags, with duplicates and fallbacks
  • Social image availability, size, type and dimensions
  • Canonical, og:url and robots directives
  • Redirects, HTTP status and crawler-access hints
  • Facebook, LinkedIn and X preview approximations
  • Plain-language fixes for every issue found

How link previews work

What this analyzer checks

Enter a public page and the analyzer downloads its HTML once, reads the metadata, and answers two questions: how will this page look when it is shared, and is anything wrong with its social metadata? It covers:

  • Open Graph tags (including repeated og:image tags and duplicates) and Twitter/X Card tags, with the fallback each platform may use
  • Social images: reachability, redirects, file type, dimensions, aspect ratio and size
  • The title, meta description, language, viewport and charset, plus canonical and robots directives
  • Redirects, the HTTP status, and signs that a login or bot protection is in the way
  • Preview approximations in generic, Facebook-style, LinkedIn-style and X-style layouts, each showing which tag every value came from

A minimal set of tags

Most pages need only a handful of tags in the HTML <head>:

<title>Page title</title>
<meta name="description" content="A short summary of the page.">
<link rel="canonical" href="https://example.com/page">

<meta property="og:type" content="website">
<meta property="og:title" content="Page title">
<meta property="og:description" content="A short summary of the page.">
<meta property="og:url" content="https://example.com/page">
<meta property="og:image" content="https://example.com/images/card.png">
<meta property="og:image:alt" content="Describe the image">

<meta name="twitter:card" content="summary_large_image">

See Open Graph meta tags explained for what each tag does, and Twitter/X Card tags explained for the X-specific ones.

Choosing a social image

A 1200 × 630 pixel PNG or JPEG (about 1.91:1), served over HTTPS without a login, suits most large-image cards. Platforms crop and resize differently and publish different limits, so the analyzer rates your image as recommended, acceptable or potentially problematic rather than passing or failing it. More in What size should an Open Graph image be? and How to fix an OG image not showing.

Why previews can look out of date

Social platforms and messaging apps cache link metadata and images. If you changed a tag recently, an older preview can keep appearing until the platform refreshes its copy, regardless of what the page says now. Each platform decides when and how it refreshes, so this analyzer shows what your server delivers today rather than what a platform has stored. If a preview looks stale, first confirm here that the tags are right, then use the platform's own debugging or re-scrape option where one exists. Why is my link preview not showing correctly? walks through it.

What the analyzer cannot see

The analyzer reads the HTML your server sends and does not run JavaScript. Tags that a script adds in the browser will not appear in the results, and most social crawlers do not run scripts either, so such tags usually do not produce previews. It also makes a single request with a neutral user agent, so it cannot tell whether a particular platform's crawler receives a different response, and it never tries to get past logins, CAPTCHAs or bot protection. Treat the previews as approximations and confirm important links in each platform's own tools.

Privacy and limits

Unlike most DevCraftKit tools, this one cannot run entirely in your browser, because browsers are not allowed to read other sites' pages. The URL is therefore sent to DevCraftKit's server, which fetches the public page and its social images and returns the analysis. Private, local and internal addresses are refused; redirects are re-checked at every step; the size and time of each request are limited; and the analyzer is rate limited. The URL is not stored, results are not saved, and analyzed addresses are not sent to analytics. The preview images are loaded by your own browser directly from their hosts.

Did this help you fix a link preview?

If these free developer tools save you time, consider buying me a byte. Your support helps keep DevCraftKit free and growing.

Buy me a byte 💾

Resources

View all

Explore more developer tools

Browse the full collection, or see everything in Networking.

Open Graph & Social Preview Analyzer FAQ

What is Open Graph?
Open Graph is a set of meta tags, introduced by Facebook, that tells platforms how a web page should appear when its link is shared: the title, description, image, address and type of the page. The tags sit in the page's <head> as <meta property="og:..." content="..."> elements. Many platforms and messaging apps read them to build link cards.
What does an Open Graph analyzer check?
It fetches the page, reads the Open Graph, Twitter/X Card, canonical and robots tags and the standard SEO tags, checks the social images and the redirects and HTTP status, and shows how the tags could be turned into a link card. This analyzer also lists what is missing, duplicated or inconsistent, with an explanation and a suggested fix for each finding.
Why is my OG image not showing?
Common causes are a missing or relative og:image URL, an image that returns 403 or 404 to crawlers, an image served over HTTP or from a host that blocks hotlinking, an image that is too small or in a format platforms do not support, tags added only by JavaScript, or an old preview cached by the platform. The Image analysis section shows the status, type, size and dimensions of each image so you can find which one applies.
What is og:title?
og:title is the headline of the link card. If it is missing, platforms may fall back to the HTML <title> or show only the address. It does not have to match the <title> exactly, so you can write a shorter or more social-friendly headline.
What is og:description?
og:description is the one- or two-sentence summary shown under the title. If it is missing, platforms may use the meta description or show no summary. Different platforms truncate it at different lengths, so put the important part first.
What is og:image?
og:image is the URL of the picture shown in the link card. It should be an absolute HTTPS URL to an image that anyone can download without logging in. A 1200 by 630 pixel PNG or JPEG (about 1.91:1) suits most large-image cards, but platforms crop images differently and no single size is required everywhere.
What is og:url?
og:url is the address a page wants to be known by for sharing. Platforms use it to treat several URL variants (with tracking parameters, for example) as one page. In most cases it should match the page's canonical URL; a difference is sometimes intentional and sometimes a configuration mistake, and the analyzer tells the two apart where it can.
What is the difference between Open Graph and Twitter Cards?
Open Graph tags are a general standard read by many platforms. Twitter/X Card tags (twitter:card, twitter:title and so on) are specific to X. X documents falling back to Open Graph tags when Twitter tags are missing, so many sites only add twitter:card to choose the layout and rely on Open Graph for the rest. The analyzer shows which values are explicit and which come from a fallback.
Why does my social preview show an old image?
Platforms cache link metadata and images, often for days. After you change a tag or replace an image at the same URL, the platform may keep showing the old copy until its cache refreshes. Using a new image file name usually helps, and most platforms offer their own debugging tool or a way to request a re-scrape. How and when they refresh is up to each platform.
Can this tool check a private website?
No. It only analyzes public pages that anyone can open without logging in. Localhost, private network addresses, internal host names, URLs with embedded credentials and pages behind authentication are refused, and it does not try to bypass logins, CAPTCHAs or bot protection.
Does this tool execute JavaScript?
No. It reads the HTML that the server delivers, which is also what most social crawlers read. If your tags are added by JavaScript in the browser, they will not appear here and are often missed by crawlers too; render them on the server instead. When a page looks like a client-side app with no metadata, the analyzer points this out.
Why does my page have missing metadata?
Usually because the tags are not in the first HTML response: they are added by JavaScript, the page is a different one from the one you meant to analyze after redirects, the server returned an error or challenge page, or a plugin or template is not outputting them. Check the final URL, the HTTP status and the Raw metadata section to see exactly what was received.
What image size should I use for social sharing?
A common choice is 1200 by 630 pixels (about 1.91:1) as a PNG or JPEG under a few megabytes, with the important content away from the edges because platforms crop differently. Smaller square images work for small summary cards. These are recommendations rather than universal requirements, and the analyzer rates your image against them instead of failing it.
Are the previews exact?
No. They are approximations built from your tags using sensible fallbacks. Real rendering depends on the platform, its crawler, cache state, account type and platform-specific rules, and platforms change their designs. Use them to find problems in your metadata, and confirm important links in each platform's own tools.
Is my URL stored or sent to analytics?
The URL you enter is sent to DevCraftKit's server so the page can be fetched. It is not stored, results are not saved, the full URL is not logged, and it is not sent to analytics. A short in-memory cache may keep a finished analysis of a public page without a query string for about 30 seconds so repeated checks do not hit the same site repeatedly.

Found a bug or an incorrect result in Open Graph & Social Preview Analyzer?

Report it, or suggest an improvement. Messages go straight to the developer.

Send feedback