RSSFeeds.com

RSS Namespaces and Extensions

RSS 2.0 is deliberately small. Everything else – full content, author names, thumbnails, video, comments, locations – comes from extensions in their own XML namespaces. This is the reference for the ones that matter.

Updated

Illustration of modular extensions plugging into an RSS feed

How Namespaces Work

A namespace is declared once on the root element with a prefix and a URI. After that, elements with that prefix belong to the extension. The URI is an identifier, not a page that has to load, but it must be spelled exactly – including case and trailing slashes – or parsers won't recognise the elements.

<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  …
  <content:encoded><![CDATA[<p>Full article</p>]]></content:encoded>

The prefix is your choice, but stick to the conventional ones below: some readers are sloppy and look at prefixes instead of URIs.

Namespace Reference

PrefixNamespace URIUsed for
atomhttp://www.w3.org/2005/AtomSelf link and WebSub hub in RSS
contenthttp://purl.org/rss/1.0/modules/content/Full HTML content
dchttp://purl.org/dc/elements/1.1/Author names, dates, subjects
mediahttp://search.yahoo.com/mrss/Images, video, thumbnails
ituneshttp://www.itunes.com/dtds/podcast-1.0.dtdPodcasts
podcasthttps://podcastindex.org/namespace/1.0Podcasting 2.0
syhttp://purl.org/rss/1.0/modules/syndication/Update schedule
slashhttp://purl.org/rss/1.0/modules/slash/Comment counts
wfwhttp://wellformedweb.org/CommentAPI/Comment feeds
georsshttp://www.georss.org/georssLocations
thrhttp://purl.org/syndication/thread/1.0Threads and replies (RFC 4685)
dctermshttp://purl.org/dc/terms/Extended Dublin Core

content:encoded

The single most useful extension. RSS has only description, which many publishers use for a summary. content:encoded carries the full HTML of the item, so readers can show the whole article.

<description>Contour lines look like fingerprints until you know three rules.</description>
<content:encoded><![CDATA[
  <p>Contour lines look like fingerprints until you know three rules.</p>
  <figure><img src="https://example.com/img/topo.jpg" alt="Map"><figcaption>A 1:25,000 map</figcaption></figure>
  <h2>Rule one: lines never cross</h2>
  <p>…</p>
]]></content:encoded>

Use absolute URLs inside it, avoid scripts and iframes (readers strip them), and include image alt text.

Dublin Core (dc)

Dublin Core is a general metadata vocabulary. In RSS, its main job is dc:creator: RSS's own author must be an email address, while dc:creator can be just a name. WordPress uses it for every post.

<dc:creator>Mara Lindqvist</dc:creator>
<dc:date>2026-11-10T08:30:00Z</dc:date>
<dc:subject>Maps</dc:subject>
<dc:rights>CC BY 4.0</dc:rights>

Other elements: title, description, publisher, contributor, type, format, identifier, source, language, relation and coverage. dc:date uses ISO 8601, not RFC 822.

atom:link

Borrowed from Atom, mainly for two links: the feed's own URL and a WebSub hub.

<atom:link href="https://example.com/feed.xml" rel="self" type="application/rss+xml" />
<atom:link href="https://pubsubhubbub.appspot.com/" rel="hub" />

Some feeds also use rel="next" and rel="previous" for paged archives.

Media RSS (media)

Created by Yahoo in 2004 for video and image search, Media RSS is now the standard way to attach images and video to items. YouTube's Atom feeds use it for thumbnails, descriptions and view counts.

<media:content url="https://example.com/video/intro.mp4" type="video/mp4" medium="video"
  fileSize="24117248" duration="185" width="1920" height="1080" isDefault="true">
  <media:title>Introduction</media:title>
  <media:description>A three-minute tour.</media:description>
  <media:thumbnail url="https://example.com/video/intro.jpg" width="640" height="360" />
  <media:credit role="author">Jane Doe</media:credit>
  <media:license type="text/html" href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</media:license>
</media:content>

<media:thumbnail url="https://example.com/img/post-640.jpg" width="640" height="360" />
ElementPurpose
media:contentA media object. Attributes: url, type, medium (image, audio, video, document, executable), fileSize, duration, width, height, bitrate, lang, isDefault, expression.
media:groupSeveral versions of the same object, e.g. different resolutions.
media:thumbnailA preview image: url plus optional width, height and time.
media:title, media:descriptionTitle and description of the media object.
media:keywords, media:categoryKeywords and categories.
media:player, media:embedA URL or embed code for a player.
media:credit, media:copyright, media:licenseCredits and rights.
media:rating, media:restrictionAge rating, and country or sharing restrictions.
media:text, media:subTitleTranscripts and subtitle files.
media:hashChecksum of the file (md5 or sha-1).
media:communityRatings and statistics, such as YouTube's view counts.

Tip: want thumbnails in Feedly, Inoreader and other readers? Add a media:thumbnail or media:content medium="image" to every item. It's the most reliable signal, more so than the first image in the content.

Syndication (sy)

Tells readers how often the feed updates. WordPress adds it by default.

<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2026-01-01T00:00:00Z</sy:updateBase>

updatePeriod is hourly, daily, weekly, monthly or yearly; updateFrequency is how many times per period. Most readers ignore it in favour of their own scheduling and HTTP caching headers.

Comments: slash, wfw and thr

<slash:comments>12</slash:comments>
<wfw:commentRss>https://example.com/posts/hello/feed/</wfw:commentRss>
<comments>https://example.com/posts/hello#comments</comments>

slash:comments gives the number of comments, wfw:commentRss the URL of a feed with the comments of this item. The Atom Threading extension (thr) does the same for Atom with <link rel="replies"> and thr:in-reply-to.

GeoRSS

<georss:point>52.3676 4.9041</georss:point>

Latitude and longitude, separated by a space. GeoRSS-Simple also has georss:line, georss:polygon and georss:box. Used by map tools, earthquake and weather feeds.

Obsolete Extensions

  • googleplay (http://www.google.com/schemas/play-podcasts/1.0): used by Google Podcasts, which closed in 2024. The tags do no harm but have no effect.
  • feedburner: tracking metadata added by FeedBurner. Safe to remove.
  • creativeCommons: an early license module. Use dc:rights or media:license today.

Creating Your Own Extension

You can add your own data to any feed: pick a URI you control, declare a prefix and use it. Readers that don't know it will ignore it.

<rss version="2.0" xmlns:shop="https://example.com/ns/shop/1.0">
  …
  <item>
    <title>Blue ceramic mug</title>
    <shop:price currency="EUR">14.95</shop:price>
    <shop:stock>23</shop:stock>
  </item>

Never put custom elements in the RSS namespace itself (without a prefix) – that makes the feed invalid. The Feed Validator flags undeclared prefixes and misspelled namespace URIs.

Sources and Further Reading