Lesson 6 · 17 min
In Spanish, the competition is usually smaller and the demand is big. On INEMA, the page about learning AI in Spanish was indexed on 10/03/2026, and the following week it was already showing up in queries that the Portuguese version didn't reach. In this lesson, you use data to decide whether a page deserves another language, and how to do it without falling into mass translation.
Start the lesson
Goal: decide, using real countries and queries, whether a winning page deserves a version in another language, and plan that reviewed version.
Click each block.
Start with a page that has already shown a signal, not the whole site.
Click each step.
Look at the countries by impressions for the last 28 days.
A few impressions from abroad is not ready-made demand; it is a signal to test with one page.
Impressions by country: Brazil 1,449, Portugal 106, Argentina 24, Uruguay 13. A small signal, but from people who speak Spanish.
Pick a page that already works in your language and make the version in the other one, with its own title and address.
One well-reviewed page is worth more than ten sloppily translated ones.
On 09/30/2026, the target queries in Portuguese sat between positions 23 and 69, with 0 clicks. The page /es/aprender-inteligencia-artificial/ was indexed on 10/03; the following week it had 5 to 10 impressions on each Spanish query, at positions 29 to 61.
A Spanish impression is not a click or a conversion. At INEMA, the case shows that the language opened a door; the click has not come yet.
Measure the new version in the same weekly export, separated by page.
Machine translation published at scale, without review, falls under the scaled content policy.
One page at a time, reviewed, with a destination in the language.
Replace what is between < > with your own. The hreflang goes on each page, not in the general layout.
<link rel="alternate" hreflang="pt-BR" href="https://www.<seusite.com>/<pagina-pt>/"> <link rel="alternate" hreflang="es" href="https://www.<seusite.com>/es/<pagina-es>/"> <link rel="alternate" hreflang="en" href="https://www.<seusite.com>/en/<pagina-en>/"> <link rel="alternate" hreflang="x-default" href="https://www.<seusite.com>/<pagina-pt>/">
Source page: </pagina-pt/> (signal: <impressions, queries>) Language: <es> Validated query in the language: <query> (autocomplete: yes/no; Search Console: <impressions>) Title and address in the language: <title> · </es/<slug-no-idioma>/> Who reviews: <name> Destination in the language: <course / group / contact in Spanish> Measurement: weekly export, new page row, for 4 weeks
| country | impressions |
|---|---|
| Brazil | 1,449 |
| Portugal | 106 |
| Argentina | 24 |
| Uruguay | 13 |
From the baseline report of 09/23/2026.
If the dashboard shows no other language, E2 becomes a justified "not yet."
Write down the 5 countries with the most impressions in the last 28 days and any queries in another language that show up.
Done when: the list has 5 countries with impressions and the queries in another language (or "none").
Pick a page with a signal and fill in the version plan: validated query in the language, its own title and address, reviewer, and destination in the language.
Done when: the plan has the query checked in autocomplete, who reviews, and a destination in the language; or one sentence with the reason to wait.
The explanation appears after your answer.
Question 1 of 4
The INEMA ES page gained Spanish impressions the week after indexing. What does the case prove?skill
Question 2 of 4
Why is it not enough to translate the title word for word?
Question 3 of 4
What is the risk of publishing 200 automatically translated pages all at once?
Question 4 of 4
The ES page turned out great, but the button leads to a community that is only in Portuguese. What's missing?
Pick an answer. The explanation shows up after you try.