og:url matches the page canonical URL

Without og:url, social platform crawlers cannot reliably deduplicate shares of the same page that arrive via different URLs — such as with UTM parameters, trailing slashes, or HTTP vs HTTPS variants. Per ogp.me, og:url specifies the canonical URL that should aggregate all social engagement signals. When og:url is absent or mismatched with the canonical URL, share counts and engagement metrics fragment across URL variants. This directly affects how platforms surface your content in social feeds and how link preview analytics attribute engagement. The findability impact is concrete: a page shared 500 times across two URL variants may show as two separate posts with 250 shares each rather than one high-engagement result.

Set og:url alongside your other OG properties and keep it in sync with your canonical URL. Both should use the same scheme, host, and path:

export async function generateMetadata({ params }): Promise<Metadata> {
  return {
    alternates: { canonical: `https://yoursite.com/blog/${params.slug}` },
    openGraph: {
      url: `https://yoursite.com/blog/${params.slug}`,
      title: post.title,
      description: post.excerpt,
      images: [...],
    },
  }
}

For static pages, set both metadata.alternates.canonical and metadata.openGraph.url in the page's metadata export. If you use a NEXT_PUBLIC_SITE_URL environment variable for the base, apply it consistently to both fields.