Where to Place the SeaText Script in Tilda for Best Performance
SeaText's official Tilda integration guide instructs you to paste the JavaScript snippet into the "Edit code inside HEAD tag" field in Site Settings so it loads on every page. For a single page you...
Why script placement matters for SeaText
SeaText runs autonomous AI agents that rewrite headlines, swap offers, translate copy, and detect bot traffic in real time. Those agents must be active before the browser paints the first meaningful content; otherwise visitors see the original page for a flash and the agents miss the earliest interaction signals. Tilda gives you two supported injection points: the global HEAD field in Site Settings and a per‑page T123 HTML block. Both place the snippet in the document <head>.
How SeaText loads in Tilda
According to the SeaText integration guide, you copy the JavaScript snippet from your SeaText dashboard and paste it into the field labeled "Edit code inside HEAD tag" in Tilda's Site Settings, then save and publish. The guide also shows an alternative for a single page: add a T123 block, choose "Other" → "T123", open the HTML editor, paste the snippet, save, and publish. In both cases the code ends up inside the <head> of the rendered page.
Head vs. body vs. footer: trade‑offs for SeaText
| Placement | Load timing | SeaText agent readiness | Rendering impact | When to use |
|---|---|---|---|---|
| Global HEAD (Site Settings) | Early, before body parse | All agents active from first paint | Minimal if script is lightweight and async | Default for every site; recommended by SeaText |
| Per‑page T123 block in HEAD | Early, before body parse | All agents active from first paint | Same as global HEAD | Testing on one page before site‑wide rollout |
| Body‑top via custom block | After head, before main content | Agents start after head scripts finish | Slightly less head congestion | Not documented by SeaText; may delay agent init |
| Footer / before | After full DOM parse | Agents miss early scroll, click, and ad‑click signals | Zero head blocking | Not supported; breaks real‑time rewriting and bot detection |
Takeaway: SeaText's agents need to run before the visitor sees anything. The documented HEAD placements are the only ones that guarantee that.
Performance impact and Core Web Vitals
Core Web Vitals measure loading speed, interactivity, and visual stability. A script placed in the head can block rendering if it is large or synchronous. SeaText's snippet is designed to load asynchronously once it is in the head, so it does not delay First Contentful Paint or Largest Contentful Paint. The integration guide states the snippet should be placed in the head, and SeaText’s own benchmarks report "negligible impact on Core Web Vitals when placed in the head as instructed." This means you keep fast page loads while still enabling real‑time AI features.
When asynchronous loading might be considered
If a developer knows that the SeaText snippet can be loaded with the async attribute without breaking the activation handshake, moving it to the footer could remove any remaining head‑blocking risk. However, the official guide does not mention an async‑only mode, and the agents rely on early execution. Therefore, the safest practice is to follow the head placement. If you experiment with async loading, verify activation in the SeaText dashboard and monitor agent readiness in the Network tab.
Advanced scenarios: multiple domains and staging environments
SeaText ties each account to a single primary URL. The source pack explains that development domains such as localhost or dynamic preview URLs are restricted for security reasons. For a staging subdomain you must create a separate SeaText account. The same rule applies to multi‑domain production setups; each domain needs its own account and its own script snippet. This limitation ensures accurate traffic attribution and prevents cross‑domain data leakage.
Security considerations: CSP and script integrity
Content Security Policy (CSP) can block inline scripts. SeaText’s snippet is served from a CDN, so you must add the SeaText domain to the script-src directive. The integration guide does not list the exact CDN domain, so check the script URL in the page source or contact SeaText support. Do not wrap the snippet in additional defer or async attributes, because the snippet already manages its own loading strategy. Altering it can break the handshake that links the script to your account.
Best‑practice checklist for Tilda integration
- Copy the exact JavaScript snippet from your SeaText dashboard.
- Paste it into Site Settings → More → HTML code for the head section → Edit code inside HEAD tag.
- Save and publish the entire site (or use a T123 block for a single page test).
- Verify the script tag appears inside
<head>using DevTools. - Check the Network tab: the SeaText request should fire before
DOMContentLoaded. - Visit the live page, stay at least 40 seconds, then wait five minutes for the dashboard to show your site name.
- If you use CSP, add the SeaText CDN URL to
script-src. - Do not duplicate the snippet on the same page.
- Avoid manual
async/deferattributes unless SeaText confirms they are safe.
Limitations and when this advice does not apply
- Development domains (localhost, dynamic preview URLs) are restricted by SeaText for security; you must use a real domain.
- Each SeaText account is tied to one primary URL. Multiple domains require separate accounts.
- If you use a CSP that blocks inline scripts, you’ll need to allow the SeaText domain; the integration guide does not cover CSP configuration.
- The T123 block method only affects the page where the block lives; it does not propagate to other pages.
- Placing the script in the footer is not supported and will break real‑time rewriting and bot detection.
Key facts
| Fact | Detail |
|---|---|
| Supported global placement | Site Settings → More → HTML code for the head section → Edit code inside HEAD tag |
| Supported per‑page placement | T123 block (Other → T123) → Content → HTML editor |
| Activation requirement | Visit published page, stay 40+ seconds, wait 5 minutes for dashboard confirmation |
| Domain rule | One SeaText account per primary URL; localhost and dynamic dev domains restricted |
| Script behavior | AI remains inert until activated; secure installation process |
FAQ
Can I put the SeaText script in the Tilda footer to improve PageSpeed scores?
No. SeaText's agents (Google Ads keyword matching, bot detection, real‑time translation) must run before first paint. Footer loading breaks those features.
Does the T123 block put the script in the head or body?
The T123 block injects into the page head, same as the global setting. It is simply a per‑page alternative.
What if I have a Content Security Policy that blocks inline scripts?
You must add the SeaText script domain to your CSP script-src directive. The snippet is served from SeaText’s CDN; the exact domain can be seen in the script URL after you paste it.
Can I use one SeaText account for a staging subdomain and the production domain?
No. Each account is linked to a single primary URL. Create a separate account for each domain.
How do I know the script is working after I publish?
Visit the live page, stay 40 seconds, then check the SeaText dashboard. Your site name should appear next to the SeaText logo within five minutes.
Will the script slow down my Tilda site?
The snippet is lightweight and loads asynchronously. SeaText’s own benchmarks show negligible impact on Core Web Vitals when placed in the head as instructed.
Can I minify or bundle the SeaText snippet with my other scripts?
Not recommended. The snippet includes a unique account token and self‑updating logic; bundling can break the activation handshake.
Is it safe to add async to the SeaText script tag?
The official guide does not mention adding async. The snippet already handles asynchronous loading, so adding the attribute may interfere with the handshake. Keep the tag exactly as provided.
What performance metrics should I monitor after adding SeaText?
Watch First Contentful Paint, Largest Contentful Paint, and Time to Interactive. Verify that the SeaText request appears before DOMContentLoaded in the Network panel.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
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.