How do you make a WeWeb website or web app multilingual without losing navigation, form accuracy or international search visibility? This WeWeb localization guide explains app languages, page language settings, translated text elements, the Change language workflow, dynamic content and how to test published language URLs and SEO metadata. It is written for builders who need visitors to understand and complete tasks in another language, not merely see a second-language heading in an editor preview.
WeWeb’s current documentation describes app languages in Interface Settings, enabling languages on individual pages, switching visible text in the editor, and a Change language action within workflows. Those facilities help authors prepare a multilingual interface. They do not automatically guarantee that API-backed records, emails, legal text, every generated message or international search metadata are correct. Editor versions and routing configurations have changed over time, so claims about URL prefixes, canonical tags or hreflang should be checked against the real deployed site.
Start with one complete visitor journey: arrive at a public page, choose a language, follow navigation, open a form, trigger an error, submit a valid request and read the true result. Then separately test whether the page is discoverable through the intended international search path. Build from real tasks and stable data rather than from word-count or translation-coverage badges. The following chapters explain the important boundaries and use fictional cases to show how to verify them.
The quick answer
Add the intended languages at the app level, enable them for the necessary pages and prepare reviewed values for each translated element. Offer a clear selector or documented Change language workflow, while keeping application data and access rights stable. Test API-driven content and error states separately. For public SEO pages, inspect deployed language URLs, metadata, canonical tags and any alternate-language markup instead of assuming an editor setting guarantees indexing.
WeWeb multilingual launch checklist
- Choose supported locales and a predictable default.
- Enable each language on every page in the intended visitor journey.
- Translate actions, forms, error states, help, navigation and downstream messages.
- Separate dynamic data and stable IDs from visible labels.
- Test language-change workflows on live and production-equivalent builds.
- Verify language URLs, page metadata and indexability where SEO is relevant.
- Review RTL display, accessibility, responsiveness and privacy boundaries.
1. WeWeb offers app and page language settings
Current WeWeb documentation describes app languages under Settings and Interface Settings, while page language controls determine where a translation is used.
A situation worth understanding: A website might add French as an app language but forget to enable French on its pricing page, leaving that important journey unavailable in the visitor’s selected language. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: Choosing a locale at project level is not evidence that every page, element, form, record and notification has been translated. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Inspect app languages and each page’s enabled languages; run real navigation tests rather than checking only the configuration modal. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
2. Know the editor version and location of controls
WeWeb’s newer editor documentation puts languages under Interface Settings in the Settings tab and shows page-level language switching in the canvas header; older tutorials use different menus.
A situation worth understanding: A maker follows a previous-generation guide looking for a More menu and assumes multilingual support was removed when the interface no longer matches. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: UI steps can become outdated even while the underlying concept remains useful. A guide should distinguish documented behavior from a guess about current layout. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Use the current editor’s Settings and page controls, consult the official documentation linked below, and verify every action in the actual project. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
3. Choose a default language deliberately
The default language should supply an understandable first visit and an intentional fallback for people whose browser locale is unsupported.
A situation worth understanding: A Spanish-speaking visitor arrives at a project that supports English and French; the product must have a predictable response rather than displaying a broken mixture. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: A browser language is a useful hint but cannot prove the visitor’s actual preference, especially on public or shared devices. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Set a clear default, provide a visible change-language route and test first visits with browsers set to unsupported and mixed language preferences. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
4. Enable languages on the pages people need
WeWeb’s official page guidance describes enabling a language for an individual page and previewing its text using the language controls.
A situation worth understanding: A customer enters a localized home page but lands on an account form whose page language was never enabled. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: A multilingual project can appear complete from the landing page while navigation leads into source-language dead ends. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Create a page inventory and test the entire user journey in each locale, including rarely visited recovery and help pages. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
5. A language selector must mean what it promises
The documented language dropdown and Change language workflow action can control visible content, but they should not silently change customer identity or submitted data.
A situation worth understanding: A user selects Japanese in a settings control and expects the remaining interface labels to update without losing the partially completed form. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: A selector that changes only one heading while leaving forms and error messages unchanged creates false confidence about language coverage. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Wire and test switching across pages, delayed content, form state and return visits. Identify clearly which parts of the app support each locale. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
6. Use the Change language workflow for real behavior
WeWeb documents a Change language action that can be triggered by a workflow and switch the displayed language for the application or particular pages.
A situation worth understanding: A member clicks a French-language button to move to English instructions without navigating away from the underlying account record. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: A workflow that resets unrelated variables, opens a new unauthenticated session or clears a form may make language switching costly or unsafe. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Test before and after partial form completion and ensure that switching affects words, not underlying records or permissions. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
7. Translate text elements with context
Page text and headings can have language-specific values, but a translator still needs to know whether a phrase is a heading, warning, button or confirmation.
A situation worth understanding: The source phrase ‘Close account’ can mean dismiss a window or permanently terminate membership; its translation depends on the operation behind the control. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: A grammatically polished target word may be wrong if the translator cannot see the consequence of the action. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Document important source meanings, provide page screenshots with safe synthetic data and review each action in its real interface. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
8. Dynamic text is a separate translation surface
Records retrieved from a database or API are not guaranteed to have translated content simply because the surrounding WeWeb page has language variants.
A situation worth understanding: An events website may translate its navigation while event titles, descriptions, cancellation notices and organizer messages still come from one source language. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: An interface can be bilingual around a wholly monolingual catalogue, or it can display a generated paraphrase as though it were the original notice. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Model localized content fields or a separate approved translation source where appropriate; retain canonical identifiers and ownership. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
9. Keep API and database identities stable
Content may be displayed through WeWeb elements, formulas and data sources. A visible translated caption should not become the identifier used by an API to authorize an update.
A situation worth understanding: A French customer chooses a delivery status that is stored internally as delivery_requested, not the target-language phrase displayed on screen. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: Changing a key when the language changes can break filters, reports and conditional workflows, even when the page looks correct. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Use stable IDs in data and workflows; map them to translated labels when displaying human-readable states. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
10. Form labels and validation messages travel together
An international form needs translated labels, placeholders, examples, validation errors, required-field markers and final confirmation states.
A situation worth understanding: A visitor enters a telephone number after reading an Arabic hint, but the form displays an English error with an unfamiliar number format. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: Reviewing only the filled successful form misses the moment a user cannot proceed and needs the most precise instructions. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Submit empty, invalid and valid data in every enabled language; confirm what is saved and what the visitor is told at each step. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
11. Success text must describe the actual system state
Pending, saved, submitted, confirmed, authorized and refunded are not synonyms. Their translations must follow authoritative data or workflow responses.
A situation worth understanding: A member presses Request Cancellation, and a translated confirmation says the membership has ended before the backend approves or processes anything. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: Language polishing can conceal the more serious product bug: claiming an action happened when the server has not confirmed it. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Connect messages to real response states, show pending and failed steps accurately and test slow, rejected and duplicated requests. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
12. Browser preference is not identity or consent
Browser language detection is a starting signal for presentation, not proof that the user gave informed consent or belongs to a particular region.
A situation worth understanding: A multilingual visitor using a shared computer may inherit a language choice that does not belong to them; a traveler may use English on a French-region network. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: A website should not select legal permissions, account roles or pricing eligibility solely from the displayed language. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Offer a comprehensible choice and keep authentication, authorization and regulatory decisions based on their actual rules. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
13. Locale-specific URLs need direct verification
Multilingual SEO depends on which URLs the published project serves, how a crawler receives language versions and whether alternate pages are indexable. Historical WeWeb guidance and editor versions differ.
A situation worth understanding: A marketer expects distinct /fr/ and /en/ URLs from a language selector, yet the production deployment may use another routing configuration. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: Assuming a URL pattern, automatic hreflang or indexability without checking the published site can make translated pages inaccessible to search engines. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Inspect real requests, browser address changes, source markup, canonical tags and language alternates in the deployed version. Avoid promising search results from editor previews. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
14. Do not mix canonical URLs and translation variants
Search engines need coherent indexable pages. A canonical element that points every translated page to one source-language URL can defeat the team’s discovery objective.
A situation worth understanding: A German product explanation has a distinct address, but its metadata points only at the English page as canonical without a reason. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: The problem is not just translation quality; the site may tell crawlers the alternate-language page should not be indexed independently. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Audit one representative language pair with its actual URLs, canonical decisions, sitemap inclusion and any hreflang signals appropriate to the deployment. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
15. Language paths and page navigation require consistency
When a project uses locale-specific paths, navigation should preserve the chosen language through links, forms, authentication redirects and return journeys.
A situation worth understanding: A person reads a French pricing page but the link to account registration lands on the English version, making the language switch look unreliable. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: A globally translated header cannot compensate for a path or redirect rule that routes visitors away from their chosen language. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Follow internal and external links while watching both the visible language and the URL. Include invalid paths and redirect behavior in testing. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
16. Page titles and descriptions need localization
A translated page’s on-screen heading may be correct while its search title, description and social preview remain in the source language.
A situation worth understanding: An Arabic-language event page shares an English preview card whose wording no longer accurately summarizes the localized page. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: A mismatch can confuse readers before they even arrive, and search engines may extract the wrong summary. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Inspect published metadata and link previews for each intended locale, checking that titles and descriptions match the content and language. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
17. Navigation, breadcrumbs and menus are user tasks
A localized page should let readers find products, support, policies and the language switch. Its menu must remain understandable at every breakpoint.
A situation worth understanding: A Spanish visitor changes language but a mobile navigation drawer still uses untranslated custom menu labels or hides the language control. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: People may abandon the site not because the article translation is wrong but because they cannot navigate to the next action. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Test desktop and mobile menus, keyboard focus, bread crumbs and the route back to the language selector. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
18. Right-to-left text needs layout review
Arabic and Hebrew raise questions about alignment, visual direction, bidirectional punctuation, cursor behavior and mixed Latin account identifiers.
A situation worth understanding: An Arabic form shows a Latin booking reference in the wrong visual order and confuses the reader about which characters to copy. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: Reversing all layout elements indiscriminately is not the same as making a trustworthy right-to-left interface. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Test real sample strings on published pages; preserve exact identifiers, numbers and technical values and review with native-language users. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
19. Long strings need breathing room
Translations can be longer than English, so a fixed-width button or narrow mobile form can become inaccessible after adding another language.
A situation worth understanding: A German confirmation button wraps into three lines and covers a Cancel action on a small smartphone. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: Shortening wording by removing important qualifications can change the meaning of a legal or financial action. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Use responsive layouts and locally reviewed concise alternatives, then test the exact published page and touch targets. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
20. Content security and privacy still apply
WeWeb may connect to backend services and third-party translation tools. A localization project must not expose account data, confidential messages or API secrets unnecessarily.
A situation worth understanding: A translator is asked to review a real customer complaint copied from production into an uncontrolled spreadsheet. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: More readers and editors may see translation material than the original secure app data, creating a disclosure risk. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Prepare synthetic examples, minimize access and obtain appropriate permissions before processing sensitive text with any outside service. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
21. Accessibility is a language feature
Accessible labels, headings, error descriptions, focus order and screen-reader announcements must remain useful in every supported language.
A situation worth understanding: A visually labeled icon announces only ‘button’ to a screen reader while the action deletes a record. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: Correct written words cannot rescue a workflow that cannot be operated with keyboard or assistive technology. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Use supported accessibility checks and a real task with keyboard and screen reader, including changing language and recovering from mistakes. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
22. Published content differs from editor preview
The editor can show language variants without proving that the deployed version includes those translations, correct backend values or working redirects.
A situation worth understanding: A marketer previews a French page successfully but the current published site still serves the earlier source-language version. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: A clean preview screenshot proves only that one preview state looked right at that moment. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Test the live deployment with fresh sessions and actual user roles. Record version, URL, locale and resulting backend behavior. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
23. Separate website SEO from authenticated app localization
A private portal and a public multilingual content site have different discovery needs. SEO may be irrelevant behind authentication while comprehension and access remain crucial.
A situation worth understanding: A member-only dashboard needs readable forms and statuses, whereas a public guide may need independently discoverable translated URLs and metadata. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: Applying one SEO checklist blindly to both products wastes effort and can accidentally expose private routes to crawlers. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Choose goals by page type; verify crawler controls for public pages and security boundaries for private ones. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
24. Every content update creates a translation decision
A changed source action, new pricing term, altered account policy or additional page can invalidate earlier reviewed translations.
A situation worth understanding: A product team changes a page from ‘Request a trial’ to ‘Start paid plan’, while existing target-language text still promises a free trial. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: An outdated translated promise may persist for months if content review is separated from release ownership. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Track changed meaning across page variants, reopen review for high-consequence text and retest the end-to-end task after publication. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
25. Measure outcomes, not the number of translated fields
A multilingual WeWeb project is successful when visitors can find a page, read its meaning, navigate, submit the right data and understand the response.
A situation worth understanding: A page may report 100 percent text coverage while a crucial checkout exception or consent notice still appears only in the source language. The reader’s journey is a chain of decisions; a translated heading is only useful when the next action remains understandable and available.
What may go wrong: Translation statistics measure coverage but not comprehension, access or trustworthy state reporting. Misleading language can cause the person to act on the wrong assumption, even if the website still appears to function.
How to work through it: Ask unfamiliar fluent readers to complete tasks and report what they think happened, then compare it with actual saved records and public URLs. Record the expected task outcome, inspect the published state and ask a reader in the target language to explain the next available step.
Diagnostic casebook: problems to rehearse before publishing
These are constructed testing examples, not reports of current WeWeb defects. The point is to identify which part of a multilingual web experience produced the failure: language configuration, page coverage, content source, workflow, routing, accessibility, backend response or search metadata. Use safe example records so testing does not disclose real customer information.
Case 1: French was added to the project but not the page
Diagnosis. The app configuration lists French, yet the checkout page is not enabled for that language. The user reaches a mixed-language journey. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Inspect the page’s enabled languages and test navigation from the localized home page to the final checkout action. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 2: The visitor cannot find the selector
Diagnosis. The language switch exists on desktop but disappears behind a mobile navigation drawer or inaccessible overlay. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Test responsive layouts, focus order and touch access with a first-time visitor who has no knowledge of the editor. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 3: Switching language clears a half-filled form
Diagnosis. The Change language workflow unexpectedly resets page variables or navigates through a fresh session. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Separate presentation updates from form state, then test language switching after partial entries and errors. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 4: A dynamically loaded record remains English
Diagnosis. The element’s fixed caption is localized, but its product description comes from a one-language database column. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Model translated data deliberately or explain the available language; test real sample records and preserve the original identity. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 5: The API receives a translated status
Diagnosis. The French caption for a booking state is sent as the API status instead of the canonical code. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Keep internal keys stable and translate only the human-readable label. Inspect the actual payload and resulting stored record. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 6: The page promises a completed payment
Diagnosis. The translated success banner appears before the payment provider returns confirmation. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Introduce pending, declined and completed states based on authoritative responses and test the failure journey. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 7: A localized link returns to the source language
Diagnosis. A French landing page links to an English registration URL without preserving the selected language or explaining the change. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Audit public navigation and redirects in the published build; confirm the user can continue the intended journey in French. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 8: The translation page is not indexable
Diagnosis. The team assumes a second language automatically creates a crawler-accessible alternate page, but the live URL, tags and rendering are unverified. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Inspect actual page response, robots behavior, canonical decisions and any hreflang markup rather than relying on promotional claims. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 9: Two language URLs share a wrong canonical
Diagnosis. A page has distinct English and German paths but metadata signals that only the English page is authoritative. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Review canonical strategy with the SEO owner, align it with genuine duplicates and verify language alternatives on the published pages. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 10: Social previews use the source language
Diagnosis. A shared French guide link appears with English title and description because metadata was not localized. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Inspect previews and rendered metadata for target URLs; make promises consistent with the target-page content. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 11: A German button becomes unreadable
Diagnosis. An important action has a long translated label that clips on mobile. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Give the control enough space or review a concise equivalent; retest accessibility and the exact resulting action. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 12: Arabic punctuation changes an account code
Diagnosis. Bidirectional display makes a mixed Latin-digit customer reference appear out of order. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Test exact copy-paste and record lookup behavior with native-language readers; preserve the original identifier. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 13: A guest inherits a language from another user
Diagnosis. A shared machine retains the previous visitor’s preference, and the next person assumes the app chose their own account language. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Define guest and sign-out behavior; test first visits after different users without leaking account-specific information. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 14: A form example contradicts its validation
Diagnosis. A localized hint shows one date format, but the input’s accepted format and error still refer to another. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Translate hint, sample and error together; enter the example literally and verify the saved date. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 15: A privacy notice is only partly translated
Diagnosis. The heading has a target-language value while the actual data-use terms, opt-in state or withdrawal instructions remain source-only. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Require a complete reviewed notice and ensure the consent interaction accurately records a deliberate choice. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 16: An email contradicts the page confirmation
Diagnosis. The WeWeb form says an appointment request is received but a downstream email claims the appointment is confirmed. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Give each service a correct state and target-language template; test both channels with a fictional request. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 17: The wrong region is inferred from language
Diagnosis. A visitor chooses Portuguese and the app assumes the customer lives in Brazil, changing terms or currency without confirmation. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Keep country, language, billing currency and user eligibility separate; ask for required facts directly. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 18: A dashboard reports an impossible currency conversion
Diagnosis. The display symbol changes after a language switch while the numeric amount remains identical. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Store actual currency codes and implement approved conversion logic only where needed; verify rates and rounding separately. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 19: A page’s supported languages differ from the menu
Diagnosis. The navigation displays Spanish as an option on a page without approved Spanish content. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Align offered language choices with actual supported pages and specify fallbacks instead of silently displaying a partial translation. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 20: A screen reader cannot identify Change language
Diagnosis. The visible icon is recognizable but has no meaningful localized accessible name. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Add or verify an action-specific accessible label and test operation with keyboard and a supported screen reader. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 21: A preview is mistaken for production QA
Diagnosis. Language variants look correct inside the WeWeb editor while the published domain is a release behind. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Check the live URL in a fresh browser session and record which version, language and page were actually tested. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 22: An old translation still advertises free access
Diagnosis. The product’s policy changed, but the translation of the earlier signup promise was not reopened for review. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Flag substantive source edits, ask a qualified translator to review the new meaning and test the exact signup consequence. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
Case 23: A complaint cannot be reproduced
Diagnosis. The support ticket says a translation failed but contains no locale, page URL, text key or version, and includes an unnecessary customer screenshot. Before changing copy, distinguish what the user saw from what the browser requested, what the backend returned and what the application actually saved.
Resolution and verification. Record safe reproduction details using dummy data, then compare visible text with the actual page and workflow state. Recheck the complete journey in the published site rather than stopping at the first corrected screenshot. For public pages, include a fresh browser visit and inspect the resulting URL as well.
A practical four-week rollout
Week one is discovery. Choose a few priority languages based on real audiences and decide whether the project is a public site, a private portal or both. Inventory page content, navigation, forms, validation, automated messages, data records and metadata. Identify which wording conveys permissions, prices, commitments or irreversible actions. Rewrite the source text for clarity where needed before asking translators to carry it into another language. Document the actual business meaning behind each important control.
Week two creates controlled language variants. Add the locales in the documented app settings, enable them on target pages and translate the essential elements. Implement a user-facing language route, then trace how it behaves through navigation and partial form completion. Preserve canonical status codes and backend identities. For dynamic text, choose an approved multilingual data model or translation workflow instead of assuming static text settings will rewrite database records.
Week three is failure testing. Submit invalid forms, simulate a slow or rejected request, navigate on mobile, use long strings and check mixed-script identifiers. Have local readers complete tasks without coaching. For public international pages, inspect the real deployed URLs and metadata. Confirm any canonical or alternate-language behavior using the actual deployment; do not claim search engines will index a page merely because the editor has a French or German setting.
Week four is release review. Compare the authoritative backend result with every success, pending and error message. Test a fresh browser, an unsupported browser locale and a return visit. Verify accessibility names, keyboard focus and any right-to-left presentation. Assign an owner for new strings and future content edits so updates do not strand readers in old language variants. Publish only when the task outcomes are correctly represented across supported languages.
Frequently asked questions
Does WeWeb have multilingual settings? Its current documentation describes app languages, page language configuration and a Change language workflow. Is adding a language enough to translate every page? No; pages and text elements need appropriate coverage. Does the language switch rewrite database content? Do not assume it does. Can language switching alter permissions? It should not; authorization must remain based on independent security rules.
Are translated pages automatically indexed internationally? Do not assume so. Inspect deployed URLs, crawlability, metadata and language signals. Do all projects use the same URL prefix rules? Verify the actual editor version and published routing. Does a long translated label require redesign? Sometimes; test layout and accessibility. What is the most useful acceptance test? Have an unfamiliar person finish a real task in the target language and confirm the backend result.
What a finished multilingual WeWeb experience feels like
A visitor can arrive, recognize the available languages, select one, follow links without unexpected language changes, understand each field and make a deliberate decision. When a request fails, the message helps them recover. When an operation succeeds, the site describes the outcome the backend actually confirms. Public translated pages can be reached through the intended links and verified search-facing metadata. The interface, the application state and the words agree.
Official documentation and further reading
WeWeb Documentation — App languages explains project-level language settings. WeWeb Documentation — Change language describes workflow switching. WeWeb Documentation — Page languages describes enabling and previewing page translations. WeWeb Documentation — Editor describes the newer interface. See the Translate Like a Pro series index and Master Art of Translation for the larger world-facing architecture.