Why SKU Accuracy Matters for Inventory and Sales

SKUs are the backbone of your inventory system. They identify each product variant uniquely. When SKUs are wrong, inventory counts become unreliable. You might oversell a product you don't have or understock a bestseller.

Accurate SKUs also keep sales channels in sync. If you sell on Amazon, eBay, or Shopify, those platforms use SKUs to match listings. A mismatch can cause listing errors or duplicate products.

SKUs help with reporting too. You can track which variants sell best. You can analyze margins by SKU. You can forecast demand more accurately. Without clean SKUs, your data is noisy and decisions get harder.

For SeaText users, SKU accuracy matters even more. SeaText generates AI copy variants for your product pages. Those copy variants drive traffic and conversions. If your SKU is wrong, the wrong product might get the traffic. That wastes your marketing spend.

In short, SKU accuracy protects your revenue, your inventory, and your customer trust. It is not just a data hygiene task. It is a business-critical operation.

How Odoo Variant SKUs Work

Odoo uses a product template and product variant structure. The template holds shared attributes like name and description. Variants hold specific attribute combinations like size and color.

Each variant has its own SKU field. In Odoo, this field is often called Internal Reference or Reference. It is separate from the template's SKU.

When you create a variant, Odoo can auto-generate a SKU. It might combine the template SKU with attribute values. For example, SHIRT-BLUE-M for a blue medium shirt.

You can also set SKUs manually. This gives you full control. You can use your own naming convention. You can match SKUs to external systems.

SeaText does not touch this SKU system. SeaText runs as a JavaScript snippet on your Odoo website. It reads the product variant's database ID from the page HTML. It does not read or write the SKU field.

So when you edit a SKU, you are working purely in Odoo's native product management. SeaText's AI copy generation continues to work because it relies on the variant ID, not the SKU.

Step-by-Step: Editing the SKU Field

Here is the exact process to edit a SKU for a SeaText-enabled product variant in Odoo.

1. Log in to your Odoo backend with an account that has product editing permissions. You need access to the Inventory or Sales module.
2. Open the Inventory module (or Sales module, depending on your setup).
3. Navigate to Products > Products.
4. Find the parent product that contains the variant you want to edit. Click on its name to open the product form.
5. Look for the Variants tab. Click on it to see the list of variants.
6. Click on the specific variant you want to edit. This opens the variant's individual product form.
7. Find the SKU field. It may be labeled Internal Reference or Reference.
8. Type the new SKU value. Make sure it is unique across your entire product database.
9. Click Save to apply the change.

That is it. The SKU is now updated. SeaText will continue to work because it does not depend on the SKU.

Trade-offs and Risks of Editing SKUs

Editing SKUs is not always risk-free. Here are the main trade-offs to consider.

Impact on Historical Orders

When you change a SKU, historical orders still reference the old SKU. Odoo keeps the old SKU in the order lines. This can create confusion in reports. You might see two SKUs for the same product in your sales history.

To avoid this, document the change. Keep a mapping of old SKU to new SKU. This helps with audits and reconciliation.

Impact on External Integrations

If you sync Odoo with an external ERP, marketplace, or accounting system, changing a SKU can break the sync. The external system might not recognize the new SKU. This can cause failed orders or duplicate listings.

Always check with your system administrator before changing SKUs in a synced environment. You may need to update the external system first.

Impact on Reporting

Reports that group by SKU will change. Historical data will be split between old and new SKUs. This can make trend analysis harder.

Consider running reports before and after the change. Compare them to ensure nothing is lost.

Risk of Duplicate SKUs

Odoo may allow duplicate SKUs. This is dangerous. Duplicate SKUs can cause inventory tracking errors. They can also confuse pickers and packers.

Always verify that your new SKU is unused. Use Odoo's search function to check.

Barcode and Other Fields

SKUs are not automatically linked to barcodes. If you use barcodes, update them separately. Otherwise, your scanning system may fail.

Bulk Editing and Automation

Editing SKUs one by one is fine for a few variants. But what if you have hundreds? Bulk editing is the answer.

Using Odoo's Import/Export Feature

Odoo has a built-in import/export tool. You can export your product list to a CSV file. Edit the SKU column in a spreadsheet. Then import the file back.

Here is the process:

1. Go to Products > Products.
2. Click the Export button. Select the fields you need, including the variant ID and SKU.
3. Download the CSV file.
4. Open it in a spreadsheet. Update the SKU values.
5. Save the file.
6. Go back to Odoo and click Import.
7. Upload the CSV file. Map the columns to the correct fields.
8. Click Import to apply the changes.

This method is fast and reliable. It also lets you apply a consistent naming convention across many variants.

Using Odoo Automated Actions

You can also set up automated actions. For example, you can create a rule that assigns SKUs to new variants automatically. This is useful if you add many variants regularly.

Go to Settings > Technical > Automated Actions. Create a new action that triggers when a variant is created. Use a Python expression to generate the SKU based on attribute values.

This saves time and reduces human error.

SeaText and Bulk Editing

SeaText does not manage SKUs. So bulk editing SKUs does not affect SeaText's AI copy variants. The copy variants are tied to the variant's database ID, not the SKU. You can change SKUs freely without disrupting your A/B tests.

Verification and Troubleshooting

After editing a SKU, verify the change. Here is how.

Search for the New SKU

Go to the product list and search for the new SKU. It should appear in the results. If it does not, the save may have failed.

Check Inventory Adjustments

Open the variant's inventory adjustments or stock moves. The new SKU should be reflected in all related records. If not, there may be a sync issue.

Check SeaText Functionality

Visit the product page on your Odoo website. SeaText should still generate copy variants. The page should display the correct variant. If SeaText stops working, check the JavaScript snippet. It may have been removed or altered.

Common Issues and Fixes

• SKU field is missing: Enable developer mode. Go to the form view settings and make the SKU field visible.
• Duplicate SKU error: Search for the SKU before saving. If it exists, choose a different value.
• External sync broken: Check the external system. Update the SKU there first, then in Odoo.
• Historical orders show old SKU: This is normal. Keep a mapping document for reference.

Frequently Asked Questions

Can I edit SKUs in bulk for multiple SeaText variants?

Yes. Use Odoo's import/export feature to update SKUs for multiple variants at once. SeaText's copy will continue to work because it relies on the variant's internal ID, not the SKU.

Does changing the SKU affect SeaText's A/B test results?

No. SeaText tracks copy variants by the page URL and visitor behavior, not by SKU. Changing the SKU will not reset or alter test data.

What if the SKU field is missing on the variant form?

Go to the form view settings in developer mode. Ensure the SKU field is visible. Alternatively, check if your Odoo version uses a different field name like "Internal Reference".

Can I automate SKU assignment for new SeaText variants?

Yes. Use Odoo's automated actions or a barcode generation rule to assign SKUs when new variants are created. SeaText does not generate SKUs—it only generates copy.

Will editing the SKU break the SeaText script on the product page?

No. The SeaText JavaScript snippet is embedded in the website theme and works independently of the product SKU. It reads the product variant's database ID from the page HTML, which does not change when SKU is updated.

What happens to historical orders when I change a SKU?

Historical orders keep the old SKU. This is normal. Keep a mapping of old to new SKUs for reporting and audit purposes.

How do I avoid duplicate SKUs?

Always search for the new SKU before saving. Use Odoo's search function. If the SKU exists, choose a different value.

What if I sync Odoo with an external ERP?

Check with your system administrator first. Changing a SKU may break the sync. Update the external system before changing the SKU in Odoo.

Comparison: Editing SKU in Odoo vs SeaText AI Copy Variants vs Manual SKU Management

Recommendation: Use Editing SKU in Odoo for inventory accuracy and external sync. Use SeaText AI Copy Variants for conversion optimization. Use Manual SKU Management only for small catalogs with occasional changes. For most growing ecommerce stores, combine Odoo SKU editing with SeaText AI copy testing.

Learn More and Next Steps

Now that you know how to edit SKUs, you can keep your inventory accurate and your SeaText copy tests running smoothly. For more details on SeaText's Odoo integration, visit the Odoo Integration page. It shows the exact steps to embed the SeaText JavaScript snippet on your Odoo website.

If you want to explore SeaText's AI copy variant functionality, check the SeaText homepage. You can see how AI copy A/B testing and other agents work. You can also book a demo to see how SeaText fits your workflow.

For setup guides and playbooks, visit the SeaText blog. It has 400+ guides on CRO, AI SEO, bot protection, and more.

Start by editing your SKUs in Odoo. Then activate SeaText to test copy variants. Together, they keep your inventory accurate and your conversions growing.

Understanding the System Divide

To manage your website effectively, you must understand that SeaText and Odoo operate on two separate layers. Odoo is your backend database for inventory, pricing, and physical product variants. SeaText is an AI-driven overlay that injects dynamic copy—such as headlines, CTAs, and descriptions—into your site via a JavaScript snippet.

Because these systems do not share a native database connection, editing availability in one does not automatically update the other. You cannot change the availability of a physical product by adjusting SeaText settings, nor can you use Odoo's backend to toggle SeaText's AI-generated copy variants.

What Are SeaText Content Variants?

SeaText variants are not SKUs. They are content variations designed to improve conversion rates. The SeaText script analyzes visitor behavior, traffic sources, and intent to display the most relevant copy for that specific user. You manage these variants within the SeaText dashboard.

These variants are "always on" unless you manually pause them in the SeaText platform. They exist to optimize the user journey, not to track stock levels. If you need to stop a specific headline or CTA from appearing, you must log into your SeaText account and disable the specific experiment or agent.

Odoo Product Variant Availability Controls

Odoo's native variants represent physical or configurable attributes like size, color, or material. Each combination has its own SKU, price, and inventory count. When you need to stop selling a specific item, you must use Odoo's internal tools.

Odoo provides two primary ways to manage this: archiving a variant or toggling its website visibility. Archiving removes the variant from all Odoo views, including quotes and POS. Toggling "Website Published" hides the variant from your e-commerce store while keeping it available for internal sales teams.

Comparison: SeaText vs. Odoo Variants

Who each option fits: Use Odoo's native tools for inventory and stock management. Use SeaText to optimize the messaging that surrounds those products to increase conversion rates.

Steps to Edit Odoo Product Availability

If you need to change the availability of a physical product variant, follow these steps within your Odoo instance:

1. Log in to your Odoo dashboard and open the Inventory or Sales application.
2. Navigate to Products > Products and select the relevant product template.
3. Click the Variants smart button or tab to view the list of combinations.
4. Select the specific variant row you wish to modify.
5. To hide the item from the website, toggle the Website Published field to off.
6. To fully disable the variant, use the Action menu and select Archive.
7. Click Save to apply your changes.

Integrating SeaText with Odoo

SeaText integrates via a single JavaScript snippet. This ensures that your website remains fast and your Odoo database remains clean. To install or update the script:

1. Open the Website module in Odoo and enter the editor for your target page.
2. Locate the Dynamic Content section in the Blocks panel.
3. Drag an Embed Code block onto your page.
4. Click Edit in the right-hand panel.
5. Paste your SeaText JavaScript snippet into the provided area.
6. Click Save.

Once the script is active, SeaText will begin analyzing visitor reading telemetry and deploying copy variants. Remember that SeaText does not read your Odoo inventory status by default. If you require SeaText to react to stock levels, you must implement a custom middleware layer to push Odoo data to the SeaText API.

Frequently Asked Questions

Can I use SeaText to show different headlines for each Odoo product variant?

Not automatically. SeaText personalizes content based on visitor context, such as traffic source or reading behavior. To link copy to a specific Odoo variant ID, you would need to pass that ID to SeaText via custom data attributes.

Does archiving an Odoo variant remove SeaText copy?

No. The SeaText script operates independently. If the product is hidden by Odoo, the SeaText copy may still load on the page, though it will not be associated with a visible product.

How do I pause a SeaText copy variant?

Log in to your SeaText dashboard, navigate to the active agent or experiment, and toggle the variant off. No changes are required in Odoo.

Can I edit SeaText availability from the Odoo website builder?

No. The Odoo website builder only hosts the Embed Code block. All management of SeaText variants must occur within the SeaText platform.

What if I need SeaText to respect real-time stock levels?

This requires custom development. You would need to create a bridge (such as an Odoo webhook) that sends stock updates to your server, which then communicates with the SeaText API to update targeting rules.

Is there a dedicated SeaText module in the Odoo App Store?

No. SeaText is designed to be platform-agnostic and integrates via a standard JavaScript snippet, ensuring compatibility without the need for specific Odoo modules.

Understanding the SeaText and Odoo Relationship

SeaText integrates with Odoo via a lightweight JavaScript snippet. This snippet is placed within an Odoo "Embed Code" block. It does not modify your Odoo database records. Instead, it acts as an overlay that serves AI-generated copy variations dynamically to your visitors.

Because SeaText operates as an external layer, Odoo's native list view and bulk-edit tools cannot see or modify these variants. Attempting to edit product variants in Odoo will only change your catalog data, not the AI-optimized marketing copy served by SeaText.

Comparison: Odoo Native Variants vs. SeaText AI Variants

Who is this for? Use Odoo native variants for physical product attributes. Use SeaText variants for marketing copy, headlines, and CTAs that need to be tested and optimized for conversion.

Why Bulk Editing Matters for Conversion

Manual A/B testing is slow. Traditional methods often require thousands of visitors to reach statistical significance. By using SeaText's bulk editing capabilities, you can manage hundreds of copy variations across your entire site simultaneously. This allows you to respond to seasonal trends, update brand messaging, or correct friction points identified by AI reading telemetry without editing individual pages one by one.

Step-by-Step: Bulk Editing in the SeaText Dashboard

To modify multiple variants at once, follow these steps:

1. Log in to your SeaText account.
2. Navigate to the "AI Copy A/B Testing" agent.
3. Filter your view to isolate the specific pages or components you wish to update. You can filter by URL, traffic source, or current test status.
4. Select the checkboxes next to the variants you want to modify.
5. Use the Bulk Action Toolbar that appears at the top of the list.
6. Choose your action: Edit text, Approve, Reject, Pause, or Delete.
7. Confirm your changes. The updates propagate to your live site via the edge network within minutes.

Managing Large-Scale Copy Updates

When you need to update copy across hundreds of pages, the SeaText dashboard is your primary tool. If you update a product title in Odoo, SeaText automatically detects the change on the next page render. It will then generate fresh variants based on the new content. You do not need to manually trigger a sync.

For global changes, such as suppressing a specific headline across your entire site, use the URL pattern filter. Select all matching variants and choose "Pause" or "Reject." This ensures consistent messaging without the risk of human error associated with manual updates.

Limitations and Best Practices

While SeaText provides powerful bulk-editing tools, it is important to understand the boundaries of the integration:

• No Odoo Import/Export: You cannot use Odoo's CSV import/export to change SeaText variants. All changes must occur within the SeaText interface.
• Edge Propagation: Changes are pushed to the edge network. This means your site remains fast, and you do not need to clear Odoo caches or perform a site redeploy.
• Security: Ensure your Embed Code block is correctly configured. If the script is removed from Odoo, SeaText will stop serving variants, and your site will revert to its original static copy.

Frequently Asked Questions

Can I bulk-edit SeaText variants from Odoo's backend?

No. SeaText variants are not stored as Odoo records. You must use the SeaText dashboard to manage and edit your AI-generated copy.

Do I need to re-embed the script after bulk edits?

No. The JavaScript snippet remains the same. Once installed, it automatically pulls the latest approved variants from the SeaText edge network.

What happens if I edit a product description in Odoo?

SeaText detects the updated content on the next page view. It will automatically generate new variants for the updated text, and existing variants for the old copy will be archived.

Can I export all SeaText variants for an audit?

The dashboard allows for filtered views and bulk actions. For a full export of all variants, contact SeaText support for assistance with your specific account data.

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

Yes. Each Odoo website requires its own SeaText account, as each account is linked to a single primary URL. Install the unique snippet provided for each site separately.

Is there a way to pause all tests across the site at once?

Yes. In the SeaText dashboard, filter by your domain, select all variants, and choose "Pause test" from the bulk-action toolbar.

Show the SeaText Block Only on Mobile in Odoo

If you want the SeaText AI block to appear only on mobile devices (phones) and not on tablets or desktops, Odoo's website builder gives you a straightforward way to do that. The key is to use the visibility options available when you place the SeaText embed code block.

Prerequisites

• A SEATEXT AI account – you need to create one and copy the JavaScript code snippet provided.
• Access to your Odoo website's Website module with editing rights.
• Odoo version 16 or later (the visibility options are available in recent versions).

Step-by-Step: Show SeaText Only on Mobile Using Odoo's Visibility Settings

1. Log in to your Odoo account and go to the Website module.
2. Edit the page where you want the SeaText block. Click the “Edit” button on the top right.
3. In the editing panel, scroll through the “Blocks” panel until you find the “Dynamic Content” section.
4. Drag the “Embed Code” block into the desired location on your page.
5. Click “Edit” on the placed block. A pop-up window appears.
6. Paste the SeaText JavaScript code into the code area, then click “Save”.
7. Set visibility to mobile only:
   • In the block's settings, find the “Visibility” section.
   • Select “Hide on Desktop” – this hides the block on computers but keeps it visible on tablets and phones.
   • To show only on mobile phones, also select “Hide on Tablet” (if available). If the option is not present, you can combine with a CSS media query (see alternative below).
8. Click “Save” again to apply the changes.
9. Test on mobile: Open the page on a phone, tablet, and desktop. On mobile you should see the SeaText block; on desktop and tablet it should be hidden.

Alternative: Using CSS Media Queries

If you need more control, you can add custom CSS to the page or to the block. For example, you can wrap the SeaText block in a div with a class like mobile-only and then add this CSS in your theme's custom styles:

@media (min-width: 768px) { .mobile-only { display: none; } }

This hides the block on screens wider than 768px (tablets and desktops). You can adjust the breakpoint as needed.

Common Mistake to Avoid

Forgetting to clear the website cache after making visibility changes. Odoo caches pages for performance, so your mobile visitors may still see the block on desktop if the cache isn't cleared. Always refresh the page or use Odoo's “Clear Cache” option in the Website settings after updating visibility.

Understanding Device-Based Visibility

Odoo's website builder allows you to control the visibility of any block based on the visitor's device type: mobile, tablet, or computer. This is available in the block's settings under “Visibility”. The options are straightforward: “Show on Mobile”, “Show on Tablet”, “Show on Computer”, or a combination of hide/show. By using these, you can tailor the content to specific screen sizes without writing any code.

Why Mobile-Only Visibility Matters

Mobile traffic often accounts for over half of website visits. Showing a dynamic AI block like SeaText only on mobile can improve the user experience on larger screens where the same content might be distracting. It also helps you focus mobile-specific features such as a chat widget or a simplified CTA. Ignoring device visibility can lead to cluttered layouts on desktop or missing functionality on mobile, hurting conversion rates.

Limitations and Considerations

• Tablet ambiguity: Odoo's built-in “Hide on Desktop” alone does not distinguish between tablet and phone. You may need to use CSS or additional options to isolate mobile phones.
• Cache: As mentioned, always test after clearing the cache.
• Development URLs: SeaText does not work on localhost or dynamic development domains. Use a real domain for testing.
• Multiple domains: Each domain requires a separate SeaText account.

Key Facts

Frequently Asked Questions

Can I show the SeaText block only on mobile phones (not tablets)?

Yes, either by selecting both “Hide on Desktop” and “Hide on Tablet” in Odoo's visibility settings (if available) or by using a CSS media query with a breakpoint around 768px. Test on actual devices to confirm.

Do I need to edit the code for visibility?

No, Odoo's built-in visibility options work without touching the code. You only need to paste the SeaText snippet once.

What if the “Hide on Tablet” option is missing?

Some Odoo versions may not have a separate tablet option. In that case, use the CSS media query method to hide the block on screens wider than 768px.

Will the SeaText block still work on mobile if hidden on desktop?

Yes, the block remains active on mobile. The JavaScript runs only when the block is visible, so it will function normally on mobile devices.

How do I test the visibility before going live?

Use your browser's developer tools to simulate mobile viewports. Also check on a real phone and tablet to be sure. Clear Odoo's cache after each change.

Does SeaText provide any built-in visibility options?

No, SeaText relies on the hosting platform's visibility controls. In Odoo, you use the native block visibility settings.

When integrating SeaText into an Odoo website, you may find that certain AI agents—such as conversion relays, translation engines, or intent amplifiers—are better suited for mobile users than desktop visitors. Odoo provides a native "Hide on Desktop" feature, but understanding the difference between visual suppression and full script removal is critical for performance and data accuracy.

Understanding the Mechanics of "Hide on Desktop"

The "Hide on Desktop" setting in Odoo is a CSS-based visibility toggle. When you select this option in the Embed Code block's Visibility panel, Odoo applies a display: none style to the container at desktop breakpoints. While the element is invisible to the user, the browser still downloads the associated JavaScript snippet. Because the script is still present in the Document Object Model (DOM), it initializes and executes its core functions.

This approach is ideal for rapid prototyping. If you are running an A/B test or need to quickly toggle the visibility of a chat agent or translation tool without modifying your site's underlying theme or page structure, this is the most efficient path. However, it does not reduce the browser's processing load or the number of network requests generated by the SeaText script.

Why Disabling the Integration Matters for Performance

If your primary goal is to improve Core Web Vitals or reduce third-party script weight, hiding the block is insufficient. Every script loaded on a page contributes to Total Blocking Time (TBT) and increases the number of network requests. By disabling the integration entirely on desktop, you remove the SeaText JavaScript file from the critical path of the desktop page load.

This is particularly important for sites on metered API plans. If your SeaText account tracks agent executions or API calls per page view, a hidden block will still generate these calls as long as the script is active. Disabling the block at the layout level ensures that your API quota is reserved exclusively for the traffic segments where you want the AI agents to operate, such as mobile users.

Decision Criteria: When to Choose Each Strategy

Choosing the right strategy requires balancing operational convenience against technical optimization. Use the "Hide on Desktop" toggle if you are in a development phase, frequently changing your site layout, or need to maintain a consistent codebase across devices. It is a low-friction solution that keeps your configuration centralized within the Odoo editor.

Conversely, choose to disable the integration if you are conducting a performance audit or managing high-traffic sites where every millisecond of load time counts. If you notice that desktop sessions are skewing your conversion data or if you are hitting API rate limits, removing the block from the desktop layout is the only way to achieve a clean, zero-impact baseline.

Practical Scenarios for Implementation

Consider a scenario where you use the SeaText Translation Agent to reach international mobile users. You might want this active on mobile but prefer a native, non-AI experience on desktop. In this case, simply hiding the block might still trigger translation telemetry on desktop, potentially confusing your analytics. By creating a mobile-specific layout that includes the Embed Code block and a separate desktop layout that excludes it, you ensure that the translation agent only interacts with the intended audience.

This segmentation also helps with attribution. When the script is absent on desktop, your analytics tools will not register SeaText-related events for those users. This provides a clearer view of how your site performs without AI intervention, allowing you to compare the conversion rates of mobile users (with SeaText) against desktop users (without SeaText) more accurately.

Limitations and Technical Considerations

The main limitation of the "Hide on Desktop" setting is its inability to gate background processes. Many SeaText agents, such as the Conversion Relay (CAPI) or Intent Amplifier, operate in the background. Even if the visual component (like a chat bubble) is hidden, the script may still attempt to communicate with SeaText servers. If you require absolute silence on desktop, you must ensure the script is not present in the page source.

Additionally, Odoo's block system is page-specific. If you decide to disable the integration, you must repeat the process for every page where the block exists. While this requires more effort than a global toggle, it offers granular control. You can keep SeaText active on high-converting landing pages while disabling it on informational blog posts, tailoring the experience to specific user intents.

Frequently Asked Questions

Does "Hide on Desktop" stop SeaText from tracking desktop visitors?

No. The script still loads and can fire telemetry, CAPI events, or bot-detection calls. Only removing the block from the desktop layout stops those calls.

Can I conditionally load the SeaText script based on screen width in Odoo?

Odoo does not expose a native "load script only on mobile" toggle for Embed Code blocks. You must use separate desktop/mobile layouts or a custom theme hook to achieve true conditional loading.

Will hiding the block affect my SeaText billing or API quota?

If your plan counts API calls or agent executions per page view, hidden desktop blocks still generate those calls. Disabling the block on desktop is the only way to avoid the charges.

How do I verify the script is not loading on desktop?

Open the page in Chrome DevTools, switch to a desktop user agent, reload, and check the Network tab for the SeaText JavaScript file. It should be absent if you disabled the block correctly.

Can I keep SeaText active on desktop for some pages only?

Yes. Apply the "Hide on Desktop" toggle or layout removal page-by-page. Odoo's block system is per-page, so you can mix strategies across your site.

What happens to SeaText's translation or SEO agents if I disable on desktop?

Those agents only run where the script loads. Disabling on desktop means desktop visitors won't see translated content or AI-generated FAQ pages from SeaText. Mobile visitors are unaffected.

Finding the CSS Selector for Your SeaText Block in Odoo

You can find the CSS selector by right-clicking the SeaText block in your browser, selecting 'Inspect', and identifying the unique class or ID assigned to the widget container.

Start with the Symptom: You Can't Find the Selector

You've placed the SeaText block on your Odoo page. Now you want to style it. But when you look at the HTML, you see a mess of nested divs and generic classes. Nothing seems to say "SeaText." This is a common problem. Odoo wraps third-party widgets in its own structure. The SeaText code snippet sits inside an "Embed Code" module. That module adds its own classes and IDs. The actual SeaText widget might be buried several levels deep.

Don't guess. Guessing leads to broken styles and wasted time. Use a diagnostic sequence instead. This sequence moves from the symptom to the solution in a logical order.

Step 1: Inspect the Block in Your Browser

Open your Odoo page in a browser. Make sure the SeaText block is visible. Right-click directly on the SeaText block. Select "Inspect" or "Inspect Element" from the context menu. This opens the developer tools panel. The panel highlights the HTML element you clicked on.

Look at the highlighted line in the Elements tab. That line is the starting point. It might be a div, a span, or another tag. This is the element that contains the SeaText widget.

Step 2: Identify the Widget Container

The highlighted element might not be the SeaText container itself. It could be a child element inside it. Look at the parent elements in the tree. Expand the HTML structure by clicking the arrows next to each tag. Search for a class or ID that includes "seatext" or "sea-text." SeaText typically adds a unique class to its main container. Common examples include .seatext-ai-widget or .seatext-container.

If you don't see a class with "seatext" in it, look for a unique ID. The SeaText integration script often generates a random ID for each widget instance. This ID looks like id="seatext-widget-abc123". This ID is the most reliable selector because it's unique to that specific block.

Step 3: Test the Selector in the Console

Once you have a candidate selector, test it. Switch to the Console tab in developer tools. Type the following command:

document.querySelector('.your-candidate-class')

Replace .your-candidate-class with the class or ID you found. If the command returns the SeaText element, your selector is correct. If it returns null, the selector is wrong. Try a different class or ID.

You can also test multiple selectors at once. Use the comma operator:

document.querySelectorAll('.seatext-ai-widget, .seatext-container, #seatext-widget-abc123')

This returns all elements matching any of those selectors. Check the results to see which one targets your SeaText block.

Step 4: Choose Between ID and Class Selectors

IDs and classes have different strengths and weaknesses. Understanding these trade-offs helps you pick the right one.

ID selectors are unique. They target exactly one element on the page. This makes them very specific. But IDs can change. If SeaText regenerates the ID during an update, your CSS breaks. IDs are also harder to reuse if you have multiple SeaText blocks on the same page.

Class selectors can target multiple elements. This is useful if you have several SeaText blocks and want to style them all the same way. Classes are more stable than IDs because they don't change as often. But classes can be less specific. A class like .seatext-container might also be used by other widgets.

For most cases, use the class selector. It's more stable and reusable. Use the ID selector only if you need to style one specific block differently from others.

Step 5: Handle Specificity Issues

Odoo has its own CSS. That CSS might override your custom styles. This is a specificity problem. Specificity determines which CSS rule wins when multiple rules target the same element.

Odoo's default styles often use high-specificity selectors. For example, Odoo might use .o_website .s_seatext_block .seatext-container. Your simple selector .seatext-container has lower specificity. Odoo's rule wins.

To fix this, increase the specificity of your selector. Add a parent element to your selector. For example:

.o_website .seatext-container {
    background-color: #f0f0f0;
}

This selector has higher specificity than .seatext-container alone. You can also use !important as a last resort. But use it sparingly. !important makes your CSS harder to maintain and can cause unexpected side effects.

Step 6: Apply Custom CSS in Odoo

Now that you have the selector, you need to apply your CSS. Odoo provides several ways to add custom CSS.

Theme Customization: Go to your Odoo backend. Navigate to Website > Customize. Look for a "Custom CSS" or "Custom Code" section. Paste your CSS there. This method works for most Odoo versions.

Custom Theme: If you're developing a custom Odoo theme, add a CSS file to your theme's assets. This gives you more control but requires more technical knowledge.

Website Editor: In the Odoo website editor, you can sometimes add custom CSS through the "Customize" panel. Look for an option to add custom code or styles.

After adding your CSS, save your changes. Refresh your Odoo page. Check if the styles apply correctly.

Troubleshooting: Why Your Styles Aren't Working

If your styles don't apply, work through this checklist.

• Check for typos: Compare your selector to the one in the inspector. Even one missing character breaks the selector.
• Check specificity: Your selector might be too weak. Increase specificity by adding parent elements.
• Check caching: Clear your browser cache. Also clear Odoo's cache. Odoo caches CSS aggressively. You might be seeing an old version.
• Check the element: Verify the SeaText block is actually loaded. If the block isn't visible, the selector won't match anything.
• Check for JavaScript errors: Open the Console tab. Look for red error messages. JavaScript errors can prevent the SeaText widget from rendering.

Limitations: Selectors Can Change

CSS selectors are not permanent. They depend on the HTML structure. Odoo updates can change that structure. SeaText updates can also change the classes and IDs it uses.

If your custom styles stop working after an update, re-inspect the element. The selector might have changed. You'll need to find the new selector and update your CSS.

Also, be careful with aggressive styling. Don't hide critical elements or change the layout too drastically. Overly aggressive CSS can break the SeaText widget's functionality. The widget needs its container to render properly. If you hide the container, the widget disappears.

Practical Scenario: Styling a SeaText Block

Let's walk through a real example. You have a SeaText block on your Odoo homepage. You want to change its background color to light gray and add some padding.

First, right-click on the SeaText block. Select "Inspect." The developer tools highlight a div. Look at its classes. You see class="seatext-ai-widget". This is your selector.

Test it in the console:

document.querySelector('.seatext-ai-widget')

The console returns the element. Your selector works.

Now add your CSS to Odoo's custom CSS section:

.seatext-ai-widget {
    background-color: #f0f0f0;
    padding: 20px;
    border-radius: 8px;
}

Save and refresh. The SeaText block now has a light gray background with padding and rounded corners.

Frequently Asked Questions

What if I can't find a unique ID or class for the SeaText block?

If no direct ID or class is obvious, use a more complex selector. Target a parent element that contains the SeaText widget. Then select the child element. For example, if SeaText is always inside a div with class .o_record_content, use .o_record_content .seatext-widget. This compound selector targets the SeaText widget only when it's inside that specific parent.

Can I hide the SeaText block on mobile devices using CSS?

Yes. Odoo offers built-in visibility settings like "Hide on Desktop." You can also use CSS media queries. To hide the block on mobile, add this CSS:

@media (max-width: 767px) {
    .seatext-ai-widget {
        display: none;
    }
}

This hides the block on screens smaller than 768 pixels wide.

How do I add custom CSS to my Odoo website?

The method varies by Odoo version and theme. Generally, you can access theme options in the Odoo backend. Look for a "Custom CSS" field. If you're developing a custom theme, include a CSS file in your theme's assets. Check Odoo's documentation for your specific version.

What is the difference between an ID selector and a class selector?

An ID selector (e.g., #my-id) targets a single, unique element on a page. A class selector (e.g., .my-class) can target multiple elements that share the same class. IDs should be unique. Classes can be reused.

Will Odoo updates break my custom CSS selectors?

It's possible. If Odoo or the SeaText integration updates its HTML structure, your selectors might no longer apply. Regularly check your website after updates. Re-inspect elements if styles break.

How do I integrate SeaText with Odoo if I haven't yet?

First, create a SEATEXT AI account. Each domain needs its own account. Then log in to your Odoo account. Access the Website module. Navigate to the page you want to edit. Click "Edit" to open the editing panel. Scroll through the "Blocks" panel to the "Dynamic Content" section. Locate the "Embed Code" module. Drag it into the desired location. Click "Edit" on the module. Paste the SeaText code snippet into the pop-up window. Click "Save." If you want to hide the block on desktop, select the "Hide on Desktop" option in the "Visibility" section. Click "Save" again.

Next Steps: Apply Your Styling or Integrate SeaText

Now you know how to find the CSS selector. You can apply custom styling to your SeaText block. Use the diagnostic sequence to identify the right selector. Test it in the console. Then add your CSS to Odoo.

If you haven't integrated SeaText yet, follow the integration steps. Create a SEATEXT AI account. Use the "Embed Code" module in Odoo's "Dynamic Content" section. Paste the code snippet. Configure visibility settings as needed. Then use your new selector skills to style the block.

SeaText helps you convert more visitors. Custom styling makes the widget fit your brand. Start with the selector. Then make it look great.

Why Script Placement Matters in Odoo

Where you place the SeaText script determines when it loads relative to your page content. Scripts loaded late may miss early user interactions or fire after critical rendering decisions. In Odoo specifically, the section of your website's main layout template is the most reliable location.

If SeaText loads after the page content has already rendered, it may not properly track visitor behavior or apply its copy changes at the right moment. This can reduce the effectiveness of features like reading telemetry and real-time copy optimization.

SeaText's reading telemetry measures eye-line dwell velocity, friction points, and scroll deceleration. These metrics depend on capturing visitor behavior from the very first millisecond. A script that loads late misses the initial scan of your headline and hero section. That data loss is permanent and cannot be recovered later.

Placement also affects how SeaText applies copy changes. If the script initializes after the page renders, visitors may see the original copy first, then a sudden swap. This creates a flash effect that looks unprofessional and can confuse buyers. Early placement prevents this by letting SeaText prepare changes before the page becomes visible.

How SeaText Works and Why Timing Matters

SeaText is not a simple analytics tag. It is an autonomous AI agent that reads visitor behavior in real time. The script observes how quickly visitors scan headlines versus deeply comprehend value propositions. It tracks sections where visitors repeatedly backtrack or pause, indicating confusing phrasing or vague claims. It also measures scroll deceleration to find the exact page coordinates where buying interest spikes before CTA exposure.

All of this happens at millisecond-level precision. The script needs to be present before the first paint of your page. If it loads even 500 milliseconds late, it misses the critical first impression window. Visitors decide whether to stay or leave within seconds. Late-loading scripts simply cannot capture that decision process.

SeaText also uses adaptive multi-armed bandit algorithms to allocate traffic to top-performing copy variants. Instead of a rigid 50/50 split, it sends 80% or more of visitors to the winning variant within hours. This optimization only works if the script sees every visitor from the start. A late script creates blind spots where visitors receive unoptimized copy without contributing data.

Where the Script Actually Goes in Odoo

The section sits in your website's main layout template. In Odoo 14 and later versions, you can access this through the Website module's editor or by editing the XML template directly if you have developer access.

Navigate to Website > Customize > Theme Settings or use the Settings > Website > Head HTML option depending on your Odoo version. Paste the SeaText script tag in the Custom JavaScript or Script Injection field.

If you use the visual editor instead, drag the Embed Code block from the Dynamic Content section into your page layout, paste the SeaText code there, then set the block to Hide on Desktop so it doesn't display visibly on your pages.

The Embed Code block method is the officially documented approach in SeaText's Odoo integration guide. It works reliably across all Odoo versions with the website editor. However, head placement is technically superior because it loads before the page body renders.

Step-by-Step: Adding SeaText to Odoo's Head Section

Follow these steps to place the script correctly:

1. Log in to your Odoo account and open the Website module from the dashboard.
2. Go to Settings > Website > HTML Head or access the theme template directly.
3. Locate the custom scripts or footer section in your website's layout.
4. Paste the SeaText script tag provided in your SeaText dashboard.
5. Save the changes and refresh your website.

Alternatively, use the visual editor: open any page in edit mode, find the Embed Code block in the Dynamic Content section, drag it onto your page, paste the SeaText code, and hide the block from desktop visibility.

For the Embed Code method, click the Edit button in the right panel after placing the module. A pop-up window appears where you paste the code snippet. Click Save to apply. Then select Hide on Desktop in the Visibility section and save again.

What Happens If You Place It Incorrectly

Placing the script in the footer, inside a content block, or after your main page content causes problems. The script initializes late, meaning it misses the first few seconds of visitor behavior. Reading velocity metrics become inaccurate, and real-time copy changes may flash or apply after the visitor has already scrolled past the relevant section.

In Odoo specifically, content blocks render dynamically through the website editor. If you place the script inside a block that only appears on certain pages, SeaText won't initialize on pages where that block is absent. This creates inconsistent tracking and incomplete optimization data.

Footer placement is the most common mistake. Many developers default to footer scripts because they believe it improves page speed. For SeaText, this is counterproductive. The script is designed to load asynchronously and should not block rendering. Placing it in the head gives you the best of both worlds: early initialization without performance penalty.

Per-page placement is only acceptable for testing. If you want to validate SeaText on a single landing page before rolling it out site-wide, placing the script only on that page is fine. But for production, you need global placement across all pages.

Key Facts: SeaText Script Placement in Odoo

Testing Your Installation

After placing the script, verify it loads correctly. Open your browser's developer console (F12), go to the Network tab, and reload your Odoo page. Search for the SeaText script filename or domain in the request list.

You should see the script load early in the waterfall, before your main CSS and content blocks. Check the Console tab for any JavaScript errors related to SeaText. If SeaText's dashboard shows active sessions, the installation is working.

Run a quick test by visiting your page with an incognito window. Watch the SeaText dashboard for a new session to appear within seconds. If you see the session, the script is capturing data correctly. If not, check your placement and ensure the script is not blocked by any content security policy.

Also verify that the script loads on every page, not just the homepage. Navigate to a product page, a blog post, and your contact page. Each should show a new session in the dashboard. If any page is missing, the script is likely placed in a page-specific block rather than the global layout.

When the Head Section Is Not Available

Some Odoo configurations restrict access to the theme template, especially on shared hosting or managed Odoo.sh instances. In these cases, the Embed Code block method is the next best option. Place the block in your main layout footer or in a snippet that appears on every page.

If you cannot access either option, contact your Odoo administrator or hosting provider. They may need to add the script to the server-side template files.

For the Embed Code method, place the block in a location that appears on every page. The footer area of your main layout is a common choice. Even though it loads later than the head, it still captures most visitor behavior because the script initializes before most users scroll down.

If your hosting provider restricts all template access, ask them to add the script to the server-side template. This is a one-time change that ensures global placement. Most Odoo hosting providers can do this quickly if you provide them with the script tag.

SeaText Multiple Domain Considerations

If you run separate Odoo instances for development and production, each domain requires its own SeaText account. SeaText accounts are linked to a single primary URL for security. Development URLs like localhost are restricted. Use real, public domains for each SeaText installation.

Dynamic development domains may not function properly. SeaText might be unable to reliably associate traffic with your account. This can lead to inaccurate telemetry data and failed copy optimization.

For staging environments, use a real subdomain like staging.yourcompany.com. Create a separate SeaText account for that subdomain. This ensures your staging tests do not pollute your production data.

If you have multiple websites, create one account for each website. Do not try to share a single account across domains. The security model prevents this, and it would also mix your data in ways that make optimization impossible.

FAQ

Can I place the SeaText script in Odoo's footer instead of the head?

You can, but it is not recommended. Scripts in the footer load after the page content renders, which can cause delayed initialization and missed tracking data. The script may miss the first few seconds of visitor behavior, including the critical decision to stay or leave.

Does the Embed Code block method work as well as head placement?

It works, but head placement is slightly better for performance. The Embed Code block loads as part of your page content, which may be a fraction of a second later than the head section. For most sites, this difference is negligible. But if you want maximum accuracy in reading telemetry, head placement is the best choice.

How do I hide the Embed Code block from showing on my pages?

In the block's visibility settings, select Hide on Desktop and optionally Hide on Mobile to prevent the block from displaying visibly while keeping the script active. This is the officially documented method in SeaText's Odoo integration guide.

Will SeaText slow down my Odoo website?

SeaText is designed to load asynchronously and should not significantly impact page load times. Placing it in the head section ensures it initializes cleanly without blocking rendering. The script is lightweight and does not add noticeable latency to your pages.

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

Yes. Each SeaText account is tied to one primary domain. For multiple Odoo instances or subdomains, create separate accounts. This is a security requirement that also ensures your data stays clean and accurate.

What if my Odoo hosting provider restricts template access?

Use the Embed Code block method in the website editor. If that is also restricted, ask your hosting provider to add the script to the server template. This is a one-time change that ensures global placement across all pages.

Can I test the script on a staging domain before going live?

SeaText restricts localhost and non-public domains for security reasons. Use a staging subdomain with a real, public URL and create a separate SeaText account for it. This ensures your staging tests do not interfere with production data.

How quickly will I see results after installing SeaText?

SeaText begins collecting reading telemetry immediately after installation. The AI needs some time to gather enough data to generate copy variants. Within hours, the adaptive multi-armed bandit algorithm starts allocating more traffic to top-performing variants. Most users see measurable improvements within the first week.

What if I have multiple Odoo websites on different domains?

Create a separate SeaText account for each website. Each account is linked to a single primary URL. This ensures accurate tracking and prevents data mixing between your sites.

How SeaText Impacts Odoo Page Load Speed

SeaText is designed to be lightweight, so the impact on page load speed is minimal when implemented correctly. Proper placement in the section prevents the script from blocking critical rendering, meaning your visitors see content before SeaText initializes. The script remains inert until a visitor interacts, so it does not add processing overhead during initial page load.

Any external JavaScript will have some effect on load times because the browser must download and parse the code. The practical impact depends on three factors: the script file size, where it loads in the page sequence, and your server response time. SeaText accounts for these by staying dormant until needed, rather than running continuously.

Why Scripts Normally Slow Down Pages

When a browser encounters a JavaScript file during page load, it typically pauses rendering to download and execute the code. This is called render-blocking. If a script is large or served slowly, the visitor sees a blank or incomplete page while waiting.

Modern browsers handle scripts more efficiently than in the past. Techniques like async loading allow the page to continue rendering while the script downloads. The defer attribute tells the browser to wait until the HTML is fully parsed before running the script. These methods reduce the visible impact on load speed.

External scripts also add DNS lookups, TCP connections, and TLS handshakes if served from a different domain. These network steps introduce small delays that add up across multiple scripts. Minimizing external script dependencies helps keep load times fast.

What Makes SeaText Different

SeaText remains inactive until a visitor takes a specific action, such as moving a mouse, scrolling past a certain point, or spending time on a page. This lazy activation means the script does not consume browser resources during the initial load sequence. The visitor sees your content immediately.

The installation process hides the SeaText block on desktop by default, so it does not affect layout or rendering. Per SeaText's Odoo integration guide (S1), you select the "Hide on Desktop" option in the Visibility section after placing the Embed Code module. This keeps the script out of the visible page structure.

Because the AI activates only when engaged, it does not interfere with Core Web Vitals metrics that measure first impressions. Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift focus on the initial rendering experience, which SeaText does not touch.

Measuring the Actual Impact on Your Odoo Site

Before and after installing SeaText, run your Odoo website through a performance testing tool like Google PageSpeed Insights or WebPageTest. Record these key metrics:

• Time to First Byte (TTFB): How quickly your server responds to a request
• Largest Contentful Paint (LCP): When the main content appears
• Total Blocking Time (TBT): How long the page is unresponsive during load
• Page weight: The total size of all resources downloaded

Compare the before and after numbers. If LCP stays within 200 milliseconds of the original value, the impact is negligible. A small increase in TBT may occur if SeaText loads synchronously, but this typically affects only low-end mobile devices on slow connections.

If you notice significant slowdowns, check where the Embed Code block sits in your page structure. Placing it lower in the layout or using async loading can help. Avoid wrapping SeaText in heavy containers or loading it inside images or videos.

Optimization Tips for Fast Odoo Pages

Even with SeaText installed, you can keep your Odoo website running fast. These practices help minimize any script impact:

• Use a Content Delivery Network (CDN) to serve static assets from locations near your visitors
• Enable browser caching for images, CSS, and JavaScript files
• Compress images before uploading them to your Odoo media library
• Limit the number of third-party scripts running on the same page
• Monitor your Odoo hosting performance and upgrade if TTFB exceeds 600 milliseconds

Odoo's built-in optimizer handles many of these automatically. Check the Website module settings to ensure asset compression and minification are enabled. These settings reduce file sizes without changing how the site looks or functions.

When Performance Concerns Are Valid

In rare cases, script loading does affect user experience noticeably. This typically happens when the external server is slow, the script contains blocking operations, or the page already carries heavy resources from other sources.

If your Odoo site runs on shared hosting with limited resources, adding any external script may compound existing slowdowns. The solution is not necessarily avoiding SeaText, but improving your overall hosting setup. Dedicated or cloud hosting often resolves these baseline performance issues.

Pages with extensive customizations, third-party themes, or large media libraries may have less tolerance for additional scripts. In these cases, test thoroughly in a staging environment before deploying to production. Measure load times on both desktop and mobile to catch any edge cases.

Key Facts About SeaText Integration

Frequently Asked Questions

Does SeaText slow down mobile users more than desktop users?

Mobile devices have less processing power and often rely on slower network connections. Any script, including SeaText, may have slightly more impact on mobile. However, because SeaText activates lazily, the initial page render remains fast on both devices.

Can I remove SeaText if it causes problems?

Yes. Simply delete the Embed Code block from your Odoo page editor and save the changes. The removal takes effect immediately with no lasting impact on your site.

Will SeaText affect my Google search rankings?

Search engines measure page experience partly through Core Web Vitals. Since SeaText does not block rendering and activates only after user interaction, it should not negatively affect your metrics. Fast-loading pages still rank better, so maintain your existing optimization practices.

Does the position of the Embed Code block matter?

For SeaText specifically, the block's visual position does not affect performance because the script is hidden by default. However, placing the block lower in the page structure can help if you notice loading issues with other scripts.

How do I test if SeaText is causing slowdowns?

Use Google PageSpeed Insights before and after installing SeaText. Compare the Largest Contentful Paint and Total Blocking Time numbers. If LCP increases by more than 200 milliseconds, investigate further by checking your browser console for errors and your network tab for slow resource loads.

Does SeaText work with Odoo Shard/Cloud hosting?

SeaText integrates with any Odoo deployment that allows custom script injection through the Website module. Cloud-hosted Odoo instances typically handle external scripts well due to their optimized infrastructure.

What happens if my visitor has JavaScript disabled?

SeaText requires JavaScript to function, much like Odoo itself. Visitors without JavaScript will not see the SeaText interaction features, but they can still browse and use your site normally.

Why Odoo Version Compatibility Matters

If you run an older or heavily customized Odoo instance, assuming compatibility without checking can lead to broken layouts or missing AI features. SeaText AI agents operate by injecting real-time JavaScript into your live DOM (Document Object Model). If your Odoo version has a different layout structure or if custom themes override the standard block editor, the snippet might not load correctly. Ignoring version checks means you risk deploying code that either does nothing or causes JavaScript errors that disrupt the user experience for your visitors.

How the SeaText Snippet Works in Odoo

The technical mechanism is straightforward. SeaText does not require you to modify Odoo Python source files, write custom modules, or alter your database schema. Instead, it uses the "Embed Code" module, which is a standard feature in the Odoo Website application. This module allows you to inject raw HTML, CSS, and JavaScript directly into a page. When you paste the SeaText snippet, it loads asynchronously in the browser. The AI remains inert until activated by user interaction or specific trigger conditions, ensuring your website core performance is preserved.

Installation Requirements and Readiness Checklist

Before you begin, verify that your environment meets these prerequisites. Each item is required for a successful installation.

• Active Website module installed and enabled in your Odoo instance.
• Access to the "Embed Code" block within the "Dynamic Content" section of the block library.
• A valid primary domain registered to your SeaText account (not localhost).
• The target URL is a real, publicly accessible domain (dynamic development domains may not function properly).
• Editor permissions to edit pages and save block changes in the Website module.
• If you need the block hidden on desktop, confirm the "Hide on Desktop" visibility option is available in your version.

Step-by-Step Installation on Odoo

To install SeaText on your Odoo website, follow these steps:

1. Log in to your Odoo dashboard and open the "Website" module.
2. Navigate to the specific page where you want the SeaText AI to appear and click the "Edit" button.
3. In the editing panel, look for the "Blocks" panel on the right side and scroll down to the "Dynamic Content" section.
4. Locate the "Embed Code" module and drag it to your desired location on the page.
5. Click the "Edit" button on the newly placed module. A pop-up window will appear.
6. Paste the JavaScript code snippet provided by SeaText into the designated area and click "Save".
7. If you want the block hidden on desktop devices, select the "Hide on Desktop" option in the "Visibility" section, then click "Save" again to finalize.

Domain Policy and Development Restrictions

SeaText accounts are tied to a single primary URL. If you need to use the service on multiple domains (such as a development site and a production site), you must create separate SeaText accounts for each domain. Development URLs like "localhost" are restricted for security reasons. The AI may not function reliably on dynamic development domains because it cannot associate traffic with your account. Always use a valid, real domain for testing.

Limitations and Important Considerations

Before installing, be aware of two critical limitations. First, each SeaText account supports only one primary URL. Multiple domains require multiple accounts. Second, localhost and dynamic development URLs are restricted. The AI may not work on these domains because it cannot reliably associate traffic with your account. Use a valid, real domain for testing. If your Odoo theme does not show the Dynamic Content section, the standard block library may be hidden or removed. In this case, consult your developer to ensure the standard block library is active.

FAQ

Can I use one SeaText account for multiple domains?

No. Each SeaText AI account is linked to a single primary URL. If you need to use SeaText AI on multiple domains (e.g., a development domain and a production domain), you must create separate accounts for each domain.

Why does SeaText not work on localhost?

Development URLs such as localhost are restricted for security reasons. Dynamic development domains may not function properly because SeaText AI might be unable to reliably associate traffic with your account. Ensure you use a valid, real domain.

How do I hide the SeaText block on desktop?

After placing the Embed Code module, click the "Edit" button on the module. In the pop-up window, select the "Hide on Desktop" option in the "Visibility" section, then click "Save" to finalize.

What if my Odoo theme does not show the Dynamic Content section?

If you are using a heavily customized theme, the Dynamic Content section might be hidden or removed. You may need to consult your developer to ensure the standard block library is active.

Do I need developer access to install SeaText?

No. The drag-and-drop interface is designed for non-technical users. As long as you have access to the Odoo Website editor, you can paste the code snippet directly.

Direct Answer: Manual Injection Is the Only Supported Path

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

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

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

How the Official Manual Injection Works

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

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

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

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

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

Why No Official Module Exists

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

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

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

When You Might Still Want a Custom Technical Approach

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

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

Key Facts from SeaText's Odoo Integration Guide

Common Mistakes to Avoid

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

Decision Framework: Choose Manual Injection If…

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

Consider a Custom Technical Integration If…

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

FAQ

Does SeaText plan to release an official Odoo module?

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

Can I put the script in a custom theme instead?

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

What happens if I upgrade Odoo from v17 to v18?

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

Can I use one SeaText account for staging and production?

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

Is the script loaded asynchronously?

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

What if my CSP blocks the script?

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

Where do I get the snippet?

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

Can I use SeaText on multiple websites?

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

Is the installation process secure?

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

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

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

Why Verifying SeaText AI Matters

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

Understanding SeaText AI Agents

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

How SeaText Integration Works Under the Hood

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

Step-by-Step Verification Sequence

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

1. Confirm the Embed Block Placement:

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

2. Check Visibility Settings:

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

3. Save and Publish Changes:

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

4. Visit or Refresh the Live Page:

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

5. Open Browser Developer Tools (Network Tab):

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

6. Inspect the Console Tab:

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

7. Log in to Your SeaText Dashboard:

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

8. Test Frontend Behavior:

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

What the SeaText Dashboard Shows

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

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

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

Frontend Signals That Agents Are Running

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

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

Comparison of Verification Methods

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

Common Installation Mistakes on Odoo

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

Limitations and Trade-offs

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

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

Quick answer: compatibility follows the Website module

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

How the integration actually works

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

What to verify in your Odoo instance

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

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

Edition differences: Community vs. Enterprise

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

Hosting and deployment considerations

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

Key facts from the official integration guide

Limitations of the current documentation

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

Decision checklist before you start

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

When to contact SeaText support

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

Frequently asked questions

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

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

Will the integration work on Odoo 17 or 18?

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

Can I use one SeaText account for multiple Odoo websites?

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

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

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

Is there any server-side configuration required?

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

Can I test on a staging site before going live?

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

Direct Answer: No Custom Module Needed

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

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

How the Odoo Integration Actually Works

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

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

Why This Is Not a Custom Module

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

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

Step-by-Step Installation in Odoo

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

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

Common Mistakes and How to Avoid Them

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

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

Key Facts About SeaText AI Odoo Installation

When This Advice Does Not Apply

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

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

Frequently Asked Questions

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

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

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

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

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

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

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

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

Is the SeaText AI script safe to add to Odoo?

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

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

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

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

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

Why the integration code matters

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

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

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

Step 1: Log in to your SeaText account

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

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

Step 2: Open the Odoo integration page

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

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

Step 3: Copy the JavaScript code

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

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

Step 4: Open Odoo's Website editor

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

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

Step 5: Add an Embed Code block

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

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

Step 6: Paste the code and save

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

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

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

Step 7: Verify the integration

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

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

Common mistake: using the wrong account or domain

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

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

What the integration code actually does

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

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

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

Key facts

Limitations and when this advice does not apply

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

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

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

Frequently asked questions

Do I need an API key for Odoo?

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

Where exactly is the code in SeaText?

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

Can I use the same code on two Odoo sites?

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

Why is my code not working on localhost?

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

Do I need to keep the Embed Code block visible?

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

What happens after I paste the code?

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

What if I have multiple websites?

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

Can I test on a staging subdomain?

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

What does the script do before activation?

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

Is the installation process secure?

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

Understanding the Odoo Website Module Structure

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

Step-by-Step: Locating the Embed Code Module

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

Why the Embed Code Module Is the Correct Location

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

Common Variations Across Odoo Versions

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

Verifying the Installation Works

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

Troubleshooting Common Placement Issues

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

Key Facts

Limitations and When This Advice Does Not Apply

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

FAQ

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

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

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

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

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

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

Will the script slow down my page?

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

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

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

Can I use the same snippet on multiple Odoo websites?

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

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

What the installation actually involves

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

Readiness checklist before you start

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

When you might still want technical help

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

How the integration works — scope and mechanics

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

Key facts

Limitations and when this advice does not apply

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

Terminology

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

FAQ

Can I install the snippet on a staging domain first?

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

What happens if I paste the snippet on multiple pages?

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

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

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

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

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

Will the script slow down my Odoo page load?

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

What if my Odoo theme hides the Dynamic Content section?

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

Expert perspective: why the no-code path works

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

How SeaText can help

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

The Short Answer

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

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

Why This Matters for Your Business

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

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

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

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

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

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

How Multi-Website Setup Works in Odoo

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

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

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

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

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

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

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

How Data Separation Works Technically

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

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

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

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

Practical Scenario: A Business Running Three Odoo Websites

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

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

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

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

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

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

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

Trade-Offs of Multi-Account Setups

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

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

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

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

Development vs. Production Domains

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

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

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

Limitations to Know

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

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

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

Frequently Asked Questions

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

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

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

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

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

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

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

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

Do development and staging environments work with SeaText?

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

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

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

Does SeaText support multi-brand Odoo setups?

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

Next Steps

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

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

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

Quick Answer: The Top Setup Mistakes

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

Why the Odoo Integration Steps Matter

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

Mistake 1: Using the Wrong Code Snippet

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

Mistake 2: Forgetting "Hide on Desktop"

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

Mistake 3: Testing on Localhost or Dynamic Staging URLs

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

Mistake 4: One Account for Multiple Domains

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

Mistake 5: Not Refreshing the Page After Save

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

Mistake 6: Insufficient Odoo User Permissions

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

Mistake 7: Outdated Odoo Module List

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

Diagnostic Checklist When Activation Fails

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

Key Facts at a Glance

Limitations and When This Advice Does Not Apply

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

Terminology

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

FAQ

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

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

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

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

Do I need to paste the snippet on every page?

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

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

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

Does SeaText work on Odoo.sh or Odoo Online?

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

How do I verify the script is active?

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

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

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

Why Odoo permissions matter for SeaText activation

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

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

Readiness Checklist

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

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

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

Understanding Odoo access rights: Administrator vs Settings

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

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

Step‑by‑step: Checking your current Odoo role

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

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

Preparing your Odoo environment for SeaText

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

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

Installing the SeaText embed code in Odoo Website

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

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

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

Verifying activation and troubleshooting common issues

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

Common failure points:

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

Limitations and when this advice does not apply

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

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

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

Key facts at a glance

FAQ

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

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

What if my Odoo admin refuses to grant Administrator rights?

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

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

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

Will the SeaText script slow down my Odoo page load?

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

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

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

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

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