---
title: "Free Open Graph checker and link preview tester | SEO Skill"
description: "Check any page's Open Graph and X card tags for free. Preview the link on Facebook, X and chat apps, measure the og:image size and file, and find what to fix."
canonical: "https://seoskill.dev/tools/open-graph-checker"
language: "en"
---

# Open Graph checker

Enter a URL to see how the link will look when someone shares it, and which tags or image problems to fix.

### How a share looks

### Checks

### Tags found in the head

| Tag | Value |
| --- | --- |

## Read the Open Graph result

The previews show the link as Facebook and LinkedIn, X and chat apps draw it, from the tags the page has now. Under them, each check has a label.

| Label | What it means |
| --- | --- |
| Fix | The preview breaks or loses its image on at least one platform. |
| Check | It works, but looks worse than it could, or depends on a fallback. |
| Note | Good to know. Often fine as it is. |
| OK | The tag or image meets the platforms' published rules. |

The image card gives the real size, shape and file size of the share image, measured from the file, not from what the tags claim. The tag table lists every Open Graph and X tag found in the head, in order.

## Open Graph image size for each platform

One image at 1200×630 pixels works everywhere. The limits below are from each platform's own documentation.

| Platform | What it needs |
| --- | --- |
| Facebook | At least 200×200. A large card from 600×315. 1200×630 recommended. Up to 8 MB. |
| LinkedIn | 1200×627 or larger, 1.91:1. Up to 5 MB. |
| X | For a large card, at least 300×157, about 2:1. Up to 5 MB. PNG, JPEG, WebP or GIF, not SVG. |
| Chat apps | The same 1.91:1 image. Keep the file small, because some apps skip large images. |

Keep the text and faces away from the edges. Each platform crops a little differently, and a square or tall image is cropped hard to fit a wide card.

## The Open Graph tags to add

These go in the head of every page you expect people to share. Write each one for that page, not one set for the whole site.

```
<meta property="og:title" content="How to brew pour-over coffee">
<meta property="og:description" content="A five-step method with the grind, ratio and timing that work.">
<meta property="og:image" content="https://example.com/images/pour-over-1200x630.jpg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="A glass pour-over brewer on a kitchen scale">
<meta property="og:url" content="https://example.com/guides/pour-over">
<meta property="og:type" content="article">
<meta property="og:site_name" content="Example Coffee">
<meta name="twitter:card" content="summary_large_image">
```

The width, height and alt tags are optional but worth it. Facebook shows the image on the very first share only when it knows the size in advance, and the alt text is read to people using screen readers.

## How link previews are built

When someone pastes a link, the platform's crawler fetches the page, reads the tags in the head and fetches the image. Most of these crawlers do not run JavaScript, so tags added by a script after the page loads are invisible to them. This checker reads the page the same way, so a tag missing here is missing for them too.

Platforms then cache the result, often for days. That is why a fixed page can keep an old preview. X falls back to Open Graph when its own tags are missing, and chat apps mostly use Open Graph alone.

## Fix common link preview problems

-   **No image.** og:image is missing, relative, or points at a file that redirects to a login or returns an error.
-   **Old image or title.** The platform cached it. Refresh it in Facebook's Sharing Debugger or LinkedIn's Post Inspector.
-   **Tiny thumbnail instead of a big card.** The image is under 600×315, or twitter:card is summary rather than summary\_large\_image.
-   **Cropped image.** The image is not close to 1.91:1.
-   **Tags present in the browser but not here.** They are added by JavaScript. Render them on the server.
-   **Blocked crawler.** A firewall or bot challenge can stop platform crawlers. If this checker could not fetch the page, they may not either.

## Why Open Graph matters for search traffic

Open Graph tags do not change where a page ranks in Google. They change what happens after: a page that ranks gets shared in Slack, WhatsApp, LinkedIn and group chats, and a link with a clear title and a sharp image gets clicked more than a bare URL. For many sites, that second wave is a real share of their visits.

Your title and meta description do the same job in Google's results. The [SERP preview](https://seoskill.dev/tools/serp-preview) shows how those look.

## Check Open Graph tags across your site with your agent

One URL tells you about one template. The [seo crawl](https://seoskill.dev/docs/crawl) command checks every page it reaches on your own machine and reports pages with no Open Graph title, description or image, and no X card. Your agent can then add the missing tags to the right template and check one page here before it ships. Ask:

```
Crawl example.com and list the pages missing og:image or twitter:card, grouped by template
```

The crawl runs from the CLI on your machine. Install it and run setup:

```
npm i -g seo && seo start
```

Or add the hosted MCP server to your agent and sign in with Google:

Run it in a terminal, then sign in with Google.

Or run it on your machine

Installs the CLI, signs you in and adds the skill to your agents. Crawls and Bing run this way.

## Open Graph questions