To find the image a webpage declares for social sharing, inspect its HTML head for <meta property="og:image" content="...">. Copy the URL in content, check the other required Open Graph fields, and then test the page with the social platform’s own debugger. Source inspection tells you what the page publishes; a platform debugger tells you what that platform’s crawler can read and whether its cached preview has changed.
What Open Graph tags do
Open Graph is a metadata protocol that lets a webpage describe itself when another service creates a link preview. The four basic required properties are og:title, og:type, og:image, and og:url. The og:image value is the URL of the representative image for the page.
These values are ordinary meta elements in the document’s <head>. The property name is in the property attribute and its value is in content. An image URL should normally be absolute, such as https://example.com/images/article.jpg, rather than a path that only makes sense relative to the current page.
How to find og:image in a browser
Method 1: View the page source
- Open the published URL in your browser.
- Use View Page Source (often Ctrl+U on Windows/Linux or Option+Command+U in some macOS browsers).
- Search the source for
og:image. - Read the matching
contentattribute. For example:<meta property="og:image" content="https://example.com/media/share-card.webp"> - Copy that complete URL into a new tab to confirm that it resolves to the intended image.
Source view is useful because it shows the HTML delivered by the server. A setting in a CMS is not evidence that the setting reached the published page.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →#1 Best Overall
Method 2: Use developer tools
- Open the page and press F12 or choose Inspect.
- Open the Elements panel.
- Expand the
<head>element, then search forog:imageor use the panel’s find command. - Inspect each matching
metaelement and itscontentvalue.
Developer tools show the current document tree. If JavaScript changes metadata after the initial response, compare this view with View Page Source; some crawlers may process only the server-delivered HTML.
Check every important Open Graph field
Do not stop after finding an image. Record the four basic fields together:
| Property | What to check |
|---|---|
og:title |
The title that should appear in the share card. |
og:type |
The object type declared for the page. |
og:image |
The representative image URL. |
og:url |
The canonical URL associated with the object. |
Open Graph permits additional image properties. When present, inspect og:image:secure_url for an HTTPS image address, og:image:type for the MIME type, og:image:width and og:image:height for dimensions, and og:image:alt for alternative text. The alt property describes the image; it does not replace the image URL.
Check the order of repeated tags
A page can contain more than one og:image. The protocol gives preference to the first value from top to bottom when values conflict. Therefore, an old image listed before the intended image can explain why a platform selects the wrong artwork. Review all occurrences in source order and remove or reorder duplicates in the CMS or template.
Recommended Free Tools
Verify the image itself
- Open the exact URL copied from
content, not a resized thumbnail shown in a CMS. - Confirm that it returns an image rather than an HTML error page, login screen, or redirect loop.
- Check that the image is the one intended for sharing and that its URL is stable.
- Keep platform-specific size, format, access, and cache rules separate from the Open Graph specification. Those requirements vary by service and can change, so consult the target platform’s current official documentation before relying on an exact dimension or format.
A successful browser load proves only that your browser can retrieve the resource. It does not prove that every social crawler can reach it.
Use the platform’s debugger after reading the tags
HTML inspection and platform validation answer different questions. A metadata inspector can parse and display tags, but it cannot by itself prove that a social network can reach your server, download the image, or refresh an already cached preview.
- Choose the platform where the link will be shared.
- Open that platform’s current link-preview debugger or inspector and submit the page URL.
- Review the URL, title, image, and any fetch or parsing errors reported by the platform.
- After correcting the page, run the platform check again. A result may still reflect a cached preview until the platform refreshes it according to its own rules.
The Open Graph protocol site identifies Facebook’s Object Debugger as its official parser and debugger. Use the target service’s own current tool for platform-specific validation rather than treating a generic tag checker as a crawler test.
Why the wrong image appears
Another og:image comes first
Search the complete head for duplicates. Because the first value has preference in conflicts, an obsolete tag generated by a theme, plugin, or template may win. Remove the duplicate or place the desired image first.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The tag is not in the published head
A CMS control can be configured correctly while the live template omits it. Inspect the actual page source, then check the CMS or theme output responsible for the head. Publish the change and inspect the public URL again.
The crawler cannot fetch the page or image
A browser session may have cookies, authentication, JavaScript execution, or network access that a social crawler does not. Use the platform debugger to see whether its fetch failed, and verify that both the page URL and image URL are reachable without an interactive login.
The platform is showing an old cache
Correct tags do not automatically prove that an existing share preview has been refreshed. Submit the URL to the platform’s debugger after publishing the fix and follow that platform’s current cache-refresh guidance.
The image URL returns the wrong content
Redirects, permissions, hotlink protection, a missing file, or a server error can make an apparently valid URL unusable. Open the URL directly and inspect the debugger’s fetch result. Fix the response at the image host, then validate again.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Inspecting many pages
For a one-off check, source view and the target platform debugger are usually enough. For repeated CMS publishing, configure social metadata in the CMS’s social settings, publish a representative page, and verify the emitted HTML rather than trusting the setting alone. A third-party inspector can make repeated parsing faster, but treat its output as a view of metadata, not proof of crawler access or cache refresh.
Or skip the browser setup
ScreenshotNeo can capture a page after you have checked its metadata, which is useful when you need a visual record of the rendered result. Its API also handles the browser work that makes repeated checks tedious. Before capture it accepts the cookie or consent banner like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status in X-Page-Verdict and X-Billed headers. It also provides an MCP server for AI agents, including Claude, Cursor, and other MCP clients.
For a direct screenshot of a page, use this GET request (replace the URL and key):
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}`);See the ScreenshotNeo documentation for request options. The service supports full-page captures with lazy images loaded, CSS-selector element captures, dark mode, device and viewport settings, retina scale, PDF output, custom CSS and JavaScript, clicks, waits, blocked resources, headers, cookies, user agents, authorization, timezone and geolocation, transparent backgrounds, resizing, configurable caching, signed links, asynchronous webhooks, bulk capture of up to 100 URLs per call, usage data, and an OpenAPI specification. Parameter names used by other screenshot APIs also work, which can simplify migration.
The Free plan includes 1,000 screenshots per month without a card. Paid plans start at $5 for 3,000 shots; every feature is available on every plan. Create a free ScreenshotNeo account to try it.
Best Value
Troubleshooting checklist
- No
og:imagefound: inspect the raw source, confirm the tag is inside<head>, and verify that the published template emits it. - Several images found: compare their order; move the intended image to the first position or remove obsolete tags.
- Image opens for you but not in the debugger: check redirects, access controls, hotlink protection, and the debugger’s fetch error.
- Tags are correct but the preview is unchanged: run the target platform’s debugger and follow its cache-refresh process.
- Alt text is required: add
og:image:altwith a concise description of the image. - Exact dimensions or formats are unclear: do not infer a universal rule; check the destination platform’s current documentation.
FAQ
Is og:image the same as an HTML image?
No. It is a document-head declaration that tells sharing systems which image represents the page. It is separate from an in-body <img> element.
Can a tag checker guarantee a social preview?
No. It can parse metadata, while the platform’s own debugger is needed to investigate crawler access and platform-specific preview behavior.
What should I do when a CMS shows the right social image?
Inspect the live page source and validate the public URL. The CMS control matters only if it produces the expected tags in the published HTML.
Free tools Windows power users keep installed
One-click scans. No signup required.
Frequently Asked Questions
Is og:image required?
The Open Graph protocol lists og:image among its four basic required properties: og:title, og:type, og:image, and og:url.
Why does the first image tag matter?
When multiple values conflict, Open Graph preference goes to the first value in document order.
Does og:image:alt replace the image URL?
No. It supplies alternative text; og:image still identifies the image resource.
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.
