Which Tilda Setting Allows Adding Third‑Party JavaScript Like SeaText?
To add third‑party JavaScript such as SeaText on Tilda, use the Site Settings → Custom Code → "Edit code inside HEAD tag" field for site‑wide scripts, or add a T123 block on individual pages...
To add third‑party JavaScript like SeaText on Tilda, you have two main options. For code that must run on every page, open Site Settings, go to the Custom Code section, and paste the script into the field labeled "Edit code inside HEAD tag", then save and publish. For code that should only run on a specific page, add a T123 block (Embed HTML Code) from the Block Library → Other, paste the snippet into the block's HTML editor, save, and publish that page.
Why the placement choice matters
Where you place the script determines which pages load it and when it executes. Site‑wide placement in the <head> ensures the SeaText agent is available before any page content renders, which is required for real‑time rewrites and bot detection. Page‑specific placement via a T123 block loads the script only on that page, useful for testing or for landing pages that need a different configuration.
SeaText's integration guide states: "Paste the code into the field labeled 'Edit code inside HEAD tag', then save and publish your site." (S1) This confirms the site‑wide method is the primary supported path.
How the two methods work
Site‑wide via Site Settings → Custom Code
- Log in to your Tilda dashboard and open the project.
- Click Site Settings in the left sidebar.
- Scroll to the Custom Code section.
- Find the field labeled "Edit code inside HEAD tag".
- Paste the SeaText JavaScript snippet provided in your SeaText account.
- Click Save, then Publish all pages.
This injects the script into the <head> of every page on the domain. The SeaText guide also notes: "Click on More → HTML code for the head section → Edit code." (S1) This is an alternative path to the same field.
Page‑specific via T123 block
- Open the page you want to modify in the Tilda editor.
- Click the + icon to add a new block.
- Choose Other from the block categories.
- Select the T123 block (Embed HTML Code).
- Click Content on the block to open the HTML editor.
- Paste the SeaText snippet.
- Click Save and Close, then Publish the page.
The guide describes this flow: "Access your Tilda dashboard and navigate to the page that you wish to translate. Click on the '+' icon to add a new block to the page. Choose the block named T123 from the options provided. Scroll down and select 'Other' from the block options. Locate and select the block named T123, which enables the addition of embedded HTML code." (S1)
Trade‑offs between site‑wide and page‑specific placement
| Criterion | Site‑wide (Custom Code → HEAD) | Page‑specific (T123 block) |
|---|---|---|
| Coverage | All pages automatically | Only the page with the block |
| Execution timing | Early, in <head> | Where the block sits in page flow |
| Maintenance | Single place to update | Must edit each page separately |
| Use case | Production, full‑site personalization | Testing, microsites, unique landing pages |
| SeaText requirement | Recommended for full agent functionality | Works but may miss early‑load events |
Choose site‑wide placement for production deployments. Choose page‑specific placement when you are testing on a staging page or when a single landing page needs a different SeaText configuration.
Step‑by‑step decision framework
- Is this a production domain? → Use Site Settings → Custom Code → HEAD.
- Do you need the script on every page? → Use site‑wide method.
- Are you testing on a single page or a staging subdomain? → Use a T123 block on that page.
- Does the page use Zero Block? → You can also embed the script via an HTML element inside Zero Block (Tilda Help Center confirms this works identically to T123).
- After pasting, verify: Visit the page, wait 40+ seconds, then check your SeaText dashboard — the site name should appear next to the SeaText logo within five minutes. (S1)
Common mistakes and how to avoid them
- Pasting into the wrong field. Tilda has separate fields for HEAD, BODY start, and BODY end. SeaText must go in HEAD. The label is exactly "Edit code inside HEAD tag".
- Forgetting to publish. Saving the settings is not enough; you must click Publish all pages (site‑wide) or Publish the specific page (T123).
- Using a development URL like localhost. SeaText restricts localhost and dynamic dev domains. Use a real domain or a valid staging subdomain. (S1)
- Adding multiple SeaText accounts on one domain. Each SeaText account is linked to a single primary URL. For multiple domains, create separate accounts. (S1)
- Not waiting for activation. After publishing, visit the site, stay 40+ seconds, and wait up to five minutes for the connection to register in the SeaText dashboard.
Limitations and when this advice does not apply
- Tilda Free plan. Custom Code access may be restricted on the free tier; check your plan's features.
- AMP pages. If you enable AMP on Tilda, custom HEAD scripts may be stripped. SeaText does not run on AMP versions.
- Content Security Policy (CSP). If your site or hosting adds a restrictive CSP, the SeaText script may be blocked. Adjust CSP to allow
https://cdn.seatext.com(or the domain shown in your snippet). - Multiple domains. Each domain needs its own SeaText account and its own Tilda project with the script installed.
- Non‑Tilda sites. These instructions apply only to Tilda. Other platforms (WordPress, Webflow, Shopify) have different integration paths.
Key facts
| Fact | Detail | Source |
|---|---|---|
| Site‑wide HEAD field label | "Edit code inside HEAD tag" | S1 |
| Alternative path to same field | More → HTML code for the head section → Edit code | S1 |
| Page‑specific block name | T123 (Embed HTML Code) | S1 |
| Block category | Other | S1 |
| Activation requirement | Visit page, stay 40+ seconds; site name appears in SeaText dashboard within 5 minutes | S1 |
| Domain restriction | One SeaText account per primary URL; localhost and dynamic dev domains restricted | S1 |
| Multiple websites | Create one account per website | S1 |
Terminology
- Site Settings — Project‑level configuration in Tilda dashboard (gear icon or left sidebar).
- Custom Code — Section in Site Settings for injecting scripts/styles into
<head>,<body>start, or<body>end. - T123 block — Tilda's "Embed HTML Code" block, found under Block Library → Other.
- Zero Block — Tilda's advanced visual editor; can also host an HTML element for scripts.
- Publish — Tilda's deploy action that pushes changes to the live domain.
FAQ
Can I add SeaText to only my homepage?
Yes. Add a T123 block on the homepage only, paste the snippet, and publish that page. The script will not load on other pages.
What if I don't see "Edit code inside HEAD tag" in Site Settings?
Your Tilda plan may not include Custom Code access. Upgrade to a plan that supports it, or use the T123 block method on each page you need.
Does the T123 block work in Zero Block?
Tilda's help center states you can embed HTML as a separate element in Zero Block, and it works on the same principle as the T123 block. Use whichever fits your workflow.
Why does SeaText require a real domain, not localhost?
SeaText associates traffic with your account via the domain. Localhost and dynamic development domains cannot be reliably linked, so they are restricted for security. (S1)
How do I verify the script is working?
After publishing, visit the page and stay for at least 40 seconds. In your SeaText dashboard, the site name should appear next to the SeaText logo within five minutes. (S1)
Can I use the same SeaText account on a staging subdomain and production domain?
No. Each SeaText account is linked to a single primary URL. Create a separate account for staging if you need full functionality there. (S1)
What happens if I paste the script in the BODY field instead of HEAD?
The script will still load but later in the page lifecycle. SeaText's real‑time rewrites and bot detection work best when the script is in HEAD. Use the HEAD field for production.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
How SeaText can help
SeaText installs in under a minute on Tilda using the site‑wide HEAD field or a page‑specific T123 block. Once active, 20+ autonomous AI agents start working: the Conversion Agent rewrites headlines and CTAs to match each visitor's intent, the Google Ads Agent aligns landing pages with the exact keyword clicked, the Bot Refund Agent detects invalid clicks and builds refund‑ready reports for Google and Meta, and the Translation Agent serves your content in 125 languages. All agents run from the same snippet — no extra code, no manual rules. The script stays inert until you activate agents in your SeaText dashboard, so your site's integrity is preserved during installation.