Open Graph checker
Enter a URL and see the og: and twitter: tags a crawler reads, with a list of what to fix.
- Free
- No account required
Enter a URL to check
The result shows the Open Graph and Twitter tags as a crawler sees them, with anything that looks wrong.
The Open Graph checker fetches the URL you give it and reads the tags a crawler would see: og:title, og:description, og:image, og:url, og:type and the twitter: equivalents. It reports what is missing, what is duplicated, an image given as a relative rather than absolute https URL, and Open Graph written on the name attribute instead of property. It does not predict how any given network will render the card, because each applies its own cropping, length limits and cache.
How to set up Open Graph tags on a page
Open Graph tags are <code><meta property="og:…"></code> elements in the <code><head></code> that networks use to build the card for a shared link. Five steps get the card working in most places.
-
Add the four tags the protocol requires
The Open Graph specification requires
og:title,og:type,og:imageandog:url. Write each with thepropertyattribute and the value incontent. -
Prepare an image with a 1.91:1 ratio
Meta recommends at least 1200 × 630 px, and LinkedIn 1200 × 627 px at the same ratio. A JPG or PNG file up to 5 MB fits the limits of Meta, LinkedIn and X.
-
Add a description, alt text and the X card
Add
og:description,og:image:altdescribing what the image shows, andtwitter:card. X falls back to og: tags when the twitter: equivalents are missing. -
Check the URL with the tool above
Paste the public URL of the page. You will see the tags in the server HTML, which is what a network crawler reads, plus a list of gaps and errors.
-
Refresh the card in the network debugger
Networks cache a card once they fetch it. After changing the tags, paste the URL into Meta Sharing Debugger or LinkedIn Post Inspector so they fetch the page again.
Example Open Graph tags before and after a fix
The URLs are examples on example.com.
<meta name="og:title" content="Pricing plans">
<meta name="og:image" content="/img/pricing.png"><meta property="og:title" content="Pricing plans">
<meta property="og:image" content="https://example.com/img/pricing.png">The specification uses the property attribute. Any network can fetch an image with a full https URL, while a relative path resolves only on your own site.
<meta property="og:type" content="article">
<meta property="og:title" content="How to cut store load time">
<meta property="og:description" content="Five changes that speed up a product page.">
<meta property="og:url" content="https://example.com/blog/load-time">
<meta property="og:image" content="https://example.com/og/load-time.png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="Chart of load time before and after the change">
<meta name="twitter:card" content="summary_large_image">Dimensions in og:image:width and og:image:height help networks lay out the card before they fetch the image.
Common Open Graph tag mistakes
-
The name attribute instead of property
Some networks tolerate
name="og:title", but the specification describes thepropertyattribute. Markup that follows the specification behaves the same everywhere. -
An image on a relative URL or behind a login
The network fetches the image in a separate request from its own servers. LinkedIn lists a site blocking its crawler and a protected directory as common reasons an image does not appear.
-
An image that is too small
LinkedIn shows images narrower than 401 px as a thumbnail, and Meta accepts a minimum of 200 × 200 px. For a large card Meta sets a minimum of 600 × 315 px and recommends 1200 × 630 px.
-
One card for the whole site
The same
og:titleand image on every page make a shared article look like a link to the home page. Every important page needs its own title and description. -
Missing og:image:alt
The Open Graph specification says a page that sets
og:imageshould also setog:image:alt. Describe what the image shows.
Open Graph requirements and image sizes by network
| Value | What it means | Source |
|---|---|---|
| 4 tags | Required by the Open Graph protocol: og:title, og:type, og:image and og:url. | The Open Graph protocol |
| 1200 × 630 px | Image size Meta recommends for high resolution screens, with a ratio as close to 1.91:1 as possible. | Meta for Developers, images |
| 8 MB | Maximum image file size Meta accepts. The smallest allowed dimension is 200 × 200 px. | Meta for Developers, images |
| 1200 × 627 px | Minimum image size according to LinkedIn, with a 5 MB file limit and a 1.91:1 ratio. | LinkedIn Help |
| 5 MB | Image file limit for X cards. Supported formats are JPG, PNG, WEBP and GIF, with no SVG. | X Developer, Cards markup |
| 420 characters | Maximum length of twitter:image:alt, the alt text for the image in an X card. | X Developer, Cards markup |
Sources checked:
Usually because og:image is a relative or http URL. Networks fetch the image in a separate request and several require an absolute https address. The other common cause is caching: many platforms keep the first card they fetched and will not refresh it until you force them through their own debugger.
No, and we deliberately do not promise that. We show the tags and an approximate card layout. Every network crops images differently, truncates text differently and keeps its own cache, so the only reliable preview for a platform is that platform's debugger.
An og:image works best at 1200 × 630 px, a 1.91:1 ratio, as a JPG or PNG file up to 5 MB. A file like that meets the recommendations of Meta, LinkedIn and X at the same time.
What else might come in handy
This test checks one thing on one page
Indexability, metadata and structure, with priorities and a client report.