Shipping a 592-URL site in 8 locales as a static export: what actually broke
I build for the web. The thing I most recently shipped is Solitaire Online : 27 solitaire variants, eight languages, no third-party ad scripts, exported as static HTML. That last constraint is the only one that mattered. Every decision below follows from it. The build: 592 URLs, eight languages The sitemap has 592 URLs: roughly 30 game pages and 45 written guides, replicated across en (root),…
I recently shipped Solitaire Online, a website featuring 27 solitaire variants, eight languages, and no third-party ad scripts. The site is exported as static HTML, which affected the design and functionality of the website. The build consists of 592 URLs, replicated across eight languages: English, German, Spanish, French, Dutch, Italian, and Portuguese.
All eight locales feature full hreflang plus x-default, localised titles, and localised content. The site's structure includes a single shared slug for each game, rather than separate slugs for each language. The JSON-LD structured data for each game page is generated dynamically and included in the HTML at request time, ensuring that search engines can properly index the content.
The main issues that arose at scale involved sitemap weight, icon assets, and screenshot routes. To address these issues, the author recommends keeping static output, using a single data object per game, and avoiding third-party scripts. The author also notes that the hard part was not the game logic, but rather the complexities of managing a multi-locale static site.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
