Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
A sharing debugger checks the metadata a fetcher can read from a page and helps you diagnose a link preview that is missing or outdated. Start with the exact public URL you plan to share, inspect its Open Graph values, and then compare a preview with your intended card. A preview is a diagnostic, not a promise that every social platform will render the page identically.
What a sharing debugger checks
Open Graph (OG) tags are metadata in a webpage’s HTML <head>. They describe the page as an object that can be represented in a social graph. A sharing debugger fetches a URL and reports metadata it can access; some tools also show a simulated share-card preview or warnings.
The Open Graph protocol says, “To turn your web pages into graph objects, you need to add basic metadata to your page.” Its four required basic properties are og:title, og:type, og:image and og:url. The protocol describes og:description and og:site_name as optional properties, along with optional locale, audio and video properties. See the Open Graph protocol specification.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsChecking tags and checking how a browser draws the page are different tasks. A sharing debugger reports metadata its fetcher can read; a screenshot shows rendered pixels. A screenshot can help inspect the page’s appearance, but it does not replace a tag validator.
#1 Best Overall
How to validate a page’s Open Graph tags
- Use the URL that will actually be shared. Check the public, canonical page address—not just a homepage or a local development URL. A debugger can only inspect what its fetcher can reach.
- Run the URL through a debugger. For a multi-platform preview and tag check, Liinks provides a free Open Graph debugger. Review the extracted values, not only the visual mock-up. If you are diagnosing a particular platform’s cached preview, use that platform’s own current debugger or refresh workflow where available.
- Check the four required properties. Confirm the title is the one you intend to share, the type describes the object, the image URL points to the intended representative image, and the URL is the canonical address for that object.
- Review optional and structured image fields. Check that the description is useful and that the site name is appropriate. If you provide image dimensions, MIME type, a secure URL or alternative text, make sure each value describes the image correctly. The specification says an image should specify alternative text when
og:imageis present. - Compare the preview with the intended card. Treat the rendered card as a useful diagnostic of that tool’s simulation. Do not assume it guarantees identical appearance on every live platform.
- After editing, fetch again. If the debugger now sees corrected tags but a platform still shows the old card, cached preview data may be involved. Use that platform’s current refresh mechanism and inspect again.
Example of tags in the page head
Adapt the values to the specific page. The URLs below are examples, not values to copy blindly.
<head>
<title>Page title</title>
<meta property="og:title" content="Page title">
<meta property="og:type" content="website">
<meta property="og:image" content="https://example.com/social-card.jpg">
<meta property="og:url" content="https://example.com/page">
<meta property="og:description" content="A concise description of this page.">
<meta property="og:site_name" content="Example Site">
<meta property="og:image:alt" content="A description of the social card image">
</head>The basic properties are protocol requirements; description and site name are optional. Image alternative text is structured image metadata, not a replacement for the image itself. Ensure the og:url reflects the permanent object URL you intend platforms to associate with the page.
What to do when the preview is wrong
The title or description is missing or incorrect
Look at the extracted tag values in the debugger. If the values are absent or stale, correct the metadata in the page’s head and fetch again. Do not infer that the page source is correct just because its visible headline looks right: visible page content and metadata are separate things.
Rank #2
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
The image is absent or not the intended image
Check the extracted og:image URL and whether it points to the expected representative image. Then consider whether the page and image are reachable to the platform’s fetcher. The cited sources establish that blocked or inaccessible pages can prevent third-party inspection; they do not provide a universal diagnosis for every image-loading failure. Image dimensions, MIME type, secure URL and alt text can be supplied as structured image details, but the specification does not set a universal image size.
Liinks recommends an image of 1200 by 630 pixels and a file below 5 MB for its debugger use case. Treat that as Liinks’ guidance, not a protocol requirement or a guarantee that every platform will display the image the same way.
The debugger cannot inspect the page
A page that requires a login or blocks automated requests may not be inspectable by a third-party fetcher. Confirm that the URL is publicly reachable and that automated requests are not blocked before treating the result as proof that the tags are missing. A debugger can report only what its fetcher can access.
Rank #3
The platform still shows an old card after a fix
Cached metadata can persist after a site owner changes tags. The Liinks debugger page describes platform debugger re-scraping for Facebook and LinkedIn. The available controls and labels can change, so confirm the current steps in the platform’s own documentation rather than relying on an old menu path. Fetch the page again after refreshing so you can distinguish an updated scrape from a stale preview.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →How to choose the right debugger
Choose a checker based on the platform and the evidence you need. An official platform debugger is the relevant place to investigate that platform’s own cache or scrape behavior. A multi-platform preview interface is useful for comparing simulated card layouts. For either kind, inspect raw tag values as well as the rendered preview when the tool exposes both.
- Platform-specific cache issue: use the affected platform’s current debugger or refresh mechanism.
- General tag audit: use a checker that exposes the extracted OG values, not just a mock card.
- Cross-platform design check: use preview simulations as comparisons, not guarantees of live rendering.
- Fetch failure: first establish that the exact URL can be accessed by automated fetchers.
The available information supports these decision criteria, but not a current ranked comparison of multiple debugger products. Meta’s official debugger interface and behavior are not specified here, so verify those details in Meta’s current documentation rather than assuming particular labels or login requirements.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
Or skip the browser setup
If you also need a rendered capture of the page—for example, to inspect whether its visible layout matches your intended share card—a screenshot API can capture the page, but it does not validate OG tags. ScreenshotNeo is a separate website screenshot API and MCP server, not a metadata debugger. One GET request can return a PNG, JPEG, WebP or PDF. The API supports 63 options, including full-page capture, CSS-selector element capture, device and viewport settings, custom CSS and JavaScript, wait conditions, and PDF options.
Use the exact API example below to capture the page image; replace only the target URL. The API key is required. See the ScreenshotNeo API documentation for request options and response details.
Recommended Free Tools
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpScreenshotNeo accepts cookie and consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups and chat widgets before capture; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and responses identify the page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info and capture_pdf for AI agents including Claude, Cursor and other MCP clients. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Every feature is on every plan. For the product and plan details, visit ScreenshotNeo.
Sign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common problems and fixes
| Symptom | Likely consideration | What to do |
|---|---|---|
| No metadata appears | The fetcher cannot access the URL, or the page does not expose the tags it needs. | Check that the exact page is public and review the fetched tag values. |
| Title or image differs from the intended card | The extracted metadata may not match the intended values. | Correct the relevant tag and fetch the page again. |
| Debugger looks right, live share is old | The platform may retain cached metadata. | Use that platform’s current debugger or refresh workflow, then inspect again. |
| One preview looks different from another | Preview interfaces simulate layouts; their results do not guarantee identical live rendering. | Check the platform where the link will be shared and treat each simulation as a diagnostic. |
| Image sizing is uncertain | The Open Graph specification reviewed here does not set a universal image size. | Follow the target platform’s current requirements; Liinks’ 1200 × 630 pixels and below-5-MB suggestion is guidance for its tool use case, not a protocol rule. |
Practical checklist before sharing
- The exact public URL is the one being checked.
og:title,og:type,og:imageandog:urlare present and appropriate.- Optional description and site-name metadata are useful and accurate.
- Image URL and any supplied structured image details match the intended image.
- The debugger can fetch the page, and the preview is treated as a simulation rather than a cross-platform guarantee.
- If a platform shows old data, its current refresh workflow has been checked.
Frequently Asked Questions
Can a sharing debugger guarantee the exact card everyone will see?
No. A tool’s rendered preview is a diagnostic simulation; live rendering can differ by platform.
Is 1200 × 630 pixels an Open Graph protocol requirement?
No. That size is Liinks’ recommendation for its debugger use case; the specification does not establish a universal image size.
Does a screenshot API validate Open Graph tags?
No. A screenshot captures rendered pixels. Use a metadata debugger to inspect the tags a fetcher can access.
Quick Recap
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.
