HTML5 game publishing
Spanish and German Queries: Pages That Match the Games You Actually Have
Use the feed's language field, label what is translated, write the text with a fluent reviewer and set up separate URLs, lang and hreflang, starting with one page.
Your search reports show queries in Spanish and German: "juegos de destreza mental", "juegos de agilidad mental", "mejores juegos gratis", "kostenlose spiele". Naturally you wonder whether to build Spanish and German pages. You can, but there is a trap. If the games on those pages are in English, a Spanish page that only translates the heading is a promise the game cannot keep. This post is about serving other-language queries honestly, using what the game feed tells you, and writing pages that a native speaker would not find embarrassing.
Start from the feed's language field
Each game in the PlayKovo feed carries a language value. It tells you what language the game's text is in. Use it. A Spanish-speaking visitor is not well served by a page of games whose menus are English, unless the game has very little text, like many puzzle or arcade games.
Separate games into three groups for each target language:
- Games in that language. The best fit. Show them first.
- Games with almost no text. Tap-and-drag puzzles, runners, sorting games. Language barely matters. Check each one by playing it.
- Games with a lot of text. Quests, story games, text-heavy strategy. Leave these off a page for people who do not read the language.
Do not guess from the title. A game with a Spanish title may have an English interface and the reverse.
Be honest about what is translated
If you say "juegos en español" on a page and half the games are in English, visitors will notice immediately. Promise only what you checked:
- "Juegos que se entienden sin saber inglés" (games you can understand without English) is a safe angle for text-light games.
- "Juegos en español" is only for games that actually are.
- If the page mixes, say so: a small label on each card showing the game's language.
Write the page in the language, by a human
Automatic translation of your English page produces text a native speaker spots in a second. Search engines also see the pattern. The text around the games, such as the introduction, the explanations and the tips, should be written or at least reviewed by someone fluent. If you cannot do this, a smaller, smaller-scope page is better than a large machine-translated one.
Think about how people really search in that language. "Juegos de agilidad mental" and "juegos de destreza mental" are two phrasings of one idea. A native speaker knows which is more natural for the page title and which fits in the body. A direct word-for-word translation of the English page would pick neither on purpose.
Technical setup for language pages
- Give each language its own URL, such as
/es/juegos-de-agilidad-mental. Do not switch language on the same URL based on browser settings, because search engines may only ever see one version. - Set the
langattribute on thehtmlelement for each page. - Use
hreflangannotations to link equivalent pages across languages, but only where an equivalent page really exists. Our post on a multilingual games section and hreflang has the details. - Translate the meta title and description too. Leaving them in English on a Spanish page is a common slip.
- Translate navigation and key labels, such as "Play" and "Controls", on the page, or the page looks half-finished.
Where the queries come from
Treat other-language queries as a hint, not an instruction. A few queries in Spanish in a list of thousands may come from a handful of people. Check the volume band in the report and ask whether you can serve that audience well for the long run. Building and maintaining a Spanish and German section is real work. If you are not going to keep it current, do not start it.
A cheaper first step is a single, well-made page in one language, and a check after a month to see whether it earns impressions. If it does, add a second page. If it does not, you have learned something at low cost. For finding the queries in the first place, see Bing Webmaster Tools for a games section.
Consider your audience beyond the query
The same query can come from very different places. "Mejores juegos gratis" might be Spain, Mexico or Argentina, which use different vocabulary and different habits. Write for the region you actually serve and say so on the page. If your site's audience is mostly one country, match its usage.
A short checklist
- Pick one language and one query group.
- Filter the feed by
language, then add text-light games you played yourself. - Write the text with a fluent reviewer.
- Set up a separate URL,
lang,hreflangand translated meta tags. - Label each game's language on its card.
- Re-check after a month.


