Sharing Debugger Tool: Free Open Graph and Meta Tags Validator

To check how a page will appear when someone shares it, run the public URL through an Open Graph debugger, inspect the extracted og: values, and compare the result with your intended card. Start with the four required properties—og:title, og:type, og:image, and og:url—then verify optional description and image fields. A debugger reports what its fetcher can read; it cannot guarantee that every social network will render an identical card.

What a sharing debugger actually checks

Open Graph metadata is placed in a page’s HTML <head>. It tells a social platform what the page represents when its URL is pasted into a post or message. The official specification explains: “To turn your web pages into graph objects, you need to add basic metadata to your page.”

#	Preview	Product	Price
1		Social Media Marketing All-in-One For Dummies	$21.93	Buy on Amazon
2		Social Media Marketing for Small Business Made Simple: :: Build Your Audience, Gain Trust and Turn...	$16.99	Buy on Amazon
3		Social Media Marketing Workbook: How to Use Social Media for Business	$47.85	Buy on Amazon
4		500 Social Media Marketing Tips: Essential Advice, Hints and Strategy for Business: Facebook,...	$11.49	Buy on Amazon
5		One Million Followers, Updated Edition: How I Built a Massive Social Following in 30 Days	$6.66	Buy on Amazon

A debugger fetches the URL as an automated visitor, parses the response, and displays the tags it found. Many tools also draw a simulated card. Treat that drawing as a diagnostic preview, not a promise that Facebook, LinkedIn, or another service will use exactly the same crop, font, truncation, or layout.

The Open Graph tags to validate

The Open Graph protocol lists four basic properties as required for every page. Put one value for each in the document head.

#1 Best Overall

Sale

Social Media Marketing All-in-One For Dummies

$21.93

Buy on Amazon

The specification describes og:description and og:site_name as optional properties that are generally recommended. Image metadata can be expanded with og:image:secure_url, og:image:type, og:image:width, og:image:height, and og:image:alt. The specification says an image should have alternative text when og:image is present. Locale, audio, and video are additional optional properties.

When multiple values for a property are supplied, the first tag takes precedence when values conflict. This matters when a CMS plugin emits one title and a theme emits another.

How to use a free Open Graph debugger

1. Open the exact public URL. Use the URL that is actually being shared, including its protocol, path, and meaningful query string. A checker cannot inspect a page that requires a login or blocks automated requests.
2. Run the address through a debugger. The Liinks Free Open Graph Debugger provides extracted values and a rendered preview. Paste the URL, submit it, and wait for the fetch to finish.
3. Check the required values first. Confirm that og:title, og:type, og:image, and og:url are present and contain the intended values. A missing property is a metadata problem even if the page looks correct in your browser.
4. Review optional and structured fields. Check the description, site name, image dimensions, MIME type, secure image URL, and image alternative text where your implementation provides them.
5. Compare the simulated card with the design. Look for a wrong title, stale description, unexpected image, or an image crop that hides important content. Keep in mind that a simulation is not a cross-platform rendering guarantee.
6. Recheck after changing the HTML. If a previously shared URL still shows old information, use the relevant platform’s current debugger or refresh control to request a new fetch, then inspect the URL again. The Liinks guidance specifically describes Facebook and LinkedIn debugger tools as mechanisms that can trigger re-scraping; interface names and requirements can change.

Inspect the source yourself before blaming the debugger

A browser’s rendered document can differ from the initial HTML returned to a crawler. View the page source, search for og:, and verify that tags are inside <head> rather than injected only after client-side JavaScript runs. A minimal set looks like this:

Rank #2

Social Media Marketing for Small Business Made Simple: :: Build Your Audience, Gain Trust and Turn Followers into Profitable Customers

$16.99

Buy on Amazon

<head>
  <meta property="og:title" content="Example article title">
  <meta property="og:type" content="article">
  <meta property="og:url" content="https://example.com/article">
  <meta property="og:image" content="https://example.com/images/article.webp">
  <meta property="og:description" content="A concise description of the article.">
  <meta property="og:site_name" content="Example">
  <meta property="og:image:alt" content="Description of the preview image">
</head>

Use fully qualified HTTPS URLs for the page and image. If your CMS produces duplicate tags, remove the unwanted source so the first value is not accidentally selected.

Image size, format, and accessibility checks

The Open Graph specification requires an image URL but does not establish one universal pixel size. Liinks recommends an image of 1,200 × 630 pixels and a file below 5 MB for its debugger use case. Those are tool guidance, not protocol-wide requirements. Use the dimensions and file-size limits documented by the platform where the card will appear if that platform supplies them.

• Confirm that the image URL returns an image rather than an HTML error page or a login redirect.
• Make sure the server permits the social crawler to request the file and does not require a session cookie.
• Provide og:image:alt that conveys the image’s meaning; do not repeat a keyword list.
• Check that the image’s important text remains visible in the simulated crop.

Why a preview can be wrong even when your tags look right

Cached metadata

Platforms may retain a previously fetched title, description, or image. Changing the HTML does not necessarily replace that stored result immediately. Trigger a re-scrape with the platform’s current debugging or refresh workflow and then test the exact URL again.

Rank #3

Social Media Marketing Workbook: How to Use Social Media for Business

$47.85

Buy on Amazon

The fetcher cannot reach the page

Authentication, an IP allowlist, robots or firewall rules, bot protection, a slow origin, and a redirect chain can prevent a third-party fetcher from seeing the head. Test the URL in an unauthenticated session and inspect server logs for the crawler request. A page that works only after JavaScript executes may expose no usable tags in the initial response.

Different platforms apply different presentation rules

Even with identical extracted tags, services can crop images differently, truncate text at different lengths, or choose a different card layout. Use a debugger to identify metadata errors, then verify important campaigns on each platform where they will run.

Choosing a validation workflow

Troubleshooting common debugger failures

Or skip the browser setup: capture a clean visual check with ScreenshotNeo

ScreenshotNeo is a screenshot API and MCP server, not an Open Graph tag validator. It is useful when you also need a repeatable image of the page as a visitor sees it—for example, to confirm that a consent banner, newsletter popup, or chat widget is obscuring the content you expect to share. It accepts the page URL and returns PNG, JPEG, WebP, or PDF; it does not replace inspecting the source tags or a social platform’s own cache.

One GET request is enough:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Python:

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

Node.js:

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

See the ScreenshotNeo documentation for authentication and all options. Before capture, it can accept the cookie or consent banner and remove more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be disabled. Responses identify the page verdict and whether it was billed in X-Page-Verdict and X-Billed headers. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed.

For automated workflows, ScreenshotNeo provides an MCP server with take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. It also supports full-page lazy-image loading, CSS-selector element capture, dark mode, device presets, custom viewports, retina scale, PDF controls, custom CSS and JavaScript, clicks before capture, waits, request blocking, headers, cookies, user agents, authorization, timezone, geolocation, transparent backgrounds, resizing, selectable cache TTLs, signed links, asynchronous jobs with signed webhooks, bulk capture for up to 100 URLs per call, usage reporting, and an OpenAPI specification. Parameters used by other screenshot APIs also work, which can simplify migration.

Rank #4

Sale

500 Social Media Marketing Tips: Essential Advice, Hints and Strategy for Business: Facebook, Twitter, Instagram, Pinterest, LinkedIn, YouTube, Snapchat, and More!

$11.49

Buy on Amazon

Yearly billing provides two months free, and every feature is included on every plan. Create a free ScreenshotNeo account to get 1,000 screenshots a month with no card.

A practical pre-share checklist

• The URL is publicly reachable without a login.
• og:title, og:type, og:image, and og:url appear once with intentional values.
• The description, site name, image dimensions, MIME type, secure URL, and alternative text are correct where supplied.
• The image URL works independently for an unauthenticated fetcher.
• The debugger’s extracted values match the intended page, not a staging or redirected URL.
• After edits, the relevant platform has been asked to fetch the URL again if its cache held old data.
• The live destination has been checked on each important platform because simulated cards are not universal guarantees.

Frequently Asked Questions

Does Open Graph replace standard SEO metadata?

No. Open Graph describes a page for social graph previews. Keep the page title, description, canonical link, structured data, and other metadata required by your search and accessibility workflows.

Should every page use og:type set to article?

No. Choose the object type that accurately represents the URL. An article page and a general website page can use different types.

Best Value

One Million Followers, Updated Edition: How I Built a Massive Social Following in 30 Days

$6.66

Buy on Amazon

Can a debugger validate pages behind a login?

Not reliably. A third-party fetcher can report only what it is allowed to reach, so provide a genuinely public URL when testing a share card.

Is 1,200 × 630 pixels mandatory for an Open Graph image?

No. The protocol does not set a universal size. Liinks recommends 1,200 × 630 pixels for its debugger use case; follow the current requirements of the platform where you will publish.

Quick Recap

SaleBestseller No. 1

Social Media Marketing All-in-One For Dummies

$21.93

Bestseller No. 2

Social Media Marketing for Small Business Made Simple: :: Build Your Audience, Gain Trust and Turn Followers into Profitable Customers

$16.99

Bestseller No. 3

Social Media Marketing Workbook: How to Use Social Media for Business

$47.85

SaleBestseller No. 4

500 Social Media Marketing Tips: Essential Advice, Hints and Strategy for Business: Facebook, Twitter, Instagram, Pinterest, LinkedIn, YouTube, Snapchat, and More!

$11.49

Bestseller No. 5

One Million Followers, Updated Edition: How I Built a Massive Social Following in 30 Days

$6.66

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.