Skip to main content

Open Graph Checker - Reading Your Results

7 min read

You ran a scan and got a wall of meta tags plus five platform previews. Now what? An Open Graph checker like OpenGraph Check gives you more data than a yes-or-no answer. Knowing how to read the results turns a 30-second scan into a confident go/no-go decision before you share.

Short answer

After scanning a URL in an Open Graph checker, review three areas: the tag list (raw og:* values crawlers receive), the platform preview grid (how each network renders your card), and any warnings about missing or invalid fields. Green means required tags exist with valid URLs. Red or empty fields need fixes before sharing. Cross-check the image URL in a browser tab, then confirm with platform debuggers if cache may be stale.

What OpenGraph Check shows you

OpenGraph Check returns four result sections after you paste a URL:

  1. Platform previews - Visual cards for Facebook, LinkedIn, X, WhatsApp, and Discord
  2. Detected tags - Every Open Graph and Twitter Card meta tag found in HTML
  3. Warnings - Missing required fields, relative URLs, or unreachable images
  4. Raw code - The exact <meta> tags extracted from your page

Each section answers a different question. Previews show appearance. Tags show what crawlers read. Warnings show what to fix first.

Reading the tag panel

The tag panel lists property names and content values exactly as they appear in your HTML response.

Required tags to verify

TagWhat a good value looks like
og:titleClear headline, 40-60 characters
og:descriptionSupporting text, 80-125 characters
og:imagehttps:// absolute URL ending in .jpg, .png, or .webp
og:urlMatches the URL you plan to share
og:typewebsite, article, or appropriate type

If any required tag is absent, the checker flags it. Fix on the server before re-scanning.

Optional tags worth checking

  • og:site_name - Brand name above the title
  • og:locale - Language code (en_US, de_DE)
  • og:image:width / og:image:height - Helps platforms allocate layout
  • twitter:card - Should be summary_large_image for image cards
  • twitter:image - Explicit X image if different from OG

Tag reference: Open Graph Tags Explained.

Reading platform previews

Each preview card simulates how that network crops and displays your content.

What to compare across platforms

  • Title truncation - Does the headline cut off mid-word on any network?
  • Image crop - Is important content visible in every crop, especially top and bottom edges?
  • Description length - Does supporting text read clearly or disappear entirely?
  • Domain display - Does the correct hostname appear?

Platforms crop differently. LinkedIn shows taller images. Facebook uses 1.91:1. Design your OG image for the worst crop you see in the grid.

When previews disagree with each other

Small visual differences are normal. Large content differences usually mean:

  • X uses different twitter:* tags than your og:* values
  • Image aspect ratio suits one platform but not another
  • One preview reflects cached data (re-scan after fixes)

Image sizing guide: Open Graph Image Size Guide.

Understanding warnings and errors

Common checker warnings and what they mean:

Missing og:image

No image tag found or value is empty. Social platforms will pick a random page image or show a blank card. Fix: How to Fix a Missing OG Image.

Relative image URL

Value like /images/og.jpg without domain. Many crawlers reject relative paths. Convert to absolute HTTPS URL.

Image not reachable

Checker fetched the image URL and got 403, 404, or timeout. Open the URL manually. Check CDN permissions, auth walls, and hotlink protection.

Missing og:url

Crawlers may associate the preview with the wrong canonical URL. Set og:url to your preferred share link.

Duplicate tags

Two og:title or og:image tags in HTML. Crawlers pick unpredictably. Remove duplicates in theme or plugin config.

Title or description too long

Not always an error, but previews truncate aggressively. Shorten for readability in the preview grid.

Step-by-step - acting on results

1. Start with warnings

Fix every flagged issue before evaluating previews. Missing tags make preview rendering unreliable.

2. Validate og:image manually

Copy the image URL from results. Open in a new browser tab. Confirm:

  • HTTP 200 status
  • Correct image content (not a placeholder or logo fallback)
  • File size under 8 MB
  • Dimensions at least 1200 × 630 px

3. Compare previews to your intent

Ask: "Would I click this card?" If title, image, or description do not match campaign messaging, update tags at the source (CMS, Next.js metadata, etc.) and re-scan.

4. Check page source independently

Right-click → View Page Source. Confirm tags in the checker match raw HTML. Mismatch means the checker cached an old response or your CDN serves different HTML to crawlers.

5. Re-scan after fixes

Deploy changes, purge CDN cache, scan again in OpenGraph Check. Repeat until warnings clear and previews look correct.

6. Confirm with platform debuggers

For high-stakes shares, also run:

Debuggers clear platform cache. The checker shows live tags.

Results for common site types

WordPress blog post

Expect og:type article, featured image as og:image, Yoast or Rank Math as tag source. If image is wrong, check featured image and plugin social override. Guide: Open Graph Tags in WordPress.

Next.js marketing page

Tags come from Metadata API. If missing, check metadata export or generateMetadata function. Guide: Open Graph Tags in Next.js.

E-commerce product page

Look for og:type product, product image URL, and price-related tags if your platform adds them. Verify image is the product photo, not a site logo.

Landing page with redirect

If the checker follows a redirect, confirm final URL matches og:url. Redirect chains can strip tags or point to wrong content.

When results look correct but live share fails

Stale platform cache

Platforms cache previews for days or weeks. Your checker shows current tags, but Facebook still shows old data. Re-scrape in platform debugger. Read Why Social Platforms Cache Link Previews.

Different URL shared

You scanned example.com/page but shared www.example.com/page/. Test the exact URL. Set og:url accordingly.

Crawler blocked

robots.txt or firewall blocks social crawlers but not your checker. Compare user agents and allow Facebook, LinkedIn, and Twitter bots.

A/B test or geo variation

Some sites serve different HTML by region. Scan from the checker's perspective and verify production serves consistent tags globally.

Building a results review habit

For marketers: Screenshot the preview grid for campaign documentation. Attach to content calendar entries.

For developers: Add "OpenGraph Check scan passed" to PR checklist before merging metadata changes.

For support teams: When a client reports wrong preview, scan first, share results, then guide fix based on specific warnings.

Related workflow: How to Test Open Graph Tags.

FAQ

How often should I re-scan?

After every metadata change and before every high-visibility share. Takes under 30 seconds.

Does a clean checker result guarantee a perfect live preview?

It guarantees crawlers receive correct tags now. Platform cache and app-specific behavior can still cause surprises. Private test share recommended.

Why does the checker find tags my SEO plugin hides?

Some plugins output tags only for certain post types or user roles. The checker sees what unauthenticated crawlers see.

Can I share checker results with clients?

Yes. Screenshot previews and tag panel as proof of status before and after fixes.

What if og:title differs from the browser tab title?

Normal. Document <title> and og:title serve different purposes. Social headline can be shorter or more engaging.

Should I fix warnings in priority order?

Yes. Missing og:image first, then unreachable image URL, then missing og:url, then optional optimizations.

Does the checker validate Twitter Card tags separately?

It displays both og:* and twitter:* tags. X falls back to OG when Twitter tags are absent. See Open Graph vs Twitter Card.

Bottom line

Open Graph checker results tell you exactly what crawlers see and how your link will look across platforms. Read warnings first, validate the image URL, review every preview crop, fix issues at the source, and re-scan until clean. OpenGraph Check turns tag debugging from guesswork into a checklist you can finish in minutes.