Open Graph guides

Your page has no og:image tag, so shared links render as a bare text row instead of a card. Here is what each platform does without it, and how to add one correctly.

The og:image tag is present but the URL does not return an image. Here are the six reasons a crawler cannot fetch it and how to tell which one applies.

A relative og:image path like /og.png is silently dropped by social crawlers. Here is why the Open Graph protocol requires an absolute URL and how to build one.

Your og:image is not close to 1200 × 630. Here is what each platform does with an off-ratio image and why below 600 × 315 downgrades your card entirely.

Your og:image file is over 1 MB. Here are the real per-platform limits, why WhatsApp is the strictest, and how to get the size down without visible quality loss.

Your og:image URL starts with http:// rather than https://. X refuses these outright and other platforms treat them inconsistently. Here is how to fix it.

Your og:image has no accompanying og:image:alt tag, so screen reader users hear nothing describing the preview image. Here is what to write and how long it should be.

Without og:title, platforms fall back to your <title> tag or to the URL itself. Here is why the fallback usually reads badly and what to write instead.

Your og:title runs past 60 characters and will be cut with an ellipsis. Here is where each platform truncates and how to tighten the headline without losing the point.

Without og:description, platforms either fall back to your meta description or leave the card body empty. Here is what each one does and what to write.

Your og:description runs past the point where mobile previews truncate. Here is where the cut lands on each platform and how to tighten it.

Your page has no og:url tag. It is one of the four properties the Open Graph spec marks required, and it is how platforms pool engagement across variants of the same URL.

Your page has no og:type tag. It is required by the Open Graph spec, and it determines which additional properties platforms will read from your page.

Your page does not declare og:locale, so platforms assume your preview text is US English. Here is when that assumption causes problems and how to declare alternates.

X needs twitter:card to render a rich preview. Without it your link may post as a bare URL even though your Open Graph tags are correct.

Your twitter:card is set to something other than summary_large_image, so X renders a small thumbnail instead of a full-width image. Here is when that is the right call and when it is not.

Your page has no twitter:site tag, so X cards carrying your content are not attributed to your account. Here is the difference between twitter:site and twitter:creator.

Your page has no <title>. That breaks browser tabs, bookmarks, search results and the fallback path for social previews all at once.

Without a meta description, Google writes its own snippet from your page content. Here is what it picks and why you usually want to choose instead.

Your meta description runs past the point where Google truncates the snippet. Here is where the cut lands and how to write to the limit.