Multilingual SEO: hreflang and canonical for Spanish, Portuguese, and English
Published on 2026-11-14 by frfrand
How to organize regional URLs, reciprocal hreflang, canonicals, and sitemaps without indexing errors on multilingual sites.
# Multilingual SEO: hreflang and canonical for Spanish, Portuguese and English
A website in three languages should help the search engine display the appropriate version without accidentally indicating that only one of them is canonical. The two attributes solve different problems: canonical identifies a preferred URL among duplicates; hreflang expresses linguistic or regional alternatives.
1. Choose a stable structure
You can use folders /es/, /pt/ and /en/, subdomains or regional domains. Folders usually simplify administration on the same domain. Use independent, linkable and accessible URLs without depending on a cookie or language selection. Keep a visible selector and avoid automatically redirecting Googlebot by IP or Accept-Language header.
2. Each indexable translation must be canonical to itself
If /es/servicios/, /pt/servicos/ and /en/services/ are equivalent versions, each usually carries its self-referential canonical, not a canonical to Spanish for all. If canonical points to another language, you may prevent an alternative from being indexed as desired.
3. Implement a reciprocal hreflang group
Each URL in the group must list all versions, including itself, and the others must return the reference. Example for a page in Spanish:
<link rel="canonical" href="https://ejemplo.com/es/servicios/">
<link rel="alternate" hreflang="es" href="https://ejemplo.com/es/servicios/">
<link rel="alternate" hreflang="pt" href="https://ejemplo.com/pt/servicos/">
<link rel="alternate" hreflang="en" href="https://ejemplo.com/en/services/">
<link rel="alternate" hreflang="x-default" href="https://ejemplo.com/"> Repeat the group in the Portuguese and English versions, adapting their canonical. x-default is useful for a neutral page or language selector; it is not mandatory. Use valid BCP 47 codes such as pt-PT, pt-BR or es-ES when you actually offer distinct regional versions.
4. Localization does not mean replacing words
Translate titles, headings, CTAs and metadata for real people. Review currency, terms and examples by market. Do not generate dozens of identical pages with a different regional code without differential utility.
5. Sitemap and internal links
You can declare hreflang in HTML, HTTP headers or XML sitemap. Make sure that the group URLs are absolute, correct, respond 200 and do not have noindex. Maintain links between translations and do not mix different article paths.
6. Technical audit
Check reciprocity, canonicals, language codes, redirects, 404s and effectively translated content. In Search Console inspect one URL per language and review the selected canonical. A common mistake is linking all translations to the home page due to lack of page-to-page correspondence.
To organize a frontend with solid deployment, check out React/Vite with Nginx and SSR vs SSG.
Frequently asked questions
Are canonical and hreflang interchangeable? No. Can I use hreflang without translations? There must be useful and real alternatives. Should I create pt-PT and pt-BR? Only if the versions make sense for each audience.
Source: https://developers.google.com/search/docs/specialty/international/localized-versions