Website delivery

Choose how translated pages reach the web.

Use the WordPress plugin, add the client script, or configure proxy and custom-domain delivery with setup details and connection status in the project.

Start translating free See LangRelay in action

Free to start. No credit card required.

Domains and delivery

LangRelay domains screen with website translation delivery options and DNS status

Why it matters

One part of the same operating loop: detect, translate, review, publish, and check the result.

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.

Fit the existing site

Make the delivery path an explicit project choice.

The right setup depends on who controls the CMS, DNS, and page runtime, so LangRelay keeps each path visible instead of pretending every stack is the same.

Start with the site you have

Use the WordPress plugin for the proven native path, or choose a generic web delivery option.

Keep languages project-scoped

Connect the same project language settings to the URLs and switcher visitors use.

Share a bounded setup

Give a developer the script snippet or give the domain owner the DNS records required for the chosen path.

See connection status

Track custom domains, verification records, and certificate state from the project screen.

Keep SEO beside delivery

Review localized paths and metadata as part of the same setup that serves translated pages.

Tuskara

Our rugs and wallcoverings sell on how they feel in a room, not on copy — so the last thing we wanted was translation that flattened that. LangRelay picked up our tone in every language automatically, and we didn't have to manage a single spreadsheet of strings to get there.