9 Common OG Image Mistakes (and How to Fix Them)

Most broken link previews trace back to nine repeat mistakes: wrong dimensions, text in the crop zone, files over platform limits, and missing meta tags. Every one is fixable in minutes. Start fresh with our OG image generator — the full diagnosis guide is below.

Mistakes 1-3: dimension and composition errors

The first three mistakes are design errors that no meta tag can fix. Mistake 1: wrong aspect ratio. Designing at 1080 x 1080 (square) or 1920 x 1080 (16:9) and letting the platform center-crop to 1.91:1 produces unpredictable results — headlines get decapitated and logos vanish. Always design at exactly 1200 x 630. Mistake 2: critical content outside the safe zone. Text or logos within 100 pixels of any edge risk clipping on X's 2:1 crop, WhatsApp's square-ish crop, or rounded card corners. Keep everything meaningful inside the central 1000 x 500 pixels. Mistake 3: text too small to read. Body copy at 32 pixels looks fine in your design tool at full size and becomes gray smudge when the card renders at 500 pixels wide on a phone. Headlines at 72 to 120 pixels, supporting text never below 48, and a maximum of two text elements per image. The common thread: designers compose for the canvas, but viewers see the card — often at half size, on a phone, in a busy feed. Preview every OG image at 500 pixels wide before shipping; if you cannot read it there, redesign it. Our OG image size guide details the safe zone, and how to create OG images walks through the full design workflow.

Mistakes 4-6: technical deployment errors

The next three mistakes are invisible in the design file and only appear at deployment. Mistake 4: relative image URLs. An og:image of '/images/og.png' works in your browser and fails on every crawler, because crawlers do not know your domain — the tag must contain the full absolute HTTPS URL. Mistake 5: missing width and height tags. Without og:image:width and og:image:height declared as 1200 and 630, some crawlers misdetect the dimensions and render a small thumbnail card or a stretched image. Mistake 6: file over the platform limit. A 12MB PNG exceeds Facebook's 8MB and X/LinkedIn's 5MB ceilings, and the failure mode is silence — no error, just no image. Compress to 200 to 500KB before deploying. A fourth deployment-adjacent error deserves mention: hotlink protection or login walls blocking the crawler — if your CDN requires a referer or your staging site needs a password, the scraper gets a 403 and your card ships imageless. The deployment checklist is short: absolute HTTPS URL, width/height declared, sub-500KB file, publicly accessible, then validate in Facebook's Sharing Debugger and X's Card Validator. For tag syntax, see how to generate Open Graph meta tags.

Mistakes 7-9: caching, staleness, and neglect

The final three mistakes happen after a working card ships. Mistake 7: not re-scraping after changes. Platforms cache previews aggressively — updating your image or tags does nothing until you force a re-scrape in each platform's debugger. Teams that 'fixed' the image but never re-scraped conclude the fix did not work and revert a correct change. Mistake 8: expiring image URLs. CDN-signed URLs with 24-hour tokens make catastrophic og:images: the card caches fine on day one, then the signature expires and every share renders broken forever. Always use permanent, stable image URLs. Mistake 9: set-and-forget staleness. The OG image showing 2023 statistics on a 2026 article quietly undermines credibility with every share. Refresh OG images on your top-traffic pages quarterly — or at least when the underlying content changes materially. The maintenance habit that prevents all three: add 'OG image verified in debuggers' to your publishing checklist and 'OG images refreshed' to your quarterly content audit. When debugging cache timing specifically, our Unix timestamp converter helps you compare scrape times across platforms. And if your card strategy needs rethinking from the headline up, how to write a meta description that gets clicks teaches the tight copy that makes cards convert.

The 60-second OG image audit

Run this audit on any page in under a minute. View the source and confirm og:image exists with an absolute HTTPS URL, og:image:width is 1200, og:image:height is 630, and twitter:card reads exactly 'summary_large_image'. Open the image URL directly in a private window — if it does not load without login, neither can the crawler. Check the file size — over 1MB deserves compression, over 5MB is broken on X and LinkedIn. Paste the page URL into Facebook's Sharing Debugger and X's Card Validator and confirm the rendered card matches your design. Share the link to yourself on mobile in the apps that matter and confirm the headline is readable. Any failure gets a specific fix from the mistakes above; most audits find exactly one issue, and most issues take under five minutes to resolve. Make this audit part of every publish, and broken previews become a solved problem rather than a recurring mystery. If the audit reveals the image itself needs rebuilding, our OG image generator produces a correct-by-construction replacement in minutes, and our word counter keeps the replacement headline tight.

Bonus: the mistakes teams make at scale

Everything above covers a single page, but teams managing hundreds of pages hit a second layer of OG image mistakes. Mistake 10: hand-making every image. Designing cards one by one in a graphics tool does not scale past a few dozen posts — at volume, the images go stale, off-brand, or missing entirely because nobody owns the task. The fix is templates: one master design with headline, brand, and background slots, or fully programmatic generation from page metadata for large sites. Mistake 11: no ownership. When the OG image belongs to no one's checklist, it ships broken by default — assign it to the publishing workflow alongside the meta description and headline, with the debugger validation as the acceptance step. Mistake 12: ignoring the data. Teams that never compare click-through across headline variants leave 20 to 40% CTR gains on the table; add UTM parameters to shared links and review quarterly which card styles earn the click. The pattern across all three is treating OG images as decoration instead of infrastructure — the card is often the first and only impression of your content, and at scale it deserves systems, not heroics. Build the system once with our OG image generator and the audit above, and every future page inherits it.