Add Any Language to a Site You Already Built — Without Blocking Anything

A serious update for anyone who builds for more than one country. Fractera is an Agentic Engineering Infrastructure — an agentic engineering platform where AI agents build and run your app on your own server. Until now, adding a brand-new language to a site that already had content was the awkward part: every section and every page needed its own copy, the search-engine markup had to stay perfect, and a full translation could eat a whole subscription budget in one sitting. Today that becomes a single, calm, non-blocking move.

Multilingual Is How You Earn Organic Reach — the Legal Way

Speaking your reader's language is one of the cleanest, fully legitimate ways to grow your audience and your search presence. Google itself documents how to do it: give each language its own real URL and tell search engines, in the page markup, that these URLs are the same content in different languages. Done right, every language you add is a new, honest door into your site. Done wrong — duplicate pages with the wrong markup — and you get punished as a doorway. So the entire job is not just "translate the words"; it is "translate the words and keep the markup flawless." We treat that markup as a first-class part of the feature, not an afterthought.

What "Alternate Languages" Means, and How We Generate It for You

When the same page exists in several languages, each version must carry a small piece of markup — the alternate-language links, known as `hreflang` — that says: "here I am in English, here in Spanish, here in Armenian, and here is the default for everyone else." It is the signal that lets Google show the Spanish version to a Spanish reader and, crucially, understand that your `/es/` and `/hy/` pages are translations, not duplicates competing with each other. Get it wrong and the same content under two languages looks like spam; get it right and it is pure, legitimate reach.

A Non-Blocking Pipeline: the Site Is Whole Now, the Translation Comes Later

Here is the idea that makes the whole thing comfortable. The moment you add a language, every page is seeded with your default language's content — so the site is complete and valid the instant the build finishes, with no machine-translation bill and nothing broken. Each freshly seeded page is quietly marked "needs translation," which tells the engine to keep it out of the search index until it is real — exactly the Doorway guard from the previous section. Then, whenever you choose, a second tool walks those pages and the real translation is written in. The day it is translated, the mark is cleared and the page becomes indexable on the next deploy.

• Step one — expand: the new language appears across every section and post, seeded and valid, pages held out of the index.
• Step two — translate (separately): a runner fills in the real text, clears the "needs translation" mark, and the page goes live to search the next time you deploy.
• Nothing is half-broken in between — a seeded page is a correct page in your default language, never a blank or an error.

Why We Split Translation Into Its Own Step: Limits, and Focus

This separation is deliberate, and it is about respecting how you actually work. The platform runs on a subscription, which means every period has its limits — and translating a whole site is one of the heaviest text jobs there is. If translation were welded onto the main build, a big site could blow through a budget and stall the work. So we draw a clean line: first the structure is finished and deployed, then — at any later moment, on a fresh budget, even with a different and cheaper model — the architect picks up the translations. The main plan is never blocked by a translation hitting a ceiling. It is the same decoupling instinct behind our static-safe app configuration by AI: turn a heavy, recurring job into a clean, separate, repeatable move.

A Step Per Language, So No Translation Is Ever Forgotten

When the expansion runs, it opens one development step for each new language — a real, tracked task that lists every page waiting for that language. This is the guarantee: nothing slips through, ever. You can open the service page Development Steps at any time and see exactly what is planned and what is left. And it is not read-only — you can add a note to a specific translation. Want the Spanish version to lean into Spanish law and link to the actual statutes? Write that note next to the Spanish step, and when the model generates that translation it will honor your instruction. That is how a translation step becomes a place to add regional value, not just swap words.

Your Four Menus Translate Themselves

One detail people expect to be painful, and it simply is not. A site has four menus — the header, the footer, and the left and right drawers. You do not have to think about whether each one will have the new language: the moment you add a language, the matching menu entries are created across all four automatically, because the architecture derives them from each section. You scale the content; the navigation comes along for free. If you have followed our work on the universal multilingual footer, this is the same principle, now applied end to end.

And a Box Never Ships Instead of an "ó": Built-In Encoding Integrity

There is a quiet way multilingual text goes wrong: a lossy step — a voice dictation, a copy-paste, a bad transform — can drop an accented letter and leave a stray character in its place. The file still works, so it ships silently, and a visitor sees a little box where the "ó" in "Documentación" should be. Because we care that markup and text are both flawless, the platform now refuses these broken characters the moment any content tool tries to write one, and ships a project-wide scanner that sweeps every language and every file and reports exactly where a box is hiding — so it gets fixed by hand, with the right letter, before anyone ever sees it.

Put it all together and the bottom line is simple: you prototype your project in one or two languages, and then scale it to the rest safely — pages valid immediately, translation on your own schedule, menus for free, and search-engine markup that Google rewards rather than penalizes. The internal structure is doing the heavy lifting, and it is doing it the legitimate way. For the wider story of how content is built this way, see our note on multilingual content architecture.

Do not wait until they start competing with you. Start competing first.