A language switcher at the top does not make a multilingual site. You need per-language content models, coherent URLs, translated metadata and a clear link between versions of the same page.
[IMAGEM 1 AQUI]
Language is not only swapping the menu
Define the canonical locale (e.g. pt-BR) and how en/es/it appear in routes. Each locale needs its own title, summary, body and slug — not one mixed text block.
Routes and content per locale
Assisted translation in the admin speeds things up, but human review locks quality and tone. The editorial flow should require all four languages when that is the portal rule.
[IMAGEM 2 AQUI]
Assisted translation without skipping review
hreflang, canonical and per-language sitemaps prevent poorly interpreted duplicates. That is the platform's job.
Signals for search engines
If multilingual is a day-one requirement, choose core — not a workaround. Context in Ready CMS by consultation.
[IMAGEM 3 AQUI]
Conclusion
undefined