Website translation should fit the ownership of the site
A WordPress team can install a plugin. Another client may prefer a reverse proxy because the agency controls DNS, while a smaller integration may use a client-side script. These paths have different setup work and different tradeoffs; calling them all an “integration” hides the decision an operator actually has to make.
LangRelay exposes delivery options in the project. The WordPress plugin is the proven native path. Generic web projects can use client-side delivery or configure proxy and custom-domain routing with the relevant script or DNS instructions.
Keep handoff details visible after launch
The domains screen records more than the initial configuration. It shows the selected mode, custom domains, verification records, and certificate state so the next person does not have to reconstruct how translated traffic reaches the site.
Delivery also connects directly to the visible product surfaces. The same project owns its languages, switcher configuration, localized slugs, and SEO fields. That gives an agency one place to check both sides of the launch: the translated content and the route that serves it.
