1. Choose pages
Select the published pages you want to translate. FunnelLingo suggests the audience, page purpose, voice, and names to protect.
Documentation
Translate with context. Publish with control. Prepare language drafts, protect human-approved wording, and publish a visitor language switcher without collecting form submissions.
Get started with the pages you already run.
Use the getting-started guide in the app, then return here for review, publishing, and recovery details.
Select the published pages you want to translate. FunnelLingo suggests the audience, page purpose, voice, and names to protect.
Add the FunnelLingo switcher to the selected pages, save your changes, and visit each published page once so phrases can load. Plans with managed updates then prepare the translation.
Confirm the website and publish the visitor language. Ready phrases go live; the rest stay in the source language until they are translated. The first publish is yours.
Approve phrases you want to lock. Review is optional and does not block publishing.
Use this table instead of treating every launch idea as a live feature.
| Capability | Status | Notes |
|---|---|---|
| Contextual translation of authored page copy | Available | Installed workspaces review and publish in the dashboard. |
| Human-approved wording stays locked | Available | Source changes return affected copy to review. Automation cannot silently overwrite approved text. |
| Visitor language switcher | Available | Runs on the original page. Form entries stay untranslated. |
| Monitor, Assist, and Autopilot policies | Available | New projects default to Autopilot. The first publish is always yours. Wording review is optional and does not block publishing. Managed ongoing updates require a plan that includes them. |
| Domain setup through TapTapDNS | Included | DNS, hostname, and certificate status stay separate. No extra marketplace install is required for domain setup. |
| Language pages on a connected hostname | Available | Multilingual SEO is included. Publish approved language pages after the connected address and certificate are ready. Search indexing is currently disabled; activation follows project verification and approval. Rankings are never guaranteed. |
Authenticated /agent/v1 | Available | Same review and publish rules as the dashboard. Unauthenticated calls return 401. |
Your selected plan sets the language, translation, project, address, and published-page allowances. View the current allowance in your dashboard. Agency plans share translation words across separately licensed client accounts; other limits apply to each client account.
Each page in each target language uses one URL slot, even before indexing is enabled. Republishing an existing URL does not add another slot. At a translation limit, new machine work pauses. Existing entitled pages, human edits, and republishing within capacity remain available. Domain connection is included; domain registration is separate.
Each phrase includes its page purpose, nearby text, protected terms, and placeholders. You can refresh unapproved drafts. Approved wording stays locked until a reviewer reopens it.
Check selected pages and report changes. You start translation and publishing.
Translate new or changed machine-owned copy after a page check confirms it. You review exceptions and publish.
Update a language you already published when every safeguard passes. Human-approved wording stays protected. After the first publish, Autopilot can refresh eligible pages when all checks pass, on a plan that includes managed updates.
The first publish is always yours. An account administrator can change the policy at any time in Project settings.
When a project uses a dedicated language address, FunnelLingo reports DNS, hostname, and certificate progress separately. Authoritative DNS can be correct while a certificate is still pending. Do not change a record that already matches the shown plan just because the certificate is not ready yet. TapTapDNS owns the DNS connection; FunnelLingo owns hosting, certificates, translated copy, and publication.
Multilingual SEO is included. Connect a language address, review translated page titles and descriptions, and publish approved pages after the address and certificate are ready. Search indexing is currently disabled; activation follows project verification and approval. Rankings are never guaranteed. Language annotations and multilingual sitemap publication are included in verified activation. The visitor switcher also works on the original page.
Installed workspaces can inspect, draft, review, publish, and restore through the dashboard or the authenticated /agent/v1 API. The same ownership protections apply either way. See the developer guide for the widget snippet and API notes.
You can keep the existing google_translate_element container and its setup function. Remove the Google loader script, then load FunnelLingo in its place:
<script
src="https://cdn.funnellingo.com/widget/v1.js"
data-funnellingo-project="PROJECT_PUBLIC_KEY"
data-funnellingo-google-widget="replace"
defer></script>Replace PROJECT_PUBLIC_KEY with the public key shown in the project’s Publish view. FunnelLingo reuses the container, source-language hint, included and excluded language lists, and compact layout when it can read them safely. The enabled project languages remain the final authority.
Do not leave the Google loader on the page. If FunnelLingo detects Google translation code or an active Google translation, it leaves the existing control and page copy unchanged instead of running both translators.
FunnelLingo translates only the words a business publishes. It does not translate anything visitors type or pull in contact records. If a translation cannot load, the original language remains available.
Read the Privacy Policy, Terms of Service, and data-deletion steps. Send privacy requests to [email protected].