Fixing og:title vs Page Title Mismatch

Resolve mismatches between og:title and the page <title> that cause social platforms to render unexpected previews.

1. Identify which pages are affected

The first step is to get the complete list of affected pages from your audit. Don’t try to fix in isolation — you need to see every instance to spot patterns and apply the fix consistently.

2. Understand the root cause

Before applying a fix, understand why the issue exists. Symptom-level fixes that don’t address the root cause tend to regress — the same problem reappears the next time a deploy or content update happens.

3. Apply the fix

Apply the fix consistently across all affected pages. Test on staging or a small sample first to confirm the fix pattern works before bulk-applying.

4. Verify the fix is working

Re-run the audit to confirm the issue is resolved. Don’t take the fix on faith — the audit needs to show the issue is gone before you mark it complete.

5. Monitor for recurrence

Add monitoring so the issue is caught quickly if it returns. Most issues that get re-introduced come from CMS updates, plugin changes or new content that doesn’t follow the pattern — catching them within hours rather than weeks limits the damage.

What a mismatch actually costs

Before the fix, the scope. An og:title that disagrees with the page title is not a ranking problem: Open Graph tags are not ranking signals. Google does not use og:title or og:description, and no mismatch between them will move you a single position.

What it costs is the share — and on most sites, shares are the warmest traffic there is. Somebody has personally recommended your page into a Slack channel, a WhatsApp group, or a LinkedIn feed, and the preview is what their audience judges it by.

What the reader sees when the title is wrong:
  - A headline that does not match the page they land on
  - Or a headline that describes a different product
  - Or your brand name, and nothing else useful

What that does:
  - Fewer clicks on a recommendation somebody
    was generous enough to make
  - And, when they do click, a small jolt of
    "this isn't what I was promised"

So fix it, and fix it for that reason. Anybody presenting an OG mismatch as an SEO emergency is either confused or selling something.

The cache, and why the fix appears not to work

The single most common follow-up to this fix is somebody reporting that it did not work. Almost always, it did — and the platform simply is not looking.

Facebook, LinkedIn, Slack, Discord and the rest fetch your page once, when a link is first shared, and keep what they found. They do not come back to check. Editing the tag afterwards changes nothing about a preview that is already stored, because nothing is reading your page any more.

None of them publishes how long that cache lasts, and the specific durations you will see quoted online are community guesses. So do not try to wait it out:

After fixing the tag, force a re-fetch:
  Facebook  → Sharing Debugger, "Scrape Again"
  LinkedIn  → Post Inspector
  Slack/Discord → usually a query parameter forces
                  a fresh fetch

Only then promote the URL.

Where mismatches come from

The root-cause work above is right, and the causes are consistent enough to be worth listing. A mismatch is nearly always a second source of truth that somebody introduced without noticing.

1. An SEO app or plugin sets og:title from its own
   field, while the page title comes from the CMS.
   Two fields, two humans, guaranteed to diverge.

2. The theme hardcodes an og:title in the layout,
   so every page shares one, and only the homepage
   is correct.

3. A template appends a brand suffix to the page
   title but not to og:title, or the reverse.

4. Two plugins both emit og:title, and the platform
   takes whichever it sees first.

5. Somebody edited the page title and never knew
   there was a second field to update.

Notice that every one of these is the same bug: the same fact is stored in two places. Anything typed twice will diverge, and the divergence will be silent — because nothing renders og:title on screen, nothing errors, and nobody complains.

The fix that lasts: one source, or a deliberate difference

There are two defensible configurations, and the failure is being in neither.

Derive og:title from the page title. The right default for most sites. One field, one truth, and the mismatch class of bug disappears permanently. If your CMS or theme lets you fall back to the page title when no override is set, use it — and remove any hardcoded og:title from the layout while you are there.

Or make it deliberately different, and know why. There is a legitimate case for this: the page title is written for a search results page, where the reader has typed a query and is scanning; the og:title is written for a feed, where nobody was looking for you at all. Those can reasonably be different sentences.

Page title  → "Waterproof Trail Running Shoes | Acme"
              (matches what somebody searched)

og:title    → "The trail shoe that survived a winter
               in the Peak District"
              (earns a click from somebody scrolling)

That is a real, intentional difference and it is worth having on the handful of pages that actually get shared. What you must not have is a difference nobody chose — which is what an audit flags, and which is the entire subject of this page.

Fix the source, not the pages

The CSV export invites you to work through the list, and on a mismatch of this kind the list is usually a symptom of one broken template. Fixing four hundred pages by hand, one at a time, is a way of spending a week and leaving the cause in place — so the next content update reintroduces it.

So diagnose before you edit: view source on three affected pages from different templates. If they share the same defect, it is a template problem, and one fix clears the whole list. If they differ, you have several problems wearing one label, and the CSV is telling you so.

And when it is fixed, assert it. A check that fetches one URL per template and compares the og:title to the rendered page title is a few lines of code, and it is the only thing standing between you and the same mismatch reappearing on a deploy nobody connected to social previews. This category of bug has no natural feedback loop: the page renders perfectly, nothing errors, and the first person to notice is a customer looking at a preview that does not make sense.

Frequently Asked Questions