Direct answer: if the same brand, core offer, and operating team serve the United States, Brazil, and Latin America, start with one global domain and localized subdirectories. Give every version a self-canonical, reciprocal hreflang, x-default, a visible selector, and local commercial evidence. Choose subdomains when platforms, teams, security boundaries, or site names truly need separation. Use country domains only when distinct operations, brands, catalogs, regulation, and budget justify complete sites with their own authority. Avoid language parameters and silent IP redirects.
There is no special architecture for AI citation. Google documents the trade-offs among ccTLDs, subdomains, and subdirectories; OpenAI documents OAI-SearchBot access. Both require public, crawlable, coherent URLs. The choice changes CMS cost, content operations, analytics, authority, governance, and migration risk, so it belongs to the CMO, technology leadership, and regional owners—not only an SEO checklist.
Use a six-axis Market Architecture Decision
- Entity and brand — is this the same company and public name in every market?
- Offer — do services, catalog, price, availability, and value proposition materially differ?
- Local obligation — do contracts, data, tax, consent, support, or claims require a separate operation?
- Evidence — does each market have its own examples, experts, addresses, currency, proof, and sources?
- Operations — who publishes, reviews, repairs, measures, and owns each version?
- Migration economics — what will infrastructure, authority fragmentation, redirects, analytics, content, and continuing maintenance cost?
When all six axes favor sharing, subdirectories preserve one platform and operation. When two or more require durable technical or editorial isolation, compare subdomains. When the business behaves as distinct national companies with local accountability, a ccTLD can be defensible. The matrix does not replace technical testing or legal analysis; it keeps a visual preference from becoming an expensive architecture.
Compare three architectures before funding migration
- Subdirectories — example.com/pt/ and example.com/es/. Lower maintenance and shared authority, but strong governance is needed so local markets do not receive late translations.
- Subdomains — br.example.com and latam.example.com. Easier stack and owner separation and eligible for separate site names; more configuration, observability, and inconsistency risk.
- Country domains — example.com.br and example.mx. Clear country signal and autonomy, with infrastructure, content, links, analytics, security, and operations required for every property.
- Parameters — example.com?lang=pt. Do not use them as the primary architecture; they create fragile segmentation and unstable duplicate paths.
For a midsize company using U.S. English, Brazilian Portuguese, and regional Spanish, a practical base may be /, /pt, and /es. Use en-US, pt-BR, and es when those pages address those audiences. Google does not support es-419 in hreflang. If Mexico, Colombia, or Chile has a materially different offer, publish distinct pages and use valid codes such as es-MX, es-CO, or es-CL. Do not create country variants merely to replace a few words.
Do not confuse language with market
Translation preserves meaning; localization changes the offer, examples, currency, proof, CTA, availability, and accountable team. One Spanish page can serve several countries when service and terms are regional. Split by country when the buying decision changes. Every variant needs substantive content, a self-canonical, and reciprocal alternates; canonicalizing them all to English removes the signal localization was meant to create.
Provide a language and region selector and preserve user choice. Google advises against IP-only adaptation because geolocation is unreliable and crawlers may not discover every variation. Automatic redirects can also hide the right option from travelers, global teams, and buyers who prefer another language.
Implement in eight weeks
- Weeks 1–2 — inventory URLs, rankings, links, leads, languages, markets, CMSs, profiles, domains, and owners; preserve a baseline.
- Week 3 — score the six axes, choose an architecture, and define the URL map, x-default, canonicals, hreflang, and selector rules.
- Week 4 — write contracts for content, offers, metadata, structured data, images, forms, and CRM handoff by market.
- Weeks 5–6 — build templates and priority pages; configure redirects, sitemaps, robots, CDN, analytics, and events without publishing everything at once.
- Week 7 — validate reciprocity, codes, rendered HTML, links, status, canonicals, forms, consent, OAI-SearchBot, and fallbacks.
- Week 8 — release in batches, monitor errors, compare the baseline, and retain rollback plus the redirect map.
Set technical and commercial acceptance criteria
- Every priority URL answers a market-specific intent instead of changing only navigation.
- Canonical points to the same locale variant; hreflang lists every version and provides return links.
- x-default leads to a useful fallback or global version, never an unchosen redirect.
- Organization, WebSite, Article, or Service markup matches visible content and the correct entity.
- Every new host permits approved crawlers through robots, CDN, and firewall and keeps separate logs.
- Analytics and CRM preserve URL, language, selected market, source, consent, lead, opportunity, and revenue as separate fields.
One important constraint: Google supports one site name per domain or subdomain, not per subdirectory. This does not make subdirectories inferior for ranking. It means /pt and /es cannot carry independent site names. If the business needs different public brands by market, that limitation belongs in the decision alongside legal evidence, user experience, and operating cost.
Budget the cost that continues after launch
Investment rises with market count, offer divergence, CMS count, migration, redirects, page volume, inherited authority, local content, legal review, integrations, consent, forms, media, hreflang maintenance, monitoring, and support. Subdirectories reduce infrastructure but require strong central governance. Subdomains protect autonomy but create more surfaces. ccTLDs reinforce separation, but every country must justify a complete operation.
Measure discovery, quality, and revenue separately
Track valid URLs by market, indexed coverage, canonical and hreflang errors, crawl time, local impressions and clicks, observed AI questions, cited domain, referrals, engaged session, CTA, qualified lead, opportunity, and mature revenue. ChatGPT referrals can be observed when present; missing referral data does not prove no influence. Separate collection freshness, Google reporting delay, recrawl windows, and concurrent changes.
Resolve entity ambiguity through https://makinai.co/insights/en/ai-search-confuses-company-namesake-entity-disambiguation, structure the first discovery cycle with https://makinai.co/insights/en/company-ranks-search-absent-ai-answers-what-implement-first, and localize campaign operations through https://makinai.co/insights/en/ai-campaign-localization-us-brazil-latin-america. If the company must choose between a global site and regional properties, bring MAKINAI at https://makinai.co/services/en/data-content-intelligence-systems the current domain map, three offers, target markets, owners, and conversion data. We can scope the decision, migration, and smallest publishable batch.