We need to translate content to Russian, preserving HTML tags, JSON keys, etc. The content already includes some Russian in meta description and JSON description. We need to translate English parts to Russian, but keep Russian parts unchanged.
Also preserve tags. We must translate all English text nodes. Let's go through.
Title h1: "Download Escape to the Italian brainrot – horror game, multiplayer horror, escape game, survival horror, Italian horror" => translate to Russian: "Скачать Escape to the Italian brainrot – игра в жанре хоррор, многопользовательский хоррор, игра-выживание, выживание в жанре хоррор, итальянский хоррор". But keep the game name unchanged. Probably: "Скачать Escape to the Italian brainrot – хоррор-игра, многопользовательский хоррор, игра-выживание, выживание в жанре хоррор, итальянский хоррор".
We'll produce natural translation. Next h2 Overview: "Overview" => "Обзор". Paragraph: translate.
We need to translate all English sentences. Also list items. Also meta title: "Download Escape to the Italian brainrot – horror game, multiplayer horror, escape game, survival horror, Italian horror" => translate.
Meta description already Russian, keep. JSON description already Russian, keep. But JSON keys remain same, values that are English need translation.
In JSON, "name": "Escape to the Italian brainrot" stays same (proper noun). "description": already Russian, keep. "genre": "Horror" => translate to Russian "Хоррор" or "Ужасы".
Probably "Ужасы". "gamePlatform": "PC (Windows)" => maybe keep as is? It's technical, but could translate "ПК (Windows)".
But rule: preserve URLs, technical identifiers unchanged. "PC (Windows)" is a technical identifier, but translation may be okay. Safer to keep unchanged?
The rule says preserve URLs, links, file paths, technical identifiers unchanged. "PC (Windows)" is a technical identifier, so keep unchanged. "operatingSystem": "Windows" keep.
"applicationCategory": "Single-player, Multiplayer" => maybe keep? It's technical. Keep unchanged.
"publisher": "команда из 3 человек" already Russian. "developer": same. "offers": price unchanged.
"aggregateRating": unchanged. "review": "reviewBody": "Comprehensive editorial review of Escape to the Italian brainrot." => translate to Russian. "author": "SoftPas Editorial Team" keep as proper noun.
"breadcrumb": "Escape to the Italian brainrot review" => translate. "datePublished": unchanged. Thus we need to translate those JSON values.
Now go through article content. I'll produce final output with translated Russian text. Let's translate paragraph by paragraph.
Paragraph 1 (Overview): "Escape to the Italian brainrot is a collaborative horror experience designed for 1-2 players, blending tense survival mechanics with atmospheric dread. The game centers on evasion—players must avoid the presence of a threatening entity known as Сахур (Sahur) and other unseen horrors to survive long enough to escape. While the game's narrative is intentionally minimal, the developer has emphasized a strong focus on tension, pacing, and player cooperation.
The experience is built around the core idea of shared vulnerability, where every decision, movement, and sound can have lasting consequences. Designed by a small team of three creators, the game reflects a lean but focused development approach, prioritizing mood and atmosphere over expansive content. The publisher has not shared detailed story information, nor has it described the setting beyond the implied presence of a haunting environment.
The genre expectations of survival horror are met through a combination of limited resources, unpredictable enemy behavior, and environmental storytelling. The game is intended for players who appreciate psychological tension, cooperative gameplay, and the unsettling charm of Italian horror aesthetics. It offers a compact,
