Social Image Wrong Size

Element Code: IM-007

What "wrong size" actually means here

This check does not mean your social image is missing, it means one exists but its pixel dimensions or aspect ratio fall outside what Open Graph consumers expect. The de facto standard, set by Facebook's own documentation and followed by LinkedIn, Slack, and most link-unfurling tools, is 1200x630px, an aspect ratio of roughly 1.91:1. When your image comes in as a square, a portrait crop, a tiny thumbnail, or an oddly wide banner, platforms respond in different unhelpful ways: some crop aggressively from the center, some stretch it to fit, some fall back to a small thumbnail card instead of a large image card, and some drop the image entirely if it is below their minimum threshold.

Twitter and X use the same underlying og:image tag by default unless a twitter:image override is present, and their "summary_large_image" card also wants roughly 2:1, with a documented minimum of 300x157px. Below that minimum, X silently falls back to a small square thumbnail card instead of the large image card, which is a meaningfully worse click-through experience.

Why this matters for SEO and beyond

This is not a ranking-factor issue in the traditional sense, Google does not read your og:image dimensions and adjust your position in the SERP. It matters for a more direct reason: shared links are a real traffic channel, and a cropped or stretched preview image looks broken, unprofessional, or spammy, which tanks click-through rate on every share, whether that is a colleague posting a link in Slack, a reader sharing your article on X, or your own social team boosting a post on LinkedIn.

• Click-through rate. A clean, correctly-cropped 1200x630 image reliably outperforms a stretched or off-center one in social CTR, because the preview looks intentional rather than broken.
• Brand trust. A warped logo or a face cropped in half reads as low quality, and users extend that judgment to the destination page before they have even clicked.
• Indirect SEO signal. More shares and more click-throughs from social can contribute to the kind of traffic and engagement signals that correlate with authority over time, even though they are not a direct algorithmic input.

How to detect it

Run the URL through Facebook's Sharing Debugger (developers.facebook.com/tools/debug) and look at the preview render, it will show you exactly how the image gets cropped. Do this for one URL per template, not just your homepage, since dimensions often vary by page type if images are pulled dynamically from featured images or CMS fields.

Use Twitter Card Validator or manually check via X's card preview to confirm the large-image card triggers rather than the small summary card, that fallback is your signal the image is below the minimum.

For a site-wide check, crawl with Screaming Frog, enable the "Custom Extraction" or built-in social meta reporting, and export all og:image URLs. Then batch-check dimensions with a script or an image inspection tool rather than eyeballing them one at a time. Sitebulb's Social tab does this natively and will flag images outside the expected ratio automatically.

Also check the raw image file directly, sometimes the meta tag URL is fine but the actual file behind it was replaced with a different size during a CMS update or asset swap, which the crawl won't catch unless you fetch the image itself.

How to fix it, step by step

1. Create a dedicated social image asset at exactly 1200x630px for each template or page type. Do not reuse a random content image and hope the platform crops it well, design it flat at the target size.
2. Keep essential content inside the safe zone. Some platforms crop edges slightly on certain layouts, so keep text and faces centered, roughly within the middle 80 percent of the frame.
3. Compress without over-compressing. Stay well under the 5MB ceiling, aim for under 1MB where possible for faster unfurling, using JPEG for photos and PNG for graphics with text or flat color.
4. Set the dimension meta tags explicitly. Add <meta property="og:image:width" content="1200"> and <meta property="og:image:height" content="630"> alongside the image URL. This lets platforms render the correct aspect ratio immediately instead of having to fetch and measure the image first.
5. Fix the template, not just one page. If the issue traces back to a dynamic featured-image field, update the CMS logic or theme function that generates the og:image so every future page inherits the correct dimensions automatically.
6. Re-scrape the cache. Facebook and LinkedIn cache preview images aggressively. After fixing, use the Sharing Debugger's "Scrape Again" button, and LinkedIn's Post Inspector, to force a refresh, otherwise old broken previews can linger for days.

What good looks like

Every page serves an og:image at 1200x630px (or another clean 1.91:1 multiple), the image file itself matches those dimensions rather than relying on the platform to crop it, width and height meta tags are declared explicitly, and a Sharing Debugger check on a sample from each template shows a clean, uncropped, correctly composed preview.

Too square (1:1) crops or small card

Correct (1.91:1) 1200 x 630

Too wide (3:1) stretched thin

Rule of thumb: design flat at 1200x630px per template. Declare og:image:width and og:image:height so platforms don't have to guess the ratio before rendering a preview.

Platform requirements at a glance

FAQ