Fill from Your Website
A new localization engine starts with no glossary, rules, or brand voice. Instead of writing them by hand, you can fill an engine from your website: Lingo.dev reads your pages and drafts a glossary, a ruleset, and a brand voice from how your product already writes about itself. Everything it creates is an ordinary glossary, ruleset, or brand voice you can edit.
Where to start#
| Where | What it does |
|---|---|
| New engine | The wizard's website step fills the engine as it's created. |
| Fill missing context on an engine | Fills what you choose among the glossary, ruleset, and brand voice the engine doesn't have yet. |
| Create from website on the glossary, ruleset, or brand voice list | Creates one glossary, ruleset, or brand voice and attaches it to the engine you pick. |
| MCP | Your AI assistant can create and fill an engine, or fill an existing one, from the conversation. It can also read up to ten links or pasted texts instead of one website. |
What it reads#
Enter your website. Lingo.dev shows a screenshot of it so you can confirm it's the right site before anything runs, and detects the site's language.
It reads the page you gave, then picks the pages that say most about your product - docs, pricing, product, and about pages - up to five pages in total. When it picks pages, it skips any your robots.txt disallows. If robots.txt can't be read, it reads only the page you gave.
What it creates#
| What it holds | |
|---|---|
| Glossary | Your own brand, company, and product names, kept as written in every language, plus feature and UI names with the translation your site already uses. Other companies' products and standards are left out - translations keep those as written anyway. |
| Rules | Conventions your content shows, each scoped to every target locale it applies to. |
| Brand voice | Tone, formality, register, and how readers are addressed: one text for every target locale, plus a locale's own text only where your content calls for something different. |
Content is written for the engine's languages. Each one is a new glossary, ruleset, or brand voice attached to the engine - provisioning never edits or merges into one the engine already applies:
- Fill missing context fills only what the engine has nothing attached for. An attached glossary with no terms counts as present.
- A new glossary or ruleset is attached next to the engine's current ones.
- A brand voice is never replaced. If the engine already applies one, it's skipped.
Progress and retries#
Filling runs in the background. Progress shows what's happening with the glossary, ruleset, and brand voice, and you can leave the page while it runs: the job continues and stays visible across the app. An engine runs one job at a time.
When the job finishes, each part is done, skipped with a reason, or failed. Retry starts a new job that refills only the parts that failed, from the same website.
Daily limit
An organization can start up to 10 provisioning jobs in 24 hours, retries included.
Review what was generated#
Treat the result as a first draft. Read the new glossary terms, rules, and brand voice texts, remove anything that doesn't fit, and test a representative sample in the Playground before relying on it for important content.