Skip to content
Get Ranked On TopIllustrative case studySignal plan

A fictional business. The figures are a modelled scenario, not a client result.

Yarumo Cableways · Industry, energy & mobility

How a Medellín cable-car engineer stopped Google sending Brazil to its Spanish site

+74% organic enquiries, the right language in 96% of searches

Urban ropeway engineering firm, 150 staff · Medellín · 12 months · Latin America · Signal plan

Hreflang · Staging lockdown · Canonical mapping · Geo-redirect removal

SStaging1ES2PT3EN

Month 12 · 3 of 3 lines running · ghost station closed

  1. 58% → 96%

    Searches landing on the right language

  2. 3,140 → 0

    Hreflang errors

  3. 1,870 → 0

    Staging URLs indexed

  4. +74%

    Organic enquiries a month

The challenge

Three languages on one hillside, and the wrong gondola in every market.

Spanish, Portuguese and English subdomains with broken hreflang, plus an indexed staging copy: in every market, Google showed the wrong language.

Yarumo designs urban ropeways for city governments and bids for work in three languages. Each version lived on its own subdomain, run by a different team. Over the years the hreflang tags drifted apart, the Portuguese pages were canonicalised to the Spanish ones, and a staging copy of all three sites was left open to crawlers. Brazilian transport planners landed on Spanish pages, consultants in the United States on a staging server, and tender enquiries went quiet in the two markets the firm wanted most.

Departures, before · what Google showed
MarketSearcher readsPage shownRight language
COColombiaSpanishes.yarumo.example84%
MXMexicoSpanishstaging.yarumo.example79%
BRBrazilPortuguesees.yarumo.example31%
USUnited StatesEnglishes.yarumo.example44%
GBUnited KingdomEnglishstaging.yarumo.example52%

Share of searches in each market that reached a page in the searcher's language. Modelled.

Diagnosis

Four faults found walking the line.

Hreflang

3,140 errors

2,210 tags without a return link, pt-PT declared on pages written for Brazil, an invalid en-UK code and 180 alternates pointing at staging URLs. Google ignores a pair that is not confirmed from both sides.

Fault 1 of 4

Staging

1,870 URLs

staging.yarumo.example had no password and no noindex. 1,870 of its URLs were in Google's index, duplicating all three languages and outranking the live site on 212 queries.

Fault 2 of 4

Canonicals

640 pages

640 Portuguese pages named their Spanish original as the canonical, so Google treated them as copies and left them out of Brazilian results.

Fault 3 of 4

Geo-redirects

100% redirected

Every visit to a home page was redirected by IP address. Googlebot crawls mostly from the United States, so it was sent to English every time and almost never saw the Spanish or Portuguese home page.

Fault 4 of 4

The strategy

Four repairs, one timetable.

Built on our Signal plan: technical SEO for sites where architecture, crawling and indexing decide who finds you.

  1. Stop 1

    Hreflang

    One hreflang graph generated from the CMS, where every page is tied to its translations by content ID: es, pt-BR, en and an x-default, with each page listing itself and all its alternates. Hand-written tags were removed, and the XML sitemaps are validated every night.

  2. Stop 2

    Staging lockdown

    Staging went behind a password, and every response carries an X-Robots-Tag: noindex header. robots.txt was not used on its own, because a blocked page can never show Google its noindex. Indexed URLs were removed in Search Console, and a deploy check now fails any release that leaves staging open.

  3. Stop 3

    Canonical mapping

    Every page now canonicalises to itself, in its own language. The 640 Portuguese pages got their own canonicals back, and the 38 that had never been translated got a Portuguese summary instead of a copy of the Spanish text.

  4. Stop 4

    Geo-redirect removal

    The IP redirects gave way to a language banner that visitors can dismiss. Each home page now answers 200 to every visitor and every crawler, and hreflang does the job of sending each market to its own version.

Run the line

String the return cables. Close the ghost station.

Each station is one language version of the Yarumo home page. A cable only runs when both pages name each other: a tag with no return snaps it. Choose a station, edit the tags in its head and watch where each market lands.

!!SStaging1es2pt-BR3en
  • Running: both pages name each other
  • Snapped: a tag with no return
  • Ghost station: the indexed staging copy

Who lands where

  • Mexico74%

    74% on the right language

    Google shows es.yarumo.example

  • Brazil31%

    31% on the right language

    Google shows staging.yarumo.example

  • United States44%

    44% on the right language

    Google shows staging.yarumo.example

  • Everywhere else40%

    40% on the right language

    No x-default: Google picks a version

Modelled shares, for illustration only.

Tags in the <head> of pt.yarumo.example

  • <link rel="alternate" hreflang="pt-BR" href="https://pt.yarumo.example/"> self

Press a tag to add or remove it. A pair only counts when both pages carry it.

Line status

1 of 3 lines running

  • Spanish ↔ Portuguese (Brazil): snapped, the Portuguese (Brazil) page does not link back to the Spanish page
  • Spanish ↔ English: running
  • Portuguese (Brazil) ↔ English: snapped, the Portuguese (Brazil) page does not link back to the English page
  • Ghost station open: staging is indexed

Month by month

12 months on the timetable.

  1. Months 1–2

    Survey

    Crawled the three subdomains and staging, mapped every page to its translations, pulled Search Console data for each property and sampled 30 days of server logs.

  2. Month 3

    Lockdown

    Password and noindex on staging, removal requests filed, deploy check added. Staging URLs in the index reached zero by month 8.

  3. Months 4–6

    Hreflang graph

    Tag generator built on the CMS content IDs, codes corrected to es, pt-BR and en, x-default added, self-referencing canonicals restored on the Portuguese pages.

  4. Months 7–8

    Redirects out

    IP redirects replaced with a language banner; all three home pages recrawled within two weeks.

  5. Months 9–12

    Monitor

    Nightly hreflang validation, a weekly check of which host ranks in each market, and Portuguese summaries for the 38 untranslated pages.

Results

Every market on its own line.

Searches landing on the right language

58% → 96%

Average of five markets

Hreflang errors

3,140 → 0

Validated nightly across 1,860 URLs

Staging URLs indexed

1,870 → 0

Password, noindex and a deploy check

Organic enquiries a month

+74%

23 → 40 enquiries a month

Modelled scenario for a fictional business — not a client result. Rankings and traffic are never guaranteed; see our Terms.

Right language up, ghost station downSearches landing on the right languageStaging URLs indexed
0%050%1,000100%2,00058%96%M1M2M3M4M5M6M7M8M9M10M11M12

Right language by market

  • Colombia · Spanish84% → 98%
  • Mexico · Spanish79% → 97%
  • Brazil · Portuguese31% → 95%
  • United States · English44% → 94%
  • United Kingdom · English52% → 96%

BeforeMonth 12

Who ranked for what

QueryMarketPage shown, beforePage shown, month 12Position
ingeniería teleférico urbanoMXstaging.yarumo.examplees.yarumo.example#9 → #4
cable aéreo estudio de factibilidadCOes.yarumo.examplees.yarumo.example#6 → #2
projeto de teleférico urbanoBRes.yarumo.examplept.yarumo.example#14 → #5
empresa de teleféricoBRstaging.yarumo.examplept.yarumo.example#11 → #3
urban cable car engineeringUSes.yarumo.exampleen.yarumo.example#18 → #6
urban ropeway consultantsGBstaging.yarumo.exampleen.yarumo.example#21 → #7

Queries as searched, in the searcher's language. Positions are the modelled average in that market.

Get a plan like this

Running several language versions, a set of subdomains or a staging server you are not sure about? Start with the Signal plan, or tell us how your sites are set up.

All case studies