When to Add SeaText JavaScript to Your Tilda Site: Readiness Checklist
Add the SeaText script during initial site setup or as soon as you enable SeaText in your account; the script must be live before you can activate any AI agents. If you update the...
Add the SeaText JavaScript to your Tilda site during initial site setup or the moment you create your SeaText account and choose a plan. The script must be present on every page you want optimized before you activate any AI agents — otherwise the agents have no way to rewrite content, detect bots, or translate pages. If you already have a live Tilda site, add the script as soon as you decide to use SeaText; delaying only postpones the 40‑second activation visit and the five‑minute connection check that confirm the integration works.
Why timing matters for SeaText on Tilda
SeaText’s autonomous agents — conversion optimizer, Google Ads matcher, bot‑refund detector, translation engine, and others — run entirely in the browser after the script loads. No script means no agent activity, no keyword‑aware rewrites, no bot evidence collection, and no multilingual rendering. The integration guide states: "Paste the Javascript code from Seatext on your website To insert code in the head of all website pages, go to the Site Settings. Paste the code into the field labeled 'Edit code inside HEAD tag' , then save and publish your site." Until that step is complete, the AI remains inert.
Readiness checklist: before you add the script
- SeaText account created. You need a valid SeaText account; each account is tied to a single primary domain.
- Primary domain is live and not a development URL. Localhost and dynamic staging domains are restricted for security reasons.
- Tilda Site Settings accessible. You must have permission to edit the global HEAD code field or add a T123 block on specific pages.
- Plan selected or trial started. Agent activation requires an active subscription or the free one‑month pilot.
- Time reserved for verification. After publishing, you’ll need to visit the site, stay at least 40 seconds, and wait five minutes for the dashboard to show the site name next to the SeaText logo.
When to add during site setup vs. later
New Tilda project: Insert the script in Site Settings → HEAD before you publish the first version. That way every page — including future pages — inherits the script automatically. Existing live site: Add the script immediately after you create the SeaText account. Use the global HEAD field for site‑wide coverage; only use a per‑page T123 block if you intentionally want SeaText on a subset of pages. Redesign or migration: Re‑add the script in the new environment before you switch DNS. The script is tied to the domain, not the Tilda project ID.
How the activation process works
- Copy the JavaScript snippet from your SeaText dashboard (the code appears under the integration section).
- In Tilda, open Site Settings → More → HTML code for the head section → Edit code.
- Paste the snippet into the "Edit code inside HEAD tag" field.
- Save and publish the site.
- Visit the published site, refresh a few times, and remain on a page for at least 40 seconds.
- Wait at least five minutes. The SeaText dashboard will then display your website name next to the logo, confirming the connection.
The guide emphasizes: "Important: Visit or refresh your website several times and stay on your page for at least 40 seconds—this will activate the AI and link it to your account. Important: Wait at least five minutes until you see your website name displayed next to the SEATEXT logo at the top of this page. This indicates that your website is connected and ready to proceed to the next step."
Common timing mistakes and exceptions
- Adding the script but not publishing. The script only runs on the published version; draft changes don’t count.
- Using a staging subdomain (e.g.,
staging.mysite.tilda.ws) for the primary account. Each domain needs its own SeaText account; staging domains count as separate domains. - Skipping the 40‑second visit. Without real browser traffic, the AI never activates and agents stay dormant.
- Exception — per‑page testing. If you only want to test SeaText on a single landing page, add a T123 block ("Embed HTML Code") to that page instead of the global HEAD. This limits activation to that page only.
Key facts
| Item | Detail | Source |
|---|---|---|
| Global install location | Site Settings → More → HTML code for the head section → Edit code inside HEAD tag | S1 |
| Per‑page install block | T123 block ("Embed HTML Code") added via the "+" icon → Other → T123 | S1 |
| Account‑domain rule | One SeaText account per primary domain; multiple domains require separate accounts | S1 |
| Development URL restriction | Localhost and dynamic development domains are restricted | S1 |
| Activation visit | Visit published site, stay ≥ 40 seconds, refresh several times | S1 |
| Connection confirmation | Wait ≥ 5 minutes for site name to appear next to SeaText logo in dashboard | S1 |
| Script behavior before activation | "The installation process is secure, and the AI remains inert until activated" | S1 |
Limitations and when this advice does not apply
- If you manage multiple brands on subdirectories (e.g.,
example.com/brandA,example.com/brandB) under one Tilda project, a single script covers all — but each brand may need its own SeaText account if they use different primary domains. - Tilda’s Zero Block HTML element can also hold the script, but the global HEAD field is simpler for site‑wide coverage.
- This checklist assumes you control the Tilda Site Settings. Agency or client‑side permission constraints may shift the timing to a hand‑off meeting.
- SeaText does not support localhost or ephemeral preview URLs; you must use a real, publicly resolvable domain.
FAQ
Can I add the script after I’ve already launched my Tilda site?
Yes. Add it in Site Settings → HEAD, publish, then complete the 40‑second visit and five‑minute wait. All existing pages will start receiving agent activity immediately.
Do I need to re‑add the script if I change Tilda templates?
No. The global HEAD code persists across template changes. Only a full project reset or domain change would require re‑entry.
What happens if I add the script but never activate agents in the dashboard?
The script loads but stays inert. No rewrites, translations, or bot detection occur until you toggle agents on in your SeaText account.
Can I use the same SeaText account for a Tilda site and a WordPress site on the same domain?
No. Each primary domain requires its own SeaText account. If both sites share the exact same domain (e.g., subdirectory vs. subdomain), you’d still need separate accounts per SeaText’s one‑account‑per‑domain rule.
How do I verify the script is working before activating agents?
After publishing, open the browser dev tools → Network tab, filter for "seatext", and confirm the script loads. Then complete the 40‑second visit; the dashboard connection status is the final proof.
Is there a downside to adding the script early, before I’m ready to pay?
No downside. The script is lightweight and inert until you activate agents. Adding it early lets you verify the connection while you finalize agent selection.
What if my Tilda site uses a custom domain that isn’t live yet?
Wait until the custom domain resolves and serves the published Tilda site. SeaText cannot connect to a domain that doesn’t serve content.
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.