Seatext library

Odoo Data Not Syncing With SeaText? Follow This Diagnostic Checklist

If Odoo website data isn't syncing with SeaText, check the SeaText account domain first, then confirm the embed code is in Odoo's Dynamic Content section, and finally review the block's visibility settings. Use separate...

If Odoo website data isn't syncing with SeaText, run the checks in this order: confirm the SeaText account is linked to the current site URL, confirm the embed code is in Odoo's Dynamic Content > Embed Code block, and confirm the block isn't hidden by the Hide on Desktop setting. If those all pass, check that your Odoo user can edit website pages and that your network isn't blocking the SeaText script.

Use this guide as a diagnostic path, not a list of isolated fixes. Each step below connects to a documented part of SeaText's Odoo integration.

What “not syncing” usually looks like

People describe the problem in different ways:

  • The SeaText chat widget does not load on the Odoo page.
  • Copy that should be rewritten stays the same.
  • A SeaText-powered block appears on staging but not production.
  • The page works in one browser but not another.

Those symptoms often come from a setup mismatch, not from corrupted Odoo data. The fastest way to find the cause is to check the setup pieces in order.

Why SeaText depends on the account URL

Each SeaText account is linked to a single primary URL. This is the most important rule for troubleshooting.

If you have a development domain and a production domain, you need separate accounts for each. Using one account on both is a common mistake. It can make data appear to disappear on one site.

SeaText also restricts development URLs. Localhost is blocked for security. Dynamic development domains may not work because SeaText cannot reliably tie traffic to your account.

Action: log into SeaText, check the primary URL on the account that generated the code, and compare it with the exact URL of your Odoo site, including https and www.

Step-by-step: install the SeaText embed in Odoo

SeaText installs through JavaScript. That JavaScript goes into Odoo's Embed Code module.

  1. Log into Odoo and open the Website module.
  2. Open the page you want to edit and click Edit.
  3. Scroll the Blocks panel to Dynamic Content.
  4. Drag the Embed Code module into the spot you want.
  5. Click the module to open its edit panel.
  6. Paste the JavaScript snippet from SeaText into the pop-up.
  7. Click Save to apply the change.

The source instructions say to log in to Odoo, access the Website module, navigate to the page, and click Edit. Then scroll through the Blocks panel to the Dynamic Content section. Locate the Embed Code module and drag it into place. In the pop-up window, paste the code snippet provided by SeaText AI, then click Save. If you need to hide the block on desktop, select “Hide on Desktop” in the Visibility section and save again.

This process is secure. The AI remains inert until activated. Installing the code alone does not change your content.

Check the embed code placement

A common mistake is pasting the snippet into a text block or an HTML block. It needs the dedicated Embed Code module. If the script is in the wrong block, the page may still look fine, but SeaText never runs.

Another common mistake is pasting code from the wrong account. Use the snippet that came from the SeaText account whose primary URL matches the site.

After you paste the code, save the page. Then view the page in a private browser window to confirm the SeaText element appears.

Check visibility and cache

SeaText's Odoo instructions mention a Visibility section with a Hide on Desktop option. If that option is checked, the block is hidden on desktop devices. If you can't see the SeaText element, check that setting first.

After you change visibility, click Save again. Then test in a private browser window. Odoo pages can be cached, and a cached page may keep serving the old code. If your site uses a CDN or proxy, flush that cache too.

Check Odoo permissions and network rules

If the domain, code, and visibility all look right, the blocker may be outside SeaText.

Check whether your Odoo user has permission to edit the Website app. A read-only user can view a page but cannot apply the embed change. Ask an administrator to confirm your role.

Check network-level blockers too. A strict firewall, ad blocker, or content security policy can stop SeaText's script from loading. Test the page on a different network or with browser extensions disabled.

If you use a third-party SeaText Odoo module, confirm it is up to date. The official integration described here uses Odoo's built-in Embed Code block, so a module update is only relevant if you added one.

Quick diagnostic table

SymptomLikely causeNext step
Works in staging, not on live siteOne account is linked to one primary URLCreate separate SeaText accounts for staging and production
Nothing loads on localhostDevelopment URLs are restrictedUse a valid, real domain
The block never appearsCode is not in the Embed Code moduleDrag Embed Code from Dynamic Content and paste the snippet
The element is missing on desktopHide on Desktop is selectedUncheck it in Visibility and save

Common mistakes that break the sync

  • Using the same SeaText account for two domains.
  • Pasting the code into a text block instead of Embed Code.
  • Leaving “Hide on Desktop” checked.
  • Testing on localhost.
  • Forgetting to save after pasting the code.

Each of these mistakes has a simple fix. The diagnostic table above maps symptoms to causes.

Scope and limitations

SeaText's Odoo integration is a JavaScript embed, not a data pipeline. The installation process is secure, and the AI remains inert until activated. In plain terms, installing the code alone will not change your site content.

This guide covers website data and embed behavior. It does not cover Odoo's internal record sync, such as products or orders moving between Odoo and an external API. That kind of sync has different causes: API credentials, scheduled actions, and server logs. If your error message comes from Odoo's API layer, treat this as a separate issue.

SeaText also warns that dynamic development domains may not function properly. Use a valid, real domain for reliable behavior.

Key facts about SeaText and Odoo

FactWhy it matters
Each SeaText account is linked to a single primary URL.You need separate accounts for separate domains.
Development URLs such as localhost are restricted for security.Test on a real domain instead.
The embed code belongs in the Dynamic Content section.Use Odoo's Embed Code module, not a plain text block.
Hide on Desktop hides the block on desktop devices.Check it when the widget does not appear.
The AI remains inert until activated.Installation alone does not change your content.

FAQ

Why did SeaText work in staging but not production?

Each SeaText account is linked to one primary URL. If both sites share an account, production has no matching account URL. Create separate accounts for each domain.

Can I use localhost for testing SeaText?

No. Development URLs such as localhost are restricted for security reasons. Use a valid, real domain for tests.

I pasted the code but the widget still doesn't show. What now?

Check the account domain, confirm the code is in the Embed Code module, uncheck Hide on Desktop if needed, and clear the cache.

Does SeaText need a separate Odoo module?

The official SeaText integration uses Odoo's built-in Embed Code module. You place SeaText's JavaScript in that module.

Do I need an account before installing?

Yes. SeaText's instructions say you need a SeaText account before you can install the script.

What if my issue is Odoo API record sync, not website data?

This article does not cover that. Check Odoo API credentials, scheduled actions, and server logs instead.

Further reading and comparison sources

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

Further reading and comparison sources

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

Learn more

Visit the website for more information.