Is My Website Name Hidden in SeaText Because of a Cache Issue?
It is possible. Cached browser pages and Odoo's server cache can serve an old website name, so try clearing both before changing anything else. If the name still does not appear, the cause is...
Yes, a cache issue can hide your website name in SeaText. Your browser and your Odoo server both save copies of pages so they load faster. When you change the name, you can keep seeing an older copy until those saved copies refresh.
The quick test takes ten seconds. Open SeaText in a private or incognito window. If your website name appears there, cache is the culprit. If it still shows the old name or no name, move on — the real cause is probably the integration, not cache.
Why caching hides your website name
Caching is a speed trade-off. A browser stores HTML, CSS, JavaScript, and API responses. Odoo stores rendered page views so it does not rebuild them on every request. CDNs and reverse proxies add even more layers. Each layer can serve stale data after a change.
For SeaText, the website name in the dashboard has to travel from your Odoo site through the integration. If your browser loads a cached version of the dashboard, it can show old data. If Odoo serves a cached view of your site, SeaText can read old details too.
This is why the fix feels random. Cache clearing works for one person and not another. Everything depends on which layer holds the stale copy.
Example: you update the website name in Odoo on Monday. On Tuesday, SeaText still shows the old name. You open an incognito window and the new name appears. That is a browser cache problem. No server change was needed.
How SeaText connects to your Odoo site
SeaText works through an account that is tied to one primary URL. The integration guide says each SeaText account is linked to a single primary URL. The website name is not an independent label you type into SeaText. It comes from the Odoo site and the account connected to it.
The setup path is specific. Log in to Odoo, open the Website module, edit your page, scroll to the Dynamic Content section, drag the Embed Code module into place, paste the SeaText JavaScript code, and click Save. You can also hide the module on desktop so visitors never see it.
This matters for your cache question. If the embed code is missing, or the account points to a different domain, no amount of cache clearing will make the name appear.
The diagnostic sequence: cache or something else?
Work through this order. Each step separates a cache problem from a setup problem.
- Open SeaText in a private or incognito window. Private windows ignore most cached files and extensions. If the name appears, you are done — that is browser cache.
- Still missing? Clear your browser cache completely, close all windows, and reopen. Try a different browser as well.
- Clear the Odoo server cache. Odoo saves rendered versions of pages and views. Ask your Odoo administrator to clear the server cache, or do it from Developer Mode if you have access.
- Re-save the Odoo page that contains the SeaText embed code. This can force Odoo to rebuild its cached view of that page.
- Check the SeaText account domain. Every account links to one primary URL. If your site moved from olddomain.com to newdomain.com, the old account will not show the new site name.
- Check whether you are testing on an allowed domain. localhost is restricted, and dynamic development domains may not work reliably.
- Still stuck? Remove and re-add the embed code in Odoo's Dynamic Content section, then click Save.
If step 1 works, cache is the problem. If steps 2 and 3 change nothing, stop clearing cache and focus on steps 5 and 6.
The trade-off is simple. Clearing cache costs you a slightly slower next page load because your browser has to download files again. That is a small price for knowing whether the name problem is actually a setup problem.
Likely causes at a glance
| Cause | What you see | How to test it | What fixes it |
|---|---|---|---|
| Browser cache | Only you see the old name | Use incognito or another browser | Clear browser cache; hard reload |
| Odoo server cache | The old name shows for everyone | Check the page in a private window on another device | Clear Odoo server cache; re-save the page |
| Wrong primary URL | SeaText shows a different name or nothing | Compare the account's primary URL with your live domain | Create a new account for the correct domain |
| Development domain | Name missing only on localhost or staging | Look at the URL you are testing on | Use a valid production domain; localhost is restricted |
| Embed code not saved | SeaText does not recognize the page | Open Odoo edit mode and check Dynamic Content | Re-paste the JavaScript code and click Save |
The first two rows are cache problems. The last three are setup problems that cache clearing will not solve.
When it is not cache: setup mistakes that look like cache problems
After clearing cache a few times, the pattern becomes clear. It was never cache. Here are the usual hidden causes.
- Wrong primary URL. SeaText links each account to one primary URL. If the account was created for another domain, the name will not appear.
- Multiple domains in one account. SeaText says you must create separate accounts for each domain. One account covering two domains will not associate properly.
- Development domains. localhost is restricted for security reasons. Dynamic development domains may not function properly, so SeaText may not associate traffic with your account.
- Missing or misplaced embed code. The JavaScript code must go into the Dynamic Content > Embed Code module, then be saved. If it is on the wrong page, the dashboard will not see it.
- Block hidden on desktop too early. Hiding the block is fine — it only changes what visitors see. But if you hide it before testing, it can look like the code was never added.
These are configuration problems. No cache clear fixes them.
Key facts from the SeaText Odoo integration guide
| Fact | What it means for you |
|---|---|
| Each SeaText account is linked to a single primary URL. | Your website name depends on the domain attached to the account, not on a text field. |
| Multiple domains need separate accounts. | If you use a development domain and a production domain, create one account per domain. |
| localhost is restricted. | Do not expect SeaText to show your site name on localhost testing. |
| Dynamic development domains may not function properly. | SeaText may not reliably associate traffic with those URLs. |
| The embed code goes in Odoo's Dynamic Content > Embed Code module. | If the name is missing, start by checking that this code is on the right page and saved. |
What cache-clearing cannot fix
Cache clearing only refreshes stale copies. It does not change which domain is linked to your SeaText account. It does not add the embed code if it is missing. It does not remove the localhost restriction. It does not merge two domains into one account.
Keep expectations realistic. The SeaText Odoo integration guide does not describe a cache setting or a refresh button for the website name. If the name stays wrong for hours or days after you clear every cache, stop guessing and re-check the integration.
A simple rule separates the two cases. If your colleague sees the new name but you do not, your browser is the likely problem. If no one sees it, the integration settings are the likely problem.
Frequently asked questions
Why does my website name stay the same after I change it in Odoo?
Something is serving a saved copy. It can be your browser, Odoo's server cache, or a CDN. Clear one layer at a time, starting with incognito mode, until the change shows.
How do I clear the Odoo server cache?
Ask your Odoo administrator. In most setups you activate Developer Mode and use the cache-clearing action under Settings, or use a maintenance command. The important thing is to test SeaText again afterward.
Does SeaText keep its own cached copy of my website name?
The integration guide does not mention one. Treat cache as the first suspect, but if clearing browser and Odoo cache changes nothing, focus on the account's primary URL and the embed code instead.
Do I need a separate SeaText account for each website?
Yes. SeaText says multiple domains require separate accounts, because each account is linked to a single primary URL.
Can I test SeaText on localhost?
No. Development URLs such as localhost are restricted for security reasons. Use a valid, real domain.
What should I do if the name is still hidden after clearing all caches?
Re-check the embed code in Odoo's Dynamic Content section, confirm the account's primary URL matches your live domain, and create a new account if the domain changed.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
How SeaText can help
SeaText's Odoo integration page walks you through the exact placement of the embed code. You log in to Odoo, open the Website module, edit the page, and drag the Embed Code module from the Dynamic Content section into place. Then you paste the SeaText JavaScript code and click Save.
The guide also covers the requirements that look like cache problems: each SeaText account is linked to a single primary URL, multiple domains need separate accounts, and development URLs such as localhost are restricted. Use it to verify your domain and embed code before you spend more time clearing caches.