If your site is in Spanish + English (or Spanish + Catalan/Basque/Galician) and your traffic feels stuck, you're probably hitting one of five SEO traps we see weekly. Each one with a clean, copy-able fix.
Tell us your idea and we'll send you a fixed quote in less than 24 hours. No commitment.
A pattern we see almost every week. A Spanish business calls us, frustrated. They built a beautiful bilingual site (often Spanish + English, sometimes Spanish + Catalan, increasingly Spanish + Portuguese for the LATAM/Brazil play). The site looks great. The content is good. But:
There are typically five mistakes underneath this pattern. Each one alone is enough to torpedo your international SEO. Three or four stacked is the norm. Here's the diagnosis, ranked in order of how often we find them.
hreflang is wrong, missing, or contradicting <link rel="canonical">This is the single most common technical error. Symptoms:
The cause is almost always one of:
hreflang tags missing entirely (≈40% of cases)hreflang referencing the wrong URL pair (e.g. /en/page points back to /es/another-page)<link rel="canonical"> set to the Spanish URL on the English page (a copy-paste accident from a CMS)hreflang="en-US" when targeting all English speakers (use hreflang="en" unless you have specific country variants)The fix that always works, copy-able:
<link rel="alternate" hreflang="es" href="https://yoursite.com/es/products/widget" />
<link rel="alternate" hreflang="en" href="https://yoursite.com/en/products/widget" />
<link rel="alternate" hreflang="x-default" href="https://yoursite.com/es/products/widget" />
<link rel="canonical" href="https://yoursite.com/en/products/widget" />
Three rules:
x-default points to the version you want shown to anyone not matching another language.Missing x-default alone has caused us to recover +38% organic traffic for one client in three months.
Pasting your Spanish copy into DeepL and shipping it is a fast way to:
A real example: a Madrid law firm translated their Spanish landing page about "abogados de divorcio" directly to English. The result:
What to do instead:
A pattern that's almost invisible:
/en/...Google's quality systems detect this. The English pages are demoted to "soft 404" status. They never rank.
How to find this in 5 minutes: in Search Console → Pages → "Soft 404", filter by URLs containing /en/. If you see lots of them, that's the problem.
The fix: complete the translation, or temporarily unpublish the English path with a real 404 (not 301 to Spanish — that's a different mistake).
Even subtle versions of this hurt:
martes 4 de marzo left inGoogle detects the page's language with two signals: the <html lang=""> attribute and the body content's actual language. If they disagree, the page falls into a confused state where neither language ranks well.
Quick checklist:
<html lang="en"> matches body languageog:locale, og:title, og:description in the page's languageThis is the deathblow we see in surprisingly many large Spanish brands:
/es/ automatically/en/Same problem in reverse: a /en/ page with an automatic redirect to /es/ for Spanish-IP visitors. Googlebot from a Spanish IP gets bounced. The English page is never indexed.
The fix is non-negotiable:
Vary: Accept-Language header only for content negotiation, never for blocking the alternate versionWe've recovered organic traffic by 80–120% on multilingual sites just by killing the auto-redirect.
If we open your bilingual site for the first time, here's what we check in 90 seconds:
hreflang, canonical, <html lang>.site:yoursite.com /en/ in Google → see how many English URLs are indexed vs how many exist./en/ → if impressions are 5%+ of /es/, you're not crashed; if they're below 1%, you have one of the traps above.If we run those five and one fails, we have a 70% chance of recovering significant traffic in the next 90 days.
A B2B SaaS in Madrid serving the LATAM market had zero organic traffic in English despite having ~85 well-written English pages.
Diagnosis: traps #1, #4, and #5 all present. Their CDN was redirecting any non-Spain IP to /es/ "for performance reasons". Googlebot in the US never saw the English pages.
Fix: removed the geo-redirect, fixed hreflang, audited 12 pages with mixed-language content. Cost of project: €2,800 (one engineer, one SEO, two weeks).
90 days later:
This is the kind of fix that pays for itself in a month and keeps paying for years.
If your bilingual or multilingual site feels "stuck" on the second language, send it our way. We'll run our 5-trap audit and a Search Console check for free, write up the diagnosis with severity, and tell you what's worth fixing first. We won't try to upsell you a generic "SEO retainer" if you don't need one.
Request an international SEO audit or see our SEO services.
Bilingual is a competitive advantage. Bilingual done badly is invisible.