
Short answer: PostRSS builds the text of every post from one of nine message formats. The text can come from the item title, the item description, the title of the linked page, your own fixed text, or a combination: for example your fixed text followed by the item title. Pick the format per source, so a news feed can post bare headlines while a product feed adds a short label in front. The link and the picture are added automatically, so the format only decides the words around them.
Most people set up a source, accept the default and never look at the format again. That is a pity, because the wording of a post is the part of automation that readers actually see. The same feed can produce a crisp headline on one network and a confusing wall of text on another, depending on one setting. This guide explains the nine formats that PostRSS offers, what each one puts into a post, where each one works well and how to test a change without risking your audience. It uses only the options that PostRSS describes on its public pages and in its API documentation.
A feed item has several parts: a title, a description, a link, a date, categories and usually a picture. A message format answers one question: which of those texts becomes the message of the post. The link is always attached so that readers can click through, and the picture is taken from the feed item or from the page, so neither depends on the format. The format also does not decide the schedule, the order, the filters or the hashtags. Those are separate settings of the same source.
The setting belongs to the source, not to the account. If you send one feed to three targets through three sources, each source can use its own format. That makes it possible to give a Telegram channel a longer text and an X account a short headline without touching the website.
The formats fall into three families: texts taken from the item, texts taken from the page and texts that start with your own words. The table lists all nine.
| Format | The post text contains | Works well for |
|---|---|---|
| Item title | The title of the feed item | News, blogs, release notes |
| Item description | The description or summary of the item | Product feeds with good short copy |
| Item title and description | Title followed by the description | Channels that allow longer text |
| Page title | The title of the page the item links to | Feeds whose item titles are cryptic |
| Page title and description | The page title plus its description | Pages with strong metadata |
| Static text | Only your own fixed text | Campaign slogans, fixed calls to action |
| Static text and item title | Your text, then the item title | Labelled series such as New in stock |
| Static text, item title and item description | Your text, title and description | Announcements that need a label and detail |
| Static text and page title | Your text, then the page title | Labelled posts when item titles are weak |
The item title is the safest choice. A title is written to stand alone, it is short and it fits every network. For a blog or a news site the title is the headline, and a headline with a link and a picture is exactly the post that readers expect to see. If your titles are good, you can leave this format on for years.
The weak point is that a title tells nothing about context. A title such as Spring update can mean anything. If you publish many items with similar titles, consider one of the formats that adds a label or a description.
Some feeds carry a carefully written summary in the description, for example a two-sentence product blurb or the first lines of an event. If the title is only a name, the description can make a better post. Check what your description contains before you choose it. Many platforms fill the description with the start of the article, with markup or with a long text that is cut mid-sentence. Open the feed address in a browser and read three descriptions. If they read like finished sentences, the format will work. If they look like a raw dump, use the title.
Combining the title and the description gives a longer post: a headline followed by a few lines of detail. This is useful on channels where longer text is welcome, such as team chats, a Telegram channel or a blog platform, and less useful where the text limit is short. When the text is too long for a network, PostRSS never cuts the link, and hashtags that do not fit the limit are dropped first. Still, a long description can push the useful part out of view, so look at the first post on each network before you trust the format.
The page formats take the words from the page that the item links to, not from the feed. Why would that matter? Some feeds are generated by software that fills the title with an internal name, a code or a shortened string, while the page itself has a proper title. In that case the page title is the better text. It is also useful when you do not control the feed and cannot change what its titles look like. The page title and description format adds the description of the page, which is often the same text that search engines show.
The trade-off is that the text now depends on the page, so if the page title is long or has the name of the site added at the end, the post will be too. Check one example before you decide.
The static text format ignores the item words and posts the same text each time, with the link and the picture of the item. It sounds odd, but it suits campaigns. A fixed line such as Fresh from the workshop, tap to see it, can accompany any item from a feed of new products, and the picture and the link do the rest. It also suits feeds that have no useful titles at all, for example a spreadsheet source where every row is a photo.
Use it with care on networks where repeated identical text can look like spam. If you post often, vary the text by choosing a combined format instead.
Three formats start with your own text and then add words from the item. They are the most flexible ones because the fixed part gives the series a name that readers learn to recognise.
A short label at the start is a quiet form of branding. A shop can start every post with its name, a club can start with the name of the season, a newsroom can mark the series. Keep the label short, because it uses part of the text limit of every network, and do not repeat information that is already in the title.
The right format depends less on the website than on the place where the post appears. A headline works on X and Bluesky. A longer text works on Telegram, Discord and team chats. A label and a title works on a Facebook Page where a post sits in a feed among photos. Because the format belongs to the source, you can make one source per network group and set the format for each. That does cost an extra source for each combination, but on plans with enough targets the work is small and the difference in quality is visible.
When you are unsure, start with the item title for every network and change the format only for the network where a post looked wrong. The article about Open Graph tags and wrong preview images explains why the picture and the card can look different from the text on some networks.
A format change affects only new posts, but those can reach the public immediately. A cautious way to test is to use a source with a single target that you control, such as a private channel or a test blog, and send a few items. Look at the first post, then at the second. If both look right, change the format of the production source.
The format only decides the words, so it works well with the other source settings. Keyword filters decide which items are posted at all. They search the title, the description and the categories, and an exclude word always wins over an include word. Hashtags can be added after the text or before it, and your own fixed hashtags come first. Because hashtags use part of the limit, a long combined format may leave no room for them. If hashtags matter on a network, prefer a shorter format there. The guides to include and exclude filters and to hashtags describe the details.
A small online shop publishes new products to a feed. Each item has a product name as the title, two sentences as the description and a good picture. The owner connects a Facebook Page, a Telegram channel and an X account. For the Page she chooses the static text and item title format with the label New in the shop, because the picture carries the post and the label is friendly. For Telegram she chooses the title and description, since subscribers like detail. For X she chooses the item title only, because the limit is short and the link and the picture complete the post. One feed, three sources, three formats, and no change to the website.
The message format is a small setting with a large effect on how your automated posts look. Use the item title when your headlines are good, the description or the page title when they are not, and add static text when you want a label that readers recognise. Decide per source and per network, test on a private target and read the first posts after every change. The options are on the features page, and the limits of each plan are on the pricing page.
Nine. They combine the item title, the item description, the page title and your own static text, from a single item title to a label followed by a title and a description.
Yes. The format is a setting of the source. If you create one source for each target or group of targets, each can have its own format.
No. The link is always attached, and the picture comes from the feed item or from the page. The format only decides the words of the post.
The link is never cut, and hashtags that do not fit the limit are dropped. Read the first post on each network to see how your format looks there.
No. A new format applies to posts created after the change. Posts that were already published stay as they are.
What changed in the networks, what broke, and how to fix it before it costs you reach.
Do Internet Solutions, đội ngũ đứng sau PostRSS, phát triển. Mỗi sản phẩm giúp bạn tiết kiệm thời gian theo một cách riêng.