---
title: ToolRouter — Agent Use Case Guide
description: Step-by-step guide for completing a task with a specific AI agent using ToolRouter.
url: https://toolrouter.com/tools/translate/use-cases/localize-landing-pages/copilot
---
# How to Localize Landing Pages with Copilot

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.

## Setup

{"mcpServers":{"toolrouter":{"command":"npx","args":["-y","toolrouter-mcp"]}}}

## Steps

1. Add ToolRouter to Copilot MCP config
2. In Copilot Chat: "Translate the landing page strings in locales/en.json to French using the translate tool"
3. Copilot creates locales/fr.json with all translated strings
4. Review the translations against your page layout
5. Ask Copilot to verify all interpolation variables are preserved

## Example Prompt

```
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
