Yes — SeaText AI works on Odoo websites hosted on different servers

Short answer: server location doesn't matter

Yes, you can use SeaText AI on Odoo websites that live on different servers. SeaText AI doesn't install anything on your server. It works by injecting a small JavaScript snippet into your Odoo pages, and that snippet talks to SeaText's cloud over the public internet.

So whether your Odoo instance runs on Odoo.sh, a VPS in Frankfurt, a shared host in Texas, or a custom cloud setup, the integration works the same way. The only thing that matters is that the website is publicly reachable and you can paste the code snippet into the page.

How the integration actually works

SeaText AI's Odoo integration uses the Embed Code block that ships with Odoo's Website module. You don't need a custom module, a server-side plugin, or SSH access.

Here's the flow:

1. Log into your Odoo backend and open the Website module.
2. Navigate to the page you want to edit and click Edit.
3. Scroll to the Dynamic Content section in the Blocks panel.
4. Drag the Embed Code block onto the page.
5. Click Edit on that block and paste your SeaText AI JavaScript snippet.
6. Save the page.

Because this happens entirely inside Odoo's page editor, the hosting provider is irrelevant. The snippet loads in the visitor's browser, not on your server.

How the snippet interacts with Odoo page caching and CDN

Odoo often caches rendered pages to speed up delivery. The SeaText AI snippet is just JavaScript that runs in the browser after the page loads. Cached HTML still contains the snippet, so the AI activates normally.

If you use a CDN (like Cloudflare) in front of Odoo, the snippet passes through unchanged. The CDN caches the HTML with the snippet included. The browser then executes the snippet and contacts SeaText AI's API directly. No server-side changes are required.

However, if you enable aggressive HTML minification or script deferral, verify that the snippet still loads. Test by viewing the page source and checking for the SeaText AI script tag.

Performance implications for multi-server setups

Because the snippet runs client-side, your Odoo servers do not process SeaText AI logic. There is no added CPU or memory load on your application servers.

Each visitor's browser makes a direct HTTPS request to SeaText AI's cloud. Latency depends on the visitor's distance to SeaText AI's edge nodes, not on your Odoo server location. In a multi-server deployment (e.g., load-balanced Odoo instances), each server serves the same snippet. Performance is consistent across all nodes.

If you have many domains on different servers, each domain loads its own snippet. The snippets operate independently. There is no cross-server synchronization needed.

Security considerations when using a public API across different hosts

The snippet communicates with SeaText AI over HTTPS. Traffic is encrypted in transit. No secret keys are exposed in the snippet; the snippet contains a public account identifier.

Each domain has its own SeaText AI account. If one domain is compromised, the attacker only gains access to that account's data. Other domains remain isolated.

Ensure your Odoo sites serve pages over HTTPS. Mixed-content warnings can block the snippet. Also, configure Content Security Policy (CSP) to allow script-src from SeaText AI's domain (e.g., https://cdn.seatext.com).

SeaText AI restricts development URLs like localhost for security. Use a real domain or a staging subdomain that resolves publicly.

Trade-offs: client-side vs server-side integration

Client-side integration (SeaText AI's approach) means zero server installation. It works on any hosting, including shared hosts where you lack root access. The downside: the snippet adds a small JavaScript payload (typically < 50 KB gzipped) and an extra DNS lookup.

Server-side integration would require a custom Odoo module, Python dependencies, and server configuration. It could process data before sending to the browser, but it ties you to a specific hosting environment and adds maintenance burden.

If SeaText AI's cloud is unreachable, the snippet fails silently. Your Odoo page still loads and functions normally. No content is altered. Visitors see the original page. This fail-safe design prevents a third-party outage from breaking your site.

The one real limitation: one account per domain

Here's the catch that most people miss. Each SeaText AI account is linked to a single primary URL. If you want to use SeaText AI on multiple Odoo websites — even if they're on the same server — you need to create a separate SeaText AI account for each domain.

So if you have a production site at shop.example.com and a staging site at staging.example.com, those are two separate accounts. You can't just copy the same snippet to both.

What about development domains and localhost?

SeaText AI restricts development URLs like localhost for security reasons. The system needs to reliably associate traffic with your account, and dynamic development domains can break that association.

If you're testing on a local machine, use a real domain that points to your local server (like a tunnel or a staging subdomain) rather than localhost. That way SeaText AI can track the traffic correctly.

Practical scenarios for multi-server setups

Scenario 1: Production and staging on different hosts

You run production on Odoo.sh and staging on a DigitalOcean droplet. Create two SeaText AI accounts — one for each domain. Paste the correct snippet into each site. Both work independently.

Scenario 2: Multiple client sites on one shared server

You're an agency managing Odoo for five clients, all on one VPS. Each client has their own domain. Create five SeaText AI accounts — one per domain. Each client's site gets its own snippet.

Scenario 3: Same domain, different servers (migration)

You're moving an Odoo site from one host to another. The domain stays the same — so the same SeaText AI account keeps working. Just reinstall the snippet on the new server after the migration.

Common mistakes to avoid

• Reusing one snippet on multiple domains. This won't work. Each domain needs its own account and its own snippet.
• Testing on localhost. SeaText AI blocks development URLs. Use a real domain or a staging subdomain.
• Forgetting to hide the embed block on desktop. SeaText's integration guide recommends selecting Hide on Desktop in the Visibility section so the code block doesn't show up as an empty box on your live page.
• Assuming the snippet runs server-side. It doesn't. It runs in the visitor's browser, so the site must be publicly accessible.

When this advice doesn't apply

If your Odoo website is behind a firewall, requires VPN access, or isn't publicly reachable, SeaText AI won't be able to load the snippet. The same applies if you're using a private network or an intranet-only Odoo instance.

Also, if you're using a custom Odoo theme that removes the Embed Code block, you'll need to add the snippet manually via the theme's HTML editor or a custom module. The standard Website module includes the block, but custom themes can vary.

Troubleshooting common cross-server issues

1. Snippet not loading. Check browser console for 404 or CSP errors. Ensure the snippet URL is correct and HTTPS.
2. Content not changing. Verify the SeaText AI account is active and the domain matches exactly. Clear Odoo cache and browser cache.
3. Mixed-content warnings. Force HTTPS on your Odoo site. Update the snippet URL to HTTPS if needed.
4. CDN caching old snippet. Purge CDN cache after updating the snippet. Use cache-busting query parameter if necessary.
5. Multiple snippets on same page. Only one SeaText AI snippet per page. Remove duplicates.
6. Domain mismatch after migration. Update the primary URL in SeaText AI dashboard or create a new account for the new domain.

FAQ

Do I need to install anything on my Odoo server?

No. The integration is purely client-side. You paste a JavaScript snippet into a page using Odoo's built-in Embed Code block.

Can I use one SeaText AI account for multiple domains?

No. Each account is linked to a single primary URL. You need a separate account for each domain.

What if my Odoo site is on Odoo.sh?

That works fine. Odoo.sh is just another hosting provider. The snippet loads in the browser, so the hosting platform doesn't matter.

Does SeaText AI work with Odoo Community Edition?

Yes, as long as the Website module is installed. The Embed Code block is part of the standard Website module in both Community and Enterprise editions.

What happens if I change my domain later?

You'll need to update the account to point to the new domain, or create a new account. The snippet is tied to the account, not the server.

Is there any performance impact from the snippet?

The snippet loads in the visitor's browser. SeaText AI states the AI remains inert until activated, so it doesn't alter your content until you turn it on.

What if SeaText AI's cloud goes down?

The snippet fails silently. Your Odoo page loads normally with original content. No functionality is lost.