Open Graph Protocol (OGP)

OGP uses an RDFa-based type system where object types inherit properties from parent types in a defined hierarchy. For example:

• og:type business.bank inherits all properties from business.local_business, which inherits from business, which inherits from place.
• This means a bank can use place:location:latitude and place:location:longitude without redefining them.
• Custom verticals like music.album or video.episode expose domain-specific properties (music:song, video:actor) that generic types do not.

This inheritance model allows platforms to render rich, type-specific previews—such as a music player for a song or a map for a restaurant—based on the declared type.

Beyond the four required properties, OGP defines optional tags that significantly improve the shared experience:

• og:description: A one-to-two sentence summary displayed below the title. Facebook truncates at approximately 200 characters.
• og:site_name: The human-readable name of the overall site, displayed in grey text above the title on Facebook.
• og:locale: Declares the language and optional territory (e.g., en_US), enabling platforms to serve the correct localized preview.
• og:video: An absolute URL to a video file or SWF player, which can render an inline playable preview on Facebook.
• og:audio: An absolute URL to an audio file, used by platforms like Spotify to render an inline audio player.

These properties collectively determine whether a shared link appears as a simple text link or a rich, interactive card.

Social platforms do not fetch OGP tags in real-time on every share. Instead, they employ aggressive caching:

• Facebook's crawler (facebookexternalhit/1.1) fetches the URL once and caches the parsed OGP data for approximately 30 days.
• LinkedIn's crawler (LinkedInBot/1.0) caches for 7 days.
• Twitter's card bot (Twitterbot/1.0) caches for approximately 7 days.

To force a cache refresh after updating tags, developers must use platform-specific debugging tools:

• Facebook: Sharing Debugger
• LinkedIn: Post Inspector
• Twitter: Card Validator

Failing to manually refresh the cache after a tag update means old, incorrect previews persist for weeks.

When OGP tags are missing, platforms apply a fallback hierarchy to construct a preview:

• Title fallback: og:title → <title> tag → <h1> heading → URL path.
• Description fallback: og:description → <meta name="description"> → first 200 characters of body text.
• Image fallback: og:image → first <img> tag over 200x200 pixels → no image.

This fallback behavior is unreliable and often produces poor results—such as pulling a logo or spacer GIF as the preview image. Explicit OGP tags are the only way to guarantee a professional, controlled social preview. Additionally, Twitter Cards (twitter:card) take precedence on Twitter only if OGP tags are absent; if both exist, Twitter defers to OGP.

The algorithmic generation of concise HTML <meta name="description"> tags. While OGP's og:description controls the social preview text, the standard meta description remains critical for search engine result pages. Automated pipelines must synthesize both tags from the same source content.

• Optimal length: 150-160 characters
• Must be distinct from og:description in some contexts
• Directly impacts click-through rates from SERPs

The automated identification of the preferred, authoritative URL for a piece of content. The og:url tag must match the canonical URL to ensure social platforms consolidate engagement signals to a single address. Mismatched URLs fragment likes, shares, and comments across duplicate pages.

• Prevents social proof dilution
• Uses <link rel="canonical"> as source of truth
• Critical for parameterized and paginated URLs

The automated assessment of whether a page's structured data and content quality meet the threshold for enhanced search results. While OGP governs social previews, rich snippet eligibility governs SERP enhancements like star ratings and recipe cards. Both require flawless metadata implementation.

• Validated via Rich Results Test
• Requires both schema markup and high-quality content
• OGP does not directly influence rich snippet eligibility