Why is my Open Graph image not showing?

Is the image tag on the page being shared?

Start with the exact URL someone will paste into a message. Check that its HTML contains og:image and that the value identifies your intended image. A homepage can have correct tags while a blog post inherits a different image or has none at all. Check redirects too: the final page may have different metadata.

Use a complete HTTPS image URL. If tags are added only after browser JavaScript runs, some sharing services may miss them. Render your metadata on the server or in the static HTML so it can be read directly. OGFrame's checker reports the tags it fetches; it does not reproduce every platform's crawler or execute your full browser application.

Does the image URL return an actual image?

Copy the image URL from the metadata and open it while signed out. It should return image bytes, not a login page, a JSON response, or a branded error document with a successful status code. Inspect its response status and Content-Type in your browser's network panel.

Check for a missing file, an expired signed URL, a hostname typo, or a deployment that did not include the exported PNG. OGFrame's image check measures the fetched image rather than trusting the declared width and height tags. A report warning about size is a reason to inspect the image, not proof that every platform will reject it.

Can an external crawler fetch both URLs?

Your browser can succeed while a crawler fails. Cookies, bot challenges, authentication, rate limits, firewall rules, and robots.txt can produce different responses for a sharing service. Inspect your hosting logs for requests to both the page and the image around the time you share.

If your image lives under an API path, a broad robots.txt rule blocking /api/ can also block the image. Allow the public image route while keeping unrelated APIs restricted. Do not disable protection across the whole site to solve a single image-route problem.

Why does the old image still appear?

There can be multiple caches: your host or CDN, the image endpoint, and the sharing platform. First verify that fetching the image directly returns the new design. Then verify that the page points to that URL. If both are correct, the sharing platform may still have its previous copy.

Use the platform's preview inspection or refresh tool when available. If necessary, publish an image with a new filename, such as launch-v2.png, and update the image tag. Keep the page's canonical URL stable. Adding random parameters repeatedly is not a reliable substitute for finding which cache is stale.

Use the checker as a debugging checklist

OGFrame's free checker gives a 0–100 score for its own set of checks, suggested tag fixes, and preview simulations. The score is not a Google ranking score or a guarantee of platform acceptance.

1. Run the exact public page URL through the OG Image Checker.
2. Fix image availability and missing tags before fine-tuning dimensions or copy.
3. Deploy the change and recheck the page; a cached report may take time to refresh.
4. Verify a real share and inspect the target platform's own tools if the result differs.