Same SeaText API Key on Multiple Odoo Domains? Use Separate Accounts Instead
No, you should not use the same SeaText API key or account for multiple Odoo domains. SeaText links each account to a single primary URL, so create a separate account for each domain and...
No. You should not use the same SeaText API key or account for multiple Odoo domains. SeaText links each account to a single primary URL. The correct setup is one SeaText account per domain, with that account's own code snippet installed on the matching website.
The good news is that adding a second domain is not a complex development project. You create a separate SeaText account for the new domain, copy its code, and paste it into Odoo's Embed Code module. The steps below show the exact process and how to verify it.
What changes if you reuse one SeaText key on multiple Odoo domains
If you paste the same integration code into two Odoo sites, SeaText cannot reliably know which site should count as the primary URL. Data from both sites can be mixed, and you may not be able to tell which page changes produced which result.
That is why the SeaText Odoo integration page says each account is linked to a single primary URL. The page also says dynamic development domains may not function properly because SeaText might be unable to reliably associate traffic with your account.
In practical terms, sharing a key across domains makes your reporting less trustworthy. You may think a change on one site caused a lift, but the traffic and reading data could actually be coming from the other site.
Before you start: prerequisites
- List every domain where you need SeaText. Treat production, staging, and separate brand or country sites as separate domains.
- Have access to your Odoo account and the Website module.
- Create a SeaText account for each domain. Each account is linked to one primary URL.
- Use a valid, real domain for each account. Development URLs such as localhost are restricted for security reasons.
- Keep each account's code snippet labeled by domain so you do not paste the wrong script.
How to install SeaText on multiple Odoo domains, step by step
- Create a SeaText account for domain A and set its primary URL to domain A.
- Copy the JavaScript code from that SeaText account.
- Log in to Odoo and access the Website module from the dashboard.
- Navigate to the page you want to edit and click the Edit button.
- Scroll to the Dynamic Content section in the Blocks panel.
- Find the Embed Code module and drag it into the desired location on the page.
- Click Edit in the right panel to open the code input.
- In the pop-up window, paste the SeaText code snippet and click Save.
- If the block should not appear on desktop, select Hide on Desktop in the Visibility section, then click Save again.
- Repeat the process for domain B using a separate SeaText account. Do not copy domain A's code into domain B.
How to verify the setup
Visit or refresh the page after saving the Embed Code module. Confirm the page still loads normally and the block is hidden on desktop if you selected that option.
Then confirm that the code pasted on each Odoo domain came from the account whose primary URL matches that domain. That is the main check. If you used a dynamic development domain, switch to a stable, valid real domain because dynamic development domains may not work reliably.
Your realistic options for multiple Odoo domains
Option 1: One SeaText account per domain
This is the setup SeaText describes. It keeps data separated and makes it easy to see which domain is sending traffic. The trade-off is that you have more accounts to manage.
Option 2: Use SeaText on only one domain
If a second domain does not need SeaText, do not install the code there. This avoids extra accounts and keeps reporting simple. The other domain simply does not get the same optimization.
Option 3: Confirm a special multi-domain setup with SeaText
The public Odoo integration page does not describe a way to link one account to multiple primary URLs. If you are told otherwise, ask how traffic is assigned before relying on it.
Scope: your SeaText account is not Odoo's external API key
The SeaText Odoo integration uses a JavaScript code snippet from your SeaText account. You paste that snippet into Odoo's Embed Code module. The same rule applies whether you call it an API key, an account, or a code snippet: one account per primary URL.
This is separate from Odoo's own external API, which developers use to connect other software to Odoo data through JSON-RPC or XML-RPC. Those are different credentials for a different purpose.
Key facts about SeaText and multiple domains
| Fact | What it means for you |
|---|---|
| Each SeaText account is linked to a single primary URL. | One account should serve one domain. Use a separate account for another domain. |
| If you need SeaText on multiple domains, you must create separate accounts for each domain. | There is no documented path to share one account or key across websites. |
| To use SeaText on several websites, create one account for each website. | This rule is not limited to Odoo. Every website gets its own account. |
| Development URLs such as localhost are restricted for security reasons. | Use a valid, real domain for testing, not localhost. |
| Dynamic development domains may not function properly. | Use a stable domain for staging or development instead of a randomly generated URL. |
Common mistakes and how to avoid them
| Mistake | Why it hurts | Fix |
|---|---|---|
| Reusing one account's code snippet on two domains | SeaText is tied to one primary URL, so data can be mixed. | Create a separate account for each domain. |
| Testing with localhost | localhost is restricted for security reasons. | Use a valid, real domain. |
| Using a dynamic development domain | SeaText may not reliably associate traffic with your account. | Use a stable development or staging domain. |
| Pasting the wrong account's code when you manage several accounts | The code may be attributed to the wrong primary URL. | Label each snippet by domain before pasting. |
Limitations and when this guidance does not apply
SeaText's public documentation does not describe a way to merge accounts or share one API key across multiple primary URLs. If you believe you have a special case, check with SeaText before assuming a workaround exists.
Subdomains are not covered in the source material. If two Odoo sites share the same root domain but use different subdomains, ask SeaText whether one account is enough.
If you only need SeaText on your production site, leave staging without SeaText or create a separate staging account. The source explicitly lists a development domain and a production domain as an example of when separate accounts are required.
Frequently asked questions
Can I use the same SeaText API key in Odoo and another website?
No. SeaText links each account to a single primary URL. Create one account for each website.
What happens if I paste the same code into two Odoo domains?
Data can be mixed or associated with the wrong URL. Use a separate account for each domain to keep reporting clean.
Is localhost allowed as an Odoo test domain?
No. Development URLs such as localhost are restricted for security reasons.
Do I need a separate SeaText account for staging?
If staging is a separate domain, yes. The SeaText documentation names development and production domains as a case where separate accounts are required.
Can a dynamic development domain work?
It may not. SeaText might be unable to reliably associate traffic with your account on a dynamic development domain.
Can I merge two SeaText accounts later?
The source documentation does not mention account merging. Contact SeaText to check your specific situation.
Does Odoo's external API matter here?
No. Odoo's external JSON-RPC or XML-RPC API is for connecting software to Odoo data. It is separate from the SeaText integration code you paste into a page.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.