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 reinstallIf a shared link preview cuts off its title, check the page’s Open Graph metadata, choose a properly sized social image with safe margins, make sure the platform can fetch it, then refresh that platform’s cached preview. If the title is cropped on the website itself—not in a share card—the likely fix is in the site’s theme or image component.
First identify where the crop happens
Copy the exact URL shown in the faulty preview and check whether the problem appears in a social or messaging app, or on the website itself. Facebook, LinkedIn, X, WhatsApp and other services assemble link cards from page metadata and their own display rules. A crop inside the page is usually controlled by the site’s layout or image component, not by social metadata.
As an Amazon Associate I earn from qualifying purchases.
- Shared-link preview: Follow the metadata, image, crawler-access and cache steps below. The same page can look different across platforms.
- Image on the site: Inspect the theme or component’s image-fit, aspect-ratio and focal-point settings. Check the image at the affected screen width; changing Open Graph tags will not repair an on-page crop.
Check the metadata the platform receives
Inspect the page’s rendered source or the social-preview fields in your content management system. Confirm that og:title, og:image, og:description and og:url contain the intended title, image, description and canonical page URL. LinkedIn lists these four Open Graph properties for website sharing in its website-sharing guidance. WordPress.com says posts and pages automatically use og:title, og:description and og:image for social previews (WordPress.com Support).
Changing the visible headline on the page does not necessarily change the title in a shared card. Make sure the Open Graph title is the one you want people to see, and confirm the image URL points to the intended share image rather than an unrelated page image or old asset.
#1 Best Overall
Prepare an image that survives different card layouts
Use a dedicated landscape image for sharing instead of relying on a platform to crop a portrait image or a page screenshot. The recommendations below are platform guidance, not guarantees that every app will display the whole image.
| Guidance | Recommended image details |
|---|---|
| LinkedIn website sharing | Minimum 1200 × 627 px, recommended 1.91:1 ratio, maximum 5 MB. LinkedIn’s guidance page does not specify a publication or update date and says it was last updated approximately two years before retrieval. Source |
| WordPress.com general social-preview guidance | 1200 × 630 px, approximately 1.91:1, JPG or PNG, under 5 MB. The guide was reviewed August 11, 2026. Source |
| WordPress.com Facebook thumbnail guidance | 1200 × 630 px for high-resolution display; 1.91:1 image ratio. The guide was reviewed August 12, 2026. Source |
Keep the title and other important details near the center, not tight to the edges. WordPress.com Support’s instruction is: “Center important content: Prevent cropping on smaller viewports.” Preview the image in the target platform’s card layouts where possible; smaller viewports and different placements can crop differently.
Rank #2
- Intuitive interface of a conventional FTP client
- Easy and Reliable FTP Site Maintenance.
- FTP Automation and Synchronization
Make the intended image explicit and accessible
Set the desired featured or social image for the specific page rather than assuming a platform will select the right one. On WordPress.com, a post or page’s featured image is the normal source. If it is missing, social networks may choose a gallery or slideshow image, another image on the page, an external image, a profile photo or other imagery (WordPress.com Support).
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 errorsAlso check that the image URL loads without requiring a login or access to a protected directory, and that the site is not blocking the platform’s crawler. LinkedIn notes that a protected image location or blocked retrieval can prevent an otherwise valid image from appearing (LinkedIn Help).
Rank #3
Refresh the preview after correcting the page
Platforms may keep an earlier title or image in a cache. After publishing the metadata or image correction, use the relevant platform tool to request a fresh preview:
- Facebook: WordPress.com directs users to Facebook Sharing Debugger and its “Scrape Again” control to request a new preview.
- WhatsApp: WordPress.com says WhatsApp uses Facebook’s preview system, so refreshing through Facebook’s tool may help.
- LinkedIn: Use Post Inspector to inspect the URL preview.
- X: WordPress.com says X re-indexes card tags roughly every seven days; this is its platform-specific troubleshooting guidance, not a universal cache duration. Source
If the refreshed card still shows the old image, verify that the metadata points to the corrected image URL and that the image can be fetched. A platform may continue to display its previously cached card until it re-reads the page.
Rank #4
LinkedIn Page posts can use a post-level override
If you are publishing a URL post as an eligible LinkedIn Page admin, LinkedIn provides an in-composer option to replace the preview image or article title for that post. Paste the URL, open the edit control, and choose the override. LinkedIn’s guidance recommends 1200 × 627 px at 1.91:1; images must be more than 200 pixels wide for the larger format. It says mobile images are not cropped and other ratios are shown in full with subtle white padding. See LinkedIn’s Page-post instructions.
Free tools Windows power users keep installed
One-click scans. No signup required.
This changes that LinkedIn Page post; it does not replace correcting the page metadata for other platforms and future shares.
Best Value
Troubleshoot common causes
- The card shows the page headline, not the intended share title: Check
og:titlein the rendered page and the CMS social-preview field. Refresh the platform’s cached card after correcting it. - The wrong image appears: Confirm
og:imagepoints to the right file and explicitly set the page’s featured or social image. Do not rely on fallback image selection. - The image is missing: Test whether the image URL is publicly reachable. Check for protected directories or rules that block platform image retrieval.
- The title is readable on desktop but clipped on mobile: Move text and key graphics away from image edges and preview smaller layouts. Use a landscape share image close to the destination platform’s recommended ratio.
- The page is fixed but the card is stale: Request a new scrape or inspection with the relevant platform tool, then allow for that platform’s cache behavior.
- The crop appears only on the site: Adjust the theme or component’s crop and focal-point settings; social-card metadata is not the control for an on-page image.
Optional: manage WordPress social metadata per page
WordPress.org lists the Social Preview and Open Graph Tags plugin as an option for controlling Open Graph and X/Twitter Card titles, descriptions, URLs, images and fallback images. Check its current maintenance and compatibility with your WordPress installation before using it; not every site needs an additional plugin if its theme or existing tools already provide these fields.
Or skip the browser setup
If you need a screenshot of the corrected page to check its appearance, ScreenshotNeo can return a screenshot or PDF from one request. Its clean-shot flow accepts consent banners and removes more than 60 known consent platforms, newsletter popups and chat widgets before capture; those steps can be turned off. Bot checks, blank pages, timeouts, failed loads and cache hits cost nothing, and response headers identify the page verdict and billing status. It also offers an MCP server with screenshot, page-info and PDF tools for AI agents.
cURL example, with the API options documented at ScreenshotNeo documentation:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
Python:
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’s free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. Sign up for free and get 1,000 screenshots a month with no card.
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.




