How to switch from staging to production environment?
In this article, you'll learn how to switch from staging to production environment.
Translations in Weglot are linked to your project’s API key, not to your website, domain, or its status (staging or production).
1. I have a temporary URL that will change later
If you install Weglot on a staging website with a temporary URL (e.g. mymocksite123.hosting.com ) and plan to later switch to your own domain:
- No action is required. Weglot will continue working without affecting your translations or settings.
- Recommendation: Update your website URL in Weglot Dashboard > Settings > General so that the Visual Editor is synchronized with your final domain:
2. I'm already managing 2 different websites
If you have both a staging and production website with different URLs but identical HTML and content, you can choose between two approaches:
Option A — Single Project
- Configure Weglot on both staging and production environments using the same API key.
- Both websites will share the same translations and settings.
Option B — Separate Projects
- Create a dedicated Weglot project for each environment.
- Follow this guide: [How can I manage my project(s)?]
We recommend using separate projects if:
- The HTML or content differs between your websites.
- You want to manage different languages and/or settings on each website.
- You plan to use subdomain-based integration (see Section 3).
3. Additional information
If you are using or planning to use subdomain-based integration (fr.example.com , de.example.com , etc.):
- You must create one project per website/domain.
- Otherwise, you may encounter conflicts between translations and/or the translated versions of your site.
👉 To learn more about your current integration, see: How does Weglot manage SEO?