There is no universally best architecture for international SEO. A subdirectory can make a centralized offer easier to manage; a country domain can suit an independent regional operation. The right choice is the structure that supports useful content, a clear local experience and consistent technical implementation.
Before debating /mx/ versus mx.example.com, define what changes between markets: language, catalogue, currency, terms, support and delivery capability. Creating another URL without resolving those differences does not create an international strategy.
Separate language, country and business operations
A Spanish version can serve several countries. A version for Mexico may need different information even when it shares a language with Colombia. This distinction determines whether you need translation, regional localization or a separate operation.
Google’s multiregional site guidance compares available structures. A country domain generally communicates a clear geographic association; a generic domain can organize languages or countries through folders or subdomains. This does not establish a universal ranking advantage.
- Language: the language used in content and customer support.
- Market: where people can actually purchase the offer.
- Entity: who bills the customer and fulfils the terms.
- Operations: who updates, reviews and maintains each version.
If the business cannot yet serve a country, avoid presenting it as confirmed coverage. A general page in the appropriate language can be more useful and accurate than numerous regional pages without a distinct offer.
Compare architectures using operational criteria
| Option | When it may fit | Cost or risk to examine |
|---|---|---|
| Subdirectory: example.com/mx/ | A centralized platform and team coordinating versions | Routing, permissions and global changes affecting markets |
| Subdomain: mx.example.com | Regional platforms or releases requiring separation | Repeated crawling, measurement and maintenance configuration |
| Country domain: example.mx | A local brand and operation able to sustain an independent presence | Domain registration, governance and ongoing site upkeep |
This is a decision tool, not a traffic forecast. Review the project’s history and dependencies: existing links, established URLs, teams, infrastructure and legal processes. Do not assume a subdomain automatically isolates every configuration or a folder eliminates duplication.
Know when to preserve a working structure
Migrating only because someone says “Google prefers folders” is not a sufficient business case. If the existing structure supports clear, crawlable and measurable versions, identify the specific improvement a move would produce. Migration takes work and can cause fluctuations while new URLs are processed.
Establish whether architecture is actually responsible for the observed problem. Poorly translated generic offers, broken language links or forms that reject international phone numbers will not be fixed by changing the hostname. Your SEO strategy must connect site organization with sales and delivery.
Two hypothetical decision scenarios
A service business with centralized remote delivery
Imagine a firm serving Spanish and English speakers through one team. Services and delivery are the same, but examples, schedules and wording need adaptation. Language subdirectories could simplify publishing, internal links and maintenance. Country pages would only be added when a real need and relevant local information justified them.
A retailer with regional catalogues and teams
Now imagine a store with different stock, pricing and delivery terms in each country. If regional teams use separate platforms, subdomains or country domains may suit that independence. The decision still requires a plan for products, languages, measurement and equivalent pages. These scenarios are illustrative, not client results or ranking guarantees.
Align hreflang and canonical signals with the decision
Whatever structure you choose, connect equivalents with consistent hreflang annotations. A Mexican product page should point to the corresponding product versions, not an arbitrary regional home page. Use valid codes and reciprocal relationships.
Do not canonicalize every translation to a single language. Each version intended to remain independent needs compatible signals. For duplicate or very similar content in the same language, settle the consolidation strategy before completing international relationships. Our canonical guide separates these tasks.
Provide an accessible language or country selector. Do not rely solely on forced redirects based on IP address or browser language: these can prevent people and crawlers from reaching other versions. A suggestion visitors can change usually provides more control than an obligatory transfer.
Budget for maintenance before multiplying versions
Assign an owner and review schedule to each market’s pricing, terms, commercial pages and editorial content. Define how security updates, template changes and link corrections propagate. Include analytics, consent, forms and mobile testing in the operating plan as appropriate to the business.
Do not automatically translate the entire inventory without asking what the audience needs. A guide about an exclusively Colombian procedure may not need a Mexican version. Maintaining irrelevant pages consumes time that could improve offers with verified demand and delivery capability.
Prepare a decision the whole team can review
Before choosing a structure, bring business, editorial and technical owners around the same inventory. Document served markets, available languages and genuine differences in the offer. Add a status for each resource: existing, needs localization or should not yet be published. This prevents designing an architecture for an expansion that has no delivery capability.
Evaluate each option qualitatively for maintenance, platform independence, user experience and migration cost. Do not turn the matrix into a ranking formula; its purpose is to expose the reasoning. A folder may be easy for one team and difficult for another whose platform cannot support the required rules.
Include change approval and incident ownership for every market. If nobody can correct regional prices or terms, opening a country domain adds an unmanaged surface. The structure should fit present operating capacity and a credible expansion plan, not merely the presentation that looks most attractive.
Ask questions that can change the decision
- Are catalogues equivalent or do countries offer different products?
- Can teams share publishing workflows and templates?
- Is there a commercial reason for a separate regional brand or entity?
- Can the platform maintain stable URLs and relationships between versions?
- Can the business measure journeys and respond to enquiries from each market?
- Who will update pages when the offer changes?
Unknown answers should become explicit tasks. If the team does not yet know what information a new audience requires, research that offer and local needs before creating every category. Choosing a domain cannot resolve commercial uncertainty.
Do not confuse business signals with architectural preferences
A competitor with a country domain having stronger visibility does not establish that its extension caused the advantage. Its offer may be more relevant, resources more useful, brand better known or publishing history different. Compare intent and answer quality before attributing the difference to URL format.
Likewise, low traffic in an international folder does not prove folders fail. Check discovery, relevance to market queries and whether visitors can purchase the offer. If a literal translation uses terms the audience does not use, research and localization may be responsible. None of the three architectures replaces that work.
Do not assume every country needs an identical inventory. A regulated service, delivery method or product may be unavailable elsewhere. Publishing a page solely to maintain visual symmetry can create inaccurate promises and more maintenance without meeting a real need.
Test complete journeys before approving the structure
Select three journeys: discovering a service from search, switching markets on an interior page and requesting information. Ask someone unfamiliar with the structure to complete them. Observe whether they understand where they are, which version they use and what happens when the form is submitted. Record obstacles without leading them to the expected answer.
Test a directly shared interior address as well as entry from the home page. A selector may work on the main page while losing equivalent relationships inside the catalogue. Check that navigation does not silently switch markets and relevant terms remain visible through conversion.
For centralized operations, verify that regional forms reach the correct team. For independent operations, ensure visitors understand which business they are contacting. These are not special ranking factors; they test whether architecture performs the job that justified creating it.
Use a pilot when uncertainty remains
An expansion beginning with one service does not require an immediate whole-site migration. Prepare a limited but complete experience to test publishing, links, customer handling and measurement. Define what makes the pilot representative. Avoid choosing an empty page merely because it is quick to build.
In a hypothetical example, a Colombian company considers serving Mexico through the same team. Before separating domains, it prepares a localized offer, verifies delivery and records commercial questions. Those observations may indicate that a general version is sufficient or reveal differences supporting a regional section. This is not a client result or a universal demand threshold.
The pilot should also test upkeep. Simulate a price update, service withdrawal and new translation. If the process requires editing too many disconnected places, simplify it before expanding. A sustainable architecture lets the team preserve consistency after launch.
Define acceptance and continuity criteria
Before approval, confirm that every version has a documented purpose, owner and complete journey. Sample each template for HTTP responses, language links, canonicals, hreflang and sitemaps. Review shared resources and global rules that might affect other markets when one version changes.
Plan how queries and enquiries will be observed by market without assuming all tools attribute them identically. Record launch and subsequent change dates. If the section does not receive expected searches, investigate editorial coverage, accessibility and demand before blaming the selected structure.
Keep a clear way to expand or reduce scope. Withdrawing a market should not leave active links and forms promising an unavailable service. An orderly inventory lets future business decisions become concrete, testable changes instead of another improvised URL reorganization.
Account for ownership beyond the first launch
Consider what happens when a regional employee leaves, an agency contract ends or the commerce platform changes. Ensure domain renewals, redirects, content access and analytics remain under the business’s control. A technically elegant structure can still be difficult to operate if crucial configuration is inaccessible to the team responsible for maintaining it.
Document these dependencies alongside the decision matrix. This allows future reviewers to distinguish an architectural limitation from a missing operating process. It also makes the chosen trade-off explicit: the business knows which independence it is gaining and which coordination work it must continue to fund.
If a migration is justified, map every URL
- Document each current URL and its equivalent destination; avoid redirecting everything to a home page.
- Test the new site and forms before the move.
- Coordinate internal links, canonicals, hreflang and sitemap updates.
- Use permanent redirects for genuine relocations.
- Monitor responses, crawler access and the performance of old and new pages.
Google describes this workflow in its site migration documentation. Keep a baseline by country and page type. Avoid unnecessarily combining a domain move, redesign and full content rewrite: isolating a failure becomes harder. The chosen architecture should make the business maintainable as well as organize its URLs.
Frequently asked questions
Do subdirectories always rank better than subdomains?
There is no universal rule. Compare technical requirements, content, teams and maintenance. The decision should improve a specific experience rather than rely only on a presumed Google preference.
Does a country domain replace hreflang?
No. Geographic structure and relationships between versions have different roles. If equivalent pages serve several languages or regions, review their annotations and consolidation signals.
Does every Spanish-speaking country need a page?
Only when a real need and offer justify it. A general Spanish version can serve several markets; local pages should contribute useful, verifiable information.
Should I migrate an existing architecture?
When a clear operational or experience improvement justifies the cost and risk. First document URLs, equivalents, metrics and a redirect and validation plan.