Fix Competing Open Graph Tags and Publish Correct X Cards on WordPress

You paste a post URL into Slack, LinkedIn, or X. The preview shows the wrong image, a truncated leftover title, or a blank card. View source and you find two og:title tags, three image candidates, and a Twitter card that disagrees with Open Graph. The page looks fine in the browser. Social scrapers do not forgive duplicate heads.

That mess usually comes from two SEO plugins (or an SEO plugin plus a “social share” add-on) both printing meta. Each thinks it owns the document head. Scrapers pick whichever tag they see first, or give up and show junk.

Rankify is the DaftPlug SEO plugin. This post is about Open Graph and X (Twitter) cards with correct social previews, the warning when another plugin competes / duplicate OG output is detected, and how title/description templates feed social when appropriate. Run one SEO plugin at a time. Rankify can read Yoast / Rank Math / AIOSEO / SEOPress data in place when you switch. For title pixel width and schema graph hygiene, keep WordPress SEO titles, pixel truncation, and schema graph close.

What Rankify actually ships for OG and X cards

Feature list for this article:

• Open Graph and X (Twitter) cards aimed at correct social previews
• Warning when another plugin competes / duplicate OG output detected
• Titles and descriptions templates that feed social when appropriate
• One SEO plugin at a time; Rankify can read Yoast, Rank Math, AIOSEO, or SEOPress data in place

The contract is simple. One clean set of social tags. A visible warning if something else is still printing OG. Templates you already trust for search can inform social without a second messy system.

Why competing OG tags destroy previews

Open Graph and X card tags are instructions for scrapers, not humans. Scrapers are dumb on purpose. Two og:image values do not mean “artistic choice.” They mean undefined behaviour.

Common WordPress failure patterns:

1. Yoast (or Rank Math / AIOSEO / SEOPress) still outputs OG while a social plugin also does.
2. The theme prints legacy Twitter tags and the SEO plugin prints modern ones.
3. A page builder “share” module injects its own head tags on landing pages only.
4. Cached HTML keeps old tags after you disable a plugin, so scrapers and you disagree for days.

You cannot eyeball this from the rendered page. You need view-source or a debugger, plus a plugin that warns when competition shows up instead of silently stacking tags.

X cards (Twitter cards) still matter for previews on X even though the company renamed. Correct twitter:card, title, description, and image keep the large-image or summary card you intended. When OG and X tags disagree, you get platform-specific chaos: Slack looks fine, X looks wrong, or the reverse.

How to fix competing tags and publish clean cards in wp-admin

Assume Rankify is installed. If another SEO suite is still active, plan the cutover before you chase individual tags.

1. Run one SEO plugin at a time

Disable the outgoing SEO plugin’s social module, or deactivate the old SEO plugin once Rankify is ready. Two full SEO suites on one site is how duplicate OG happens.

Rankify can read Yoast, Rank Math, AIOSEO, or SEOPress data in place. That means you are not starting titles and descriptions from zero when you switch. Import or read what you already tuned, then let Rankify own output.

2. Open Rankify social / Open Graph / X card settings

In wp-admin, open Rankify and find Open Graph and X (Twitter) card controls. Confirm social previews are enabled and that titles/descriptions can follow your templates when appropriate.

Set defaults that match your brand: site name, default image fallback, card type expectations. Then override on key pages (homepage, flagship product, campaign landing pages) where the default image would look generic.

3. Respect the competing-plugin warning

If Rankify warns that another plugin competes or duplicate OG output is detected, treat that as a stop-ship for social. Find the other printer:

• Second SEO plugin still active
• Social share plugin with its own meta
• Theme “SEO / social” panel
• Page-builder head injection

Turn the duplicate source off. Do not try to “win” by printing harder. Scrapers do not award points for volume.

4. Align title and description templates with social

When templates feed social appropriately, your search title work carries into previews. That is good when titles are already human and pixel-aware. It is bad when you stuffed titles for SERPs and now those strings look greedy in Slack.

Use the pixel truncation and schema guide linked above for search-title craft. For social, prefer clarity and a real image over keyword piles. Spot-check a post URL in X’s card validator or by pasting into a private Slack channel after cache clears.

5. Clear caches and force a fresh scrape

After fixes:

1. Purge full-page cache and CDN HTML if you use them.
2. Re-fetch the URL in social debuggers (X card validator, Facebook sharing debugger, LinkedIn post inspector, as relevant).
3. Confirm a single og:title, a single primary image decision, and X card tags that match the story you want.

Old scraper caches lie. Rankify can be correct while a platform still shows last week’s image until you ask for a re-scrape.

6. Smoke-test the money URLs

Homepage, pricing, and top landing pages deserve manual preview checks after any SEO plugin change. Blog pagination and thin archives matter less than the URLs you actually share in ads and outreach.

What good looks like

A clean social setup feels uneventful:

• View source shows one coherent OG set and matching X card tags.
• Rankify is not warning about competing plugins.
• Shared links show the intended image and title in Slack, LinkedIn, and X.
• Templates feed social where it helps, with manual overrides on flagship pages.
• Only one SEO plugin owns head output; Rankify has read prior Yoast/Rank Math/AIOSEO/SEOPress data if you migrated.
• Re-scrapes after cache purge match what you see in Rankify’s preview fields.

If one platform still shows a bad image after a re-scrape, check absolute image URLs, image size floors, and whether the image is blocked for anonymous fetchers. That is a hosting or robots issue, not “need more OG tags.”

Pitfalls (the ones that bite)

Leaving two SEO plugins active “just during migration.” Duplicate OG loves transition weeks.

Ignoring the competing-plugin warning. It is the feature. Use it.

Fixing tags but never purging cache / re-scraping. You will swear Rankify failed when a CDN served antique HTML.

Keyword-stuffed titles flowing into social unchanged. Search and social audiences are not the same reader.

Theme plus plugin both printing Twitter tags. Disable the theme’s legacy social meta.

Assuming Free social plugins are harmless beside Rankify. Many still print OG. Check.

Practical checklist before you call it done

1. Keep a single SEO plugin active (Rankify).
2. Let Rankify read Yoast / Rank Math / AIOSEO / SEOPress data if you are switching.
3. Enable Open Graph and X cards; set defaults and flagship overrides.
4. Resolve any competing-plugin / duplicate OG warning before sharing campaign links.
5. Align title/description templates with social-safe copy.
6. Purge HTML caches.
7. Re-scrape key URLs in platform debuggers.
8. View-source confirm one clean tag set.
9. Re-check after the next theme update (themes love re-enabling old meta).

Takeaway

Broken link previews are rarely “X being weird.” They are usually two plugins printing Open Graph and nobody watching. Correct cards need one owner, clean tags, and a warning when competition creeps back.

Rankify publishes Open Graph and X cards for correct social previews, warns when another plugin competes, and can read your existing Yoast, Rank Math, AIOSEO, or SEOPress data in place so you are not starting from zero. Pair it with solid title and schema habits from the related guide.

One Pro membership unlocks Rankify plus Progressify, Lightify, Generatify, and Snapshotify. New Pro plugins join existing memberships. Plans differ by site count only. See pricing when you want shared links to look like the page you meant to share.

One SEO plugin. One OG set. Fix the warning, then re-scrape. That is the whole fix.