Translate Like a Pro | 5550 — Prismic Locales, Linked Translations, Alternate Languages, Slice Content and International SEO

Prismic localizations, linked alternate-language documents, UIDs, page builders, locale-aware routes and international SEO means making the meaning, publishing state and reader experience agree in every intended language. Prismic multilingual websites depend on both localized documents and the frontend’s handling of language routes. A translated page is not automatically a working international page: editors must create the correct locale variant, preserve its relationship to the original, review Slice content and publish an accessible language-specific destination. This guide walks through that process for content teams and developers working across countries. The objective is practical: a person should receive correct information in the expected language, complete the next step and never have to guess whether an untranslated field is an editorial decision or an oversight.

Prismic documents can be copied to another configured locale and linked as alternate-language variants. The API’s alternate_languages metadata helps applications build language switching, but independently created documents with matching UIDs are not necessarily linked. Prismic’s AI translation support and workflow vary by plan or rollout; generated translations still require editorial review before publication. These details matter because a multilingual content system does not, by itself, translate or approve facts. A successful implementation separates language editing from release controls, checks the public delivery behavior and preserves shared identifiers, dates and measurable claims wherever those facts have not been authorized to change.

Quick answer: start with a representative page and its source facts; choose the exact target locales; map which fields may change; prepare a reviewed translation; check missing-language behavior and references; publish to the correct environment and stage; load the real public route; test navigation, accessibility and SEO metadata; record approval; then expand the rollout. The sections below explain each decision and the failure it is designed to prevent.

What Prismic localization means in practice

A translation is a meaningful language version of content for a defined readership. Localization goes further: it accounts for presentation, conventions, user expectations, links, supporting media and the availability of a page in a particular market. The platform provides a way to model and serve variants. The people operating it remain responsible for deciding which language is appropriate, whether the facts are correct, whether publication is permitted and what readers will encounter when a translation does not exist.

For Prismic, begin with one existing source page, one target language and one expected reader journey. Inspect how a localized field or document is connected to its source, which status is visible in the editing interface, and what the publicly delivered result looks like. These are three different views of the same workflow. It is common to find a convincing translation in an editor while a website shows a previous version because a publishing step, environment, frontend query or cache has not caught up.

Do not equate translation quality with word-for-word similarity. Technical instructions require stable numbers, ordered steps, permissions, product names and clear warnings. Marketing language requires a natural promise that does not become stronger than the original. Educational content needs plain examples that teach the same underlying idea. The right question is not “Are the strings different?” but “Can a reader in this locale safely understand and use this information?”

The essential distinction: content, locale, publication and delivery

A content entry or document is the stored representation of a page, component or data record. A locale identifies a particular language or language-and-region target. Publication means making an approved version available to a specified delivery context. Delivery is the response an application or website actually receives. In a modern headless CMS these concerns interact but remain distinct. A mistake at any boundary can produce a page that looks translated in a preview and behaves differently for real readers.

The content team should maintain a small but precise inventory: a stable content identifier; source locale; desired locale; page owner; reviewer; revision; approval date; publication destination; actual public route; and fallback rule. The inventory is not valuable because it is bureaucratic. It makes difficult incidents answerable. When somebody reports an English paragraph inside a French page, the team can determine whether the field was never translated, the locale is wrong, the localized version is unpublished or the frontend is requesting a different value.

Twenty-six practical lessons for Prismic

1. Define repository locales

Imagine this real editorial situation: A nonprofit serves English, French and Portuguese but has not agreed which regions each version targets. Adding a language in repository settings is the first configuration decision, not a finished editorial plan. This is not merely an issue of replacing words; it is a decision about which version the site is allowed to represent as correct. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Begin by recording the exact page and language requested, then compare the saved content with the published response rather than guessing from appearance. In Prismic, adding a language in repository settings is the first configuration decision, not a finished editorial plan. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to document public audiences, preferred language identifiers and local reviewers. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. A sensible acceptance test uses two locales, a missing-value case and one link out of the page. This reveals whether the implementation is robust instead of merely plausible. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

2. Understand the master document

A common failure begins quietly: A marketing page in English will become the source for regional variants. The master is a starting reference but translated documents may need different examples and local conditions. The visible page and the stored record must be tested separately, because a convincing preview cannot prove successful delivery. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Ask who owns the underlying fact, who approves the language and who controls the website route. They may be different people. In Prismic, the master is a starting reference but translated documents may need different examples and local conditions. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to record which facts must remain identical and which require explicit market approval. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. The final check should be performed in the real page context, including its heading, navigation, supporting visual, next action and search metadata. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

3. Copy into another locale

The difficulty becomes visible when An editor creates a fresh French document with the same UID as an English one. Two documents can share a readable identifier without being correctly linked as translations. The practical risk is that fluent language hides a broken relationship between content, locale and publication. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Check the source content first, since even a perfect translation of an outdated instruction remains outdated. In Prismic, two documents can share a readable identifier without being correctly linked as translations. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to use the page’s locale-copy workflow and inspect alternate language relationships. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. Do not resolve an uncertainty by silently substituting a promise from another market. Leave a clear gap until the relevant owner decides. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

4. Inspect alternate_languages

For an international content team, consider this case: A language switcher fails because the API metadata contains no French alternate. The alternate_languages property identifies the related localized documents known to Prismic. A useful diagnosis identifies the responsible field, the actual target locale and the version the application is consuming. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Open the page on a second device or clean browser session to separate personalized navigation from the actual public response. In Prismic, the alternate_languages property identifies the related localized documents known to Prismic. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to inspect the document response before debugging the menu component. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. Keep a before-and-after example that future editors can use to recognize the same issue without repeating the investigation. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

5. Understand UID uniqueness

One useful way to understand the platform is to examine what happens when A translated blog post has a language prefix and a repeated human-readable UID. The UID must be resolved together with locale and route policy, not treated as a globally unique page name. The right outcome is a reliable reader journey, not a dashboard that happens to show a translation as complete. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Work with a small reproducible example, noting each step and the exact difference between expected and observed behavior. In Prismic, the UID must be resolved together with locale and route policy, not treated as a globally unique page name. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to test both URLs and ensure the router requests the intended language document. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. Where several systems are involved, test each boundary independently: editorial record, API response, deployed route and user-visible interaction. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

6. Map locale-aware routes

The reader notices the problem before the editor does: An English page works but the French URL returns a 404. An application framework needs routes that recognize the requested locale and fetch corresponding Prismic content. This is not merely an issue of replacing words; it is a decision about which version the site is allowed to represent as correct. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Begin by recording the exact page and language requested, then compare the saved content with the published response rather than guessing from appearance. In Prismic, an application framework needs routes that recognize the requested locale and fetch corresponding Prismic content. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to verify locale parsing, route generation, query language and fallback behavior together. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. A sensible acceptance test uses two locales, a missing-value case and one link out of the page. This reveals whether the implementation is robust instead of merely plausible. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

7. Prevent false links

Imagine this real editorial situation: A German language menu points to an unrelated German page with a similar title. Matching words in the title do not prove two documents are translations. The visible page and the stored record must be tested separately, because a convincing preview cannot prove successful delivery. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Ask who owns the underlying fact, who approves the language and who controls the website route. They may be different people. In Prismic, matching words in the title do not prove two documents are translations. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to build alternatives from actual document relationships and check the destination content. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. The final check should be performed in the real page context, including its heading, navigation, supporting visual, next action and search metadata. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

8. Translate Slice content

A common failure begins quietly: A page-builder section includes headline, body copy, button label and image caption. Reusing a Slice layout does not guarantee that every visible string is localized. The practical risk is that fluent language hides a broken relationship between content, locale and publication. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Check the source content first, since even a perfect translation of an outdated instruction remains outdated. In Prismic, reusing a Slice layout does not guarantee that every visible string is localized. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to inspect each rendered Slice including mobile variations and shared components. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. Do not resolve an uncertainty by silently substituting a promise from another market. Leave a clear gap until the relevant owner decides. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

9. Preserve page structure with judgment

The difficulty becomes visible when A team duplicates every English section verbatim for all cultures. Translation can require different examples and occasionally different section order without changing essential facts. A useful diagnosis identifies the responsible field, the actual target locale and the version the application is consuming. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Open the page on a second device or clean browser session to separate personalized navigation from the actual public response. In Prismic, translation can require different examples and occasionally different section order without changing essential facts. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to make approved page-level choices and keep core commitments clear across versions. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. Keep a before-and-after example that future editors can use to recognize the same issue without repeating the investigation. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

10. Review rich-text marks

For an international content team, consider this case: A translated paragraph loses its linked source, emphasis or numbered instructions. Meaning can be damaged by losing structure as well as words. The right outcome is a reliable reader journey, not a dashboard that happens to show a translation as complete. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Work with a small reproducible example, noting each step and the exact difference between expected and observed behavior. In Prismic, meaning can be damaged by losing structure as well as words. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to compare links, emphasis, headings and accessible labels in the final rendered page. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. Where several systems are involved, test each boundary independently: editorial record, API response, deployed route and user-visible interaction. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

11. Adapt media assets

One useful way to understand the platform is to examine what happens when A tutorial image embeds English annotations next to a Spanish explanation. Localizing text does not automatically replace words baked into images. This is not merely an issue of replacing words; it is a decision about which version the site is allowed to represent as correct. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Begin by recording the exact page and language requested, then compare the saved content with the published response rather than guessing from appearance. In Prismic, localizing text does not automatically replace words baked into images. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to create suitable alternate imagery and review cropping and alt text. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. A sensible acceptance test uses two locales, a missing-value case and one link out of the page. This reveals whether the implementation is robust instead of merely plausible. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

12. Translate shared navigation

The reader notices the problem before the editor does: A translated page is reachable directly but its main menu remains English. Navigation and footer components may be sourced separately from the page document. The visible page and the stored record must be tested separately, because a convincing preview cannot prove successful delivery. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Ask who owns the underlying fact, who approves the language and who controls the website route. They may be different people. In Prismic, navigation and footer components may be sourced separately from the page document. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to inspect the site’s global content model and route-aware links. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. The final check should be performed in the real page context, including its heading, navigation, supporting visual, next action and search metadata. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

13. Manage missing translations

Imagine this real editorial situation: A user requests a Japanese version that has not been created. A site should not present unavailable material as an approved Japanese translation. The practical risk is that fluent language hides a broken relationship between content, locale and publication. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Check the source content first, since even a perfect translation of an outdated instruction remains outdated. In Prismic, a site should not present unavailable material as an approved Japanese translation. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to choose a clear fallback page or unavailable-language notice and maintain the reader’s context. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. Do not resolve an uncertainty by silently substituting a promise from another market. Leave a clear gap until the relevant owner decides. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

14. Use releases carefully

A common failure begins quietly: A content team groups localized pages into a release for one market. Related pages should be reviewed together so menus do not lead to unpublished children. A useful diagnosis identifies the responsible field, the actual target locale and the version the application is consuming. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Open the page on a second device or clean browser session to separate personalized navigation from the actual public response. In Prismic, related pages should be reviewed together so menus do not lead to unpublished children. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to inspect every planned document and launch time before publishing. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. Keep a before-and-after example that future editors can use to recognize the same issue without repeating the investigation. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

15. Separate language and region

The difficulty becomes visible when A European Portuguese translation is reused for a Brazilian service offer. Shared language does not imply identical regulation, pricing or eligibility. The right outcome is a reliable reader journey, not a dashboard that happens to show a translation as complete. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Work with a small reproducible example, noting each step and the exact difference between expected and observed behavior. In Prismic, shared language does not imply identical regulation, pricing or eligibility. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to have domain owners approve differences rather than leaving translators to invent them. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. Where several systems are involved, test each boundary independently: editorial record, API response, deployed route and user-visible interaction. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

16. Handle AI-assisted translation

For an international content team, consider this case: An editor uses an available AI translation feature for an initial French draft. Machine-generated prose may be fluent while misreading contractual conditions or cultural references. This is not merely an issue of replacing words; it is a decision about which version the site is allowed to represent as correct. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Begin by recording the exact page and language requested, then compare the saved content with the published response rather than guessing from appearance. In Prismic, machine-generated prose may be fluent while misreading contractual conditions or cultural references. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to review against the approved source and keep sensitive claims in human approval. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. A sensible acceptance test uses two locales, a missing-value case and one link out of the page. This reveals whether the implementation is robust instead of merely plausible. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

17. Use glossary instructions

One useful way to understand the platform is to examine what happens when A brand name changes across several localized Slice buttons. Prismic describes glossary and instruction support in its translation offerings, subject to feature availability. The visible page and the stored record must be tested separately, because a convincing preview cannot prove successful delivery. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Ask who owns the underlying fact, who approves the language and who controls the website route. They may be different people. In Prismic, prismic describes glossary and instruction support in its translation offerings, subject to feature availability. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to check account capabilities and verify all outputs instead of assuming a glossary guarantees perfection. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. The final check should be performed in the real page context, including its heading, navigation, supporting visual, next action and search metadata. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

18. Do not assume translation memory

The reader notices the problem before the editor does: An agency expects previously approved segments to be automatically reused without review. Prismic’s public feature FAQ distinguishes glossaries from a traditional translation memory engine. The practical risk is that fluent language hides a broken relationship between content, locale and publication. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Check the source content first, since even a perfect translation of an outdated instruction remains outdated. In Prismic, prismic’s public feature FAQ distinguishes glossaries from a traditional translation memory engine. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to maintain external terminology and revision history when formal TM reuse is required. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. Do not resolve an uncertainty by silently substituting a promise from another market. Leave a clear gap until the relevant owner decides. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

19. Localize SEO titles

Imagine this real editorial situation: The French body loads but the browser tab and search snippet remain English. An international page needs appropriate HTML metadata produced by the application. A useful diagnosis identifies the responsible field, the actual target locale and the version the application is consuming. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Open the page on a second device or clean browser session to separate personalized navigation from the actual public response. In Prismic, an international page needs appropriate HTML metadata produced by the application. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to check rendered title and description for every public locale. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. Keep a before-and-after example that future editors can use to recognize the same issue without repeating the investigation. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

20. Map canonical and alternates

A common failure begins quietly: Two languages are live but only one is included in the alternate links. Correct hreflang needs actual page counterparts and accurate language-region codes. The right outcome is a reliable reader journey, not a dashboard that happens to show a translation as complete. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Work with a small reproducible example, noting each step and the exact difference between expected and observed behavior. In Prismic, correct hreflang needs actual page counterparts and accurate language-region codes. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to generate alternatives from verified published documents and test reciprocal links. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. Where several systems are involved, test each boundary independently: editorial record, API response, deployed route and user-visible interaction. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

21. Keep redirects after slug changes

The difficulty becomes visible when A local editor renames a popular localized page UID. Old URLs may continue receiving inbound links and search traffic. This is not merely an issue of replacing words; it is a decision about which version the site is allowed to represent as correct. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Begin by recording the exact page and language requested, then compare the saved content with the published response rather than guessing from appearance. In Prismic, old URLs may continue receiving inbound links and search traffic. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to preserve supported redirects and update internal menus and alternate references. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. A sensible acceptance test uses two locales, a missing-value case and one link out of the page. This reveals whether the implementation is robust instead of merely plausible. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

22. Verify preview versus production

For an international content team, consider this case: An editor sees a correct French preview but live content is stale. Draft preview data and published API data are not identical by default. The visible page and the stored record must be tested separately, because a convincing preview cannot prove successful delivery. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Ask who owns the underlying fact, who approves the language and who controls the website route. They may be different people. In Prismic, draft preview data and published API data are not identical by default. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to compare the publicly served document and its publication state before announcing completion. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. The final check should be performed in the real page context, including its heading, navigation, supporting visual, next action and search metadata. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

23. Test links in local context

One useful way to understand the platform is to examine what happens when A help page points from French shipping instructions to English-only returns rules. Localization must preserve a coherent reader journey, not isolated readable pages. The practical risk is that fluent language hides a broken relationship between content, locale and publication. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Check the source content first, since even a perfect translation of an outdated instruction remains outdated. In Prismic, localization must preserve a coherent reader journey, not isolated readable pages. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to open every priority link and record justified language crossings. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. Do not resolve an uncertainty by silently substituting a promise from another market. Leave a clear gap until the relevant owner decides. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

24. Review consent and offers

The reader notices the problem before the editor does: An international sign-up page includes consent text translated from a different jurisdiction. Translation can change legal interpretation if claims or permissions are carried across borders. A useful diagnosis identifies the responsible field, the actual target locale and the version the application is consuming. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Open the page on a second device or clean browser session to separate personalized navigation from the actual public response. In Prismic, translation can change legal interpretation if claims or permissions are carried across borders. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to seek qualified market review and avoid making legal promises by translation alone. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. Keep a before-and-after example that future editors can use to recognize the same issue without repeating the investigation. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

25. Design a publication checklist

Imagine this real editorial situation: A translated page publishes with no alternate-language navigation, metadata or mobile QA. Editorial signoff needs to cover the application that presents Prismic content. The right outcome is a reliable reader journey, not a dashboard that happens to show a translation as complete. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Work with a small reproducible example, noting each step and the exact difference between expected and observed behavior. In Prismic, editorial signoff needs to cover the application that presents Prismic content. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to require evidence for route, language, links, accessibility, search metadata and publication. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. Where several systems are involved, test each boundary independently: editorial record, API response, deployed route and user-visible interaction. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

26. Expand from a tested pilot

A common failure begins quietly: A team prepares twenty locales before validating one French journey end to end. The earliest representative page reveals routing and content modeling errors cheaply. This is not merely an issue of replacing words; it is a decision about which version the site is allowed to represent as correct. For a world-facing site, language expectations can change from one region to another, yet the underlying meaning and any material commitment must stay controlled. Explain the situation to a colleague in one sentence before changing a setting. If the colleague cannot identify the expected reader outcome, the team has not defined the problem precisely enough.

Begin by recording the exact page and language requested, then compare the saved content with the published response rather than guessing from appearance. In Prismic, the earliest representative page reveals routing and content modeling errors cheaply. The important evidence is the actual field value, locale selection and delivery state, not a generic “translated” label. Capture the relevant example with its URL and record identifier, while excluding personal information and private credentials. Then inspect one comparable entry that is working correctly. The contrast often reveals whether the cause is editorial content, configuration, publishing, references or an application route.

A practical correction is to complete one language-specific journey before scaling into other markets. Have the right reviewer confirm that the result is both linguistically natural and factually equivalent to the approved source. A sensible acceptance test uses two locales, a missing-value case and one link out of the page. This reveals whether the implementation is robust instead of merely plausible. If the public page still differs, follow the change into the request and response rather than rewriting a correct translation. Close the issue only when the exact target-language page demonstrates the intended result, and record the observation in terms another editor can repeat.

A complete worked example: translating a public service guide

Suppose a worldwide service organization publishes an English guide titled “How to change a delivery address.” It now needs a French edition for readers in several countries. The source guide tells readers to open their order details, choose the address action if the order has not been dispatched, and contact support when the change is no longer available. A literal translation alone is not sufficient: the support channel may differ, button labels may be localized, and the language switcher needs to connect the correct page pair.

First, the content owner verifies that these steps are currently true for the target service. The translator receives the complete guide, its screenshots and a list of product-interface labels. They mark “dispatched” as an operational state rather than inventing a broader promise such as “any order can always be changed.” The editor creates the right Prismic locale variant using the platform’s approved relationship and localization controls. Shared identifiers remain intact; visible headings, body copy, image text and help links receive the language treatment they actually need.

Next, a reviewer checks an order that can still be changed and an order that cannot. If the French page says an action is always available but the application removes the button after dispatch, the translation is misleading even though it reads smoothly. The reviewer also checks whether the public page links to the French support instructions, or clearly indicates when the destination is English. They compare a narrow mobile screen with desktop, confirm that long French labels do not cover controls and verify keyboard focus and screen-reader labels.

Finally, the publication owner checks the approved revision in its actual delivery context. The direct page URL, language switcher, metadata and alternate-language relationships should refer to live content rather than drafts or generic landing pages. A deliberately missing translation is tested to see whether the website gives a sensible response. Only after those checks does the project treat the French page as complete. This is a small example, but its evidence scales much better than checking thousands of isolated word strings.

A repeatable four-week learning and launch plan

Week 1 — understand the content and locale model

Choose one essential reader task. Inventory the source records, visible fields, shared identifiers, linked pages, language targets and current deployment paths. Read the relevant platform documentation and test one localized example in a safe environment. Write the expected output in ordinary language so an editor and developer agree before any translation begins.

For Prismic, make this week’s deliverable observable. Do not accept “translation underway” as a result by itself. The deliverable should name a route, locale, approved content revision, reviewer and actual reader outcome. A small, well-tested set of pages is more useful than a large count of strings whose destination is uncertain. Invite both the writer and the person who maintains the frontend to inspect the same example, because their separate perspectives detect different categories of error.

Week 2 — translate and review a complete journey

Prepare the target-language content with context, vocabulary decisions and marked risk statements. Review headings, buttons, references, images and missing-field behavior. Let a native or professionally qualified reviewer identify ambiguity, awkward register, inaccurate claims or culturally misleading examples. Record decisions that recur across components.

Week 3 — test publication and delivery

Publish the sample to its approved destination, then inspect the actual API and public route. Check direct URLs, language switcher, responsive layouts, keyboard operation, search metadata, canonical and alternate links, caching and intended fallbacks. Exercise both a complete translation and a missing one. Keep screenshots and expected-versus-observed notes for anything that fails.

Week 4 — repair, standardize and extend

Fix the highest-risk issues first: wrong locale, incorrect promise, broken link, unpublished important page or misleading fallback. Retest the exact reader journeys, publish corrections and update the checklist. Introduce additional topics or languages only after the pilot has evidence of reliable content, approvals, publishing and page behavior.

Quality-assurance questions to ask before every release

Meaning: Does the translation preserve the original action, quantity, condition, exception and responsibility without adding an unapproved promise? Test this in a real browser, not only in the content editor. If the answer is uncertain, capture the exact route and locale and assign a person to verify it. The final reader experience is the standard, especially for pages involving payments, eligibility, safety, deadlines or other important decisions.

Language: Would the intended reader recognize the terminology, tone and phrasing as natural for this context rather than as a literal imitation? Test this in a real browser, not only in the content editor. If the answer is uncertain, capture the exact route and locale and assign a person to verify it. The final reader experience is the standard, especially for pages involving payments, eligibility, safety, deadlines or other important decisions.

Structure: Do headings, lists, emphasis, inline links, media captions and alternative text still support the same task? Test this in a real browser, not only in the content editor. If the answer is uncertain, capture the exact route and locale and assign a person to verify it. The final reader experience is the standard, especially for pages involving payments, eligibility, safety, deadlines or other important decisions.

Locale: Is the application requesting the intended language and region, and is missing-language behavior visible and appropriate? Test this in a real browser, not only in the content editor. If the answer is uncertain, capture the exact route and locale and assign a person to verify it. The final reader experience is the standard, especially for pages involving payments, eligibility, safety, deadlines or other important decisions.

Publishing: Is the approved revision published to the actual stage or environment used by the live site? Test this in a real browser, not only in the content editor. If the answer is uncertain, capture the exact route and locale and assign a person to verify it. The final reader experience is the standard, especially for pages involving payments, eligibility, safety, deadlines or other important decisions.

Navigation: Do links, breadcrumbs, language switches, forms and help pathways take readers to correct available destinations? Test this in a real browser, not only in the content editor. If the answer is uncertain, capture the exact route and locale and assign a person to verify it. The final reader experience is the standard, especially for pages involving payments, eligibility, safety, deadlines or other important decisions.

Search: Do the public title, description, canonical, alternate links and indexing behavior match the actual delivered page? Test this in a real browser, not only in the content editor. If the answer is uncertain, capture the exact route and locale and assign a person to verify it. The final reader experience is the standard, especially for pages involving payments, eligibility, safety, deadlines or other important decisions.

Evidence: Can the team show a reproducible user journey, record the reviewer and locate the version released? Test this in a real browser, not only in the content editor. If the answer is uncertain, capture the exact route and locale and assign a person to verify it. The final reader experience is the standard, especially for pages involving payments, eligibility, safety, deadlines or other important decisions.

Frequently asked questions

Does adding a locale translate existing content?

No. A locale configuration identifies a supported target. It does not guarantee approved language content for each record or a live route for each page. For Prismic, use the real source record and the rendered target-language route as the two ends of the test. Record what the reader can do after receiving the information, then decide if the response is both correct and usable. Avoid treating any one dashboard status as a substitute for reviewing the public result.

Can fallback be treated as finished translation?

No. Fallback can help readers in some circumstances, but it may contain another region’s wording or incomplete legal and service information. For Prismic, use the real source record and the rendered target-language route as the two ends of the test. Record what the reader can do after receiving the information, then decide if the response is both correct and usable. Avoid treating any one dashboard status as a substitute for reviewing the public result.

Why does the editor show a translation that visitors cannot see?

The translation may be unsaved, unpublished, published to another destination, absent from the frontend request or hidden behind a cached build. For Prismic, use the real source record and the rendered target-language route as the two ends of the test. Record what the reader can do after receiving the information, then decide if the response is both correct and usable. Avoid treating any one dashboard status as a substitute for reviewing the public result.

Should every field be translated?

No. Localize human-readable content and market-specific material deliberately. Protect identifiers and shared data where their meaning depends on staying stable. For Prismic, use the real source record and the rendered target-language route as the two ends of the test. Record what the reader can do after receiving the information, then decide if the response is both correct and usable. Avoid treating any one dashboard status as a substitute for reviewing the public result.

How do we decide whether a different regional fact is legitimate?

Ask the appropriate content or subject owner to approve the market-specific variation, and describe it as a localized content decision rather than a spontaneous translator alteration. For Prismic, use the real source record and the rendered target-language route as the two ends of the test. Record what the reader can do after receiving the information, then decide if the response is both correct and usable. Avoid treating any one dashboard status as a substitute for reviewing the public result.

What should the language switcher do when a matching page is missing?

Prefer a transparent destination or language notice over sending the reader silently to an unrelated page. For Prismic, use the real source record and the rendered target-language route as the two ends of the test. Record what the reader can do after receiving the information, then decide if the response is both correct and usable. Avoid treating any one dashboard status as a substitute for reviewing the public result.

Are translated titles and public slugs the same thing?

Not necessarily. A content headline, route slug and HTML title may live in separate fields or application logic. For Prismic, use the real source record and the rendered target-language route as the two ends of the test. Record what the reader can do after receiving the information, then decide if the response is both correct and usable. Avoid treating any one dashboard status as a substitute for reviewing the public result.

Does perfect grammar guarantee search readiness?

No. Search visibility also depends on indexable routes, correct metadata, canonical relationships and accurately mapped alternate pages. For Prismic, use the real source record and the rendered target-language route as the two ends of the test. Record what the reader can do after receiving the information, then decide if the response is both correct and usable. Avoid treating any one dashboard status as a substitute for reviewing the public result.

Can automatic translation replace review?

It can help prepare a draft where supported, but it cannot reliably certify commercial commitments, sensitive wording or the correctness of the delivered application. For Prismic, use the real source record and the rendered target-language route as the two ends of the test. Record what the reader can do after receiving the information, then decide if the response is both correct and usable. Avoid treating any one dashboard status as a substitute for reviewing the public result.

Why test both the API and the website?

The API reveals what the content system serves; the website shows what the reader actually sees after routing, rendering and caching. For Prismic, use the real source record and the rendered target-language route as the two ends of the test. Record what the reader can do after receiving the information, then decide if the response is both correct and usable. Avoid treating any one dashboard status as a substitute for reviewing the public result.

How should a team update languages when the source changes?

Record the new source revision, identify affected language variants, secure review and publish verified corrections with a clear change trail. For Prismic, use the real source record and the rendered target-language route as the two ends of the test. Record what the reader can do after receiving the information, then decide if the response is both correct and usable. Avoid treating any one dashboard status as a substitute for reviewing the public result.

What is a good first project?

Choose one short but complete task with a heading, body text, link, call to action, shared identifier and at least one deliberately missing translation case. For Prismic, use the real source record and the rendered target-language route as the two ends of the test. Record what the reader can do after receiving the information, then decide if the response is both correct and usable. Avoid treating any one dashboard status as a substitute for reviewing the public result.