To check Open Graph metadata, inspect the page’s delivered HTML, review the <meta> elements in the document <head>, and then confirm the result with the social platform’s preview or debugger. Start with og:title, og:type, og:image, and og:url; then check descriptions, image details, duplicate tags, and canonical URLs.
The fastest reliable workflow
- Open the exact public URL you intend to share.
- Use View Source to see the HTML delivered to crawlers. Use developer tools as a second check of the rendered document.
- Search for
property="og:and record every matching element’spropertyandcontentvalues. - Verify the four required properties:
og:title,og:type,og:image, andog:url. - Check recommended description, site, locale, and image-structured properties.
- Look for duplicate root properties and confirm that the intended value appears first.
- Run the URL through the relevant platform preview or debugger after publishing changes.
This sequence separates three different questions: what your server sends, what a browser renders, and what a social crawler ultimately uses.
What Open Graph metadata contains
Open Graph metadata is a group of HTML <meta> properties in the document <head>. The protocol is designed to let a web page become a rich object in a social graph. Every page should provide four basic properties.
| Property | What to verify | Typical value |
|---|---|---|
og:title |
The title intended for the share card | Your article or page title |
og:type |
The object type | website or an article type |
og:image |
An absolute URL for the share image | https://your-domain.example/images/share.jpg |
og:url |
The canonical URL that identifies the object | The preferred public URL for the page |
Also inspect og:description, og:site_name, and og:locale. These fields help platforms describe the page and identify its site and language context.
#1 Best Overall
Image structured properties
When og:image is present, look for these optional structured properties:
og:image:secure_url— an HTTPS version of the image URL when supplied.og:image:type— the image’s MIME type.og:image:widthandog:image:height— declared dimensions.og:image:alt— alternative text describing the image, not a caption.
Structured image properties belong with the corresponding og:image root tag. If you provide more than one image, keep each image’s structured properties immediately after its root property.
Method 1: inspect the delivered HTML with View Source
View Source is the best first check because it shows the HTML returned by the server, before client-side JavaScript changes the page.
- Open the public page in your browser.
- Right-click and choose View Page Source (the exact wording varies by browser), or use the browser’s view-source: form of the URL.
- Press Ctrl+F on Windows/Linux or Command+F on macOS.
- Search for
property="og:. - Copy each matching
propertyandcontentvalue into a checklist.
A correct tag has the Open Graph property in the property attribute and its value in content, for example:
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →<meta property="og:title" content="A page title">
<meta property="og:type" content="article">
<meta property="og:image" content="https://your-domain.example/images/share.jpg">
<meta property="og:url" content="https://your-domain.example/article">Confirm that the tags are inside <head>, that image and page URLs are absolute, and that the text matches what you want displayed. View Source will not show metadata injected later by JavaScript.
A quick command-line check
For a publicly reachable page, you can save the delivered HTML and search it without opening a browser:
curl -L --max-time 30 "https://your-domain.example/article" -o page.html
grep -oiE '<meta[^>]+(property|name)="og:[^"]+"[^>]*>' page.htmlReview the complete tags manually after the search. A simple pattern search can find tags but cannot tell you whether duplicate values are intentional or whether the resulting card looks correct.
Method 2: inspect the rendered document in developer tools
Developer tools let you inspect the live DOM after scripts, frameworks, and tag managers have run.
- Open the page and press F12 or choose Inspect.
- Open the Elements (or Inspector) panel.
- Expand the
<head>element. - Search the panel for
og:and inspect every matching<meta>element. - Compare the live DOM with View Source.
If a tag appears in Elements but not in View Source, JavaScript added it after the initial response. That difference matters because crawlers may process the delivered source differently from a full browser. If the two views disagree, use a platform parser or debugger to establish what the platform actually fetched.
Method 3: verify the platform’s fetched result
A social platform’s preview tool or debugger is the final check because it shows the result of that platform fetching and parsing your URL. The official Open Graph site references Facebook’s Object Debugger, and platform preview documentation describes inspectors that can re-scrape a URL after edits.
Rank #3
- blogging
- seo
- backlink
- ip address
- marketing
- Publish the corrected metadata on the public URL.
- Open the platform’s preview or debugger for that URL.
- Submit the URL and inspect the title, description, image, and destination shown.
- Use the tool’s re-fetch, refresh, or scrape-again action after a change.
- Compare the preview with the exact values in View Source.
This step catches access, caching, redirects, and parser behavior that local inspection cannot reproduce.
How duplicate properties are interpreted
Open Graph arrays are represented by repeating a root property such as og:image. When conflicting root values exist, the first tag from top to bottom wins. Therefore, put the intended value first and keep its structured properties directly below it.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
<meta property="og:image" content="https://your-domain.example/images/primary.jpg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="A product dashboard">
<meta property="og:image" content="https://your-domain.example/images/alternate.jpg">When a card shows the wrong title or image, search the entire source for duplicate og:title and og:image roots. Common causes include a theme and an SEO plugin both emitting tags, a template adding defaults after page-specific values, or a tag manager inserting a second set.
What each checking method can and cannot tell you
| Method | What it inspects | Duplicate and structured fields | Shows final card preview | Can trigger a re-fetch |
|---|---|---|---|---|
| View Source | HTML delivered by the server | Yes, exactly as sent | No | No |
| Developer tools | Rendered DOM after scripts run | Yes, including injected tags | No | No |
| Platform parser or debugger | What the platform fetched and parsed | Usually, through its result or diagnostics | Yes | Yes, when a refresh or scrape-again control is provided |
Use all three when a share card is wrong: source inspection identifies server output, Elements reveals client-side changes, and the platform tool confirms the crawler’s result.
A repeatable validation checklist
- The URL you tested is the same public, canonical URL you intend to share.
og:title,og:type,og:image, andog:urleach appear.og:imagepoints to the intended absolute image URL.og:urlmatches the URL you want associated with the object.og:description,og:site_name, andog:localeare present when relevant.- Image width, height, type, secure URL, and alt text are attached to the correct image root when used.
- There are no unintended duplicate root tags.
- The intended duplicate value is first when multiple values are deliberate.
- The platform inspector has been run again after the change.
Troubleshooting common Open Graph problems
The share card has no image
Confirm that an og:image tag exists, that its URL is correct and absolute, and that any structured image fields follow that exact root tag. Then run the platform inspector again.
The title or image is wrong
Search for every og:title and og:image in View Source and Elements. If more than one root exists, move the intended value first or remove the unintended emitter. Check both the server source and the rendered DOM because a script may be changing the value.
Recommended Free Tools
The platform associates the share with the wrong URL
Compare og:url with the canonical URL you intend platforms to use. Check redirects and URL variants, then test that exact URL in the platform parser.
View Source and Elements disagree
Source is the delivered response; Elements is the post-script DOM. Identify whether a framework, SEO plugin, or tag manager adds or replaces the tags. Use the platform’s fetched result to decide which representation is being used for the card.
The preview is stale after a fix
Open the platform’s inspector or debugger and explicitly request a new fetch. Do this after the corrected HTML is publicly available; otherwise the platform may continue showing its previous result.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
ScreenshotNeo can capture the rendered page after you update its metadata, so you can verify the visible result without maintaining browser-automation code. It is useful for visual confirmation; use View Source or a parser when you need to read the actual og: values.
Free tools Windows power users keep installed
One-click scans. No signup required.
Best Value
One GET request returns a PNG, JPEG, WebP, or PDF. The API accepts controls for full-page capture, a CSS-selected element, device and viewport settings, retina scale, custom CSS or JavaScript, waits, cookies, headers, user agents, geolocation, timezone, blocking requests, caching, signed links, asynchronous jobs, bulk capture, and more. The ScreenshotNeo documentation lists the parameters.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
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}`);ScreenshotNeo accepts consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be disabled. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and each response reports the outcome in X-Page-Verdict and X-Billed headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
The Free plan includes 1,000 screenshots per month with no card. Paid plans start at Starter: $5 for 3,000 shots; Growth is $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000. Yearly billing gives two months free, and every feature is available on every plan. Create a free ScreenshotNeo account to start checking rendered pages.
Practical reliability and cost notes
For a one-off diagnosis, View Source and a platform debugger are sufficient. For repeated checks, save the raw HTML and the parser result with a timestamp so you can identify when a template or plugin introduced a duplicate. Re-run the platform inspector after deployment rather than relying only on a local browser cache.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11If you automate visual checks with ScreenshotNeo, inspect the response headers: they identify whether the page was cleanly captured and whether the request was billed. Configure a cache TTL when repeated captures do not need a fresh render, and use asynchronous jobs or bulk capture for larger URL sets.
Frequently Asked Questions
Can I check Open Graph tags without changing the page?
Yes. View Source, developer tools, and a platform preview are read-only checks. You only need to publish a change when a tag value, ordering, or URL is incorrect.
When should I keep more than one og:image tag?
Keep multiple image roots only when you intentionally provide an ordered set of alternatives. Put the preferred image first and keep each image’s width, height, type, secure URL, and alt text directly after its own root.
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.
