viton13.com: a Next.js site in four languages across seven hosts

VITON¹³ is one company with several parts: a studio, a store, the journal VJOURNAL, the marketplace VIT MARKET, a school and a support centre. It needed one website that holds all of them in English, Russian, Spanish and French and gives each part an address of its own.

Releases also had to stay safe. With thousands of pages in four languages, a broken route or a missing language edition is easy to ship and hard to notice, so every release needed a check before it reached visitors.

One Next.js 16 application, built with React 19, serves seven hosts: viton13.com for the company pages and the research library, and subdomains for the studio, store, journal, market, school and support. English is served without a prefix; the other editions live under /ru, /es and /fr.

Each host publishes its own sitemap. Pages list their language editions with hreflang tags in the HTML and leave out any edition that is closed to indexing. Old section addresses on the main domain answer with a permanent 308 redirect to their subdomain: viton13.com/journal, for example, now opens journal.viton13.com.

The robots.txt on viton13.com names 13 AI and search agents, lets them read the content and keeps the admin area closed in every language. The application sends Content-Security-Policy, HSTS with preload, X-Frame-Options DENY and Permissions-Policy headers.

A release is built on the server and has to pass several gates before it goes live: SEO and content checks, the production build, and then a crawl of the built release started on an isolated port. If a gate fails, the release stops and the live site stays as it was. On 19 September 2026, when the site still had a fifth edition (since closed), the crawl checked 18,987 unique internal routes and found no broken responses.

After the switch, 76 routes are requested through the web server across the subdomains; that day, 40 of 40 AI service pages on the studio and 32 of 32 checks on the VIT MARKET catalogue passed on the live site. If verification fails, the previous release is restored automatically, and ten rollback copies are kept. The release took about 40 minutes from start to the last live check, and the codebase carries 175 automated test files.

On 19 September 2026 the seven live sitemaps listed 7,215 URLs across the five editions the site had then: 5,427 on the journal, 1,130 on the studio, 255 on support, 230 on the store, 105 on the market, 63 on the main domain and 5 on the school. The main domain’s 63 include the 17 published studies of the research library.

The SEO release gate passed its 21 checks with no warnings, and the live pages of the main domain, studio, store and market carry the build ID recorded in that release log, so the figures here describe the site that was live that day.

This case shows how the site is built and released, not how it performs with visitors. It is our own site, not a client project. No Lighthouse or Core Web Vitals measurements were taken, so it makes no speed claim, and it reports no traffic, rankings, leads or sales.

A URL in a sitemap is an invitation to crawl, not proof of indexing. The 308 redirects are in place, but this case does not measure whether search positions carried over to the subdomains. The release crawl covers internal routes only; links to other sites are not checked.

How to check a web studio’s portfolio →