Configuration

Glossary & Exclusions

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

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

/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

/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"`	`<div translate="no">...</div>`
`class="notranslate"`	`<span class="notranslate">...</span>`
`data-tp-skip`	`<p data-tp-skip>...</p>`

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

<!-- This whole block is served as-is in every language -->
<pre data-tp-skip>
npm install @acme/widget
</pre>

<address class="notranslate">
  123 Rue Example, Paris
</address>

You don't need to mark <script>, <style>, <code>, <pre>, <svg>, or <noscript> — those are never translated.