CORE4
Global commercial core
EN → PT-BR / ES / ZH-HansMarket entry, setup, hiring, GTM, costs, sourcing, flagship tools. High cross-border intent and commercial value justify four supported languages.
INTERNATIONAL SEO GOVERNANCE
Language publication policy
English is the source layer. Localization is earned by demand, value and execution need.
E2M does not translate every new page by default. International search starts with a strong English source asset, then each additional language must have a reason to exist: target-language demand, commercial value, operating relevance or a real distribution need.
Core principle
English-first does not mean English-only.
English is the planning and source-of-record layer for international content. Once a localized edition is published, it is a first-class page: self-canonical, fully translated in its main content, locally edited and connected with hreflang only to variants that actually exist.
LANGUAGE MODES
Seven publication modes
The mode controls the default release sequence for new content. Existing high-quality translations are not removed simply because a future asset would now launch more selectively.
UX4
Product & trust UX
Keep four-language parityHomepage, product flows, privacy/security and navigation surfaces. Localization is driven by user experience, not keyword demand.
EN_PT
Brazil execution layer
EN → PT-BR; ES/ZH on signalTax/finance, city and other execution-heavy topics where Portuguese is operationally useful but every satellite does not need four versions.
HYPERLOCAL
São Paulo hyperlocal
EN → PT-BR; ES/ZH on signalNeighborhood, commute, office and housing micro-intelligence. Translate further only when the target market actually uses it.
CORRIDOR
Country corridor
EN + corridor language + PT-BR when usefulChina prioritizes ZH-Hans; Spain/Chile prioritize ES; Portugal prioritizes PT-BR. Do not translate a country corridor into unrelated languages by default.
INDUSTRY
Industry validation
EN first; PT-BR next; ES/ZH by demandIndustry pages launch in English, then localize when Search Console, pipeline, partner distribution or campaign demand justifies it.
GOVERNANCE
Governance / experimental
EN source; localize only public trust assetsCore public methodology may be localized. Internal governance, experimental or low-demand assets remain English until external usefulness is clear.
TRANSLATION GATE
The localization gate
A translation should pass a demand-and-maintenance gate, not a calendar deadline.
- Target-language search signal: queries, impressions, clicks or reliable market research indicate real demand.
- Commercial signal: the asset is close to a high-value E2M service, tool or qualified-lead path.
- Execution signal: local language materially improves the decision, implementation or handoff in Brazil.
- Distribution signal: a corridor, partner, campaign, customer or sales motion has a real audience in that language.
- Maintenance gate: no localized edition ships without an owner able to keep volatile facts, law and links current.
LOCALE ROLES
What each language is for
International source layer
Primary language for new research, cross-border search discovery, global executive audiences and the source version used to plan localization.
Brazil execution layer
Mandatory when the topic is operationally local, user-facing inside Brazil, or materially easier to implement with Brazilian teams/providers.
Spanish-speaking buyer layer
High priority for Latin American and Spanish decision-makers when commercial intent or corridor relevance exists.
China-origin opportunity layer
High priority for China → Brazil corridors, sourcing/manufacturing themes and proven Chinese-language demand; not a default for unrelated niches.
Technical rules
- Every published locale is self-canonical. English is the source layer, not the canonical target for localized pages.
- Use hreflang only for language variants that actually exist; partial sets are allowed when relationships are reciprocal.
- Never translate only navigation/template chrome while leaving the main body in English.
- Titles, descriptions, headings, examples, CTAs and internal links must be localized with the page — not mechanically copied.
- Do not auto-redirect users based on browser language. Keep explicit language switching available.
- A localized page must have the same evidence discipline as the English source; material facts may not change silently in translation.
How this applies to the current site
The September 2026 audit found 225 existing URL families already published in four languages. Those editions remain live because they have already been localized and quality-checked. The policy changes the default for future assets and refreshes: E2M will no longer assume that every new satellite deserves four simultaneous versions.
Google explicitly allows sites to publish only some language variants as long as existing hreflang relationships remain bidirectional; full four-language parity is not required for every URL family.
Google Search Central — localized versions →EDITORIAL GOVERNANCE
English-first does not mean English-only.
E2M does not translate every new page by default. International search starts with a strong English source asset, then each additional language must have a reason to exist: target-language demand, commercial value, operating relevance or a real distribution need.
See the editorial standards →