Spanish SEO: es-ES, es-MX, es-419, Adapting Your SEO to Spanish-Speaking Markets

Spanish SEO is not about "translating a few pages": in Madrid, Mexico City or Buenos Aires, the words, the tone and the queries change. The general principles are covered in our international SEO guide to structure, hreflang and localisation. This article keeps what is specific to Spanish-speaking markets: the es-ES, es-MX and es-419 codes, keywords by country, how many versions to run, localisation and citations in AI answers.

Spain, Mexico, Latin America: Distinct Markets for One Language

Spanish illustrates the multilingual rule: one language serves several countries, each with its own search habits. The grammar is shared, but vocabulary, forms of address and commercial expectations differ. A single "neutral" Spanish targets a demand that exists nowhere in that form.

On the search engine side, the situation is simple at the time of writing: Google dominates in every Spanish-speaking country, with no local competitor comparable to what you see in other regions of the world. The work is therefore less about choosing a search engine than about choosing which versions and which queries to target.

The following table summarises the markets most often met in B2B and the decision attached to each:

The es-419 code designates Spanish for Latin America and the Caribbean; it is based on the United Nations regional classification (UN M.49) and Google accepts it at the time of writing. It is a better option than a list of twenty countries when the content is the same for all of them.

Spanish Keywords: Start From Each Country's Queries

Translating a list of French keywords produces an editorial plan that sounds right… but does not match what people actually type. Research starts again from intent (understand, compare, buy), then validates the wording actually used in each target country. To structure this work by intent, see our article on search intent and how to classify it.

Posicionamiento web or indexación: the first trap

The word "référencement" shows the difficulty. In marketing, Spanish speakers talk about posicionamiento web (or posicionamiento SEO), which refers to the logic of rankings. The term indexación only means that a page has been recorded by a search engine. A page that targets indexación to talk about visibility attracts technical readers looking for something else.

Three types of trap recur in B2B projects:

• Meaning false friend: a term close to French that means something else, such as indexación used instead of posicionamiento.
• Usage false friend: a term that is correct but rarely searched in the country, whilst a variant dominates queries.
• Off-market query: apparent volume, but consumer or student intent with no commercial potential.

Vocabulary variants from one country to another

Everyday vocabulary changes by country, and these differences show up in queries, including in B2B when the offer involves hardware or mobility. A few examples:

The last row is a reminder that part of the professional vocabulary is shared, which makes a common es-419 version possible. The decision is made term by term, based on the queries observed in each country.

Validating queries country by country

Validating a Spanish keyword list takes three steps:

• read search data filtered by country, which shows which variant wins;
• have the list reviewed by someone from the country (local team, partner, customer), who will spot terms that are correct but dated or too formal;
• repeat the exercise for each version: a list validated for Spain cannot be reused as is for Mexico.

One Spanish Version or Several: The Decision Rule

The number of versions follows from the offer, not the language. If the product, price, currency and terms are the same in every target Latin American country, a single es-419 version is enough. Spain keeps its own version, because vocabulary, tone and commercial context (euro, European regulation) differ markedly there.

The following table turns this rule into concrete decisions:

Start small and expand on measured signals

A progressive approach limits costs: Spain or an es-419 version first, then a country version once impressions, contact requests or sales justify it. Publishing dozens of pages per country without measured demand creates content, review and support debt, with no guarantee of traffic. The same principle applies at site level: you do not open a new language without measured traction.

Measuring Spain and Latin America separately

Measurement follows the way versions are split. Mixing es-ES and Latin America in one report hides the gains of one market behind the losses of the other. Three settings avoid this trap:

• the Search Console Performance report filtered by country, for each version;
• Google Analytics 4 segmented by country and language, down to conversions;
• rank tracking by country, since results in Madrid and Mexico City are not the same.

Localising Beyond Translation: Currency, Formats, Proof and Tone

A localised version adapts everything visitors read to judge the offer, not just the sentences. The differences concentrate on a few elements, which you check version by version.

Currency, prices, formats and legal notices

The elements to adapt for each Spanish version are as follows:

• Currency and tax: euro and IVA for Spain, Mexican peso for Mexico; a shared es-419 version shows a currency and terms that are valid for every target country.
• Formats: dates, phone numbers, addresses and units, in forms as well as in content.
• Commercial terms: payment methods, delivery times and terms, support and opening hours.
• Legal notices: those of the target country, not a translation of the French ones.
• Local proof: references, examples and contacts from the market, rather than translated French examples.

Usted, tú or vos: choosing the register by country

The register changes by country and sector:

• Spain: informal address (tú) is common in marketing, including B2B; formal address (usted) remains the norm in formal exchanges.
• Mexico and Colombia: usted prevails more widely in a professional context.
• Argentina: voseo replaces tú with vos, with its own conjugations; a text written with tú sounds foreign there.
• Shared es-419 version: usted is the safest choice, because it is understood and accepted everywhere.

The chosen register goes into the editorial charter of each version, alongside terminology, so that all content for a market speaks the same way.

URL Structure and Hreflang for Spanish Versions

Spanish versions follow the site's general rules: each version gets its own URL, and country targeting relies on a ccTLD or on hreflang annotations, never on a URL parameter or a cookie.

URL structure

The subdirectory (/es-es/, /es-mx/, /es-419/) remains the default choice, because it shares domain authority; the full comparison with ccTLDs and subdomains is in the international SEO guide cited in the introduction. A ccTLD such as .es or .mx is mainly justified when a local entity already exists.

The hreflang tag set

Here is the tag set for a page available in Spain, in Mexico and for the rest of Latin America, to be placed in the <head> of each of the three versions:

• <link rel="alternate" hreflang="es-ES" href="https://www.example.com/es-es/" />
• <link rel="alternate" hreflang="es-MX" href="https://www.example.com/es-mx/" />
• <link rel="alternate" hreflang="es-419" href="https://www.example.com/es-419/" />
• <link rel="alternate" hreflang="es" href="https://www.example.com/es-419/" />
• <link rel="alternate" hreflang="x-default" href="https://www.example.com/" />

The es tag serves Spanish speakers whose country is not listed, here pointing to the Latin American version; x-default points to the selector page. Each version carries the same set (return tags) and references itself (self-referencing). The "es-LATAM" code is invalid: only es-419 designates Latin America. Other methods and verification are detailed in our guide to implementing and checking hreflang annotations.

GEO in Spanish: Getting Cited by AI in the Right Language

Generative engines (ChatGPT, Perplexity, Gemini, AI Overviews and AI Mode) answer in the language of the query and cite sources written in that language first. A question asked in Spanish in Bogotá or Seville therefore calls for an answer built from Spanish-language pages. Without a Spanish version, a brand does not enter the corpus these engines consult for that market.

The reach of these tools extends well beyond Europe: ChatGPT is available in 161 countries (Tool Advisor, 2025). For a Spanish-language version, the conditions for being eligible for citations are as follows:

• One version per language, accessible and indexable, rather than a French page translated on the fly.
• Consistent entities: the same organisation name, the same facts and the same figures from one version to another.
• Structured data declaring the language of each page with inLanguage (es-ES, es-MX, es-419).
• AI crawlers not blocked on the site's Spanish directories.

The content must also be citable: clear definitions, direct answers, tables, the country's vocabulary. A citation is observed (correlation), not guaranteed. For the overall method, see our article on optimising for generative engines (GEO).

Mistakes to Avoid on a Spanish-Language Site

The mistakes seen on Spanish-language sites concern language as much as technical setup. The following table links each one to its symptom and its fix:

These mistakes share the same reflex: treating Spanish as one language to translate, rather than as several markets to serve.

Depending on Your Situation

Depending on the stage of your Spanish-language project, these resources take over:

• You are writing your first pages in Spanish: apply our method for SEO copywriting of pages that rank.
• You sell online in Spain or Mexico: adapt product and category pages with our e-commerce SEO guide.
• Your Spanish version lacks authority: earn links and mentions from sites in the country through netlinking.

To produce content localised by market (es-ES, es-MX, es-419) from each country's queries, the Incremys content production module organises writing version by version.

FAQ on Spanish SEO

Do you need one Spanish version or several?

It depends on the offer. If the product, price and terms are identical across the target Latin American countries, two versions are enough: es-ES for Spain and es-419 for Latin America. An additional country version, such as es-MX, is only justified if the offer genuinely differs there and measured demand covers the cost of production and maintenance.

What does the es-419 code mean?

The es-419 code designates Spanish for Latin America and the Caribbean. It combines the language code "es" with the regional code 419 from the United Nations classification. Google accepts it in hreflang annotations at the time of writing. It lets you serve a single version to every Latin American country, whereas "es-LATAM" is an invalid code.

Which variant should you choose for Mexico?

For Mexico, the es-MX variant is the right choice as soon as prices in pesos, delivery or the offer differ from the rest of Latin America. Otherwise, the es-419 version covers the country. In both cases, vocabulary follows Mexican usage (computadora, carro, celular) and formal address (usted) remains the expected register in a professional context.

Should you use tú or usted in B2B Spanish?

You need to choose by country. In Spain, informal address is common in marketing, even between businesses. In Mexico and Colombia, formal address (usted) dominates professional exchanges. In Argentina, informal address takes the form of voseo. For a shared es-419 version, usted remains the safest choice, because it is understood and accepted in every country.

Is Google the only search engine to target in Spanish-speaking countries?

Google dominates in every Spanish-speaking country at the time of writing, with no significant local competitor. The priority is therefore to be Google-compatible, then to follow Bing depending on your audience. Generative engines matter too: they answer in Spanish from Spanish-language sources, which makes a Spanish version necessary to be cited by them.

Can a Spanish version compete with the French version?

Yes, if targeting is unclear. Without consistent hreflang annotations, or with canonicals pointing to another language, versions can get in each other's way in search results. With return tags, a self-referencing canonical on each version and genuinely localised content, each version is served to its own audience without competing with the others.