OG Image URL Invalid or Unreachable? Check the Response

Copy the image URL from the returned HTML

Start with the shared page's metadata. Do not copy a CSS background image or a thumbnail from the page unless that is the URL in og:image. A site may display one image and declare a different sharing image.

Use an absolute public URL such as https://example.com/images/share.jpg. Check spelling, case-sensitive paths, and HTML escaping of query parameters. A development host, local file path, or browser-only blob: URL is not a public share asset.

If the tag is absent or wrong, fix the page first. The tag setup guide and meta tag generator can help with the markup.

Download it without a browser session

A terminal GET request shows the response headers and saves the bytes for inspection:

curl -sS -L -D - -o /tmp/proovd-share-test.jpg   'https://example.com/images/share.jpg'

The example writes to a temporary file; the filename does not determine what the server sends. Look for an image content type and inspect the downloaded file. An HTML viewer, login form, security challenge, or error body is not a usable image simply because the URL ends in .jpg.

A status 200 means the request succeeded at the HTTP level; it does not certify the body is the asset you expected. See MDN's status explanation. If a HEAD request and GET request differ, use the GET result to investigate the actual download.

Check permissions and hotlink protection

Try opening the URL in a private browser window. If it only works when signed in, a crawler will not have your session. Check storage permissions, CDN rules, referer restrictions, and security events. A normal browser request can succeed while a particular platform is blocked.

For Cloudflare, inspect the event responsible for a failed request instead of disabling security across the domain. The Cloudflare guide explains that investigation. Changing the user-agent header can provide a clue, but it cannot impersonate a platform's source IP or establish a complete diagnosis.

Replace expiring and indirect asset links

Some copied media URLs contain signatures and expiration parameters. They can work during your test and fail later. Use a stable public sharing asset under your control when possible, rather than a temporary download URL.

Follow redirects and check the final response. A file-sharing page is different from the image file it displays. A redirect to a login screen or deleted file explains why the original asset cannot be fetched. Also check that a domain migration did not leave a certificate error or an obsolete image hostname.

If you do not own the source website or asset, you may be able to diagnose the failure but cannot change its permissions or lifetime through Proovd.

Check format and dimensions after access works

Once the bytes are available, verify the file opens and matches the stated content type. A broadly compatible JPEG or PNG is a practical starting point for troubleshooting, though platform support and limits vary. Re-encoding a corrupt file can help; renaming its extension does not change the encoding.

Use the image checker and image size guide for dimensions and composition. Do not assume that a large enough canvas guarantees a platform will accept the asset.

Finally recheck the live page, then the platform's fetched result where available. If a new image URL works but the old one remains in a published preview, continue with the cache guide.