Case Study: artweb.space from React SPA to Astro

01 / Results

What changed

3 → 50+

indexable pages instead of one per language

BeforeAfter

Content in HTML without JavaScriptBefore: no — an empty div#rootAfter: yes, on every page

Indexable pagesBefore: 3 (one per language)After: 50+ across RU and EN

JavaScript on the homepageBefore: 88 KB gzipAfter: ≈ 3 KB gzip

Dedicated service pagesBefore: 0After: 14 RU + 9 EN

artweb.space

02 / Challenge · Solution

The challenge

The old artweb.space was a single-page React application. It looked fine to visitors, but the HTML a crawler received contained only an empty container — every word appeared after JavaScript ran. On top of that, all services lived on one page, so none of them could rank for its own keywords.

Languages were another issue. RU, EN and ES were switched client-side, and all three URLs had the same English title and description.

The solution

Multi-page architecture. Every service got a page built around its own keyword cluster, plus case studies, pricing and a blog.
Astro with static generation. All content is rendered to HTML at build time. JavaScript ships only for the form, the calculator and the theme toggle.
Two languages, two URL sets. Russian at the root, English under /en/, hreflang on every pair, and English copy localized for international clients with USD pricing and a white-label offer.
Technical SEO by default. Unique titles and descriptions, schema markup, a sitemap with hreflang and an OG image for every page.
Legacy URLs. /ru/ and /es/ 301-redirect to the new versions.

Stack

Astro, TypeScript, Tailwind CSS, MDX content collections, Cloudflare Pages and a serverless function that routes leads to Telegram and email.

Start a project

I want results like this

Tell us about your project and we will propose an approach, a timeline and a price.