og:description is suitable for WhatsApp previews
Why it matters
WhatsApp renders OG previews in a compressed format that truncates og:description at approximately 150 characters. When og:description exceeds 300 characters or buries the key message after the 150-character mark, the message recipient sees a truncated description that ends mid-sentence. WhatsApp does not have its own meta tags — it reads og:description exclusively. Per ogp.me, the description field is the text that contextualizes the link for anyone who receives it in a message. For products shared via messaging (B2C tools, content recommendations, referral links), the WhatsApp preview is often the first impression; a truncated or absent description removes the primary click signal.
Severity rationale
Low because WhatsApp preview truncation degrades but does not break sharing — the link still functions, and the title and image remain visible even when the description is cut off.
Remediation
Front-load the most important content in og:description within the first 150 characters, and keep total length under 300 characters. This is a content strategy change, not a code change — edit the description strings in your metadata exports or generateMetadata functions.
For dynamic content pages in src/app/, derive descriptions from a summary or excerpt field on the content model, trimmed to 200 characters:
description: post.excerpt?.slice(0, 200) ?? post.title,
This aligns with general og:description best practice and requires no WhatsApp-specific configuration.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Social Sharing Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- external · ogp.me — The Open Graph Protocol
Taxons
History
- 2026-04-18·v1.0.0·Initial import from marketing-social-sharing·automated