Free tools Windows power users keep installed
One-click scans. No signup required.
If a Facebook link preview has no image, shows the wrong one, or still displays an old one, first check the page’s delivered og:image metadata. Then inspect the URL in Meta’s Sharing Debugger and check whether the page and image can be reached publicly. These checks separate a page-tag problem from stale preview data or a delivery issue.
Start with the symptom: missing, wrong, or old image?
Those symptoms can have different causes, so note what Facebook is showing before changing anything. A blank thumbnail can mean the page does not provide a usable image value, or that the image cannot be retrieved. A wrong image can point to an unintended or competing og:image value. An old image after an edit can mean the preview data has not been refreshed.
| What you see | First place to investigate |
|---|---|
| No thumbnail | Whether the shared page’s delivered HTML includes the intended og:image, then whether its image URL is reachable. |
| The wrong thumbnail | The exact image URL in the page metadata and whether more than one og:image is present. |
| An older thumbnail | Whether the page has been corrected and its preview data has been re-scraped. |
| A connection error or no preview | Whether the page and image can be fetched, and whether certificate, server, or access restrictions could be interfering. |
These are diagnostic starting points, not guarantees: more than one problem can occur at once.
Check the HTML Facebook is being given
Open the exact URL you share and inspect the HTML response, rather than relying only on an image field in your content-management system. Open Graph metadata belongs in the document’s <head>. The Open Graph protocol identifies og:title, og:type, og:image, and og:url as the basic properties, with og:image specifying an image URL that represents the page.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
For a quick check, use your browser’s page-source view and search for og:image. You can also request the page HTML from a terminal:
curl -L -s 'https://itechguides.com/' | grep -i 'og:image'Replace the URL with the full address of the page you intend to share. This command is a quick text search, not a complete HTML parser: a minified response, unusual markup, or a page that does not return the relevant metadata in its HTML can make the output difficult to interpret. If it returns nothing, inspect the full response and the page source in a browser before concluding that the tag is absent.
Check that the tag is in the head and that its content value is the intended, complete image URL. For example:
<head>
<meta property="og:title" content="A useful page title">
<meta property="og:type" content="website">
<meta property="og:url" content="https://itechguides.com/">
<meta property="og:image" content="https://itechguides.com/path/to/share-image.jpg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:type" content="image/jpeg">
<meta property="og:image:alt" content="Description of the image">
</head>The example shows the form of the tags, not a Facebook image-size requirement. The protocol defines optional image properties for secure URL, MIME type, width, height, and alt text, and recommends alt text when an image is specified. No current minimum image dimensions or file-size limit is established here; do not assume that the example’s dimensions are required.
Check for duplicate or competing image tags
Search the page source for every occurrence of og:image, not just the first one you notice. A theme, SEO extension, social-sharing plugin, or custom template can potentially output additional values. The Open Graph protocol treats these properties as arrays and says the first value is preferred when values conflict. As a result, an unwanted first tag can matter even if the intended image appears later.
- Remove redundant image tags where possible, or arrange them so the intended image is first.
- Confirm that each remaining tag has a valid image URL in its
contentattribute. - If the page is generated by a CMS, inspect the final HTML after publishing; changing a CMS field alone does not confirm what the page now delivers.
Use Meta’s Sharing Debugger to refresh and inspect the preview
After checking or correcting the HTML, look up the shared URL in Meta’s Sharing Debugger. The Open Graph protocol identifies Facebook’s parser and debugger as tools for working with Open Graph data. Use the debugger to examine the preview information it reports, then request a fresh scrape after making a correction. This is the practical way to check whether Meta is still showing previously retrieved information.
Rank #3
- Copy the exact page URL that people share, including any path or query string that is part of that link.
- Open Meta’s Sharing Debugger and submit that URL.
- Review the reported preview and image information for a mismatch with the page’s current metadata.
- After correcting the page or its delivery, request a fresh scrape and inspect the result again.
- Test the corrected URL in a new share.
Meta’s interface and preview behavior can change. The current button wording, access requirements, cache duration, and whether an existing post changes after a re-scrape are not established here. Do not treat a refreshed debugger result as a promise that an already-published post will update automatically.
If the tags look right, test whether the image can be fetched
Correct metadata is only part of the path: the page and its referenced image also need to be retrievable. Open the image URL directly in a private browser window or from a network that is not signed in to the site. Check that it returns the image rather than an error page, login screen, or redirect to an unrelated destination. Repeat the check for the page URL itself.
Recommended Free Tools
If a browser can load the image but the debugger cannot, investigate server-side delivery and access controls. Certificate problems, security rate-limiting or crawler restrictions, and server or domain problems are possible causes reported in troubleshooting guidance; they are possibilities to check, not an exhaustive list or an official Meta diagnosis.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
- Check HTTPS and the certificate: the image URL should use a valid secure connection if it is served over HTTPS. Resolve certificate warnings or misconfiguration with whoever manages the site or hosting.
- Check access rules: review firewall, rate-limiting, security-plugin, and server rules that might prevent an outside service from requesting the page or image. Change only the rule that is actually blocking legitimate access.
- Check the domain and server: confirm that the domain resolves and that the server is responding for both the shared page and the image path. Correct expired domain or nameserver configuration, if applicable.
- Check redirects and the final image response: follow the image URL to its destination and verify that the destination is still the intended image, not an access challenge or a missing-file page.
Fixes by symptom
Facebook link preview image is not showing
- Confirm that the shared page’s HTML contains
og:imagein the head and that its URL points to the intended image. - Open that image URL directly and check for access, certificate, or server errors.
- Submit the page URL to the Sharing Debugger, correct the underlying issue, and request a fresh scrape.
Facebook is showing the wrong image
- Compare the image URL in the delivered HTML with the image you expect.
- Look for multiple
og:imagevalues and check which one appears first. - Correct the source that generates the unwanted value, inspect the resulting HTML, and re-scrape the URL.
Facebook is showing an old image
- Verify that the current page HTML now points to the new image.
- Check that the new image URL itself is reachable and returns the intended image.
- Request a fresh scrape in the Sharing Debugger and check its result before testing a new share.
The debugger cannot connect or retrieve the page
Check the page and image from outside any authenticated session, then investigate certificate validity, rate-limiting or crawler access rules, and domain or server availability. A failure can be at the page URL or the image URL, so test both rather than changing metadata that is already correct.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
ScreenshotNeo can capture a page with one API request, which is useful when you also want to see how the page renders. A screenshot is not a substitute for inspecting og:image in the HTML or refreshing Meta’s preview data; use the checks above to diagnose those parts.
cURL example (replace the URL with the page you are investigating):
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://itechguides.com/ -o shot.webpPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://itechguides.com/"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://itechguides.com/' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);See the ScreenshotNeo API documentation for request options. ScreenshotNeo accepts cookie or consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each of those steps can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing status in headers. Its MCP server offers take_screenshot, get_page_info, and capture_pdf for AI agents and MCP clients. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.
Sign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.
Keep the diagnosis focused
Make one change at a time and verify the result at the layer you changed: the HTML for metadata edits, the image URL for delivery changes, and the Sharing Debugger after a re-scrape. This makes it easier to identify the actual cause instead of changing unrelated site settings.
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.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
