How to Update SeaText on Your Tilda Site: No Manual Update Needed
SeaText updates automatically because the script loads from SeaText's CDN, so routine updates never require re-pasting code or republishing your Tilda site. You only touch Tilda when you install the script, change your project...
SeaText updates itself. The JavaScript snippet you paste into Tilda is served from SeaText's CDN, so new features and fixes reach your site without any extra work. You do not need to edit Tilda, re-paste code, or republish your site for a routine SeaText update.
The only times you need to change something in Tilda are: first-time installation, a change to your project ID or domain, and adding SeaText to a site that doesn't have the script yet. If your website name already appears in your SeaText account, your installation is current.
How SeaText Updates Work
SeaText installs as one piece of JavaScript in your site's HEAD section. That script connects your Tilda site to your SeaText account. Because the script is served by SeaText rather than stored as a fixed file inside Tilda, SeaText can update the script without you re-pasting anything. When a visitor loads your page, the browser fetches the current version.
This is different from a plugin or app that lives inside Tilda and needs a manual update click. From your side, installation is a one-time step. Routine updates happen in the background.
When You Actually Need to Touch Tilda
The automatic update covers SeaText's own script. It does not cover changes on your side. These cases need your attention:
- First install. Paste the snippet into the HEAD field for all pages, or use a T123 block for one page.
- Project ID or URL change. Each SeaText account is linked to a single primary URL. If your Tilda project moves to a new domain, get the snippet for the new project.
- A new website. Create one account per website, then paste that site's own snippet.
- Script removed during a redesign. Re-paste the snippet and publish.
If you skip these cases, the old script may point at the old URL, or the new site may have no script at all. You won't see an error on the page, so check the SeaText dashboard when something changes on your side.
Step by Step: Verify Your Current Install
Before changing anything, check the install you already have. This takes about two minutes.
- Open your Tilda dashboard and go to Site Settings.
- Click More → HTML code for the head section → Edit code.
- Look for the SeaText JavaScript snippet and compare it with the one in your SeaText account.
- Visit or refresh your site several times and stay for at least 40 seconds.
- Wait about five minutes, then check the SeaText dashboard for your website name next to the SEATEXT logo.
If the snippet matches and your site name appears, you're done. There is nothing to update.
Step by Step: Replace the Script After a Project ID Change
Use this process when your Tilda project ID, domain, or primary URL has changed. Replacing the old script with the new one is the update.
- Log in to your SeaText account and copy the JavaScript snippet shown in the integration section. If the change includes a new domain, create the account for that domain first — each account is linked to a single primary URL.
- Go to Site Settings in Tilda.
- Click More → HTML code for the head section → Edit code.
- Select the old SeaText snippet in the field and replace it with the new one. For a single-page install, open the T123 block, click Content, and replace the code in the HTML editor.
- Click Save and Close, then Publish.
- Refresh your site several times and stay on the page for at least 40 seconds.
- Wait about five minutes for your website name to appear in the SeaText dashboard.
Use the HEAD field for all pages. Use the T123 block only when you want SeaText on a particular page.
Key Facts: SeaText on Tilda
Scope: This guide covers the SeaText JavaScript snippet on Tilda sites. The install is one script in the document head, plus account and activation rules. If you're looking for Tilda's own site-publishing flow, that is separate.
| Topic | What you need to know |
|---|---|
| Where the script goes (all pages) | Site Settings → More → HTML code for the head section → Edit code → paste into the field labeled Edit code inside HEAD tag. |
| Where the script goes (one page) | Add a T123 block, open Content, paste the snippet into the HTML editor, click Save and Close, then Publish. |
| Account requirement | Before you can install the script, you need a SEATEXT AI account. |
| Account and URL | Each SEATEXT AI account is linked to a single primary URL. Use separate accounts for separate websites. |
| Development URLs | URLs such as localhost are restricted for security reasons. Use a valid, real domain. |
| Activation | Visit or refresh your website several times and stay on the page for at least 40 seconds. |
| Confirmation | Wait at least five minutes until your website name appears next to the SEATEXT logo at the top of the dashboard. |
Limitations and Edge Cases
The automatic-update model works because SeaText controls the script. It comes with limits worth knowing:
- One account per primary URL. You cannot reliably point one account at two Tilda sites. Create one account per website.
- Restricted development URLs. localhost is blocked, and dynamic development domains may not work because SeaText can't reliably associate traffic with your account.
- Activation is not instant. The script needs visits and dwell time before your site appears in the dashboard.
- No update button in Tilda. There is no "Update SeaText" button. You update by replacing the snippet when something on your side changes.
- Applies to Tilda sites. This advice covers Tilda's HEAD field and T123 block. Other site builders use different install steps.
Common Mistakes
| Mistake | Why it hurts | Fix |
|---|---|---|
| Pasting the snippet into a normal HTML block instead of the HEAD field | The script may be treated as page content or only appear in one spot. | Use Site Settings → HEAD field for all pages, or T123 for a single page. |
| Using one account for two sites | Each account is linked to one primary URL. | Create a separate account for each website. |
| Testing on localhost | Development URLs are restricted for security. | Use a valid, real domain. |
| Publishing but not staying on the page | The AI never activates. | Refresh several times and stay at least 40 seconds. |
| Checking the dashboard too early | The website name may not appear yet. | Wait about five minutes after activation. |
Frequently Asked Questions
Do I have to update SeaText manually on Tilda?
No. Routine updates are automatic because the script is served by SeaText. You only re-paste the snippet when your project ID or domain changes.
Where do I paste a new SeaText script in Tilda?
Go to Site Settings, click More → HTML code for the head section → Edit code, replace the old snippet, save, and publish. For one page only, use a T123 block.
Why doesn't my site show up in my SeaText account?
The AI activates when visitors load the page. Visit or refresh the site several times, stay for at least 40 seconds, then wait about five minutes for the website name to appear.
Can I use the same SeaText account on my staging and production Tilda sites?
No. Each account is linked to a single primary URL. If you need SeaText on a development domain and a production domain, create separate accounts.
Does updating cost anything?
The integration guide doesn't list an update fee, and the change is just replacing a script. For current plan prices, check SeaText's pricing page.
What if I removed the script during a redesign?
Re-paste the snippet into the HEAD field, save, publish, and run the activation check above.
If you need the current snippet, the exact field names, or the activation steps in one place, the official SeaText Tilda integration page has everything.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.