Have you shared a WordPress page on Facebook, LinkedIn, or another social platform, only to discover that the preview image is missing, outdated, or completely wrong?
Maybe the platform displays your website logo instead of the featured image. Perhaps it shows an old image that you replaced days ago. Or the link preview contains the correct title and description but leaves the image area blank.
These problems can make your content look unfinished and reduce its visual appeal when people share your website.
In most cases, the issue is related to Open Graph metadata, image accessibility, caching, conflicting SEO settings, or the way social platforms retrieve and store preview information.
The good news is that you can diagnose most WordPress social preview problems without changing your theme or rebuilding your pages.
In this guide, you will learn how Open Graph images work, why social platforms sometimes display the wrong preview, and how to fix missing or outdated images using WordPress, Rank Math, Yoast SEO, and social sharing debugging tools.
What Is an Open Graph Image?
An Open Graph image is the image that websites can suggest to social platforms when someone shares a link.
It is defined using metadata in the HTML of a webpage.
For example, when someone shares a blog article on Facebook or LinkedIn, the platform may retrieve information such as:
- The page title.
- The page description.
- The website or article URL.
- The featured preview image.
Open Graph metadata helps platforms understand how a link should be presented.
The image is particularly important because it gives people a visual indication of what they can expect before opening the page.
However, Open Graph metadata does not force every platform to display a particular image. Each platform has its own preview generation, caching, and presentation rules.
How Does an Open Graph Image Work?
A typical Open Graph image declaration looks like this:
<meta property="og:image" content="https://example.com/images/article-preview.jpg">This tells compatible platforms which image the website recommends for the shared URL.
Other Open Graph properties commonly include:
<meta property="og:title" content="Example Article Title">
<meta property="og:description" content="A short description of the article.">
<meta property="og:url" content="https://example.com/article/">
<meta property="og:type" content="article">These tags are usually generated automatically by WordPress SEO plugins.
If the image tag is missing, incorrect, or points to an inaccessible file, the social platform may choose another image or display no image at all.
Why Is Your WordPress Open Graph Image Not Showing?
Several issues can prevent social platforms from displaying your intended preview image.
The most common causes include:
- Missing or incorrect
og:imagemetadata. - No social sharing image assigned to the page.
- An outdated image stored in the platform’s cache.
- Multiple plugins generating conflicting Open Graph tags.
- Incorrect image dimensions or an unsupported format.
- An image URL returning a 403, 404, or server error.
- CDN or security rules blocking social crawlers.
- HTTP and HTTPS inconsistencies.
- Social metadata not appearing in the initial HTML.
- A platform choosing a different image despite valid metadata.
Before changing settings, determine whether the problem affects one platform or several.
If Facebook, LinkedIn, and other services all display the wrong image, the issue may originate from your website.
If only one platform displays an outdated image, its cached preview is a more likely explanation.
1. Check Whether Your WordPress Page Has an Open Graph Image
Start by inspecting the metadata generated by your website.
Open the affected page in your browser.
Right-click and select:
View Page Source
Search for:
og:image
You should find a declaration similar to:
<meta property="og:image" content="https://example.com/wp-content/uploads/social-preview.jpg">Some SEO plugins also generate additional metadata, including image width, height, and type.
For example:
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:type" content="image/jpeg">These additional properties can help compatible platforms interpret the image.
What If the og Tag Is Missing?
If no og:image declaration exists, check whether your SEO plugin’s social metadata features are enabled.
Also confirm that the page has an appropriate featured image or dedicated social sharing image.
Not every WordPress theme generates Open Graph metadata automatically.
WordPress featured images and Open Graph images are related, but they are not the same thing.
A featured image is part of WordPress content management. An Open Graph image is a metadata declaration used by external platforms.
What If the Tag Exists but Points to the Wrong Image?
Check which plugin or theme is generating the tag.
The page may be using a default social image instead of the intended article image.
You may also have a page-specific social image overriding the featured image.
Correct the source image in your SEO plugin, save the page, and check the generated HTML again.
2. Fix Open Graph Images in Rank Math SEO
Rank Math allows you to control social sharing metadata for WordPress posts and pages.
If you use Rank Math, start by opening the affected post or page in the WordPress editor.
Set a Facebook Sharing Image
- Open the post or page.
- Open the Rank Math SEO panel.
- Navigate to the Social settings.
- Select the Facebook preview options.
- Upload or select the image you want to display.
- Save or update the page.
Rank Math can use the featured image or fallback images when no dedicated social image is configured, depending on your settings.
However, assigning a specific image removes uncertainty about which image you intend to use.
Check the Default Open Graph Image
Rank Math also provides global social metadata settings.
Navigate to:
Rank Math SEO → Titles & Meta → Global Meta
Review the OpenGraph Thumbnail setting, if available in your version.
This image can serve as a fallback when a page does not have a more specific image.
A default social image is useful for pages without featured images, such as certain informational or utility pages.
However, individual blog posts generally benefit from relevant, article-specific images.
Verify the Generated Metadata
After updating the social image, open the public page source.
Check whether og:image references the intended file.
Do not rely only on the image shown inside the Rank Math editor.
The actual HTML served to visitors and social crawlers is what matters.
3. Fix Open Graph Images in Yoast SEO
Yoast SEO also provides controls for social sharing previews.
Open the affected post or page in WordPress.
Find the Yoast SEO panel and navigate to its social appearance settings.
Depending on your Yoast version and editor, the exact interface may vary.
Configure the Social Image
Select the image you want platforms to use when sharing the page.
Save your changes.
If no dedicated social image is provided, Yoast may use other available images, such as the featured image or a configured default.
Check Yoast’s Social Settings
Review the plugin’s social sharing configuration to make sure Open Graph metadata is enabled.
Avoid running multiple SEO plugins that generate overlapping social metadata without carefully controlling their output.
For example, if Rank Math and Yoast both generate og:image tags, the page may contain inconsistent image recommendations.
Confirm the Result
Open the page source and search for og:image.
Check the URL and any additional image properties.
Then test the URL using a social sharing debugger.
4. Use the Correct Open Graph Image Dimensions
Image dimensions are an important part of social sharing previews.
An image may load successfully but still be cropped unexpectedly or displayed as a small thumbnail.
For a typical large social sharing preview, 1200 × 630 pixels is a practical default.
This corresponds to an aspect ratio of approximately 1.91:1.
It works well for many Facebook and LinkedIn sharing layouts.
Recommended Image Settings
| Setting | Recommendation |
|---|---|
| Dimensions | 1200 × 630 px |
| Aspect ratio | Approximately 1.91:1 |
| Format | JPEG or PNG |
| File size | Optimized without sacrificing readability |
| Image content | Clear subject, branding, or relevant illustration |
| Text | Large enough to remain readable when scaled down |
These are practical recommendations, not universal requirements for every social platform.
Each service can apply different image constraints and cropping behavior.
Avoid Excessive Text
Social previews are often displayed at relatively small sizes.
An image containing several paragraphs or tiny text may become unreadable.
Use a clear visual hierarchy and keep important elements away from the edges.
Check the Actual Image Dimensions
Do not assume that uploading a 1200 × 630 image means the platform receives that exact file.
Your SEO plugin or image optimization system may reference a different generated image size.
Open the URL found in og:image and check its actual dimensions.
If it points to a small thumbnail, select or generate a larger suitable image.
5. Check Whether the Open Graph Image URL Works
A correctly formatted Open Graph tag is not enough if the referenced image cannot be downloaded.
Social platforms must be able to retrieve the image from your server.
Test the Image Directly
Copy the URL from the og:image tag.
Open it in a new browser tab.
The image should load successfully.
If it does not, investigate the HTTP response.
Common problems include:
404 Not Found
The image file was deleted, moved, or referenced using an outdated URL.
403 Forbidden
A firewall, security rule, hotlink protection system, or access restriction may be blocking the request.
500 Internal Server Error
The server encountered an error while handling the request.
Unexpected Redirects
The image URL redirects to another domain, a login page, or an incorrect resource.
Check the Content Type
The server should return an appropriate image content type, such as:
image/jpeg
or
image/png
If the URL returns an HTML page instead of an image, social platforms may fail to generate the preview.
Check for Protected Images
Avoid using images that require authentication.
For example, an image hosted inside a private membership area or password-protected staging website may be visible to you while logged in but inaccessible to social crawlers.
Your Open Graph image should generally be publicly accessible.
6. Clear WordPress, Hosting, and CDN Cache
Caching can cause social platforms to receive outdated metadata even after you update the image in WordPress.
For example, your SEO plugin may save the new image correctly, but a caching system may continue serving HTML containing the previous og:image URL.
Clear Your WordPress Cache
If you use a caching plugin such as LiteSpeed Cache, WP Rocket, or W3 Total Cache, purge the affected page cache.
Then inspect the page source again.
Confirm that the correct Open Graph image URL is present.
Check Hosting Cache
Some hosting providers use server-level caching independently of WordPress plugins.
If your host provides page caching, clear the relevant cached page.
Check Cloudflare
If your website uses Cloudflare, review whether its cache contains outdated HTML or image resources.
Purge the affected URLs when necessary.
A full CDN purge is usually unnecessary for a single social preview image.
Use a New Image Filename When Appropriate
If you replaced an existing image while keeping the same URL, some caching systems may continue serving the old file.
Uploading the updated image under a new filename can help.
For example:
Old image:
https://example.com/uploads/article-preview.jpg
New image:
https://example.com/uploads/article-preview-v2.jpg
Update the social image setting to reference the new file.
Then clear the relevant caches and confirm that the HTML contains the new URL.
7. Fix Facebook Link Preview Images Not Showing
Facebook uses its own systems to retrieve and cache shared URL metadata.
This means updating your WordPress page does not necessarily update an existing Facebook preview immediately.
One of the most useful troubleshooting tools is Meta’s Sharing Debugger.
How to Use Facebook Sharing Debugger
Open:
Enter the URL of the affected WordPress page.
Run the debugging process.
Review the information Facebook retrieves, including the image, title, description, and any warnings.
If Facebook has previously cached the URL, use the available Scrape Again option to request fresh information.
What to Look For
Check whether Facebook detects:
- The correct
og:image. - The correct page title.
- The correct canonical or shared URL.
- An accessible image.
- Any warnings related to the metadata.
If the debugger shows the correct image but an existing Facebook post still displays the old one, the post or platform cache may not have refreshed.
A successful debugger result does not guarantee that every previously shared post will immediately update.
Common Facebook Preview Problems
Wrong Image
Check for duplicate Open Graph tags or an outdated default social image.
No Image
Verify that the image URL is accessible and uses a supported format.
Old Image
Clear the relevant website cache and request a fresh scrape.
Unexpected Crop
Use a suitable image aspect ratio and keep important content away from the edges.
8. Fix LinkedIn Preview Images Not Updating
LinkedIn also caches information about shared URLs.
You may update the Open Graph image in WordPress, but LinkedIn can continue displaying an older version.
LinkedIn provides a tool called Post Inspector.
How to Use LinkedIn Post Inspector
Visit:
Enter the affected page URL.
Inspect the result.
Review the image, title, and description LinkedIn retrieves.
Post Inspector can help refresh LinkedIn’s stored preview information for the URL.
If LinkedIn Still Shows the Wrong Image
Check the following:
- Does the page source contain the correct
og:image? - Does the image URL load without authentication?
- Is the image large enough for a proper preview?
- Are there duplicate Open Graph tags?
- Is LinkedIn inspecting the same URL you are sharing?
The last point is important.
For example, these URLs may not always be treated identically by caching systems:
Where possible, share the canonical page URL consistently.
Do not add arbitrary tracking parameters simply to force a new preview unless you understand the resulting URL behavior.
9. Why Open Graph Images May Not Work on WhatsApp or Other Platforms
WhatsApp and other messaging applications may generate link previews using their own fetching and caching systems.
Even when Facebook and LinkedIn display the correct image, another application may show a different result.
This does not automatically mean your WordPress metadata is incorrect.
Check Basic Compatibility
Make sure the shared page has:
- A valid title.
- A useful description.
- A publicly accessible Open Graph image.
- Correct HTTPS URLs.
- No unnecessary redirects.
- No restrictions preventing automated retrieval.
Avoid Relying on JavaScript-Generated Metadata
Some applications do not execute JavaScript in the same way as a normal browser.
If your Open Graph tags are inserted only after JavaScript runs, the preview crawler may never see them.
The metadata should ideally be present in the initial HTML response.
Check URL Variations
If the same page is accessible through several URL versions, preview caching can become inconsistent.
Use a consistent canonical URL and proper redirects.
For example, avoid unnecessarily sharing both HTTP and HTTPS versions of the same page.
Understand Platform Limitations
Some messaging applications provide limited debugging information and may cache previews for periods you cannot directly control.
If the metadata is correct and publicly accessible, the remaining issue may be platform-specific.
10. Check for Duplicate Open Graph Tags
Duplicate metadata is a common problem on WordPress websites with multiple SEO, social sharing, or theme optimization features.
For example, your page source might contain:
<meta property="og:image" content="https://example.com/old-image.jpg">
<meta property="og:image" content="https://example.com/new-image.jpg">Multiple og:image declarations are not automatically invalid. Open Graph supports multiple image values, with ordering indicating preference.
However, conflicting images generated unintentionally by different systems can produce unpredictable results across platforms.
Common Sources of Duplicate Tags
- Two active SEO plugins.
- Theme-generated Open Graph metadata.
- Social sharing plugins.
- Custom header code.
- Page builder integrations.
- Custom functions added to a child theme.
How to Find the Source
Open your page source and search for:
og:image
Review all matching declarations.
Then identify which plugin or theme is responsible.
Some plugins include HTML comments around their generated metadata, making the source easier to identify.
How to Fix Conflicting Metadata
Choose one primary system to manage Open Graph metadata.
Disable overlapping social metadata output from other plugins or theme features where appropriate.
After making changes, clear the cache and inspect the source again.
Do not remove valid alternative image declarations simply because more than one exists. The goal is to eliminate unintended conflicts.
11. Check HTTP, HTTPS, and Domain Configuration
Incorrect URLs can prevent social platforms from retrieving preview images.
For example, your website might load over HTTPS while the Open Graph image points to an old HTTP URL.
Although some platforms follow redirects, unnecessary redirect chains and inconsistent protocols can complicate image retrieval.
Check the Image URL
Your Open Graph image should ideally use an absolute HTTPS URL.
For example:
https://example.com/wp-content/uploads/social-image.jpg
Avoid relative paths such as:
/wp-content/uploads/social-image.jpg
An absolute URL is clearer and more reliable for external crawlers.
Check WordPress Settings
Navigate to:
Settings → General
Verify that the WordPress Address and Site Address are configured correctly.
If your website recently moved to a new domain, check whether Open Graph metadata still references the old one.
Check for Staging URLs
A common migration issue occurs when social images still point to a staging environment.
For example:
https://staging.example.com/wp-content/uploads/preview.jpg
If that environment is password-protected or inaccessible, the social image may fail to load.
Update the relevant image references and clear your cache.
If you recently migrated your site, our guide to moving WordPress to a new host explains additional checks that can help prevent broken URLs and configuration problems.
12. Check Robots.txt and Security Restrictions
Social crawlers need access to the page and image resources to generate previews.
If your website blocks these requests, metadata may not be retrieved correctly.
Check Robots.txt
Open:
https://example.com/robots.txt
Review whether important resources are disallowed.
However, remember that robots.txt behavior varies between crawlers.
A rule affecting Googlebot does not necessarily affect Facebook or LinkedIn in the same way.
Check Security Plugins
Some WordPress security plugins can block automated requests based on user agents, request patterns, or firewall rules.
If a social debugger reports that it cannot retrieve your page, check your security logs.
Look for blocked requests associated with the relevant URL and time.
Check Cloudflare WAF
If you use Cloudflare, review WAF events for requests to the shared page or image.
A bot protection rule or challenge page may interfere with automated metadata retrieval.
Avoid disabling your entire firewall.
Instead, identify the specific rule causing the problem and make a narrowly scoped adjustment when necessary.
13. Make Sure Open Graph Tags Are Present in the Initial HTML
This issue is especially important for websites using JavaScript-heavy themes, headless WordPress setups, or custom frontend applications.
Some websites generate metadata dynamically after the initial page has loaded.
A normal browser may display the correct information because JavaScript executes successfully.
However, many social preview crawlers do not rely on client-side rendering.
How to Test
Open your page using:
View Page Source
Search for:
og:image
Do not rely exclusively on the Elements panel in browser developer tools.
The Elements panel shows the current DOM, which may have been modified by JavaScript after the page loaded.
View Page Source is generally a better first check for the HTML originally returned by the server.
What If the Tag Only Appears After JavaScript Runs?
Your frontend may need server-rendered metadata.
For a standard WordPress website, a properly configured SEO plugin usually handles this automatically.
For headless WordPress websites, the frontend application should generate the relevant metadata in its initial server response.
This ensures social crawlers can discover the information without executing client-side JavaScript.
14. Check Featured Images and Social Image Overrides
A WordPress featured image is not always the image used in social previews.
Your SEO plugin may apply a hierarchy of image sources.
For example, it may prioritize:
- A page-specific social image.
- The WordPress featured image.
- A default social sharing image.
The exact behavior depends on your plugin and configuration.
When the Wrong Image Appears
Open the affected post or page.
Check its featured image.
Then inspect the social settings in your SEO plugin.
Look for a manually assigned social image.
If an outdated social image is configured, it may override the featured image.
When No Image Appears
Confirm that at least one appropriate image source is available.
For blog posts, using a relevant featured image is usually a good starting point.
However, a dedicated Open Graph image can provide more control over cropping, composition, and branding.
Use Consistent Social Image Designs
For a professional blog, consider using a consistent visual style across social previews.
This could include:
- A recognizable brand color palette.
- A clear article title or topic.
- A relevant WordPress illustration.
- Consistent typography.
- A small brand mark.
Consistency can make your content easier to recognize when shared.
However, avoid making every social image identical. Each article should still have a visually relevant image.
15. Open Graph Image vs. Twitter Card Image
Open Graph metadata is widely used across social platforms, but some services also support their own metadata formats.
X, formerly Twitter, supports Twitter Card metadata.
A typical configuration may include:
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Example Article">
<meta name="twitter:description" content="A short article description.">
<meta name="twitter:image" content="https://example.com/twitter-preview.jpg">The summary_large_image card type requests a larger image presentation when supported.
Do You Need Separate Images?
Not necessarily.
Many websites use the same image for both Open Graph and Twitter Card metadata.
A well-designed 1200 × 630 image is often suitable for both.
However, you may want separate images if your content requires different layouts or platform-specific branding.
Check Your SEO Plugin
Rank Math and Yoast can generate Twitter Card metadata.
Review the relevant social settings and confirm that the intended image is selected.
If your Open Graph preview works but the X preview does not, check the Twitter Card metadata separately.
16. Fix Open Graph Images After Changing a Featured Image
Suppose you publish a blog article and share it on LinkedIn.
A week later, you replace the featured image with a better design.
Your WordPress page now displays the new image, but LinkedIn continues showing the original preview.
This is a typical caching scenario.
Recommended Process
First, confirm that the featured image has changed on the public page.
Next, inspect the og:image tag.
If the metadata still references the old image, update the social image setting in your SEO plugin.
If the metadata references the new image, check whether the file is accessible.
Then clear any relevant WordPress, hosting, or CDN cache.
Finally, use the appropriate platform debugging tool to request updated preview information where supported.
Avoid Repeatedly Replacing Images
If the correct image is already referenced and accessible, repeatedly uploading new versions may not solve the issue.
The remaining delay may be caused by the platform’s own cache.
A stable image URL and consistent metadata are generally preferable to constant changes.
17. How to Test Your WordPress Social Previews Properly
After making changes, test the page systematically.
Do not assume that seeing the correct featured image in WordPress means social previews are fixed.
Step 1: Inspect the Page Source
Confirm that the correct Open Graph image URL appears in the initial HTML.
Step 2: Test the Image URL
Open the image directly.
Check that it loads successfully and displays the correct content.
Step 3: Check Image Dimensions
Verify that the image has suitable dimensions and a supported format.
Step 4: Check for Duplicate Tags
Review all og:image declarations and remove unintended conflicts.
Step 5: Clear Relevant Caches
Purge the affected page or image from WordPress, hosting, and CDN caches where necessary.
Step 6: Test Facebook
Use Meta Sharing Debugger to inspect the URL and review the retrieved metadata.
Step 7: Test LinkedIn
Use LinkedIn Post Inspector to check the preview and request updated information where supported.
Step 8: Check Other Platforms
Share the URL in the platforms that matter to your audience.
Remember that different services may crop, cache, or display images differently.
Step 9: Verify the Canonical URL
Make sure you are testing and sharing the intended public URL.
If the website redirects between domain versions or URL variations, use a consistent final URL.
Step 10: Retest After Major Changes
Repeat these checks after major theme changes, SEO plugin migrations, CDN configuration changes, or website migrations.
These changes can affect metadata output even when the visible page design remains unchanged.
18. How to Prevent Social Preview Problems in WordPress
Once your Open Graph images work correctly, a consistent publishing process can help prevent future issues.
Assign a Relevant Featured Image
Every important blog article should have a suitable featured image.
Avoid publishing posts with missing or unrelated images.
Use Dedicated Social Images When Needed
If the featured image is not suitable for social sharing, assign a separate Open Graph image through your SEO plugin.
Keep One Primary Metadata System
Avoid overlapping Open Graph output from multiple plugins or theme features.
Use one clearly configured system to manage social metadata.
Optimize Images Without Breaking Accessibility
Compress images appropriately, but make sure optimization plugins do not replace social images with unsupported or inaccessible resources.
Test Important Pages Before Sharing
For major announcements, product pages, or important blog posts, inspect the social preview before distributing the link.
Monitor Website Changes
After migrations, caching changes, or SEO plugin updates, verify that Open Graph metadata is still generated correctly.
For broader improvements to your site’s search visibility and content strategy, see our guide to getting more traffic to your WordPress website.
Quick Open Graph Troubleshooting Checklist
If your WordPress social preview image is missing or outdated, follow this order:
- Open the page source and find the
og:imagetag. - Confirm that the tag references the intended image.
- Check the featured image and social settings in Rank Math or Yoast.
- Open the image URL and verify that it loads.
- Check the image dimensions and file format.
- Look for duplicate or conflicting Open Graph tags.
- Clear the relevant WordPress, hosting, and CDN caches.
- Check for old domains, HTTP URLs, or staging image references.
- Review security and firewall restrictions if crawlers cannot access the page.
- Make sure the metadata appears in the initial HTML.
- Test the URL using Facebook Sharing Debugger and LinkedIn Post Inspector.
- Allow time for platforms to update cached previews when necessary.
This approach helps separate website configuration problems from social platform caching behavior.
Final Thoughts
A missing or outdated Open Graph image can make an otherwise professional WordPress page look incomplete when shared on social media.
Fortunately, most problems can be traced to a small number of causes: incorrect metadata, inaccessible image URLs, caching, conflicting plugins, or platform-specific preview behavior.
Start by checking the actual og:image tag in your page source. Then confirm that the image URL works and that your SEO plugin is generating the intended metadata.
If everything is correct on your website but a social platform still displays an old image, use its debugging tools where available and allow time for cached information to update.
A reliable social preview setup is a small but valuable part of maintaining a professional WordPress website.
If you want to improve your WordPress skills beyond individual troubleshooting problems, the WP Flow Mastery WordPress eBook brings together more than 160 pages covering WordPress hosting, performance optimization, SEO, security, WooCommerce, and practical website maintenance.
Written by Nemanja Stosic
WordPress Developer & Website Optimization Specialist
Nemanja has worked on more than 200 websites and focuses on WordPress development, performance optimization, SEO, security, WooCommerce, and practical website improvements.