A Spanish company that starts selling in Portugal or France too usually gets the first step right: it translates the site. The problem shows up afterwards, when Google does not know whether to show a user in Lisbon the Spanish version or the Portuguese one, both pages end up competing with each other for the same searches, and on top of that Google may interpret the translated content as a copy of the original unless told otherwise. Translating is the easy part; structuring international SEO properly is where most businesses waste time, traffic and, sometimes, rankings they had already earned.
The first decision: ccTLD, subdomain or subfolder?
There are three main ways to organise content across languages or countries, and each carries different advantages and costs:
- Country-code domain (ccTLD), like yourcompany.fr or yourcompany.pt. It is the strongest possible signal that this content is meant for that specific country, but also the most expensive and slowest to maintain: each domain needs to build its own authority from scratch, its own technical SEO, and in practice it almost becomes running several separate websites.
- Subdomain, like fr.yourcompany.com. Google largely treats it as a site independent from the main domain, with advantages and drawbacks similar to a ccTLD but with lower initial technical cost.
- Subfolder, like yourcompany.com/fr/. It is the most common choice for small and medium businesses: all the authority and trust the main domain has already built is shared with the subfolders, technical maintenance is much simpler, and it still allows clear segmentation by language or country.
For the vast majority of SMEs starting to sell in another country, the subfolder is the most sensible choice: it leverages the authority already built and avoids the complexity (and cost) of managing separate domains or subdomains.
Hreflang: the tag that stops versions from competing with each other
The hreflang tag tells Google, in each page's code, which other language or country versions exist of that same page, so it shows the right one based on the searcher's location and language. Without it, Google may interpret the different versions as duplicate content, or simply choose to always show the same version to everyone, leaving the rest out of the game. The tag sits in each page's header and points to every other version, including itself, something that is frequently forgotten and causes most of the errors in this area.
The most common mistake: badly implemented hreflang, which does more harm than not having it
A hreflang with errors (a version that does not point back to the one that referenced it, a mistyped language or country code, references to pages that no longer exist) can confuse Google more than not using the tag at all, because Google may ignore the entire tag if it detects too many inconsistencies. It is worth checking it with a crawling tool after any major change to the language structure, not just trusting that it was implemented correctly once and leaving it alone forever.
It is not just translating: it is adapting
A word-for-word translation, without adapting prices to local currency, without adjusting cultural examples, and without translating the keywords too (because people in France do not necessarily search using the literal translation of the term a Spanish speaker uses), rarely works well. Real localisation means researching what keywords each country's audience actually uses, which are often not the exact translation of the ones that work in Spain. A typical example: "diseño web" in Spanish and "conception de site web" in French are not automatic translations of one another when you check with the right keyword tool, and that nuance can be the difference between ranking or not.
Duplicate content across languages: why it is not a problem (if properly flagged)
Many businesses worry that having the "same" content in several languages will get penalised for duplication. That is not the case, as long as hreflang is properly implemented: Google fully understands that the same content in Spanish and French is not "duplicate content" in the negative sense of the term, it is content localised for different audiences. The real duplication problem shows up when two pages are in the same language but repeat the content almost word for word with no tag explaining why.
Management and upkeep: the cost nobody calculates at the start
Every new language is not a project that gets finished, it is a new website that needs maintaining: updating prices, news, offers and blog content in each version separately (or with a well-organised translation process) is ongoing work that grows with every language added. Before launching a third or fourth language version, it is worth genuinely calculating whether there is enough business in that market to sustain that upkeep, because an abandoned language version, with outdated content, does more damage to brand image than not having it at all.
A common case: the online shop that "translated" prices without adapting them
A Spanish online shop selling home decor products started selling in France too, using a /fr/ subfolder. The team translated the text well, but only converted prices from euros to euros (France also uses the euro, so there was no currency conversion to do) without reviewing shipping costs, which on the French site kept being calculated as if the order shipped from a Spanish warehouse with no customs involved, when in reality there was a different logistics cost for international shipping. The result was a cart abandonment rate much higher on the French version than the Spanish one, despite comparable traffic and rankings. The problem was not SEO, it was that localisation had been left half-finished: the language had been translated, but the full shopping experience had not been adapted to that specific market's expectations.
How to prioritise which country or language to tackle first
Before jumping into translating the whole site into a new language, it is worth validating demand with data that already exists: checking in Analytics how much traffic is already arriving spontaneously from that country (despite having no dedicated content), checking the search volume of the business's main keywords in that language, and assessing whether there is already the occasional sale from that market suggesting real demand waiting to be better served. Starting with the country showing the most prior signs of interest reduces the risk of investing in a language version nobody ends up using.
The role of a native speaker in the final review
Even with a well-done professional translation, it is worth having a native speaker of the target country, ideally someone close to the industry, review the final result before publishing. That review is not looking for grammar mistakes (a good translation should already have avoided those), it is looking for cultural and tonal nuances a translator with no industry knowledge might miss: phrasing that sounds forced, references that make no sense outside Spain, or a level of formality that does not match that market's expectations. It is a step that costs little time and avoids perception mistakes no translation tool, however good, can catch on its own.
Step by step: launching a second language version without hreflang errors
The technical process, applied for the first time, is best followed in this order: first, decide the structure (subfolder, in most SME cases) and create the URL hierarchy before translating anything, for example yourwebsite.com/fr/ mirroring the same structure as yourwebsite.com/. Second, translate and localise the content (not just the language, also prices, examples, local keywords) page by page, starting with the pages that get the most traffic in the original version. Third, implement the hreflang tag on every page, pointing to every existing version including itself; use an online hreflang generator to check the syntax before publishing, because a single mistyped character can invalidate the entire tag. Fourth, add both versions to the XML sitemap, to help Google discover them faster. Fifth, a week after publishing, use a crawling tool (or Search Console's own coverage report, on the property corresponding to that version) to confirm there are no hreflang errors or orphaned unlinked pages. This order avoids the most common mistake, which is translating first and thinking about the technical structure afterward, by which point dozens of pages are already published and reorganising the URL structure becomes far more costly.
International SEO versus creating an independent local brand
For businesses that grow substantially in a specific market, there is an alternative to the multilingual subfolder: creating a completely independent brand or website for that country, with its own domain, its own adapted visual identity and its own management team. This option makes sense when the target market is big enough to justify the cost of duplicating the operation, or when cultural or regulatory differences run so deep that a simple translation of the original site would never be enough (a heavily regulated industry with different rules in each country, say). For the vast majority of SMEs just wanting to start attracting customers in a neighbouring country, however, that full independence costs far more than it delivers, and the multilingual subfolder remains the most sensible option for validating the market before investing in a more complex structure.
Frequently asked questions
Do I need hreflang if my site is only in Spanish but I sell to several Spanish-speaking countries?
It depends on whether there are real content differences (prices, shipping, local terminology) between those countries. If the content is identical for all of them, a single Spanish version targeting "all Spanish-speaking countries" (using the es code without specifying a country) may be enough. If there are differences, it is worth segmenting by country with hreflang.
How long does it take Google to properly index a new language version?
Similarly to a brand new website, anywhere from several weeks to a few months for Google to crawl it, index it and start ranking it with some stability, though properly implemented hreflang from the start usually speeds up the process.
Can I use machine translation directly without human review?
It is not advisable for SEO- and conversion-oriented content: unreviewed machine translation often sounds unnatural, does not adapt keywords to each country's actual usage, and can come across as less trustworthy to readers, which directly affects conversion even if the ranking itself were fine.
What if my site only has one language but I still get traffic from other countries?
There is no technical problem at all: it is perfectly normal and Google handles it without difficulty. International SEO comes into play when you specifically want to actively target and rank in other markets, not when you simply get occasional visits from abroad.
Should I use the same domain or buy a new one for each country?
For most SMEs, the same domain with language subfolders is the most efficient option, unless the business in that specific country is going to reach a very large scale and operational independence, in which case a ccTLD can be justified.
Does the language switcher (the dropdown to change versions) affect SEO?
Indirectly yes, because it helps users (and crawlers) find all available versions. It should be visible and functional, and actually link to each version's URL, not rely solely on JavaScript to change the language without changing the URL.