How to Fix Every Open Graph Finding

The OG / Twitter Tag Generator validates how your page renders when shared on Facebook, LinkedIn, Twitter (X), Slack, Discord, WhatsApp, iMessage. Each platform has slightly different requirements, and missing tags mean ugly link previews that hurt click-through. This index covers fixes for every finding.

New here?

Start with the Open Graph Guide for the spec and platform differences.

By finding type

OG findings fall into these categories:

❌ Fix missing core OG tags PLANNED

Required: og:type, og:url, og:title, og:description, og:image. Missing any of these and platforms fall back to scraping the page (badly). The minimum-viable OG block.

🖼️ Fix wrong OG image dimensions PLANNED

Facebook: 1200×630 (1.91:1). LinkedIn: 1200×627. Twitter summary_large_image: 1200×675 (16:9). The single-image-fits-all approach vs platform-specific. The minimum size to avoid crops.

🐦 Fix Twitter card markup PLANNED

twitter:card, twitter:site (your handle), twitter:creator (author's handle). Why Twitter falls back to OG but you should set explicit Twitter tags for control.

🌍 Fix OG locale issues PLANNED

og:locale for the primary language (en_GB). og:locale:alternate for additional languages your URL serves. Common bug: locale doesn't match the actual content language.

📷 Fix image-cache poisoning PLANNED

Facebook/LinkedIn aggressively cache OG previews. Updating an image doesn't update the cache. The cache-busting query-string pattern and the Facebook Sharing Debugger's force-refresh.

📐 Fix mismatched og:title vs <title> PLANNED

og:title should be the share-optimised version (can differ from SEO <title>). Common bugs: identical to title (wasted opportunity), or completely different (looks broken in preview).

🔗 Fix og:url to canonical mismatch PLANNED

og:url must match the canonical. Otherwise shares aggregate badly across URL variants (tracking params, trailing slash). The single-canonical-everywhere rule.

📰 Fix article-specific OG tags PLANNED

article:author, article:published_time, article:section, article:tag. These power richer Facebook/LinkedIn cards for editorial content.

By platform

Implementation patterns by platform:

📰 Fix OG in WordPress PLANNED

Yoast / Rank Math OG configuration, the per-post override, custom OG images for the homepage, plugin conflicts when multiple SEO plugins are active.

🛒 Fix OG in Shopify PLANNED

Theme-level OG tags, per-product OG image, the apps that add OG support, and the platform-level constraints on dynamic image generation.

⚛️ Fix OG in Next.js PLANNED

Metadata API openGraph property, dynamic OG image generation via Vercel OG, per-route OG defaults vs page-specific.

What our OG / Twitter Tag Generator checks

The generator builds the full OG and Twitter card block for your page, validates against Facebook, LinkedIn and Twitter requirements, predicts how the preview will render on each platform, and flags missing or invalid tags. For the full reference, see the Open Graph Guide.

🔗 Audit your social previews first

Run the generator. Bad OG kills social CTR by 50-70% — fix once, ship everywhere.

Open OG Generator →