Auto-Posted Images: How PostRSS Picks the Picture for Each Post

You publish a careful article with a striking photograph, and on the social network it appears with a tiny logo, a blurry crop or no picture at all. Auto-posted images are the part of automation that owners notice first and complain about most, and almost every case has a simple cause. PostRSS, the auto-posting service from the Internet Solutions team, takes the picture for each post from the feed item or, when the feed has none, from the Open Graph tags of the page, so that every post carries the real image of the article. This guide explains how that works, how to check which image your own pages offer, why the wrong picture appears, and how to fix it at the source, where the fix lasts.
The principle is worth stating at the start: PostRSS does not invent images, and it does not need to. It uses what your website publishes. If the right image is declared in the right place, it travels automatically to every network. If it is missing or wrong, no automation can guess it, but the cause is usually a setting you can change in minutes.
Where PostRSS finds the image
Two sources are used, in this order of thinking: the feed item itself, and the page that the item links to.
| Source | What it is | Where you control it |
|---|---|---|
| The feed item | A picture declared inside the item of your RSS or Atom feed, for example as an enclosure or a media element | In the feed settings of your content management system or plugin |
| The page’s Open Graph tags | The og:image address in the head of the article page | In the article editor or the SEO plugin settings |
The RSS specification allows a feed item to carry an enclosure, and the Media RSS extension adds richer media elements. Many content management systems include the featured image in the feed automatically, others need a setting or a plugin. If your feed carries no image, PostRSS can still read the Open Graph tags of the linked page, which is why a good Open Graph setup helps even when the feed is plain.
What Open Graph is, in one paragraph
Open Graph is a small set of tags in the head of a web page that tells social networks how to present the page when it is shared: the title, the description, the address and the image. The convention was introduced by Facebook and is documented at ogp.me. The image tag is called og:image. Almost every network that shows link previews reads it, and that is why one well-prepared image appears consistently in many places. We describe the wider topic in our guide on Open Graph and X cards.
How to check which image your pages offer
You do not need special tools to find out what PostRSS will see. A short check shows it.
- Open the feed. Look at the item for your newest article. Is there an image element? Copy its address and open it in a browser to see which picture it is.
- View the page source. Open the article page, view its source, and search for “og:image”. The address next to it is the picture social networks will use.
- Test it in a debugger. Facebook’s Sharing Debugger shows the preview that would appear and lets you refresh what it has stored. Other networks offer similar inspection tools.
- Compare with the real post. Look at what appeared on your network after the last automatic post, and compare it with the three results above.
If all three show the right image, the setup is healthy. If they disagree, you have found the cause.
The usual reasons for a wrong or missing picture
| Symptom | Likely cause | Where to fix it |
|---|---|---|
| The same logo on every post | The site declares one default og:image for all pages | SEO plugin: use the featured image of each article instead of a fixed default |
| No image at all | The article has no featured image and the feed carries none | Add a featured image to the article, and include images in the feed |
| A small or blurry picture | The image is smaller than the network wants | Upload a larger original, at least 1200 pixels wide |
| An image from the middle of the article | The tool picks the first image in the content | Declare og:image explicitly |
| The old image after you replaced it | The network keeps a stored copy of the preview | Refresh the stored preview in the debugger |
| Picture does not load | Hotlink protection, a firewall or a login blocks outside access | Allow public access to the image address |
| Wrong shape or cropped faces | The proportions differ from what the network displays | Prepare the image with safe margins around the subject |
Preparing images that work everywhere
Because one image will be reused on several networks, prepare it for the strictest case. Meta’s documentation for sharing for webmasters recommends large images, at least 1200 by 630 pixels, for the best display on high-resolution screens. A few habits make an image robust.
- Use a wide format. A ratio near 1.91 to 1, such as 1200 by 630 pixels, fits link previews on most networks. Bigger is fine if proportions stay the same.
- Keep the subject in the centre. Networks crop edges differently, so keep text and faces away from the borders.
- Make text large and short. Words on an image must remain readable when the preview is small.
- Avoid pale or empty backgrounds. An image that blends into the white feed of a network is easy to scroll past.
- Use a sensible file size. A few hundred kilobytes is enough, and large files may fail to load in time.
- Give each article its own picture. A different image per post tells followers at a glance that the post is new.
How the image fits into the post
The picture is one part of what PostRSS builds. The text of each post comes from the item title, the item description, the page title or your own static text, with nine combinations to choose from, and the link can carry your own parameters such as utm_source=postrss so that your analytics show what each network brought. Our guide to message formats explains how to choose the text, and the guide on turning feed images into posts for Instagram shows how much a picture matters on a visual network. Because the image comes from your own page, any improvement you make to your articles improves every post.
Fixing the problem at the source
It is tempting to correct a single bad post by hand, but the lasting fix is at the source, in the settings of your website. The following steps solve most cases on a typical WordPress site, and similar options exist in other systems.
- Make sure every article has a featured image, and make the habit part of your publishing checklist.
- In the SEO plugin, set the social image to use the featured image, with a default only as a fallback for pages without one.
- Check that the feed includes the featured image, or install a small plugin that adds it.
- Test one article with the debugger, then publish normally and watch the next automatic post.
- If a network shows an old image, refresh the stored preview with its debugger.
If the whole chain seems correct and posts still do not appear as expected, work through our checklist on why new posts do not reach social media.
Special cases worth knowing
Online shops and product images
A store publishes products, not articles, and product pages often declare a plain packshot on a white background. That works for catalogues but can look weak in a social feed. Consider a lifestyle photograph as the social image of a product, or a collage with price and benefit. Our article on posting new products automatically from PrestaShop and OpenCart explains how product feeds and the official plugins create targets without copying feed addresses.
Articles without a natural picture
Some posts, such as notices or short news items, have no photograph. Prepare a simple template with your brand colours and a large title, and attach a version of it to each such post. A consistent look is better than a random stock picture, and it helps followers recognise your updates in a crowded feed.
Several images in one article
When an article contains many pictures, tools that grab the first image in the content may choose a small icon or a banner. Declaring og:image explicitly removes the guesswork, and it is the single most useful habit for predictable previews.
Podcasts and video
Feeds for episodes and videos usually carry a cover image or a thumbnail. Check that it is a proper, wide, readable picture and not the same square logo for every episode, because the cover is the only thing that tells followers what the episode is about before they click.
A five-minute routine for every new article
A short routine in your publishing checklist prevents most image problems before they reach a network.
- Is there a featured image, and is it larger than 1200 pixels wide?
- Does the image still look good when cropped to a wide rectangle and shrunk to the size of a thumbnail?
- Does the page source declare og:image with the address of that picture?
- Is the image address reachable without logging in?
- Does the alternative text describe the picture for people who cannot see it? Good alt text also helps search engines understand the image.
Teams that tick these five boxes rarely need to correct a post afterwards. If an exception slips through, correct the source and let the next posts benefit.
If you use an official plugin
PostRSS offers official plugins for WordPress, PrestaShop and OpenCart. They build the feed and create the targets for you, so there is no copying of feed addresses. This does not change the principle of images: the plugin publishes what your site contains, so the same habits apply. A featured image on every article and a clear social image setting give the plugin and the networks the best material to work with. When you set up a new site, add the image checks to the launch checklist right away, so that the first automatic post already looks the way you want your brand to appear.
Frequently Asked Questions
Where does PostRSS get the picture for a post?
It takes the picture from the feed item or from the Open Graph tags of the page, so every post carries the real image of the article.
Why does my post show the logo instead of the article picture?
Usually the site declares one default social image for every page. Change the SEO plugin setting to use each article’s featured image, and keep the logo only as a fallback.
What size should the image be?
Use a wide image of at least 1200 by 630 pixels, with important content in the middle. Larger images with the same proportions are fine.
I changed the image but the network shows the old one. Why?
Networks store a copy of the preview. Refresh it with the debugger of the network, and the new image will appear for new posts.
Does PostRSS need access to my website’s images?
The image address must be publicly available, because the networks must load it. If a firewall, hotlink protection or a login blocks outside access, the picture will not appear.
Do I need to write code to fix this?
Usually not. Most fixes are settings in your content management system or SEO plugin. PostRSS itself needs no code: you paste a feed address, connect an account and let it work.
The Bottom Line
PostRSS uses the picture your website already declares, in the feed item or in the Open Graph tags, so the surest way to better auto-posted images is to fix the source: a featured image on every article, a social image setting that follows it, a large wide picture with safe margins and public access to the file. Check the feed, check the page source, test with a debugger, and refresh stored previews when you change an image. When the source is right, every network shows the same strong picture without any manual work. To learn more about the service, visit the PostRSS page.