Open Graph Generator
Contact Us
Back to Blog
Open GraphJavaScript

Open Graph JavaScript Implementation

How to implement Open Graph meta tags in JavaScript frameworks like React, Vue, Svelte, Next.js, Nuxt, and Astro with server-side rendering.

SS
Sanjay Samanta•June 27, 2026
7 min read

Modern web applications built with JavaScript frameworks face a unique Open Graph challenge: social media crawlers do not execute JavaScript. If your OG tags are rendered client-side, crawlers see an empty <head> and cannot generate preview cards.

This guide covers how to correctly implement Open Graph tags in every major JavaScript framework.

The Core Problem

When Facebook, LinkedIn, or Twitter’s crawler visits your URL, it downloads the HTML response and parses it immediately. It does not:

  • Execute JavaScript
  • Wait for API calls to resolve
  • Render React/Vue/Svelte components

This means any OG tags injected via document.head.appendChild(), React Helmet, or Vue Meta after hydration are invisible to social crawlers.

Solution: Server-Side Rendering (SSR)

The only reliable way to deliver OG tags to social crawlers is to include them in the initial HTML response from the server.

Next.js (App Router)

Next.js provides native metadata support through the metadata export:

export const metadata = {
  openGraph: {
    title: 'Page Title',
    description: 'Page description',
    url: 'https://example.com/page',
    images: [{ url: 'https://example.com/og.png', width: 1200, height: 630 }],
  },
};

For dynamic pages, use generateMetadata:

export async function generateMetadata({ params }) {
  const post = await fetchPost(params.slug);
  return {
    openGraph: {
      title: post.title,
      description: post.excerpt,
      images: [{ url: post.ogImage }],
    },
  };
}

For a complete walkthrough, see Next.js Open Graph Metadata Guide.

Nuxt 3

Nuxt provides the useHead and useSeoMeta composables:

<script setup>
useSeoMeta({
  ogTitle: 'Page Title',
  ogDescription: 'Page description',
  ogImage: 'https://example.com/og.png',
  ogUrl: 'https://example.com/page',
  twitterCard: 'summary_large_image',
});
</script>

Nuxt renders these tags server-side automatically during SSR.

Astro

Astro renders all components server-side by default, making it ideal for OG tags:

---
const title = "Page Title";
const description = "Page description";
const ogImage = "https://example.com/og.png";
---
<head>
  <meta property="og:title" content={title} />
  <meta property="og:description" content={description} />
  <meta property="og:image" content={ogImage} />
  <meta property="og:url" content={Astro.url.href} />
  <meta property="og:type" content="website" />
</head>

SvelteKit

SvelteKit uses the <svelte:head> element inside +page.svelte or +layout.svelte:

<svelte:head>
  <meta property="og:title" content={data.title} />
  <meta property="og:description" content={data.description} />
  <meta property="og:image" content={data.ogImage} />
  <meta property="og:url" content={$page.url.href} />
</svelte:head>

Gatsby

Gatsby uses the <Seo> component pattern with React Helmet:

import { Helmet } from 'react-helmet';

export function SEO({ title, description, image, url }) {
  return (
    <Helmet>
      <meta property="og:title" content={title} />
      <meta property="og:description" content={description} />
      <meta property="og:image" content={image} />
      <meta property="og:url" content={url} />
    </Helmet>
  );
}

Gatsby pre-renders all pages during build, so Helmet tags are included in the static HTML.

Alternative: Pre-Rendering Services

If you have a client-side SPA that cannot be migrated to SSR, pre-rendering services can serve static HTML snapshots to social crawlers:

  • Prerender.io — Detects crawler user-agents and serves cached HTML.
  • Rendertron — Google’s open-source headless Chrome rendering service.
  • Cloudflare Workers — Intercept crawler requests at the edge and inject OG tags.

Testing Your Implementation

After implementing OG tags in your framework, always verify them using:

  1. View Page Source (not DevTools Inspect) — OG tags must be in the raw HTML source.
  2. curl — curl -s https://your-url | grep og: to confirm server-side rendering.
  3. Open Graph Inspector — Multi-platform preview and validation.

For a complete testing workflow, see How to Test Open Graph Tags.

Deep Technical Framework Implementations

Integrating optimized social preview tags into production web frameworks requires understanding how each runtime handles head metadata and server-side rendering:

1. Next.js App Router (layout.tsx / page.tsx)

In Next.js 14 and 15, use the centralized Metadata API to construct unified Open Graph and Twitter Card tags. This ensures that edge crawlers receive complete, pre-rendered meta tags in the initial HTML stream before client hydration:

import type { Metadata } from 'next';

export const metadata: Metadata = {
  title: 'Next-Generation Web Metadata & Social Graph Suite',
  description: 'Automate Open Graph, Twitter Cards, and Schema.org JSON-LD generation with sub-millisecond edge validation.',
  openGraph: {
    title: 'Next-Generation Web Metadata & Social Graph Suite',
    description: 'Automate Open Graph, Twitter Cards, and Schema.org JSON-LD generation with sub-millisecond edge validation.',
    url: 'https://opengraphgenerator.com/',
    siteName: 'Open Graph Generator',
    images: [
      {
        url: 'https://opengraphgenerator.com/images/hero-1200x630.png',
        width: 1200,
        height: 630,
        alt: 'Open Graph Generator Dashboard Interface',
        type: 'image/png',
      },
    ],
    locale: 'en_US',
    type: 'website',
  },
  twitter: {
    card: 'summary_large_image',
    site: '@OpenGraphGen',
    creator: '@sanjaysamanta',
    title: 'Next-Generation Web Metadata & Social Graph Suite',
    description: 'Automate Open Graph, Twitter Cards, and Schema.org JSON-LD generation with sub-millisecond edge validation.',
    images: ['https://opengraphgenerator.com/images/hero-1200x630.png'],
  },
};

For dynamic route handling in Next.js, read our comprehensive Next.js Open Graph Guide.

2. Astro Component Head Architecture

Astro’s component-first model allows you to encapsulate social sharing tags into reusable SEO layouts:

---
interface Props {
  title: string;
  description: string;
  image?: string;
  canonicalUrl?: string;
  type?: 'website' | 'article';
}

const {
  title,
  description,
  image = 'https://opengraphgenerator.com/images/default-og.png',
  canonicalUrl = Astro.url.href,
  type = 'website'
} = Astro.props;
---
<head>
  <title>{title}</title>
  <meta name="description" content={description} />
  <link rel="canonical" href={canonicalUrl} />

  <!-- Open Graph -->
  <meta property="og:type" content={type} />
  <meta property="og:site_name" content="Open Graph Generator" />
  <meta property="og:title" content={title} />
  <meta property="og:description" content={description} />
  <meta property="og:url" content={canonicalUrl} />
  <meta property="og:image" content={image} />
  <meta property="og:image:width" content="1200" />
  <meta property="og:image:height" content="630" />

  <!-- Twitter Cards -->
  <meta name="twitter:card" content="summary_large_image" />
  <meta name="twitter:site" content="@OpenGraphGen" />
  <meta name="twitter:title" content={title} />
  <meta name="twitter:description" content={description} />
  <meta name="twitter:image" content={image} />
</head>

3. Nuxt 3 & Vue Composition API

<script setup lang="ts">
useSeoMeta({
  title: 'Enterprise Social Metadata Management',
  ogTitle: 'Enterprise Social Metadata Management',
  description: 'Scalable Open Graph and Twitter Card automation for multi-tenant applications.',
  ogDescription: 'Scalable Open Graph and Twitter Card automation for multi-tenant applications.',
  ogImage: 'https://example.com/og-banner.png',
  ogImageWidth: '1200',
  ogImageHeight: '630',
  ogUrl: 'https://example.com/enterprise/',
  ogType: 'website',
  twitterCard: 'summary_large_image',
  twitterSite: '@OpenGraphGen',
});
</script>

Edge Caching, CDN Invalidation & HTTP Headers

To ensure that social scrapers (facebookexternalhit, Twitterbot, LinkedInBot, Slackbot, WhatsApp/2.x) always receive fresh metadata while minimizing origin server CPU load, implement a multi-tiered caching strategy:

Asset Category Cache-Control Header Edge CDN TTL Browser Cache TTL
HTML Webpages public, max-age=0, s-maxage=600, must-revalidate 10 Minutes 0 Seconds (Always revalidate)
Static OG Images public, max-age=31536000, immutable 1 Year 1 Year (Content-hashed URLs)
Dynamic OG API Routes public, max-age=3600, s-maxage=86400, stale-while-revalidate=86400 24 Hours 1 Hour 
# NGINX Edge Caching Configuration for Social Scraping
location ~* \.(html)$ {
    add_header Cache-Control "public, max-age=0, s-maxage=600, must-revalidate";
    add_header X-Robots-Tag "all";
}

location ~* \.(png|jpg|jpeg|webp)$ {
    add_header Cache-Control "public, max-age=31536000, immutable";
    add_header Access-Control-Allow-Origin "*";
}

Comprehensive Troubleshooting & Error Code Resolution Matrix

When debugging failed link previews across development, staging, and production environments, refer to this error resolution matrix:

HTTP Status / Error Scraper Behavior Root Cause Actionable Developer Fix
401 Unauthorized Plain URL rendered, no image or text Staging environment protected by Basic Auth or IP whitelist Allowlist crawler User-Agent strings or test on public preview URLs.
403 Forbidden Scraper skips metadata extraction Web Application Firewall (WAF) or Cloudflare Bot Management blocking scrapers Add WAF custom rules to bypass verified social bots (Twitterbot, facebookexternalhit, LinkedInBot).
404 Not Found Error page metadata cached Scraped URL does not exist or has an unhandled redirect Ensure canonical trailing slashes match server routing. Inspect with Head Auditor.
SSL Handshake Failure Scraper aborts connection immediately Missing intermediate SSL certificate or expired TLS cert Install full certificate bundle. Audit security with Security Headers.
Timeout (3.0s+) Text-only link with no thumbnail Slow server response time or SSR cold starts Cache HTML responses at the edge or use static pre-rendering.
Stale Preview Cache Shows old headline/image after deploy Social platform CDN cache still active Invalidate via Facebook Debugger or LinkedIn Post Inspector.

For an in-depth walkthrough on cache purging, read How to Fix Cached Previews on LinkedIn & WhatsApp.

The Complete Technical SEO & Social Ecosystem

A world-class digital presence requires harmonizing social metadata, search engine rich results, crawl directives, and AI agent context:

  1. Live URL Inspection: Audit your production URLs with our Open Graph Inspector to detect missing properties before publishing.
  2. Twitter Card Generation: Ensure large banner rendering with our Twitter Card Generator.
  3. Structured Search Data: Unlock star ratings and FAQ rich snippets with our JSON-LD Schema Generator and validate with our Schema Inspector.
  4. Crawl Budget Management: Verify search engine bot permissions using our Robots Simulator and build compliant files with our Robots.txt Builder.
  5. AI Knowledge Architecture: Format repository knowledge for AI coding agents (Cursor, Claude Code, Windsurf) using the Open Knowledge Format (OKF) Generator and explore the OKF Developer Guide.

Generate and validate your full metadata stack with our free Open Graph Generator today!

More Articles
Advertisement

Related Articles

Does Open Graph Help SEO?

6 min read

Dynamic Open Graph Images: Complete Guide

8 min read

How to Test Open Graph Tags

6 min read