Translated URLs With English Text: What It Did to Our Indexing
On our own site, blog pages under translated URLs held mostly English text. Here is what the Search Console data showed, what we changed, and what to check on yours.
If you add languages to a site, it is tempting to give every page a translated URL first and fill in the text later. We did that on our own product, Geotag.World, and the data was clear about how it went. This post covers what happened, the fix, and a short list to check on your site.
Geotag.World is a CodesSavvy product, not a client project. The figures below come from Google Search Console for that site. The comparison figures come from a Search Console audit pulled on 5 Sep 2026 and are not filtered by country.
What we found
We ran a Search Console URL audit of 245 sitemap URLs. Of the 196 non-English URLs, 125 had never been crawled.
The cause was in the blog data. It had no locale field. So the 37 English posts were served under four other language paths, and about 89% of the English body text appeared word for word on the Spanish page (measured on the Spanish blog pages in the 5 Sep 2026 audit). The menus and buttons were translated. The articles were not.
What the numbers showed
We compared untranslated blog pages with the pages that were translated (tool and landing pages).
| Group | Indexed | Clicks | CTR |
|---|---|---|---|
| Untranslated blog pages | 47 of 57 | 12 | 0.7% |
| Translated pages | 14 of 14 | 124 | 13.2% |
These are measured figures from Search Console for 1 Jul to 2 Sep 2026, from a Search Console audit pulled on 5 Sep 2026. The untranslated group is larger and got far fewer clicks. Every page in this comparison that was not indexed was in that group.
This is one site, so treat it as a case, not a rule. But the pattern matches what search engines say in their own guidance: a page should be useful in the language of its URL.
Why it happens
- A translated URL is a promise that the page is in that language.
- If the body is in another language, the page looks like a copy of an existing page.
- Search engines crawl copies less, and may skip them.
- A crawl budget spent on copies is not spent on your real pages.
What we changed
- The blog is now English-only. Other locales carry a noindex tag and were removed from their sitemaps.
- The hreflang links moved into the page head.
- A crawlable language row was added to the footer.
- The sitemap went from 245 to 93 URLs. That was the count at the time of the fix on 5 Sep 2026; the live sitemap was 98 URLs on 24 Sep 2026.
- End-to-end tests now guard the rule, and they make a quiet return less likely.
We also chose not to redirect visitors by browser language. Automatic redirects by browser language are discouraged in Google's guidance on localized versions. A small suggestion banner offers the other language and lets the visitor decide.
Today the site is not fully translated, and we do not say it is. The blog and the legal pages are English-only. That is the honest state, and it is fine.
What to check
- Does every translated URL have body text in that language, not only the menus?
- Does your data model know which locale a page belongs to?
- Does the sitemap list only pages that are fully translated?
- Do hreflang links sit in the head and point to real, translated pages?
- Can a crawler reach the language versions through plain links?
- Is there a test that fails when a translated page still shows English text?
If you are planning a multilingual build, our Geotag.World case study shows the full timeline, and Dyadfit shows the same rule applied after English leaked onto its translated pages. To talk about your own site, book a call.
Frequently Asked Questions
Need this built?
Book a free 30-minute call. We'll discuss your goals, give you honest advice, and a clear estimate — no obligation.
Ways we can help
MVP Development
Production-ready MVPs in 4-6 weeks. Fixed price, senior engineers.
Learn moreAI App Rescue
Your Lovable, Bolt, or v0 app breaks with real users? We audit, fix the gaps, and hand back code you own.
Learn moreAI Integration
Add AI features to your product — OpenAI, Claude, RAG, semantic search, and copilots.
Learn moreMobile App Development
iOS and Android from one React Native codebase. Fixed price.
Learn moreRelated articles
HTTP 500 vs 400 Error Handling: How Wrong Status Codes Wake Up Your On-Call
A 500 for a typo in a form field pages someone for nothing. Here is how to pick the right 4xx or 5xx code, and how to alert only on what needs a human.
Read moreProcessWhy Your Date Is Off by One Day: The JavaScript Timezone Bug
A birthday or due date that shows up one day early is almost always a date-only value that got treated as a moment in time. Here is why it happens, where it hides, and how to stop it.
Read moreProcessAn AI Coding Assistant Rollout Plan for Engineering Teams
A phased plan for an AI coding assistant rollout: set goals, run a pilot, share rules files, review security, set review standards, train on real tasks, then roll out and check in.
Read more