Facebook chooses a WordPress link thumbnail from the page’s Open Graph metadata, especially the og:image tag—not simply from the post’s featured image. Set the intended social image, remove duplicate Open Graph output, verify that Facebook can fetch the image, and then request a fresh scrape in Facebook’s Sharing Debugger.
Why Facebook shows the wrong WordPress image
When a link is shared, Facebook reads metadata rendered in the public page HTML. The key image field is og:image. A featured image in WordPress is not proof that the page outputs the correct value.
Incorrect previews commonly come from an unintended og:image URL, duplicate tags emitted by a theme and a plugin (or by two plugins), an image Facebook cannot fetch, or an old cached scrape. Yoast notes that duplicate Open Graph tags can produce incorrect titles, descriptions, or images.
Fix the image in WordPress first
Set the post’s Facebook image
- Open the post or page in WordPress.
- Find the social or Facebook image controls in the SEO or social-metadata plugin already active on the site. Labels and locations vary by plugin.
- Choose the image you want Facebook to display and save or update the post.
Use the plugin that owns your site’s Open Graph output. Installing another SEO plugin is not required for this workflow.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
Check the rendered HTML
- Open the public post URL in a browser.
- View the page source and search for
og:image. - Confirm that the value is the intended, complete image URL.
- Check whether more than one
og:imagetag—or duplicate Open Graph title or description tags—appears.
If both a theme and a plugin generate Open Graph tags, or two plugins do so, choose one system to manage them and disable the competing feature. Conflicting values can make Facebook select the wrong content.
Use this diagnosis table
| What you find | Next action |
|---|---|
og:image is missing |
Enable or configure Open Graph output in the existing SEO or social plugin, then inspect the source again. |
og:image contains the wrong image |
Change the page’s social image in the plugin that owns the metadata. |
Several og:image or other duplicate Open Graph tags appear |
Remove the theme/plugin duplication so one system emits the tags. |
| The source is correct, but Facebook displays old information | Use Sharing Debugger and select Scrape Again to request a new fetch. |
| The intended URL is present but the image is not shown | Verify that the image is publicly reachable and investigate access blocks, server responses, or image-delivery errors. |
Only a missing fb:app_id warning appears |
Yoast says this tag is not required; concentrate on the image, title, description, and other reported errors. |
Refresh Facebook’s cached preview
- Open Facebook’s Sharing Debugger.
- Enter the public WordPress page URL and click Debug.
- Review the scraped metadata, warnings, and preview.
- After correcting WordPress output, click Scrape Again.
- Compare the debugger’s raw tags with the page source. They should contain the same intended
og:imageURL.
If WordPress, a caching plugin, a hosting cache, or a CDN is still serving the old HTML, clear the relevant cache before scraping again. Re-run the debugger after each metadata correction.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to tell where the problem is
WordPress output problem
The page source or debugger’s raw tags contain no og:image, the wrong URL, or conflicting values. Correct the plugin or theme configuration before requesting another scrape.
Facebook cache problem
The page source and debugger both show the new image, but a share composer still shows the former one. Request Scrape Again and allow Facebook to replace its cached result.
Rank #3
Image-fetch problem
The correct URL is present, but Facebook cannot retrieve the file. Test the image as a public URL and check for access restrictions, failed server responses, or other delivery issues. WordPress support reports describe such cases, but those community reports are anecdotal and do not identify a universal server fault.
Quick Recap
Best Value
Rank #4
Final checklist
- The intended image is saved in the page’s social metadata settings.
- One Open Graph system owns the output.
- The public source contains the correct
og:imagevalue. - The image URL is publicly fetchable.
- Relevant WordPress and server caches are cleared.
- Facebook Sharing Debugger shows the corrected raw tags after Scrape Again.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
