How to troubleshoot SeaText integration on Tilda free
Tilda Free does not allow custom JavaScript in the HEAD tag or via the T123 HTML block, so SeaText cannot be installed on the free plan. The only fix is upgrading to a paid...
If you are trying to add SeaText to a Tilda site on the Free plan, stop troubleshooting the paste location. The free tier blocks any custom <script> tags, so the integration will never activate.
What SeaText does on your Tilda site
SeaText adds an AI‑powered agent that rewrites copy, optimises offers and tracks conversions in real time. The JavaScript snippet must load in the <head> of every page before the first paint. Loading early guarantees the agent can read the initial HTML, inject its own styles and start tracking visitor behaviour instantly. If the script is missing or stripped, the AI stays inert and no optimisation occurs.
Why Tilda Free blocks SeaText
Tilda disables custom code on the Free tier to keep the platform lightweight and to encourage upgrades. Both the global HEAD field and the T123 block are disabled or stripped on Free sites. Because SeaText relies on early script execution, the missing snippet means the AI never initializes.
Top 3 mistaken paste locations on Tilda Free
| Mistaken location | Intended purpose of the field | Why SeaText fails here |
|---|---|---|
| Site Settings → SEO → Header code | Meta tags, verification tokens, structured data | Free plans strip all <script> tags from this field. |
| Site Settings → Analytics → Custom code | Google Analytics, Meta Pixel, Yandex.Metrica counters | Only whitelisted analytics snippets run; custom JS is ignored. |
| Page Settings → Additional code in HEAD | Per‑page meta tags, canonical overrides | Scripts are removed on Free plans, just like the global field. |
How SeaText integration works on paid Tilda plans
Upgrading unlocks two supported insertion points. Both are described in SeaText’s official Tilda guide.
Option A – Global HEAD injection (recommended)
- Open the Tilda dashboard and go to Site Settings.
- Select More → HTML code for the head section → Edit code.
- Paste the SeaText JavaScript snippet into the field labelled "Edit code inside HEAD tag".
- Save and publish the entire site.
This loads the agent on every page automatically and ensures the earliest possible execution.
Option B – Page‑level via T123 block
- Open the page you want to optimise.
- Click the "+" icon, choose Other, then select the T123 (Embedded HTML) block.
- In the block’s Content editor, paste the SeaText snippet.
- Save, close, and publish the page.
Use this only when you need SeaText on a subset of pages, such as a single landing page.
Step‑by‑step: correct integration after upgrading
- Create a SeaText account if you don’t have one. Each domain needs its own account.
- Copy the JavaScript snippet from your SeaText dashboard (the code block labelled
SEATEXTCODEINTEGRATION). - Paste the snippet into the global HEAD field or a T123 block, depending on your choice.
- Publish the site or the specific page.
- Visit the live URL in a regular browser, stay on the page for at least 40 seconds. This activates the AI.
- Wait five minutes, then check the SeaText dashboard. Your site name should appear next to the SeaText logo, confirming the connection.
Decision criteria for upgrading Tilda
- Need for real‑time AI optimisation. If you want dynamic copy changes, you must run the script in the HEAD.
- Site scale. Larger sites benefit more from a single global injection than from many page‑level blocks.
- Budget. The cheapest paid plan (Personal) already unlocks the HEAD field. Compare the cost against the expected conversion lift from SeaText.
- Technical comfort. Global HEAD injection is a one‑time setup; page‑level blocks require repeated edits for new pages.
Practical scenarios where SeaText shines on Tilda
- E‑commerce stores. Inject the script globally so every product page receives AI‑driven headline and offer tweaks.
- Landing‑page campaigns. Use a T123 block on a single campaign page to test AI copy without affecting the rest of the site.
- Multilingual sites. SeaText can translate content on the fly; the script must be present on each language version, which the global HEAD method guarantees.
- Rapid A/B testing. Because the agent rewrites copy instantly, you can run dozens of variants without creating separate pages.
Common mistakes beyond paste location
- Each SeaText account is linked to a single primary URL. Create a separate account for each domain or subdomain.
- Testing on a development subdomain (e.g.,
localhost) does not work; SeaText restricts such URLs for security reasons. - Forgetting to publish after saving the code. Tilda requires an explicit publish step for HEAD changes to go live.
- Not waiting the full activation window. The 40‑second visit and five‑minute propagation are mandatory before the dashboard shows the site as connected.
Verification checklist
- Open the live page in an incognito window.
- View page source and confirm the SeaText script appears inside
<head>. - Stay on the page for at least 40 seconds.
- Return to the SeaText dashboard; the site name should appear next to the logo within five minutes.
- If the name does not appear, re‑check that you published the correct site (not a draft) and that the script is not wrapped in comments or conditional tags.
Limitations and when this advice does not apply
- This guide covers only Tilda’s Free vs. paid code‑injection restrictions. It does not apply to other website builders.
- If you are on a paid Tilda plan and the script still disappears, contact Tilda support – some legacy or region‑specific plans may have different limits.
- SeaText’s own restrictions (one account per domain, no localhost) apply regardless of Tilda tier.
Key facts
| Fact | Detail | Source |
|---|---|---|
| Global HEAD field label | "Edit code inside HEAD tag" | SeaText Tilda integration guide |
| Page‑level block name | T123 (Other → Embedded HTML) | SeaText Tilda integration guide |
| Activation visit time | At least 40 seconds on page | SeaText Tilda integration guide |
| Dashboard confirmation delay | Wait at least 5 minutes | SeaText Tilda integration guide |
| Account‑to‑domain rule | One SeaText account per primary URL | SeaText Tilda integration guide |
| Development URL restriction | localhost and dynamic dev domains not supported | SeaText Tilda integration guide |
FAQ
Can I use SeaText on Tilda Free if I add the script via a third‑party CDN or tag manager?
No. Tilda Free strips or blocks any custom <script> regardless of the injection method. The platform simply does not execute user‑supplied JavaScript in the HEAD.
Which paid Tilda plan is the cheapest that unlocks the HEAD field?
Any current paid plan (Personal, Business, or higher) enables the Edit code inside HEAD tag field and the T123 block. Check Tilda’s pricing page for the latest feature matrix.
Do I need a separate SeaText account for a staging subdomain on the same paid Tilda project?
Yes. SeaText treats each distinct domain, including subdomains, as a separate primary URL, so you must create a separate account for each.
What if I pasted the code correctly on a paid plan but the dashboard still shows "waiting for connection" after 10 minutes?
Confirm the script is present in the live page source (not a draft), that you visited the live URL and stayed 40 seconds, and that no ad blocker or browser extension prevented the script from loading. If all checks pass, contact SeaText support with the live URL.
Can I put the SeaText snippet in the <body> via a T123 block at the bottom of the page?
SeaText recommends the HEAD for earliest execution. A body‑placed T123 block will work but may delay the AI’s first‑paint optimisations. Use the global HEAD field whenever possible.
Does SeaText work on Tilda’s e‑commerce (store) pages?
Yes, provided the store pages inherit the global HEAD code or you add a T123 block to each store template page. The integration method is identical.
Is there a way to test SeaText before upgrading Tilda?
You can create a SeaText account and test on a different platform that allows custom code on a free tier (for example, a WordPress.com free site with a code‑injection plugin), but you cannot test the Tilda‑specific integration without a paid Tilda plan.
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.