SeaText AI on Multiple Odoo Websites: Limitations and Workarounds

The main limitation is the one-account-per-domain rule. SeaText AI links each account to a single primary URL, so if you run several Odoo websites, you need a separate SeaText AI account and a separate JavaScript snippet for each one. Development domains like localhost are blocked, and dynamic development URLs may not work reliably. Plan to set up each site individually and give each one its own account.

What is actually limited?

SeaText AI does not provide a single account that manages all your Odoo domains in one place. The integration page is explicit: “Each SEATEXT AI account is linked to a single primary URL.” That means the number of websites you can run equals the number of accounts you create.

There are no documented API rate limits or plan-specific site quotas in the integration instructions. The main constraint is architectural. One account, one website URL. If you try to use one account on two domains, you break the way the system associates traffic.

Why the one-account rule exists

SeaText AI’s agents analyze visitor reading, rewrite copy, and track conversions. To do that, they need to know which website each visitor is on. A single primary URL gives the system a clear home for that data.

If two Odoo sites point to one account, the system cannot cleanly decide which domain owns the traffic. The result is mixed data, confusing reports, and optimization decisions based on the wrong audience. The one-account rule is not a sales trick; it keeps attribution clean.

What changes if you ignore it? You may see no activity on one site, or you may see the same activity repeated on both. Corrective action is simple: give each domain its own account and install the matching snippet.

How the Odoo integration works

The integration is installed through Odoo’s Website module. Here are the steps from the official SeaText AI Odoo integration guide:

1. Create a SeaText AI account for your Odoo domain.
2. Copy the JavaScript snippet from that account.
3. In Odoo, open the Website module and go to the page you want to edit.
4. Drag the “Embed Code” block from the “Dynamic Content” section.
5. Paste the snippet into the block and save.
6. Set the block to “Hide on Desktop” so visitors do not see it.

Repeat this process for every Odoo website. Each site needs its own account and its own snippet. The source also notes that the installation is secure and the AI remains inert until activated, so placing the code does not change your content by itself.

Development domains and dynamic URLs

The integration instructions place a hard restriction on development URLs. “Development URLs, such as localhost, are restricted for security reasons.” This matters if you use a staging or test Odoo site.

Dynamic development domains are a separate problem. The source says they “may not function properly, as SEATEXT AI might be unable to reliably associate traffic with your account.” Temporary URLs change, so the system loses the thread of which visitors came from where.

Workaround: Use a real, stable domain for each Odoo site. If you need a staging environment, try a subdomain like staging.yourcompany.com on a properly registered domain. Then create a separate account for that domain if you want SeaText AI to run there. Avoid localhost and throwaway URLs whenever possible.

Common symptoms and how to diagnose them

If you see any of the following, the cause is usually the one-account-per-domain rule:

• Two Odoo websites under one account show the same traffic or no traffic.
• Code is installed on a development domain, but no activity appears in the dashboard.
• Changes made in one site’s account affect the wrong site or appear to do nothing.

To diagnose, check the primary URL in each SeaText AI account. Confirm that each Odoo site has its own snippet copied from its own account. Also check that the domain is a real domain, not localhost or a temporary development URL.

Step-by-step plan for multiple Odoo sites

Use this framework before you start installing code:

1. List every Odoo domain you want to use, including staging and live.
2. Create one SeaText AI account for each domain.
3. Make sure every domain is a valid, real domain. Avoid localhost.
4. Install the snippet in each Odoo site via the Embed Code block.
5. Verify each site appears in its own account dashboard.
6. If a site stops showing data, re-check which snippet is installed there.

This is a manual process by design. There is no bulk installation or single-account multiplier in the documented integration.

Key facts at a glance

Frequently asked questions

Can I use one SeaText AI account for two Odoo websites?

No. According to the integration instructions, you need one account for each website. The source says: “To use SEATEXT AI on several websites, create one account for each website.”

Is localhost allowed for testing?

No. Development URLs such as localhost are restricted for security reasons. Use a real domain instead.

What happens if I use a dynamic development domain?

SeaText AI may not reliably associate traffic with your account. Dynamic development domains are supported, but not guaranteed to work. For reliable testing, use a stable subdomain on a real registered domain.

Do I need to install the code on every page of a single Odoo site?

No. The integration guide shows you how to place the Embed Code block on a page in the Website editor. The JavaScript snippet is copied from your SeaText AI account and pasted into that block. You hide the block on desktop so visitors do not see it. Follow the guide for the recommended placement.

Does the integration work with Odoo 19?

The integration page does not list a version restriction. It refers to the Website module and the Embed Code block, which are standard in current Odoo releases. If you are unsure, check the integration page or contact SeaText support before starting.

When this advice does not apply

If you only have one Odoo website, the one-account rule does not affect you. The same is true if you have a second site that never runs SeaText AI. The restrictions only matter when you want SeaText AI active on more than one domain.

If you use one domain but need to track multiple language versions or subpaths, that is a different scenario. The documented limitation is about primary URLs, not about pages or subdirectories. Treat each distinct website domain as a separate account.

Plan for the account overhead. Separate accounts mean separate snippet installations, separate dashboards, and separate setup efforts. That is the trade-off for clean tracking on every Odoo website.