Integrations
Verbi supports WordPress sites. Your site, theme, and plugins stay exactly as they are — there's no translation plugin to install, no database changes, and no extra load on your server. Translation is handled entirely at the proxy layer.
How It Works with WordPress
Verbi sits between your visitors and your WordPress host. Instead of your domain pointing straight at WordPress, it points to Verbi's proxy. Verbi fetches your site from your WordPress host, translates it, and serves the result — with full SEO, edge caching, and a language switcher.
Because Verbi runs in front of WordPress rather than inside it, nothing is added to your installation: no plugin to maintain, no compatibility issues with your theme or page builder, and no performance tax on every request.
Setup
1. Find Your WordPress Origin Hostname
Verbi needs an address to fetch your original site from that is separate from the domain you'll point at Verbi (your main domain will point to the proxy, so it can't also be the origin). You have two options:
- Managed WordPress hosts usually provide a built-in hostname — for example
yoursite.wpenginepowered.comoryoursite.kinsta.cloud. Use that as your origin. - Otherwise, create an origin subdomain: add a DNS record like
origin.yoursite.compointing to your WordPress server, and use that. This lets Verbi reach WordPress while your main domain points to Verbi.
2. Add Your Site in Verbi
Go to your Verbi dashboard and click New Site. Enter your custom domain (e.g. yoursite.com) and select your target languages. In the Origin hostname field, enter the WordPress origin hostname from step 1.
3. Update DNS
Point your domain to Verbi's proxy instead of your WordPress host. In your DNS provider, add:
| Type | Name | Target |
|---|---|---|
CNAME | yoursite.com | proxy.verbi.io |
If your domain currently points to your WordPress host, replace that record with this one.
Keep the origin hostname from step 1 pointing at your WordPress server. Only your main domain moves to Verbi — if the origin record changes too, Verbi can't reach WordPress to fetch your site.
Your Setup tab also lists one or more TXT records to add — these issue your SSL certificate. Add every record shown and leave them in place. See DNS Setup for details.
4. Verify
Once DNS propagates, click Verify Connection in your Verbi dashboard. Your translated pages are live at yoursite.com/fr/, yoursite.com/de/, and so on.
WordPress-Specific Notes
Works Alongside Your Plugins
Verbi never touches your WordPress install, so it coexists with any theme, page builder (Elementor, Bricks, Gutenberg), or SEO plugin (Yoast, Rank Math). There's no plugin to keep compatible and nothing to update.
WooCommerce
Verbi translates the rendered HTML of your pages, so WooCommerce product pages, category archives, and checkout copy are all translated automatically. Prices and currency are left unchanged — those stay handled by WooCommerce.
Excluding Paths
You can exclude any path — like /wp-admin, /cart, or /checkout — so only the pages you want translated are served in other languages. See Glossary & Exclusions.
Language Switcher in WordPress
The easiest option is Verbi's built-in floating widget, which requires no changes to your site.
If you'd rather build your own selector in your theme, disable the built-in widget in Settings → Behaviour and add links to the translated URLs manually. The pattern is always /{lang-code}/{path} — for example, /fr/ for French and /de/ for German.
Publishing Updates
Whenever you publish changes in WordPress, Verbi picks them up automatically on the next request. If you want translated pages to reflect changes immediately, purge the cache from your dashboard after publishing.