What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To verify a link preview, inspect the page’s server-rendered <head>, run the live URL through a multi-platform checker, and then confirm it with the affected network’s own debugger or inspector. After you deploy metadata or image changes, trigger a fresh scrape and test the URL in a new share composer. This sequence catches incorrect tags, inaccessible images, redirects, crawler blocks and stale platform caches.
What controls a social media preview?
A preview card is built primarily from metadata in the page’s HTML head. The Open Graph protocol defines four required properties for every page: og:title, og:type, og:image and og:url. Recommended additions include og:description, og:site_name, og:image:width, og:image:height and og:image:alt.
X can prioritize its own twitter:* values, while Facebook and LinkedIn generally use Open Graph values and fallbacks. Include both families when you need predictable results across networks.
<meta property='og:title' content='Your page title'>
<meta property='og:type' content='article'>
<meta property='og:url' content='https://www.example.com/article'>
<meta property='og:description' content='A concise description for the card.'>
<meta property='og:image' content='https://www.example.com/images/article-share.jpg'>
<meta property='og:image:alt' content='Description of the share image'>
<meta name='twitter:card' content='summary_large_image'>
<meta name='twitter:title' content='Your page title'>
<meta name='twitter:description' content='A concise description for the card.'>
<meta name='twitter:image' content='https://www.example.com/images/article-share.jpg'>Use one intentional set of values. Duplicate tags from a theme, SEO plugin and application template can leave a crawler choosing an unexpected title, description or image.
#1 Best Overall
Step 1: inspect the live page, not just your template
- Open the published URL. Use the exact protocol, hostname, path and meaningful query string that people will share.
- View the source. Search the
<head>forog:andtwitter:. Browser developer tools show the final DOM, but “View Source” reveals what a non-JavaScript crawler receives initially. - Check the canonical relationship. The
og:urlvalue should be the canonical URL whose metadata you edited. A redirect or a canonical pointing at another page can make a debugger fetch a different document. - Check for duplicates. Keep one deliberate value for each property. Remove stale tags emitted by an old plugin or layout.
- Open every image URL directly. Use an unauthenticated browser session or an HTTP client. The URL should be absolute HTTPS, return the intended raster file, and not require a login, cookie or a redirect that only works for normal visitors.
Metadata added only after client-side JavaScript runs may be invisible to a crawler. Put the important tags in server-rendered HTML or otherwise confirm that the target network executes the rendering path you rely on.
Step 2: run a multi-platform preview check
A third-party checker is useful for seeing how one fetch is interpreted across several networks, but it is a simulation rather than a guarantee of the final card. OpenGraph Check documents checks for tag presence, canonical URLs and redirects, image dimensions, file size and rendered previews for Facebook, X, LinkedIn, WhatsApp, Discord and Slack.
SocialCal’s link-preview guidance is useful for understanding platform-specific tag precedence, especially X’s twitter:* family versus Open Graph fallbacks.
| Check | What it can reveal | Can it force the platform to fetch again? | Account requirement |
|---|---|---|---|
| View Source / browser tools | The HTML and image links your server exposes | No | Not applicable |
| OpenGraph Check | Tag presence, canonical and redirect behavior, image dimensions and file size, plus simulated cards across several networks | Not stated | Not stated |
| SocialCal link previewer | Cross-platform interpretation and tag-family guidance | Not stated | Not stated |
| Facebook debugger | Facebook’s own extraction of the URL | Yes, through its sharing/debugging workflow | Use the service’s current sign-in requirements |
| LinkedIn Post Inspector | LinkedIn’s extracted title, description, image and last inspection state | Yes, its inspect/refresh path | Use the service’s current sign-in requirements |
Compare the checker’s report with the raw source. If the checker sees a different canonical URL, follows a redirect or reports an inaccessible image, fix that server-side before investigating card styling.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Step 3: confirm with the network that matters
The Open Graph specification links to Facebook’s official Object Debugger/Sharing Debugger at ogp.me. Submit the exact live URL, inspect the extracted values and use the debugger’s rescrape action after deployment. The result is more useful than a generic simulator because it reflects Facebook’s own fetch and cache state.
LinkedIn’s Post Inspector provides a URL inspection and refresh path. It shows the title, description, image and the last inspection state. Run it after the new HTML and image are reachable, then paste the URL into a fresh LinkedIn share composer.
X and other networks
Use a checker to compare X’s twitter:* values with the Open Graph fallback, then test the URL in the actual composer. WhatsApp, Discord and Slack can apply their own fetch timing and crop behavior, so a simulated card cannot establish that every network will render identically.
Step 4: refresh stale previews after a change
- Deploy the corrected tags, canonical URL or image.
- Verify the live source and open the image directly without authentication.
- Submit the URL to the affected network’s debugger or inspector and trigger a new fetch.
- Wait for that inspection to complete, then start a new share composer rather than relying on an old draft or message.
- Compare the new card with the inspector output. If it is still old, check whether the debugger actually recorded a new inspection and whether an intermediate redirect or cache still points to another URL.
Changing a file on your server does not automatically invalidate a platform’s stored card. A fresh inspection is the dependable way to request new metadata; the platform may still take time to propagate it.
Why a preview can be wrong even when the tags look valid
- Client-rendered tags: the initial HTML has no metadata and the crawler does not run the JavaScript that inserts it.
- Duplicate tags: multiple plugins or templates publish conflicting titles, descriptions or images.
- Canonical mismatch: the shared URL redirects to, or declares, a different canonical page.
- Inaccessible image: the image requires login, blocks the crawler, returns an error, uses an unsuitable redirect or is not a supported raster file.
- Insufficient image information: missing dimensions or an unsuitable aspect ratio can lead to an empty image area or an unexpected crop. OpenGraph Check can report dimensions and file size, but each network’s final presentation still varies.
- Stale cache: the network is showing an earlier fetch even though the deployment is correct.
- Platform-specific precedence: X may select
twitter:titleortwitter:imagewhile Facebook or LinkedIn selects Open Graph values or a page fallback.
A repeatable release checklist
- One intentional set of Open Graph tags exists in server-rendered HTML.
og:title,og:type,og:imageandog:urlare present.og:urlmatches the canonical URL you intend to share.- Descriptions are present where you want a controlled excerpt.
- X-specific
twitter:card,twitter:title,twitter:descriptionandtwitter:imageare present when X needs independent control. - Image URLs are absolute HTTPS links that work in an unauthenticated session.
- The image response is a supported raster file and has dimensions suitable for the target card.
- Redirects do not require cookies or hide the metadata from crawlers.
- A multi-platform checker reports the intended values.
- The destination network’s own debugger or inspector has fetched the URL after the latest deployment.
- A new share composer shows the updated card.
Or skip the browser setup
For a visual confirmation of a live page, ScreenshotNeo provides a website screenshot API and MCP server. It is not a replacement for checking Open Graph tags, but it can show what the page looks like after your metadata is deployed.
Before capture, ScreenshotNeo accepts the cookie or consent banner like a visitor and removes more than 60 known consent platforms, newsletter popups and chat widgets; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads and cache hits cost nothing, and each response identifies the result with X-Page-Verdict and X-Billed headers. Its MCP server exposes take_screenshot, get_page_info and capture_pdf for Claude, Cursor and other MCP clients.
One-call screenshot
See the complete parameter list in the ScreenshotNeo documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/article -o shot.webpPython
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://example.com/article"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com/article' }); const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);You can request PNG, JPEG, WebP or PDF and use options such as full-page capture with lazy images loaded, a CSS-selector element, dark mode, device presets or a custom viewport, retina scale, custom CSS and JavaScript, click actions, waits, hidden selectors, blocked requests, custom headers, cookies, user agent, Authorization, timezone, geolocation, transparent backgrounds, resizing, a chosen cache TTL, signed image links, asynchronous webhooks, bulk capture of up to 100 URLs per call and the usage API. These options help you inspect a page’s visual state without building your own browser automation.
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 minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallEvery feature is included on every plan: 1,000 screenshots per month are free with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account to capture a page after you have fixed its metadata.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Performance, reliability and cost considerations
Keep the validation path separate from production sharing. A checker or debugger performs a live fetch, so test after deployment rather than on every page view. Make image assets cacheable and stable, but remember that a stable URL can also preserve an old image until the platform fetches again. If you replace an image at the same URL, use the network’s inspector to request a new scrape and verify the result.
Do not treat a successful HTTP response as proof of a correct card. The response must contain the intended server-rendered tags, the canonical URL must be right, and the crawler must be able to retrieve the image without credentials. Conversely, a failed checker request may reflect a bot challenge, timeout or temporary network problem rather than a malformed tag; confirm with the target network’s own inspector before changing content.
FAQ
Does adding og:image:alt change the crop?
No. It supplies descriptive image text for consumers that use it; crop and presentation remain controlled by each network.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsShould I test the URL before publishing?
Test a publicly reachable staging or preview URL only if the crawler can access it. For the dependable result, repeat the inspection against the production URL after deployment, because redirects, authentication and cache state can differ.
Best Value
Can one image guarantee the same card everywhere?
No. Networks can choose different tag families, fallbacks and crop behavior. Verify the network where the link will actually be shared.
Frequently Asked Questions
Does adding og:image:alt change the crop?
No. It provides descriptive text for consumers that support it; each network controls image presentation and cropping.
Can I validate a private staging URL?
Only if the checker and target crawler can fetch it without authentication or a cookie-dependent redirect. Otherwise inspect the publicly reachable production URL after deployment.
Why can two networks show different titles for the same URL?
They may prioritize different metadata families, such as X’s twitter:* tags versus Open Graph values, and may apply different fallback and caching rules.
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.
