Contents
- The reality of regionalised Spanish on Google
- Architecture: ccTLD, subdomain or subdirectory
- Hreflang: the part that breaks 80% of sites
- Localised vs translated content
- Local SEO per country (GBP, directories, currency)
- Multi-country regional tracker
- Case: SaaS expanding to 4 LATAM countries
- International expansion checklist
- FAQs
The reality of regionalised Spanish on Google
A Chilean searches «bencinera cerca». An Argentine searches «estación de servicio». A Mexican searches «gasolinera». A Spaniard searches «gasolinera». Same business, four different words. Google Chile returns local results that do not appear in Google Argentina. And your content optimised for «bencinera» is invisible in 3 of the 4 markets.
Chile (es-CL)
Local slang: bencinera, colectívo, palta, garzón. Formal Chilean vocabulary.
Argentina (es-AR)
Voseo, pesos, remises, boliches, subte, factura A.
Mexico (es-MX)
Refacciones, plática, camioneta, factura CFDI. Market 4x larger than Chile.
Colombia (es-CO)
Parqueadero, apartamento, DIAN, banano. Second LATAM market.
Peru (es-PE)
Chompa, jato, chela. RUC as tax identifier.
Spain (es-ES)
Use of «vosotros», euro, different VAT, peninsular terminology. Large but saturated market.
Antipattern: «universal Spanish» content
Many brands believe writing in «neutral Spanish» serves all LATAM. In reality it serves none: Chileans perceive it as foreign, Mexicans as strange, Argentines as «not speaking to me». Worse for SEO: does not rank in any country because it misses local specific keywords.
Architecture: ccTLD, subdomain or subdirectory
Separate ccTLDs
High cost- mybrand.cl / .ar / .mx
- Maximum local signal
- High maintenance cost
- Each ccTLD starts from 0 in authority
- Complex for SEO
Only if you have resources
.com subdirectories
Recommended- mybrand.com/cl/ /ar/ /mx/
- Shares domain authority
- Single hosting, single SSL cert
- Easier hreflang
- Scalable to 20+ countries
Best effort/benefit ratio
Subdomains
Intermediate- cl.mybrand.com / ar.mybrand.com
- Partial authority sharing
- More complex DNS config
- Google treats them almost as separate domains
- Useful if you need different hostings
Only specific cases
Semalt recommendation for LATAM expansion
Subdirectories on a .com domain (or maintain the local ccTLD with /ar/, /mx/ subdirectories). This is what companies like Cornershop, Betterfly and NotCo do. Single domain, correct hreflang, concentrated authority.
Hreflang: the part that breaks 80% of sites
Hreflang is the mechanism Google uses to know which version of a page to serve each user. Well done it is invisible and works. Poorly done it cannibalises your positions across all countries.
The 8 rules of correct hreflang
- Each page lists ALL its versions (including itself)
- Links are bidirectional (A points to B and B to A)
- Language-region code is valid ISO 639-1 + ISO 3166-1 (es-CL, not es-CH)
- x-default exists for fallback (ideally global .com/en/)
- Applied equally via <head>, HTTP header or sitemap.xml
- The hreflang URL exists (not 404) and returns 200
- Each version has its own canonical pointing to itself
- Real content is localised (not literal translation)
Valid vs common erroneous codes
Valid: es-CL, es-MX, es-AR, es-419 (LATAM generic), es-ES, es-CO, es-PE. Erroneous: es-LA (does not exist), es-LATAM (does not exist), es-lat (does not exist), esCL (missing hyphen), Spanish (use ISO code). Semalt Audit automatically detects invalid codes.
Semalt Hreflang Validator
Broken reciprocal detection
URL A declares alternate B but B does not declare A: association breaks. Semalt lists broken pairs with suggested fix.
Alternate URL verification
Every URL declared in hreflang is verified: exists, returns 200, has its own hreflang back.
Coverage per country
Report showing % of URLs with alternate for each target country. Ideal: 100% in core countries.
Tag auto-generation
Via AutoSEO, injects correct hreflang on each URL without touching the CMS. With guaranteed reciprocity.
Localised vs translated content
Translating your Chilean content literally to Mexican Spanish is a waste. Google detects the pattern and treats both versions as duplicate. Worse: Mexican users perceive the tone as foreign and increase bounce rate. Localisation goes beyond translation:
| Element | Literal translation | Semalt localisation |
|---|---|---|
| Keywords | Keep the same | Own per-country research with Semalt AI |
| Vocabulary | Neutral Spanish | Specific local slang |
| Examples | Copy the Chilean ones | Local case studies per country |
| Currency | Convert base currency | Local currency price + local gateway |
| Contact | Base country phone | Local country phone |
| Address | Only base city | Local office/partner per country |
| Testimonials | Only base clients | Local target-country client testimonials |
| CTA | Formal tone | Adjusted per country register |
Local SEO per country (GBP, directories, currency)
Each country has its own local SEO ecosystem. Semalt centralises management but you need to know the critical directories per country:
Argentina
OLX Argentina, MercadoLibre AR, GuiaLocal AR, ClasificadosOnline AR. GBP in Spanish with voseo.
Mexico
Sección Amarilla MX, Vive México, ClasificadosDF, MercadoLibre MX. GBP with 12/24 schedule.
Colombia
Páginas Amarillas Colombia, Mercado Libre CO, Locanto CO, Google Maps with strata.
Peru
Páginas Amarillas PE, OLX PE, Adondevivir. Segment by Lima vs interior.
Spain
Páginas Amarillas ES, 11888, Milanuncios, Wallapop (for product). Business registry as signal.
Chile (base)
Maintain Chilean GBP as base — see local SEO guide.
Multi-country regional tracker
Semalt Rank Tracker multi-country shows in the same dashboard:
- Each keyword's position across Google Chile, Argentina, Mexico, Colombia, Peru, Spain
- Position differences between countries (tells you where you do worse and better)
- SoV per country vs local competitors
- Cross-country cannibalisation alerts (when your AR URL appears in Google MX)
- SERP feature comparison per country (AI Overview varies a lot by region)
Practical data
AI Overview appears in 41% of informational queries in Chile but 58% in Mexico and 33% in Argentina. Optimising content for AI Overview varies by country. Semalt Rank Tracker segments this automatically.
Case: SaaS expanding to 4 LATAM countries
We started with mybrand.cl as Chilean base, 12k organic monthly sessions. Expansion to AR, MX, CO, PE started in January 2026. With Semalt International we migrated to subdirectories (mybrand.com/cl/, /ar/, /mx/, /co/, /pe/), reciprocal hreflang, localised content per country. 8 months later: 47k aggregate monthly sessions, distributed 34% CL, 28% MX, 15% AR, 13% CO, 10% PE.
Head of Growth, B2B SaaS (LATAM expansion 2026)Zero cannibalisation of the Chilean site: well-implemented hreflang made Google serve the correct version to each country. Without stealing SoV between them.
International expansion checklist
Phase 0: Preparation (1-2 months before launch)
- Local keyword research per country (Semalt AI)
- Local competitor analysis per target country
- Architecture decision: subdirectories recommended
- Local currency, phone, address registration (partner if no office)
- Definition of local content partner per country
Phase 1: Technical setup
- Subdirectory structure working (/cl/, /ar/, /mx/, etc.)
- Hreflang tags with reciprocity on each page
- x-default configured (ideally .com/en/ or main country)
- Canonical pointing to itself per version
- Sitemap.xml with hreflang xhtml:link declarations
- Search Console: property per subdirectory (International Targeting)
- Geo-targeting configured in GSC per country
Phase 2: Localised content
- Homepage per country with local vocabulary and examples
- Service / product landing pages localised
- Prices in local currency + local payment gateway
- Testimonials from target country clients
- Blog / content guides local (minimum 6-10 initial posts)
- Localised FAQ (taxes, shipping, warranty per country)
- Local date and time format
Phase 3: Local SEO and authority
- GBP per country (if physical office) or service area business
- NAP in 10-40 local directories per country
- Local backlinks via target country media and blogs
- Local digital PR for initial awareness
- Guest posts in local sector publications
Phase 4: Monitoring and optimisation
- Semalt Rank Tracker multi-country active
- Cross-country cannibalisation alerts
- Monthly report per country (sessions, keywords, conversion)
- Quarterly localised content refresh
- Strategy adjustment if a country does not take off in 6-9 months
More in this series: Semalt Analytics: the SEO data GA4 hides, Semalt AutoSEO: optimisation that runs 24/7, Competitor analysis without leaving a trace.
FAQs
Can I use es-419 instead of es-CL, es-AR, es-MX?
You can, but it is suboptimal. es-419 is «generic LATAM Spanish» and serves as broad fallback. For core countries (revenue-generating), use the specific code (es-CL, es-MX, es-AR) to signal dedicated content.
How do I avoid cannibalising my base SEO when launching /mx/?
Correct reciprocal hreflang is everything. Base URL declares «alternate MX at /mx/x», MX URL declares «alternate CL at /cl/x». Google understands they are the same page for different audiences and does not treat them as duplicate. Semalt validates this automatically.
Do I need hosting in each country?
No. A modern CDN (Cloudflare, CloudFront) serves your site with low latency across all LATAM from a single instance. Only consider local hosting for: payments (some countries require local PSP by regulation) and data compliance.
How long until a new country indexes?
Google indexes new URLs in days. Ranking in top 10 in a new country takes 4-8 months because you need: (1) sufficient content, (2) local authority (backlinks), (3) Google confirming your content serves that region.
What if my current site is only ccTLD?
You can: (a) migrate to .com with subdirectories (recommended medium-term), or (b) keep the ccTLD and add /ar/, /mx/ subdirectories. The second is faster but Google may give less international boost. Semalt Migration guides the decision with your current profile data.
International LATAM SEO is not writing in neutral Spanish. It is 5 parallel strategies connected by correct hreflang. Semalt centralises the architecture and prevents cannibalisation so each market grows contributing to the total.
Plan your LATAM expansion with Semalt
International module setup: 45 minutes. Initial hreflang audit: 30 minutes. Complete playbook per target country.
Sign in to Semalt International →