Direct Answer: Manual Injection Is the Only Supported Path

SeaText's official Odoo integration guide shows one method: drag the Embed Code block from the "Dynamic Content" section into your page, paste the SeaText JavaScript snippet, enable "Hide on Desktop" in visibility settings, and save. There is no SeaText-published Odoo module in the Odoo App Store or on the SeaText site. Any third-party module you find is community-maintained and not covered by SeaText support.

Manual injection takes under two minutes, requires no developer skills, and survives Odoo version upgrades because it uses core Website builder features. A dedicated module would introduce an extra dependency, potential version conflicts, and an additional update cycle — all for a task that is already a single copy-paste step.

Takeaway: Every row favors the official manual method. The only reason to consider a module is if your team forbids any JavaScript in the UI — but then you would need a custom technical solution anyway.

How the Official Manual Injection Works

Log in to your Odoo account and open the Website module from the dashboard. Navigate to the page you want to edit and click the Edit button to open the editing panel.

In the editing panel, scroll through the Blocks panel until you reach the Dynamic Content section. Locate the Embed Code module within that section and drag it into the desired location on your website editor.

Once the module is placed, click the Edit button located in the right panel to input the code. In the pop-up window that appears, paste the code snippet provided by SEATEXT AI into the designated area, then click Save to apply the changes.

To ensure the block is hidden from view on desktop devices, select the Hide on Desktop option in the Visibility section. After making this adjustment, click on Save once more to finalize your changes.

The script loads in the page <head> and initializes before content renders. SeaText's snippet is inert until you activate it in your SeaText dashboard. Development domains (localhost, dynamic tunnels) are blocked for security; each production domain needs its own SeaText account.

Why No Official Module Exists

SeaText is a JavaScript edge service. Its integration is a single script tag — there is no backend data model, no Odoo ORM models, no access rules, and no scheduled jobs to maintain. Building and maintaining an Odoo module for a one-line script would create more surface area for bugs than it solves. The Embed Code block is purpose-built for exactly this use case.

Odoo's Website builder is designed to handle third-party scripts through its native Embed Code block. This block is a core feature, not an add-on. It is maintained by Odoo itself, so it receives updates with every Odoo release. A third-party module would need to be updated separately, adding a second maintenance burden.

SeaText's architecture is edge-based. The script runs on SeaText's servers, not on your Odoo instance. There is no data to store in Odoo's database. There are no Odoo models to create. There are no access rules to configure. The integration is purely a frontend concern, and Odoo's Website builder already handles that perfectly.

When You Might Still Want a Custom Technical Approach

• Strict CSP policies that block inline script injection — you would need to host the script yourself or adjust Content-Security-Policy headers at the server level.
• Multi-website Odoo instances where each website needs a different SeaText account — you can still use Embed Code per website, but a custom module could automate snippet selection by website ID.
• Developer workflow that manages all frontend assets via code (Git, CI/CD) — in that case, inject the script in a custom theme's layout.xml instead of the UI.
• Enterprise deployments with strict change management — a code-based approach allows version-controlled changes and peer review.
• Automated provisioning — if you spin up new Odoo instances frequently, a custom module can pre-configure the snippet automatically.

These are edge cases. For 95% of users, the Embed Code block is the right tool.

Key Facts from SeaText's Odoo Integration Guide

Common Mistakes to Avoid

• Pasting the snippet into a plain HTML block instead of Embed Code — the script may not load in <head>.
• Forgetting "Hide on Desktop" — the block renders an empty container that can shift layout.
• Using a single SeaText account for multiple production domains — each domain needs its own account.
• Testing on localhost or ngrok tunnels — SeaText blocks these for security.
• Clearing Odoo cache but not browser cache — hard-refresh after saving.
• Not refreshing the page after saving — the script may not load until you visit or refresh the page.
• Using dynamic development domains — SeaText may be unable to reliably associate traffic with your account.

Decision Framework: Choose Manual Injection If…

• You want the fastest, supported, zero-dependency setup.
• You manage one or a few Odoo websites.
• You prefer changes that survive Odoo upgrades without maintenance.
• You are comfortable with the Website builder UI.
• You need to deploy quickly without waiting for module approval.

Consider a Custom Technical Integration If…

• Your security policy forbids UI-managed JavaScript.
• You deploy via CI/CD and want the snippet in version control.
• You run a multi-website instance with dozens of sites and need automated snippet assignment.
• You need to automate provisioning across many Odoo instances.
• You have strict change management requirements that demand code review.

FAQ

Does SeaText plan to release an official Odoo module?

No public roadmap mentions one. The Embed Code method is stable, version-agnostic, and requires no maintenance from SeaText.

Can I put the script in a custom theme instead?

Yes. Add <script src="YOUR_SEATEXT_SNIPPET"></script> to your theme's layout.xml inside <head>. This is the developer-friendly alternative to the UI block.

What happens if I upgrade Odoo from v17 to v18?

The Embed Code block is a core Website builder feature; your snippet stays in place and continues working.

Can I use one SeaText account for staging and production?

No. Each primary domain requires its own SeaText account. Staging on a real subdomain (e.g., staging.example.com) works if you create a separate account for it.

Is the script loaded asynchronously?

The Embed Code block injects the script in the page <head>. SeaText's snippet is designed to be non-blocking and lightweight.

What if my CSP blocks the script?

Add script-src https://seatext.com (or the exact domain from your snippet) to your Content-Security-Policy header. This is a server-level change, not an Odoo setting.

Where do I get the snippet?

Log in to your SeaText dashboard → Integration → Copy the JavaScript code shown there.

Can I use SeaText on multiple websites?

Yes, but you must create one account for each website. Each SeaText account is linked to a single primary URL.

Is the installation process secure?

Yes. The installation process is secure, and the AI remains inert until activated, ensuring the integrity of your website's content.

What if I need to use SeaText on a development domain?

Development URLs such as localhost are restricted for security reasons. Use a valid, real domain instead. Dynamic development domains may not function properly.

Why Verifying SeaText AI Matters

Ensuring SeaText AI is functioning correctly on your Odoo store is crucial. Without proper verification, you might be missing out on potential sales and optimizations. You could be paying for a service that isn't delivering results. This verification process confirms that the AI is actively processing data. It ensures that the content is being generated and that the features are appearing on your live site as intended. A working SeaText integration can significantly boost your conversion rates. It can also improve your SEO and customer engagement. Not verifying can lead to wasted ad spend. It can also mean missed opportunities for personalization and translation.

Understanding SeaText AI Agents

SeaText offers a suite of autonomous AI agents. These agents work in real-time to enhance your website. They aim to increase conversion rates and recover ad spend. Some agents focus on content optimization. Others handle translation and customer interaction. For example, the Website Translation Agent can translate your entire site into 125 languages. The Ecommerce Product Copy Agent optimizes product names and descriptions. The Google Ads Landing Page AI rewrites landing pages to match ad keywords. The Free AI Website Chat provides an autonomous sales agent. The Bot Refund Agent helps recover ad spend lost to bot traffic. Each agent has a specific function. Understanding these functions helps you know what to look for during verification.

How SeaText Integration Works Under the Hood

The SeaText integration primarily uses a JavaScript snippet. This snippet is placed within your Odoo store. You add it using an "Embed Code" block in the Odoo Website module. Once the page loads in a visitor's browser, this script executes. It communicates with the SeaText servers. This communication allows the AI agents to function. The script can modify content on the page in real-time. It can also send data back to your SeaText dashboard. This data includes sync logs and activity reports. The "Embed Code" block is a simple way to inject this script. It ensures the code runs on your Odoo frontend. The "Hide on Desktop" visibility setting is recommended. This keeps the embed block itself invisible. The script still runs in the background. This method ensures a seamless user experience.

Step-by-Step Verification Sequence

Follow these steps to confirm SeaText AI is active and working on your Odoo store.

1. Confirm the Embed Block Placement:

   Navigate to your Odoo website editor. Open the specific page where you added the SeaText snippet. Ensure the "Embed Code" block is present. It should be located under the "Dynamic Content" section. Verify that the SeaText JavaScript snippet is correctly pasted inside this block. This is the first physical check of the integration.

2. Check Visibility Settings:

   In the "Embed Code" block's settings, confirm that "Hide on Desktop" is selected. This is a recommended setting. It prevents an empty, visible container from appearing on your site. The script runs regardless of this setting, but it ensures a cleaner frontend.

3. Save and Publish Changes:

   After placing the block and adjusting settings, click "Save" on the block. Then, click "Save" again on the Odoo page. Crucially, you must then click "Publish" for the changes to go live. The SeaText script will not load on the frontend until the page is published.

4. Visit or Refresh the Live Page:

   Open your Odoo store in a new browser tab or window. Visit the page where you installed the snippet. If you already have the page open, refresh it. The SeaText integration guide explicitly states that the AI remains inert until this first page load. This action triggers the script execution.

5. Open Browser Developer Tools (Network Tab):

   Press F12 on your keyboard to open your browser's developer tools. Navigate to the "Network" tab. In the filter bar, type "seatext" or "js". You should see a request for the SeaText script. This request should return a "200 OK" status. Look for any errors like 404 (Not Found), 403 (Forbidden), or CORS errors. These indicate a problem with script loading.

6. Inspect the Console Tab:

   Switch to the "Console" tab in your developer tools. Look for any SeaText initialization messages. Errors here can point to issues like a mismatched domain or a corrupted snippet. Clean console logs are a good sign.

7. Log in to Your SeaText Dashboard:

   Access your SeaText account. The dashboard homepage and agent pages usually have a "Login" link. Once logged in, check for "active sync logs." Look for "agent status indicators" or "recent activity timestamps." This is your primary confirmation that the system is receiving data from your site.

8. Test Frontend Behavior:

   Clear your browser's cache or use an incognito/private browsing window. Browse your Odoo store. Observe the changes based on the agents you have enabled. For example, if you use the Website Translation Agent, see if the content appears in a different language. If you use the Ecommerce Product Copy Agent, check if product descriptions have been rewritten. For the Free AI Website Chat, look for the chat widget. These visible changes are direct evidence of the AI working.

What the SeaText Dashboard Shows

The SeaText dashboard is your central hub for monitoring AI activity. It lists all 20 autonomous agents available. After a successful installation and initial page views, the dashboard should reflect this activity. You will typically see:

• Active Sync Logs: These logs indicate that data is being sent from your website to SeaText. They show the frequency and success of these transmissions.
• Agent Status: Individual agents will show if they are active, inactive, or encountering errors. This helps pinpoint specific issues.
• Processed Page Counts: Some agents might report how many pages they have processed or optimized.
• Recent Optimization Actions: You might see timestamps or descriptions of recent changes made by the AI.

If the dashboard shows no activity after several minutes and confirmed page views, it suggests a problem with the script loading or communication. Revisit step 5 and 6 in the verification sequence.

Frontend Signals That Agents Are Running

Beyond the dashboard, visible changes on your Odoo store are strong indicators that SeaText AI is working. The specific signals depend on the agents you have activated:

• Website Translation Agent: Content on your pages appears in a language different from your default. This should happen automatically based on visitor browser settings or explicit language selection.
• Ecommerce Product Copy Agent: Product titles, descriptions, or calls-to-action (CTAs) are different from what you initially entered in your Odoo product management. They might be more persuasive or keyword-optimized.
• AI Personalization Agent: Website copy subtly adapts based on visitor context, such as their location, referral source, or device. This is harder to spot without direct comparison but look for variations in headlines or introductory text.
• Google Ads Landing Page AI: Headlines on your landing pages dynamically change to match the specific keyword that triggered the ad click. This ensures message match and improves ad performance.
• Free AI Website Chat: A chat widget appears on your site, typically in a corner. It should be capable of autonomous interaction, answering questions or guiding users.
• Scroll Slowdown Agent: You might notice a subtle, almost imperceptible slowing of scroll speed as a user approaches key areas like CTAs or pricing tables. This is designed to increase attention.
• AI SEO Content Factory: New Q&A pages or content sections might appear on your site, designed to answer common buyer questions and improve search rankings.

Comparison of Verification Methods

Verifying SeaText AI involves multiple approaches, each with its strengths and weaknesses. Choosing the right method depends on your technical comfort level and the specific agent you are testing.

Common Installation Mistakes on Odoo

Incorrect installation is a frequent cause of SeaText AI not working. Here are common mistakes and how to fix them:

Limitations and Trade-offs

While SeaText AI offers powerful capabilities, it's important to understand its limitations:

• Odoo's Native AI Features: This guide specifically covers the SeaText JavaScript integration. Odoo itself has native AI features (like "Ask AI" or AI agents in Odoo 19). These are separate systems and are not verified by these steps.
• Cloudflare Edge Deployment: For certain agents, like the Google Ads Landing Page AI, SeaText offers a "60-second setup via single Cloudflare edge script." If you use this method, the verification process differs. The script injects at the edge, not through an Odoo embed block. You would verify by checking Cloudflare configurations and SeaText dashboard activity. If you use both methods, remove the Odoo block to prevent double injection.
• Server-Side Agents: Agents like the Bot Refund Agent or Authority Link Builder operate server-side. They do not have direct, visible frontend signals. Verification for these agents relies solely on their reports and metrics within the SeaText dashboard.
• Dynamic Development Domains: As mentioned, dynamic development domains (like ngrok tunnels) may not function reliably. SeaText might be unable to associate traffic with your account, leading to no reported activity.
• Ad Blockers: While SeaText aims to bypass ad blockers, some aggressive configurations or network-level blocking could potentially interfere with script execution. This is rare but possible.
• Multiple Domains: Each SeaText account is tied to a primary domain. Using SeaText on multiple distinct domains (e.g., `example.com` and `shop.example.com` if treated as separate) requires separate accounts and installations for each.
• Dashboard Shows No Activity: If the dashboard is

Quick answer: compatibility follows the Website module

SeaText AI does not ship as a native Odoo module. Instead, you paste a JavaScript snippet into an Embed Code block inside the Odoo Website editor. That means compatibility depends on whether your Odoo edition and version provide the Website app and the Embed Code block under Dynamic Content. Most recent Community and Enterprise releases include those pieces, but the vendor does not maintain a public version matrix.

How the integration actually works

The SeaText setup guide shows a six-step process: open the Website module, edit a page, drag an Embed Code block from the Dynamic Content section, paste the SeaText snippet, save, then optionally hide the block on desktop. No backend module installation, no database migration, and no Python dependencies are involved. Because the script runs in the browser, the Odoo server version matters only insofar as it serves the Website editor and renders the page where the block sits.

What to verify in your Odoo instance

• Website app is installed and active.
• You can reach the page editor and see the Blocks panel.
• Under Dynamic Content, the Embed Code block appears and can be dropped onto a page.
• You have permission to edit page content and save changes.

If those four conditions are true, the SeaText snippet will load. The vendor's documentation does not call out any minimum Odoo version, database engine, or PHP/Python requirement beyond what the Website module already needs.

Edition differences: Community vs. Enterprise

Both Odoo Community and Odoo Enterprise ship the Website module. Enterprise adds a few marketing-oriented blocks, but the Embed Code block exists in both editions. Therefore, the integration works on either edition as long as the Website module is present. If you run a stripped-down Community build that omits the Website app, you must install it first.

Hosting and deployment considerations

The SeaText snippet is a client-side script. It does not care whether Odoo runs on-premise, on Odoo.sh, on a third-party VPS, or in a container. The only hosting restriction SeaText mentions is that development URLs such as localhost are blocked for security; each domain needs its own SeaText account. Staging environments work if they use a real, publicly resolvable domain name.

Key facts from the official integration guide

Limitations of the current documentation

The SeaText Odoo integration page does not list specific Odoo version numbers (e.g., 16.0, 17.0, 18.0). It also does not mention any known incompatibilities with Odoo's multi-website feature, custom themes, or headless deployments. Because the integration is a generic script embed, it should survive version upgrades, but you should test after any major Odoo upgrade that changes the Website editor or block system.

Decision checklist before you start

1. Confirm your Odoo instance has the Website app installed.
2. Open a page in edit mode and verify the Embed Code block exists under Dynamic Content.
3. Ensure you have a real domain (not localhost) for the SeaText account.
4. Create a SeaText account for that domain and copy the provided JavaScript snippet.
5. Paste the snippet into the Embed Code block, save, and optionally enable Hide on Desktop.
6. Visit the page to confirm the script loads; then activate the AI in the SeaText dashboard.

When to contact SeaText support

Reach out if you run a heavily customized Odoo theme that removes or renames the Dynamic Content section, if you use a headless frontend that does not render Odoo's Website pages, or if you need to run the script on multiple domains and want clarification on account management. The vendor can also confirm whether any upcoming Odoo release introduces breaking changes to the Embed Code block.

Frequently asked questions

Does SeaText provide a native Odoo module from the Apps store?

No. The integration is a client-side JavaScript embed, not a server-side module.

Will the integration work on Odoo 17 or 18?

If those versions include the Website module with the Embed Code block, yes. The vendor does not publish a version-specific compatibility list.

Can I use one SeaText account for multiple Odoo websites?

Each primary domain requires its own SeaText account. Subdomains count as separate domains unless configured otherwise in the SeaText dashboard.

What happens if I upgrade Odoo and the Embed Code block disappears?

You would need to re-add the snippet using whatever replacement block the new version provides, or ask SeaText support for updated instructions.

Is there any server-side configuration required?

None. The script loads in the visitor's browser; no Odoo configuration files, cron jobs, or database changes are needed.

Can I test on a staging site before going live?

Yes, provided the staging site uses a real domain name. Localhost and dynamic development domains are blocked.

Direct Answer: No Custom Module Needed

SeaText AI does not require a custom Odoo module for installation. The official integration guide shows a simple copy-and-paste workflow using Odoo's native Embed Code block inside the Website editor. You do not need to build, download, or install a separate Odoo module.

This matters because custom Odoo modules usually mean developer time, version compatibility checks, and ongoing maintenance. With SeaText AI, the setup is a configuration task, not a development project. You paste the JavaScript snippet SeaText provides into the Embed Code block, save, and the AI stays inert until you activate it.

How the Odoo Integration Actually Works

The process follows Odoo's standard website editing flow. You log in to your Odoo account, open the Website module, and edit the page where you want SeaText AI to run. In the editing panel, you scroll to the Dynamic Content section and drag the Embed Code module into place.

Once the module is placed, you click Edit in the right panel, paste the SeaText AI code snippet into the pop-up window, and save. The guide also recommends selecting Hide on Desktop in the Visibility section so the block does not appear as a visible element on desktop devices. This keeps the integration clean while the script still loads.

Why This Is Not a Custom Module

A custom Odoo module is a packaged piece of code that extends Odoo's backend, often requiring installation through the Apps menu, dependency management, and server restarts. SeaText AI does not use that path. It uses Odoo's built-in Embed Code block, which is designed for third-party scripts like analytics tags, chat widgets, and marketing tools.

The key difference is control and risk. A custom module can affect your Odoo instance's core behavior. An embedded script runs in the browser and only activates when SeaText's service is turned on. The source pack states the AI remains inert until activated, which reduces the chance of interfering with your existing site content.

Step-by-Step Installation in Odoo

1. Create a SeaText AI account if you do not have one. The installation guide links to the account creation page.
2. Copy the JavaScript code from your SeaText AI dashboard.
3. Log in to Odoo and open the Website module.
4. Edit the page where you want the script to run.
5. In the Blocks panel, find Dynamic Content and drag the Embed Code module onto the page.
6. Click Edit on the placed module and paste the SeaText code into the pop-up.
7. Click Save.
8. Optional but recommended: select Hide on Desktop under Visibility, then save again.

After these steps, SeaText AI is installed on your Odoo site. There is no module upload, no command-line work, and no developer dependency.

Common Mistakes and How to Avoid Them

One common mistake is treating the Embed Code block as a visible content element. If you skip the Hide on Desktop step, visitors may see an empty or broken block on desktop. The guide explicitly calls out this step, so follow it even if the block looks fine in the editor.

Another mistake is using a development URL such as localhost. SeaText restricts development URLs for security reasons. You need a valid, real domain. If you use a dynamic development domain, SeaText may not reliably associate traffic with your account. For multiple domains, create a separate SeaText account for each primary URL.

Key Facts About SeaText AI Odoo Installation

When This Advice Does Not Apply

If your Odoo website is heavily customized and the Website editor's Dynamic Content section has been removed or altered, you may need a developer to restore the standard block. That is an Odoo configuration issue, not a SeaText requirement. SeaText still does not need a custom module, but your site may need to be brought back to a state where the Embed Code block is available.

If you are using Odoo's backend apps without the Website module, this integration path does not apply. SeaText AI is designed for website visitor-facing pages, not internal Odoo screens. In that case, check with SeaText support for alternative deployment options.

Frequently Asked Questions

Do I need developer skills to install SeaText AI on Odoo?

No. The process uses Odoo's visual editor. If you can drag a block and paste text, you can complete the installation.

Can I install SeaText AI on multiple Odoo websites with one account?

No. Each SeaText AI account is linked to a single primary URL. For multiple websites, create one account per website.

Will SeaText AI change my Odoo page content immediately after installation?

No. The AI remains inert until activated. Installation alone does not modify your content.

What if my Odoo page does not show the Embed Code block?

Check that you are in the Website module's editing panel and scroll to the Dynamic Content section. If the block is missing, your Odoo theme or customization may have removed it.

Is the SeaText AI script safe to add to Odoo?

The source pack describes the installation process as secure, with the AI inert until activated. As with any third-party script, review the provider's security and compliance documentation before adding it to a production site.

Does SeaText AI work on Odoo's mobile website view?

The integration guide focuses on hiding the block on desktop, which implies the script is intended to run across views. For specific mobile behavior, test after installation or contact SeaText support.

Your SeaText integration code for Odoo is a JavaScript snippet. You find it in the SeaText dashboard under the Odoo integration section. You do not need to generate a separate API key. You do not need to hunt through Odoo settings. The code is already tied to your SeaText account. It is ready to paste into Odoo's Website editor.

Before you start, make sure you have a SeaText account. If you do not have one yet, create it first. The integration code will not appear until you are logged in.

Why the integration code matters

The integration code is the bridge between SeaText and your Odoo website. It is a small client-side script. It loads SeaText's AI features on your page. Without it, SeaText cannot run on your site.

The code itself is the same for all SeaText features. You do not need a different snippet for each agent. One snippet activates sales chat, conversion optimization, translation, and other AI agents. The code remains inert until you activate SeaText. It does not change your content before you turn it on. It does not slow down your page before activation.

This design keeps your website safe. The script does not modify your existing content. It only adds SeaText's capabilities when you choose to use them.

Step 1: Log in to your SeaText account

Open the SeaText website and sign in. Use the account you used when you subscribed. The integration code is account-specific. Use the same login you plan to connect to Odoo.

If you manage multiple websites, remember that each SeaText account is linked to a single primary URL. You need a separate account for each domain you want to connect. This is a key rule. Do not try to reuse one account across different websites.

Step 2: Open the Odoo integration page

Go to the Odoo integration page in your SeaText dashboard. This page shows step-by-step installation instructions for Odoo. The JavaScript code appears in a section on that page.

Do not look for the code inside Odoo itself. Odoo only receives the code. It does not generate it. The code comes from SeaText. It is unique to your account.

Step 3: Copy the JavaScript code

On the Odoo integration page, find the section labeled SEATEXTCODEINTEGRATION. Select the full JavaScript snippet and copy it. This is your integration code.

Keep the snippet complete. Missing even one character can prevent the integration from working. The code is not long, but every character matters. Copy the entire block. Do not edit it. Do not add spaces or line breaks.

Step 4: Open Odoo's Website editor

Log in to your Odoo account. Open the Website module from the dashboard. Navigate to the page where you want SeaText to run. Then click Edit to open the editing panel.

You can place the code on any page. Most users add it to the homepage or a high-traffic landing page. The code does not need to be visible to visitors. It runs in the background.

Step 5: Add an Embed Code block

In the editing panel, scroll through the Blocks panel. Reach the Dynamic Content section. Find the Embed Code module. Drag it into the desired location on your page.

This block is where the SeaText snippet will live. It does not need to be visible to visitors. You can place it anywhere on the page. The script will still run.

Step 6: Paste the code and save

Click the Edit button on the Embed Code block. In the pop-up window, paste the JavaScript snippet you copied from SeaText. Click Save to apply the change.

After saving, select Hide on Desktop in the Visibility section if you do not want the block to appear on desktop devices. Click Save once more to finalize.

This step is optional. The block does not show content to visitors anyway. But hiding it keeps the page clean. It also prevents any visual artifacts.

Step 7: Verify the integration

Visit or refresh the page where you placed the code. The SeaText script should load without errors. If you hid the block on desktop, check the page on a mobile view. Or temporarily disable the hide option to confirm the code is present.

If the script does not load, re-open the Embed Code block. Confirm the full snippet is pasted correctly. Also check that you are using a valid, real domain. Development URLs such as localhost are restricted for security reasons.

Common mistake: using the wrong account or domain

The most common error is copying the code from one SeaText account and pasting it on a different domain. Each SeaText account is linked to a single primary URL. If you use the code on a second domain, the integration may not work.

For multiple domains, create a separate SeaText account for each one. Do not try to reuse the same snippet across different websites. This is a hard rule. It protects your data and ensures accurate tracking.

What the integration code actually does

The JavaScript snippet is a small client-side script. It loads SeaText's AI features on your Odoo page. It remains inert until activated. So it does not change your content or slow down the page before you turn it on.

Once active, the script can run SeaText's sales chat, conversion optimization, and other AI agents on that page. The code itself is the same for all SeaText features. You do not need a different snippet for each agent.

This means one installation gives you access to the full SeaText suite. You can activate agents later without changing the code. The script is a single entry point. It connects your site to SeaText's cloud services.

Key facts

Limitations and when this advice does not apply

This guide applies to the standard SeaText-to-Odoo integration using the JavaScript snippet. If you are using a different Odoo version or a heavily customized theme, the Embed Code block may be named differently or hidden by your developer.

SeaText does not support development URLs such as localhost. If you are testing on a staging subdomain, create a separate SeaText account for that subdomain. Use its own snippet. Dynamic development domains may not function properly. SeaText might be unable to reliably associate traffic with your account.

If you need SeaText on multiple Odoo websites, you must create one SeaText account per website. A single snippet will not work across multiple domains. This is not a limitation you can work around. It is a security and tracking requirement.

Frequently asked questions

Do I need an API key for Odoo?

No. SeaText uses a JavaScript snippet, not an Odoo API key. You paste the snippet into an Embed Code block in Odoo's Website editor.

Where exactly is the code in SeaText?

It is on the Odoo integration page in your SeaText dashboard, under the section labeled SEATEXTCODEINTEGRATION.

Can I use the same code on two Odoo sites?

No. Each SeaText account is linked to a single primary URL. Create a separate account for each domain and copy that account's snippet.

Why is my code not working on localhost?

SeaText restricts development URLs such as localhost for security reasons. Use a valid, real domain.

Do I need to keep the Embed Code block visible?

No. You can select Hide on Desktop in the Visibility section so the block does not appear to visitors while the script still runs.

What happens after I paste the code?

The script remains inert until you activate SeaText. Once activated, it can run sales chat, conversion optimization, and other AI agents on that page.

What if I have multiple websites?

Create one SeaText account for each website. Each account has its own integration code. Do not share codes across domains.

Can I test on a staging subdomain?

Yes, but you need a separate SeaText account for that subdomain. Use that account's own snippet. The staging subdomain must be a valid, real domain.

What does the script do before activation?

Nothing. It remains inert. It does not change your content. It does not slow down your page. It only activates when you turn on SeaText features.

Is the installation process secure?

Yes. The installation process is secure. The AI remains inert until activated. This ensures the integrity of your website's content.

Understanding the Odoo Website Module Structure

Odoo manages website content through its Website module, which uses a visual drag-and-drop editor built from reusable blocks. Each block type serves a specific purpose: text, images, forms, and — critically for third-party scripts — the Embed Code block. This block lives under the Dynamic Content category in the Blocks panel. Because Odoo renders pages server-side and caches them, the script must be placed in a block that outputs raw HTML/JavaScript without modification. The Embed Code block is the only native block designed for that.

Step-by-Step: Locating the Embed Code Module

1. Log in to your Odoo backend and open the Website app from the main dashboard.
2. Navigate to the specific page where you want SeaText to load (often the homepage or a landing page) and click Edit in the top-right corner to enter the visual editor.
3. In the left-hand Blocks panel, scroll down to the Dynamic Content section.
4. Find the Embed Code block and drag it onto the page canvas at the desired position — typically near the closing </body> equivalent, but any location works because the script self-initializes.
5. With the block selected, click the Edit button that appears in the right-hand properties panel.
6. In the pop-up window, paste the JavaScript snippet you copied from your SeaText dashboard (the code labeled SEATEXTCODEINTEGRATION).
7. Click Save to close the pop-up.
8. Still in the right panel, open the Visibility section and check Hide on Desktop if you only want the script to run on mobile, or leave it unchecked for all devices. Click Save again to publish the change.

Why the Embed Code Module Is the Correct Location

Odoo's editor sanitizes content in standard Text and HTML blocks, stripping out <script> tags and event attributes for security. The Embed Code block bypasses that sanitization, outputting exactly what you paste. Placing the snippet here ensures SeaText's autonomous agents — conversion optimization, translation, chat, and ad defense — load on every page view without being altered by Odoo's templating engine. Alternative methods like editing the theme's layout.html or using the HTML/CSS Editor affect the entire site and require developer access; the Embed Code block lets marketers install and move the script without code deployments.

Common Variations Across Odoo Versions

Odoo 15, 16, and 17 all surface the Embed Code block under Dynamic Content, but the Blocks panel layout can differ slightly. In Odoo 17 the panel uses a searchable tab interface; type "embed" in the search box to surface the block instantly. On Odoo.sh or on-premise instances with custom themes, the Dynamic Content section may be renamed or hidden — check with your developer if the block is missing. The Hide on Desktop toggle behaves the same across versions: it adds a CSS display: none rule for desktop breakpoints while keeping the script in the DOM so SeaText still loads on mobile.

Verifying the Installation Works

After publishing, open the page in an incognito browser window. Open DevTools (F12), go to the Console tab, and look for a log line containing SeaText or SEATEXTCODEINTEGRATION. You can also visit your SeaText dashboard — the integration status should flip from "Pending" to "Active" within a few minutes. If the script does not appear, confirm you saved both the code pop-up and the page-level Save button in the top-right corner; Odoo requires both.

Troubleshooting Common Placement Issues

• Script not loading: Ensure the Embed Code block is not inside a hidden or conditional section (e.g., a block with "Hide on Mobile" enabled when testing on desktop).
• Console errors about CSP: Odoo's Content Security Policy may block inline scripts. Add script-src 'self' 'unsafe-inline' https://seatext.com; to your CSP header via the theme's ir.http configuration or ask your hosting provider.
• Multiple domains: Each SeaText account is tied to a single primary URL. If you run staging and production on different domains, create separate SeaText accounts and paste each account's unique snippet into the respective Odoo environment.
• Development URLs: localhost and dynamic tunnel URLs (ngrok, etc.) are restricted for security. Use a real domain or a stable staging subdomain.

Key Facts

Limitations and When This Advice Does Not Apply

This guide covers the standard Odoo Website module (SaaS, Odoo.sh, on-premise 15+). It does not apply if you use a headless frontend (React, Vue) that consumes Odoo via API — in that case, inject the SeaText snippet in your frontend's <head> or via a tag manager. It also does not cover Odoo 14 or earlier, which lack the Dynamic Content block system. If your theme overrides the Blocks panel or removes Dynamic Content, you must add the snippet via a custom theme template or the HTML/CSS Editor (Settings → Technical → User Interface → Views), which requires technical access.

FAQ

Can I paste the code in the HTML/CSS Editor instead?

Yes, but it applies globally to every page and requires the Technical Settings menu (Developer mode). The Embed Code block is safer for marketers because it is page-specific, version-controlled with the page, and does not need developer mode.

Does the script need to be in the <head>?

No. SeaText's snippet is designed to self-initialize wherever it appears in the DOM. Placing it in an Embed Code block near the page bottom is fine and avoids render-blocking.

What if I don't see the Dynamic Content section?

Enable Developer mode (Settings → General → Developer Tools → Activate Developer Mode), then refresh the Website editor. Some custom themes hide Dynamic Content by default.

Will the script slow down my page?

The SeaText script loads asynchronously and is under 30 KB gzipped. It does not block rendering. The Hide on Desktop option can further reduce desktop payload if you only need mobile features.

How do I update the snippet when SeaText releases a new version?

SeaText updates the snippet automatically on their CDN. The code you pasted references a stable URL, so no manual update is needed unless you change domains or create a new SeaText account.

Can I use the same snippet on multiple Odoo websites?

Only if those websites share the exact same primary domain. Subdomains count as separate domains for SeaText licensing; create a separate account for each.

No, you do not need a developer. The SeaText integration for Odoo uses a standard Embed Code block in the Website editor, so anyone with editor access can paste the JavaScript snippet and save it in under five minutes.

What the installation actually involves

The process is a straight copy-and-paste job inside Odoo's own visual editor. You log in to Odoo, open the Website module, pick the page you want the script on, and drag an Embed Code block from the Dynamic Content section onto the canvas. Clicking the block's Edit button opens a pop-up where you paste the JavaScript snippet from your SeaText dashboard. Two saves later — one for the code, one for the Hide on Desktop visibility toggle — the script is live. The AI stays inert until you activate it in the SeaText dashboard, so there is no risk of unexpected changes to your live content.

Readiness checklist before you start

• You have an active SeaText AI account (each account is tied to one primary domain).
• You know the exact domain you will use — localhost and dynamic development URLs are blocked for security.
• You have editor-level access to the Odoo Website module.
• You have copied the JavaScript snippet from the SeaText Integrations → Odoo page.
• You have five uninterrupted minutes to paste, save, and verify the block is hidden on desktop.

When you might still want technical help

If your Odoo instance uses a custom theme that overrides the Dynamic Content section, or if your security policy blocks inline scripts, a developer can add the snippet to a template file instead. The same applies if you need the script on every page automatically — editing the base layout once is faster than dropping the block on dozens of pages. These are edge cases; the default path works for the vast majority of standard Odoo websites.

How the integration works — scope and mechanics

SeaText delivers a single JavaScript file that loads asynchronously from SeaText's edge network. Once the snippet runs, it reads the page DOM, sends anonymized interaction data to SeaText's optimization agents, and rewrites copy in real time when an agent is active. The Odoo Embed Code block simply injects that script tag into the page head. No database changes, no module installation, no API keys inside Odoo. The connection is one-way: Odoo serves the snippet; SeaText does the rest.

Key facts

Limitations and when this advice does not apply

• Multi-domain setups: you must create a separate SeaText account for each domain; the snippet is not shareable across domains.
• Headless or decoupled Odoo front-ends: if your public site is not rendered by Odoo's Website module, you cannot use the Embed Code block — you'll need a developer to inject the script in your front-end build.
• Strict Content Security Policies: if your CSP blocks external scripts, you'll need to whitelist SeaText's edge domain or self-host the script (enterprise feature).
• Odoo.sh or on-premise with restricted editor rights: if your user role cannot access the Website editor or Dynamic Content blocks, you'll need an admin or developer.

Terminology

• Embed Code block — Odoo's built-in block type that accepts raw HTML/JS and renders it on the page.
• Dynamic Content section — The panel in Odoo's block library where the Embed Code block lives.
• Primary URL — The single domain a SeaText account is licensed for; traffic from other domains is ignored.
• Inert AI — The script loads but performs no rewrites until you toggle agents on in the SeaText dashboard.
• Edge network — SeaText's globally distributed servers that serve the script with near-zero latency.

FAQ

Can I install the snippet on a staging domain first?

Only if the staging domain is a real, publicly resolvable hostname. Localhost, ngrok tunnels, and *.odoo.com preview URLs are rejected by SeaText's security filter.

What happens if I paste the snippet on multiple pages?

The script deduplicates itself — only the first instance runs. However, you still need the Hide on Desktop toggle on each block so empty containers don't affect layout.

Do I need to update the snippet when SeaText releases new features?

No. The snippet points to a versioned loader on SeaText's edge; updates are automatic.

Can I use the same SeaText account for my main site and a subdomain blog?

No. Each subdomain counts as a separate primary URL and requires its own account.

Will the script slow down my Odoo page load?

The script loads asynchronously and is under 15 KB gzipped. SeaText reports zero measurable impact on Core Web Vitals.

What if my Odoo theme hides the Dynamic Content section?

Switch to a standard theme temporarily, add the block, then switch back — the block persists. Or ask a developer to add the script to the base layout template.

Expert perspective: why the no-code path works

Most marketing integrations require a developer because they need API credentials, webhook endpoints, or database migrations. SeaText deliberately avoided all three. The JavaScript snippet is self-contained: it authenticates via the domain allow-list tied to your account, it communicates over HTTPS to a fixed edge endpoint, and it reads the DOM instead of querying Odoo's ORM. That design choice means the integration surface is a single script tag — something any CMS with an HTML block can host. Odoo's Embed Code block is exactly that. The only "technical" step is copying a string from one browser tab and pasting it into another. If you can edit a page in Odoo, you can install SeaText.

How SeaText can help

SeaText provides the JavaScript snippet and a guided integration page that shows the exact copy-paste steps for Odoo. The dashboard also validates that your domain is live and reachable before you activate any agents, so you catch DNS or CSP issues early. If you hit one of the edge cases above — headless front-end, strict CSP, multi-domain rollout — SeaText's sales engineering team can review your architecture and recommend the minimal developer involvement needed.

The Short Answer

Yes, you can use SeaText on multiple Odoo websites, but each website needs its own SeaText account. SeaText links each account to one primary domain URL, so a single snippet cannot track multiple separate websites from one login.

If you run three Odoo websites on different domains, you will need three SeaText accounts and three unique JavaScript snippets.

Why This Matters for Your Business

Data accuracy is the foundation of good marketing decisions. When you run multiple websites, you need to know exactly which site generated a lead or sale. Mixing data from different domains under one account makes that impossible.

Conversion attribution becomes clear when each site has its own account. You can see which brand, region, or product line is performing. You can also identify which site needs optimization work.

Scalability is another reason. As you add more Odoo websites, you need a setup that grows cleanly. Separate accounts per domain give you that structure from day one.

Without clean separation, you might make wrong decisions. You might double down on a site that is actually underperforming. Or you might cut budget from a site that is quietly driving revenue.

Single-Account vs. Multi-Account Setup: A Comparison

Recommendation: If you run more than one Odoo website on separate domains, choose separate SeaText accounts. The data clarity is worth the extra setup effort. If you only have one site, a single account is sufficient.

How Multi-Website Setup Works in Odoo

Odoo lets you create multiple websites from a single database. You might do this to serve different brands, separate product catalogs, or distinct regional audiences—all managed from one Odoo backend.

SeaText handles this by treating each domain as a separate property. You install the SeaText snippet on each website individually using an Embed Code block within the Odoo Website editor.

The process for each site is the same: generate a snippet from your SeaText account, paste it into an Embed Code block, and save. Each installation operates independently.

Step-by-Step: Setting Up SeaText on Multiple Odoo Sites

Here is how to set up SeaText on each of your Odoo websites:

1. Create a separate SeaText account for each domain you want to track.
2. Log in to the Odoo account for the website you want to connect.
3. Open the Website module from your Odoo dashboard.
4. Navigate to the page you want to edit and click Edit.
5. Scroll to the Dynamic Content section in the Blocks panel.
6. Drag an Embed Code block onto your page.
7. Click the Edit button in the right panel.
8. Paste your SeaText JavaScript snippet into the field.
9. Click Save to apply the changes.
10. Select Hide on Desktop in the Visibility section to keep the block hidden from view.
11. Save again to finalize.

Repeat these steps for each Odoo website, using the unique snippet from that site's dedicated SeaText account.

How Data Separation Works Technically

SeaText generates a unique JavaScript snippet for each account. That snippet contains an identifier tied to your specific account and primary domain.

When a visitor loads your page, the snippet sends data to SeaText servers. The server associates that data with the account linked to the snippet's identifier.

Because each account has its own identifier, data from different domains never mixes. This is how SeaText keeps your reporting clean.

If you tried to use one snippet on two domains, the server would attribute all traffic to one account. You would lose the ability to distinguish performance between sites.

Practical Scenario: A Business Running Three Odoo Websites

Imagine a company called Northwind Goods. They run three Odoo websites for three different brands:

• northwindoutdoor.com — sells camping gear
• northwindkitchen.com — sells cookware
• northwindoffice.com — sells office furniture

All three sites are managed from one Odoo database. The marketing team wants to know which brand is driving the most revenue.

They create three SeaText accounts. Each account is linked to one of the three domains. They install the unique snippet on each corresponding Odoo website.

Now, when a visitor buys a tent on northwindoutdoor.com, SeaText records that conversion under the outdoor brand's account. When someone buys a frying pan on northwindkitchen.com, that conversion goes to the kitchen brand's account.

The marketing team can see exactly which brand is performing. They can allocate ad budget to the best-performing site. They can also spot underperformers and fix them.

This setup also helps with regional targeting. If northwindoutdoor.com serves US customers and northwindkitchen.com serves EU customers, separate accounts keep those markets distinct.

Trade-Offs of Multi-Account Setups

Separate accounts give you clean data, but they come with costs. You need to manage more logins and more snippets. Each new website requires a new account setup.

Cost is another factor. If your SeaText plan charges per account, running many sites increases your monthly spend. Check your plan details to understand the pricing structure.

Monitoring also becomes more complex. You need to check each account separately for issues. A tracking error on one site might go unnoticed if you only look at one dashboard.

Despite these trade-offs, the data clarity usually wins. For multi-brand or multi-region operations, the benefits of clean attribution outweigh the management overhead.

Development vs. Production Domains

SeaText restricts localhost and development URLs for security reasons. You must use a valid, live domain for each installation to function properly.

If you are building a new site on a temporary subdomain or staging environment, that URL may not associate correctly with your account. Use your production domain from the start, or test on a domain that resembles your final URL structure.

Dynamic development domains that change frequently may cause tracking issues because SeaText cannot reliably match traffic to the correct account.

Limitations to Know

You cannot use one SeaText snippet to track several Odoo websites from a single account. If you try, the data will not attribute correctly and you may experience tracking gaps.

Free or trial accounts may have restrictions on the number of domains you can connect. Check your plan details if you need to manage more than two or three sites.

Changing the primary domain on an account after installation is not straightforward. If you switch domains, you may need to create a new account and reinstall the snippet.

Frequently Asked Questions

Can I use one SeaText account for multiple Odoo websites on subdomains?

No. Each account is linked to a single primary URL. Subdomains count as separate domains, so you need a separate account for each one.

Do I need separate Odoo databases for each website to use SeaText?

No. Odoo lets you run multiple websites from one database. SeaText only requires a unique domain and account for each site.

What happens if I install the same snippet on two different websites?

Traffic and conversions will not track correctly. Data from both sites will mix under one account, making it impossible to tell which website generated results.

Can I move my SeaText account to a new domain later?

Changing the linked domain is not a simple swap. You may need to create a new account and reinstall the snippet on the new domain to ensure clean tracking.

Do development and staging environments work with SeaText?

Only if they use valid, stable domains. Localhost and constantly changing dynamic URLs are restricted for security reasons.

Is there a limit to how many websites I can connect?

The limit depends on your SeaText plan. Check your account details or contact support if you need to manage more than a handful of domains.

Does SeaText support multi-brand Odoo setups?

Yes. Each brand's website can have its own SeaText account, letting you track performance, goals, and conversions separately for each brand.

Next Steps

Create a separate SeaText account for each domain you want to track. Then install the unique snippet on each corresponding Odoo website using the Embed Code block.

Visit the SeaText pricing page to check plan limits for multiple domains. This will help you understand any cost implications before you scale.

If you need help with the setup, refer to the SeaText Odoo integration documentation for detailed instructions.

Quick Answer: The Top Setup Mistakes

Most SeaText-for-Odoo failures come from four preventable errors: (1) pasting an incorrect or incomplete JavaScript snippet, (2) leaving the Embed Code block visible on desktop so visitors see raw code, (3) trying to activate on a localhost or staging domain that SeaText blocks for security, and (4) using one SeaText account across multiple domains instead of creating a separate account per domain. Fix any of these and the integration usually works on the next save.

Why the Odoo Integration Steps Matter

SeaText installs in Odoo through the Website module's "Embed Code" block inside the "Dynamic Content" section. The process is deliberate: drag the block, click Edit, paste the snippet, save, then toggle "Hide on Desktop" and save again. Skipping or reordering any step breaks the chain. The source instructions show the exact sequence: log in, open Website, edit the target page, find Dynamic Content, drag Embed Code, click Edit in the right panel, paste the SeaText snippet, save, set Hide on Desktop, save again.

Mistake 1: Using the Wrong Code Snippet

SeaText gives each account a unique JavaScript snippet. Copying a snippet from a different account, an old trial, or a documentation example will not work. The snippet must come from the live SeaText dashboard for the exact domain you are configuring. If you manage several sites, each needs its own account and its own snippet.

Mistake 2: Forgetting "Hide on Desktop"

After pasting the snippet, the Embed Code block remains visible on the page unless you open the Visibility section and check "Hide on Desktop." Without this, visitors see the raw script tag on your live site. The source pack explicitly lists this as a required step: "To ensure the block is hidden from view on desktop devices, select the 'Hide on Desktop' option in the 'Visibility' section. After making this adjustment, click on 'Save' once more to finalize your changes."

Mistake 3: Testing on Localhost or Dynamic Staging URLs

SeaText restricts development URLs such as localhost for security reasons. Dynamic development domains may also fail because the system cannot reliably associate traffic with your account. Use a real, publicly resolvable domain (e.g., staging.yourdomain.com) for any pre-production testing.

Mistake 4: One Account for Multiple Domains

Each SeaText account is linked to a single primary URL. If you run example.com and shop.example.com, you need two accounts. The source pack states: "If you need to use SEATEXT AI on multiple domains (e.g., a development domain and a production domain), you must create separate accounts for each domain. Each SEATEXT AI account is linked to a single primary URL."

Mistake 5: Not Refreshing the Page After Save

The integration guide ends with "Important: Visit or refresh your page to activate the script." Many users save the Embed Code block and assume it is live. A hard refresh (Ctrl+F5 or Cmd+Shift+R) forces Odoo to serve the updated page with the SeaText script injected.

Mistake 6: Insufficient Odoo User Permissions

Only users with Website edit rights can add and configure the Embed Code block. If your Odoo role lacks "Website / Admin" or equivalent access, the Dynamic Content section or the Edit button will not appear. Verify permissions before troubleshooting the snippet itself.

Mistake 7: Outdated Odoo Module List

Odoo caches the available blocks. If the "Embed Code" module does not appear under Dynamic Content, click the "Update Apps List" or "Update Modules List" button in the Apps menu, then reload the Website editor. This is a generic Odoo step but a common blocker for first-time SeaText installs.

Diagnostic Checklist When Activation Fails

1. Confirm you are logged into the correct SeaText account for the target domain.
2. Copy the snippet directly from that account's dashboard — no extra whitespace, no line breaks.
3. In Odoo Website editor, drag Embed Code → Edit → paste → Save.
4. Open Visibility → check Hide on Desktop → Save again.
5. Hard-refresh the live page (not the editor preview).
6. Open browser DevTools → Console → verify no SeaText-related errors.
7. If errors persist, confirm the domain in SeaText matches the live URL exactly (protocol, subdomain, TLD).

Key Facts at a Glance

Limitations and When This Advice Does Not Apply

These steps cover the standard JavaScript embed via Odoo's Website builder. They do not apply if you are injecting SeaText through a custom theme module, a server-side template override, or a headless frontend that consumes Odoo via API. In those cases the snippet placement and visibility logic differ. Also, SeaText's own dashboard may change UI wording; always copy the snippet from the current account view.

Terminology

• Embed Code block: Odoo Website block that accepts raw HTML/JS.
• Dynamic Content section: Category in the Blocks panel where Embed Code lives.
• Hide on Desktop: Visibility toggle that prevents the block from rendering on desktop viewports.
• Primary URL: The single domain a SeaText account is bound to.
• Hard refresh: Browser reload that bypasses cache (Ctrl+F5 / Cmd+Shift+R).

FAQ

Can I use the same SeaText account for a staging subdomain and production?

No. Each primary URL requires its own account. Create a separate SeaText account for staging.yourdomain.com and another for www.yourdomain.com.

Why is the Embed Code block not showing under Dynamic Content?

Update the Odoo Apps/Modules list, then reload the Website editor. The block appears after the module registry refreshes.

Do I need to paste the snippet on every page?

No. Place the Embed Code block on a global layout element (header, footer, or a master template page) so it loads site-wide. The source instructions show placing it on "the page you wish to edit," but a single global placement is standard practice.

What if I see the script tag on the live site?

You missed the "Hide on Desktop" step. Edit the block, open Visibility, check Hide on Desktop, save, then hard-refresh.

Does SeaText work on Odoo.sh or Odoo Online?

Yes, as long as the site uses a real domain and you have Website edit permissions. The same embed steps apply.

How do I verify the script is active?

Open the live page, inspect the page source or DevTools Network tab, and look for the SeaText JavaScript file loading from the SeaText CDN. No console errors means it initialized.

Can I install SeaText via an Odoo module instead of Embed Code?

SeaText does not publish a dedicated Odoo module. The supported method is the Embed Code block described above.

Why Odoo permissions matter for SeaText activation

SeaText runs on your site through a JavaScript snippet that you paste into an Odoo page. To do that, you must be able to open the Website module, enter edit mode, drag an Embed Code block, and save changes. If your user role blocks any of those steps, the integration stops before it starts.

The Odoo documentation defines access rights as permissions that determine which content and applications a user can view or edit. In practice, only users with the Administrator role or explicit Settings access can manage website blocks and install third‑party scripts.

Readiness Checklist

Before you start, verify every item below. If any box is unchecked, resolve it first.

• ☐ You have an Odoo user account with Administrator or Settings access.
• ☐ Your role includes Website / Admin or Website / Editor rights.
• ☐ You can open the Website module from the Odoo dashboard.
• ☐ You can enter Edit mode on a page.
• ☐ You can see the Dynamic Content section in the Blocks panel.
• ☐ You have a SeaText AI account already created.
• ☐ Your SeaText account uses a real, valid domain (not localhost).
• ☐ You have the SeaText JavaScript snippet copied from your dashboard.
• ☐ You know which page on your site will host the script.
• ☐ You have a way to test the page after saving (browser with dev tools).

If you have Administrator or Settings access, proceed. Otherwise, request an upgrade first.

Understanding Odoo access rights: Administrator vs Settings

Odoo groups permissions by application. The Website application has its own access levels. A user with full Administrator rights sees every app and can change any setting. A user granted only Settings access can configure installed modules but may not install new ones. For SeaText, you need at least the ability to edit website pages — typically the "Website / Admin" or "Website / Editor" rights.

If you are unsure which group you belong to, open the Users menu, click your name, and check the Access Rights tab. Look for Website entries. If you see "Admin" or "Editor", you can proceed. If you see only "User" or nothing, ask your Odoo administrator to upgrade your role.

Step‑by‑step: Checking your current Odoo role

1. Log in to Odoo.
2. Click your avatar in the top right and choose "My Profile".
3. Select "Access Rights" from the left sidebar.
4. Scroll to the Website section.
5. Confirm the value is "Admin" or "Editor".

If the field reads "User" or is blank, you lack permission to edit website content. Request an upgrade before continuing.

Preparing your Odoo environment for SeaText

Before you paste any code, ensure you have a SeaText account. The integration guide states: "Before you can install the script, you need a SEATEXT AI account. If you don't have an account yet, you can create one HERE" (S1). Create the account on a real domain — development URLs such as localhost are restricted for security reasons (S1).

Once the account exists, copy the JavaScript snippet from the SeaText dashboard. You will need this string in the next step.

Installing the SeaText embed code in Odoo Website

The Odoo integration page walks through the exact steps (S1):

1. Access the "Website" module from the dashboard.
2. Navigate to the page you want to edit and click "Edit".
3. In the editing panel, scroll the "Blocks" panel to the "Dynamic Content" section.
4. Drag the "Embed Code" module into the desired location.
5. Click the "Edit" button on the right panel to open the code input.
6. Paste the SeaText JavaScript snippet and click "Save".
7. Optionally, select "Hide on Desktop" in the Visibility section if you only want the script active on mobile, then save again.

These actions require write access to website pages. If the Edit button is greyed out or the Blocks panel is missing, your role does not include website editing rights.

Verifying activation and troubleshooting common issues

After saving, visit the page as a regular visitor. Open the browser developer tools (F12) and check the Console for SeaText initialization messages. If you see the script loading, activation succeeded.

Common failure points:

• Script not loading: The embed block may be inside a container that strips scripts. Move it to the page root.
• Console errors about domain mismatch: SeaText accounts are tied to a single primary URL. Using the snippet on a different domain (including a staging subdomain) will fail. Create a separate SeaText account for each domain (S1).
• Edit button missing: Your user lacks website editing rights. Revisit the role check above.

Limitations and when this advice does not apply

This checklist covers standard Odoo Website (formerly Odoo CMS) deployments. It does not apply to:

• Odoo.sh or on‑premise instances with custom security rules that override standard access groups.
• Headless Odoo setups where the frontend is a separate React/Vue app — there you inject the script in your frontend build, not via Odoo blocks.
• Odoo versions older than 14, where the Website module structure differs significantly.

If any of those scenarios match your setup, consult your Odoo developer or SeaText support for a tailored integration path.

Key facts at a glance

FAQ

Can I install SeaText with a standard "User" role in Odoo?

No. The User role only permits viewing published pages. You need edit access to add the Embed Code block.

What if my Odoo admin refuses to grant Administrator rights?

Ask for the specific "Website / Editor" permission instead. That narrower role still allows page editing and block management.

Do I need a separate SeaText account for my staging environment?

Yes. SeaText ties each account to a single primary URL. Staging subdomains count as separate domains (S1).

Will the SeaText script slow down my Odoo page load?

The script loads asynchronously. In most cases the impact is negligible, but you can verify with Lighthouse after activation.

Can I use the same SeaText snippet across multiple Odoo websites in one database?

Only if those websites share the same primary domain. Different domains require separate SeaText accounts (S1).

What happens if I paste the code but forget to click Save twice?

The first save stores the script. The second save (after toggling Hide on Desktop) persists the visibility setting. Both are required for the configuration to stick.

SeaText does not demand a special Odoo server build. The integration works through a standard JavaScript snippet that you paste into an Odoo "Embed Code" block on any page. The only hard requirements are a publicly reachable domain (no localhost or dynamic dev URLs) and an Odoo instance that can serve the Website module and allow outbound HTTPS calls to SeaText's API.

What SeaText Actually Needs from Your Odoo Server

SeaText runs as a client-side script. You copy a JavaScript snippet from your SeaText dashboard and place it inside an Odoo "Embed Code" block (found under Website → Edit → Blocks → Dynamic Content). Odoo then serves that script to every visitor. No server-side module, no custom Python code, no database migration.

Because the script loads in the browser, the Odoo server only needs to deliver the page containing the snippet. Any standard Odoo installation that runs the Website module and uses HTTPS will work. The source documentation confirms the steps: log in, open the Website module, edit a page, drag in the Embed Code block, paste the snippet, save, and optionally hide the block on desktop.

This means the server's job is simple. It must serve the HTML page. It must not block the script from loading. It must allow the browser to make outbound calls. That is the entire server-side requirement.

Network and Firewall Requirements

The snippet makes outbound HTTPS requests to SeaText's API endpoints to fetch personalized content, run A/B tests, and send conversion events. If your Odoo server sits behind a restrictive egress firewall, those calls will fail silently and the AI agents will not activate. Allow outbound TCP 443 to *.seatext.com and *.seatext.ai. No inbound ports are required.

If you use a reverse proxy (Nginx, Apache, Cloudflare) in front of Odoo, ensure it passes the Content-Security-Policy header without blocking script-src 'self' https://*.seatext.com. A misconfigured CSP is the most common reason the script loads but never phones home.

Check your proxy logs if the script loads but no personalization appears. Look for blocked requests to cdn.seatext.com or api.seatext.com. A 403 or 404 in the network tab usually points to a CSP or firewall issue.

Odoo Version Compatibility

SeaText's integration guide does not list a minimum Odoo version. The Embed Code block has existed since Odoo 12 (Website Builder rewrite). In practice, any Odoo 12+ instance with the Website module installed will render the block correctly. Odoo 10/11 users should upgrade first — those versions lack the block and receive no security patches.

Enterprise and Community editions behave identically for this integration. The only difference is that Enterprise includes the Website module by default; Community users must install it from the Apps menu.

If you run Odoo 12 or 13, the block works but the editor interface is older. The steps are the same. If you run Odoo 17 or 18, the block is still present. No version-specific code changes are needed.

Domain and SSL Considerations

SeaText ties each account to a single primary URL. The documentation states: "Development URLs, such as localhost, are restricted for security reasons. Ensure you use a valid, real domain for these cases. Dynamic development domains may not function properly, as SeaText AI might be unable to reliably associate traffic with your account."

This means:

• Production domain (https://shop.example.com) — works.
• Staging on a real subdomain (https://staging.example.com) — works if you create a separate SeaText account for it.
• Localhost, ngrok tunnels, *.local, *.test — blocked.
• Dynamically generated preview URLs (e.g., GitHub Pages preview, Vercel preview deployments) — unreliable; use a stable subdomain instead.

SSL is mandatory. The snippet loads over HTTPS; mixed-content warnings will stop it on HTTP sites.

If you use a self-signed certificate on a staging server, the browser will block the script. Use a valid certificate from Let's Encrypt or your hosting provider.

Common Configuration Pitfalls

1. Embed Code block not visible. You must be in "Edit" mode on a Website page. The block lives under Dynamic Content. If you don't see it, confirm the Website module is installed and you have editor permissions.
2. Script saved but nothing happens. Check browser dev tools → Network. Look for a request to cdn.seatext.com or api.seatext.com. If it's blocked, inspect CSP and firewall rules.
3. Multiple domains on one account. The docs are explicit: "If you need to use SeaText AI on multiple domains … you must create separate accounts for each domain." Sharing one snippet across domains breaks attribution and billing.
4. Hiding the block incorrectly. The guide recommends "Hide on Desktop" in the Visibility section so the empty container doesn't affect layout. Forgetting this step leaves a zero-height div — usually harmless but can shift CLS on slow connections.
5. Wrong snippet pasted. Each account has a unique snippet. Pasting the wrong one sends traffic to the wrong account. Check the domain in your SeaText dashboard before copying.
6. Blocked by ad blockers. Some browser extensions block third-party scripts. This is a client-side issue, not a server issue. SeaText offers a Cloudflare edge deployment option to bypass some blockers.

Key Facts

Limitations and When This Advice Does Not Apply

• On-premise Odoo with no internet access. SeaText cannot function if the server cannot reach its API. Consider a cloud proxy or move the snippet to a CDN edge worker (Cloudflare Workers) that forwards calls.
• Odoo.sh or Odoo Online with strict CSP. Platform-managed instances may lock down script-src. You may need to request a CSP exception from Odoo support.
• Headless Odoo (API-only). If you don't serve Website pages, there's nowhere to inject the snippet. SeaText requires a rendered page.
• Custom Odoo themes that strip Dynamic Content blocks. Rare, but some theme overrides remove the block registry. Switch to a standard theme or ask the theme vendor to re-enable the block.
• Very old Odoo versions (below 12). The Embed Code block does not exist. You would need to inject the snippet via a custom template or a third-party module. This is not supported by SeaText's official guide.
• Odoo with a strict reverse proxy that strips query strings. Some proxies remove parameters needed by SeaText for attribution. Test with a clean proxy configuration.

Practical Scenarios and Decision Criteria

You are setting up SeaText on a new Odoo site. You have a production domain with HTTPS. You install the Website module. You paste the snippet. It works. No server changes needed.

You are testing on a staging server. You use a real subdomain like staging.example.com. You create a separate SeaText account. You paste the staging snippet. It works. Do not use the production snippet on staging.

You have a firewall that blocks all outbound traffic. You must open TCP 443 to SeaText domains. If you cannot, SeaText will not work. You need a network change before activation.

You use Cloudflare in front of Odoo. Cloudflare may inject its own CSP. You must allow script-src for SeaText. Check Cloudflare's "Transform Rules" or "Headers" settings.

You run Odoo Community. You install the Website module from the Apps menu. The Embed Code block appears. Everything else is identical to Enterprise.

You have multiple websites on one Odoo instance. Each website needs its own SeaText account. Paste the correct snippet into each website's pages. Do not share snippets.

FAQ

Do I need root access to the Odoo server?

No. The integration is done entirely from the Odoo backend UI. You only need editor access to the Website module.

Can I use SeaText on an Odoo development database?

Only if the dev database is reachable via a real domain name with HTTPS. Localhost, IP addresses, and temporary tunnels are blocked.

What if my firewall blocks outbound connections?

The script will load but never contact SeaText. You'll see no personalization, no A/B tests, no conversion tracking. Open TCP 443 to SeaText domains.

Does SeaText work with Odoo's multi-website feature?

Yes, but each website needs its own SeaText account and snippet. Paste the correct snippet into each website's pages.

Will SeaText slow down my Odoo pages?

The snippet is ~2 KB gzipped and loads asynchronously. It adds negligible latency. SeaText also offers a Cloudflare edge deployment option for zero-redirect latency.

Can I test SeaText before pointing production traffic?

Create a staging subdomain (e.g., staging.example.com), provision a separate SeaText account for it, and test there. Do not use the production snippet on staging.

What happens if I paste the wrong account's snippet?

Traffic will be attributed to the wrong SeaText account. Billing, analytics, and personalization will be mixed. Always match snippet to domain.

Do I need to configure anything in Odoo's settings?

No. There is no Odoo setting for SeaText. The integration is purely client-side. You only need the Website module and a reachable domain.

What if my Odoo server uses HTTP instead of HTTPS?

The script will not load due to mixed-content restrictions. You must enable HTTPS on your Odoo server. Use a valid SSL certificate.

Can I use SeaText on an Odoo instance behind a load balancer?

Yes. The load balancer must pass HTTPS traffic and not strip headers. Ensure the load balancer forwards the Host header correctly.

You set it up by defining your audience segments, creating the personalized variation, and using a CRO tool to split traffic between the original page and the personalized experience while tracking conversion metrics.

This approach lets you see which version drives more leads or sales without rebuilding your site.

Definition and scope

An A/B test for personalized landing pages compares a generic version with a version that changes copy, offers, or layout based on visitor data such as ad keyword, referral source, or past behavior.

The goal is to prove that personalization actually improves conversions. Without a test, you are guessing. With a test, you get evidence.

This method works for any page that receives traffic from ads, email, social, or search. It is especially useful for paid campaigns where you know the exact keyword or source.

How it works

You create two URLs: one serves the original page, the other serves the personalized version. A testing tool routes visitors randomly to each URL and measures actions like form submissions or purchases.

The tool assigns each visitor to a variant based on rules you set. For example, visitors from a specific ad campaign go to the personalized URL. Everyone else sees the original.

Because each visitor sees a fully rendered page, there is no flicker or layout shift. This is a key advantage over element-level testing.

Main options and trade-offs

You can use a dedicated split-URL testing platform, a general A/B testing tool with URL targeting, or build a custom solution with JavaScript redirects. Dedicated platforms give faster setup and built-in analytics but may cost more; custom solutions give full control but require engineering time.

Dedicated split-URL platforms fit most marketing teams. They remove the need for engineering. General A/B tools work if you already have one and only need simple URL splits. Custom JavaScript fits only when you have a specific requirement that off-the-shelf tools cannot meet.

Check with the vendor for exact pricing and feature limits.

Step-by-step implementation

1. Define the audience segments you want to personalize for (e.g., visitors from a specific Google Ads keyword).
2. Create the personalized landing page variant, changing only the elements you want to test (headline, offer, CTA).
3. Set up the split-URL test in your CRO tool, entering the original URL and the personalized URL.
4. Allocate traffic – a 50/50 split is common, but you can weight toward the variant if you prefer.
5. Choose the conversion goal to track (e.g., form submit, purchase).
6. Launch the test and monitor traffic distribution.

Before you launch, verify that your tracking pixels fire on both URLs. If analytics does not record visits on the variant, the test is invalid.

Also set a minimum sample size. Use a sample size calculator based on your baseline conversion rate and the lift you want to detect. For low-traffic pages, this may mean running the test for several weeks.

Audience segmentation and personalization strategies

Segmentation is the foundation of any personalized test. You must decide who gets the personalized version. Common segments include:

• Visitors from a specific Google Ads campaign or keyword group.
• Visitors who clicked a particular email link.
• Visitors from a specific referral source (e.g., a partner site).
• Returning visitors who have viewed a product before.
• Visitors in a specific geographic region.

Each segment should be large enough to produce meaningful data. If a segment has only 50 visitors per month, you will wait a long time for results.

Personalization strategies vary by segment. For ad keywords, rewrite the headline to match the exact search term. For email clicks, show a special offer or banner. For returning visitors, highlight a product they viewed earlier.

Keep the change focused. Do not rewrite the entire page. Change one or two key elements. This makes it easier to attribute any conversion lift to the personalization.

Traffic allocation methods

The simplest method is a 50/50 split. Half of the eligible visitors see the original, half see the personalized version. This gives you a clean comparison.

However, 50/50 is not always optimal. If you are confident the personalized version will perform better, you might allocate 70% to the variant and 30% to the control. This reduces the cost of showing a losing page to many visitors.

More advanced tools use multi-armed bandit algorithms. These dynamically shift traffic toward the better-performing variant as data comes in. Instead of waiting for a fixed sample size, the algorithm learns in real time.

Bandit allocation is especially useful for low-traffic sites. It can reach a winner faster than a fixed split. It also reduces the number of visitors who see a losing variant.

When choosing an allocation method, consider your traffic volume and your tolerance for risk. Fixed splits are simpler to explain. Bandits are more efficient but require a tool that supports them.

Statistical significance and test duration

Statistical significance tells you whether the observed difference is real or just random noise. The standard threshold is 95% confidence. This means there is only a 5% chance the result is a false positive.

To reach 95% confidence, you need enough conversions in each variant. The required sample size depends on your baseline conversion rate and the size of the lift you want to detect.

For example, if your baseline conversion rate is 2% and you want to detect a 20% relative lift, you need roughly 8,000 visitors per variant. At 1,000 visitors per month, the test would take 8 months.

This is why many low-traffic sites struggle with traditional A/B testing. The math simply does not work in a reasonable timeframe.

Some modern tools use reading telemetry instead of binary conversion tracking. They analyze how visitors read and scroll the page. This provides signal much faster than waiting for conversions. It can identify friction points and generate copy variants automatically.

If you cannot wait months for results, consider a tool that uses adaptive algorithms or reading telemetry. These can produce actionable insights in days rather than months.

Common mistakes to avoid

Mistake 1: Testing too many changes at once. If you change the headline, offer, and CTA simultaneously, you cannot tell which one caused the lift. Test one element at a time.

Mistake 2: Ignoring sample size. Launching a test with 200 visitors and declaring a winner is meaningless. The result is almost certainly noise.

Mistake 3: Stopping the test too early. If you check results daily and stop as soon as one variant leads, you risk a false positive. Let the test run to the planned sample size.

Mistake 4: Not segmenting correctly. If your tracking is broken, visitors from different sources may be mixed into the wrong group. Verify your data before launching.

Mistake 5: Forgetting about SEO. If you use a separate URL for the variant, make sure it is not indexed by search engines. Add a noindex tag or use a canonical tag to avoid duplicate content issues.

Mistake 6: Overlooking mobile. Personalization that works on desktop may not work on mobile. Test on both devices or at least verify the variant renders correctly on mobile.

Advanced personalization techniques

Beyond simple keyword matching, you can use more sophisticated personalization. One technique is dynamic copy rewriting based on the visitor's full context. This includes the ad campaign, the device, the time of day, and the visitor's browsing history.

Another technique is AI-driven copy generation. Instead of manually writing one variant, you generate multiple variants automatically. The tool then tests them and scales the winner.

Reading telemetry is another advanced method. It tracks how visitors read the page, where they pause, and where they scroll back. This reveals friction points that binary conversion data misses.

For example, if visitors repeatedly re-read a section, that section may be confusing. The AI can then generate a clearer version and test it automatically.

Multi-armed bandit optimization is also advanced. It continuously reallocates traffic to the best-performing variant. This is more efficient than a fixed split and works well with AI-generated variants.

Finally, consider account-based personalization for B2B. This adapts the page to the specific company or account visiting. It can include the company name, industry-specific messaging, or tailored offers.

Practical scenarios

Scenario 1: You run a Google Ads campaign for "running shoes" and want to test whether a headline that includes the exact keyword improves conversions over a generic headline.

You create a personalized URL that shows "Best Running Shoes for Your Next Race" when the visitor comes from the "running shoes" keyword. The original page shows "Shop Our Athletic Footwear Collection." You split traffic 50/50 and track purchases.

Scenario 2: You have an email campaign that drives traffic to a product page and want to test a personalized discount banner for visitors who clicked the email versus a standard banner for all others.

You create a variant URL that shows a 10% off banner for email visitors. The original page shows a standard banner. You track sign-ups and purchases.

Scenario 3: You run a B2B site and want to personalize for visitors from a specific industry. You create a variant that uses industry-specific language and case studies. You track demo requests.

In each scenario, the key is to define the segment clearly and measure the right conversion metric.

Limitations

This method works best when you can create a separate URL for the variant. If your platform does not support URL-level changes, you may need to use client-side rendering tricks that can cause flicker or affect SEO.

Personalization relies on accurate visitor data. If your tracking of ad keyword or referral source is incomplete, the test groups may be mixed. This can invalidate your results.

Low-traffic sites face a major limitation. Reaching statistical significance can take months. By the time you have results, the market may have changed.

Another limitation is cost. Dedicated split-URL platforms often charge based on traffic volume. For high-traffic sites, this can be expensive.

Finally, personalization can sometimes feel intrusive. If the personalization is too aggressive or inaccurate, it may hurt trust. Test carefully and monitor user feedback.

FAQ

• Why use split-URL testing instead of element-level A/B testing?
  Split-URL testing avoids any risk of flicker or layout shift because each visitor sees a fully rendered page, which is important for personalization that may change many elements at once.
• How long should I run the test?
  Run it until each variant reaches enough conversions to achieve your desired confidence level; for low-traffic sites this may take weeks, but AI-driven tools can reduce the time by allocating more traffic to the better variant.
• What does it cost?
  Costs depend on the CRO platform; some charge a monthly fee based on traffic volume, while others offer pay-as-you-go pricing. Check the vendor's pricing page for details.
• What should I compare when choosing a tool?
  Compare setup effort (e.g., 60-second edge script vs. code installation), traffic routing method (split-URL vs. client-side), built-in analytics, and any requirements such as tag limits or data privacy certifications.
• Can I run multiple personalized tests at once?
  Yes, but each test should have its own clearly defined segment and conversion goal. Running too many tests simultaneously can dilute traffic and slow down results.
• What if my personalized variant performs worse?
  That is a valid outcome. It means your personalization hypothesis was wrong. Use the data to refine your approach and test again. Do not force a winner.

For a faster setup with zero redirect latency and no site rebuilds, explore Seatext's AI split-URL testing solution.

CTA: See how Seatext can automate your landing page personalization tests.