A declared sharing image needs attention
og_image_unreachable_or_undersized · Issue
This reports a specific problem with a declared sharing image. Read the recorded verdict before changing it: an unavailable image, a small image, a relative address and inaccurate width or height are different conditions.
Severity: Low. A confirmed unavailable image is Low. A small image, a relative address or inaccurate declared dimensions is Notice. None of these proves how a sharing service will display the page.
Why it matters
Open Graph describes the image a sharing service can use for a page. An unavailable address or inaccurate declaration can make that image harder to use.
What to do
- Look at the recorded image address and verdict, the pages that declare it, and any measured dimensions.
- For an unavailable image, restore the file or update the declaring pages to a working image. Use an absolute image address.
- If the image is small, choose a suitable larger image. If declared width or height is inaccurate, correct or remove that dimension declaration.
When to leave it as it is: A small image can be intentional. Review the preview in the sharing service you use before replacing it.
What we read
We read image declarations and their associated width and height from the original page head. Pages that declare the same normalized image address form one group; a redirect of the image does not change that original subject.
The shared resource collection reads selected image addresses within its existing request and byte limits. We use validated PNG, GIF, JPEG or WebP header dimensions, without rendering the image.
An unavailable-image verdict requires a recorded 404 or 410, or two actual GET attempts that both answered 5xx. A small-image verdict requires either measured side to be below 200 pixels. Separate verdicts record a relative address or a valid declared width or height that differs from the measured value.
Example & evidence
Illustrative example — original declarations and measured dimensions, not a live audit.
<meta property="og:image" content="https://bakery.example/images/cake.png">
<meta property="og:image:width" content="200">
<meta property="og:image:height" content="200">The retained image header records 100 × 100 pixels. The image has two Notice verdicts: it is small and its declared dimensions differ from the measured dimensions.
A possible correction: use a suitable larger image and declare its actual dimensions. Check every page that declared the original image in a new full audit.
Confirm & check again
Check for yourself: View the original page source and check the image address and associated width and height. Open the image, inspect its actual dimensions, and test the preview in the sharing service you use.
Check again: Full audit — Run a new full audit. A fix needs a complete comparison of the original image subject and all retained declaring pages. A missing page, blocked image or partial sample does not prove that the original problem was fixed.
Limits & sources
The 200-pixel side threshold is this audit's review threshold. It does not predict the preview shown by Facebook, X or another service.
A robots or TLS refusal, 401, 403, 429, transient failure, unsupported image header or clipped source inventory remains unconfirmed. A confirmed access problem does not provide image dimensions.
Confidence: High The report records source-bound declarations, responses and header dimensions. It does not measure a rendered preview.
Sources
- ogp.me, The Open Graph protocol — Defines the image URL and associated width and height properties, and associates structured properties with the preceding root image declaration. Checked 11 October 2026.
- Meta, Images in sharing markup — Retained catalog reference for the original sharing-image size policy. The live source returned 429 during this review; no current platform eligibility claim is made. Checked 12 July 2026.
Editorial review: 2 November 2026