Book a call
Max Tymoshyn, founder of Norml Studio
Max TymoshynFounder, Norml Studio

Multilingual website launches, with each language's layouts, tags and links tested

For teams adding languages to a website, we build and check the website side of the launch. Every language gets its own addresses, hreflang tags, menus, forms and filters, plus a place in the language switcher. Translated pages and term lists are imported from your files without changing how those files are laid out, and every template is tested with your translated text before release. The translations themselves, and their native-language review, stay with your translators or reviewers.

A few clients we’ve worked with

99Legal / Kremenchuker Law GroupAstraZenecaCoxitDiet vs DiseaseFlorida seal — Regional Counsel projectMetroplex HomebuyersNasdaq Private MarketOffice of Criminal Conflict and Civil Regional Counsel, Second Region of Florida — Ita M. NeymotinPolaclubThe Farm Soho

What we do

Norml prepares the site, imports your translations and runs technical tests on each language version before launch, on the platform your site already runs on. Some projects need only the language structure and hreflang tags; others need the full set, with imports, layout checks and the release.

What we set up for each language

We plan the setup around the platform your site runs on and the files your translators already use.

Solution
Websites
  • Language and URL structureThe address pattern for every language is fixed first, usually a path on your main domain for each one. We list which pages exist in every language, which stay in the source language only, and where the switcher sends visitors when a page has no translation yet.
    01
  • Hreflang tags and language sitemapsEvery page lists itself and its versions in the other languages with hreflang tags, plus a default for visitors whose language the site doesn't serve. Each language has its own sitemap, or its own entries in a shared one, so search engines can find every version.
    02
  • A switcher that keeps visitors on the same pageChoosing a language opens the same page in that language, not the homepage. Visitors pick the language themselves instead of being redirected by browser or location, which keeps every version reachable for people and search engines.
    03
  • Menus, forms, filters and interface textNavigation, buttons, form labels, error and confirmation messages and filter names are set up as translatable text, and dates and numbers follow each language's format, so no template keeps a phrase in the source language. Form submissions can carry the language they were sent in, so your team knows which language to reply in.
    04
  • Imports from your translation filesWhen translations arrive as spreadsheets, one row per page, field or term, we import them into the matching pages and fields and leave each file's sheets and columns as they were, so translators keep working in the same file. Terms that templates reuse across many pages, such as filter labels, are kept once per language.
    05
  • Layout checks in every languageEvery template is checked with real translated text at phone, tablet and desktop widths. Labels and headings that run longer get room to wrap instead of overflowing buttons and menus. When a right-to-left language is on your list, its layouts are mirrored and checked on their own.
    06
  • Site search in each languageSearch returns results in the visitor's language, and its filters and suggestions show your translations. Before launch we run the searches your team lists for each language, including words with accents and other special characters.
    07
  • Redirects and checks after releaseOld addresses redirect to the matching page in the right language. After each release we confirm that every version is open to search engines, that hreflang tags point both ways, and that links between languages reach a page that exists.
    08
Josiah BallCo-Founder & CEO, HOMEEC

“Norml Studio's professionalism and responsiveness were impressive.”

Clutch review
Lucas SeyhunCEO, The Farm Soho

“They were proactive in suggesting improvements we hadn't considered.”

Clutch review
Gaius CooperDirector, Streamline Pump Solutions

“They delivered what they said they would, on time.”

Clutch review
Emma EstefaClient Success Manager, Metroplex Homebuyers

“They focused on how to make our daily operations easier, not just on building features for the sake of it.”

Clutch review
Bret MillerManager, Door Knock Pro

“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”

Clutch review
Saima AhmedFounder, GoPetZen

“Their level of dedication to the success of the project and GoPetZen's business as a whole is unique.”

Clutch review

Files, access and approvals we ask for

  • Translated content and term listsThe translated pages, plus spreadsheets of menu labels, filters, headings and glossary terms, in the format your translators already use and with the source text next to each translation.
    01
  • A reviewer for each languageA translator or native reviewer who approves the wording in each language, and one person who decides when a language is ready to go live. We point out text that looks untranslated or cut off; they decide what it should say.
    02
  • Website and staging accessAdmin or developer access to the site and a staging copy, sent as invitations rather than shared passwords. If a language will use a subdomain or its own domain, we also need access to the account where its DNS is managed.
    03
  • Access to search and visitor reportsAccess to Google Search Console and your analytics, so each language version can be submitted, measured and checked after launch.
    04
  • Your launch listThe languages and regions launching first, the pages each one needs, and any pages a language can't launch without, such as legal pages or terms of sale.
    05

How a new language reaches the live site

  1. [Inventory the pages and text]

    We list every template, page type, form and piece of interface text, and note where each language's content will come from.

    Step 01
  2. [Sign off the language plan]

    You approve the address pattern, the hreflang rules and the handling of untranslated pages before any template changes.

    Step 02
  3. [Prepare the templates]

    Interface text becomes translatable, and the switcher, search and layout fixes are built on a staging copy.

    Step 03
  4. [Import a sample first]

    One section's translations go in first, and your reviewers check them in place. The full import runs once the field mapping holds up.

    Step 04
  5. [Test the staging site]

    Your reviewers read each language on the staging site while we test layouts, links, forms, search and tags at every screen width.

    Step 05
  6. [Release the languages]

    Languages go live together or one at a time, as you prefer, and each release ends with checks on the live site.

    Step 06

The people who do this work.

Meet the whole team

No account layer between you and them. These are the Norml specialists this work runs through.

Max Tymoshyn, founder of Norml Studio

Let's chat

“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”

Max TymoshynFounder & Architect

From the Norml blog.

Questions about launching in more languages

Who writes and reviews the text in each language?
Your translators or native reviewers. Norml doesn't translate or proofread languages, and we don't judge whether a translation reads naturally. Your reviewers get every page in its real layout on staging, so they see the wording where visitors will read it.
Can you work with machine-translated content?
Yes, provided a person reviews each language before it goes live. Machine-translated drafts are imported the same way as human translations, and your reviewers check them in context on staging. Their corrections go back into your files and are imported again, so the site and the files match.
Does our website platform need to change?
Usually not. We start with what your platform supports for languages, natively or through an extension made for it, and set up the language versions there. If it can't give each language its own addresses or translate the parts you need, we explain the limit and the options before any work starts.
Which address pattern should each language use?
A path for each language on the main domain is usually the simplest choice, because it leaves one site to host, track and maintain. Subdomains or separate country domains suit a team that runs each market as its own site. We recommend one after looking at your hosting, your platform and how your markets are run.
What happens to pages that aren't translated yet?
You decide by page type. A page can stay unpublished in a language until its translation is approved, or the switcher can send visitors to the source-language page instead. Sitemaps and hreflang tags list only the pages that exist in each language.
How do later corrections reach the site?
Through the same files. Each row is matched to its page or term by a value that stays fixed, such as the page address or the source-language term, so importing a corrected file updates what is already on the site instead of adding copies. A corrected filter label or heading changes on every page that uses it.
Can a language be added to a site that is already live?
Yes. The new language is prepared on a staging copy, and your reviewers read it there while the live site runs as before. It then goes live with its own sitemap and redirects. Pages in the existing languages normally keep their addresses, and any that move are redirected.
What sits outside the website setup?
Keyword research for each new market, ad campaigns in new languages and ongoing maintenance are scoped as separate work, and translation stays with your translators. We don't promise rankings or traffic for a new language.

The law firm, the directory and the rebuild in detail

Read them for the parts a language launch reuses: how the law firm's multilingual pages were structured, how the directory builds pages from records, and how the rebuild went live in stages.

See all case studies