Open Graph Tester

Free SEO Utility

Open Graph Tester

This open graph tags checker reads a page's existing og: and twitter: meta tags, flags anything missing or misconfigured, checks that your og:image actually loads at a usable size, and shows a live preview of the Facebook and X share card - all before the link goes out. Enter a URL to check a live page, or fill in the fields yourself to build new tags from scratch.

Open Graph & Twitter Card Tester
og: and twitter: tags checked in one pass
Live Facebook, LinkedIn & X Previews
Real share-card simulation
og:image Dimension Checker
Validated server-side, safely

See Your Full SEO Picture

Social tags are just one signal. A full audit checks everything else holding your rankings back.

196+Checkpoints
10Dimensions
FreeNo Card
Try Free Onpage Audit
White Label • Your Brand • Your Domain

Social Share Fields

Control exactly how this page looks when shared on social platforms

10 of 10 AI rewrites left today
0/90 characters

Keep it between 40-90 characters - a hook, not just a restated headline. (og:title)

0/200 characters

Keep it between 100-200 characters for best results. (og:description)

Recommended: 1200×630px (1.91:1 ratio), minimum width 600px. Must be an absolute https:// URL. (og:image)

Accessibility text for the share image. (og:image:alt)

The canonical URL this content should be attributed to. (og:url)

The type of object this page represents. (og:type)

The name of your overall site/brand. (og:site_name)

Language/region of the content. (og:locale)

summary_large_image needs an image set. (twitter:card)

The site's X (Twitter) @username. (twitter:site)

The content author's X (Twitter) @username. (twitter:creator)

Share Preview

How this link will look when shared

Also compatible with:

Facebook & LinkedIn Card

summary_large_image style
Social Tags Health Score
100/100
Title
40-90 chars
Description
100-200 chars
Image
Missing
Type
website
Twitter Card
Valid

HTML Head Tags

Tips for High-Converting Share Cards

Use a 1200×630px og:image - it's the safest fit across every platform.
Keep critical text/logos away from the image edges - platforms crop differently.
Write og:description for a social feed - more conversational than SEO copy.
Always set an absolute https:// og:url, never a relative path.
Re-scrape with Facebook's Sharing Debugger after changing tags on a live URL.
Set twitter:site so shares attribute back to your brand's X account.

What This Open Graph Tags Checker Does

Open Graph tags (often called Facebook meta tags, since Facebook created the protocol) are the og: properties in a page's <head> that tell Facebook, LinkedIn, Pinterest, and other platforms what title, description, and image to show when that page is shared. This tool fetches those tags from a live URL, checks them against social-share best practices, verifies your og:image actually loads at a usable size, and renders a live preview of the resulting share card - so you catch a bad preview before it's public, not after.

It's built for anyone who publishes pages that get shared: SEO professionals running a pre-launch check, agencies doing quality assurance before a client site goes live, developers wiring up meta tags in a CMS template, and marketers or bloggers who just want to confirm a link will look right before posting it. You don't need to know the og: syntax by heart - paste a URL to check what's already there, or fill in the fields manually to build tags for a page that doesn't have any yet.

Title Description Image & og:image size Page URL Content Type Site Name Locale Twitter Card Twitter Handles
Related Tool
Meta Tags Generator
Generate your Google SERP title, meta description, and canonical tags - the SEO counterpart to this Open Graph tester.

How to Check Open Graph Tags on a Page

This is an open graph checker online, so there's nothing to install - the whole process happens in the form above.

  1. 1
    Enter the page URL
    Paste the full URL into the field at the top of the tool, including the https:// scheme.
  2. 2
    Click Fetch Existing
    The checker reads the live page and fills in every og: and twitter: tag it finds. Anything missing is flagged rather than silently left blank, so gaps are obvious at a glance.
  3. 3
    Read the health score and preview
    The Social Tags Health Score and the Facebook/X preview cards translate the raw tags into "will this actually look right when shared."
  4. 4
    Fix, check the image, and copy the tags
    Edit any flagged field, use Check Image to confirm your og:image loads at the right size, then copy or download the corrected HTML and paste it into your page's <head>.

How the Checker Works

Fetching & Parsing

When you fetch a URL, the tool requests that page directly and parses its <head> for og: and twitter: meta properties - the same markup a social platform's own crawler would read. It also falls back to sensible defaults (like your <title> tag) for fields a page hasn't set, so you can see what a platform would probably guess if you left og:title blank.

Validation & Image Size Checking

Title and description lengths are checked against the ranges that tend to display cleanly on social feeds, and og:image is checked separately: the Check Image button fetches the image itself and reports its real pixel width and height, rather than just confirming the URL is present. That distinction matters, because a tag can point at a broken or undersized image and still "exist."

What Your Results Mean

Each of the five pills in the Social Tags Health Score covers one thing you can act on directly:

  • Title / Description - "Optimal" means the length falls in the range that tends to avoid truncation on most feeds; "Short" or "Over" are warnings, not hard failures, since platforms differ slightly in where they cut off text.
  • Image - "Configured (HTTPS)" only confirms the URL format is valid; run Check Image separately to confirm the file actually loads and is sized correctly.
  • Type - flags whether og:type is one of the recognized values (website, article, product, and so on); an unrecognized value can cause a platform to fall back to a generic rendering.
  • Twitter Card - warns specifically when summary_large_image is selected but no image is set, since that combination renders as a broken card on X.

The Facebook and X preview cards below the score are the more important signal in practice - a 100/100 score with an ugly crop or an unreadable title is still worth fixing before you publish.

AudEsto Open Graph Tester vs Other Open Graph Testers

Compare key features, AI copywriting, live preview accuracy, and image validation.

Scroll horizontally to view full comparison
Feature / Capability AudEsto Open Graph Tester Traditional OG Checkers
AI-Powered Social Copywriting1-click rewrite tuned for social engagement, not just SEO Built-in & Free (10/day) None or Paid API Key
Live Facebook, LinkedIn & X Card PreviewsPlatform-accurate share card simulators Real-time, Both Platforms Facebook Only or Static
Server-Side og:image Dimension CheckFetches the real image safely and reports actual pixel size SSRF-Hardened Live Check No Validation
Live Webpage Tag FetcherInstantly extracts existing og:/twitter: tags from any live URL Instant Fetch & Auto-Fill Manual Entry Only
Combined Open Graph + Twitter Card OutputBoth tag families generated together, always in sync Always Included Open Graph Only

Do Open Graph Tags Affect SEO?

Not directly. Google has not listed og: tags as a ranking factor, and there's no evidence they influence how a page is crawled, indexed, or positioned in search results - that's the job of your title tag, meta description, headings, and content, which the Meta Tags Generator covers separately.

Where Open Graph does matter is indirect but real. A page shared with a broken or missing preview gets fewer clicks than one with a clean title, description, and image - and that lost referral traffic is traffic Google never sees an opportunity to reward, because the visit never happened. Treat a passing open graph check as a best-practice fix for social CTR and brand presentation, not as something that will move a keyword's ranking on its own.

A Practical Example

Say you're about to share a freshly published blog post and want to opengraph test it first.

Inputhttps://example.com/blog/site-migration-checklist
Resultog:title and og:description are found and well within range, but og:image is missing - the theme never set one, so Facebook would fall back to the first <img> it can find on the page, which turns out to be a small author avatar.
What it meansThe health score sits around 70/100. Nothing is technically broken, but the share card will look unfinished, and the fallback image is unpredictable across platforms.
ActionAdd a dedicated 1200x630px og:image for the post (not just a hero image cropped awkwardly), run Check Image to confirm the real dimensions, and re-check the page before sharing it.

Real-World Use Cases

  • SEO professionals running a pre-launch or post-migration audit, checking that og: tags survived a CMS or domain change instead of pointing at old URLs and images.
  • Agencies doing client QA before a site goes live, confirming every key template (homepage, product page, blog post) renders a correct share card.
  • Developers wiring up meta tag logic in a CMS or framework template, using the tool to verify the generated markup actually resolves correctly on a real URL.
  • Marketers and bloggers checking a link before scheduling it in a social calendar, so a campaign doesn't launch with a broken or off-brand preview.

Common Mistakes to Avoid

  • Leaving og:image unset and assuming a platform will pick a sensible fallback - it usually won't.
  • Using a relative image or URL path (e.g. /images/share.png) instead of an absolute https:// URL, which most crawlers simply can't resolve.
  • Reusing one tall, portrait-oriented image for og:image across every page - it gets cropped unpredictably in the wide 1.91:1 card format.
  • Assuming a fix is live immediately and not re-scraping the URL with Facebook's Sharing Debugger or LinkedIn's Post Inspector after changing tags on an already-shared page.
  • Copying the exact same og:title on every page of a site (often the brand name alone), which makes every shared link from that domain look identical in a social feed.

Expert Recommendations

  • Set og:image explicitly rather than relying on a platform to pick something reasonable from the page - even if you have a clear hero image, a dedicated share image gives you control over cropping and framing.
  • Write og:description differently from your SEO meta description - social copy can be more conversational and doesn't need to front-load a keyword the way a search snippet does.
  • Re-check key templates after any redesign, CMS migration, or domain change - a template edit that accidentally drops the og:image loop is easy to miss until a share goes out looking wrong.
  • Set twitter:site on every page if your brand has an X account - it's a small tag that consistently attributes shares back to you.

Related SEO Concepts

Open Graph tags sit alongside a few other pieces of a page's metadata that are worth understanding together rather than in isolation. Canonical tags tell search engines which URL is the authoritative version of a page - separate from og:url, which tells social platforms which URL a share should be attributed to; the two often match but serve different systems. Meta descriptions are written for Google's search snippet, while og:description is written for a social feed, which is why this checker treats them as distinct fields rather than mirroring one into the other. And schema.org structured data (JSON-LD) is a third, separate metadata layer again - it doesn't affect share previews at all, but it's what powers rich results in search. If you're setting up a page's metadata from scratch, the Meta Tags Generator handles the SEO side of that same page.

Limitations & Important Considerations

  • This checker reads the tags currently on the page - it can't see what a platform has already cached from a previous scrape. If a preview still looks wrong after a fix passes here, that's almost always a caching issue, not a tag issue.
  • It can't fetch pages that sit behind a login, IP allowlist, or staging password - the URL needs to be publicly reachable, the same requirement a real social crawler has.
  • Character-length and image-ratio guidance here reflect commonly cited best practices, not fixed platform rules - individual platforms adjust their display behavior over time, so treat the health score as a strong indicator, not a guarantee.
1

Title (og:title)

<meta property="og:title" content="...">
Required 40-90 characters

og:title is the headline shown in a share card. It doesn't need to match your page's SEO <title> tag exactly - it can (and often should) be written with a stronger, more conversational hook aimed at getting a click in a social feed rather than a search result.

Do / Don't

  • Lead with the specific hook or benefit, not a generic label.
  • Don't leave it blank - platforms will fall back to an unrelated <title> or nothing at all.

Example

<meta property="og:title" content="Open Graph Tester: Check Your OG Tags Free">
Read byFacebook, LinkedIn, Slack, Pinterest
Fallback source<title> tag
2

Description (og:description)

<meta property="og:description" content="...">
Required 100-200 characters

og:description is the supporting line under the title in a share card. Write it for a social feed - conversational, specific, and benefit-led - rather than reusing dense SEO meta-description copy written for a search snippet.

Do / Don't

  • Mention one concrete detail or benefit from the page.
  • Don't just restate the title in different words.

Example

<meta property="og:description" content="Fetch, validate, and preview your og: and twitter: tags before you publish - completely free.">
Truncation risk~200+ chars on most platforms
3

Image & Alt Text (og:image, og:image:alt)

<meta property="og:image" content="https://...">
Recommended 1200×630px (1.91:1)

The Open Graph image is the picture shown in a share card, and og:image size is one of the most common causes of a broken-looking preview - too small, wrong ratio, or an internal/blocked URL. Use the Check Image button next to the field to fetch the URL server-side and confirm its real pixel dimensions.

Do / Don't

  • Use an absolute https:// URL, at least 600px wide, ideally 1200×630px.
  • Don't put critical text/logos near the edges - platforms crop the image differently.

Example

<meta property="og:image" content="https://example.com/share.png"> <meta property="og:image:width" content="1200"> <meta property="og:image:height" content="630">
Min width600px
Recommended ratio1.91:1
4

Page URL (og:url)

<meta property="og:url" content="https://...">
Recommended

og:url declares the canonical URL this share card belongs to. It should always be an absolute https:// URL - setting it consolidates likes/shares onto one canonical link instead of splitting engagement across tracking-parameter variants of the same page.

Example

<meta property="og:url" content="https://example.com/page">
5

Content Type (og:type)

<meta property="og:type" content="website">
Default: website

og:type tells platforms what kind of object the page represents. Most pages should use website; use article for blog posts and news, and product for e-commerce listings, since some platforms render extra fields (like price) only for matching types.

Common values

Homepage / toolwebsite
Blog postarticle
Product listingproduct
6

Site Name (og:site_name)

<meta property="og:site_name" content="...">
Optional

og:site_name is your overall brand/site name, shown in small text near the domain on some share cards (particularly Facebook). It helps a shared link read as coming from a recognizable source rather than a bare domain.

Example

<meta property="og:site_name" content="AudEsto">
7

Language / Locale (og:locale)

<meta property="og:locale" content="en_US">
Default: en_US

og:locale declares the language and region of the content, formatted as language_TERRITORY (e.g. en_US, es_MX). It's a light signal some platforms use to decide whether to offer a translation of the shared card.

Example

<meta property="og:locale" content="en_US">
8

Twitter Card Style (twitter:card)

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

twitter:card controls the card layout X (Twitter) renders - summary_large_image shows a big banner image (best for most links with a good og:image), summary shows a small square thumbnail beside the text, and app/player are for app installs and embedded media.

Which to pick

Have a wide image?summary_large_image
No image / logo onlysummary
9

Twitter/X Handles (twitter:site, twitter:creator)

<meta name="twitter:site" content="@yourbrand">
Optional

twitter:site attributes a shared card to your brand's @handle; twitter:creator attributes it to the individual author's @handle. Both are purely for attribution on X (Twitter) and have no equivalent in standard Open Graph.

Do / Don't

  • Include the @ symbol, e.g. @audesto.
  • Don't leave both blank on a business site - you lose easy attribution on every share.

Example

<meta name="twitter:site" content="@audesto"> <meta name="twitter:creator" content="@author">

Frequently Asked Questions

An open graph tags checker is a tool that fetches a webpage and reads its existing og: and twitter: meta tags, then reports whether a title, description, image, and other social metadata are present and correctly formatted. It shows you exactly what a shared link will look like on Facebook, LinkedIn, or X before you publish, instead of finding out after a broken preview has already gone out.
Paste the page's URL into the field at the top of this tool and click Fetch Existing. It reads the live page's head section for og: and twitter: tags and fills in the form with whatever it finds - anything missing is flagged so you can see the gap immediately. You can also view a page's raw tags yourself by opening view-source: before the URL in your browser and searching for og:.
An og:image checker verifies that the image referenced in your og:image tag actually loads and reports its real pixel dimensions, separate from just confirming the tag exists. Facebook and LinkedIn recommend roughly 1200x630px (a 1.91:1 ratio) with a 600px minimum width; an image that's too small, oddly cropped, or unreachable is one of the most common reasons a share preview looks broken.
They're the same thing, just two names for it. Facebook meta tags is the informal name people use because Facebook created and popularized the Open Graph protocol; technically they're the og: properties (og:title, og:description, og:image, and so on) defined in a page's head section. LinkedIn, Slack, Pinterest, and most other platforms besides X (Twitter) read the same tags.
Social platforms cache the Open Graph tags from the first time they scraped your URL. Editing your HTML doesn't clear that cache automatically - you need to force a re-scrape using Facebook's Sharing Debugger or LinkedIn's Post Inspector before the corrected preview will show up.
Not directly. Google has not described og: tags as a ranking factor, and they don't influence how a page is indexed or ranked in search results. Their SEO value is indirect: a share card that looks right earns more clicks and referral traffic from social platforms, which can support the kind of engagement and backlinks that do have an SEO effect over time.
Open Graph tags (og:title, og:description, og:image) are the original Facebook-authored standard, now read by LinkedIn, Slack, Discord, and most other platforms. X (Twitter) reads its own twitter: metadata first and only falls back to Open Graph tags when they're missing, which is why this checker always outputs both tag sets together.
The Meta Tags Generator focuses on Google SERP metadata - title tags, meta descriptions, canonical URLs, and robots directives. This Open Graph Tester focuses on social metadata specifically - og: and twitter: tags that control how links look when shared on social platforms. Most pages benefit from using both tools together.
The AI rewrite analyzes your existing title, description, and (when a URL is provided) the live page's actual content, then writes a fresh title and description tuned for social engagement - a stronger hook and more conversational tone than SEO-focused meta tags - within recommended character ranges.

Ready to see how your own page looks when shared? Paste a URL into the field at the top of this page and run the check.