Impressions go up. Clicks do not. If that sentence describes your Spanish-language pages, you are not imagining it, and it is not a Google Search Console glitch. I watched this pattern for months on a Central Florida law firm’s Spanish site before I rebuilt it, and it is consistent enough that I can usually tell a translated page from a written-native one just by looking at the impressions-to-click ratio in Search Console, before I read a word of the copy.
The symptom: impressions climb, clicks do not
Here is what a translated Spanish page usually looks like in Search Console. It shows up for real search volume — sometimes hundreds of impressions a month — because Google can match the words on the page to the words in the query. But the click-through rate sits far below what the same content gets in English, often under 1%. The page is visible. It is just not being chosen.
That gap is the tell. A page that ranks but does not get clicked is not failing on rankings — it is failing on relevance to the person reading the snippet. And the fastest way to lose relevance in Spanish is to write the page in English first and run it through a translator second.
Why a translated page loses to a written-native page
Translation preserves meaning. It does not preserve how a first-generation Spanish speaker in Central Florida actually phrases a search. Those are two different problems, and search engines only reward solving the second one.
A translated page says what the English page says, in grammatically correct Spanish. A written-native page says what the person searching would actually type — which is frequently a mix of Spanish and English, phrased the way someone raised speaking both languages phrases things, not the way a textbook would.
What “written natively” actually means
It does not mean better grammar, and it is not about hiring a more careful translator. It means starting from the question a real bilingual client would ask, in the words they would actually use, and building the page around that question instead of around an English page’s outline.
In practice that means keeping certain words in English inside a Spanish sentence, because that is genuinely how U.S. Hispanic bilingual speakers write and search — not because Spanish lacks the words. “Google Business Profile,” “website,” “reviews,” and “near me” almost never get translated in real search queries, even though a Spanish word exists for each of them. A translated page insists on translating them anyway, which is one more small signal to a bilingual reader that the page was not written for them.
The search terms a translation will never catch
I found this by reading actual Google Search Console query data for a bankruptcy law firm’s site, not by guessing. Real, recurring queries included phrases like “chapter 7 que es” and “chapter 11 en español” — a legal term kept in English, dropped into a Spanish question. Local business queries follow the same pattern: “dentista near me” and “abogado near me” are two of the most common ways Central Florida’s Spanish-speaking residents search for services, and neither one is a phrase a translator would ever produce from an English source page, because there is no English sentence that translates into it. It only exists as a native bilingual search habit.
A page built from an English outline and translated afterward cannot contain phrases like these, because nothing in the English version suggested they existed. You have to go looking for them directly in bilingual search behavior — which is exactly what a native rewrite does and a translation cannot.
What changed when the site was rewritten, not translated
The clearest proof I have is Juan Burgos Law, a Central Florida bankruptcy firm whose Spanish pages I rebuilt from scratch instead of translating. After the rewrite, Spanish-language clicks rose 179% quarter over quarter, with one two-week stretch showing roughly a 10x jump over the prior two weeks as the new pages were indexed and started matching real bilingual queries. Clicks across the whole site, English included, rose 93% in the same window — because a site that finally answers real questions in both languages compounds, it does not just add a second audience next to the first one.
None of that came from new backlinks or a bigger ad budget. It came from replacing translated pages with pages written around the actual questions Central Florida’s Spanish-speaking clients were typing into Google. You can read the full breakdown, including the Search Console screenshots, in the Juan Burgos Law case study.
How to tell if your Spanish pages are translated or native
You do not need my Search Console access to check your own site. Look for these signs:
Your Spanish page’s structure mirrors your English page’s structure exactly, section for section. Real bilingual content sometimes answers a question your English page never asks, because it is a question only Spanish-speaking searchers raise.
Every English term has been translated, including the ones bilingual speakers never translate. If your Spanish page says “perfil de negocio de Google” instead of “Google Business Profile,” that is a translation, not native copy.
Your Spanish pages have real impressions in Search Console but a click-through rate well below your English average. This is the single fastest diagnostic. Filter Search Console by your Spanish URLs, compare the CTR to your English pages, and if it is dramatically lower, the page is not connecting with the person reading it.
Where to start
If your business already serves Hispanic clients in English and you are only now adding Spanish, resist the urge to just translate the site you already have. Start with the handful of questions your Spanish-speaking clients actually ask — in your own intake calls, in reviews, in the DMs and voicemails you already get in Spanglish — and build from there. That is the difference between a page that ranks and a page that gets clicked. I go through exactly how to do this, page by page, on the Hispanic Market SEO page.
Frequently asked questions
Is machine-translated Spanish content bad for SEO?
It is not penalized outright, but it consistently underperforms on click-through rate because it does not match how bilingual U.S. Hispanic audiences actually search. Google can index a translated page just fine; it simply will not be the result people choose.
How do I find out what my Spanish-speaking customers actually search for?
Start with your own Search Console query data filtered to your Spanish pages, plus the actual words your bilingual staff hear on calls and see in reviews. Real query data beats keyword-tool volume estimates for Spanish, because tools built for English search behavior often miss Spanglish phrasing entirely.
Do I need separate Spanish pages, or can I just add a language toggle to my English pages?
Separate, natively written pages under their own URLs (an /es/ folder, for example) perform better than a toggle over the same English content, because a toggle usually still serves translated copy. The URL structure matters less than what is actually written on the page.