Hreflang is a note you write to a search system about which URL is for which audience. It is not a ranking booster. It is not a way to make one Spanish page stand in for twenty countries. When it is honest, it prevents the wrong URL from being shown. When it is decorative, it advertises that you have not chosen.
Spanish sites get this wrong in a particular way. Someone publishes /es/, tags it as es, es-ES, es-MX, es-AR, and x-default, and then asks why the page is confused. The annotation said the page was for everyone who reads Spanish. The content was written, if you are lucky, for one of those audiences.
One page, one audience
If you only have a Spain page, annotate it as Spain. Do not add Mexico “for coverage.” Coverage is a word from media plans. Search systems will pick a URL anyway. Your job is to make that pick match reality.
If you have a Spain page and a Mexico page, they should differ in more than the hreflang tags. Prices, examples, legal notes, and vocabulary should justify the split. Two near-duplicate articles with different tags are a cluster waiting to be ignored. The markets are not interchangeable; the pages should not be either.
Coverage is a word from media plans. Search systems will pick a URL anyway. Your job is to make that pick match reality.
Language tags are not country tags
`es` means Spanish, unspecified. `es-ES` means Spanish as used in Spain. Using `es` on a page full of Spanish (Spain) legal references is a mild lie. Using `es-MX` on that same page is a louder one. The louder one is more common in plugins that offer a dropdown.
English pages pointing at Spanish pages, and the reverse, only help when both sides exist and are maintained. A hreflang entry to a redirected URL, a 404, or a noindexed template is a broken note. It is worse than no note. Crawl the return tags. This is boring. It is also the work.
| Tag | What it claims | When it is honest |
|---|---|---|
es | Spanish, unspecified | A genuinely international Spanish page, which is rare |
es-ES | Spanish as used in Spain | Prices, legal notes, and examples are Spanish |
es-MX | Spanish as used in Mexico | The page is actually for Mexico, not a sticker |
x-default | The fallback URL | You maintain a chooser, or a real international hub |
es-MX on a Spain legal page is a louder lie than using es. The louder one is more common in plugins.What this has to do with links
Mentions should point at the URL that is meant to rank for that audience. If publishers in Spain are citing your Mexican URL because it was the one in the pitch, you have taught the graph the wrong destination. Outreach and hreflang are the same decision, made in two places. See how campaigns are run for the join, and outreach for the pitch.
Search behaviour belongs in the same conversation. If people in Chile search differently, a Spain URL with a Chile tag will not become a Chile URL. It will become a mislabelled Spain URL. Read how Spanish queries differ before you add another code to the cluster.
Sitemaps, HTML, and the urge to do both
Plugins love to emit hreflang in the head and in a sitemap. That is fine when they stay identical. They rarely stay identical. A marketing URL added to one and not the other, a trailing slash mismatch, a language code that differs by a hyphen: these are how clusters rot. Pick a source of truth. Check it after each release, not after a ranking dip.
HTML in the head is easier to inspect on a single URL. Sitemaps are easier to audit in bulk. Either can work. Both at once only work if someone owns the diff. If nobody owns it, you do not have an international setup. You have two notes that will drift.
When not to use hreflang at all
If you have one Spanish URL and you are not targeting more than one country with separate pages, you may not need a cluster. A language HTML tag and a coherent page are sometimes enough. Hreflang becomes useful when there are real alternates. Decorating a single URL with five codes is not a cluster. It is a wish.
The same applies to x-default. If you do not have a sensible default — a chooser, or a genuinely international English hub — do not invent one. Search systems will pick. Your job is to make the remaining annotations true. Truth is a higher bar than coverage.
A small implementation standard
Reciprocal tags. Absolute URLs. Canonicals that do not contradict the cluster. No mixing of hreflang in sitemaps and HTML if you cannot keep them in sync — pick one. No x-default that points at a marketing homepage when the useful default is a language chooser you actually maintain.
- Reciprocal tags on every URL that participates in the cluster.
- Absolute URLs, including the trailing-slash convention you actually use.
- Canonicals that agree with the cluster, not a second opinion from a plugin.
- Hreflang in the sitemap or in the HTML head — not both unless someone owns the diff after every release.
- No x-default pointing at a marketing homepage when the useful default is a language chooser you maintain.
- Empty cells when you do not have the page yet. Empty is accurate. Invented coverage is not.
None of this requires a case study. It requires a spreadsheet of URLs and audiences that matches the site, and the humility to leave cells empty when you do not have the page yet. Empty is accurate. Invented coverage is not.