Can I Use SeaText AI on an Odoo.sh Hosted Website?
Yes, SeaText AI works on Odoo.sh. You add the JavaScript snippet through Odoo's built-in Embed Code block in the website editor, just as you would on any Odoo instance. No custom module or server-side...
Yes, SeaText AI is fully compatible with Odoo.sh. The integration uses Odoo's standard Embed Code block, which is available in the website editor on Odoo.sh exactly as it is on self-hosted or Odoo Online instances. You paste the SeaText JavaScript snippet into that block, save, and the AI agents begin working once you activate them in your SeaText dashboard.
What Odoo.sh Is and Why the Integration Works
Odoo.sh is Odoo's managed cloud platform. It runs the same Odoo codebase as self-hosted and Odoo Online deployments, but Odoo handles the infrastructure, backups, updates, and staging branches. Because the website module and its Embed Code block are part of the core Odoo application, they function identically on Odoo.sh. There is no separate "Odoo.sh website builder" — it is the standard Website module running on Odoo's servers.
SeaText AI integrates by injecting a single JavaScript file into your pages. That script loads from SeaText's edge network, reads the page content, and communicates with SeaText's APIs to run its 20 autonomous agents (conversion optimization, translation, bot protection, AI SEO, and more). Since the injection happens client-side via the Embed Code block, the hosting environment does not need to allow custom modules, server-side scripts, or SSH access.
How the Embed Code Integration Works
The integration steps documented by SeaText for Odoo apply directly to Odoo.sh:
- Log in to your Odoo.sh database and open the Website app.
- Navigate to the page you want to edit (usually the homepage or a landing page) and click Edit.
- In the Blocks panel, scroll to the Dynamic Content section and drag the Embed Code block onto the page.
- Click the Edit button on the placed block to open the code input window.
- Paste the JavaScript snippet provided by SeaText AI into the designated area and click Save.
- Optionally, enable Hide on Desktop in the Visibility section if you want the block invisible to visitors while the script still loads.
- Save the page again.
Once the page is published, the SeaText script loads on every page that includes that block. If you place the block on a global layout element (header or footer), it will load site-wide. On Odoo.sh, you typically edit the master layout via Website → Configuration → Layout or by editing the header/footer structure directly in the editor.
Key Facts at a Glance
| Aspect | Detail | Source |
|---|---|---|
| Integration method | Embed Code block in Odoo Website editor | S1 |
| Custom module required | No | S1 |
| Server-side access needed | No | S1 |
| Script visibility | Can be hidden via "Hide on Desktop" option | S1 |
| Multi-domain support | Separate SeaText account per primary domain | S1 |
| Development domains | localhost and dynamic dev domains restricted | S1 |
Odoo.sh Specific Considerations
Staging and Production Branches
Odoo.sh uses Git branches for staging, development, and production. When you add the Embed Code block on a staging branch, the change is part of the database and code state for that branch. Merging to production carries the block forward. However, SeaText ties each account to a single primary URL. If your staging branch uses a different domain (e.g., staging-myproject.odoo.com), you will need a separate SeaText account for that domain, or you can wait to activate until the code reaches your production domain.
Asset Cache and Deployment
Odoo.sh rebuilds assets on each deployment. After you save the Embed Code block, the change is stored in the database. The next time Odoo.sh builds the production environment, the script will be included. You do not need to clear a separate asset cache manually; the platform handles it during the build. If you do not see the script loading immediately after saving, wait for the current deployment to finish or trigger a new build from the Odoo.sh dashboard.
Content Security Policy (CSP)
Odoo.sh does not impose a restrictive CSP by default. If your project has a custom CSP header (added via a custom module or Cloudflare configuration), ensure it allows script-src from SeaText's domain (https://seatext.com and its CDN endpoints). Without this, the browser will block the script.
Comparison: Odoo.sh vs. Self-Hosted vs. Odoo Online
| Factor | Odoo.sh | Self-Hosted | Odoo Online |
|---|---|---|---|
| Embed Code block available | Yes | Yes | Yes |
| Custom module installation | Allowed (via Git) | Full control | Not allowed |
| Server-side script injection | Not needed | Possible | Not possible |
| Staging environment | Built-in branches | DIY | Limited (duplicate database) |
| SeaText account per domain | Required | Required | Required |
Takeaway: For SeaText AI, all three hosting options are equivalent because the integration is purely client-side. Choose your hosting based on other needs (custom modules, infrastructure control, cost), not SeaText compatibility.
Common Issues and How to Verify
Script Not Loading
- Open the page in an incognito window.
- Open Developer Tools → Network tab.
- Filter for "seatext" or "js".
- If the request returns 200, the script is loading. If 404 or blocked, check the Embed Code block content and any CSP errors in the Console tab.
SeaText Dashboard Shows No Data
- Confirm the domain in your SeaText account matches the live domain exactly (including
wwwvs. non-www). - Visit the site yourself and perform a few actions (scroll, click).
- Wait 5–10 minutes; data appears in the SeaText dashboard after the first sessions are processed.
Staging Domain Shows Errors
If you added the script on a staging branch with a different domain, the SeaText script will load but the dashboard will reject events because the domain does not match the account's primary URL. This is expected. Either create a separate SeaText account for the staging domain or accept that staging traffic will not appear in your production dashboard.
Limitations and When This Advice Does Not Apply
- Odoo versions before 14: The Embed Code block exists in v14+. Very old Odoo.sh projects on v12 or v13 may need a different approach (custom template edit).
- Headless Odoo setups: If you use Odoo.sh only as a backend API and serve the frontend via Next.js, Nuxt, or another framework, the Embed Code block is not used. You would add the SeaText script to your frontend build instead.
- Strict CSP without control: If your organization enforces a CSP you cannot modify, you cannot load third-party scripts. SeaText cannot bypass browser security policies.
- Multiple websites on one Odoo database: Each website (domain) needs its own SeaText account. The Embed Code block must be added to each website's pages separately.
Terminology Quick Reference
- Embed Code block: A standard Odoo Website block that accepts raw HTML/JS and renders it on the page.
- Primary URL: The single domain a SeaText account is licensed for. Traffic from other domains is ignored.
- Edge script: SeaText's JavaScript file served from a global CDN (Cloudflare) for low latency.
- Autonomous agents: SeaText's 20 AI modules (conversion, translation, bot refund, AI SEO, etc.) that run automatically once the script is active.
- Odoo.sh branch: A Git branch (staging, production, feature) that maps to a running Odoo instance with its own database and domain.
Frequently Asked Follow-Up Questions
Do I need a separate SeaText account for each Odoo.sh branch?
Only if each branch uses a different domain. If your staging branch runs on staging-example.odoo.com and production on example.com, you need two accounts. If you use the same domain with a subpath or host header, one account suffices.
Can I use SeaText AI on Odoo.sh's free trial databases?
Yes, as long as the trial database has a real, publicly accessible domain (not localhost or a dynamic tunnel). SeaText restricts development URLs for security.
Will SeaText slow down my Odoo.sh site?
The script loads asynchronously from a CDN with zero redirect latency. SeaText claims 0ms flicker for its split-testing agent. In practice, the script is under 50 KB gzipped and does not block rendering.
What happens when Odoo.sh upgrades the Odoo version?
Upgrades are managed by Odoo.sh. The Embed Code block and your saved snippet persist through upgrades because they are stored in the database, not in code files.
Can I control which pages load SeaText?
Yes. Place the Embed Code block only on the pages or layout sections where you want it active. For site-wide coverage, add it to the global header or footer layout.
Is there an Odoo app/module for SeaText?
No. SeaText does not distribute an Odoo module. The Embed Code method is the supported integration for all Odoo hosting types.
Where do I get the JavaScript snippet?
After creating a SeaText account and adding your domain, the snippet appears in the SeaText dashboard under Integration → JavaScript. Copy it from there.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
How SeaText AI Helps on Odoo.sh
SeaText AI adds 20 autonomous agents to your Odoo.sh website without any server-side changes. The conversion agent rewrites landing page copy in real time to match each visitor's search intent. The translation agent serves 125 languages from a single script. The bot protection agent detects and refunds fraudulent ad clicks. The AI SEO agent publishes thousands of indexed Q&A pages that rank in Google and ChatGPT. All of this runs from the same Embed Code block you just added.
Requirement: You need a valid SeaText account tied to your production domain. Staging branches on different domains need their own accounts. The script loads asynchronously and does not affect Odoo.sh deployment pipelines.