What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To inspect a social preview, open the exact page you plan to share, view its HTML source, and check the Open Graph tags in the document’s <head>. Start with og:title, og:type, og:image, and og:url; then check the description and any platform-specific card tags. If the tags are missing or differ from what the browser displays, inspect the rendered DOM and use the relevant platform’s preview or refresh tool.
Inspect the page’s original HTML source
- Open the exact URL being shared. A homepage may have different metadata from an article, product page, or campaign landing page.
- Open View Source. In many browsers, use Ctrl+U on Windows or Linux, or Cmd+Option+U on macOS. The label and shortcut can vary by browser.
- Find the document’s
<head>. Search the source forog:to locate Open Graph properties. Open Graph metadata belongs in the document head. - Read the values, not just the tag names. Check that titles, descriptions, URLs, and image links match the page you intend people to share.
View Source shows the HTML delivered for the page. It is a useful first check, but it does not necessarily show markup added later by JavaScript.
Check the Open Graph tags that shape a card
The Open Graph Protocol names four required properties for every page: og:title, og:type, og:image, and og:url. The Open Graph Protocol also describes og:description as optional and generally recommended.
| Property | What to verify |
|---|---|
og:title |
The title intended for the shared page, rather than a generic or outdated title. |
og:type |
The page type declared by the site. |
og:image |
A URL for the image intended to appear in the card. |
og:url |
The URL the page declares as its canonical share URL; compare it with the URL you are sharing. |
og:description |
An optional summary that can provide card text. |
og:site_name |
An optional site name, useful when the publisher’s name should appear in the card. |
Inspect image details when provided
Open Graph supports optional image properties such as og:image:width, og:image:height, og:image:type, og:image:secure_url, and og:image:alt. Check the image URL itself as well as these declarations: a tag can be present while the image is inaccessible to a platform’s fetcher. The protocol says an image should have og:image:alt.
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 & 11#1 Best Overall
Check platform-specific card tags separately
Look for tags such as twitter:card in addition to Open Graph properties when relevant. Checker guidance may display both sets of tags, but do not assume every social network reads the same fields or uses identical fallback rules. A correct Open Graph value alone does not guarantee identical cards across platforms.
Compare source with the rendered DOM
If a tag appears in the browser’s page but not in View Source, the site may add or change it with JavaScript. Open the browser’s developer tools, select the Elements panel, and inspect the rendered document’s <head>. Search for the same og: or twitter: property and compare its value with the original source.
Rank #2
This distinction helps narrow the issue: source inspection checks the HTML initially delivered, while the rendered DOM shows the markup after browser-side changes. A social service may fetch the page differently from your browser, so a tag visible only after JavaScript runs may not be available to its crawler.
Test the URL with the platform that shows the wrong card
After checking the tags, use the relevant network’s own preview, inspection, or refresh tool. For LinkedIn, the cited checker guidance names LinkedIn Post Inspector as a refresh option. Platform tools can expose parsing differences or let you request a new fetch, but their cache behavior and steps are platform-specific.
A local source check confirms what the page declares; a platform preview is the more direct test of what that service fetches and renders. If corrected metadata does not appear immediately, a cached preview is one possible explanation.
Troubleshoot a wrong or missing social preview
- The expected tags are absent from View Source: Check that you opened the exact share URL and inspect the rendered DOM. If the tags exist only after scripts run, the platform may not see them.
- The browser shows updated values but the source is old: The page may populate metadata client-side. Compare the original source and rendered
<head>, then test with the platform’s tool. - The image tag is present, but the card has no image: Check that the image URL is correct and that the audience-facing service can fetch it. The declared dimensions or MIME type may help describe the image, but they do not establish that the URL is reachable.
- The preview still shows old content: Ask the platform to inspect or refresh the URL where its tools allow it. Refresh steps and cache behavior differ by platform.
- One service looks right and another does not: Compare the platform-specific tags and test each service independently; parsing and fallback behavior are not universal.
Or skip the browser setup
If you need a screenshot of the page while investigating how it appears, ScreenshotNeo can capture it with one GET request. Its screenshot response is not a substitute for inspecting metadata tags or a social platform’s own preview.
Quick Recap
Rank #4
ScreenshotNeo API documentation
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo accepts cookie or consent banners before capture and removes known consent platforms, newsletter popups, and chat widgets; these steps can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed. Its MCP server provides screenshot tools for AI agents, and the Free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots. See ScreenshotNeo for the service details. Sign up free for 1,000 screenshots a month, with no card required.
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.
Recommended Free Tools
