Installation recipe — site test required

Website translation & localization for Carrd

One translation dashboard for Bubble apps, WordPress and public websites. Choose a platform-specific installation, protect customer data and control your wording with AI-assisted translation and reusable Cloudflare caching.

Public-page script

Choose your platform Platform guide

Translate public headings, navigation, labels and dynamic content. Installation depends on your platform, plan, theme and access to the top-level page. A code recipe is not a claim that a native marketplace app is released.

Tested on the documented demo, not a guarantee for every theme, extension or private page. Follow the acceptance checklist on your own staging site.

1. Installation

Create a GoLocal project for the published site domain and select this platform. Use its public project API key, not a provider or database secret. Add one loader using the location below; never install both the plugin and a second generic loader. Test on staging before publishing.

Add element → Embed → Code → Hidden → Body End

<script defer src="https://goinglocal.online/plugin/golocal-web-1.2.2.min.js"
  data-golocal data-key="YOUR_PROJECT_KEY"></script>

Official platform documentation ↗

2. Protect customer data

Form values and contenteditable rich-text editors are not rewritten. Saved customer names, comments and descriptions still need explicit exclusion where displayed. Mark their container with data-tr-skip, translate="no" or class="notranslate"; descendants are excluded too. Keep translatable labels outside it. Do not send private page content to translation providers.

<span>Source name</span>
<span data-tr-skip>Travail à domicile</span>

<!-- Equivalent whole-container exclusions: -->
<div translate="no">Customer-entered content</div>
<div class="notranslate">Customer-entered content</div>

3. Translation Editor

Review AI wording in the Translation Editor. Manual corrections take priority over automatic translations. Open pages poll for updated translation bundles; changes appear asynchronously, not necessarily in the same second. A network failure keeps the original text visible instead of hiding it repeatedly.

4. Test before release

Switch English → French → English. Check menus, popups, delayed content and mobile layout. Type accented text into forms and rich-text editors, save and reopen it: the stored value must match. Check excluded customer names, selection values and filters. Edit one manual translation and confirm every matching visible instance updates. Test slow or failed requests: originals must remain visible.

5. Multilingual SEO

The widget changes the visible client-side interface. It does not create localized URLs, translate server-rendered HTML, checkout or email, or guarantee search rankings. For indexed language pages, use your platform’s native localization with dedicated URLs, self-canonicals and reciprocal hreflang. Do not run two translators over the same content.

6. Disable & roll back

Remove the single loader or disable the plugin, then publish and clear your platform’s page cache. Your original content and database values remain unchanged. Keep a theme/template backup and check language controls and normal forms again after removal.

Plans & limits

The plugin or loader is free to install; GoLocal service usage is a separate subscription. Starter $15/month, Pro $35/month, Business $89/month. The same plans apply across platforms. Platform hosting/custom-code charges are separate. Trial: 5 days, 500 MAU; paid plans have visitor and project limits, not word-based pricing.