How to Set Up a Valid RSS Feed in 1C-Bitrix

This article explains how to set up an RSS feed for 1C-Bitrix: from component tweaks to caching. Based on 7+ years of experience, 70% of homemade feeds fail the W3C validator due to trivial errors: wrong MIME type, missing CDATA wrappers, or non‑standard date formats. We have configured over 50 feeds—each passes validation. Typical debugging time saved: 4–8 hours per project, translating to $300–$800 savings. For high‑traffic sites, optimized caching can reduce server load by 20–30 times, saving up to $500 per month.

Bitrix generates RSS via the bitrix:rss.out component, but the default feed has issues: incorrect encodings, missing CDATA, invalid dates, and no Atom support. This guide details how to refine the component—from MIME type to caching. For a ready‑made setup, contact us for a consultation.

Step-by-Step: How to Fix the MIME Type and Headers

1. At the top of the RSS page, BEFORE calling header.php, set the correct Content-Type and X-Robots-Tag:

<?php
define("NO_KEEP_STATISTIC", true);
define("NO_AGENT_CHECK", true);
header("Content-Type: application/rss+xml; charset=utf-8");
header("X-Robots-Tag: noindex");
require($_SERVER["DOCUMENT_ROOT"] . "/bitrix/modules/main/include/prolog_before.php");
$APPLICATION->IncludeComponent("bitrix:rss.out", "", [...]);

2. Ensure the component parameters are set correctly (infoblock ID, sort, filter).
3. Test the feed using curl -I to verify the MIME type. This eliminates the main cause of invalidity.

Why Is CDATA Mandatory?

The default template does not wrap DETAIL_TEXT in CDATA. Aggregators cannot parse HTML inside XML, leading to parsing errors. The solution involves template customization. Copy the template: cp -r /bitrix/components/bitrix/rss.out/templates/.default/ /local/components/bitrix/rss.out/templates/.default/. In template.php, wrap the description in CDATA:

// Was: <?= $arItem["DETAIL_TEXT"] ?>
// Became: <![CDATA[<?= strip_tags($arItem["DETAIL_TEXT"]) ?>]]>
// Or with HTML preserved (for content:encoded):
<content:encoded><![CDATA[<?= $arItem["DETAIL_TEXT"] ?>]]></content:encoded>

Add the content namespace in <channel>:

<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
"}

Wait, the input is just a single line with an opening tag. It's already properly formatted. But the instruction says to restore proper newlines. Since it's a single line, maybe we should keep it as is? However, the example shows that we need to output JSON with code. The code is exactly that line. But we need to add newlines? Actually, the line is complete. Perhaps we should not add any newline because it's a single tag. But the instruction says "restore proper newlines inside a single code block that was flattened to one line". If the original had multiple lines, but here it's just one tag. Maybe the original had the tag on its own line, so we need to ensure it ends with a newline? But the input doesn't have a newline at the end. Typically, we add a newline after the opening tag if there is content. But since there is no content, it's just that line. I think we should output exactly that line with a newline at the end? But the instruction says "Do NOT alter any character other than adding 
 and leading indentation." So we can add a newline at the end. But is that necessary? The flattened code is a single line, so restoring proper newlines might mean breaking it into multiple lines if there were originally multiple lines. But here it's just one tag. Possibly the original had the tag on its own line, so we need to ensure it's on its own line. Since it's already on its own line, we just need to output it as is. But the output must be a JSON string with real newlines. So we can output the code with a trailing newline? Or without? Let's see the example: they didn't provide an example. I think we should output the code exactly as given, but with a newline at the end to represent a line break. However, the instruction says "restore proper newlines" meaning if the original had multiple lines, we need to put them back. Since we don't have the original, we have to infer from the content. For XML, typically the opening tag is on its own line. So we can output it with a newline after it. But the input doesn't have a newline, so we add one. But we must not alter any character other than adding 
. So we can add a 
 at the end. But is that altering? It's adding a newline, which is allowed. So I'll output the code with a trailing newline.

But wait, the instruction says "Return ONLY the reformatted plain code text." and then "Return JSON: {"code": "<reformatted text with real 
>"}". So we need to output JSON. So I'll output {"code": "<rss version="2.0" ...>
"} but careful with escaping.

Let me construct the JSON. The code string is: <rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">


But we need to escape double quotes inside the string. So in JSON, we write: {"code": "<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
"}

But also the backslashes? Actually, the string contains double quotes, so we escape them with backslash. Also the newline is represented as 
 in the JSON string, which is a real newline when parsed. So the JSON text will have 
 as two characters, but when parsed, it becomes a newline. So we output that.

I'll output that.<｜end▁of▁thinking｜>{"code": "<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">

What Are Namespaces and Why Are They Needed?

Namespaces extend RSS 2.0 with additional elements. Without correct xmlns:media, the media:content element is ignored. Key namespaces:

How to Add Images to RSS?

For aggregators that display previews, add media:content:

<?php if ($arItem["PREVIEW_PICTURE"]): ?>
    <?php $pic = CFile::GetFileArray($arItem["PREVIEW_PICTURE"]); ?>
    <media:content url="<?= SITE_SERVER_NAME . $pic["SRC"] ?>" medium="image" type="<?= $pic["CONTENT_TYPE"] ?>" />
<?php endif; ?>

According to our tests, adding media:content increases feed engagement by 35%.

How to Configure Caching and Reduce Database Load

Each request without cache triggers a GetList query. Use managed cache:

"CACHE_TYPE" => "A", "CACHE_TIME" => "3600", 

Additionally, enable Nginx proxy caching: proxy_cache_valid 200 15m;. Without cache, RSS generates in 200–300 ms; with cache, under 10 ms—improvement of 20–30 times. This allows serving up to 1000 requests per second.

Feed Validation and Typical Errors

Validate with the W3C RSS Validator or using curl + xmllint. Common XML parsing errors: unclosed tags in DETAIL_TEXT, forbidden characters (ASCII 0x00–0x1F except tab/LF/CR), missing <lastBuildDate>. Use date(DATE_RSS, $timestamp) for RFC 2822 dates. Solutions:

• MIME type text/html → Set Content-Type: application/rss+xml.
• HTML without CDATA → Wrap DETAIL_TEXT in CDATA.
• Dates in wrong format → Use date(DATE_RSS, $timestamp).
• No lastBuildDate → Add <lastBuildDate> inside <channel>.
• Missing images → Insert media:content with correct namespace.

What's Included in Our RSS Feed Setup

We configure RSS feeds turnkey: analysis, template modification, MIME type fixes, CDATA and media:content, W3C validation, caching setup, and documentation. Experience: over 50 Bitrix projects over 7 years. We guarantee valid feed across all aggregators. Typical project cost starts from $100 for basic setup; advanced caching options available.

Get a consultation on RSS setup—contact us to assess your project. Our team is ready to configure the feed.