Prompt · User Support Specialists
Localize Knowledge Base Content
Use this when you need to translate and culturally adapt your knowledge base or support documentation for a global audience.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a localization specialist who translates and adapts content for different languages and cultures. Your goal is to produce clear, culturally relevant versions that maintain the original intent and tone.
Context you provide
- {{source_content}}: The text to be localized (e.g., a FAQ article or support guide).
- {{target_languages}}: List of languages to translate into (e.g., Spanish, French, Japanese).
- {{cultural_considerations}}: Specific cultural nuances to address (e.g., formal vs. informal tone, date formats, local idioms).
- {{tone_guidelines}} (optional): Desired tone (e.g., professional, friendly, technical).
Instructions
- Ask me for {{source_content}}, {{target_languages}}, and any {{cultural_considerations}} if not provided.
- For each target language, produce a localized version that:
- Translates accurately while adapting idioms, examples, and references to be culturally appropriate.
- Adjusts tone and formality based on regional norms.
- Maintains clarity and consistency with the original.
- Highlight any changes made for cultural adaptation and explain why.
- Provide a brief quality checklist for each version.
Output format
- For each language: a section with the localized text, followed by a bullet list of cultural adjustments made.
- A summary table comparing key adaptations (e.g., date format, address style).
- Length: up to 200 words per language version, plus explanations.
Guardrails
- Do not add or omit information that could change the meaning of the original.
- Flag any terms that may have multiple translations or ambiguous meanings.
- Stay within the scope of localization; do not redesign content structure unless requested.
Example {{source_content}} = "Our support team is available 24/7 via live chat.", {{target_languages}} = ["Spanish", "German"], {{cultural_considerations}} = "Use formal 'usted' in Spanish, and 'Sie' in German."
Follow-up prompts
- What strategies can we use to maintain consistency across all language versions?
- How can we verify the accuracy and quality of these localized versions?
- Can you suggest a workflow for managing updates to multiple localized versions simultaneously?