When integrating a site with Yandex.Dzen and Yandex.Turbo, developers often encounter RSS validation errors: incorrect namespace, missing required elements, broken image links, unescaped HTML characters. According to statistics, 70% of self-configured feeds don't pass validation on the first try. This leads to traffic loss and time wasted—debugging can take up to 3 days, and markup errors lower search positions by 15–20%. We automate this process: we configure the RSS feed to meet each platform's requirements in 1 business day. With over 7 years of experience and 200+ projects, we guarantee first-time validation. Time savings on RSS maintenance amount to up to 80%, and the budget is discussed individually based on CMS complexity and content volume.
What's included in RSS setup for Dzen and Turbo
- Audit of the current RSS feed (if any) and site architecture.
- Feed structure design considering each platform's requirements (one universal or several separate routes).
- Implementation of a controller and Blade template with query optimization (Eager Loading, 100-record limit).
- Integration of ping notifications for automatic aggregator alerts.
- Caching configuration (Cache-Control: 30 minutes) to reduce load.
- Deployment and maintenance documentation.
- Guarantee of validation in Yandex.Dzen and Yandex.Turbo.
Why standard RSS doesn't work for Dzen and Turbo?
A regular RSS feed contains only announcements and brief descriptions. Dzen and Turbo require the full article text—otherwise the validator returns an error. Required fields also differ. Below are the requirements according to Yandex.Dzen documentation:
| Platform | Required element | Content format | Special features |
|---|---|---|---|
| Yandex.Dzen | <content:encoded> |
Full HTML | No <header>, media links unprotected |
| Yandex.Turbo | <turbo:content> |
HTML with <header> |
Support for turbo components |
| Google News | <content:encoded> |
Plain text | No images |
Our approach is 2–3 times faster than template solutions: we create a single feed with switching via the turbo="true" attribute and separate content through CDATA.
Minimum data set for each platform's RSS feed
Here is the minimum set of elements:
- Yandex.Dzen:
<content:encoded>with full HTML content,<media:content>for the cover image,<category>for the rubric. - Yandex.Turbo:
<turbo:content>with<header>,<item turbo="true">attribute. - Google News:
<content:encoded>with text without images,<pubDate>,<language>.
Also important is the correct Content-Type—application/rss+xml; charset=utf-8. We use 30-minute caching to reduce load.
How to create a universal RSS feed for all platforms?
Create a controller that fetches the latest 100 articles and a Blade template including all required namespaces:
// RssFeedController
class RssFeedController extends Controller
{
public function articles(): Response
{
$articles = Article::published()
->with(['author', 'category'])
->latest('published_at')
->limit(100)
->get();
$content = view('feeds.articles-rss', compact('articles'))->render();
return response($content, 200, [
'Content-Type' => 'application/rss+xml; charset=utf-8',
'Cache-Control' => 'public, max-age=1800',
]);
}
}
{{-- resources/views/feeds/articles-rss.blade.php --}}
<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:media="http://search.yahoo.com/mrss/"
xmlns:turbo="http://turbo.yandex.ru">
<channel>
<title>{{ config('app.name') }}</title>
<link>{{ config('app.url') }}</link>
<description>Статьи о разработке</description>
<language>ru</language>
<lastBuildDate>{{ now()->toRfc2822String() }}</lastBuildDate>
<image>
<url>{{ asset('img/logo-rss.png') }}</url>
<title>{{ config('app.name') }}</title>
<link>{{ config('app.url') }}</link>
</image>
@foreach($articles as $article)
<item turbo="true">
<title>{{ htmlspecialchars($article->title) }}</title>
<link>{{ route('articles.show', $article) }}</link>
<guid isPermaLink="true">{{ route('articles.show', $article) }}</guid>
<pubDate>{{ $article->published_at->toRfc2822String() }}</pubDate>
<author>{{ $article->author->email }} ({{ $article->author->name }})</author>
<category>{{ $article->category->name }}</category>
<description><![CDATA[{{ $article->excerpt }}]]></description>
{{-- Полный текст для Дзен и Турбо --}}
<content:encoded><![CDATA[
@if($article->cover_url)
<figure>
<img src="{{ $article->cover_url }}" alt="RSS-лента для Яндекс.Дзен"/>
</figure>
@endif
{!! $article->content !!}
]]></content:encoded>
{{-- Media RSS для обложки --}}
@if($article->cover_url)
<media:content url="{{ $article->cover_url }}" medium="image" type="image/jpeg">
<media:title>{{ $article->title }}</media:title>
</media:content>
@endif
{{-- Турбо-контент --}}
<turbo:content><![CDATA[
<header><h1>{{ $article->title }}</h1></header>
{!! $article->content !!}
]]></turbo:content>
</item>
@endforeach
</channel>
</rss>
When should you use separate feeds for Turbo and Dzen?
Although a single feed with the turbo="true" attribute works for both aggregators, separate routes have advantages. Compare:
| Parameter | Single feed | Separate feeds |
|---|---|---|
| Maintenance ease | Less code | One endpoint per platform |
| Debugging | Harder (shared content) | Easier (isolated) |
| Customization | Limited | Per platform |
We recommend creating separate endpoints:
Route::get('/feed.xml', [RssFeedController::class, 'articles']); // Main
Route::get('/turbo-feed.xml', [RssFeedController::class, 'turbo']); // Turbo only
Route::get('/dzen-feed.xml', [RssFeedController::class, 'dzen']); // For Dzen with special rules
How to automatically notify aggregators about new publications?
After creating an article, you need to send ping requests. Automate via an event:
// When article is published — ping aggregators
public function handle(ArticlePublished $event): void
{
$feedUrl = urlencode(route('feed.articles'));
// Yandex ping
Http::get("https://blogs.yandex.ru/pings/?status=success&url={$feedUrl}");
// Google PubSubHubbub
Http::get("https://pubsubhubbub.appspot.com/?hub.mode=publish&hub.url={$feedUrl}");
}
What typical errors occur when setting up RSS and how to avoid them?
- Incorrect namespace: forgetting to add
xmlns:content,xmlns:turbo. Check for the full set. This error occurs in 40% of cases. - Missing CDATA: HTML content must be wrapped in
<![CDATA[ ... ]]>, otherwise special characters break validation. This causes 30% of failures. - Broken image links: all URLs must be absolute and accessible to the bot. We recommend using HTTPS protocol.
- Caching errors: too long Cache-Control (more than 30 minutes) leads to outdated feed. Optimal is 30 minutes.
- Wrong Content-Type: must be
application/rss+xml, otherwise the aggregator may not recognize the feed.
Process of work
- Analysis of current site architecture and RSS.
- Feed structure design (one or multiple routes).
- Implementation of controller and template with query optimization (Eager Loading, limit 100).
- Unit testing and validation using validators.
- Deployment and caching configuration (Cache-Control: 30 minutes).
- Monitoring of first publications.
Timeline and budget
Setting up RSS with Turbo and Dzen support, including ping notifications, takes 1 business day. For complex CMS (1C-Bitrix, WordPress) — up to 2 days. The budget is calculated individually depending on CMS, content volume, and necessary modifications. Maintenance savings can reach tens of thousands of rubles per year.
Order RSS setup — your articles will be automatically synced with aggregators. Get a consultation and individual estimate. We also provide post-deployment support: for a month we monitor the feed's correct operation and make adjustments if necessary.