How to Fix Social Previews in WordPress (Facebook, Twitter, LinkedIn)

When sharing WordPress URLs to social media, the preview should be your branded image, title and description. When it isn't — wrong image, no preview at all, old cached version — engagement drops. This guide covers WordPress-specific social preview debugging across Facebook, Twitter, LinkedIn and WhatsApp. Pair with social preview guide and OG tag fixes.

Step 1: Test current preview on each platform

Facebook Sharing Debugger, Twitter Card Validator, LinkedIn Post Inspector, WhatsApp link preview (paste into a draft message). Note what each shows. Differences often indicate platform-specific issues.

Step 2: Fix common: missing OG image

Each post should have a featured image set (required for OG). Audit posts without featured images. Set default OG image in SEO plugin for posts where no featured image exists.

Step 3: Fix common: OG image too large or wrong dimensions

1200x630 ideal. Over 8MB rejected by Facebook. Wrong aspect ratios get cropped awkwardly. Audit and replace problem images. Use a plugin that auto-generates OG images at correct dimensions (Branda, OG Image Generator).

Step 4: Force refresh cached previews

Facebook: Sharing Debugger → Scrape Again. LinkedIn: Post Inspector → Inspect. Twitter: Card Validator typically refreshes on each test. WhatsApp: harder — they cache for ~30 days; sometimes require URL parameter to bypass (?v=2).

Step 5: Fix Twitter card type

Default should be summary_large_image (large hero image preview). Some plugins default to 'summary' (small thumbnail). Override in plugin's Social/Twitter settings.

Step 6: Fix WhatsApp preview-not-showing

WhatsApp requires: OG tags in first 4KB of HTML, og:image accessible without auth, image under 300KB, server returns 200 for image URL with proper Content-Type. Often fails on heavy WordPress headers — move OG tags up in .

Step 7: Set up monitoring

Periodically (monthly) re-test critical URLs in each platform's debugger. After major plugin updates, immediately re-test. Track OG image rendering — broken images on social are a slow-bleed brand issue.

Frequently Asked Questions

Why does Facebook show my old WordPress preview even after I updated it?

Facebook caches OG data 30 days. Force refresh via Sharing Debugger: paste URL → Scrape Again button. May need 2-3 scrapes. If still wrong: confirm og:image is absolute URL, image is publicly accessible (try in incognito), image meets size requirements.

LinkedIn shows wrong preview for my WordPress site — how do I fix?

LinkedIn caches more aggressively than Facebook — up to 7 days. Use linkedin.com/post-inspector to force a fresh fetch. If wrong values persist: check og:title, og:description, og:image are correct in source. LinkedIn ignores some Twitter-specific tags.

Do I need separate OG images for Twitter and Facebook?

No — same 1200x630 image works for both. Twitter uses og:image as fallback when twitter:image isn't set. Set og:image in your SEO plugin; Twitter inherits.

Why don't WhatsApp previews show for my WordPress site?

WhatsApp is the strictest: OG tags must be in first 4KB of HTML, image under 300KB, 1.91:1 aspect ratio. Heavy WordPress headers (multiple analytics, large schema blocks, polyfills) push OG tags beyond 4KB. Audit by 'curl -s URL | head -c 4096' — should include og:image.

Can I have different OG images for desktop vs mobile sharing?

No — there's no device-specific OG tag standard. Use one image that renders well at both 1200x630 (desktop) and the 16:9 cropped version mobile platforms sometimes show. Test in actual platforms across devices to verify rendering.

🔗 Audit social previews

See how your URLs render on Facebook, Twitter and LinkedIn.

Run Social Preview Audit →