WordPress Social Share Image Not Showing? 9 Checks for Affiliate Blogs

WordPress social share image not showing? You can publish a polished article with the right featured photograph, open it on your website, and still see a missing thumbnail or yesterday’s image when someone shares the link on Facebook or LinkedIn. It is tempting to upload the picture again, change SEO settings, or resend the entire social campaign. Those reactions can create duplicates without identifying what actually failed.

The first question is simpler: Are you looking at a link-preview card, an image attached to a social post, or the image displayed on the WordPress page? Those are related but different things. Their images can come from different settings, and fixing one does not necessarily change the others.

This guide walks through nine specific checks for affiliate bloggers using WordPress, Rank Math, and Jetpack Social. You’ll learn what to examine before publishing, how to investigate a wrong or missing Open Graph image, what a social platform may have cached, and when to retry only a failed share. You do not need to install another plugin merely because a preview looks wrong.

First, Identify Which Image Is Actually Wrong

Suppose an affiliate article has a large photo at the top and the same photo selected as its WordPress Featured Image. You paste the permalink into LinkedIn, but LinkedIn shows an older photograph. Alternatively, Jetpack’s preview looks fine, yet Instagram never receives the image. Those symptoms point to different checkpoints.

Practical distinction: An image can appear correctly on your WordPress article while the link-preview card remains wrong. Conversely, an attachment can look correct on the social network even if the site’s Open Graph metadata still needs attention.

Check 1: Confirm the Article Is Public and You’re Using Its Final URL

Begin with the actual public permalink rather than a temporary editor preview, draft link, or shortened link you have not tested. Open it in a logged-out browser window. Confirm the post loads normally, the expected headline appears, and the featured photograph is visible where the theme displays it.

A social crawler may not be able to read a page that is restricted to logged-in visitors, requires special access, redirects unexpectedly, or returns an error. Test the final permalink and note any recent slug change or redirect before blaming the image itself.

Also distinguish a public article from a scheduled article that has not gone live. A preview inside the WordPress editor may be available to you while the public version is not yet accessible to social platforms.

Check 2: Verify the Featured Image, Not Just the Picture in the Body

The first full-width photograph inserted into an article is not necessarily the WordPress Featured Image. These can happen to be the same file, but selecting an Image block inside the body does not always assign it as the featured thumbnail.

1. Open the relevant WordPress post for editing.
2. Choose the Post settings tab rather than the settings of an individual image block.
3. Find Featured image and confirm the intended file is selected.
4. Check that it is the correct photograph and not an earlier draft or thumbnail.
5. Save the draft or update the post, then inspect the public page again.

WordPress documents the featured-image control in its official Post Settings sidebar guide. Themes may use the image differently on archive cards, single articles, and other layouts, so a correct featured-image setting is an essential first check but not proof that every platform will use it.

Check 3: Inspect the Open Graph Image the Page Declares

Most social link previews rely on metadata published in the webpage’s HTML. One key field is og:image, which supplies an image URL intended for link previews. WordPress SEO plugins can generate this metadata automatically, and some allow a separate image for a specific post.

To inspect the published output:

1. Open the final article URL in a browser.
2. Choose View Page Source, not the WordPress Code Editor.
3. Search the source for og:image.
4. Look at the image URL in the content attribute.
5. Check whether that URL refers to your intended image and opens successfully when visited directly.

For illustration, the page source may contain a tag shaped like this:

<meta property="og:image" content="https://example.com/uploads/article-photo.jpg" />

This is an inspection example, not code to paste into your WordPress article. The actual Open Graph metadata belongs in the HTML head, normally managed by your configured SEO or social integration.

What if no image appears, or the wrong one is declared?

Rank Math explains that its image selection can prioritize a post-specific Open Graph image, followed by the featured image, the first suitable image in the article, and a configured fallback. Check the Rank Math Social controls on the individual post only if the published source demonstrates a mismatch. See Rank Math’s Open Graph metadata guide for details.

Do not insert a second SEO plugin or manually add an extra og:image tag just to increase the number of tags. Duplicate or conflicting Open Graph declarations can make it harder to identify which image a platform should select.

Check 4: Check Image Size, Format, and Accessibility

An image should be large enough for the social network’s preview format and accessible from a public URL. A landscape image around a 1.91:1 ratio is a practical starting point for many link previews; Rank Math references 1200 × 630 pixels as a recommended Open Graph size, while LinkedIn documents a similar 1.91:1 shape for large preview images.

These are guidelines rather than universal guarantees. An image may be cropped or presented differently by platform and device. A photograph that is only a few hundred pixels wide may appear as a small thumbnail or fail to provide the desired large-card presentation.

File formats also matter. A WebP may be suitable for a fast WordPress article, while social-platform link previews and native uploads have their own supported formats and requirements. If a particular network fails with one image, inspect its current media rules and the output it actually sees before changing the image format across your whole site. For a targeted fix, a separate compatible JPEG or PNG social image may be useful without replacing the optimized image inside the article.

Open the exact image URL listed in og:image in a logged-out browser. If it fails, returns an access error, or points to an obsolete file, the platform may have nothing suitable to fetch. If the image opens correctly, continue the diagnosis rather than assuming the issue is solved.

Check 5: Separate a Stale Link Preview From an Incorrect Website Image

Sometimes WordPress already sends the correct Open Graph metadata, but a social platform still displays an image captured when the URL was shared earlier. The platform may be showing a cached preview rather than reading your article again at that moment.

For LinkedIn, use its official Post Inspector guidance: submit the exact public URL and review the resulting preview. LinkedIn explains that using the inspector can refresh its cached preview for future shares. It also cautions that existing posts containing the same URL may retain their old previews.

For Facebook link cards, the Meta Sharing Debugger can be used, where accessible, to examine fetched Open Graph information and request another scrape after the underlying website metadata has been corrected.

Use the tools in that order: first confirm the published page and image URL are correct; then inspect the relevant platform’s cached view. Repeatedly pressing refresh on a debugging page is not a substitute for repairing an actual missing tag or blocked image.

What about WordPress or CDN caching?

If you changed the featured or social image but the HTML source itself still shows an earlier URL, an applicable page or host cache may need to refresh. Clear the relevant cache through your site’s supported controls, then view the public page source again before asking the social platform to re-fetch it. You generally do not need to deactivate caching sitewide or purge unrelated pages.

Rank Math’s troubleshooting guide for missing Open Graph images describes file accessibility, dimensions, plugin conflicts, and cache-related causes. The important lesson is to identify the failing layer before changing several systems at once.

Check 6: Confirm Whether Jetpack Is Sharing a Link Preview or an Image Attachment

Jetpack Social introduces a distinction that can explain many apparent contradictions. Depending on your configuration, you can share a link with a generated preview card or share the selected image as attached media. These are different presentations, and Share as attachment is not the same thing as repairing your page’s Open Graph link-preview data.

Jetpack documents its Social Preview and media customization options. For a new WordPress post, inspect the Jetpack or Social sidebar before publishing:

1. Confirm Auto-share post is enabled only for the accounts you intend to use.
2. Open Preview and customize and examine the selected account previews.
3. Check whether the desired featured or custom image is actually selected under Media.
4. Confirm whether you are using a link preview or Share as attachment.
5. Check that the message and destination URL are accurate.

For example, Facebook could receive a correctly attached photograph from Jetpack even while a manually pasted link in a separate post displays an outdated Open Graph thumbnail. That points to a link-preview metadata or cache issue, not necessarily a failure of Jetpack’s attached-media workflow.

Do not switch sharing modes indiscriminately after publication. First inspect the real outcome and decide which presentation you actually want.

Check 7: Verify the Individual Sharing Results, Not Just the Switches

A correct Jetpack preview and three enabled social accounts indicate that sharing has been configured. They are not evidence that all three platforms successfully received a public post.

Jetpack’s social-sharing documentation describes the Sharing Activity view. After a post is published, open that activity and check each destination’s status. You may see Shared, Failed, or other pending information depending on the stage.

If one network fails:

• Read the specific error if Jetpack provides one.
• Check the actual public social profile or page before treating the post as absent.
• Confirm the media is valid for the failed platform.
• Retry only the failed item when the cause has been addressed and the service permits it.
• Do not resend successful Facebook or LinkedIn posts simply because Instagram failed.

Similarly, WordPress’s Published status, a newsletter send setting, and a queued Pinterest Pin are different checkpoints. A WordPress post becoming public does not establish that every downstream delivery happened successfully. Our WordPress missed-schedule checklist explains this separation for scheduled articles.

Check 8: Treat Instagram’s Media Requirements Separately

Instagram feed posts are image- or video-centered, so a standard URL link preview does not function in the same way it does when someone pastes a web address into LinkedIn. For Jetpack’s Instagram integration, the post needs eligible featured or custom media and a successful delivery to the connected account.

Jetpack’s official Instagram sharing guide explains the supported media workflow and image requirements. A correct Open Graph tag alone is not enough to establish that an Instagram post has been sent.

If the Instagram share reports a media-processing error, inspect the connection and media requirements, allow an appropriate interval if processing is still underway, and retry only the failed Instagram share if appropriate. Verify the public result on the Instagram account rather than treating the WordPress auto-share toggle as a delivery receipt.

Remember that ordinary Instagram captions are not equivalent to clickable article-link cards. Your caption should be understandable even when readers must use a separately provided path to find the article.

Check 9: Fix the Correct Image Without Breaking Your Content or Tracking

If the problem is limited to a social preview, don’t rush to replace a perfectly good featured image throughout your site. An approved article photograph might also appear in homepage cards, category archives, newsletters, and Pinterest Pins. Changing it can affect several surfaces that already work.

Make the smallest correction that resolves the observed problem:

• If the Featured Image is unset, assign it in WordPress and recheck the published output.
• If Rank Math points to an older per-post social image, update that specific setting and verify og:image.
• If the image URL is inaccessible, repair the URL or file access before asking platforms to refresh.
• If LinkedIn has cached an earlier preview, use Post Inspector after confirming the source is correct.
• If the Jetpack attachment is wrong, inspect its selected Media and the relevant share status.
• If just one connected network failed, correct and retry that network rather than creating duplicates everywhere.

Keep your affiliate redirects, approved referral IDs, and destination URLs separate from these image fixes. Repairing a thumbnail should never silently change an affiliate link to a generic vendor page or alter a UTM-tagged campaign URL. For legitimate traffic attribution, see our UTM tracking guide.

Quick Symptom-to-Action Troubleshooting Table

A Ten-Minute Social Image Audit Before Publishing

For a new affiliate blog article, a short repeatable check is usually better than an expensive new toolkit:

1. Set the Featured Image. Confirm the exact file in the WordPress Post settings.
2. Use a suitable landscape source. Make sure the selected image has adequate resolution and a composition that survives social crops.
3. Inspect the SEO/social preview. Check the headline, excerpt, image selection, and any intentional custom Open Graph image.
4. Check the final permalink. Do not use an editor draft preview or obsolete slug.
5. Review Jetpack media mode. Know whether the post will use a link card or an image attachment.
6. Verify the selected accounts. Make sure only the intended social connections are enabled.
7. Check the public page after publication. Verify the featured image and final URL load outside the editor.
8. Inspect Sharing Activity. Record which networks actually report success or failure.
9. Refresh platform caches only if necessary. Use a platform inspector when the current site metadata is correct but a link preview remains stale.

The checklist is about reliability, not chasing a particular social-media image score. Good photographs, useful article content, accurate descriptions, and functional links still matter more than decorative preview tweaks. For ways to turn an article into a wider distribution plan without repeating the same message everywhere, read how to turn one affiliate blog post into useful social content.

Frequently Asked Questions

Why does my WordPress Featured Image look correct, but LinkedIn shows an older picture?

The social network may be using cached link-preview information, or the page’s Open Graph metadata may still point to an earlier image. Check the published og:image first, then use LinkedIn Post Inspector if the website’s current metadata is correct.

Does Share as attachment fix a broken Open Graph image?

Not necessarily. An attached social image and a link-preview card are different outputs. Attachment sharing may display the selected photo on a social post without changing the website metadata that a manually pasted URL uses.

Do I need to stop using WebP for all my blog photographs?

No. WebP is useful for WordPress images, but different platforms and media modes have their own requirements. Test the actual social preview and, if a format-specific problem is confirmed, use a suitable supported image for that channel rather than replacing every optimized image.

Should I publish the same article again after correcting its social thumbnail?

Usually not. First determine whether the problem is website metadata, a cached link preview, or an unsuccessful social share. Repair the affected layer, and avoid duplicating an article, newsletter, or social post that has already succeeded.

Can I tell whether Facebook, LinkedIn, and Instagram worked from the WordPress Publish screen?

The Publish screen can confirm publication settings, but it does not establish successful delivery on every network. Check Jetpack Sharing Activity and the actual social destinations for post-specific outcomes.

Do better social preview images guarantee more affiliate conversions?

No. A clear preview can help visitors recognize your article, but clicks, engaged reading, qualified customer purchases, and paid affiliate commissions are different outcomes. Evaluate genuine audience behavior rather than promising revenue from an image change.

Final Thoughts: Diagnose the Preview, Not the Entire Website

When your WordPress social share image is not showing, start by determining where it is missing: on the actual webpage, in Open Graph metadata, in a cached link card, or in an attached social post. Then work through the smallest relevant checks instead of changing plugins, uploading every photograph again, or resending successful shares.

A correct Featured Image, accessible image URL, consistent Open Graph data, deliberate Jetpack media selection, and platform-specific delivery verification give you a dependable publishing process. That reliability helps your content travel without unnecessary cleanup, while keeping readers focused on the value of the article rather than the mechanics of its thumbnail.