OG Tags Checker
When someone shares your link on Twitter, LinkedIn, or Slack, Open Graph tags control the preview card. Broken OG tags mean broken previews — no image, wrong title, or a generic fallback. An OG tags checker catches these before your content goes viral with a broken card.
Essential Open Graph Tags
The four required OG tags are og:title, og:description, og:image, and og:url. Together they define the preview card that social platforms render when someone shares your link. Missing any one of them results in a degraded or generic preview.
og:type specifies the content type — 'website' for homepages, 'article' for blog posts. og:site_name provides branding context. og:locale specifies the content language. These are optional but recommended for complete social previews.
Twitter has its own tags: twitter:card (summary or summary_large_image), twitter:title, twitter:description, and twitter:image. While Twitter falls back to OG tags, dedicated Twitter tags give you more control over the card format.
OG Image Requirements
The recommended OG image size is 1200x630 pixels with a 1.91:1 aspect ratio. This works across Facebook, Twitter, LinkedIn, Slack, and Discord. Images outside this ratio may be cropped unpredictably.
The og:image URL must be absolute (starting with https://), publicly accessible, and return a valid image. Relative URLs, localhost URLs, and URLs behind authentication will not render. The image should be under 5MB for reliable loading.
In Next.js, use the opengraph-image.tsx convention to generate dynamic OG images per route. This eliminates the need to maintain static images and ensures every page has a unique, relevant preview image.
Common OG Tag Mistakes
The most common mistake is missing og:image entirely. When shared on social media, the link shows a text-only card that gets significantly less engagement than a card with a visual preview.
Using relative URLs for og:image is another frequent error. Social platforms fetch images from your URL — a relative path like '/og.png' does not resolve without your domain. Always use absolute URLs like 'https://yourdomain.com/og.png'.
Duplicate og:title and og:description across all pages happens when a layout sets static OG tags and pages do not override them. Each page should have unique OG tags that match its specific content, not generic site-wide defaults.
Validating OG Tags
Facebook's Sharing Debugger and Twitter's Card Validator let you preview how a specific URL will appear when shared. They also show errors and warnings about your OG tags. But they only check one URL at a time.
Indxel validates OG tags across your entire site in a single command. It checks: presence of all required OG tags, og:image URL resolution and dimensions, og:title length, twitter:card type, and consistency between HTML meta tags and OG equivalents.
Integrate OG tag validation into your CI/CD pipeline. When a developer creates a new page without an og:image or with a broken image URL, the build fails. No more discovering broken social previews after someone tweets your blog post.
Frequently asked questions
What happens if OG tags are missing?
Social platforms fall back to the page title and attempt to extract a description and image from the content. The result is usually a generic, text-only card with no visual preview, which gets significantly less engagement.
What is the best og:image size?
1200x630 pixels with a 1.91:1 aspect ratio. This works across all major platforms: Facebook, Twitter, LinkedIn, Slack, and Discord. Keep file size under 5MB.
Do I need separate Twitter Card tags?
Twitter falls back to OG tags, but dedicated twitter:card, twitter:title, and twitter:image tags give you more control. Specifically, twitter:card lets you choose between summary and summary_large_image formats.
Learn more
Related guides
Meta Tags Checker
Meta tags are the first thing search engines read on your page. A missing title, a truncated description, a broken canonical — each one costs you rankings or clicks. A meta tags checker validates them all systematically.
Meta Description Checker
Meta descriptions appear as the snippet in search results. Too long and they get truncated. Too short and they waste SERP real estate. Missing entirely and Google writes its own. A checker catches all three problems.
Next.js SEO Checklist 2026
A checklist you can run through before every deploy. Covers the metadata, structured data, performance, and indexation checks that matter for Next.js App Router projects. No fluff — just the items that affect rankings.