Mismatched Open Graph Tags

What This Means

Open Graph tags are present and complete, but their values diverge significantly from the page's actual metadata — the og:title differs substantially from the <title> tag, or the og:description differs substantially from the meta name="description" tag. The divergence is beyond minor phrasing variation and appears unintentional.

Why It Matters for SEO

The most common cause is a page where the title, description, or content was updated but the OG tags were not refreshed. Someone changes the article headline to reflect a 2025 update, but the og:title still reads "2022 Guide to...". Users who find the page via search see the current title; users who share the link on social see the outdated one. This inconsistency looks like an error and reduces trust.

OG mismatch can also occur after CMS migrations, when OG data is stored in a separate field that isn't tied to the main content update workflow.

What the Platform Checks

The platform compares og:title against the <title> tag, and og:description against the meta name="description". It measures the divergence between the normalized strings and fires when the difference exceeds a meaningful threshold — flagging substantial mismatches while not flagging intentional minor differences (e.g., brand name removed from OG).

How to Fix It

Update the OG tags to reflect the current page content:

• If the mismatch is due to a page update: refresh the OG tags in your CMS to match the updated title and description.
• If the mismatch is intentional (different phrasing for social vs. search): review whether the difference still serves a purpose, and if so, document it as intentional in your CMS.
• Enable OG-to-metadata sync in your SEO plugin so updates to the title/description automatically update the OG tags.
• For static sites, check if your template pulls OG values from a separate field or from the shared title/description variable.

After updating, validate with a sharing debugger. Facebook and LinkedIn cache OG data — use the "Scrape again" function in their debuggers to force a re-fetch.