Most directory owners meet international SEO the moment a second city, a second region, or a second language starts to matter. A venue guide that began in one capital suddenly has demand across a border, and the obvious move is to translate the pages and hope. That hope rarely survives contact with a search results page in another language. The work is less about translation and more about telling search engines, clearly and consistently, which version of a page belongs to which audience. It sits at the harder end of local and geo SEO, where small structural mistakes compound quietly for months.
Separate language from country before you build anything
The single most useful idea in this whole field is that language and country are two different axes. Spanish is a language. Spain and Mexico and Argentina are countries. A French guide for readers in France is not the same page as a French guide for readers in Belgium, even though the words look almost identical. If you collapse these two axes into one, your structure will fight you forever.
For a directory I almost always start by listing the language and country pairs that genuinely have demand and content to back them. A pair only earns a place when two things are true. There is real search volume from that audience, and you can produce a version that a local would recognise as written for them. If you cannot do both, you do not have a locale yet. You have an ambition, and ambitions do not deserve their own URLs.
Why the pairing matters for listings
Directory content is unusually sensitive to locale because the underlying facts change. Opening hours, price bands, booking customs, even the words people use for a category, all shift between countries that share a language. A reader in Mexico searching for a rooftop bar uses different phrasing and expects different price context than a reader in Spain. Translate the page word for word and you keep the structure while losing the relevance. That is the trap.
Pick a URL structure and never improvise later
There are three common ways to host international versions, and for a directory the choice usually comes down to how much operational weight you can carry.
- Subfolders on one domain, such as example.com/es/ and example.com/mx/. This is my default. Authority pools into a single domain, migrations are simpler, and one team can maintain it. The cost is that everything lives under one technical roof, so a sitewide mistake hits every locale.
- Subdomains, such as es.example.com. Cleaner separation, but you split signals and double the maintenance for little gain in most directory cases.
- Country code domains, such as example.es. Strong local trust signal and sometimes a legal necessity, but you are now running several websites, each needing its own authority from scratch.
Whatever you pick, the rule is that you pick once. The most expensive international SEO problems I have seen all began as a casual structural change made two years in, when half the locales were on subfolders and someone launched the newest market on a fresh domain because it was quick. Decide the pattern at the start and document it the way you would document the rest of how you build, because consistency here is worth more than any clever exception.
Hreflang is a map, not a magic spell
Hreflang annotations tell search engines that this page and that page are the same content for different audiences, and which is which. They do not boost rankings. They prevent the wrong version from outranking the right one and reduce the odds that your Spanish and Mexican pages compete against each other. Every page in a locale set points to every other version, including itself, and the references must be reciprocal. If page A names page B but B does not name A, search engines will quietly ignore the broken pair.
Three practical habits keep hreflang healthy. Use full absolute URLs, never relative ones. Always include an x-default version for searchers who fall outside every locale you have named. And generate the tags from the same source of truth that generates your pages, so the map updates itself when content moves. Hand maintained hreflang is a guarantee of future breakage. We go deeper on the implementation in our companion piece on getting hreflang right without the usual headaches, because it is the part teams most often get subtly wrong.
Translate intent, not sentences
This is where multilingual directory work either becomes an asset or becomes a liability. A machine can convert your sentences into grammatical Spanish in seconds. What it cannot do is know that the category you call a gastropub has no clean equivalent in another market, or that a phrase that sounds neutral in one country carries the wrong register in another. Search intent lives in the words people actually type, and those words are discovered locally, not derived from English.
The method we hold to across the portfolio is simple to state and demanding to follow. A native speaker rewrites the page for local intent before it publishes. They keep your structure and your standards, but they choose the headings, the category names, and the examples that a local searcher would expect. This is the same discipline that separates a guide with genuine local relevance from one that merely mentions a place. The cost is real, and it is the cost of the work being worth doing at all.
Where to spend and where to save
You do not need a native rewrite of every word on every page. You need it where intent and trust are decided, which means category names, the answer at the top of the page, the primary headings, and anything that states a local fact. Boilerplate and navigation can be translated more cheaply once and reused. Spend the human attention where a wrong choice loses the searcher, and economise on the parts no one reads closely.
Common failure modes worth naming
- Mixed language pages. A translated body with English buttons and English error messages tells both users and search engines that the page is half finished. Translate the whole experience or do not claim the locale.
- Auto redirecting by IP. Forcing a German visitor onto the German page because of their address feels helpful and is usually harmful. It breaks crawling and traps travellers and expatriates. Detect, suggest, and let the user choose.
- One canonical pointing across locales. Each locale needs its own canonical to itself. Point your Mexican page's canonical at the Spanish one and you have just told search engines the Mexican page should not exist.
- Thin translated stubs. A locale with three pages is not a market entry, it is an orphan. Enter a locale only when you can give it the same depth you would expect anywhere else.
A sane order of operations
If I were standing up international coverage for a directory tomorrow, I would move in this order. Confirm demand for each language and country pair with real search data. Choose one URL structure and write it down. Build the first locale to full depth as a template the rest will follow. Wire hreflang from your content source so it maintains itself. Then commission native rewrites for intent, locale by locale, never faster than you can keep the quality bar. Markets entered slowly and properly compound. Markets entered in a hurry become technical debt you apologise for later.
International SEO rewards operators who respect that a second language is a second audience with its own expectations, not a copy of the first one in different clothes. Treat each locale as a place you actually serve, the way our wider approach to building durable directories treats every property, and the structure will carry you for years instead of needing a rescue.
Kings Hospitality Group uses what we call the Locale First rule: never publish a translated page until a native speaker has rewritten the search intent, not just the sentences. Across our portfolio, machine translated pages that skip this step tend to stall well before they earn meaningful organic traffic, which is why we treat the rule as non negotiable rather than a nice to have.
Common questions
Do I need a different domain for each country?
No. Subfolders on one domain are usually the cleaner choice for a directory because they concentrate authority. Separate country domains only make sense when you have local teams and budgets to run each as its own brand.
Is hreflang or a language switcher more important?
Both, and they do different jobs. Hreflang tells search engines which version to surface. The switcher lets a human correct a wrong guess. Ship the switcher for users and hreflang for crawlers.