og:type is set appropriately per content type

Setting og:type correctly unlocks platform-specific display features. Facebook and LinkedIn parse og:type: 'article' to expose article-specific properties — article:published_time, article:author, and article:section — which enable richer presentation in article feeds and content discovery systems. When blog posts use og:type: 'website', these article-specific fields are ignored even if present, and the platform cannot categorize the content correctly. Per ogp.me, the type field is mandatory for structured content; the default website type is a catch-all that opts the content out of article-specific distribution features. The findability impact is real for content-driven sites dependent on social amplification.

Set og:type: 'article' at the blog route level, not in the root layout. Override per page type:

// app/blog/[slug]/page.tsx
openGraph: {
  type: 'article',
  publishedTime: post.publishedAt,
  authors: [post.authorUrl],
  section: post.category,
}

For marketing pages, landing pages, and the homepage, omit og:type entirely or set type: 'website' explicitly. Never set type: 'article' in app/layout.tsx — it will misclassify every page in the site.