If a Facebook link preview for your Hindi website has no image, check the exact page’s delivered Open Graph metadata—especially og:image—then verify Facebook’s fetched preview in Meta’s Sharing Debugger. Fix any missing or inaccessible image, and ask Facebook to scrape the page again.
Start with the exact URL Facebook is sharing
Get the complete URL that was posted, including any query string, and follow its redirects to the final page. Check that page rather than assuming every page on the site uses identical metadata. First identify the symptom: is the image missing, wrong, or simply stale? Each points to a different part of the diagnosis.
As an Amazon Associate I earn from qualifying purchases.
Check the metadata Facebook receives
Inspect the page’s delivered HTML and look for a nonempty og:image value pointing to the image you intend Facebook to show. A featured image visible within the page does not prove this Open Graph property is present. Confirm the metadata is included in the HTML Facebook fetches; do not rely on what appears only after browser-side JavaScript runs.
If the tag is absent or points to an old or unintended image, correct the page’s Open Graph metadata and check the delivered HTML again. Also look for competing image declarations if the preview chooses an image other than the one expected.
Make sure the image can be retrieved
Use an absolute image URL that is publicly reachable. Test it without being logged in or passing through a visitor-only step. If the metadata is correct but the preview has no image, investigate whether Facebook can retrieve that image and whether delivery is blocked or failing.
A 1200 × 630 pixel image is described by secondary troubleshooting sources as a practical Open Graph baseline, not as a verified current Meta requirement. The evidence available here does not establish an authoritative Meta image-size or format rule, so treat those dimensions as a recommendation rather than a guarantee.
Use Meta’s Sharing Debugger to refresh the preview
- Open Meta’s Sharing Debugger and enter the exact URL that was shared.
- Review the fetched preview and any warnings. Compare the image and metadata shown there with the page’s delivered HTML.
- Fix the reported or observed page or image problem first.
- Use the debugger’s scrape-again action to ask Facebook to fetch the URL again.
- Check the preview again. Updating the page and refreshing Facebook’s cached scrape are separate steps.
Match the symptom to the likely cause
| What you see | What to investigate | Next step |
|---|---|---|
| No image | Missing or empty og:image, an unusable image URL, or failed image retrieval. |
Check the delivered HTML and public accessibility of the image, then scrape again. |
| Wrong image | The page may declare an unintended image or have competing image declarations. | Correct the metadata and confirm the debugger fetches the intended image. |
| Old image | Facebook may still have an earlier scrape cached. | After confirming the live page is corrected, request a fresh scrape in the debugger. |
| Browser looks right, debugger does not | The crawler may receive different HTML, or the image may not be delivered to it. | Compare crawler-visible HTML and image delivery with the normal browser view; check whether metadata is added only by JavaScript. |
Troubleshooting when the image is still missing
- The tag appears in your browser but not in the fetched page: inspect the initial delivered HTML and whether your site adds Open Graph tags only after JavaScript runs. Make sure the intended metadata is present in the HTML Facebook fetches.
- The image URL works for you but not for the crawler: test it without a login or visitor-specific step, and investigate blocked or failed image delivery.
- The debugger shows the old preview: verify the live metadata and image are fixed, then use scrape again. A page change alone does not refresh the fetched preview.
- The debugger fetches a different page: verify redirects and test the final destination corresponding to the exact shared URL.
- The debugger reports no obvious error: compare its fetched metadata and preview with the page’s delivered HTML, and check for competing image declarations or stale scraped data. These are investigation paths, not proof of a particular cause.
Or skip the browser setup
If you also need a programmatic visual check of the page, ScreenshotNeo can return a screenshot or PDF with one GET request. This is separate from fixing Facebook’s Open Graph metadata or refreshing its preview.
Quick Recap
Best Value
Rank #4
For example, this cURL request captures the page:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpSee the ScreenshotNeo documentation for API options. ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up for free.
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.
