SeaText does not combine multiple Odoo domains onto one bill. Each SeaText account is linked to a single primary URL, so you need a separate account for every domain. Your total SeaText billing is the sum of the plans attached to those accounts.

For example, a production domain and a development domain need two accounts and two subscriptions. You manage billing by keeping each account's plan current, not by adding domains to an existing account.

Why billing matters for multiple Odoo domains

Billing structure affects your cost predictability. When you know each domain needs its own account, you can forecast your monthly spend accurately. You avoid surprises when you add a new site or a staging environment.

It also prevents traffic misattribution. If you reuse one account across two domains, SeaText may not associate traffic correctly with your account. That can skew your analytics and make your AI agents less effective.

Finally, it avoids setup errors. If you try to install one snippet on two sites, you may break the single-URL rule)Skip. That can lead to failed installations or missing data. Planning per domain from the start keeps everything clean.

How SeaText billing works for multiple Odoo domains

SeaText bills per account, not per Odoo instance. The integration guide states that each SEATEXT AI account is linked to a single primary URL. If you use SeaText on multiple domains, you must create separate accounts for each domain.

That creates a simple billing model: each domain has its own account, and each account has its own plan. There is no consolidated invoice that groups several domains under one seat. To estimate your monthly cost, add the plan price for each domain you want to cover.

For example, if you have a production site and a staging site, you need two accounts. If each plan costs $50 per month, your total is $100 per month. There is no discount for bundling domains in the current documentation.

Step-by-step: Set up billing for each domain

1. List every Odoo domain that needs SeaText. Include production, staging, and separate brand sites. A domain is defined by its primary URL.
2. Create one SeaText account per domain. Do not share an account across domains. The source pack says to create one account for each website.
3. Choose a plan for each account. SeaText's pricing page shows current rates. Your total is the sum of those plans.
4. Copy the JavaScript snippet from the correct account. Each account's snippet is tied to that account's primary URL.
5. Install the snippet in Odoo. In the Website module, open the page you want to edit, drag the Embed Code module from Dynamic Content, paste the snippet, and save. To keep the block hidden on desktop, choose 'Hide on Desktop' and save again.
6. Verify the primary URL. Make sure the account's primary URL matches the domain where you installed the snippet. Then visit or refresh the page to confirm it loads.

Prerequisite: use a valid, real domain. Localhost is restricted, and dynamic development domains may not work reliably.

One account vs. separate accounts: trade-off table

Choose separate accounts for every distinct domain. There is no supported one-account-for-all path in the source documentation.

What counts as a domain for SeaText billing?

The source pack defines the rule by URL, not by Odoo instance. Each account is linked to a single primary URL. So if you have two Odoo storefronts on different domains, they count as different domains for account and billing purposes.

The integration guide doesn't explain how subdomains are handled. If you plan to use a subdomain like shop.example.com in addition to example.com, treat it as a separate URL and confirm with SeaText before you commit to a billing setup.

Also, if you run multiple Odoo instances on the same domain, that still counts as one primary URL. You would only need one account for that domain. But if you use different domains for different instances, each needs its own account.

Common billing mistakes with multiple domains

• Reusing one account on two sites. The account is tied to one primary URL, and the guide tells you to create separate accounts.
• Using localhost or dynamic development URLs. These are restricted or unreliable, so you may see no correct traffic association.
• Forgetting to refresh or visit the page after installation. The integration guide says to visit or refresh the page as part of the setup.
• Assuming you can merge domains later. Because each account is locked to a single URL, the supported workflow is separate accounts.
• Not checking current pricing before adding domains. Rates change; use the official pricing page for today's numbers.
• Mixing up snippets between accounts. If you paste the wrong snippet, the traffic may not associate with the correct account. Double-check each snippet before saving.

Limitations and when this advice doesn't apply

This billing model applies when each Odoo domain is a separate primary URL. If you only have one domain, you only need one account and one plan.

If SeaText adds a multi-domain plan in the future, this advice will change. Also, the source pack doesn't cover subdomains, multiple Odoo instances on the same domain, or enterprise contracts. In those cases, check with SeaText directly.

Another limitation is that dynamic development domains may not work. If your staging URL changes frequently, you may need to use a stable subdomain or a dedicated staging domain to ensure reliable traffic association.

Frequently asked questions about SeaText billing and multiple domains

Can I add a second Odoo domain to my existing SeaText account?

No. The integration guide says each account is linked to a single primary URL, so you need a new account for each additional domain.

Do I pay twice for two domains?

You pay per account, not per domain label. Each domain needs its own account, so your total cost is the sum of the plans for those accounts. Check the current pricing page for exact amounts.

Can I use localhost to test SeaText?

No. Localhost is restricted for security reasons.

What if my staging domain changes often?

Dynamic development domains may not function properly because SeaText might not associate traffic with your account. Use a stable, real domain for testing.

Does SeaText have a multi-domain plan?

The Odoo integration page doesn't describe one. It explicitly says to create one account per domain. If a multi-domain option exists, it will be listed on the current pricing or product pages.

How do I verify my billing setup is correct?

For each domain, confirm that the account's primary URL matches the actual domain and that the SeaText snippet is installed on that site only. Visit or refresh the page after saving.

Can I use one account for a production domain and a staging subdomain?

The source pack doesn't clarify subdomain handling. Treat a subdomain as a separate URL and confirm with SeaText before you set up billing. It may require a separate account.

What happens if I install the wrong snippet on a domain?

Traffic may not associate with the correct account. That can lead to inaccurate analytics and reduced AI effectiveness. Always verify the snippet matches the account's primary URL.

Brand bridge: Learn more about SeaText pricing

For current pricing and plan details, visit the SeaText pricing page. You can also check the Odoo integration guide for the latest setup instructions. If you have multiple domains, plan your accounts carefully to keep billing predictable.

Here is the short answer: SeaText does not allow one account to work on two different Odoo domains. Each SeaText account is linked to a single primary URL. If you need SeaText on more than one Odoo domain, you must create a separate account for each domain. Trying to use the same account on a second domain will fail or mix data. So the difference is not a choice—separate accounts are the only way.

Who should choose separate SeaText accounts?

Every user who runs multiple Odoo domains must use separate accounts. This includes:

• Production + staging domains – You need clean data per environment, and SeaText requires a unique account for each.
• Multiple brand websites – If you operate two or more Odoo websites for different brands, each needs its own SeaText account.
• Multi-company setups – Each company’s domain should have its own account to avoid billing confusion and data overlap.

If you only have a single Odoo domain, one SeaText account is all you need. But as soon as you add another domain, create a new account.

Why one account cannot serve multiple domains

The reason is technical, not a business choice. SeaText’s account model is built around a single primary URL. When you create an account, you register one domain. The system then issues a JavaScript snippet tied to that domain.

That snippet is not generic code. It carries an identifier linked to the registered domain. When the script loads in a browser, it checks the current page URL. If the URL does not match the registered primary URL, SeaText cannot reliably attribute traffic, conversions, or AI training data.

The official SeaText Odoo integration page states this directly: each account is linked to a single primary URL, and accounts must be separate for each domain. The same page notes that development URLs such as localhost are restricted for security reasons, and dynamic development domains may not function properly.

This design protects three things at once:

• Data accuracy – Analytics and AI learning stay tied to the correct site.
• Security – The script cannot be moved between unrelated sites without re-registration.
• Billing clarity – Each account has its own subscription, so usage maps cleanly to a domain.

How SeaText accounts work with Odoo domains

SeaText integrates with Odoo via a JavaScript code snippet. You copy the snippet from your SeaText account, then paste it into the Odoo website editor using the “Embed Code” module. That snippet is tied to the primary URL you entered when you created the account.

The integration steps on the official page are:

1. Log in to Odoo and open the Website module.
2. Navigate to the page you want to edit and click “Edit.”
3. In the Blocks panel, scroll to “Dynamic Content.”
4. Drag the “Embed Code” block onto the page.
5. Click “Edit” in the right panel and paste the SeaText code snippet.
6. Save, then enable “Hide on Desktop” if you want the block invisible on large screens.
7. Save again to finalize.

If you try to paste the same snippet on a different domain, SeaText will not work correctly. The system associates all traffic and data with the original domain only. For a new domain, you need a fresh account with its own snippet.

Key facts about SeaText accounts

When separate accounts are mandatory

SeaText requires separate accounts in these situations:

• Multiple Odoo domains – Every domain name needs its own account.
• Development vs. production – Staging or dev domains must have their own account to avoid polluting production data.
• Different business units – If you run separate Odoo instances for different divisions, each needs its own SeaText account.

There is no exception. SeaText’s architecture is built around a single primary URL per account.

Cost implications of multiple SeaText accounts

Since each account requires a separate subscription, your monthly cost multiplies by the number of domains. For example, if you have two production domains and one staging domain, you need three plans.

SeaText pricing information can be found on their website. The cost per account is the same whether you have one or fifty—there is no bulk discount at this time. Check with SeaText for current pricing and plan options.

For teams watching budget, the practical decision is which domains truly need SeaText. A staging domain used only for internal QA may not need a paid plan. A production domain used for ads and SEO clearly does. The rule is simple: one domain, one account, one bill.

Step-by-step setup for separate SeaText accounts per Odoo domain

1. Log in to SeaText and create a new account for each Odoo domain. Use the domain’s URL as the primary URL.
2. After creation, copy the JavaScript snippet provided in each account’s integration section.
3. In Odoo, go to Website → Edit the page → Blocks → Dynamic Content → Embed Code.
4. Drag the Embed Code block into the page and paste the snippet. Save.
5. For each domain, repeat this process using the snippet from that domain’s SeaText account.

Keep a simple spreadsheet with three columns: domain name, SeaText account email, and snippet location. This avoids mixing snippets across accounts and saves time when you audit setups.

Limitations and what to watch out for

• No consolidation possible – You cannot merge multiple accounts later. Plan account creation from the start.
• Staging domains – Dynamic development URLs (like localhost or temporary staging links) may not work. Use a real, valid domain.
• Account management – You will have to log into each account separately to view analytics or change settings.
• Shared team access – Adding team members must be done per account. There is no master login that sees all accounts at once.
• Snippet drift – Updating or replacing a snippet must be done in every account individually.

These limits are not flaws. They reflect the per-domain model. Knowing them upfront helps you avoid surprises during setup or audits.

Practical scenarios and which option fits

Here are common setups and the right call for each:

• Single production site – One SeaText account. No need for more.
• Production + staging – Two accounts. Keep test data separate from live data.
• Two brand sites on different domains – Two accounts. Each brand keeps its own analytics and AI training.
• Multi-country sites on country-specific domains – One account per country domain. Avoid mixing visitor behavior across regions.
• Localhost development – Not supported. Use a real subdomain for testing.

The pattern is simple. The number of accounts equals the number of real, distinct domains where SeaText needs to run.

Frequently Asked Questions

Can I use the same SeaText code on two different Odoo websites?

No. The code snippet is tied to the primary URL of the account. It will not function correctly on a second domain.

Do I need a separate account for a staging or test Odoo domain?

Yes, you need a separate SeaText account if you want SeaText to run on staging. However, be aware that dynamic staging URLs may cause issues; use a fixed subdomain like staging.yourdomain.com.

Will I pay the same price for each account?

Each account requires its own subscription at the current listed price. There is no shared plan or volume discount currently mentioned. Check with SeaText for the latest pricing.

What happens if I mistakenly use the same snippet on two domains?

SeaText may not work on the second domain, or data from both sites may mix into one account, leading to inaccurate analytics. Remove the snippet from the wrong domain and create a new account instead.

Can I manage all my SeaText accounts from one dashboard?

No, each account has its own dashboard. You must log in separately. SeaText does not currently offer a master account view.

How long does it take to create a new account and set it up in Odoo?

About 5 minutes per account, assuming you already have an Odoo website ready.

Why are localhost and dynamic URLs restricted?

SeaText restricts these URLs for security and reliability. The system needs a stable, real domain to associate traffic and conversions correctly. Localhost and changing URLs cannot be tracked reliably.

Can I move data from one SeaText account to another?

No. Accounts are independent. Plan your account structure before launch so you do not need to migrate data later. Check with SeaText if a specific data export option exists for your plan.

Summary: one account per Odoo domain

The difference between one SeaText account and separate accounts is not a flexible tradeoff. It is a hard rule: one account, one Odoo domain. This keeps data clean, billing clear, and security tight. If you run multiple domains, set up one account per domain. If you run only one domain, a single account is enough.

Direct Answer: How to Install SeaText in Odoo

To install SeaText in Odoo, you embed a JavaScript code snippet into your website using the Website module's Embed Code block. You need a SeaText AI account first, then log into Odoo, edit the target page, drag the Embed Code module from Dynamic Content, paste the snippet, hide the block on desktop, and save. This is not an Odoo App Store app; it is a third-party script.

Process at a Glance

What the SeaText Integration Actually Is

SeaText is not an Odoo app from the Odoo App Store. It is a JavaScript snippet that you add to your Odoo website using the built-in Website builder. Once installed, the AI remains inert until you activate it, so your site content stays safe.

This integration matters because it lets you add SeaText's AI agents—like conversion optimization, translation, and SEO tools—to your Odoo site without modifying core Odoo code. The script runs in the visitor's browser, not on your Odoo server. That means no database changes, no module conflicts, and no need for Odoo developer skills.

The script is lightweight and loads asynchronously. It does not block page rendering. It only becomes active when you turn on the specific SeaText agent you want. This keeps your site fast and your content unchanged until you choose to activate the AI.

Prerequisites Before You Start

• A SeaText AI account. If you don't have one, create it at seatext.com.
• The JavaScript code snippet from your SeaText account dashboard. It appears in a section labelled “SEATEXTCODEINTEGRATION” on the integration page.
• Access to Odoo’s Website module with edit permissions.
• A real, valid domain. Development URLs like localhost are not allowed. Dynamic development domains may not work reliably.

Why does the domain matter? Each SeaText account is linked to a single primary URL. The script uses that URL to associate traffic with your account. If you use localhost or a dynamic domain, SeaText cannot reliably match visitors to your account. That means the AI may not function correctly.

If you manage multiple Odoo sites, you need a separate SeaText account for each domain. Do not try to reuse one account across different websites. The script is tied to one primary URL only.

Step-by-Step Installation Guide

1. Log in to your Odoo account and go to the Website module from the dashboard.
2. Navigate to the page you want to edit and click the Edit button to open the editing panel.
3. In the editing panel, scroll through the Blocks panel until you reach the Dynamic Content section.
4. Locate the Embed Code module inside Dynamic Content and drag it to the desired location on your page editor.
5. Click the Edit button on the newly placed module (right panel). A pop-up window appears.
6. Paste the code snippet provided by SeaText into the designated area, then click Save.

What does the code snippet look like? The SEATEXTCODEINTEGRATION section contains a JavaScript snippet. It typically includes a script tag with a source URL pointing to seatext.com, plus a small configuration object with your account ID or domain key. The exact contents vary by account, but it is a single block of JavaScript you copy and paste exactly.

Why use the Embed Code block instead of a native module? Odoo's Website builder is designed for non-developers. The Embed Code block lets you insert any HTML or JavaScript without touching Odoo's source code. This is a trade-off: you get quick installation, but you lose the structured configuration a native module would provide. A native module would appear in the Apps menu and offer settings screens. The script approach is simpler but requires manual management.

Hiding the Code Block from Desktop Visitors

The Embed Code block is visible on the front end by default. To hide it so it does not show as a blank box on your site:

1. Select the block and go to the Visibility section in the right panel.
2. Choose Hide on Desktop.
3. Click Save again to finalize the changes.

Why hide it? The Embed Code block renders as an empty container on the page. Without hiding it, visitors see a blank space or a small gap in your layout. That looks unprofessional and can confuse users. Hiding it on desktop removes the visual artifact while keeping the script active.

What about mobile? The instructions specifically say to hide on desktop. On mobile, the block may still show. You can also hide it on mobile if needed, but the standard SeaText guide only mentions desktop. Test your page on both devices after installation to ensure no blank boxes appear.

Verifying the Installation

Refresh your website page and check that the SeaText script is loaded. You can use your browser’s developer tools (Network tab) to look for a request to seatext.com or the script name. If you see it, the integration is active.

Here is a more detailed verification process:

1. Open your website in a browser.
2. Press F12 to open Developer Tools.
3. Go to the Network tab.
4. Refresh the page.
5. Look for a request to seatext.com or a script file with “seatext” in the name.
6. If you see it, the script loaded successfully.

You can also check the Console tab for any errors. If the script fails to load, you may see a 404 error or a CORS warning. That usually means the snippet was pasted incorrectly or the domain is not registered in your SeaText account.

Another quick check: view the page source (Ctrl+U) and search for “seatext”. If the snippet is there, it is embedded correctly. If not, go back to the Embed Code block and re-paste the code.

Why This Integration Matters for Your Odoo Site

SeaText adds AI-powered capabilities to your Odoo website. These include conversion rate optimization, website translation, AI SEO content generation, and bot traffic protection. All of these run through the same JavaScript snippet.

For an Odoo store, this means you can improve conversions without hiring a developer. The AI agents analyze visitor behavior, test copy variants, and adapt landing pages in real time. That is a significant advantage over static pages.

The integration also matters because it is non-invasive. Your Odoo database stays untouched. Your modules remain intact. If you ever want to remove SeaText, you simply delete the Embed Code block. No uninstall process, no data cleanup, no risk to your Odoo system.

This is a key trade-off. A native Odoo module would give you deeper integration, like access to Odoo's internal data models. But it would also require more setup, more maintenance, and more risk of conflicts. The script approach is lighter and safer for most users.

Practical Use Cases and Scenarios

Here are common situations where you would install SeaText on Odoo:

• E-commerce store: You want to test different product descriptions to see which converts better. SeaText's CRO agent handles this automatically.
• B2B website: You want to translate your site into multiple languages to reach international buyers. SeaText translates up to 125 languages with one click.
• Ad campaign landing page: You run Google Ads and want each visitor to see copy matching their search keyword. SeaText rewrites the landing page in real time.
• Local SEO: You want to rank for “near me” searches in multiple cities. SeaText generates hyper-localized pages.
• Bot protection: You are losing ad spend to bot clicks. SeaText detects and blocks non-human traffic.

In each case, the installation is the same. You paste the snippet once, and all active agents run. You can enable or disable specific agents from your SeaText dashboard without touching the Odoo code again.

Troubleshooting Common Issues

If the script does not work, check these common problems:

• Incomplete snippet: Make sure you copied the entire code from the SEATEXTCODEINTEGRATION section. Missing characters break the script.
• Extra spaces or line breaks: When pasting, avoid adding spaces or newlines. Paste it exactly as copied.
• Wrong domain: Your SeaText account is linked to one primary URL. If you installed on a different domain, the script will not associate traffic correctly.
• Development URL: localhost is not allowed. Use a real domain.
• Embed Code block missing: Ensure you are in edit mode on the correct page. The block is under Dynamic Content. If it still does not appear, your Odoo version may not support it.
• Browser cache: Clear your browser cache and refresh. Old cached versions may not load the new script.

If you still see errors, check the browser console. Look for messages about seatext.com. A 404 means the script URL is wrong. A CORS error means the domain is not allowed. Contact SeaText support if the issue persists.

Frequently Asked Questions

Do I need to be an Odoo administrator to install SeaText?

You need at least edit access to the Website module. Administrator rights are not required, but if you cannot see the Edit button, ask your admin.

Can I install SeaText on Odoo Community Edition?

Yes, as long as your Odoo instance includes the Website module. The integration works with both Community and Enterprise editions.

What if the Embed Code module is missing from the Blocks panel?

Make sure you are in edit mode on the correct page. The Embed Code is under “Dynamic Content”. If it still does not appear, your Odoo version may not support it; try upgrading or contact Odoo support.

Will the SeaText script slow down my website?

SeaText is designed to be lightweight. The script loads asynchronously and does not affect page load times significantly. You can test performance using tools like Google PageSpeed Insights.

How do I uninstall SeaText?

Delete the Embed Code block from your page. The script will stop running. You can also deactivate your SeaText account from the dashboard.

Can I use SeaText on multiple pages?

Yes. Repeat the installation steps for each page where you want the AI to operate. Each page needs its own Embed Code block with the same snippet.

What if I get an error when pasting the code?

Double-check that you copied the entire snippet from your SeaText account. Ensure there are no extra spaces or line breaks. Refresh the Odoo editor and try again.

Can I use one SeaText account for multiple domains?

No. Each SeaText account is linked to a single primary URL. If you need SeaText on multiple domains, create a separate account for each domain.

Does SeaText modify my Odoo database?

No. The script runs in the browser. It does not touch your Odoo database or modify any Odoo records.

Is SeaText secure?

Yes. The script is secure and remains inert until you activate it. It does not alter your website content unless you enable a specific agent.

Ready to Install SeaText on Your Odoo Site?

Visit the SeaText Odoo Integration page for the code snippet and pricing details. Create your SeaText AI account first, then follow the steps above to embed the script. If you need help, contact SeaText support for assistance.

You likely can't see the SeaText app because it's not an Odoo app or module. SeaText integrates with Odoo through a JavaScript snippet that you embed into the Website builder, not as a clickable menu item. If you looked in the Apps menu and didn't find it, that's normal. The real question is whether the SeaText script is actually running on your site.

Why SeaText Appears Differently Than Other Odoo Apps

Odoo has two types of add-ons: native apps installed from the Apps menu, and external scripts loaded via the Website builder. SeaText belongs to the second group. The integration guide from SeaText explains that you need to log into Odoo, go to the Website module, edit a page, and drag the "Embed Code" block from the Dynamic Content section into your layout. Then you paste the JavaScript snippet provided by SeaText. This method does not create a new app entry in the Odoo menu.

Step-by-Step Diagnostic Sequence

Follow these steps in order. Each one rules out a common cause.

1. Step 1: Confirm you are on the correct database. Log out and log back in. Check the database name in the URL. SeaText accounts are tied to a single primary URL. If you are on a staging or development database, the script may not associate traffic correctly.
2. Step 2: Check user permissions. Go to Settings and confirm your user role has "Website / Editor" access. Without this, you cannot see the Website module or edit pages. An administrator can grant this permission.
3. Step 3: Verify the Website module is installed. Look for the Website icon on your Odoo dashboard. If it is missing, install it from the Apps menu. SeaText relies on this module for the embed block.
4. Step 4: Locate the Embed Code block. Open the Website module, click Edit on a page, and scroll to the "Dynamic Content" section. Drag the "Embed Code" block into your layout. If you cannot find it, your Odoo version may differ. Check with the vendor for version-specific guidance.
5. Step 5: Confirm the script is in the page source. Save the page. Then right-click in your browser and select "View Page Source". Search for "seatext". If the script tag appears, it is installed. If not, the block was not saved correctly.
6. Step 6: Check domain restrictions. SeaText accounts are linked to one primary URL. Development domains like localhost are restricted for security. Dynamic development URLs may not work. Use a real, valid domain for testing.

Common Misconceptions

Many users expect a native app icon. That is not how SeaText works. It is a third-party script, not an Odoo module.

Another misconception is that the embed block must be visible on the page. The integration guide instructs you to select "Hide on Desktop" in the Visibility section. This hides the container but the script still runs. Hiding it prevents layout disruption.

Some users think the script will work on any domain. It will not. Each SeaText account is linked to a single primary URL. If you need multiple domains, create a separate account for each one.

What to Do If You Are a Developer

If you are an Odoo developer, you might expect to install SeaText as a custom module. That is not the standard method. The embed approach is designed for non-technical users.

You can still use the embed code. Place it directly in your theme's HTML template if you prefer. This bypasses the Website builder. However, you must ensure the script loads on every page where you want it active.

If you need a different integration method, contact SeaText support. They may offer a custom solution for your setup.

Performance and Security Considerations

Hiding the embed block on desktop is a performance choice. It prevents the code container from affecting your page layout. The script still loads and runs in the background.

Security is also a factor. SeaText states that the AI remains inert until activated. This means the script does not alter your content until you turn it on. The installation process is secure.

Development URLs are restricted for security reasons. SeaText may be unable to reliably associate traffic with your account on dynamic development domains. Always use a real domain for production.

Key Facts About SeaText and Odoo Integration

Limitations and When the Advice Doesn't Apply

This diagnostic assumes you are using Odoo's Website module. If you are on Odoo.sh or on-premise with custom addons, the steps may differ.

If you have multiple websites, remember that each domain requires its own SeaText account. You cannot use one account for two different primary URLs.

If you are testing on localhost, the script may not work. Use a real domain instead.

Frequently Asked Questions

Why can't I find SeaText in the Odoo app store?

SeaText is not listed in the Odoo app store. It is a third-party service that integrates via a script, not through Odoo's module marketplace.

Do I need to install anything in Odoo to use SeaText?

No. You only need to add the embed code to your website. No server-side module installation is required.

Can I use SeaText if I don't have the Website module?

The integration requires the Website module because it relies on the dynamic content block. If you don't have that module, you cannot use the drag-and-drop method. You may need to embed the script directly in your theme's HTML template.

What if I already added the embed code but still don't see any effect?

Check that the script is not blocked by ad blockers or browser extensions. Also ensure the SeaText account is active. Visit your SeaText dashboard to confirm the script is deployed.

Why does the integration guide mention hiding the block on desktop?

Hiding the block on desktop prevents the embed code container from disrupting your page layout. The script still loads and runs in the background.

How do I know if SeaText is working on my Odoo site?

Use your browser's developer tools to check the Network tab for requests to SeaText servers. Alternatively, log into your SeaText account and look for activity data.

Next Steps

If you have confirmed the script is installed but still see no effect, visit the SeaText dashboard to verify your account is active and your domain is correctly linked.

Continue to the SeaText Odoo integration guide for the full step-by-step instructions.

Prerequisites Checklist for Using SeaText in Odoo

Before you start, ensure you have these three essentials:

• Valid SeaText account – Sign up at seatext.com if you don’t have one.
• Active Odoo instance – Either Odoo.com (SaaS) or a self-hosted Odoo 16+ installation with the Website module enabled.
• Internet connection – Needed to sync the SeaText script and data between platforms.

That’s the short list. Below we break down each requirement and add a few extra items you’ll want to have ready.

1. A SeaText Account

You must create a SeaText account before you can get the JavaScript code snippet. The account is free to start. Go to seatext.com and sign up. After login, you’ll find the integration code in your dashboard.

Important: Each SeaText account is linked to one primary URL. If you need to use SeaText on multiple domains (e.g., a development site and a production site), you must create separate accounts for each domain. Sharing one account across domains will not work correctly.

2. An Active Odoo Instance

You need an Odoo instance where you can edit pages. This can be:

• Odoo.com (cloud): A standard Odoo Online subscription. You’ll log in via the web.
• Self-hosted Odoo: Any version 16 or later that supports the Website module. Ensure your server meets Odoo’s system requirements (min 2GB RAM, modern browser).

Both options work the same way for adding SeaText. The key is having access to the “Website” module and the ability to edit a page.

3. Website Module Access

Within Odoo, you must be able to access the Website module from the dashboard. If you don’t see it, ask your Odoo administrator to install the “Website” app. This module is required because SeaText is added via the “Dynamic Content” section of the page editor.

4. Edit Permissions on a Target Page

You need edit rights on at least one Odoo page. Typically, the Odoo administrator or a user with “Website / Editor” role can edit pages. Confirm you can click the “Edit” button on the page you want to modify.

5. A Real, Reachable Domain (Not localhost)

SeaText restricts development URLs like localhost or dynamic development domains for security. The integration script will only work on a valid, public domain. If you’re testing locally, use a staging domain that is accessible over the internet (e.g., staging.yourcompany.com). This is a hard requirement – the script will not activate on localhost.

6. Ability to Add an “Embed Code” Block

Odoo’s page editor includes a “Dynamic Content” section with an “Embed Code” module. You must be able to drag that block onto your page and save the code. No coding skills are needed – just drag, paste, and save. The steps are:

1. Open the page editor (click “Edit”).
2. Scroll through the Blocks panel to “Dynamic Content”.
3. Drag the “Embed Code” module to where you want the SeaText widget to appear.
4. Paste the JavaScript code from your SeaText account.
5. Save the page.

Key Facts

Limitations and When This Advice Doesn’t Apply

Custom Odoo themes: If your Odoo theme removes or overrides the “Dynamic Content” section, you may need to add the SeaText code via Odoo’s custom code editor or a theme setting. This is rare but possible.

Odoo versions before 16: The “Embed Code” block may not exist in older versions. You’ll need to manually edit the template or use a custom module. Check your Odoo version first.

High-traffic sites: SeaText imposes no rate limits stated in the source pack, but ensure your server can handle the extra JavaScript load. The script is lightweight.

Frequently Asked Questions

Do I need coding skills to add SeaText to Odoo?

No. The integration uses Odoo’s drag-and-drop editor. You only need to paste a code snippet into an “Embed Code” block.

Can I use the same SeaText account on my staging and production sites?

No. Each SeaText account is tied to a single primary URL. Create a separate account for each domain.

What if I use Odoo.com (cloud) – are there any extra prerequisites?

No extra steps. Log in, access the Website module, edit a page, and add the Embed Code block. The same process works for Odoo.com and self-hosted instances.

Does SeaText work with Odoo’s mobile editor?

Yes, but you should add the code from a desktop browser for the full editing experience. The mobile editor may not show the “Dynamic Content” block.

How long does the integration take?

About 5 minutes. Create an account, copy the code, drag the block, paste, save, and refresh the page.

What if I see no “Dynamic Content” section in the blocks?

Check that the Website module is installed and you are using a supported Odoo version (16+). If still missing, contact your Odoo administrator.

Is there a free trial?

SeaText offers a free trial. Visit seatext.com to start.

Immediate cause: the embed script never reaches the browser

SeaText does not run inside Odoo as a native module. It loads through a single JavaScript snippet that you paste into an Embed Code block inside the Odoo Website editor. If that block is absent, placed on a page that the dashboard URL does not visit, or stripped by Odoo's sanitizer, the SeaText dashboard — meaning the SeaText AI control panel that should appear on your site — has nothing to initialize.

Direct answer

This usually happens due to a poor internet connection, an invalid API key, or a temporary server issue with SeaText.

Comparison: Odoo Embed Code block vs. Cloudflare edge script

Choose the Odoo Embed Code block if you have Website editor rights and want a no-code setup. Choose the Cloudflare edge script if you need to bypass Odoo's CSP restrictions or lack editor access.

Why this matters

A blank SeaText dashboard is not just a cosmetic issue. It means your site is running without critical AI-driven optimization. Every visitor who lands on your page is not being personalized. Your A/B tests are not running. Your translation engine is silent. Your bot protection is off.

This has real business consequences. Lost personalization means lower conversion rates. Failed A/B tests mean you are guessing what works. Missed translation opportunities mean you are losing international customers. Wasted ad spend on bot traffic means your budget is being drained without return.

Consider a typical ecommerce site with 10,000 monthly visitors. If the dashboard is down, you lose the ability to test headlines, personalize offers, and block bots. That could mean thousands of dollars in lost revenue every month.

For paid traffic, the impact is even sharper. If bots are clicking your Google Ads and the dashboard is not blocking them, you are paying for clicks that will never convert. SeaText's bot protection can recover up to 20% of wasted ad spend. Without it, that money is gone.

The dashboard is the control panel for all these systems. When it is blank, you are flying blind.

Diagnostic sequence

1. Verify the Embed Code block exists. In Odoo Website → Edit → Blocks → Dynamic Content → Embed Code, confirm the block is on the page you are testing.
2. Check the pasted snippet. The code must be the exact snippet from your SeaText AI account (see Step 5 in the integration guide). A truncated or altered snippet will not boot.
3. Inspect browser console. Open DevTools → Console. Look for 404 on the SeaText loader, CSP violations, or JavaScript errors before SeaText initializes.
4. Confirm domain eligibility. SeaText accounts are locked to one primary URL. Localhost, staging subdomains that change, or any domain not registered in the account will be rejected.
5. Review visibility settings. If you enabled Hide on Desktop in the block's Visibility section, the container (and the script inside it) is removed from the DOM on desktop viewports.
6. Validate account status. An expired trial, unpaid invoice, or revoked API key stops the loader from responding.

Practical use case

Let's walk through a real scenario. Sarah is the marketing manager for an ecommerce store built on Odoo. She logs into her SeaText dashboard and sees a blank screen. She follows the diagnostic sequence step by step.

Step 1: Sarah opens her Odoo Website editor. She navigates to the homepage and clicks Edit. She scrolls to the Dynamic Content section and finds the Embed Code block. It is there.

Step 2: She clicks on the block and checks the code. It matches the snippet from her SeaText account. No truncation.

Step 3: She opens her browser DevTools. In the Console, she sees a CSP violation error. The SeaText loader is being blocked by Odoo's Content Security Policy.

Step 4: She checks her domain. She is testing on staging.example.com, but her SeaText account is registered for example.com. That is the problem.

Step 5: She creates a separate SeaText account for the staging domain)Skip. She copies the new snippet and pastes it into the Embed Code block. She saves and refreshes.

Step 6: The dashboard loads. She sees the SeaText control panel with all her agents ready to activate.

This walkthrough shows the importance of checking each step in order. The issue was not the code itself, but the domain mismatch. A quick fix that saved hours of frustration.

How the integration works

SeaText delivers a single JavaScript file that mounts an invisible overlay on your site. The overlay communicates with SeaText's edge network to run A/B tests, personalization, translation, and bot protection. Odoo serves the page; SeaText rewrites copy in the browser. No server-side Odoo module is installed.

Because the integration is client-side only, anything that prevents the script from downloading or executing — CSP headers, ad blockers, Odoo's HTML sanitizer, or a missing block — breaks the dashboard view.

Key facts

Common misconfigurations

• Pasting the snippet into a code field instead of the Embed Code block. Odoo's HTML fields often strip script tags.
• Using the same SeaText account for production and staging. The account's primary URL must match the browser's address bar exactly.
• Enabling "Hide on Desktop" while testing on a laptop. The block disappears, taking the script with it.
• Odoo CSP blocking the SeaText domain. Check Content-Security-Policy headers; add https://cdn.seatext.com (or the current loader domain) to script-src.

Trade-offs and alternatives

The Odoo Embed Code block is the simplest method. It requires no coding and lives directly in your page. But it has limitations. Odoo's CSP may block the script. You need editor access to place the block. And if you change themes or pages, you must re-add the block.

The Cloudflare edge script method is more robust. It bypasses Odoo's CSP entirely. You do not need Odoo editor access. The script runs at the edge, before the page even loads. This means faster execution and fewer conflicts with Odoo's sanitizer.

But the Cloudflare method has trade-offs. You need DNS control and a Cloudflare account. The script is managed outside Odoo, so you must track updates separately. If you do not have Cloudflare, this is not an option.

For most users, the Odoo Embed Code block is the right choice. It is simple, fast, and requires no extra infrastructure. Use the Cloudflare method only if you hit CSP walls or lack editor access.

When the problem is not the embed

If the script loads (network tab shows 200 for the loader) but the SeaText dashboard UI still shows a blank screen, the cause shifts to:

• API key mismatch between the snippet and your account.
• Browser extensions blocking third-party scripts (Privacy Badger, uBlock).
• SeaText platform outage — check status.seatext.com or the SeaText status page.

Limitations of this diagnostic

• Odoo SaaS (odoo.com) may enforce stricter CSP than on-premise; you cannot edit headers there.
• SeaText does not support iframe-embedded Odoo pages (e.g., portal views inside another site).
• This guide covers the Website frontend only; backend Odoo dashboards (e.g., /web) are not supported surfaces.

Next steps and follow-up questions

If the diagnostic sequence does not resolve the issue, take these next steps:

• Contact SeaText support with your browser console logs.
• Verify your API key is valid by logging into your SeaText account and checking the Integration page.
• Check if the SeaText status page reports any ongoing incidents.
• Try loading the dashboard in a different browser or incognito mode to rule out extensions.

Common follow-up questions include:

• How do I check if my API key is valid? Log into your SeaText dashboard, go to Integration, and confirm the key matches the one in your snippet.
• What should I do if the loader returns 200 but the dashboard is still blank? Check for JavaScript errors in the console. Look for API key mismatches or browser extension interference.
• Can I use one SeaText account for multiple domains? No. Each domain needs its own account.
• Does SeaText work on Odoo's backend? No. Only the Website frontend is supported.

Terminology

• Embed Code block — Odoo Website block type that accepts raw HTML/JS.
• Primary URL — The single domain a SeaText account is licensed for.
• Loader — The small JS file that bootstraps the full SeaText engine.
• CSP — Content Security Policy, an HTTP header that restricts script sources.

FAQ

Why does the dashboard work in incognito but not my regular browser?

An extension is likely blocking the SeaText loader. Disable extensions one by one.

Can I use one SeaText account for my Odoo staging and production sites?

No. Each domain needs its own account. Create a second account for staging and use its snippet.

Does SeaText work on Odoo's backend (/web) or only the Website frontend?

Only the Website frontend. The backend uses a different framework and CSP that blocks third-party scripts.

What if I cannot add the Embed Code block because I lack Website editor rights?

Ask an Odoo admin to place the block, or use the Cloudflare edge script method (requires DNS control) instead of the Odoo block.

How do I know the snippet is the current version?

Log into your SeaText dashboard, go to Integration → Odoo, and copy the snippet shown there. Old snippets may reference deprecated endpoints.

Will "Hide on Mobile" also break the dashboard?

Yes. Any visibility rule that removes the block from the current viewport removes the script.

Brand bridge

For more detailed integration guides and troubleshooting resources, visit the SeaText website.

Call to action

Learn more — Visit the SeaText Odoo integration page for the latest setup instructions and support.

To share SeaText access with other users in Odoo, open Settings → Users → Users, choose the person, and assign the SeaText user group. This grants the permission needed to view and edit SeaText settings inside Odoo. After saving, have that user log out and back in so the new rights load.

Why sharing SeaText access correctly matters

Proper access control protects your SeaText account and keeps workflows smooth. SeaText is an external AI marketing service that connects to Odoo via a JavaScript snippet. The snippet is placed in an Embed Code block inside Odoo's Website module (source: S1). If the wrong person can edit that snippet, they could break the integration or inject malicious code. If too many people have the dashboard login, you risk credential leaks or unauthorized changes to AI agents, translations, or ad‑defense settings.

In multi‑domain setups, each SeaText account is linked to a single primary URL (source: S1). Sharing one account across domains can cause tracking failures or billing issues. Correct sharing ensures each domain uses its own account and each user has only the permissions they need.

Workflow efficiency also improves. A marketing manager who only needs to adjust SeaText settings should not require full Odoo administrator rights. A developer who maintains the embed code does not need the SeaText dashboard. Matching the sharing method to the role reduces confusion and support tickets.

How SeaText access works in Odoo

SeaText does not ship an official Odoo module in the source documentation (source: S1). The integration guide describes a manual code placement: drag an Embed Code block into a page, paste the snippet, save, and optionally hide on desktop. However, many Odoo integrations create a custom module that registers a user group (e.g., group_seatext_user) and access rights on a model like seatext.config.

If such a module exists, Odoo's standard access‑rights engine applies:

• User groups are assigned on the user record under the Access Rights tab.
• Access rights (read, write, create, delete) are defined per model per group.
• Company‑specific permissions matter in multi‑company databases. A group may grant access only for the user's active company. Switch companies via the user menu to verify.

If no module is installed, there is no SeaText group. Access is then controlled by Odoo's website editor permissions: users with edit rights on the page can modify the Embed Code block. This is coarser but works for simple setups.

Two versions of sharing SeaText access — detailed comparison

Many Odoo admin questions on this topic come from one misunderstanding: thinking SeaText access is a single button inside Odoo. It is not, unless you have installed a SeaText Odoo module that creates a group.

Version A: Odoo user group (module installed)

How it works: The module adds a group (often named "SeaText / User" or similar). Assign it to any user. They gain menu access to SeaText settings, can view or edit configuration, and possibly trigger sync actions.

Trade‑offs: Clean separation of duties. No need to share external passwords. Limited to Odoo‑side settings; dashboard features (AI agents, translation jobs, bot reports) remain in the external SeaText portal.

When to use: You have a SeaText module in your Apps list, and you want Odoo‑native permission management.

Version B: Website builder permissions (code snippet only)

How it works: SeaText was added by pasting the JavaScript snippet into an Embed Code block. No module, no group. To let someone update the snippet, give them edit access to that website page (or the whole website).

Trade‑offs: Simple, no extra module. But the user can edit any block on that page, not just the SeaText snippet. They cannot change SeaText dashboard settings.

When to use: You followed the manual embed steps from the integration guide (source: S1) and have no SeaText module.

Version C: SeaText dashboard login (external account)

How it works: Share the SeaText account email/password or invite the user if the plan supports team seats. The source guide does not document a multi‑user dashboard role system (source: S1). Verify current options with SeaText support or the pricing page.

Trade‑offs: Gives full access to all SeaText features: AI agents, translation, CRO testing, bot defense, etc. Higher security risk if credentials leak. Not tied to Odoo user records.

When to use: A marketer or agency needs to configure AI agents, run translation jobs, or view conversion analytics.

Conditional recommendation: Start with Version A if a module exists. Fall back to Version B for snippet‑only setups. Use Version C only for users who truly need dashboard features, and prefer a plan with team seats over credential sharing.

Practical use cases and scenarios

Step‑by‑step: assign SeaText permissions to a user

1. Log in to Odoo as an administrator.
2. Go to Settings → Users → Users.
3. Click the user you want to share access with.
4. Open the Access Rights tab.
5. In the Groups field, type "SeaText".
6. Select the SeaText group. If there are multiple groups, pick the one that matches the access level the user needs.
7. Click Save.
8. Ask the user to log out and log back in.

If this is a first‑time setup, complete the SeaText installation first. The Odoo integration page shows you how to place the code snippet in a "Dynamic Content" block on your website (source: S1).

Verify the user can actually see SeaText

After the user logs back in, have them look for the SeaText menu or settings item. They should be able to open it without an "Access Denied" error.

If the menu is still missing, check these in order:

1. Is the SeaText group saved on the user's record?
2. Is the correct company selected? Groups can apply per company.
3. Has the browser cache been cleared, or have they tried a private window?
4. Does the SeaText module actually exist in this database? If not, you'll need to install it or share the embed code instead.

Common mistakes when sharing SeaText access

• Assigning the group but not saving. Odoo does not save until you click Save. Always confirm the group appears in the user's Groups list after save.
• Forgetting the company. Multi‑company databases may not show the group for the user's active company. Switch the user's active company or set the group for all companies.
• Sharing one account across multiple domains. SeaText links each account to one primary URL (source: S1). Create a separate SeaText account for each domain.
• Trying to test on localhost. SeaText restricts development URLs for security reasons (source: S1). Use a real, valid domain for test and production.
• Looking for a SeaText group when the code was embedded manually. No module means no group. Use website editor permissions or share the dashboard login instead.
• Giving full administrator rights instead of the SeaText group. This over‑grants access. Assign only the SeaText group.
• Not verifying after assignment. Always have the user log out and back in, then test the SeaText menu.

Limitations and when this advice does not apply

The source SeaText Odoo integration guide covers code placement, not user management (source: S1). If SeaText has evolved to include a full Odoo module with predefined groups, your exact group name may differ. Check your Apps list.

This advice also does not apply if you only need to share the SeaText dashboard login with a contractor. That is a credential hand‑off, not an Odoo permission.

If you run several websites, do not try to force one SeaText account across all of them. The integration guide says to create separate accounts (source: S1). For your primary domain, you still need to paste the correct code snippet from the account that is linked to that domain.

This guide assumes a standard Odoo Community or Enterprise installation. Odoo.sh, Odoo Online, or heavily customized instances may have different menu paths or group names.

If your SeaText plan includes team seats or role‑based access in the dashboard, the external sharing method (Version C) may be more structured than credential sharing. Check the current SeaText pricing page for details.

Frequently asked questions

Can I give someone access to SeaText without making them an Odoo administrator?

Yes. Assign only the SeaText group. That gives them the SeaText‑related rights, not full administrator rights.

Why don't I see a SeaText group in Odoo's Access Rights list?

If you embedded SeaText as a code snippet rather than installing a SeaText Odoo module, no group is created. Use website editor permissions or share the account login instead.

Can two people use the same SeaText account?

Sharing the login is possible technically, but each accou

Disconnecting SeaText from Odoo means removing the JavaScript code snippet that links your Odoo website to the SeaText AI platform. Once that snippet is removed, the integration stops instantly: SeaText agents no longer rewrite copy, run A/B tests, translate pages, track reading behavior, or forward conversion data to ad platforms. Your existing content in Odoo reverts to its original state, and any SeaText-generated variants or translations stop appearing. Data already collected in SeaText (test results, reading telemetry, translation memories) stays in your SeaText account until you delete it. Data in Odoo (products, pages, orders) is unaffected.

How the SeaText–Odoo Integration Works

SeaText connects to Odoo through a single JavaScript snippet. According to the official integration guide, you copy the snippet from your SeaText dashboard, open the Odoo Website editor, drag an Embed Code block into the page, paste the snippet, and save. The script loads asynchronously, scans the DOM, and begins applying the AI agents you have activated (copy testing, translation, personalization, bot protection, etc.). Because the integration is client-side only, there is no database link, API token, or webhook between the two systems.

What Stops Immediately After Disconnection

• Copy optimization: AI-generated headline, CTA, and product-description variants stop serving. Visitors see the original Odoo content.
• Translation: Automatic 125-language translation ceases. Pages display in the base language only.
• Reading telemetry: Millisecond-level scroll, dwell, and friction tracking ends. No new behavioral data flows to SeaText.
• Conversion Relay (CAPI): Real-time purchase forwarding to Meta and Google CAPI halts.
• Bot protection: Bot-click refunds, VPN detection, and form-spam blocking stop.
• Personalization: Real-time copy adaptation based on visitor context (referrer, keyword, geography) ends.

What Persists in Each Platform

Step-by-Step: How to Disconnect

1. Log in to Odoo and open the Website module.
2. Navigate to the page(s) where you placed the Embed Code block (usually the homepage or a global footer block).
3. Click Edit, select the Embed Code block, and choose Delete or simply clear the code snippet and save.
4. Optional: In SeaText, go to Settings → Domains and remove the Odoo domain to stop any background polling.
5. Clear your browser cache and revisit the site to confirm the original content loads without SeaText modifications.

Reconnecting Later

Reconnection is the same as the initial setup: copy the current snippet from SeaText (it may have updated agent IDs), paste it into an Embed Code block in Odoo, and save. Historical data in SeaText is not restored automatically; new tests start fresh. If you kept the same domain in SeaText, translation memories and bot-block lists persist and resume working immediately.

Limitations and Edge Cases

• Multi-domain accounts: Each SeaText account is tied to one primary URL. If you used separate accounts for dev and production, disconnect one without affecting the other.
• Development URLs: Localhost and dynamic dev domains are restricted for security. Disconnecting a dev domain simply means removing the snippet; you cannot re-add it until the domain is a valid, public URL.
• Cached pages: CDN or browser caches may serve SeaText-modified HTML for a short TTL after snippet removal. Purge caches if you need instant rollback.
• Embedded scripts: If you placed the snippet in a global layout block (header/footer), it affects all pages. Removing it from one page may not stop it site-wide.

Key Facts

Frequently Asked Questions

Will my Odoo content be deleted or altered?

No. SeaText only overlays changes via JavaScript. The original Odoo records stay exactly as you left them.

Do I lose A/B test history?

Test results remain in your SeaText dashboard. They are not pushed back into Odoo, so they won't reappear if you reconnect.

Can I pause instead of fully disconnecting?

Yes. In SeaText, toggle individual agents off (e.g., disable Translation but keep Bot Protection). The snippet stays in Odoo but runs a reduced payload.

What happens to translated URLs (/fr/, /de/, etc.)?

SeaText creates virtual translated pages via JavaScript. Without the snippet, those URLs return 404 or redirect to the base language, depending on your Odoo routing.

Does disconnecting affect my Google Ads Quality Score?

Indirectly. If SeaText was rewriting landing pages to match keywords, reverting to generic pages may lower relevance and increase CPC. Monitor Quality Score after disconnection.

How do I verify the snippet is fully removed?

Open browser DevTools → Network tab → filter for "seatext" or your account ID. No requests should fire. Also check the page source for the snippet string.

Can I keep SeaText on a staging site while disconnecting production?

Yes, if they are separate SeaText accounts (each tied to its own domain). Disconnect production by removing its snippet; staging continues unaffected.

How the SeaText-Odoo Integration Works

SeaText installs on your Odoo website through a JavaScript code snippet. You copy the code from your SeaText AI account and paste it into the Odoo Website editor using the Embed Code module.

First, log in to your Odoo account and access the Website module. Navigate to the page you want to edit and click the Edit button to open the editing panel.

In the editing panel, scroll to the Dynamic Content section and locate the Embed Code module. Drag it into the desired location on your website editor.

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

The installation process is secure, and the AI remains inert until activated. This means the script does not modify or interfere with your website content before you choose to enable it.

Security Measures and Permission Model

SeaText adheres to Odoo's permission model. Only users with the right access rights in Odoo can view or edit the embedded configuration blocks.

SeaText uses secure API keys to authenticate your account. These keys are tied to your specific SeaText AI account and are not stored in plain text within your website's public-facing code.

The code snippet itself is a client-side script. It runs in the visitor's browser and communicates with SeaText's servers over encrypted connections. Your website's backend and database remain untouched by the integration.

Before you can install the script, you need a SeaText AI account. If you don't have an account yet, you can create one on the SeaText website. This account acts as the central control point for all configuration and activation.

Account and Domain Restrictions

SeaText enforces strict domain-level account rules. Each SeaText AI account is linked to a single primary URL.

If you need to use SeaText AI on multiple domains, such as a development domain and a production domain, you must create separate accounts for each domain.

Development URLs, such as localhost, are restricted for security reasons. This prevents unauthorized or accidental activation on non-production environments.

Dynamic development domains may not function properly, as SeaText AI might be unable to reliably associate traffic with your account. Always use a valid, real domain for proper operation.

To use SeaText AI on several websites, create one account for each website. This one-to-one mapping ensures clear accountability and prevents cross-domain data leakage.

What Happens If You Ignore Security Considerations

If you skip the domain restriction rules, your integration may fail silently. SeaText AI might not associate traffic correctly with your account, leading to missing data or inactive features.

Using a shared account across multiple domains can blur ownership and make it difficult to track which site generated specific conversions or interactions.

Ignoring Odoo's permission model can expose your configuration blocks to unauthorized users. Anyone with access to the Odoo editor could modify or remove the SeaText embed code.

Always restrict editor access to trusted team members. Regularly review your Odoo user roles to ensure only authorized personnel can alter the website's embedded content.

Limitations and Exceptions

The SeaText-Odoo integration has clear boundaries. It does not provide server-side access to your Odoo database. The JavaScript snippet operates entirely in the browser.

Local development environments are not supported. You cannot test SeaText on localhost or similar development URLs due to security restrictions.

Dynamic or changing development domains may cause unreliable behavior. SeaText AI needs a stable, verifiable domain to function correctly.

The integration depends on your Odoo website being publicly accessible. If your Odoo instance sits behind a firewall or VPN without public access, SeaText AI cannot properly associate traffic with your account.

Each domain requires its own SeaText AI account. There is no multi-domain license or shared account option. This can increase cost if you manage many properties.

FAQ

Does SeaText store my Odoo credentials?

No. SeaText does not store your Odoo login credentials. You only need to paste a JavaScript code snippet into the Odoo editor. The integration uses API keys tied to your SeaText account, not your Odoo login.

Can any team member see the SeaText configuration?

Only users with access to the Odoo Website editor can see or modify the embedded code block. SeaText's permission model relies on Odoo's built-in access controls, so restrict editor rights to trusted staff.

What if I run a staging site alongside my production Odoo site?

You must create a separate SeaText AI account for each domain. Staging and development domains like localhost are restricted for security reasons. Use a valid, real domain for each account.

Is the SeaText code snippet encrypted?

The script communicates with SeaText's servers over encrypted connections. The code itself is a standard client-side JavaScript snippet. It does not contain sensitive credentials in plain text within the page source.

How do I deactivate SeaText on my Odoo site?

You can remove the embed code block from the Odoo editor at any time. Alternatively, you can use the Visibility section to hide the block. Simply delete or hide the module and save your changes to deactivate the integration.

Does SeaText work with Odoo Online or only on-premise?

The integration works through the Odoo Website editor, which is available in both Odoo Online and on-premise deployments. The process is the same: access the editor, add the Embed Code module, and paste the SeaText script.

Why do I need to grant permissions to SeaText in Odoo? Because SeaText needs a narrow set of read and write rights to install its JavaScript integration, read the pages it works on, and save changes back. Those rights are the guardrail that lets SeaText do its job without touching unrelated parts of your database.

If you do not grant them, the integration cannot install, the code will not run, and the AI features you signed up for stay inert. Granting permission is not an open door to all your data. It is a scoped handshake between SeaText and the specific Odoo modules it uses.

What “permissions” mean in Odoo

Odoo access rights are rules that decide who, or which application, can view or change data. According to Odoo’s documentation, access rights “determine the content and applications users can access and edit.” These rights are set for individual users or for groups. When an integration like SeaText asks for permissions, Odoo treats it like a user with a specific role.

That role is limited to the actions the integration needs. It is the same system a payment gateway uses to read orders, or a shipping app uses to update deliveries. Nothing about the permission request is special or risky by itself.

What SeaText actually needs

SeaText installs on Odoo through the Website module. The integration guide explains how to drag an “Embed Code” block onto a page, paste the JavaScript snippet SeaText provides, and save. That requires write access to the page code.

Once the snippet is active, SeaText may ask for read access to page content so its AI agents can analyze what visitors read, test copy variants, and generate SEO content. Depending on the features you enable, it may also write new content back to the page. The permissions cover those actions, and nothing more.

Why Odoo asks in the first place

Odoo’s security model is built on least privilege. Odoo warns that “limiting permissions to only those who need them ensures that users do not modify or delete anything they should not.” If SeaText could write to everything, a bug or a compromised script could damage unrelated modules.

The permission prompt is the moment Odoo asks you to confirm exactly what this integration may touch. It is a safety check, not a hurdle.

What happens if you ignore the request

The most common result is a failed installation. The embed block will not accept the code, or the code saves but never runs. If you later revoke the permissions, existing SeaText features stop working: the script cannot update, the AI cannot read pages, and content agents cannot publish.

No data is deleted, but you lose the conversion, translation, and SEO functions you installed SeaText for. The trade-off is a few minutes of setup time now versus a broken feature supply later.

The trade-off: convenience versus control

You want the integration to work fast, but you also want your database safe. The solution is to grant the minimum permissions needed.

• Give SeaText access only to the Website module and the pages you want it to edit.
• Do not give it administrator rights.
• If you are unsure, start with read-only access, verify the behavior, then add write access for the specific content you want it to change.

Key facts about SeaText’s Odoo integration

Expert perspective: scope permissions like a security review

A security reviewer will tell you to treat every permission request as a risk. Start by asking, “What does this module need to do, and what can it do without full access?”

For SeaText, the answer is usually page-level read and write. Create a dedicated Odoo group for the integration, assign only the required model access, and audit the group periodically. If you stop using SeaText, remove the group or the embed code. This keeps the integration useful without giving it a permanent key to your entire system.

Limitations: when this advice does not apply

If you are using the simple JavaScript embed, you may not need database-level permissions at all. You only need permission to edit the Odoo page and paste the code.

Full database access is only necessary if you are building a custom API connection between SeaText and Odoo, for example to sync product catalogs or order data. In that case, use a dedicated API key with the specific scopes and never reuse your admin credentials. And if you are on localhost, the integration will not work because SeaText restricts development URLs for security.

FAQ

Can I revoke SeaText permissions later?

Yes. In Odoo, remove the user or group permissions you granted, or delete the embed code from the page. The integration will stop after that.

Will SeaText see my customer data?

Not by default. The core integration works with your website pages, not your sales records. If you connect a custom data source, review exactly which fields you expose.

How do I know what permissions were granted?

Check Users & Companies, select the SeaText user, and inspect the assigned groups. Odoo also keeps logs of permission changes.

Do I need permissions for each Odoo website?

Yes. Each SEATEXT AI account is linked to a single primary URL, so you need one account per website and you should grant permissions per website.

What does granting permissions cost?

The permissions themselves are free. The cost is the time you spend reviewing and maintaining them. SeaText’s pricing is separate and depends on the plan you choose.

How to Enable AI Features in SeaText via Odoo: Complete Setup Guide

To enable AI features in SeaText via Odoo, install the SeaText JavaScript snippet using Odoo's Embed Code block, then toggle on individual AI agents in the SeaText dashboard. The script remains inert until you activate each feature.

What you need before starting

You need an active SeaText account and a live domain — localhost and dynamic development URLs are restricted for security. Each SeaText account links to a single primary URL, so if you run multiple domains (for example, a staging and a production site), create a separate account for each one. You also need administrator access to your Odoo instance with the Website module installed (S1).

Step 1: Copy the SeaText JavaScript snippet

Log in to your SeaText dashboard. The integration code appears in the setup section labeled SEATEXTCODEINTEGRATION. Copy the entire JavaScript snippet; you will paste it into Odoo in the next step (S1).

Step 2: Open the target page in Odoo Website editor

In Odoo, go to the Website module from the main dashboard. Navigate to the page where you want SeaText to load — typically your homepage or a global layout page — and click Edit to open the visual editor (S1).

Step 3: Add the Embed Code block

In the editing panel, scroll the Blocks sidebar down to the Dynamic Content section. Drag the Embed Code module into the desired location on the page. This block lets you inject raw HTML or JavaScript without modifying theme files (S1).

Step 4: Paste the snippet and save

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 SeaText JavaScript snippet into the designated area, then click Save to apply the changes (S1).

Step 5: Hide the block on desktop (optional but recommended)

To keep the block invisible to visitors, select the Hide on Desktop option in the Visibility section of the block settings. Click Save again to finalize. The script will still execute while remaining hidden from view (S1).

Step 6: Activate AI agents in the SeaText dashboard

Return to your SeaText account. The script is now live but inert. In the dashboard you will see a catalog of 20 autonomous AI agents grouped into Conversion, Traffic & Ad Defense, Growth & AI Search, and Sales & Edge Infra. Toggle the switch for each agent you want to enable — for example, AI CRO Reading Analysis, AI Copy A/B Testing, Website Translation (125 Langs), ChatGPT Brand Visibility, or Bot Protection & Refund Agent. Each agent activates independently, so you can start with one and add others later (S2, S3).

Step 7: Verify the installation

Visit your live site and open the browser developer console (F12 → Console). You should see a SeaText initialization log confirming the script loaded. In the SeaText dashboard, the Status indicator for your domain will switch from Pending to Active. If you enabled the AI CRO Reading Analysis agent, the dashboard will begin showing reading telemetry within a few minutes of real traffic (S1).

How the activation process works

The activation follows a two-stage pipeline. First, you install the JavaScript snippet in Odoo. This script is deliberately inert — it loads but performs no AI actions until you explicitly enable agents in the SeaText dashboard. This design gives you granular control and prevents unwanted changes to your site content (S1). Second, you toggle agents on in the dashboard. Each toggle corresponds to a specific autonomous agent. The agent then begins processing visitor data and applying optimizations in real time. The separation ensures that installation is safe and reversible; you can disable any agent without removing the script (S2).

Why enabling AI features matters for Odoo sites

Odoo websites often serve as the primary touchpoint for leads, ecommerce sales, and brand communication. Enabling SeaText AI agents adds autonomous optimization layers that work without developer intervention. For example, the AI CRO Reading Analysis agent measures millisecond-level reading behavior to identify copy friction points, then generates and deploys improved variants automatically (S4). The Website Translation agent unlocks 125 languages with zero code, expanding global reach instantly (S2). Bot Protection agents recover wasted ad spend by detecting and refunding fraudulent clicks (S2). These capabilities turn a static Odoo site into a self-optimizing conversion engine.

Trade-offs of enabling multiple agents

Each agent consumes a small amount of browser resources and adds processing overhead. Enabling many agents simultaneously can increase script execution time, though SeaText loads asynchronously to minimize impact (S5). Some agents require additional configuration — for instance, Conversion Relay (CAPI) needs Meta or Google pixel credentials (S1). You also need to monitor agent interactions; overlapping agents (e.g., AI Copy A/B Testing and AI Personalization) may test similar elements. Start with one high-impact agent, measure results, then add complementary agents. The dashboard provides per-agent metrics so you can evaluate ROI before expanding (S2).

Troubleshooting after activation

• Script not loading: Verify the Embed Code block is placed on a page that loads globally (e.g., homepage or layout). Check that the snippet was pasted exactly, without extra whitespace.
• Domain status stays Pending: Ensure you used a valid, live domain. Development URLs like localhost are blocked (S1). Refresh the page and wait a few minutes for the dashboard to update.
• Agent shows no data: Confirm the agent toggle is on. Some agents need traffic to generate metrics; low-traffic sites may take longer. Check the agent's configuration panel for required settings (e.g., exclusion rules, intensity levels).
• Console errors: Look for Content Security Policy (CSP) violations. Odoo may block inline scripts; the Embed Code block usually bypasses this, but custom CSP rules could interfere.
• Multiple domains using one account: Each domain requires its own SeaText account. Create a new account for each domain and repeat the installation steps (S1).

Available AI agents you can enable

SeaText groups its 20 agents into four categories. You do not need to enable all of them at once.

• Conversion agents: AI CRO Reading Analysis, AI Split URL Testing, Google Ads Landing Page AI, AI Copy A/B Testing, Ecommerce Product Copy, AI Personalization, Scroll Slowdown.
• Traffic & Ad Defense agents: Bot Protection & Refund, Conversion Relay (CAPI), Intent Amplifier, Shielded Buyers & Ad Firewall, Detect VPN Ad Click Fraud.
• Growth & AI Search agents: Website Translation (125 Langs), ChatGPT Brand Visibility, AI SEO Content Factory, Local AI SEO, Authority Link Discovery.
• Sales & Edge Infra agents: Enterprise Sales Webchat, ABM Account Personalization, Visitor Source Rewrites, WebMCP Server for AI Agents, Scroll Slowdown & Attention.

Each agent has its own configuration panel where you set targets, exclusions, and intensity levels (S2, S3).

Common setup mistakes

• Pasting the snippet into a text block instead of Embed Code. The script will render as visible text and not execute.
• Using a development domain like localhost. SeaText blocks these for security; use a real domain or a public staging URL.
• Forgetting to toggle agents on. The script loads but no AI features run until you enable them in the dashboard.
• Installing the same account snippet on multiple domains. Each domain needs its own SeaText account.

Limitations and when this approach does not apply

• Odoo's Embed Code block is the supported no-code method. If your theme uses a custom head injection field, you can paste the snippet there instead, but SeaText documentation only covers the Embed Code workflow.
• The script remains inert until you activate agents. No automatic AI behavior occurs on install.
• Dynamic development domains (e.g., preview URLs that change per deploy) may not function reliably because SeaText associates traffic with a fixed primary URL.
• Some agents (e.g., Conversion Relay CAPI) require additional pixel or API credentials from Meta/Google; those are configured inside the agent settings, not during Odoo installation.

Now that you know how to enable SeaText AI features in Odoo, you can start with one agent and expand as you see results. For a full list of agents and pricing, visit the SeaText website.

Frequently asked questions

Do I need coding skills to enable SeaText AI features in Odoo?

No. The Embed Code block handles the JavaScript injection. All agent configuration happens in the SeaText dashboard via toggles and forms.

Can I test SeaText on a staging site before pushing to production?

Yes, but you must create a separate SeaText account for the staging domain. Each account is tied to one primary URL.

Which AI agent should I enable first?

Most teams start with AI CRO Reading Analysis because it surfaces reading friction points without requiring traffic splits. From there, AI Copy A/B Testing or Google Ads Landing Page AI are common next steps depending on whether you run paid search.

Does the SeaText script slow down my Odoo site?

The snippet loads asynchronously and is designed for zero-flicker operation. SeaText also offers a Cloudflare edge deployment option for enterprise customers who want the script served from the edge (S5).

How do I know the AI features are actually working?

Check the SeaText dashboard: the domain status shows Active, and each enabled agent displays live metrics (reading telemetry, variant performance, translation coverage, bot refunds, etc.).

Can I disable an agent without removing the script?

Yes. Toggle the agent off in the dashboard. The script stays on the page but that agent stops processing.

What if I need help configuring a specific agent?

SeaText provides 400+ playbooks in the Resources hub and a sales engineering team for custom roadmaps. The dashboard also links to agent-specific documentation (S7).

Odoo configuration manages your ERP data, user access, and website content through its Website module. SeaText configuration handles your SEO strategy, AI-driven content generation, conversion optimization, and analytics settings via a JavaScript snippet installed in Odoo. They operate at different layers: Odoo runs your business operations; SeaText optimizes how visitors experience and convert on your Odoo-powered site.

What Odoo Configuration Actually Manages

Odoo is an ERP suite. Its configuration covers the modules you activate (Sales, Inventory, Accounting, Website, eCommerce), the users who can access each module, and the data structure inside them. When you open the Website module, you edit pages using a drag-and-drop builder. You add blocks like text, images, products, and — crucially for this integration — an Embed Code block. That block is where SeaText lives. Odoo also controls product data, pricing, tax rules, payment acquirers, and the checkout flow. None of those are touched by SeaText.

What SeaText Configuration Actually Manages

SeaText is a layer of 20 autonomous AI agents that sit on top of any website. Its configuration lives in the SeaText dashboard, not in Odoo. You choose which agents to activate: AI CRO Reading Analysis, AI Split URL Testing, Google Ads Landing Page AI, Website Translation (125 languages), Local AI SEO, AI SEO Content Factory, Conversion Relay (CAPI), Bot Protection & Refund Agent, and more. You set target languages, excluded URL patterns, conversion goals, and ad-account connections. The only thing you do inside Odoo is paste the JavaScript snippet that loads those agents.

How the Integration Works in Practice

You log into Odoo, open the Website module, edit the page where you want SeaText active (often the homepage or a landing page), drag an Embed Code block from the Dynamic Content section into the page, click Edit on that block, paste the SeaText JavaScript snippet, save, then optionally hide the block on desktop via the Visibility settings. That's the entire Odoo-side configuration. After that, SeaText's dashboard controls everything else. The snippet stays inert until you activate agents in SeaText.

Why the Distinction Matters for Your Team

If you treat SeaText as just another Odoo module, you'll look for settings inside Odoo that don't exist there. Conversely, if you expect Odoo to handle AI-driven copy testing or multilingual SEO, you'll be waiting for features that live in SeaText. Clear ownership prevents gaps: your Odoo admin manages the snippet placement and page structure; your growth/marketing team manages SeaText agents, conversion goals, and language targeting. When something breaks — say, a translation doesn't appear — you know to check SeaText's language settings, not Odoo's translation module.

Common Mistakes When Configuring Both

• Placing the SeaText snippet on only one page instead of globally (use a layout-level block or theme header for site-wide coverage).
• Forgetting to create separate SeaText accounts for development and production domains — each primary URL needs its own account.
• Trying to use localhost or dynamic dev domains; SeaText restricts these for security.
• Assuming Odoo's built-in translation covers what SeaText's 125-language AI translation does — they serve different purposes (static UI vs. dynamic marketing content).
• Not connecting ad accounts (Meta, Google) in SeaText's Conversion Relay, so bot-click refunds and CAPI forwarding don't work.

Decision Framework: Which Settings Go Where

Use this quick checklist when a new requirement arrives:

1. Does it change product data, pricing, checkout, user roles, or backend workflows? → Odoo configuration.
2. Does it change how visitors read, convert, or are tracked on the front end? → SeaText configuration.
3. Does it involve translating marketing copy into new languages automatically? → SeaText.
4. Does it involve translating static UI labels, menu items, or system messages? → Odoo.
5. Does it involve recovering ad spend from bot clicks or forwarding purchase events to Meta/Google CAPI? → SeaText.
6. Does it involve setting up payment providers, tax rules, or shipping methods? → Odoo.

Limitations and When This Advice Doesn't Apply

This comparison assumes you're using Odoo's Website/eCommerce module as your public-facing site. If you run a headless frontend (React, Vue, Next.js) that pulls data from Odoo via API, the integration changes: you'd paste the SeaText snippet in your frontend codebase, not in Odoo's Embed Code block. The domain-per-account rule still applies. Also, SeaText's AI agents only optimize HTML content they can see; content rendered client-side after the initial load may need additional configuration. Check with the vendor if your stack uses heavy client-side rendering.

FAQ

Can I manage SeaText agents from inside Odoo?

No. SeaText's dashboard is a separate web app. Odoo only hosts the JavaScript loader.

Do I need a separate SeaText account for each Odoo database?

Yes, if each database serves a different primary domain. One SeaText account = one primary URL.

Will SeaText slow down my Odoo site?

The snippet loads asynchronously via Cloudflare edge (60-second setup, zero redirect latency). It's designed for minimal impact.

Can I use Odoo's translation and SeaText's translation together?

Yes. Odoo translates static UI; SeaText translates and optimizes marketing content, product descriptions, and SEO pages in 125 languages.

What happens if I deactivate the Embed Code block in Odoo?

SeaText stops loading on that page. Agents won't run. Reactivate the block to restore.

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

Each website domain needs its own SeaText account and snippet. Configure each in its respective Odoo website editor.

Where do I get the JavaScript snippet?

In your SeaText account dashboard, under the integration or installation section. Copy it once per domain.

Why SeaText Is Not a Native Odoo Module

SeaText does not appear in the Odoo app launcher, dashboard widgets, or app list. It is not installed from the Odoo App Store. Instead, SeaText runs as a third‑party JavaScript service that you add to any Odoo website page by pasting a code snippet into an Embed Code block. This approach keeps SeaText independent of Odoo version upgrades and lets it work on Odoo Online, Odoo.sh, and on‑premise instances alike.

The integration method is documented on the SeaText Odoo integration page (S1). You log in to Odoo, open the Website module, edit a page, drag the Embed Code block from the Dynamic Content section, paste the snippet, and save. There is no SeaText icon to click on the home screen.

How the JavaScript Integration Works

SeaText delivers a single Cloudflare edge script that loads asynchronously. The script remains inert until you activate it in your SeaText dashboard (S6). Once active, it injects AI agents that analyze visitor behavior, rewrite copy in real time, translate content into 125 languages, protect ad spend from bots, and feed conversion data to Meta and Google CAPI (S2). Because the code runs in the browser, it does not require backend changes, database migrations, or Odoo module updates.

The snippet is unique to your SeaText account and tied to one primary domain (S1). If you need SeaText on a development domain and a production domain, you must create separate accounts (S1). Localhost and dynamic development URLs are restricted for security reasons (S1).

Step‑by‑Step: Embedding SeaText in Odoo

1. Create a SeaText account. Visit the SeaText site, sign up, and copy the JavaScript snippet provided for your domain (S1).
2. Log in to Odoo. Open your Odoo instance and navigate to the Website module from the main menu.
3. Open the page you want to edit. Click the Edit button to enter the website builder.
4. Add the Embed Code block. In the left Blocks panel, scroll to the Dynamic Content section. Drag the Embed Code block onto the page where you want the script to load (typically in the footer or a global layout area).
5. Paste the snippet. Click the Edit button on the Embed Code block (right panel). In the pop‑up, paste the SeaText JavaScript code and click Save (S1).
6. Hide on desktop if desired. In the block’s Visibility settings, enable Hide on Desktop to keep the block invisible to visitors while the script still loads (S1). Click Save again.
7. Publish the page. Exit the editor and publish the changes. The script is now live on that page.

Verifying the Integration

After publishing, visit the page in a private browser window. Open the browser developer tools (F12) and check the Network tab for a request to the SeaText Cloudflare edge domain. You should see the script load with a 200 status. In the SeaText dashboard, the domain status should change from Pending to Active once the first visitor triggers the script (S6). If the script does not load, confirm the Embed Code block is not inside a container that strips scripts and that Odoo’s Content Security Policy allows the SeaText domain.

Common Setup Issues and Fixes

• Script not loading: Ensure the Embed Code block is placed in a global layout (footer or header) so it appears on every page. Verify the snippet matches exactly what SeaText provided—no extra spaces or line breaks.
• Block visible on desktop: Enable Hide on Desktop in the block’s Visibility settings (S1).
• Multiple domains: Each domain needs its own SeaText account and snippet (S1). Do not reuse a snippet across domains.
• Development environment blocked: Localhost and dynamic dev URLs are restricted (S1). Use a real domain (e.g., dev.example.com) with a valid SSL certificate.
• Content Security Policy errors: Add the SeaText script domain to Odoo’s CSP allowed sources if your instance enforces a strict policy.

Security and Account Requirements

SeaText is SOC 2 Type II certified and GDPR/CCPA compliant (S6). The AI agents remain inert until you explicitly activate them in the SeaText dashboard, so no visitor data is processed before you opt in. You need a SeaText account before you can obtain the snippet; the account is tied to one primary URL (S1). Setup takes roughly 60 seconds once you have the snippet (S6). No Odoo administrator rights are required beyond access to the Website module editor.

Limitations and Trade‑offs

Because SeaText is not a native module, you cannot manage its settings from inside Odoo. All configuration—agent activation, language selection, bot‑protection rules, CAPI mapping—happens in the SeaText dashboard. The snippet adds a small JavaScript payload (loaded from Cloudflare edge) which may affect page‑speed scores marginally. Each additional domain requires a separate paid account. Odoo’s own caching or minification features could interfere with the script if not configured to exclude the SeaText domain.

FAQ

Do I need to install a SeaText module from the Odoo App Store?

No. SeaText is not distributed as an Odoo module. You integrate it by pasting a JavaScript snippet into an Embed Code block in the Website builder (S1).

Can I hide the Embed Code block from visitors?

Yes. In the block’s Visibility settings, enable Hide on Desktop. The script still loads but the block occupies no visual space (S1).

How do I use SeaText on multiple websites or domains?

Create a separate SeaText account for each primary domain. Each account gets its own snippet. You cannot share one snippet across multiple domains (S1).

How do I know the integration is active?

Check the SeaText dashboard: the domain status changes to Active after the first page view. You can also verify the script loads in the browser Network tab (S6).

Will SeaText work on Odoo Online or Odoo.sh?

Yes. Any Odoo instance that allows custom code injection in the Website builder supports SeaText (S1).

What happens if I update Odoo?

The JavaScript snippet lives in the website content, not in Odoo’s Python codebase. Odoo upgrades do not remove or break the embed block.

Direct Answer: Editing Variant Options in Odoo

Yes, you can edit variant options like size and color in Odoo. Odoo has built-in support for product variants. You can define attributes such as size, color, and fit. These attributes are managed at the product template level. You can create multiple values for each attribute.

SeaText is an AI-powered optimization tool. It integrates with Odoo to improve your website's content, translation, and SEO. But SeaText does not directly edit product variants. Variant editing is a native Odoo feature.

Why This Matters for Your Store

Product variants are essential for ecommerce. Customers expect to choose size, color, or material. Without variants, you would need a separate product page for every combination. That creates clutter and hurts SEO.

Odoo solves this with a clean variant system. You define attributes once. Odoo generates all combinations automatically. This keeps your catalog organized. It also improves the customer experience.

SeaText works alongside this system. It does not replace Odoo's variant management. Instead, it enhances the content around your products. This includes product descriptions, metadata, and page copy. The result is better SEO and higher conversion rates.

How to Edit Variant Options in Odoo

To edit variant options, follow these steps within Odoo:

1. Access the Sales app – Go to the Odoo dashboard and open the Sales module.
2. Select a product template – Navigate to Products and choose the product template you want to edit.
3. Add or edit attributes – In the product template form, go to the “Variants” tab. Here you can add attributes like Size, Color, or Material. For each attribute, add values (e.g., S, M, L for Size; Red, Blue for Color).
4. Configure variant options – You can also set extra prices, customizations, or images for each variant.
5. Save changes – Odoo automatically generates all possible variant combinations based on the attributes and values you defined.

Prerequisites for Editing Variants

Before editing variant options, ensure:

• You have an Odoo account with access to the Sales app.
• Product variants are enabled in your Odoo settings (usually enabled by default).
• You have the necessary permissions to edit product templates.

If you lack permissions, contact your Odoo administrator. They can grant you access to product editing.

Step-by-Step Guide

Step 1: Log in to Odoo

Log in to your Odoo account. Access the “Website” module if you need to see the frontend effects. For variant editing, the Sales app is the primary location.

Step 2: Navigate to Products

From the Sales dashboard, click on “Products” under the Products section. Find the product template you want to modify.

Step 3: Edit Variants

Open the product template. Under the “Variants” tab, you can add or remove attributes. Each attribute can have multiple values. Odoo will automatically create variants for every combination.

Step 4: Save and Verify

Save your changes. The variants will appear on your website's product page for customers to select.

Verify the Changes

After editing, visit your Odoo website. Check the product page. You should see the variant options (e.g., size dropdown, color swatches). Test that selecting different options updates the price and image correctly.

If something looks wrong, go back to the product template. Check your attribute values. Make sure there are no typos or duplicates. Save again and refresh the page.

Limitations of SeaText and Odoo Variants

SeaText does not manage Odoo product variants. Its integration focuses on content optimization, SEO, and conversion rate improvement. Each SeaText account is linked to a single primary URL. Development URLs like localhost are restricted. To use SeaText on multiple domains, you must create separate accounts.

For variant editing, you must rely on Odoo's native interface. If you need to automate variant content or SEO, SeaText can help by generating optimized product descriptions and metadata. But the variant structure itself is controlled in Odoo.

Another limitation is the number of variants. Odoo allows many attributes and values. But the number of variants grows multiplicatively. For example, 5 sizes and 4 colors create 20 variants. Adding a third attribute with 3 values creates 60 variants. This can become unwieldy. Plan your attributes carefully.

Key Facts About SeaText Odoo Integration

Practical Scenarios

Scenario 1: Adding a New Color

You sell t-shirts. You want to add a green option. Go to the product template. Open the Variants tab. Find the Color attribute. Add “Green” as a new value. Save. Odoo creates the new variant automatically.

Scenario 2: Removing a Size

You no longer sell size XS. Open the product template. Go to the Variants tab. Find the Size attribute. Remove the XS value. Save. Odoo removes all variants that use XS.

Scenario 3: Changing Variant Prices

You want to charge more for size XL. Open the product template. Go to the Variants tab. Select the XL variant. Set an extra price. Save. The price difference appears on the website.

Frequently Asked Questions

Does SeaText provide a way to edit size and color options?

No. SeaText does not edit product variants. It enhances content, SEO, and conversion optimization on your Odoo site. Variant options are managed in Odoo's Sales app.

Can I use SeaText to automatically generate variant descriptions?

SeaText can generate optimized product copy. But it does not automatically populate variant-specific descriptions. You can use its AI content tools to write descriptions for each variant manually or via bulk editing.

What if I need to add new attribute values like “extra large” or “green”?

Add those values directly in Odoo's product template under the Variants tab. SeaText will not affect that process.

Will SeaText interfere with my existing Odoo variants?

No. SeaText runs as a script on your website. It does not modify Odoo's database or product variant settings. It only changes the frontend content (text, layout) using AI.

How do I install SeaText on my Odoo site?

Follow the integration guide. Copy the JavaScript code from your SeaText account. Paste it into the “Embed Code” module in Odoo's website editor. Save. The script will activate on your site.

Is there a limit to how many variant options I can have?

Odoo allows many attributes and values. But the number of variants grows multiplicatively. SeaText has no impact on this limit.

Can I use SeaText on multiple domains?

No. Each SeaText account is linked to a single primary URL. To use SeaText on multiple domains, you must create separate accounts for each domain.

What about development URLs like localhost?

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

Direct answer: how to delete a SeaText variant

Open the product record in Odoo, go to the Variants tab, select the variant you want to remove, and choose Delete from the action menu. Odoo will warn you if the variant is used in orders, stock moves, or other records. If you see that warning, stop and consider archiving the variant instead of deleting it.

Deleting a variant is permanent. It removes the product variant record and can break links to past sales orders, purchase orders, inventory adjustments, and reports. For most cleanup tasks, archiving is safer because it hides the variant without destroying historical data.

Important clarification: SeaText AI is a marketing optimization layer that integrates with Odoo via a JavaScript snippet or Odoo module. It does not create or manage Odoo product variants. A "SeaText variant" typically means a product variant you use in SeaText campaigns (for A/B testing, personalization, or translation). The deletion process is identical to any Odoo product variant.

Before you delete: check what depends on the variant

Odoo links variants to many records. Before deleting, check these areas:

• Sales orders and quotations: past orders may reference the variant. Deleting it can make those lines unreadable or break reports.
• Stock moves and inventory: if the variant has stock, deleting it can create inconsistencies in valuation and stock history.
• Purchase orders: supplier orders may reference the variant.
• Bills of materials and routings: manufacturing records may depend on the variant.
• Website product pages: if the variant is published on the Odoo website, deleting it removes the page.
• SeaText campaign data: if the variant is used in active SeaText A/B tests, personalization rules, or translation projects, deleting it in Odoo will not remove it from SeaText. You must also remove it from the SeaText dashboard.

If any of these exist, archive the variant instead. Archiving keeps the record but hides it from active lists, the website, and SeaText synchronization.

Step-by-step: delete a SeaText variant in Odoo

1. Open the product. Go to Sales or Inventory → Products → Products, then open the parent product that contains the variant.
2. Go to the Variants tab. Click the Variants smart button or tab. You will see a list of all variants for that product.
3. Select the variant. Click the specific variant you want to remove. Do not select the parent product template.
4. Check dependencies. Look at the variant's On Hand quantity, Forecasted stock, and any linked sales or purchase order lines. If any exist, archive instead of delete.
5. Check SeaText links. Log into your SeaText account. Verify the variant is not part of an active A/B test, personalization rule, or translation job. Pause or remove it there first.
6. Delete the variant. From the variant form, choose Action → Delete. Confirm the deletion dialog.
7. Verify the parent product. Return to the product template and confirm the variant no longer appears in the Variants list.

Common mistake: deleting instead of archiving

The most common mistake is deleting a variant that is already used in orders or stock. Odoo may allow the deletion, but historical records then show a broken reference or missing product name. Reports can become misleading, and inventory valuation can be wrong.

If you only want to stop selling or displaying a variant, use the Archive action instead. Archived variants stay in the database but are hidden from active lists, the website, and sales selection. You can restore them later if needed.

Another common mistake: deleting the variant in Odoo but leaving it active in SeaText. SeaText may continue to serve personalized content or run tests for a variant that no longer exists in Odoo, causing errors or blank content for visitors.

How to verify the deletion worked

After deleting, check three places:

• Product Variants list: the variant should no longer appear.
• Sales order lines: open a past order that used the variant. If the line shows an error or blank product, the deletion broke a reference. Restore from backup if possible.
• Inventory valuation report: run the report for the product. If totals changed unexpectedly, the variant had stock that should have been moved or archived first.
• SeaText dashboard: confirm the variant is removed from all campaigns, tests, and translation projects. If SeaText still references it, delete it there manually.

If you see broken references, contact your Odoo administrator or restore a database backup. Do not continue deleting other variants until the issue is understood.

When deletion is safe

Deletion is safe only when the variant has never been used in any transaction. That means no sales order lines, no purchase order lines, no stock moves, no inventory adjustments, no bills of materials, and no website page views tied to it. In practice, this is rare for variants that have existed for more than a few days.

If you created a variant by mistake and it has no history, deletion is the right choice. Otherwise, archive it.

Safe deletion also requires that the variant is not referenced in any SeaText configuration. Check the SeaText dashboard for active experiments, personalization rules, or translation tasks using that variant SKU or ID.

Key facts about SeaText variants in Odoo

Limitations and when this advice does not apply

This process applies to standard Odoo product variants. If you use a custom module or a third-party app that creates variants differently, the delete action may behave differently. Check your module documentation first.

If the variant is linked to a SeaText integration or external script, deleting it in Odoo may not remove it from the external system. You may need to remove the variant from both Odoo and the SeaText dashboard.

Bulk deletion of thousands of variants is not supported through the standard Odoo interface. You would need an export, a filtered import, or a custom script. That is an advanced operation and should be tested on a staging database first.

SeaText AI reads product data from Odoo via its integration. If you delete a variant, SeaText will stop receiving updates for it on the next sync. Historical SeaText analytics for that variant remain in SeaText but will no longer map to an Odoo record.

Practical scenarios and decision criteria

Scenario 1: Variant created by mistake, never used

You added a size "XXL" to a product but no orders, stock, or SeaText campaigns reference it. Safe to delete.

Scenario 2: Variant used in past orders, no current stock

Customers bought the "Red" variant last quarter. No current stock. Archive it. Deleting breaks order history.

Scenario 3: Variant active in SeaText A/B test

The "Blue" variant is in a live SeaText copy test. Pause the test in SeaText, wait for it to finish, then archive in Odoo.

Scenario 4: Variant has stock but discontinued

Move stock to another variant or write it off via inventory adjustment. Then archive the variant.

Decision checklist

• Any sales order lines? → Archive
• Any stock moves or on-hand quantity? → Move stock, then archive
• Active in SeaText campaign? → Pause/remove in SeaText first
• Linked to bill of materials? → Archive
• No history at all? → Delete

Recovery and backup considerations

Odoo deletion is permanent at the database level. The only recovery method is restoring a database backup. Before deleting any variant with potential dependencies, ensure you have a recent backup.

If you use Odoo.sh or a managed hosting provider, check their backup retention policy. Some keep daily backups for 7-30 days. On-premise installations depend on your backup schedule.

SeaText does not back up your Odoo data. If you delete a variant in Odoo, SeaText cannot restore it. SeaText retains its own campaign analytics, but they will reference a non-existent Odoo ID.

Frequently asked questions

Can I restore a deleted SeaText variant?

No. Odoo deletion is permanent. You can only restore from a database backup. If you think you might need the variant later, archive it instead.

What happens to sales orders if I delete a variant?

Past sales order lines may show a broken reference or blank product name. Reports and invoices can become inconsistent. Archive the variant to avoid this.

How do I archive a variant instead of deleting it?

Open the variant, choose Action → Archive. The variant disappears from active lists but remains in the database.

Can I delete multiple variants at once?

Odoo does not offer a simple bulk delete for variants. You can select multiple records in a list view and delete them, but only if none have linked transactions. For large cleanups, use export/import or a custom script.

Why do I get an error when deleting a variant?

The error usually means the variant is referenced by another record, such as a sales order line, stock move, or bill of materials. Odoo blocks deletion to protect data integrity. Archive the variant or remove the references first.

Does deleting a variant remove it from the Odoo website?

Yes, if the variant was published on the website, deleting it removes the page. Archiving also hides the page but keeps the record.

Will deleting a variant in Odoo remove it from SeaText?

No. SeaText maintains its own campaign data. You must manually remove the variant from SeaText campaigns, tests, and translation projects. The next SeaText sync will show the variant as missing in Odoo.

What if SeaText is still showing content for a deleted variant?

SeaText caches content and may serve it until the next sync or cache clear. Remove the variant from SeaText campaigns and clear the SeaText cache from the dashboard.

Quick verdict

SeaText variants and Odoo product variants solve different problems. Odoo product variants let you manage a single product template with multiple attribute combinations (size, color, material) that each become a distinct SKU with its own price, inventory, and barcode. SeaText variants are alternative pieces of marketing copy — headlines, descriptions, CTAs — that the AI writes, tests, and rotates for the same page or product. SeaText integrates with Odoo by embedding a script in an Odoo website page; it reads the rendered variant and swaps or optimizes the text layer without touching Odoo's product data model.

How SeaText variants work

SeaText deploys a single Cloudflare edge script on your site. When a visitor lands on a product page, the script reads the DOM, identifies the product and its current Odoo variant, then selects or generates the best-performing copy variant for that context. The AI Copy A/B Testing agent creates new copy variants automatically from reading telemetry — dwell time, scroll deceleration, re-reading signals — and routes traffic to winners using a multi-armed bandit algorithm. The original Odoo product data (price, SKU, stock) stays untouched.

How Odoo product variants work

In Odoo, a product template holds shared attributes (name, category, base description). You define attribute types (Color, Size) and values (Red, Blue / S, M, L). Odoo then creates a variant record for each combination. Each variant can override price, cost, barcode, weight, volume, route, and bill of materials. On the website, the variant selector updates the displayed price, image, and availability in real time. This is core ERP functionality used by sales, inventory, manufacturing, and accounting.

Where they meet: the Odoo website page

On an Odoo website product page, the variant selector renders the current variant's data. SeaText's embed script sees that rendered output. It can then rewrite the product name, description, or CTA text for that specific variant without changing the underlying Odoo record. For example, if a visitor selects "Red / Large", SeaText might show a headline "Bold Red — Ready to Ship Today" while Odoo still serves the same SKU, price, and stock number.

Key facts

Limitations and boundaries

• SeaText cannot create, delete, or modify Odoo product variants. It only touches the text layer in the browser.
• Odoo product variants cannot run copy tests or personalize messaging per visitor segment without external tooling.
• SeaText requires a valid public domain (no localhost) and one account per domain.
• If you change Odoo's product template structure (add/remove attributes), SeaText continues to work as long as the DOM selectors remain stable.
• SeaText's multi-armed bandit allocation needs traffic volume to reach statistical confidence; very low-traffic variants may stay in exploration mode longer.

Decision framework: which do you need?

1. If you need to sell a t-shirt in three colors and four sizes with different barcodes and stock levels → use Odoo product variants.
2. If you already have variants in Odoo but your product descriptions are generic and you want the AI to write and test better copy for each variant → add SeaText.
3. If you want to test whether "Free shipping on Red Large" beats "Red Large — Best Seller" without duplicating SKUs → SeaText variants.
4. If you need the variant to carry a different cost price for manufacturing → Odoo product variants only.

Common misconceptions

• "SeaText replaces Odoo variants." False. SeaText has no write access to Odoo's product.product table.
• "Odoo variants can A/B test headlines." Not natively. You would need a separate CRO tool or custom development.
• "SeaText variants show up in Odoo backend." They do not. They exist only in SeaText's dashboard and the visitor's browser.

FAQ

Can SeaText optimize copy for each Odoo variant individually?

Yes. The script detects the active variant on the page and can serve different copy variants per Odoo variant.

Do I need to map SeaText variants to Odoo variants manually?

No. SeaText reads the rendered page. As long as the variant selector updates the DOM predictably, the AI associates copy performance with that variant context automatically.

Will SeaText slow down my Odoo website?

The edge script adds ~0ms redirect latency and loads asynchronously. It is SOC 2 Type II certified and GDPR/CCPA compliant.

Can I use SeaText on Odoo's backend (not the website)?

SeaText is designed for the public-facing website. It does not integrate with Odoo's backend views.

What happens if I delete an Odoo variant?

SeaText stops seeing that variant on the front end. Historical copy performance data for that variant remains in SeaText's dashboard but no longer receives traffic.

Does SeaText support Odoo's "optional products" or "accessory products"?

SeaText optimizes text on the page it's installed on. If optional products render on the same page, their copy can be optimized too.

How do I measure lift from SeaText variants vs Odoo variant changes?

SeaText reports conversion lift per copy variant. Odoo reports sales per product variant. Compare them side by side in your analytics to isolate copy impact from assortment changes.

Why you cannot edit SeaText variants in Odoo

SeaText is not an Odoo module that adds variant fields. It is an external AI service that injects optimized copy into your live pages via a single JavaScript snippet. You install that snippet once using Odoo's Embed Code block (found under Website → Edit → Blocks → Dynamic Content). After installation, SeaText reads visitor behavior and rewrites text in the browser—nothing is stored as an Odoo product variant or translatable field.

If you are seeing errors while "editing variants," you are likely trying to change SeaText-generated copy inside Odoo's product variant UI, or you pasted the snippet into the wrong block type. The fix is to stop editing in Odoo and manage copy changes inside the SeaText dashboard instead.

Diagnostic sequence: identify the real symptom

1. Check where the error appears. Is it in Odoo's backend (product variant form, translation interface, website builder) or on the live frontend (console errors, missing translations, unchanged copy)?
2. Verify the installation step. Open the page in Odoo Website builder, click Edit, and confirm the Embed Code block exists under Dynamic Content. The block must contain the exact SEATEXTCODEINTEGRATION snippet provided by your SeaText account.
3. Confirm the domain matches your SeaText account. SeaText restricts development URLs such as localhost and dynamic staging domains. Each primary domain needs its own SeaText account.
4. Look for JavaScript console errors. Open browser dev tools on the live page. Errors like Failed to load resource or SeaText not initialized usually mean the snippet was stripped, minified incorrectly, or blocked by a Content Security Policy.
5. Test with SeaText disabled. Temporarily unpublish the Embed Code block. If the Odoo backend error disappears, the issue is not a native Odoo variant problem.

Common causes and corrective actions

1. Snippet pasted into wrong block type

Odoo's Website builder has several code-related blocks (HTML, Script, Embed Code). Only the Embed Code block under Dynamic Content preserves the snippet exactly as SeaText requires. Using an HTML or Script block often strips attributes or wraps the code in extra tags, breaking initialization.

2. Snippet saved but not published

After pasting the snippet and clicking Save in the Embed Code pop-up, you must also click Save on the page editor and then Publish the page. Unpublished changes are not served to visitors, so SeaText never loads.

3. "Hide on Desktop" visibility left enabled

The installation guide recommends enabling Hide on Desktop in the Visibility section so the block occupies no visual space. If you accidentally disable this, an empty container may appear on the page, but SeaText still works. This is cosmetic, not an error.

4. Using a restricted development domain

SeaText blocks localhost, 127.0.0.1, and dynamic preview domains (e.g., *.odoo.com staging URLs). You must use a real, registered domain (or a stable subdomain like staging.yourdomain.com) that matches the primary URL in your SeaText account.

5. Multiple domains on one SeaText account

Each SeaText account is linked to a single primary URL. If you run production and staging on the same account, the second domain will fail silently. Create a separate SeaText account for each domain.

6. Content Security Policy (CSP) blocking the script

If your Odoo instance or Cloudflare/WAF adds a CSP header without script-src 'unsafe-inline' https://cdn.seatext.com (or the current SeaText CDN), the browser will refuse to execute the snippet. Check the console for Refused to execute inline script and adjust the CSP accordingly.

How SeaText actually works inside Odoo

SeaText's Odoo integration is a one-time copy-paste of a JavaScript snippet. The snippet loads an AI agent that:

• Analyzes visitor reading behavior (dwell time, scroll depth, re-reading patterns)
• Generates copy variants for headlines, product descriptions, CTAs
• Serves the best-performing variant to each visitor in real time
• Reports results in the SeaText dashboard, not in Odoo

Because the variants exist only in the browser session, Odoo's product variant matrix, translation CSV exports, and website translation UI never see them. Editing those native Odoo fields changes the fallback copy that SeaText optimizes from, but it does not edit the live variants themselves.

Limitations and when this advice does not apply

• If you have a custom Odoo module that does store SeaText variants as database records (not standard), the above diagnostic does not cover it. Check your module's documentation.
• SeaText's own dashboard may show variant edit errors (e.g., character limits, language mismatches). Those are fixed inside the SeaText UI, not Odoo.
• Odoo version upgrades (e.g., 16 → 17) sometimes move the Embed Code block location. The function remains the same; only the menu path changes.

Key facts

FAQ

Why do my product variant changes in Odoo not appear on the live site?

SeaText overrides the fallback copy with AI-generated variants in the visitor's browser. Edit the fallback in Odoo if you want a new baseline, but control the live variants from the SeaText dashboard.

I pasted the snippet but see no SeaText activity in the dashboard.

Confirm the page is published, the domain matches your SeaText account exactly, and no CSP or ad blocker prevents the script from loading. Check the browser console for errors.

Can I use SeaText on my Odoo staging environment?

Only if the staging URL is a real, stable subdomain (e.g., staging.yourdomain.com) and you create a separate SeaText account for it. Dynamic Odoo preview URLs will not work.

Does SeaText work with Odoo's website translation feature?

SeaText translates into 125 languages via its own Translation Agent. Odoo's native translation CSV/PO exports will not capture SeaText-generated copy because it renders client-side.

What if I need to disable SeaText temporarily?

Unpublish the Embed Code block in Odoo Website builder, then save and publish the page. SeaText stops loading immediately.

Where do I get the current snippet if I lost it?

Log into your SeaText account; the integration code is displayed in the setup section for that domain.

Understanding the SeaText and Odoo Relationship

Many users assume that SeaText integrates directly into the Odoo database to modify product attributes like size, color, or material. This is a common misconception. SeaText is an autonomous AI layer that functions independently of Odoo’s backend database structure.

SeaText uses a JavaScript snippet to inject optimized copy, translations, and A/B test variants directly into the browser of your website visitor. Because it operates on the client side, it does not create or edit Odoo product variants. If you are looking to change the physical attributes of a product, you must use Odoo's native interface. If you want to optimize the language, headlines, or CTAs displayed to your customers, you use the SeaText dashboard and the Embed Code block.

Comparison: SeaText vs. Odoo Native Variants

Understanding the distinction between these two systems is critical for maintaining an accurate e-commerce store. Use the table below to determine which system handles your specific needs.

Who is this for? Use Odoo native variants if you need to manage stock levels or specific pricing for different product versions. Use SeaText if you want to increase conversion rates through AI-driven copy testing and real-time personalization.

How to Edit SeaText Copy Variants

SeaText generates "variants" of your website copy to improve conversion rates. These are not Odoo product variants; they are dynamic text replacements. To modify how these appear or to update the script, follow these steps:

1. Log in to your Odoo Website module and navigate to the page containing the SeaText script.
2. Click the Edit button in the top right corner of the Odoo editor.
3. Locate the Embed Code block where the SeaText snippet is installed.
4. Click the block to open the configuration panel.
5. Modify the JavaScript code within the window. You can update account IDs or configuration parameters here.
6. Click Save and publish your page.

Changes made to the JavaScript snippet take effect immediately. Because the script is client-side, you do not need to perform a module upgrade or clear your Odoo server cache.

Managing Odoo Native Product Attributes

If your goal is to change the actual product options (e.g., changing "Small" to "Extra Small" or adding a new color), you must use the Odoo backend. SeaText cannot modify these database-level records.

1. Navigate to Sales → Products → Products.
2. Select the product template you wish to modify.
3. Click the Attributes & Variants tab.
4. Add or edit the attribute lines.
5. Define the specific values for each attribute.
6. Save the product record.

These changes update the Odoo database directly. Once saved, the product configurator on your website will reflect these new options automatically.

Why SeaText Matters for Conversion

Traditional A/B testing often fails because it requires massive traffic to reach statistical significance. SeaText solves this by using AI reading telemetry. It analyzes how visitors interact with your page—measuring dwell velocity and scroll deceleration—to identify exactly where they lose interest.

By deploying SeaText, you move away from binary conversion tracking. Instead of waiting months for a test to finish, the AI uses multi-armed bandit algorithms to allocate traffic to winning copy variants in real time. This allows even low-traffic stores to see significant improvements in conversion rates without needing a dedicated team of data scientists.

Limitations and Best Practices

While SeaText is a powerful tool for optimization, it has specific operational boundaries. First, SeaText cannot add or remove Odoo variant attributes; it only optimizes the text displayed to the user. Second, each domain requires its own SeaText account. You cannot share a single snippet across multiple primary URLs, as the AI associates traffic with a specific account ID.

For testing, avoid using local development environments like localhost. SeaText requires a valid, live domain to associate traffic correctly. If you are running multiple websites, ensure you create a unique account for each to maintain data integrity and accurate conversion reporting.

Frequently Asked Questions

Can I edit SeaText variant attributes from the Odoo backend?

No. SeaText does not expose its variant settings within the Odoo interface. All modifications to SeaText behavior must be handled via the JavaScript snippet in the Embed Code block.

How do I translate product variant attributes with SeaText?

You can enable the Website Translation (125 Langs) agent within your SeaText dashboard. This agent translates visible text on your page, including variant labels, without altering the underlying data in Odoo.

Does SeaText create Odoo product variants for each AI copy variant?

No. SeaText copy variants are served dynamically via JavaScript. They exist only in the visitor's browser and do not create database records in Odoo.

What happens if I change an attribute value in Odoo?

SeaText will detect the updated text on the next page load and generate new translations or copy variants based on the updated content.

Is there a SeaText Odoo module that adds variant fields?

No. The integration is strictly via the JavaScript snippet. There is no Odoo module that adds SeaText-specific fields to the product variant form.

How do I verify my SeaText installation?

Visit your live page in an incognito window. Open your browser's Developer Tools, navigate to the Network tab, and filter for "seatext." If the script loads, your integration is active.

Quick answer: SeaText has no variants in Odoo

SeaText AI is a conversion-optimization platform that runs on your website via a JavaScript snippet. It does not create product variants, SKUs, or inventory records inside Odoo. The integration is a one-time embed of a script tag — nothing more.

If you're looking to manage inventory for product variants (like t-shirts in different sizes and colors), you use Odoo's built-in product variant feature. That's a separate, native Odoo capability.

How SeaText actually integrates with Odoo

The SeaText-Odoo connection works through Odoo's Website editor. You add an "Embed Code" block to a page, paste the SeaText JavaScript snippet, and save. The script then runs on the front end, analyzing visitor behavior and rewriting copy in real time.

1. Log in to Odoo and open the Website module.
2. Navigate to the page where you want SeaText active (usually the homepage or a landing page).
3. Click Edit to open the website builder.
4. In the Blocks panel, scroll to Dynamic Content and drag an Embed Code block onto the page.
5. Click the block's Edit button in the right panel.
6. Paste the JavaScript snippet from your SeaText account into the pop-up window and click Save.
7. Optional: In the block's Visibility settings, enable Hide on Desktop if you only want the script to load on mobile, then save again.

That's the entire integration. No product data, variants, or inventory settings are exchanged.

What SeaText does once installed

The script activates SeaText's AI agents on your site. These agents can:

• Rewrite headlines and CTAs to match each visitor's search keyword (Google Ads Landing Page AI)
• Run continuous multi-armed bandit copy tests without 50/50 traffic splits (AI Copy A/B Testing)
• Translate the entire site into 125 languages with zero code (Website Translation)
• Detect and block bot traffic, then request refunds from ad platforms (Bot Protection & Refund Agent)
• Forward 100% of real purchases to Meta and Google CAPI (Conversion Relay)

All of this happens in the browser. SeaText never writes to your Odoo product catalog or inventory tables.

Managing actual product variant inventory in Odoo

If your goal is to track stock for product variations (size, color, material), you use Odoo's native variant system. Here's the standard workflow:

1. Go to Inventory → Products → Products and open (or create) a product template.
2. On the Variants tab, add attributes like Size (S, M, L) and Color (Red, Blue).
3. Odoo automatically generates a variant for each combination (e.g., Red-S, Red-M, Blue-L).
4. Open each variant to set its own SKU, Barcode, Sales Price, Cost, and Initial Quantity.
5. Use Inventory → Operations → Inventory Adjustments to correct on-hand quantities per variant.
6. Enable Reordering Rules on variants that need automatic purchase orders when stock drops below a minimum.

Each variant is a distinct product record with its own stock moves, valuation, and traceability.

Common confusion: SeaText "variants" vs. Odoo product variants

SeaText's own platform does generate copy variants — alternative headlines, descriptions, CTAs — but these live inside SeaText's dashboard and are served dynamically via the JavaScript snippet. They are not Odoo records. You don't manage them in Odoo's inventory, sales, or product modules.

If you see "variant" in SeaText documentation, it refers to AI-generated copy variations for A/B testing. If you see "variant" in Odoo, it refers to product attribute combinations (size/color). They are unrelated.

Verification step

After embedding the SeaText script, visit your live site and open the browser dev tools (F12 → Console). You should see a log line confirming the SeaText snippet loaded. In your SeaText dashboard, the domain status will flip to "Active" once the first pageview hits. No Odoo configuration beyond the Embed Code block is required.

When to involve SeaText support

• The script loads but the dashboard stays "Inactive" after 10+ pageviews.
• You need SeaText on multiple domains — each domain requires its own SeaText account and its own Embed Code block.
• You want to exclude certain pages from SeaText rewrites (configured in SeaText dashboard, not Odoo).

Key facts

Limitations

• SeaText cannot push price or stock changes into Odoo.
• SeaText cannot create or delete Odoo product variants.
• If you need product data (prices, availability) to inform SeaText's copy rewrites, you must expose that data on the page (e.g., via JSON-LD or data attributes) — SeaText does not query Odoo's backend.

FAQ

Does SeaText sync with Odoo's product catalog?

No. SeaText runs entirely in the browser. It reads the rendered DOM, not Odoo's database.

Can I use SeaText to test different product descriptions for each variant?

SeaText can rewrite any text on the page, including variant-specific description blocks, but it doesn't know which variant is selected unless your theme exposes that state in the DOM. You'd need to ensure the variant selector updates a data attribute SeaText can read.

Do I need a separate SeaText account for each Odoo website?

Yes. Each SeaText account is tied to one primary URL. If you run multiple Odoo websites (different domains), create a separate account for each.

Will SeaText slow down my Odoo site?

The snippet loads asynchronously and is designed for zero-flicker operation. Typical impact is under 50 ms.

Can I hide SeaText from specific customer groups in Odoo?

Not via Odoo. SeaText's targeting rules (by UTM, referrer, geography, device, etc.) are configured inside the SeaText dashboard.

What if I uninstall the Embed Code block?

SeaText stops running immediately. No data is left in Odoo because none was ever stored there.

You edit SeaText variant images by updating the image field in Odoo's product variant form, not in SeaText. SeaText injects AI-generated text via an Embed Code block and does not store or manage product images. Follow the steps below to locate the variant, upload a new image, and verify the change.

What SeaText Variant Images Are

SeaText variant images are the product images displayed for each variant on your Odoo website when SeaText AI is active. SeaText itself does not host, generate, or modify these images. Instead, SeaText runs as a JavaScript embed that reads the page DOM after Odoo renders the variant, then injects AI-generated copy such as headlines, descriptions, or calls to action. The image you see for a variant comes entirely from Odoo's native product variant image field. When you change that field in Odoo, the new image appears immediately; the SeaText embed continues to run without any reconfiguration.

Why You Might Need to Edit Them

You may need to update variant images when launching new product colors, replacing low-quality photos, aligning images with updated branding, or correcting mismatched images after a catalog import. Because SeaText only affects text content, any image change is a pure Odoo operation. This separation means you can refresh visuals without touching the SeaText integration or worrying about breaking AI-generated copy.

Prerequisites

• Access to an Odoo website with the SeaText module installed via the Embed Code block (see SeaText Odoo integration guide for embed steps).
• Administrator or product manager rights to edit product variants in Odoo.
• The new image file ready for upload (JPEG, PNG, or WebP; recommended size under 2 MB for performance).
• Knowledge of which product and variant you intend to update.

Step-by-Step Editing Process

1. Log in to your Odoo account and open the Website module from the dashboard.
2. Navigate to the product page that contains the SeaText variant you want to edit.
3. Click the Edit button to open the page editor.
4. In the editor, locate the product variant (usually under the Variants tab of the product form).
5. Select the specific variant whose image you need to change.
6. Click the image placeholder or the Edit icon next to the current image.
7. In the file dialog, choose the new image file and confirm the upload.
8. Save the variant changes, then save the page.
9. Refresh the live page to verify the new image appears for that variant.

These steps rely on Odoo's native variant image functionality. The SeaText integration guide (S1) describes how to add the Embed Code block for AI copy injection, but does not alter the image upload process.

How SeaText and Odoo Handle Images

SeaText works by inserting a JavaScript snippet into your Odoo pages via an Embed Code block. According to the SeaText Odoo integration guide (S1), you log in to Odoo, open the Website module, edit the target page, drag the Embed Code block from the Dynamic Content section into place, paste the SeaText code snippet, and optionally hide the block on desktop. Once saved, the script runs on every page load, analyzes visitor behavior, and injects optimized text into designated elements. It does not interact with the product variant image field at all. Odoo stores each variant's image in its database and serves it through the standard product rendering pipeline. When a visitor switches variants, Odoo swaps the image source; SeaText then reads the updated DOM and applies its text transformations. Because the two systems operate independently, changing an image in Odoo never requires a SeaText re-embed or script update.

Common Issues and Troubleshooting

• Image does not update on the front end: Clear Odoo's cache (via the developer tools or by toggling the website's maintenance mode) and your browser cache. Odoo may serve a cached version of the product image.
• Wrong variant shows the new image: Ensure you selected the correct variant in the Variants tab before uploading. Each variant has its own image field.
• SeaText copy disappears after image change: This should not happen. If it does, verify the Embed Code block is still present and published on the page (S1 steps 4-6). The script runs independently of image fields.
• Large image slows page load: Optimize images before upload (compress to under 2 MB, use WebP). Odoo does not automatically compress variant images.

Limitations and Trade-offs

• SeaText cannot generate, edit, or replace product images. It only produces text content (headlines, descriptions, CTAs) via its AI agents (S2, S3, S5, S6).
• Image management remains entirely in Odoo. Bulk image updates require Odoo's import/export tools or third-party apps, not SeaText.
• If you disable or remove the Embed Code block, SeaText's AI copy stops appearing, but variant images remain unaffected because they are native Odoo data.
• SeaText accounts are tied to a single primary domain (S1). If you run multiple Odoo websites on different domains, each needs its own SeaText account and embed code.
• Development URLs like localhost are restricted for security (S1). Test image changes on a staging domain that matches your SeaText account.

Best Practices

• Optimize before upload: Resize images to the maximum display dimensions used by your theme. Compress with tools like TinyPNG or Squoosh to keep files under 2 MB.
• Use consistent naming: Name files descriptively (e.g., "product-red-front.webp") to simplify future maintenance.
• Leverage Odoo's import/export for bulk updates: Export the product variant template, update the image URL or base64 column, and re-import. This is an Odoo-native workflow, not a SeaText feature.
• Test variant switching: After uploading, visit the live page and cycle through each variant to confirm the correct image loads.
• Keep the Embed Code block published: Do not archive or delete the block (S1 step 6) unless you intend to disable SeaText entirely.

Frequently Asked Questions

• Do I need to re-embed the SeaText script after changing an image? No. The embed script runs independently of the image field (S1).
• Can I use SeaText to generate alternative images for variants? Not currently. SeaText focuses on text and copy generation (S2, S3, S5, S6).
• What image formats does Odoo accept for variant images? JPEG, PNG, and WebP are supported; keep files under 2 MB for best performance.
• Is there a way to bulk-update images for many variants? Yes, Odoo's import/export feature lets you update image URLs or base64 data for multiple variants at once. This is general Odoo functionality, not specific to SeaText.
• Will changing a variant image affect SeaText's AI copy for that variant? No. SeaText generates copy based on page context and visitor signals, not the image file (S4, S5).
• What happens if I delete the Embed Code block? SeaText's AI copy stops appearing. Variant images remain in Odoo and continue to display normally.

Further Reading

• How to put different image on each variant of a product? | Odoo Forum
• Product Images and Variants | Odoo Forum
• Easier way to add images to variants | Odoo Forum
• SeaText Odoo Integration Guide (S1)