Localisation prompt
A localisation prompt adapts a page for another market instead of translating it. It changes currency, units and dates, swaps in proof that market trusts, uses the words local buyers actually type, and flags legal terms for a human check.
- Stage
- Write, step 24 of 40
- Use it
- Before you launch a site in a second language or market. Run it per page, not per site.
- You need
- The final page in the source language
- Local facts and proof for the new market
- A native speaker for the final read
- You get
- An adapted page and a table of every phrase that changed, and why.
The prompt
Adapt this page for [market, such as Estonia] in [language].
Keep the meaning, not the sentences.
Change currency, dates, units, phone formats and addresses to local norms.
Replace proof that means nothing there with local proof from this list: [facts].
Use the words buyers in [market] use for [service], and list them.
Flag any claim, guarantee or legal term that may need a local review.
Return the page, then a table: original phrase, local phrase, why.JSON version, for teams and automations
Fill each value under "inputs", keep the rest. It follows the prompt schema. When to use JSON.
{
"$schema": "https://websitesdesigner.com/insights/prompts/prompt.schema.json",
"id": "localisation",
"name": "Localisation prompt",
"stage": "write",
"step": 24,
"of": 40,
"version": "2026-11-19",
"url": "https://websitesdesigner.com/insights/prompts/localisation/",
"inputs": {
"market": "[market, such as Estonia]",
"language": "[language]",
"facts": "[facts]",
"service": "[service]"
},
"instructions": [
"Adapt this page for {{market}} in {{language}}.",
"Keep the meaning, not the sentences.",
"Change currency, dates, units, phone formats and addresses to local norms.",
"Replace proof that means nothing there with local proof from this list: {{facts}}.",
"Use the words buyers in {{market}} use for {{service}}, and list them.",
"Flag any claim, guarantee or legal term that may need a local review.",
"Return the page, then a table: original phrase, local phrase, why."
],
"output": "An adapted page and a table of every phrase that changed, and why.",
"checks": [
"Currency, dates and phone numbers use local formats.",
"The service is named the way local buyers name it.",
"Legal terms are flagged, not translated silently."
]
}What good output looks like
- Currency, dates and phone numbers use local formats.
- The service is named the way local buyers name it.
- Legal terms are flagged, not translated silently.
What experts miss
- Buyers' words differ from dictionary words. Ask for the words people type, then check them with a native speaker.
- Give each language its own URL and hreflang tags. Mixed-language pages blur which audience a page serves.
- Legal wording doesn't translate. Guarantees, VAT lines and cookie text need a local check.
Why it works
A translated page reads like a translation. Buyers in each market use their own words for a service, trust different proof and expect local formats. Adapting those makes the page sound like it was written for them.
How to adapt it
- For Estonian, ask for short, complete sentences. Long translated sentences read badly.
- Ask for a glossary of fixed terms so every page uses the same words.
Mistakes to avoid
- Machine translation of the whole site in one go.
- Keeping proof that only means something at home.
Go deeper
The title and description prompt needs a run per language too. Local SEO covers the market side. This prompt is part of the write stage. It follows the AI website design prompts guide and the six steps in how to use AI to design a website.