PlainFunnels Categories

Home / Categories / Editor

Why does Facebook show the wrong image when I share my page?

Short answer

systeme.io only controls the picture through each page's own Social media image field, under Settings, then the SEO section, and that setting belongs to one page, not the whole funnel. The most common cause is editing the image on a different page than the one being shared. Beyond that, systeme.io's documentation does not say what makes a network re-check a page it has already read once.

What systeme.io actually controls

The picture shown when a page link is shared comes from the Social media image field. Open the page, click Settings in the top left, scroll to Search Engine Optimization (SEO), and upload the image there.

That field belongs to the page, not to the funnel or the account. A funnel with five steps has five separate pages, each with its own image field, its own title and its own description.

The cause worth checking first

Sharing the wrong page's link is the simplest explanation, and the setup invites the mistake. An image uploaded on the sales page does nothing for the opt-in page in the same funnel, or for an older duplicate of the page still sitting in another funnel. Confirm the exact URL being shared is the exact page that was edited, before assuming anything else is wrong.

What systeme.io's documentation does not cover

Nothing in the help centre says what happens after a link has already been shared once. There is no mention of a network keeping its own copy of the preview, and no mention of anything to do to make a network look again after the field is changed.

That silence matters here. My own read is that the tag systeme.io writes follows the Open Graph protocol, the shared standard most sites use for preview images, because that is what the networks read. Nothing in systeme.io's own documentation says so, so treat what follows as an explanation rather than a documented rule. The protocol's own list of tools names a debugger and parser as one of the standard pieces of software built around it, separate from systeme.io entirely. Its existence suggests that a network reading a page once and not automatically reading it again is a normal part of how this works, though neither systeme.io nor the protocol's own page spells out the mechanism.

If the correct page has the correct image saved and a shared link still shows the old one, that is the boundary of what can be confirmed from documentation. A tool built for checking and refreshing that specific network's own reading of the page, rather than anything inside systeme.io, is the next thing to look at.

Did this answer your question?