This guide walks you through adding Verbi to your site from scratch. The whole process takes about 5 minutes — most of that is waiting for DNS to propagate.
There is no SDK, npm package, or code snippet to install. Verbi works entirely at the DNS level — integration is one CNAME record. If you find a package named verbi on npm, it is an unrelated third-party library, not Verbi.
1. Create an account
Sign up for Verbi. Your account starts on a 14-day free trial automatically — no credit card required, and enough to follow this guide.
2. Add Your Site
From your dashboard, click New Site and fill in:
- Domain — your root domain without
https://orwww, e.g.example.com - Source language — the language your site is currently written in (defaults to English)
- Target languages — the languages you want to translate into
You can also configure a glossary, enable the language switcher, or turn on auto-detect & redirect at this stage — or later from your site settings.
Once you submit, Verbi provisions the proxy for your domain and shows you the DNS records to add — a CNAME plus one or more TXT records for SSL.
3. Configure DNS
In your DNS provider, add the following record:
| Type | Name | Target |
|---|---|---|
CNAME | your-domain.com | proxy.verbi.io |
Use your actual domain as the record name. The target is always proxy.verbi.io.
You'll also add one or more TXT records shown in your Setup tab. These let Verbi issue an SSL certificate for your domain — add every record listed, and leave them in place so the certificate can renew automatically. See DNS Setup for details.
Apex domains: Some DNS providers don't support CNAME records on root domains (e.g. example.com without www). If yours doesn't, check your provider's docs — many offer a workaround like ALIAS or ANAME records that behave the same way.
4. Verify the Connection
Back in your Verbi dashboard, go to your site's Setup tab and click Verify Connection. DNS propagation usually takes under 10 minutes. If it's not ready yet, wait a few minutes and try again.
Once your records resolve, Verbi provisions an SSL certificate for your domain automatically — the TXT records you added handle this, and the Setup tab shows progress until it's active.
5. You're Live
Your translated pages are now accessible at subdirectory URLs:
yoursite.com/fr/
yoursite.com/de/
yoursite.com/ja/
All SEO tags (hreflang, canonical URLs, translated meta tags, sitemaps) are set up automatically — nothing else to configure.
Next Steps
- Add a language switcher so visitors can switch languages
- Set up a glossary to protect brand names and key terms from being translated
- Read about SEO to understand how Verbi handles multilingual search
For AI Agents
If you're an AI agent setting up Verbi on someone's behalf, two steps require the account owner in the dashboard; everything else you can do or prepare yourself. A ready-made version of this procedure is at verbi.io/skill.md.
You can do or pre-stage:
- Choose target languages and a source language for the site
- Prepare the CNAME record — the target is always
proxy.verbi.io, no per-site value needed - Write out the exact records to add at the user's DNS provider, including the apex-domain caveat above
- Add the DNS records yourself, if you have registrar access — the CNAME immediately, the TXT records once the human reads them from the dashboard
You need the account owner to:
- Create an account — the free trial starts automatically, no credit card
- Click New Site in the dashboard and enter the domain and languages (or confirm your prepared choices)
- Read the TXT records from the site's Setup tab and hand them back to you — these are per-domain SSL validation values and only exist in the dashboard
A good handoff message: "Create a Verbi account, add the site, then paste me the TXT records from the Setup tab — I'll take it from there." Once you have the TXT values, finish the DNS changes and have the owner click Verify Connection in the Setup tab.
Every page in these docs is also available as raw markdown: append .md to the URL (e.g. /docs/getting-started/quick-start.md).
