International SEO is the set of technical and content decisions that allow a site to rank across multiple countries and languages: choosing between ccTLD, subdomain or subfolder, implementing hreflang to signal each version to Google, and producing content adapted to the local market instead of literal translation. Mistakes in this architecture make versions compete with each other and waste authority built over years.
Your company decided to sell outside Brazil and someone suggested "translating the site." That phrase, said just like that, has already cost many operations years of traffic: the English version is born invisible, cannibalizes the Portuguese version or ends up orphaned on a subdomain with no authority.
The architecture decision comes before any translated text.
In this guide you will see how to choose the right structure, implement hreflang without breaking the versions and audit everything after launch.
What international SEO is
International SEO is the set of technical and content decisions that signals to Google and to AI systems which version of your site should appear for each audience, whether by language or by country. It involves choosing a structure (domain, subfolder or subdomain), hreflang markup, content adapted to the local market and monitoring of the versions. Without these signals, the search engine decides on its own, and it usually decides wrong.
Translating the site is the visible part of the work. The part that determines the result happens before: clearly stating, in the architecture and in the code, who should see what.
This is where the first distinction lives, the one that saves months of rework. Internationalization by language serves the same content to people who speak Portuguese, English or Spanish, regardless of where they are. Segmentation by country targets specific markets: Brazil and Portugal speak the same language, but have different currencies, taxes and search intents.
Confusing the two is the source of most problems that show up in international SEO projects. The classic symptom: the Spanish version for Chile ranking in Mexico, or the US English page competing with the UK page for the same term. Google sees two nearly identical pages fighting for the same position and demotes both.
Before hiring a translator or registering a domain, there is only one right question: do you want to speak to a language or sell to a country? The answer changes the entire structure, as you will see next.
Domain, subdomain or subfolder for each language
This is the most expensive decision to reverse later. Migrating an international structure involves mass redirects and months of restabilization, so it pays to get it right the first time.
ccTLD (site.com.br, site.es)
The strongest geographic signal there is. Google understands that site.es is for Spain without you configuring anything. The price: each domain starts from zero in authority and requires its own link building. It only pays off when there is a real local operation, with a team, revenue and a strategy per country.
Subdomain (en.site.com)
The middle ground that rarely pays off. Google tends to treat a subdomain as a separate property, so the main domain's authority does not flow through completely. You pay the management cost without reaping the ccTLD benefit.
Subfolder (site.com/en/)
Every version inherits the root domain's authority. A backlink earned in Portuguese strengthens the English and Spanish pages. Centralized maintenance, one CMS, one certificate, one monitoring setup.
How to decide with the team you have
Lean team and 3 languages: subfolder, almost always. That was the structure we adopted in the CLM Controller project, with the .com serving English, Spanish and Chinese and 2,013 redirects mapped during migration. ccTLD is for those with dedicated operations and budget per country.
How to implement hreflang without breaking the three versions
Hreflang is the tag that tells Google which URL to serve for each language. The syntax is simple; what breaks is the logic around it.
Anatomy of the tag in a 3-language scenario
``html <link rel="alternate" hreflang="pt-BR" href="https://site.com/" /> <link rel="alternate" hreflang="en" href="https://site.com/en/" /> <link rel="alternate" hreflang="es" href="https://site.com/es/" /> <link rel="alternate" hreflang="x-default" href="https://site.com/en/" /> ``
Language follows ISO 639-1, region follows ISO 3166-1 Alpha 2. A detail that trips up many people: "en-UK" does not exist, the correct code is "en-GB". The x-default defines the fallback for visitors who do not match any declared language.
Two rules are non-negotiable. Reciprocity: each version points to all the others, and if the English page does not return the link, Google discards the entire set. Self-reference: each page includes itself in the list.
Where to declare it: HTML head, XML sitemap or HTTP header. Choose only one method; duplicating creates conflicting signals.
Mistakes that bring the implementation down
- Hreflang pointing to a URL with noindex or a redirect
- Crossed canonical: the Spanish version canonicalizing to the Portuguese one nullifies the entire markup
- Automatic redirection by IP, which prevents Googlebot from seeing the other versions
In CLM Controller's international structure, the complete hreflang across English, Spanish and Chinese was validated along with the 2,013 mapped redirects before going live.
Content, translation and the structure that supports 3 languages
The right structure with auto-translated content delivers little. Google does not penalize translation itself; it penalizes text generated without review that fails to answer the local search. And local search is different from Brazilian search.
Keyword research per market
Someone searching for "contabilidade para multinacionais" in Brazil searches for "accounting outsourcing" in the US, with its own volume, competition and intent. Translating the keyword word for word usually targets a term nobody types. Each market requires native research before writing a single line.
This also defines what to translate. A service page that sells in the target market deserves a full version. A post about Brazilian legislation makes no sense in Chinese. In CLM Controller's international SEO project, 20 pages were ported to English, Spanish and Chinese: the ones that support the commercial operation, not the entire site.
Local signals beyond the text
Currency, date format, phone number with country code, social proof from the right market. An American reading a testimonial from a company in Contagem does not see themselves in it.
One detail that has gained weight: ChatGPT, Gemini and Perplexity cite sources by the language of the conversation. Fluent English content becomes a citation candidate in English prompts. Clunky translation does not.
How to audit and monitor the versions after launch
Publishing the three versions is half the work. The other half is knowing, every week, whether Google is serving the right URL to each country.
Search Console per property and targeting report
Create a URL property for each folder (/en/, /es/) in addition to the domain property. That way you compare impressions and clicks by language without mixing data. In GA4, a page path filter solves the same problem.
Cannibalization signal: the Portuguese version showing up in US searches, or the CTR of one version dropping while another rises for the same query. This usually indicates hreflang being ignored or not reciprocal.
Tools to validate hreflang at scale
Screaming Frog and Ahrefs flag tags without return links, invalid language codes and canonical conflicts across all pages at once. Run them after every deploy, not just at launch. In CLM Controller's structure, 2,013 redirects were mapped and hreflang was complete before going live, and continuous auditing is what keeps it standing.
30-minute diagnostic checklist
- Is each version indexed? (site:yourdomain.com/en/)
- Is hreflang reciprocal on the main pages?
- Is the canonical pointing to its own version?
- Do impressions by country match the expected language?
If any item fails, the problem is structural and warrants a full international SEO diagnosis, with no obligation. Talk to an Expert.
Decide the structure before translating the first page
If you got this far feeling that your company's English site "exists but does not show up," now the problem has a name: lack of signal. Ambiguous structure, broken hreflang or content translated without local intent make Google serve the wrong URL, and no media budget fixes that.
Three takeaways from this guide:
- Structure is the most expensive decision to reverse. A subfolder inherits authority and simplifies management; a ccTLD gives a strong geographic signal but starts from zero. Choose before producing, not after.
- Hreflang only works when complete. Every version references all the others, including itself. One missing tag brings down the whole set.
- Literal translation does not compete. Each market searches with its own terms, volume and intent. Native content beats auto-translated text.
The practical next step: list the pages that generate revenue today, define the URL structure for the versions and map the redirects before publishing anything. That groundwork is what supported the CLM Controller international project, with 2,013 redirects mapped and complete hreflang in English, Spanish and Chinese. If you want to understand the process in detail, the international SEO page shows how we run each stage.
And if your scenario is already mapped out and you just need to validate the decisions, Talk to an Expert and get a diagnosis of your case, with no obligation.
Expanding to another country is not translating a site. It is building the right answer for each market.
Frequently asked questions
What is the best structure for a multilingual site?
For most B2B companies, a subfolder on the main domain (site.com/en/, site.com/es/) is the safest choice. It inherits the authority the domain has already built and concentrates link building in one place. A ccTLD (site.es, site.mx) makes sense when there is a physical operation and a sales team in the country, because each new domain starts from zero in authority.
What is hreflang and what is it for?
Hreflang is an HTML tag that tells Google which URL to serve for each language or country. It prevents the Spanish version from appearing to someone searching in Portuguese, for example. The tag must be reciprocal: if the English page points to the Spanish version, the Spanish version needs to point back, otherwise Google ignores the entire markup.
Can I translate my site with AI or Google Translate?
You can use AI as a starting point, but publishing machine translation without review by a native speaker delivers little. The problem is rarely penalization, it is irrelevance: the translated text does not use the terms the local audience actually searches for. "Contabilidade para multinacionais" in Brazil becomes "accounting outsourcing" in the US, with different volume and intent. Adapt the keyword research for each market, not just the text.
Do I need a server or hosting in the target country?
It is not required. Google uses hreflang, ccTLD, content language and Search Console configuration as its main geographic signals. Server location carries little weight today, especially with a CDN distributing the content. It is worth investing more in content adapted to the market and correct technical markup than in local infrastructure.
How long does it take to rank in another country?
It depends on the chosen structure and local competition. Subfolders on a domain with authority tend to index and gain traction within weeks, while a new ccTLD can take 6 to 12 months to compete. As a real reference: in the CLM Controller project, the international structure in English, Spanish and Chinese required 2,013 mapped redirects and complete hreflang before going live, and that upfront work is what shortens stabilization.
How do I know if Google is showing the right version of my site in each country?
Create a URL property in Search Console for each language folder, in addition to the domain property. Compare impressions and clicks by country and check whether English queries are leading to /en/ and not to the Portuguese homepage. The international targeting report also flags hreflang errors, such as tags without a reciprocal return.
Does international SEO also work for showing up in AI systems?
Yes, and the logic is similar. ChatGPT, Gemini and Perplexity answer in the language of the question and cite sources in that language. If your company only has content in Portuguese, it does not exist in the answers generated for searches in English or Spanish. Well-structured native versions, with hreflang and adapted content, feed both Google and the AI models that consult the web.
