Keyword Research In The Target Language
A translated keyword list produces terms nobody types. Running the English set through a translation tool and handing it to a writer fails because demand is not a translation of demand: the local term is often an English loanword, a different product category, a competitor brand used as a generic, or a phrasing with no English counterpart at all. Do this before any localised page is briefed, and repeat it when localised pages sit indexed and flat.
CATEGORY
International SEO
FORMAT
keyword-transcreation-for-new-markets.md
WHEN TO REACH FOR THIS
Use when a market launch is being briefed from a translated keyword list, or when localised pages are indexed but rank for nothing despite mirroring an English page that works.
The skill file
keyword-transcreation-for-new-markets.md
---
name: keyword-transcreation-for-new-markets
description: Use when a market launch is being briefed from a translated keyword list, or when localised pages are indexed but rank for nothing despite mirroring an English page that works.
---
# Keyword Research In The Target Language
A translated keyword list produces terms nobody types. Running the English set through a translation tool and handing it to a writer fails because demand is not a translation of demand: the local term is often an English loanword, a different product category, a competitor brand used as a generic, or a phrasing with no English counterpart at all. Do this before any localised page is briefed, and repeat it when localised pages sit indexed and flat.
## What you need first
- The English keyword set with volume and the page currently serving each term
- A native speaker from the target market who buys or uses the product, not only a translator
- Volume data pulled with the target country and language set explicitly, not the default locale of your account
- The live result page for the top ten seed terms, captured from the target country
## Method
1. Pull volume with country and language set explicitly, and check the interface language of the tool as well. Tools default to the account locale, and a Mexican figure pulled with the account set to Spain is a different market entirely.
2. Ask the native speaker what they would type, unprompted, before you show them the translation. Showing the translation first anchors them onto it and you lose the term you were looking for.
3. Test whether the English word is the local word. In software, finance and technical categories the borrowed English term routinely carries more demand than any native translation, so translating it targets a phrase with no volume behind it.
4. Search every surviving candidate in the local result page and read what ranks. If the results are a different product category, the term is a false friend and no page built on it will ever match the intent.
5. Hunt for demand with no English source: local regulation, local payment methods, local units and sizing, local seasonality, local brands used as generic nouns. These are usually the highest-converting terms in the market and never appear on a translated list.
6. Resolve singular, plural and compound forms per language before committing. German compounding and Slavic case endings split volume that English holds in one term, so picking the wrong form loses most of the demand for it.
7. Map the finished set to pages before anything is briefed. A market frequently needs a different page structure rather than a translated one, and finding that out after twenty translations are paid for is the expensive way to learn it.
## What this produces
A per-market keyword set giving the local term, where it came from, the page it maps to, and a flagged list of English terms deliberately left in English.
## Where this goes wrong
- Handing the list to a translator rather than to someone who searches in that market, which returns grammatically correct terms with no volume
- Trusting volume pulled without an explicit country setting, which quietly returns worldwide or account-locale numbers
- Treating one Spanish, Arabic or Portuguese list as sufficient for every country that speaks it, when the everyday vocabulary for common products differs by country
- Building the local page from the English outline, so it answers questions that market never asks and omits the ones it does
---
From the QuQi skill library - https://www.quqi.io/skills/keyword-transcreation-for-new-markets
Free to download · no account, no email
What you need first
-
The English keyword set with volume and the page currently serving each term
-
A native speaker from the target market who buys or uses the product, not only a translator
-
Volume data pulled with the target country and language set explicitly, not the default locale of your account
-
The live result page for the top ten seed terms, captured from the target country
Method
-
01
Pull volume with country and language set explicitly, and check the interface language of the tool as well. Tools default to the account locale, and a Mexican figure pulled with the account set to Spain is a different market entirely.
-
02
Ask the native speaker what they would type, unprompted, before you show them the translation. Showing the translation first anchors them onto it and you lose the term you were looking for.
-
03
Test whether the English word is the local word. In software, finance and technical categories the borrowed English term routinely carries more demand than any native translation, so translating it targets a phrase with no volume behind it.
-
04
Search every surviving candidate in the local result page and read what ranks. If the results are a different product category, the term is a false friend and no page built on it will ever match the intent.
-
05
Hunt for demand with no English source: local regulation, local payment methods, local units and sizing, local seasonality, local brands used as generic nouns. These are usually the highest-converting terms in the market and never appear on a translated list.
-
06
Resolve singular, plural and compound forms per language before committing. German compounding and Slavic case endings split volume that English holds in one term, so picking the wrong form loses most of the demand for it.
-
07
Map the finished set to pages before anything is briefed. A market frequently needs a different page structure rather than a translated one, and finding that out after twenty translations are paid for is the expensive way to learn it.
What this produces
A per-market keyword set giving the local term, where it came from, the page it maps to, and a flagged list of English terms deliberately left in English.
Where this goes wrong
-
Handing the list to a translator rather than to someone who searches in that market, which returns grammatically correct terms with no volume
-
Trusting volume pulled without an explicit country setting, which quietly returns worldwide or account-locale numbers
-
Treating one Spanish, Arabic or Portuguese list as sufficient for every country that speaks it, when the everyday vocabulary for common products differs by country
-
Building the local page from the English outline, so it answers questions that market never asks and omits the ones it does
Use this skill in your own AI
The download is a plain markdown file with the name and trigger in its frontmatter. Where an assistant supports skills it can load itself, that frontmatter is what it reads to decide this one applies.
Claude Code
Save it as ~/.claude/skills/keyword-transcreation-for-new-markets/SKILL.md and Claude loads it on its own when what you are doing matches the trigger line. Put it in .claude/skills inside a project instead if the whole team should have it.
Claude
Upload the file in the skills section of your settings. Once it is there it applies itself in any conversation where the trigger fits, so you do not have to remember it exists.
ChatGPT
There is no skills format to install into, so paste the file contents into a Project instruction or a Custom GPT instead. It then applies to every chat in that project rather than only the one you paste it into.
Anything else
Paste the markdown into the chat before your question. It works in any assistant, it just has to be pasted again each time.
Questions about this skill
When is this needed rather than translating the English keyword list?
Translating the list is the default and it produces terms nobody types. Demand is not a translation of demand: the local term is frequently an English loanword, a different product category, or a competitor brand used as a generic noun. Do this before any localised page is briefed, and again when localised pages sit indexed and flat.
What do I need in hand before starting?
The English set with volume and the page serving each term, volume pulled with target country and language set explicitly, the live local result page for your top seed terms, and a native speaker from that market who buys the product rather than only translates it. Without that buyer you get grammatically correct terms with no volume behind them.
What do I end up with, and which part of it gets used?
A per-market set giving the local term, where it came from, the page it maps to, and the English terms deliberately left untranslated. The mapping column is what gets used, because a market often needs a different page structure rather than a translated one, and learning that after twenty translations are paid for is the expensive route.
What ruins this most often?
Showing the native speaker your translation before asking what they would type. It anchors them onto your phrasing and you lose the term you were there to find. What that costs is the loanword, the local regulation term or the local payment method never entering the list, and those are usually the highest-converting terms in the market.
More in International SEO