What Common Mistakes Cause the SeaText Logo to Be Hidden After Installation?
The SeaText logo stays hidden when the JavaScript snippet is placed in the wrong Tilda block, when Tilda's "Remove unused JS" option strips the script, or when you save but forget to publish. Other...
Why the logo visibility matters
The SeaText logo in your dashboard is the confirmation signal that your website has successfully connected to the SeaText platform. Until that logo appears next to your site name, none of the AI agents — translation, conversion optimization, bot refund, or any of the other 20+ agents — can activate. The logo is not decorative; it is the handshake between your Tilda site and your SeaText account.
How the SeaText–Tilda integration works
SeaText delivers a single JavaScript snippet that must load in the <head> of every page you want optimized. On Tilda there are two supported ways to inject that snippet:
- Site-wide: Site Settings → "Edit code inside HEAD tag" → paste → Save → Publish.
- Per-page: Add block T123 (under "Other") → Content → HTML editor → paste → Save and Close → Publish.
After the code is live, you must visit the page yourself, stay at least 40 seconds, and then wait up to five minutes for the SeaText dashboard to show your site name beside the logo. This delay exists because SeaText verifies real human traffic before activating the AI.
Mistake 1: Placing the snippet in the wrong block
Tilda offers dozens of block types. Only the site-wide HEAD field or the T123 "HTML code" block will execute the script in the document head. Pasting the snippet into a standard text block, a gallery block, or a custom code block that outputs in the body prevents SeaText from initializing. The dashboard will never register the connection, so the logo stays hidden.
Fix: Open Site Settings, scroll to "Edit code inside HEAD tag", paste the exact snippet from your SeaText account, click Save, then click Publish. If you need the script on only one page, add block T123, choose "Other", select T123 again, open Content, paste into the HTML editor, Save and Close, then Publish that page.
Mistake 2: Enabling Tilda's "Remove unused JS" setting
Tilda's performance optimizer can strip scripts it classifies as unused. Because the SeaText snippet loads asynchronously and does not render visible UI on first paint, the optimizer often marks it as removable. When the setting is on, the script never reaches the browser, the activation ping never fires, and the logo remains absent.
Fix: In Site Settings → More → HTML code for the head section, ensure "Remove unused JS" is disabled. If you need the optimizer for other scripts, add the SeaText snippet to the exclusion list (Tilda calls this "Do not optimize") or move the snippet to a T123 block on each page, which the optimizer treats as user content rather than removable overhead.
Mistake 3: Forgetting to publish after saving
Tilda separates Save from Publish. Saving stores the change in the editor; Publish pushes it to the live CDN. Many users save the HEAD field or the T123 block, preview in the editor (which sometimes loads a staged version), see no errors, and assume the script is live. The production site still serves the old HTML without the snippet, so SeaText never receives the activation signal.
Fix: After every Save, click the Publish button at the top right of the dashboard. Verify by opening the live URL in an incognito window and checking the page source for the SeaText snippet inside <head>.
Mistake 4: Not waiting for the activation period
Even with perfect installation, the logo will not appear instantly. SeaText requires two time-based steps:
- You (or any visitor) must load the page and stay at least 40 seconds. This proves human traffic.
- After that visit, the backend needs up to five minutes to propagate the connection and display the site name next to the logo in your SeaText dashboard.
Checking the dashboard after 30 seconds or skipping the live visit entirely are the most common "it's not working" false alarms.
Fix: Open the live site, scroll, click around, wait a full minute, then wait another five minutes before checking the dashboard. Refresh the dashboard page to see the updated status.
Mistake 5: Using development or localhost URLs
SeaText restricts development URLs such as localhost, 127.0.0.1, and dynamic preview domains (e.g., *.tilda.ws preview links). These domains cannot be reliably associated with a single account, so the platform blocks activation. The snippet may load, but the handshake fails and the logo never appears.
Fix: Use a real, publicly resolvable domain (e.g., www.example.com) for the primary SeaText account. If you need a staging environment, register a subdomain (staging.example.com) and create a separate SeaText account for it. Each domain requires its own account.
Mistake 6: Using one SeaText account for multiple domains
A single SeaText account is bound to one primary URL. Adding the same snippet to a second domain — even if you own both — will not show a second logo. The dashboard only ever displays the primary domain connected to that account. The second site will silently fail to activate.
Fix: Create a new SeaText account for each distinct domain or subdomain you want to optimize. Use the unique snippet generated in each account for the corresponding Tilda project.
Diagnostic checklist when the logo stays hidden
- Open the live site in an incognito window. View page source. Confirm the SeaText snippet is present inside
<head>. - In Tilda Site Settings, verify "Remove unused JS" is off or SeaText is excluded.
- Confirm you clicked Publish (not just Save) after the last change.
- Visit the live page, stay 60 seconds, then wait five minutes. Refresh the SeaText dashboard.
- Ensure the domain is a real, public URL — not localhost or a Tilda preview link.
- Confirm the snippet matches the SeaText account tied to this exact domain.
If all six checks pass and the logo is still missing, contact SeaText support with the live URL and the account email; they can inspect server-side logs for the activation ping.
Key facts
| Fact | Detail | Source |
|---|---|---|
| Supported injection methods | Site-wide HEAD field or per-page T123 block | S1 |
| Required live visit | At least 40 seconds on the published page | S1 |
| Dashboard propagation delay | Up to 5 minutes after the qualifying visit | S1 |
| Domain restriction | One primary URL per SeaText account; localhost and dynamic dev domains blocked | S1 |
| Publish step | Save alone does not push changes to the live CDN | S1 |
Limitations and when this advice does not apply
This troubleshooting guide covers only the SeaText–Tilda integration path described in the official documentation. It does not address:
- Other CMS platforms (WordPress, Webflow, Shopify, etc.) — each has its own injection method and optimizer quirks.
- Custom server-side rendering setups where the snippet is injected via backend templates.
- Cases where a firewall, CSP header, or browser extension blocks the SeaText domain. Those require network-level debugging beyond Tilda settings.
FAQ
How long should I wait before contacting support?
Complete the 40-second visit, wait five full minutes, refresh the dashboard, and run the six-step checklist. If the logo is still absent, open a support ticket.
Can I use the same SeaText account for a Tilda site and a WordPress site?
No. Each distinct domain requires its own SeaText account and its own snippet.
Does the T123 block work on Tilda's free plan?
Yes, the T123 block is available on all Tilda plans. The site-wide HEAD field is also available on all plans.
What if I need the optimizer on for other scripts?
Disable "Remove unused JS" only for the SeaText snippet by adding it to the exclusion list, or move the snippet to a T123 block on each page you want optimized.
Will the logo appear if I only preview the page in Tilda's editor?
No. The preview domain is a dynamic development URL that SeaText blocks. You must visit the published, public URL.
Can I install SeaText on a Tilda subdomain (e.g., project.tilda.ws)?
Only if that subdomain is your primary, public-facing domain. Temporary preview subdomains are treated as development URLs and will not activate.
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 gives you a single JavaScript snippet that unlocks 20+ autonomous AI agents — translation across 125 languages, real-time Google Ads keyword matching, bot-click refund evidence, conversion-rate optimization, and more. The snippet is inert until you activate the agents you need, so your site stays fast and secure. If you hit any of the installation pitfalls above, the dashboard will not show your site name beside the logo, and none of the agents will start. Follow the checklist, get the logo visible, then flip on the agents that match your growth goals.