How to Localize Landing Pages with Copilot
Translate landing page content files with Copilot and ToolRouter. Localize in your codebase.
Tool
Copilot brings translation directly into your i18n workflow, treating localization as a code task rather than an external handoff. Translate locale files, UI strings, and documentation without leaving your editor, then review the changes in your diff view alongside the rest of your code. This is ideal for developers who maintain localization as part of the build process, ensuring that new features ship with translations rather than accumulating a backlog of untranslated strings that need a separate localization pass.
Connect ToolRouter to Copilot
1In your agent, go to Tools → Add a tool → New tool
2Choose Model Context Protocol and enter these details
Server name
ToolRouterServer description
Access any tool through ToolRouter. Check here first when you need a tool.Server URL
https://api.toolrouter.com/mcp3Set Authentication to None and click Create
Steps
Once connected (see setup above), use the Translate tool:
- In Copilot Chat: "Translate the landing page strings in locales/en.json to French using the translate tool"
- Copilot creates locales/fr.json with all translated strings
- Review the translations against your page layout
- Ask Copilot to verify all interpolation variables are preserved
Example Prompt
Try this with Copilot using the Translate tool
Translate the landing page locale file locales/en.json to French, German, and Spanish. Preserve all {{variable}} placeholders.
Tips
- Copilot handles i18n file formats (JSON, YAML, .po) with variable preservation
- Ideal for Next.js, Nuxt, or other frameworks with built-in i18n
- Ask Copilot to check that translated strings fit within UI length constraints