Global Sites AI

The build script passes your English strings through a translation source, and the sample config uses Google Translate. Every page is rendered once per language, and the resulting files sit in their own directory, so a Spanish visitor gets a Spanish URL rather than a query string. Strings live in i18next keys, which means one edit to the source text flows to every locale on the next build.

Each locale gets its own path, and the switcher moves readers between the same page in different languages instead of dumping them on the homepage. It ships as a dropdown and as footer links, and you can use either or both. For multilingual SEO, that structure is the part that matters, because search engines can index and rank each language version separately.

Both files are produced during the build and include every language variant, so you don't hand-edit XML after adding a page. Skip rules for the sitemap itself, robots.txt, and the 404 folder are set in the config. This is the feature that saves the most tedious work on a site with more than a handful of pages.

The build checks that the generated HTML is valid and that no internal link points to a missing file. In the sample run shown on the site, it verified 10 HTML files and reported no internal URL errors, finishing 94 files in under half a second. Broken links surface before deploy instead of after a customer finds them.

Pages come out around 20KB each, according to the seller, because the build emits plain HTML with no framework runtime. That keeps hosting cheap and first paint quick on slow phones. It also means the site works on any static host, including object storage and CDN-backed buckets.

If you'd rather not touch the code, the seller offers to take a single HTML file with inline JavaScript and return translated pages plus the source. A 10-page site conversion is available as a separate job. Translations in that service come from AI, and the seller notes they may not get a full human review.