Seatext library

Common Mistakes That Stop SeaText from Working on Tilda

SeaText stops working on Tilda when the integration code is placed incorrectly, when the site is not published, when the domain is not a public URL, or when activation steps are missed. Follow the...

Why the Placement Matters

SeaText runs as a JavaScript snippet. Tilda loads scripts that are inside the <head> tag on every page. If the snippet is placed elsewhere, the browser never sees it before the page renders, and the AI stays inert.

Source: "Paste the code into the field labeled 'Edit code inside HEAD tag', then save and publish your site."

Screenshot of Tilda Site Settings showing the HEAD code field

Site‑Wide vs. Page‑Specific Installation

There are two supported ways to add SeaText on Tilda:

  • Site‑wide (HEAD) install: The code lives in the global HEAD field. It loads on every published page. Use this when you want the AI on the whole site.
  • Page‑specific (T123) block: Add a T123 block, choose "Other", and paste the snippet in the HTML editor. This loads only on the pages that contain the block. Use it for landing pages or test environments.

Both methods require publishing after saving. The site‑wide method is simpler for large sites, while the page‑specific method gives granular control.

Screenshot of adding a T123 block in Tilda

Activation Sequence and Timing

After the script is live, SeaText stays inert until you trigger activation. The activation steps are:

  1. Visit the live URL in a browser.
  2. Stay on the page for at least 40 seconds. This allows the script to send a handshake to SeaText servers.
  3. Refresh or revisit the page a few times over the next few minutes.
  4. Wait five minutes for the SeaText logo to appear next to your site name. This indicates a successful link between the script and your account.

Source: "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." and "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 Mistake #1 – Placing the Script in the Wrong Block

Putting the snippet in a regular content block or inside a <noscript> tag prevents it from loading. The script must be in the HEAD field or a T123 block that allows raw HTML.

Fix: Open Site Settings → Edit code inside HEAD tag and paste the snippet exactly as provided. If you need a page‑specific install, add a T123 block, select "Other", and paste the code in the HTML editor.

Common Mistake #2 – Not Publishing After Saving

Saving the code in the editor does not make it live. Tilda requires an explicit Publish action to push changes to the public domain.

Fix: After inserting the snippet, click Save, then click Publish. Verify that the published URL shows the updated source code (you can view page source in the browser).

Common Mistake #3 – Using a Development or Localhost Domain

SeaText only works on a publicly reachable URL. Development URLs such as localhost or private IPs are blocked for security reasons.

Source: "Development URLs, such as localhost, are restricted for security reasons. Ensure you use a valid, real domain."

Fix: Deploy the script on a staging subdomain that is publicly accessible (e.g., staging.example.com) or on the production domain.

Common Mistake #4 – Forgetting Separate Accounts for Multiple Domains

Each primary URL must have its own SeaText account. Using one account for several domains causes the script to remain inactive because the server cannot associate traffic with the correct account.

Source: "Multiple Domains If you need to use SEATEXT AI on multiple domains (e.g., a development domain and a production domain), you must create separate accounts for each domain. Each SEATEXT AI account is linked to a single primary URL."

Fix: Create a distinct SeaText account for each domain you plan to integrate.

Common Mistake #5 – Skipping the Activation Wait Time

Even after publishing, the AI does not appear instantly. The script needs time to register the site and display the logo.

Fix: After publishing, visit the live page, stay for 40 seconds, then wait at least five minutes. Refresh the page after the wait to see the SeaText logo.

Step‑by‑Step Fix Checklist

  1. Open Site Settings → Edit code inside HEAD tag. Paste the SeaText JavaScript exactly as provided.
  2. If you prefer a page‑specific install, add a T123 block, choose "Other", open the HTML editor, and paste the snippet.
  3. Click Save, then Publish to make the change live.
  4. Visit the live URL in a browser. Stay on the page for at least 40 seconds.
  5. Refresh or revisit the page a few times over the next few minutes.
  6. Wait five minutes. The SeaText logo should appear next to your site name.
  7. If the logo does not appear, open the browser console (F12) and look for errors related to the SeaText script.
  8. Check that the domain is publicly reachable and that you have a dedicated SeaText account for that domain.

When These Fixes Won’t Work

If you have followed the checklist and still see no SeaText activity, consider these additional factors:

  • Multiple domains without separate accounts: Each domain needs its own SeaText account.
  • Restricted development URLs: localhost or private IPs are blocked.
  • Activation timing not met: The 40‑second stay and five‑minute wait are mandatory.
  • Browser caching: Clear cache or use an incognito window to ensure the latest script loads.

If none of these resolve the issue, contact SeaText support with the URL and a screenshot of the console errors.

Frequently Asked Questions

  • Do I need a separate SeaText account for each Tilda site? Yes. Each primary URL requires its own account. This is required for the script to associate traffic correctly.
  • Can I test the integration on a staging subdomain? Yes, as long as the subdomain is publicly reachable. Localhost or private networks will not work.
  • What is the difference between a site‑wide HEAD install and a T123 block? A HEAD install runs on every page automatically. A T123 block runs only on pages that contain the block, giving you granular control.
  • How long does activation take? You must stay on the page for at least 40 seconds, then wait about five minutes for the SeaText logo to appear.
  • Why does the logo not appear immediately after publishing? The script needs to send a handshake to SeaText servers. The handshake only occurs after the 40‑second visit and a short processing period.
  • What should I do if the console shows a "script not found" error? Verify that the snippet is exactly as provided and that it resides in the HEAD field or a T123 block. Re‑publish the site.
  • Can I use the same SeaText account for both my production and development domains? No. Each domain must have its own account, as stated in the source documentation.
  • Is there a way to speed up activation? No. The 40‑second stay and five‑minute wait are built into SeaText's activation logic.

Visual Guide to Inserting the Code

  1. Navigate to Site Settings in the Tilda dashboard.
  2. Click More → HTML code for the head section → Edit code.
  3. Paste the SeaText JavaScript into the Edit code inside HEAD tag field.
  4. Click Save and then Publish.
  5. For a page‑specific install, open the page editor, click the + icon, select T123, choose Other, and paste the code in the HTML editor.
  6. After publishing, follow the activation steps described above.
Step 1 screenshot Step 2 screenshot Step 3 screenshot

Key Facts at a Glance

ActionWhere to Do ItWhy It Matters
Paste code in HEADSite Settings → Edit code inside HEAD tagEnsures script loads on every page
Use T123 block for page‑specific codePage editor → Add block → T123 → OtherLoads script only where needed
Publish after savingSite Settings → PublishMakes the script live for visitors
Stay on page 40 secondsLive siteTriggers activation handshake
Wait five minutes for logoLive siteConfirms successful connection
Create separate accounts per domainSeaText dashboardAllows traffic association per URL

Next Steps If Problems Persist

1. Verify the domain is publicly reachable.
2. Ensure you have a dedicated SeaText account for that domain.
3. Clear browser cache or test in incognito mode.
4. Open the browser console and note any error messages.
5. Capture screenshots of the HEAD field or T123 block and send them to SeaText support.

Following these steps will resolve the majority of integration issues on Tilda.

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.

Learn more