RSS Channel Elements: Title, Image, Language and What They Do

Short answer: RSS channel elements describe the feed as a whole rather than any single article. RSS 2.0 requires three of them, title, link a description, and offers optional ones such as language, image, lastBuildDate a ttl. Readers and tools use them to name, identify and display your feed, but social posts are built from item elements, so the channel image does not become the picture on your auto-posted posts.

Most guides about feeds focus on items: titles, links, GUIDs and dates of individual articles. The channel block at the top of the feed gets less attention, and it is often left with whatever default the CMS produced, such as a feed titled with the site’s tagline or a language code that does not match the content. This guide walks through the channel elements of RSS 2.0, their Atom equivalents, what each one is used for and which of them matter when the feed powers social media automation.

Channel versus item: where the elements live

An RSS 2.0 document has one rss root element, one channel inside it and any number of item elements inside the channel. Everything inside the channel but outside the items describes the feed itself:

<rss version="2.0">
  <channel>
    <title>Example Garden Blog</title>
    <link>https://example.com/blog/</link>
    <description>Practical gardening advice every week</description>
    <language>en-gb</language>
    <lastBuildDate>Sat, 10 Oct 2026 08:00:00 +0000</lastBuildDate>
    <item>...</item>
  </channel>
</rss>

The full list of channel elements, with their exact rules, is in the RSS 2.0 specification. Item elements are explained separately in RSS feed XML anatomy.

The three required elements: title, link and description

title is the name of the feed. Feed readers show it in the subscription list, and many automation tools show it as the name of the source when you add a feed. Use the name people know, such as the site or blog name, and avoid generic defaults like My Blog or a long marketing tagline.

link is the address of the website the feed belongs to, usually the home page or blog index, not the address of the feed itself. Tools use it to open the site from the reader and sometimes to identify the feed’s owner.

description is a short sentence about the feed. Readers display it under the title in directories and subscription dialogs. One plain sentence that says what the feed contains and how often it is updated is enough.

If you run several feeds, for example one per category, give each a distinct title and description. When several feeds share the same title, it becomes hard to tell them apart in any tool, which leads to mistakes such as connecting the wrong feed to the wrong account.

The language element

language states the language the feed is written in, using codes such as en, en-us, de nebo lt. Readers may use it to group or filter feeds, and directories and podcast platforms use it to list content for the right audience.

Two practical points matter:

• Match the content. A CMS installed in English and later switched to another content language often still outputs en-US. Check the code after any language change.
• One language per feed. If your site publishes in several languages, offer one feed per language, each with its own language code, rather than one mixed feed. That also makes it simple to send each language to the right social accounts, as described in multilingual RSS automation.

The channel language does not translate anything and does not change how social networks display your posts. It is metadata for tools that care about it, which is why it is easy to forget and worth getting right.

The image element and feed logos

The optional image element gives the feed a logo. It has three required sub-elements, url, title a link, and optional width a height. The specification sets a maximum width of 144 pixels and a maximum height of 400 pixels, with defaults of 88 by 31, a reminder of how old the format is.

<image>
  <url>https://example.com/logo-144.png</url>
  <title>Example Garden Blog</title>
  <link>https://example.com/blog/</link>
</image>

Feed readers may show this image next to the feed name; many modern readers use the site’s favicon instead. What the channel image does not do is supply the picture for each social post. Auto-posters take images from each item, through an enclosure, a media:content element or an image in the description, or from the Open Graph tags of the linked article. If your posts show your logo instead of the article image, the problem is in the items or in the article page, not in the channel. See how to control which image gets auto-posted.

Podcast feeds are the exception where a channel image matters a lot. Podcast directories use the channel artwork from the itunes:image element as the show cover, and Apple Podcasts expects square artwork between 1400 and 3000 pixels wide. That is a podcast requirement, separate from the RSS 2.0 image element.

Date elements: pubDate and lastBuildDate

At channel level, pubDate is the publication date of the feed content and lastBuildDate is the last time the feed was changed. Both use the RFC 822 date format, such as Sat, 10 Oct 2026 08:00:00 +0000.

Some readers and tools look at lastBuildDate to decide whether anything has changed. If your CMS updates it every time the feed is generated, even when nothing new was published, it carries no information. If it never updates, a tool that trusts it may assume the feed is stale. Most auto-posters compare item identifiers instead, but a correct lastBuildDate is still good practice. The difference between the two dates is covered in pubDate vs lastBuildDate.

Hints for readers: ttl, skipHours and skipDays

ttl (time to live) suggests how many minutes a feed may be cached before it is fetched again. skipHours a skipDays list hours and days when readers need not check the feed. These are hints, and many modern tools ignore them or treat them loosely. They do not reliably control when your items are posted to social networks. If you need posting only in business hours, set that in your automation tool’s posting windows. The details are in RSS ttl, skipHours and skipDays explained.

Other optional channel elements

RSS 2.0 lists several more channel elements. Most are harmless and rarely used:

• copyright: a short rights notice for the feed content.
• managingEditor a webMaster: email addresses of the people responsible. They are public, so use role addresses rather than personal ones.
• category: one or more categories for the whole feed, used by some directories.
• generator: the software that produced the feed. Some site owners remove it because it reveals the CMS version.
• docs: a link to the format documentation.
• cloud, rating a textInput: old features that almost nothing uses today.

Many feeds also include an atom:link element with rel="self", which states the feed’s own address. Validators warn when it is missing; the fix is explained in the missing atom:link rel self warning.

Atom equivalents

Atom feeds, defined in RFC 4287, describe the feed in the feed element with slightly different names:

Atom is stricter in a useful way: id a updated are required, which gives tools a reliable way to recognise the feed. Whether the format matters for auto-posting is discussed in Atom vs RSS for auto-posting.

Common channel mistakes and how to fix them

When you open a typical feed, the same few problems appear again and again. Each one takes only a few minutes to fix in the CMS settings or the feed template:

• The title or description is a default. WordPress builds the feed title from the site title and the feed description from the tagline. A feed described as Just another WordPress site, the old default tagline, tells nobody what it is. Set a proper site title and tagline, or change them in your SEO or feed plugin.
• The description is empty. An empty description is valid in practice, but directories and readers then show nothing under the name. Write one sentence.
• The link points to a staging or old domain. After a move, hard-coded addresses in templates can survive. Check that the channel link uses the live https domain.
• The language code is wrong. A site written in German with en-US in the feed is common after a CMS was installed in English. Correct the site language setting.
• The logo is huge. Some themes put the full-size header image into the channel image. Use a small logo within the specification’s limits instead.
• Personal email addresses are exposed. managingEditor a webMaster are public. Replace personal addresses with a role address or remove the elements.

After any fix, validate the feed again and open it in a feed reader to see how the name, description and logo appear. Some readers cache channel information, so changes may take a while to show there. Automation tools that you connected before the change may also keep the old source name until you edit it, which is harmless but worth knowing when you compare dashboards. If you change the feed address itself, not just its channel elements, treat it as a migration and update every tool that uses it.

Which channel elements matter for auto-posting

For social media automation, the item elements do the real work. Channel elements still help in a few ways:

1. A clear title makes the source easy to recognise in your automation dashboard, especially when you manage several feeds.
2. A correct link to the site helps you and your colleagues confirm which website a feed belongs to.
3. The right language keeps multilingual setups tidy and avoids confusion when feeds are shared with partners.
4. Valid dates keep the feed free of validator errors, which some tools treat as warnings.

Spend five minutes on the channel block whenever you set up a new feed, then focus your effort on item titles, descriptions, links and images, which are what your followers actually see.

How PostRSS uses your feed

PostRSS has published RSS and Atom feeds to social networks since 2014. It builds each post from item data, using the item title, the item description, the page title or your own static text, and takes the picture from the feed item or from the page’s Open Graph tags, so the real article image is posted rather than a feed logo. Any valid RSS 2.0 or Atom feed can be a source, and one feed can go to several of the 66 supported networks, messengers, team chats and blogs, each with its own settings. See the features page and the plan limits on the pricing page. More technical articles are under the RSS Feed tag.

Related reading

• RSS feed validation before auto-posting
• RSS namespaces explained
• Automatické zjišťování RSS feedu

The bottom line

The channel block names and describes your feed. Give it a real title, a link to the site and a one-sentence description, set the language code that matches the content, and keep dates valid. Add a small logo in the image element if you like, but remember that social posts take their pictures from items and article pages, not from the channel. With the channel tidy, put your effort into the items that become posts.

FAQ

Which channel elements are required in RSS 2.0?

Three: title, link and description. Everything else in the channel, including language, image and lastBuildDate, is optional.

Does the RSS channel image appear on my social posts?

No. Auto-posters take images from each item or from the Open Graph tags of the linked article. The channel image is a small feed logo that some readers display next to the feed name.

What size should an RSS channel image be?

The RSS 2.0 specification allows a width of up to 144 pixels and a height of up to 400 pixels, with a default of 88 by 31. Podcast artwork is a separate element with much larger requirements.

Which language code should my feed use?

Use the code of the language the content is written in, such as en, en-gb, de or lt. If your site publishes in several languages, offer a separate feed for each language.

Do ttl and skipHours control when my posts are published?

Not reliably. They are hints for feed readers, and many tools ignore them. Use the posting windows of your automation tool to control when posts go out.