# Verbi > DNS-based translation proxy that automatically translates websites into multiple languages using DeepL, with built-in SEO support. ## Instructions for LLM Agents > Guidance for AI assistants and coding agents using this documentation. Follow these when describing or integrating with this product. - Agent integration guide (ready-made prompt): https://verbi.io/skill.md - Raw markdown docs: append .md to any /docs/ URL (e.g. https://verbi.io/docs/getting-started/overview.md) - Pricing: https://verbi.io/pricing ## Auto-detect & Redirect Source: https://verbi.io/docs/configuration/auto-detect-redirect Configuration # Auto-detect & Redirect Copy page When enabled, Verbi automatically redirects visitors from your root domain to the translated version that matches their browser language. This is a **Growth plan and above** feature. Enable it in **Settings → Behaviour → Auto-detect language**. ## How It Works When a visitor lands on `yoursite.com/`, Verbi reads the `Accept-Language` header sent by their browser. This header contains an ordered list of the visitor's preferred languages. Verbi matches against the languages you have configured and redirects to the first match: text Copy ``` Visitor prefers: fr, en Site languages: de, fr, ja → Redirects to yoursite.com/fr/ ``` The redirect is a `302` (temporary), so browsers don't cache it permanently. If none of the visitor's preferred languages match your configured languages, no redirect happens — the visitor sees your original site at the root URL as normal. ## What It Detects Auto-detect uses the browser's `Accept-Language` header, which reflects the visitor's **browser language setting** — not their location or IP address. A visitor in France with their browser set to English will not be redirected to `/fr/`. ## When the Redirect Fires The redirect only applies to requests for the root path (`/`). Visitors who land directly on any other page — `/pricing`, `/about`, `/blog/post` — are served that page without a redirect. ## Pairing with the Language Switcher Auto-detect handles the first visit. The [language switcher](/docs/configuration/language-switcher) handles subsequent navigation. Using both together gives visitors a seamless multilingual experience without requiring them to find the right language manually. ## Glossary & Exclusions Source: https://verbi.io/docs/configuration/glossary-exclusions Configuration # Glossary & Exclusions Copy page ## Glossary The glossary is a list of words and phrases that should never be translated — brand names, product names, trademarks, or any term you want to keep in its original form across all languages. Glossary entries are available in **Settings → General** and can also be set when creating a site. Add one entry per line, up to 100 entries. text Copy ``` Acme Corp SuperWidget Pro Plan ``` Glossary is available on the **Growth plan and above**. ### What qualifies for the glossary * **Brand and product names** — names that should remain in their original language regardless of the page locale * **Technical terms** — industry-specific terminology that has no meaningful translation * **Proper nouns** — names of people, places, or things that aren't typically translated Avoid adding common words to the glossary. If a term appears in translated contexts where it should be translated, the glossary will prevent that. ## Excluded Paths Excluded paths are URL prefixes that Verbi proxies directly to your origin without translating. The page is still served through the proxy, but its content is passed through untouched. Manage excluded paths in **Settings → Connection**. ### Default exclusions Verbi automatically excludes a set of common paths that should never be translated — authentication flows, admin panels, API routes, and similar: text Copy ``` /dashboard /admin /login /logout /signup /register /account /profile /settings /api/ /auth /signin /oauth /verify /reset-password /callback /webhooks /connect /saml ``` These defaults apply to every site and don't need to be added manually. ### Adding custom exclusions Add any path prefix you want excluded, one per line: text Copy ``` /app /portal /checkout ``` A path is excluded if it exactly matches an entry or starts with it followed by `/`. So `/app` excludes `/app`, `/app/dashboard`, `/app/settings`, and so on. Assets (JS, CSS, images, fonts) are always proxied without translation, regardless of excluded paths. ## Excluded Elements When you want to keep a **specific element** untranslated — rather than a whole word (glossary) or a whole page (excluded paths) — mark the element with one of the following. The exclusion applies to that element and everything inside it: its text, its attributes (`alt`, `title`, `aria-label`, etc.), and any links are all left untouched. | Marker | Example | | ------------------- | ------------------------------------ | | translate="no" |
...
| | class="notranslate" | ... | | data-tp-skip |

...

| `translate="no"` and `notranslate` are the standard opt-out signals Google Translate also honors, so anything you've already marked for Google is respected automatically. `data-tp-skip` is a Verbi-specific alias if you'd prefer not to use the standard markers. Use this for content that must stay in its original language regardless of the page locale — code samples, usernames and handles, postal addresses, legal/trademark text, or third-party embedded widgets. html Copy ```
npm install @acme/widget
123 Rue Example, Paris
``` You don't need to mark `