Choosing the Post Text Format for Each Network From One Feed

Short answer: When one RSS feed posts to several networks, choose the post text format separately for each one. Short-form networks such as X, Bluesky and Threads work best with the item title and link, long-form networks such as LinkedIn and Facebook Pages can carry the title plus the description, messengers suit a title with a short summary, and team chats need only a clear title and link. A short static line can add context, and hashtags belong only where they help.

An RSS item offers several pieces of text: the item title, the item description, the title of the linked page, and anything you add yourself. Most auto-posters let you combine these into the post. Using the same combination everywhere is the easiest choice, but it rarely gives the best result: a full description is cut off on short-form networks, while a bare title looks thin on LinkedIn. This guide explains the building blocks, how each network treats them and which format to choose per network, so one feed produces posts that look native everywhere.

The building blocks of an auto-posted text

Every auto-posted text is assembled from a few sources:

• Item title. The title of the feed item, usually the article headline. It is short, written by the author and almost always present.
• Item description. The description in RSS or the summary arba content in Atom. It can be a one-sentence excerpt, several paragraphs or the full article, depending on the feed. The difference is covered in content:encoded vs description.
• Page title. The HTML title of the linked page, which is often the SEO title. It may differ from the headline and often ends with the site name, such as a vertical bar and the brand.
• Static text. Your own fixed text, for example New on the blog or a short call to action, added to every post on that target.
• Link and extras. The article link, optionally with UTM parameters, and hashtags generated from the item’s categories.

The structure of item elements is defined in the RSS 2.0 specification. In practice, what matters is what your own feed contains, so open it and read a few items before choosing a format.

Why one format does not fit every network

Networks differ in three ways that affect the text:

1. Length limits. X allows 280 characters for standard accounts, Bluesky 300, Threads 500, and Mastodon servers commonly 500, while LinkedIn and Facebook allow far longer posts. A long description that fits LinkedIn is truncated or rejected on a short-form network.
2. Link handling. Most networks build a preview card from the linked page, which already shows the page title and an image. Repeating the same title in the text can look redundant on some networks and helpful on others.
3. Reading habits. Followers on professional networks often read a few lines before clicking, while timelines on fast networks are scanned in seconds. Messenger channels are read like a news list.

A complete list of limits is in platform character limits and formatting. The rest of this guide turns those differences into concrete format choices.

Short-form networks: X, Bluesky, Threads, Mastodon

On short-form networks the safest and usually best format is the item title plus the link. The headline is written to attract a click, it fits the limit, and the preview card shows the image.

• Use the item title rather than the page title, because page titles often carry a site name suffix that wastes characters.
• If your descriptions are a single short sentence, title plus description can work on Threads and Mastodon, which allow longer posts than X.
• Keep hashtags to one or two. On Mastodon, hashtags are a main way posts are discovered, so a few relevant tags help there more than elsewhere.
• Avoid static prefixes on these networks unless they add real meaning, because every character counts.

Remember that links count toward the limit on most networks. On X a link counts as a fixed number of characters regardless of its length; on other networks the full address may count, so long tracking parameters reduce the space for text.

Long-form networks: LinkedIn and Facebook Pages

LinkedIn and Facebook Pages give room for more context, and posts with a short introduction usually read better than a bare headline. Good formats are:

• Title plus description, when your feed carries a concise excerpt of one to three sentences.
• Description only, when the preview card already shows the title prominently and your excerpts are well written.
• Static line plus title, such as a fixed sentence introducing a weekly column, when descriptions are long or messy.

If the description is the full article, do not post it as the text. Either switch the feed to excerpts or write a custom excerpt for each article; see custom RSS feed excerpts. Facebook-specific advice is in Facebook post formatting for automated content.

Messengers and channels: Telegram, Discord, Viber

Channel subscribers read posts one after another, often on a phone. A title with a short summary and the link is the most useful format: readers can decide from the message alone whether to open the article.

• Telegram allows long text messages, up to 4096 characters, but captions on photos are limited to 1024 characters, as stated in the Telegram Bot API documentation. Keep summaries well below that so image posts are not cut.
• Discord messages are limited to 2000 characters for most users, and a summary of a few lines reads best in a busy server.
• Hashtags are rarely useful in messengers. Leave them off unless your community searches by them.

The way channels differ from timelines is explained in messaging channels vs social feeds.

Team chats and webhooks

In Slack, Microsoft Teams, Google Chat, Mattermost and similar tools, posts are notifications, not marketing. The best format is the title and the link, perhaps with a fixed prefix that tells colleagues what kind of item it is, such as New blog post or New support article. Long summaries make channels noisy, and hashtags have no function there.

If a webhook passes the item to another system, such as an automation platform, send the richest data available and let that system decide what to show.

Visual and blog platforms

On Pinterest, the image is the post and the text is a short description. Use the title, or a description of one or two sentences, and make sure the item carries a good image. Pin titles and descriptions have their own limits, so long text is cut.

Blogs and publishing platforms such as WordPress, Ghost or DEV receive the item as a new article. There the description or full content is the body, and the title becomes the article title. Point the canonical link back to the original where the platform allows it.

Links, tracking parameters and length

The link is part of the text budget, and it deserves the same per-network thinking as the words around it. Tracking parameters are valuable because they show which network brought each visit, but they make links longer. On networks that count the full address toward the character limit, a long tracking string leaves less room for the headline. Keep parameter values short and consistent, such as the network name for the source and a short word for the campaign.

Placement matters too. Most networks build the preview card from the first link in the post, so put the article link before any other links. In messenger channels, a link at the end of a short summary reads naturally. In team chats, a link directly after the title is clearest. Whether to put the link in the post or in a first comment is a separate question, discussed in link in post vs first comment.

Finally, check how each network shortens or hides long addresses. Some show the full link, some display only the domain, and some replace it with the preview card entirely. Look at one real post on every network after you set the format.

Using static text well

Static text is the one part of the post you write once and reuse forever, so it should earn its place. Useful uses include:

• a context label on a channel that receives several kinds of content, such as Tutorial or Release notes;
• a series name when a feed contains a regular column or podcast;
• a language or region hint on accounts that serve several markets;
• a short call to action on networks where a question invites replies.

Avoid static text that sounds generic or repetitive, such as Check out our latest post on every item. Followers notice the pattern quickly. More on natural wording is in how to make auto-posted captions sound human.

A format plan for one feed

Here is an example plan for a company blog feed that goes to seven targets:

Treat such a plan as a starting point and adjust it after a few weeks based on clicks and replies. Testing two formats against each other on one network is described in how to A/B test auto-posted captions.

Fix the source text first

The best format cannot rescue poor source text. Before fine-tuning formats, improve what the feed carries:

• Write headlines that make sense without the article, because on short-form networks the headline is the whole post.
• Write a one- or two-sentence excerpt for every article, so the description is a real summary rather than the first lines of the body.
• Remove shortcodes, image captions and author boxes from the description in your feed template.
• Check special characters and emoji in the feed, so they arrive intact on every network.
• Assign a few meaningful categories to each article if you use hashtags generated from categories; see the hashtag strategy guide for automated RSS posts.

Good source text makes every format better at once, which is why it is worth more than any amount of per-network tuning.

How PostRSS builds post text

PostRSS has posted RSS and Atom feeds to social networks since 2014. For each target you choose one of nine message formats built from the item title, the item description, the page title or your own static text, so the same feed can post a headline to X, a summary to LinkedIn and a labelled notification to a team chat. Categories and tags of each item can become hashtags up to a set limit on networks where hashtags make sense, links can carry your UTM parameters, and the real image is taken from the feed item or the page’s Open Graph tags. PostRSS supports 66 networks, messengers, team chats and blogs. See the features page and the plan limits on the pricing page. More formatting guides are under the Platform Formatting tag.

Related reading

• Emoji in social media captions
• How many social accounts can you connect to one RSS feed
• RSS keyword filters: include and exclude rules

The bottom line

One feed can produce native-looking posts on every network if each target gets its own text format. Use the item title and link on short-form networks, add the description on LinkedIn and Facebook, give messenger channels a short summary and keep team chat notifications to a title and link. Use static text only where it adds context, keep hashtags where they help discovery, and invest first in good headlines and excerpts, because they improve every format at once.

FAQ

Which RSS field should become the social post text?

It depends on the network. The item title works best on short-form networks, while the title plus a short description suits LinkedIn, Facebook Pages and messenger channels.

What is the difference between the item title and the page title?

The item title is the headline in the feed. The page title is the HTML title of the linked page, often an SEO version that ends with the site name, so it can be longer and less natural in a post.

Should I post the full description to X or Bluesky?

Usually not. Descriptions often exceed the character limits of short-form networks and get cut off. The title and link are safer, and the preview card adds the image.

When is static text useful in auto-posts?

When it adds context, such as a series name, a content label on a mixed channel or a language hint. Generic phrases repeated on every post tend to look automated.

Can one feed use different formats on different networks?

Yes, if your tool sets the format per target. Connect the feed to each network as a separate target and choose the text format that suits each one.