Why the SeaText Logo Disappears After Publishing Your Tilda Site and How to Fix It
The SeaText logo disappears after publishing your Tilda site because Tilda’s minification or Content Security Policy (CSP) headers often strip or block the SeaText script during the publish process. To fix it, you need...
What Causes the SeaText Logo to Vanish on the Live Site?
When you publish a Tilda site, the platform optimizes your pages by minifying HTML, CSS, and JavaScript. This process can remove or break third-party scripts like the one SeaText uses. The script contains the code that displays the SeaText logo (and activates the AI agents). If the script is removed or fails to load, the logo will not appear on the live site, even though it shows correctly in the Tilda preview.
Another common cause is Tilda’s Content Security Policy (CSP). Tilda applies security headers that can block inline scripts or external resource loading unless explicitly allowed. The SeaText script may be blocked by these headers, preventing the logo from rendering.
The Diagnostic Sequence: A Step-by-Step Check
Use this diagnostic sequence to identify why the logo is missing. Follow the order—each step rules out a specific cause.
- Verify script placement in Tilda. Go to Site Settings → More → HTML code for the head section → Edit code. Paste the SeaText JavaScript code exactly as provided in your SeaText account. If you inserted it on a per-page basis using the T123 block, double-check that the block is added before publishing.
- Publish and hard-refresh the live site. After publishing, open your site in an incognito browser window and press Ctrl+F5 (Windows) or Cmd+Shift+R (Mac). This bypasses browser cache. If the logo appears now, the issue was a stale cache.
- Check browser console for errors. Open Developer Tools (F12) and look for JavaScript errors or blocked resources. A CSP violation will show as a message like “Refused to load the script because it violates the following Content Security Policy directive.” If you see this, Tilda’s CSP is blocking the script.
- Inspect the page source. Right-click on the live page and select “View Page Source.” Search for “seatext” or “SEATEXT” in the HTML. If the script tag is missing, Tilda removed it during minification. If the tag is present but commented out, Tilda’s system may have disabled it.
- Test with a minimal script. Temporarily replace the SeaText code with a simple script that logs a message (e.g.,
console.log('test')). Publish and check the console. If the test script runs, the issue is specific to SeaText’s script content—contact SeaText support. If the test script also fails, Tilda is blocking all custom scripts, and you need to whitelist via CSP. - Contact Tilda support about CSP. If you confirm a CSP block, ask Tilda support to add your SeaText script domain to the allowlist. You can also try hosting the script externally and referencing it via HTTPS, but the simplest fix is often to adjust the CSP settings in your Tilda project settings (if available).
Why Minification Causes Script Loss
Minification is a performance optimization that removes unnecessary characters, comments, and whitespace from code. It can also rename variables and functions. If the SeaText script uses dynamic loading or relies on specific variable names, minification may break it. Tilda’s minifier may also strip any script that it judges as “not needed” based on heuristic rules. The result is a published page without the SeaText code, and therefore no logo.
How Content Security Policy (CSP) Blocks the Script
CSP is a security standard that tells the browser what resources are allowed to load. Tilda sets a default CSP header that may restrict inline scripts or scripts from unknown origins. The SeaText script is typically loaded from a specific domain (e.g., seatext.com). If that domain is not in the CSP script-src directive, the browser will refuse to execute it. You can check the live site’s HTTP response headers for Content-Security-Policy to see the current rules. To fix this, you need to add the SeaText script URL to the allowed sources in Tilda’s CSP settings or use a nonce/hash approach.
Key Facts About the SeaText-Tilda Integration
| Fact | Detail |
|---|---|
| Script placement | Paste the SeaText JavaScript code into the HEAD tag field in Tilda’s Site Settings, or use the T123 block for per-page insertion. |
| Activation requirement | After installation, visit or refresh your website several times and stay on the page for at least 40 seconds to activate the AI and link it to your account. |
| Multiple domains | Each SeaText account is linked to a single primary URL. For multiple domains, create separate accounts. |
| Security restriction | Development URLs like localhost are restricted. Use a real, valid domain. |
| Publishing behavior | All changes are applied instantly upon publishing, but browser cache may show an old version. Hard refresh is required. |
Limitations and When This Advice Does Not Apply
This diagnostic assumes you have correctly copied the SeaText script from your account. If you are using a custom Tilda plan that restricts external scripts, the advice may not work—contact Tilda for plan-specific details. Also, if you are using a third-party caching plugin or CDN, the script may be delayed or blocked; in that case, purge the cache and re-test. The diagnostic steps do not apply if you are using a different integration method, such as a Google Tag Manager container, which would require separate troubleshooting.
Terminology: Key Terms Explained
Minification: The process of removing unnecessary characters from code to reduce file size. Content Security Policy (CSP): A security header that controls which resources can be loaded on a page. Inline script: JavaScript code written directly in the HTML instead of in a separate file. Browser cache: A local storage of previously loaded web pages that can serve outdated versions.
Frequently Asked Questions
Why does the logo show in Tilda preview but not after publishing?
Tilda’s preview mode does not apply minification or CSP headers that the live site uses. The script runs fine in preview, but the live environment may strip or block it.
How do I check if Tilda’s CSP is blocking the script?
Open your published site, press F12 to open Developer Tools, go to the Console tab, and look for red error messages that mention “Content Security Policy” or “refused to load.”
Can I add the SeaText script via Tilda’s custom code block (T123) instead of the HEAD section?
Yes, you can use the T123 block on a per-page basis. This can sometimes bypass CSP issues because the script is loaded with the page content. However, the logo will only appear on pages where the block is added.
What if the script is in the page source but the logo still doesn’t appear?
This could mean the script is loaded but not executed due to a syntax error or a conflict with another script. Check the browser console for JavaScript errors. Also, ensure the script is not commented out. If the script is present and error-free, the issue may be a timing conflict—SeaText’s script may need to load after other scripts. Try moving it to the bottom of the HEAD section.
Does the SeaText logo require a specific browser or device?
No, the logo is displayed via JavaScript and should work on all modern browsers. If it only fails on a specific browser, check that browser’s console for CSP or script errors.
How long does it take for the SeaText logo to appear after correct installation?
After publishing and hard-refreshing, the logo should appear immediately. However, SeaText’s system requires a 40-second visit and a few minutes to link the website to your account. Wait up to five minutes, then refresh the page.
What should I do if none of the diagnostic steps work?
Contact SeaText support with the diagnostic results. They can check if the script is correctly linked to your account and provide additional troubleshooting.
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 provides a dedicated Tilda integration page with step-by-step instructions for installing the script. Our support team can help you verify that the script is correctly placed and activated. If you encounter CSP issues, we can guide you on whitelisting our script domain with Tilda. The integration is secure, and the AI remains inert until you activate it, ensuring your site’s integrity.
Note: SeaText accounts are linked to a single primary URL. If you need to test on a development domain, create a separate account. Development URLs like localhost are restricted for security reasons.