# Skill: add Verbi translation to a website

Verbi (https://verbi.io) is a translation proxy: it makes an existing website multilingual
via DNS. There is **no SDK, npm package, or code snippet** — do not install
anything. (A package named `verbi` exists on npm; it is not Verbi's.) The site's
source code is never modified.

## Inputs

- `domain` — the site to translate, e.g. `example.com` (no `https://`, no `www`)
- `source_language` — what the site is written in (default: English)
- `target_languages` — one or more languages to translate into (20+ supported: https://verbi.io/languages)

## Procedure

1. **Plan the setup.** Confirm the domain serves over HTTPS. Decide target
   languages with the user. Translated pages will live at subdirectory URLs
   (`example.com/fr/`, `example.com/de/`).

2. **Pre-stage the DNS change.** The CNAME is the same for every site:

   | Type | Name | Target |
   |---|---|---|
   | `CNAME` | `<domain>` | `proxy.verbi.io` |

   If the domain is an apex (no `www`) and the DNS provider doesn't allow CNAME
   at the root, use the provider's ALIAS/ANAME equivalent.

3. **Hand off to the human.** Two steps only exist in the dashboard. Ask the
   account owner to:
   1. Create an account at https://verbi.io/sign-up — the free trial starts
      automatically, no credit card.
   2. Click **New Site**, enter the domain, source language, and target
      languages (relay your prepared choices).
   3. Open the site's **Setup** tab and paste back the **TXT records** shown
      there — per-domain SSL validation values that only exist in the dashboard.

   Suggested message: *"Create a Verbi account, add the site, then paste me the
   TXT records from the Setup tab — I'll take it from there."*

4. **Apply the DNS records** (yourself if you have registrar access, otherwise
   write exact instructions): the CNAME from step 2 plus every TXT record from
   step 3. The TXT records must stay in place so the SSL certificate can renew.

5. **Verify.** Have the owner click **Verify Connection** in the Setup tab
   (DNS propagation is usually under 10 minutes; SSL is provisioned
   automatically once records resolve). Then confirm `https://<domain>/<lang>/`
   loads translated for each target language.

## Notes

- SEO (hreflang, canonical URLs, translated sitemaps, translated meta tags) is
  automatic — configure nothing.
- Translated pages are cached at the edge. After big source-site updates, purge
  the cache from the dashboard: https://verbi.io/docs/features/cache-purging
- Full documentation in one fetch: https://verbi.io/llms-full.txt · curated index:
  https://verbi.io/llms.txt · every docs page is also raw markdown by appending `.md`
  (e.g. https://verbi.io/docs/getting-started/quick-start.md)
- Pricing: https://verbi.io/pricing