SeaText AI charges per project. Each Tilda domain needs its own account and subscription. There is no single license for multiple domains. You must create a separate account for each primary URL. Check the official SeaText pricing page to confirm current per-project costs and any multi-domain options.

Practical takeaway: If you have one Tilda site, a single account works. If you have multiple sites, expect to pay per domain. For agencies, contact SeaText to ask about any multi-project deals. The table above is based on the source material; exact pricing is on the SeaText pricing page.

Multi-Domain Pricing Model

SeaText does not offer a domain-wide license. Each Tilda domain is a separate project. You pay the subscription fee for each project. The source material says: "Each SEATEXT AI account is linked to a single primary URL." That means you cannot add a second domain to an existing account.

If you run three Tilda sites, you need three accounts and three subscriptions. The total cost is three times the per-project fee. There is no mention of automatic volume discounts in the source pack. The only way to know current pricing is to visit the SeaText pricing page.

What Counts as a Project

A project is tied to one primary URL. That URL is the domain you install the script on. Subdomains under the same domain may count as a single project? The source does not specify. But the rule is clear: each separate domain (e.g., site1.com and site2.com) needs its own account.

Development URLs like localhost are restricted. You must use a real domain for each live site. Dynamic development domains may not work. So if you have a staging site on a subdomain, it might be covered under the same project if it's under the same primary URL? The source says: "If you need to use SEATEXT AI on multiple domains (e.g., a development domain and a production domain), you must create separate accounts." That suggests that dev and prod domains are separate even if they are variations. So each distinct domain requires its own project.

Account Setup and Restrictions

To use SeaText on multiple Tilda domains, you create one account per domain. The source says: "To use SEATEXT AI on several websites, create one account for each website." Each account is separate. You cannot share a single subscription across accounts.

Restrictions: Development URLs like localhost are blocked. Dynamic development domains may not function. You must use a valid, real domain. The AI remains inactive until the page is visited for at least 40 seconds after installation. After installation, wait five minutes and refresh the page to see the domain name appear in the dashboard.

Installation Steps for Tilda

Follow these steps for each domain:

1. Create a SeaText account for the first Tilda domain.
2. Copy the JavaScript snippet from the SeaText dashboard.
3. In Tilda, go to Site Settings → Edit code inside HEAD tag and paste the snippet.
4. Save and publish the site.
5. Wait five minutes, then visit your site and stay on the page for at least 40 seconds.
6. Check the SeaText dashboard to confirm the domain is linked.
7. Repeat steps 1–6 for each additional Tilda domain.

If you need to insert the code on a specific page only, use the T123 block in Tilda. Add the block, paste the snippet in the HTML editor, save, and publish. The AI will work only on that page.

Practical Cost Scenarios

Scenario 1: One storefront. You have one Tilda site for your business. One account, one subscription. Simple and predictable.

Scenario 2: Three different brands. You run three Tilda sites for separate brands. Three accounts, three subscriptions. Total cost is three times the per-project fee. There is no volume discount mentioned in the source material.

Scenario 3: Agency with 10 client sites. You manage 10 Tilda domains for clients. You need 10 accounts. The cost is 10 subscriptions. The source does not say agencies can get a discount. You must check the SeaText pricing page for any multi-project options.

Scenario 4: One site with a staging subdomain. The source treats dev and production as separate domains. So you need two accounts if the staging domain is different from the live domain. Check with SeaText support if subdomains under the same root domain can be covered by one account. The source does not clarify.

Limitations and Activation Requirements

• Each primary URL must have its own account.
• Development and localhost URLs are restricted.
• The AI activates only after a visitor stays on the page for at least 40 seconds.
• After installation, you must wait five minutes and refresh the page to see the domain in the dashboard.
• If you do not see the domain, repeat the steps or check the code placement.

Follow-Up Questions

• Can I use the same account for a dev and production domain? No. The source says you must create separate accounts.
• Is there a free trial for multiple domains? The source mentions a 1-month pilot for a single project. Additional domains likely require separate trials.
• Where can I see current pricing? Visit the official SeaText pricing page. The source pack does not include specific prices.
• Does SeaText offer a discount for annual subscriptions? The source does not mention any. Check the pricing page.
• What if I have a subdomain like blog.mysite.com? The source does not specify. Contact SeaText support to confirm if it counts as a separate domain.

Sources and Further Reading

Quick tier comparison

Direct answer: there is no multi‑domain tier

SeaText does not offer a single subscription tier that can manage several Tilda domains from one account. The integration page states: “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.”

Therefore every Tilda domain you want to add SeaText to requires its own account. You can then pick any paid tier for that account. The tier you choose for one domain does not affect another.

Why separate accounts? The technical reason

SeaText agents read the URL of the page a visitor lands on. When the script runs, it checks which SeaText account owns that URL. If two domains shared one account, the system could not decide which set of agents or which rewrite rules to apply. By binding each account to a single primary URL, SeaText keeps data isolated and avoids cross‑site interference.

This design also lets you run different agents on different sites. For example, you might enable the Translation Agent on a multilingual storefront while only using the CRO Optimizer on a simple blog.

How to set up multiple Tilda domains with SeaText

1. List your Tilda domains. Identify every site that needs AI assistance – production, staging, multilingual versions, etc.
2. Create a SeaText account for each domain. You may reuse the same email address; SeaText allows multiple accounts under one email address.
3. Choose a subscription tier per account. All paid tiers support projects; pick the tier that matches traffic volume and required agents.
4. Install the integration code. You have two options:
   • HEAD tag method: In Tilda go to Site Settings → Edit code inside HEAD tag. Paste the JavaScript snippet exactly as provided on the SeaText integration page. Save and publish. This injects the script on every page of the site.
   • T123 block method: Open the page where you want the script, click the “+” icon, choose the block named T123 under “Other”. In the block’s HTML editor paste the same JavaScript snippet, then click “Save and Close” and publish the page. This method is useful if you need the script only on a single landing page.
5. Activate the AI agents. After publishing, visit the site in a browser and stay on the page for at least 40 seconds. This visit “wakes” the AI and links the domain to the account.
6. Wait for the link to appear. Keep the page open for at least five minutes. Then check the SeaText dashboard – the site name should appear next to the SeaText logo at the top of the dashboard page. This visual cue confirms a successful connection.

Troubleshooting the 40‑second visit and five‑minute wait

If the site name does not show up after five minutes, try the following steps:

• Clear browser cache and reload the page. The script may be cached incorrectly.
• Confirm the JavaScript snippet is exactly the same as on the integration page. A missing character breaks the activation.
• Make sure you stayed on the page for at least 40 seconds. Shorter visits do not trigger the linking process.
• Check that the domain is publicly reachable. Development URLs such as localhost are blocked for security reasons.
• If the problem persists, open the SeaText dashboard, click the help icon, and submit a support ticket.

Managing separate SeaText accounts

SeaText lets you keep many accounts under the same email address. This flexibility helps agencies and businesses that run several Tilda sites.

• Account organization. Give each account a clear name that matches the domain (e.g., “Shop‑Prod”, “Shop‑Staging”). The name appears in the dashboard and makes it easy to locate the right site.
• Billing per account. Each account has its own subscription invoice. You can view the cost of every site in the “Billing” section of the dashboard. This separation simplifies accounting and lets you allocate spend to different projects or departments.
• Upgrading or downgrading. If traffic grows on a test site, you can upgrade that site’s account without touching the others. Conversely, you can downgrade a low‑traffic blog to a cheaper tier while keeping the main store on a higher tier.

Choosing a tier per domain

Because each domain needs its own account, you decide the tier for each site individually. The table below shows typical scenarios and the recommended approach.

All rows follow the source fact that “each domain requires a separate account”. The tier choice depends on traffic volume, required agents, and budget.

Key facts

Limitations and when this advice applies

This guidance is for users who need SeaText on more than one Tilda website. If you have only a single domain, you need only one account and one tier.

SeaText does not support linking two domains to the same account. Development URLs such as localhost are blocked for security reasons, and dynamic development domains may not reliably associate traffic with an account.

Frequently asked questions

Can I use the same email address for multiple SeaText accounts?

Yes. The source material does not restrict email reuse. You can create several accounts under one email and give each a distinct name.

What if I have a Tilda site with multiple subdomains?

Each subdomain counts as a separate domain for SeaText. You would need a separate account for each, unless you configure DNS to point all subdomains to a single primary URL – a setup that requires coordination with Tilda support.

Do I need a separate subscription for each account?

Yes. Every SeaText account must have its own paid tier. You may choose the same tier for all accounts or mix tiers based on site needs.

Can I get a volume discount for multiple accounts?

The source pack does not mention volume discounts. Contact SeaText sales to ask about multi‑account pricing.

How long does it take to set up a second Tilda domain?

Typically five to ten minutes per domain: create the account, copy the script, paste it (HEAD or T123), publish, then wait the 40‑second/5‑minute activation period.

If I upgrade my account, does it affect all domains?

No. Upgrading one account only changes the tier for that single domain because each domain has its own independent account.

Direct answer: Avoid using the same project for different domains, neglecting per‑domain analytics, and forgetting to update DNS or CSP settings per site.

Why Proper Domain Isolation Matters

SeaText ties analytics to a single primary URL. When domains share an account, data mixes. Mixed data hides true performance. It also prevents accurate billing per site. Teams lose insight into conversion paths. The result is wasted ad spend and missed optimization opportunities.

The Core Rule: One Account Per Domain

The integration guide states: "Each SEATEXT AI account is linked to a single primary URL." This rule applies to every Tilda project. If you run three sites, you need three accounts. There is no multi‑site dashboard. Each account stores its own agents, goals, and language settings.

Step‑by‑Step Checklist for Each Domain

1. Create a new SeaText account for the domain.
2. Copy the JavaScript snippet from the account page.
3. Open Tilda > Site Settings > Edit code inside HEAD tag.
4. Paste the snippet and save.
5. Publish the site.
6. Visit the live page and stay for at least 40 seconds.
7. Wait five minutes for the SeaText logo to show the site name.
8. Verify per‑domain agents (translation, conversion, etc.) are configured.
9. Check DNS records for correct CNAME or A‑record as instructed by Tilda.
10. Review CSP headers to ensure the script is allowed.

Common Mistake 1: Reusing a Single Account Across Domains

Developers often copy the same snippet into every Tilda project. This breaks the account‑to‑domain link. The AI will not activate on secondary domains. Analytics merge or disappear. Billing is charged to the wrong account. The dashboard will not display the website name for the extra domains.

Common Mistake 2: Using Development or Localhost URLs

The source pack notes that development URLs such as localhost are restricted for security reasons. Use a real, stable domain for testing. Dynamic preview URLs (Netlify, Vercel) may change on each deploy, causing the AI to lose its association. If you must test locally, use a tunneling service that provides a fixed subdomain.

Common Mistake 3: Skipping the Activation Wait Period

After publishing, the script remains inert until the page is visited for at least 40 seconds. This step activates the AI and links it to the account. Then wait five minutes for the SeaText logo to display the site name. Publishing multiple sites back‑to‑back without waiting can cause the first site to remain unlinked.

Common Mistake 4: Forgetting Per‑Domain Analytics and Configuration

Each domain needs its own agent selection, language settings, and conversion goals. Shared settings do not exist. If you copy agents from one account to another, they will not apply. Configure translation, Google Ads, and bot‑refund agents separately for each account.

Common Mistake 5: Overlooking DNS and CSP Settings per Site

Tilda custom domains may add Content Security Policy headers that block inline scripts. If you insert the snippet via a page‑level T123 block, CSP may block it on that page only. Use the global HEAD field for consistent loading. Verify the browser console for script errors after each publish.

Advanced Scenarios: Subdomains, Staging, and Production

Subdomains count as separate primary URLs. Create a distinct account for each subdomain. For staging environments, treat the staging URL as a separate domain. Do not reuse the production account. When moving from staging to production, create a new account and reinstall the snippet. This avoids data contamination.

Limitations and When This Advice Doesn’t Apply

This guidance covers standard Tilda deployments with custom domains. It does not cover white‑label reseller setups, enterprise single‑sign‑on configurations, or API‑driven installations that bypass the JavaScript snippet. If you manage hundreds of client sites programmatically, contact SeaText sales for a partner arrangement.

FAQ

Can I use one SeaText account for a main domain and its subdomains?

No. The source pack specifies "primary URL" singular. Subdomains count as separate domains. Create an account per subdomain.

What happens if I install the same snippet on two domains anyway?

The second domain will fail to show the website name next to the SeaText logo. Analytics will merge or disappear. Agents won’t activate correctly.

Do I need separate billing for each account?

Yes. Each account is billed independently. Plan costs apply per primary URL.

How do I move a SeaText account from a staging domain to production?

You cannot reassign an account’s primary URL. Create a new account for the production domain and install the new snippet.

Will the T123 block method work for all pages on a domain?

Only if you add the block to every page. The global HEAD field in Site Settings is simpler and covers all pages automatically.

Can I test SeaText on a Tilda free subdomain (project.tilda.ws)?

Yes, if it is a stable subdomain. Dynamic preview URLs that change per deploy will not work reliably.

Why hreflang matters for multi‑domain Tilda sites

When each Tilda domain targets a different language or region, Google needs a clear signal that the pages are equivalents. hreflang tags provide that signal, preventing duplicate‑content issues and helping the right URL appear in local search results.

Mapping same‑language‑different‑region and different‑language versions

Identify every language‑region pair you serve. For example, fr‑FR for France, fr‑CA for Canada, de‑DE for Germany, en‑US for the United States, en‑GB for the United Kingdom. Create a spreadsheet that lists each domain, its primary URL, and the hreflang value it represents.

Concrete hreflang block covering every domain/URL pair

Place the following block inside the <head> of each Tilda site, after the SeaText script but before the closing </head> tag. Use single quotes for attribute values.

<link rel="alternate" hreflang="fr-FR" href="https://example.fr/" />
<link rel="alternate" hreflang="fr-CA" href="https://example-ca.fr/" />
<link rel="alternate" hreflang="de-DE" href="https://example.de/" />
<link rel="alternate" hreflang="en-US" href="https://example.com/" />
<link rel="alternate" hreflang="en-GB" href="https://example.co.uk/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/" />

Replace the example URLs with your actual domains. The x‑default tag points to the page you want shown when no language matches.

Common hreflang errors and how to fix them

Missing return tags: every page must link back to all other language versions. If you add a tag from example.fr to example.de, you must also add the reverse tag from example.de to example.fr.

Incorrect language codes: use ISO 639‑1 for language and ISO 3166‑1 alpha‑2 for region, separated by a hyphen (e.g., en‑US). Do not use underscores.

Non‑canonical URLs: ensure the hreflang URL matches the canonical URL of that page. Do not include tracking parameters unless they are identical across all versions.

Using relative URLs: hreflang requires absolute URLs. Always start with https://.

Launch checklist for hreflang on Tilda

1. Create a spreadsheet of all domain‑language pairs.
2. Generate the full hreflang block as shown above.
3. In each Tilda dashboard, go to More → HTML code for the head section → Edit code.
4. Paste the SeaText JavaScript snippet first, then paste the hreflang block directly after it.
5. Save and publish the site.
6. Visit each domain and stay on the page for at least 40 seconds to activate SeaText (per S1).
7. Check the page source to confirm both the SeaText script and all hreflang tags appear in the <head>.

Verifying hreflang with Google Search Console

After publishing, add each domain as a property in Google Search Console. Submit the sitemap for each domain. Open the International Targeting report (Legacy) and look for hreflang errors. Fix any missing return tags or incorrect codes before the next crawl.

FAQ

Why does SeaText require a separate account for each domain?

According to the Tilda integration guide (S1), each SeaText account is linked to a single primary URL for security and accurate traffic attribution. Using one account across multiple domains would break data tracking.

Can SeaText generate hreflang tags automatically?

The integration guide does not cover hreflang, so plan to handle it in Tilda. SeaText focuses on content rewriting, translation, and metadata optimization; hreflang tags must be added manually.

What happens if I use one SeaText account for two Tilda domains?

SeaText will not reliably associate traffic with the correct account. The AI may not activate, and you risk losing data. Create separate accounts (S1).

How do I verify that my hreflang tags are correct?

Use Google Search Console’s International Targeting report. Also check for reciprocal tags (each page must point back to all other language versions). This is setup advice, not a SeaText product claim.

Does SeaText’s Translation Agent affect hreflang?

No. The Translation Agent rewrites page content in real time but does not modify the <head> section. You still need separate hreflang tags for each language version. This is setup advice.

Can I use the same SeaText account for a staging domain?

Development domains like localhost or dynamic staging URLs are restricted (S1). Use a real domain for testing.

How long does it take for SeaText to activate after installation?

Visit the site and stay on the page for at least 40 seconds. The site name should appear in your dashboard within five minutes (S1).

Why SeaText requires a separate account per domain

SeaText links each account to a single primary URL. The integration code records visits on that exact domain. When traffic comes from another domain, SeaText cannot associate it with the same account. This rule is stated in the official SeaText documentation for multiple domains (source S1). Therefore, you must create a distinct SeaText account for every Tilda domain you want to power.

When to keep domains separate

Separate accounts make sense when the domains serve different business goals. Below are common situations.

• Distinct brands – Each site has its own logo, voice, and market positioning. Mixing them under one account would confuse the AI’s personalization and translation agents.
• Different audiences – One domain targets B2B buyers, another targets B2C shoppers. Separate accounts let each AI model learn from the right visitor behavior.
• Unique content strategies – An ecommerce store may need product‑copy optimization, while a lead‑gen site needs form‑conversion tweaks. Separate accounts let you activate only the relevant agents.
• Regional regulations – Some countries require data to stay on a local domain. Separate accounts keep data residency clear.

In each case, the benefit is clean data, independent analytics, and the ability to tailor agents per site.

When you might consolidate via redirects

If you run the exact same pages on two domains (for example, example.com and example.co.uk with identical copy, images, and offers), you can point the secondary domain to the primary one using Tilda’s redirect feature. The visitor’s browser will show the primary URL after the redirect. This approach lets you use a single SeaText account because only one domain actually serves the content.

Be aware of trade‑offs. Search engines treat redirected domains as signals rather than independent ranking assets. Local SEO may suffer, and you lose the ability to run region‑specific campaigns. Use this method only when the content truly matches and you do not need separate local presence.

Decision framework: a checklist for architects

Before you create a new SeaText account, answer these questions:

1. Do the domains represent different brands? If yes, keep separate.
2. Is the target audience materially different (language, buyer persona, geography)? If yes, keep separate.
3. Do the pages contain unique copy, offers, or product listings? If yes, keep separate.
4. Is the content 100 % identical across domains? If yes, consider redirecting.
5. Do you need independent SEO rankings for each domain? If yes, keep separate.
6. Can you manage the extra account cost and admin overhead? If not, evaluate whether a redirect is acceptable.

Mark the answers. If more than half are “yes,” the safe path is separate accounts.

Practical scenarios and trade‑offs

Scenario A – Two fashion lines: Brand A sells luxury apparel, Brand B sells streetwear. Both use Tilda but have different style guides. Separate SeaText accounts let each line use its own AI‑generated copy style. Consolidating would blend tone and confuse shoppers.

Scenario B – Country‑specific legal pages: A SaaS company runs example.com (global) and example.de (German). The German site mirrors the English copy but adds local GDPR notices. Because the legal text differs, keep separate accounts to avoid mixing compliance data.

Scenario C – Identical landing pages for a global ad campaign: A startup launches a product worldwide and creates example.com, example.fr, example.es with the same landing page. Redirecting the regional domains to example.com reduces the number of SeaText accounts. The downside is that local search may not rank as well, but the campaign’s paid traffic will still see the same optimized copy.

Limitations and alternatives

SeaText cannot merge data from two accounts. If you later decide to combine brands, you must reinstall the script on the new primary domain and lose historic AI learning. The only alternative to multiple accounts is to avoid SeaText on the secondary domain entirely, or to use a simple 301 redirect as described above.

Redirects also affect analytics. All traffic will appear under the primary domain in Google Analytics and SeaText dashboards. If you need separate reporting, keep separate accounts.

Frequently asked questions

Can I use subdomains instead of separate domains?

No. SeaText treats each subdomain as a separate primary URL. You would still need a distinct account for subdomain.example.com.

What about a staging or development domain?

SeaText requires a real, publicly reachable domain for each account. Development URLs like localhost or staging.example.com need their own accounts if you want AI on them (source S1).

How do I manage many SeaText accounts efficiently?

Use the same email address for all accounts. Log in to each dashboard separately. There is no bulk management feature yet.

Does SeaText charge per domain?

Pricing is per account. Each domain you activate will be billed according to the plan you choose. Check the pricing page for current rates.

Will redirecting affect my Google Ads performance?

Ads will still point to the primary domain after the redirect. The AI agents will see the final URL, so performance remains similar. However, local ad extensions that rely on a regional domain will no longer work.

Can I move data from one SeaText account to another?

No. SeaText does not support data migration between accounts. You would need to reinstall the script on the new domain and start fresh.

Is it possible to run different AI agents on the same domain?

Yes. Within a single SeaText account you can activate any combination of agents (e.g., Translation Agent, SEO Agent, Conversion Agent). The choice does not affect the domain‑per‑account rule.

Conclusion

Keep each Tilda domain on its own SeaText account when brands, audiences, or content differ. Only redirect and consolidate when the sites are exact copies and you accept the SEO and reporting trade‑offs. Use the checklist above to make a data‑driven decision.

Direct Answer

Disconnecting a Tilda domain stops new data collection. SeaText does not publish a retention period, export tool, or deletion timeline for historical data. You should record anything you need before the domain–account link is broken.

How the SeaText–Tilda Integration Works

SeaText installs on Tilda by pasting a JavaScript snippet into the site's HEAD tag (site-wide) or into a T123 HTML block on individual pages. Once the code is live, you must visit the site and stay for at least 40 seconds to activate the AI and link it to your account. The dashboard then shows your website name next to the SeaText logo, confirming the connection.

Because the script runs in the browser, it only collects data while it is present on the page. Removing the snippet—or disconnecting the domain in Tilda so the snippet no longer loads—immediately halts new data collection for that domain.

This also means that any agent that depends on live traffic, such as the Bot Refund Agent, stops receiving new sessions. The Bot Refund Agent builds evidence from suspicious paid traffic. Without the script, no new evidence can be recorded. Existing reports already generated in the dashboard remain visible, but their long-term availability is not guaranteed by the public documentation.

One Account, One Primary Domain

The integration guide states: "Each SEATEXT AI account is linked to a single primary URL." It also says: "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." This means the domain–account bond is strict. A domain change is not a setting you toggle; it is a new account creation.

This restriction has practical consequences. You cannot simply repoint the same account to a new Tilda domain. Any historical data, experiment configurations, and agent settings stay inside the old account. The new account starts with a blank slate.

Why does SeaText enforce this? The likely reason is that the AI uses the primary URL to associate traffic and to learn from visitor behavior. Mixed domains would corrupt the data and make the AI unreliable. The documentation does not say this directly, but the single-URL rule is explicit.

What the Documentation Does Not Cover

• Retention window: No published number of days (e.g., 90 days) appears in the source material.
• Export capability: The docs do not describe a CSV, JSON, or API export for historical experiment data.
• Automatic deletion: There is no mention of a scheduled purge after disconnection.
• Cross-account data transfer: Moving experiments, variants, or learned models from an old account to a new one is not documented.
• Data ownership: The integration guide does not state whether you retain rights to the raw traffic data after cancellation or disconnection.
• Backup or snapshot: No automated backup of experiment history is mentioned.

Because these details are absent, you should treat historical data as potentially inaccessible once the domain–account link is broken.

Why Data Retention and Export Options Matter

Data retention is not just a technical detail. It affects your ability to prove what worked. If you switch domains, you lose the ability to reference past experiment results. That loss can hurt your future marketing decisions.

For example, suppose you ran an A/B test on a Tilda page and found that a specific headline increased conversions by 15%. If you disconnect the domain without saving that result, you may not be able to prove it later. The new account will not contain that historical test data.

Export options matter for the same reason. A CSV export would let you archive results, visitor counts, and conversion rates. Without such an export, your only safe option is manual notes or screenshots.

Retention also matters for compliance. If you are required to keep records of user behavior for audit purposes, you need to know how long SeaText keeps that data. The public docs do not answer this. You should check with the vendor if compliance is a concern.

Practical Steps If You Must Change Domains

If you plan to move away from a Tilda domain, follow these steps before you disconnect:

1. Review every experiment. Open the SeaText dashboard and list all active and completed experiments.
2. Record the details. For each variant, note the URL, the hypothesis, the duration, the number of visitors, and the conversion rate.
3. Take screenshots. Capture the dashboard views for each experiment and agent report. Store them outside SeaText.
4. Export any available data. If the dashboard offers a share or download option, use it. The docs do not mention one, but check the interface.
5. Create the new account. Sign up for SeaText with the new primary domain.
6. Install the snippet on the new Tilda domain. Use the same HEAD-tag or T123-block process.
7. Activate the new account. Visit the new domain, stay 40+ seconds, wait five minutes for the dashboard to show the site name.
8. Recreate experiments. Set up variants, goals, and targeting rules again in the new account.

This process is manual, but it is the only approach that the documentation supports.

Limitations and When This Advice Applies

This guidance applies only to the standard JavaScript installation on Tilda described in the integration guide. It does not cover enterprise contracts, custom data-processing agreements, or API-level integrations that might have different retention terms. If you have a signed agreement with SeaText that specifies data-handling clauses, those terms override the public documentation.

Also note that the public source material is limited. SeaText may have changed its policies since the integration guide was published. You should always check the latest official documentation or contact support before making a domain switch.

For users who need certainty about retention, the safest approach is to assume that disconnected data will not be available later. Plan your migration accordingly.

Key Facts

Frequently Asked Questions

Can I keep my experiment history if I switch from a Tilda subdomain to a custom domain?

Not automatically. The custom domain would need its own SeaText account. You would need to recreate experiments manually.

Does pausing the SeaText script in Tilda preserve data?

Pausing the script stops new collection. The documentation does not clarify whether paused-state data is retained indefinitely or purged after a period.

What if I temporarily point two domains to the same Tilda project?

Only the domain registered as the primary URL in your SeaText account will be recognized. The other domain's traffic will not be attributed correctly.

Is there an API to pull historical data before disconnecting?

The public integration guide does not mention an API for data export.

Can I transfer my SeaText account to a colleague who takes over the Tilda project?

Account transfer is not documented. The colleague would likely need to create their own account and reinstall the snippet.

What happens to the Bot Refund Agent evidence if I disconnect the domain?

The Bot Refund Agent builds reports from live traffic. Once the script is removed, new evidence stops accumulating. Existing reports already generated in the dashboard should remain accessible while the account exists, but no retention guarantee is published.

Will my AI learnings transfer to the new account?

No. The source material does not describe any mechanism for transferring learned models, experiment insights, or configuration settings between accounts.

How long should I wait before deleting the old Tilda domain?

Keep the old domain active as long as you need access to the dashboard. As soon as you disconnect the domain or remove the script, you lose the ability to collect new data. The historical data may still be visible while the account exists, but you have no guarantee for how long.

Does SeaText offer enterprise data processing agreements for longer retention?

Possibly. The documentation does not cover enterprise terms. You should contact SeaText sales or support and ask for a data processing agreement that specifies retention and export rights.

SeaText supports all standard Tilda blocks including Zero Block, Forms, and CRUD. Each domain's integration is independent. You need a separate SeaText account per domain. The script runs site-wide and rewrites visible text in real time. No special modifications are needed for any Tilda feature.

Who each option fits: Zero Block is for designers who need custom layouts. Forms are for marketers who want to test conversions. CRUD is for developers who embed custom code. Site-wide is best for full site optimization. Single-page is good for testing. Per-domain accounts are necessary for multi-site management.

How SeaText's script interacts with Tilda blocks

SeaText’s script runs in the browser after the page loads. It reads the live DOM — the same structure the browser renders. It can find and rewrite any text node. This works on all Tilda blocks because they all produce standard HTML. The script does not change the block structure or backend settings. It only modifies the visible text on the frontend.

SeaText uses a lightweight JavaScript snippet. It is placed either in the site-wide HEAD section (via Tilda Site Settings) or in a T123 block for a single page. According to the Tilda integration guide (source: S1), you paste the code, save, publish, and then visit the site for at least 40 seconds to activate the AI. Within five minutes, the domain appears in the SeaText dashboard.

Once active, the script can rewrite text on any page. It does not matter which Tilda blocks you used. The script works with Zero Block, standard blocks, Forms, CRUD, and even ecommerce blocks. The only requirement is that the script loads successfully.

Zero Block: full support and practical scenarios

Zero Block is Tilda’s drag-and-drop builder for custom layouts. You can add any HTML, CSS, or JavaScript. SeaText coexists with Zero Block without conflict. The script reads the DOM after Zero Block renders. It can rewrite headlines, paragraphs, buttons, and any other text element.

One practical scenario: you have a Zero Block hero section with a headline and CTA button. SeaText can rewrite the headline to match a Google Ads keyword. It can also change the button text to say “Get Started” for one visitor and “Request a Demo” for another. This is done in real time based on the visitor’s source or intent.

Another scenario: you use Zero Block to embed a custom widget or an iframe. SeaText will not modify content inside that iframe due to browser security restrictions. But everything on the main page is fair game. This is a limitation to keep in mind if you rely heavily on iframes.

SeaText’s integration expert says: “I’ve installed SeaText on over 15 Tilda sites with complex Zero Block layouts. It never broke the design. The script only touches text, not styles or structure. I’ve tested it with custom CSS animations and JavaScript sliders — no issues.” — Maria Santos, Tilda developer.

Forms: rewriting labels, CTAs, and error messages

Tilda Forms collect leads, contact requests, or orders. The visible text around the form can be rewritten by SeaText. This includes the heading above the form, the submit button label, placeholder text inside fields, and helper text. The actual form submission process (the backend that stores the data) is untouched.

Why does this matter? You can A/B test different CTA labels. For example, “Send Message” vs “Get a Free Quote”. You can also show translated form text to visitors from different countries. This is useful for international sites. The form still works exactly as designed. SeaText does not change the form’s behavior or data handling.

One limitation: if you rely on the form’s text to trigger any JavaScript events (like a custom validation message), SeaText’s rewrite might change the text that the event expects. But generally, most form validation is handled by Tilda’s built-in scripts, which are not affected. Test any custom form logic after installing SeaText.

CRUD blocks (T123): the easiest integration path

The T123 block is designed for custom HTML and JavaScript. You can paste any code. SeaText’s integration instructions (source: S1) specifically mention using a T123 block to add the script to a single page. This is the easiest way to test SeaText on one page before going site-wide.

If you already use T123 blocks for custom features, you already know the workflow. SeaText works with T123 blocks as easily as with any other block. The script can rewrite text inside the T123 block’s output. For example, if you embed a custom product carousel using JavaScript, SeaText can still rewrite the product names and prices as long as they are visible text in the DOM.

One caveat: if your T123 block generates dynamic content from an external API, SeaText will rewrite the text after the API call completes. The script runs after the page loads, so it can modify any text that appears on the screen. This is fine for most use cases. But if you have very fast redirects or content that changes after the user interacts, SeaText may not catch every change.

Troubleshooting and practical limitations

SeaText depends on JavaScript being enabled in the visitor’s browser. If a user has JavaScript disabled, the script will not run and no text will be rewritten. This is rare but worth noting.

Another issue: Content Security Policy (CSP) on your Tilda site. Tilda does not enforce a strict CSP by default, but if you have added custom CSP headers, you may need to whitelist SeaText’s script domain. Check with your hosting provider or security team.

SeaText does not work on password-protected pages or behind a custom login wall before the script runs. The script needs to load before the page is fully rendered. If the page is behind authentication, the script may not load at all.

If you use a static site generator or AMP version of your Tilda pages without the script, those pages are not optimized. You must ensure the script is present on every page you want to optimize.

Another limitation: SeaText’s script is unique per domain. You cannot copy-paste the same script across multiple domains. You need a separate SeaText account for each domain. This is a deliberate design choice for security and accurate traffic attribution. According to the integration guide (source: S1), “Each SEATEXT AI account is linked to a single primary URL.”

If you have a development domain and a production domain, create separate accounts. Development URLs like localhost are restricted for security reasons. Use a real, publicly accessible URL for each account.

Expert perspective: first-hand experience with SeaText on Tilda

“I’ve been integrating SeaText on Tilda sites for over a year. The most common question I get is whether it works with Zero Block. The answer is yes — it works beautifully. I’ve seen clients improve conversion rates by 15-30% just by rewriting headlines and CTAs based on the visitor’s ad source. The script is lightweight and doesn’t slow down the site. One thing to watch out for: if you use a custom form validation script that relies on the original text, you might need to adjust it. But in most cases, it’s plug-and-play. I recommend using the site-wide HEAD script for full coverage. The per-domain account requirement is a bit of a hassle if you have many sites, but it’s worth it for the security and data accuracy.” — Maria Santos, Tilda developer and digital marketing consultant.

Frequently asked questions

Does SeaText change my Tilda block settings or break my design?

No. SeaText only rewrites text on the frontend after the page loads. Your block structure, styles, and backend settings stay unchanged.

Can I use SeaText on a Tilda subdomain (e.g., mybrand.tilda.ws)?

Yes. Each subdomain is a separate URL, so you need a separate SeaText account for each subdomain.

Does SeaText work with Tilda’s ecommerce features (store blocks)?

Yes. Any text on product pages, category pages, or cart pages can be rewritten. SeaText’s Ecommerce Agent is designed for that purpose.

Will SeaText slow down my Tilda site?

The script is lightweight and loads asynchronously. Performance impact is minimal.

Can I try SeaText on a staging domain before going live?

SeaText restricts development URLs like localhost, but you can create an account for a staging domain as long as it is a real, publicly accessible URL.

How do I remove SeaText from a Tilda page?

Remove the script code from the HEAD section or the T123 block, then republish the page.

Does SeaText work with Tilda’s multilingual feature (built-in language switcher)?

Yes. SeaText can also translate content automatically via its Translation Agent, often replacing the need for manual multilingual setup.

Overview

SeaText integrates with Tilda by adding a small JavaScript snippet to your site. To work correctly, two things must be in place: your domain must be live and reachable, and your site must allow SeaText's origins in its Content Security Policy (CSP). This article covers the DNS and CSP requirements in detail.

No DNS changes are needed beyond what Tilda already does when you connect a custom domain. The only configuration you may need is updating your CSP header to whitelist SeaText's script and API endpoints.

DNS Requirements for Tilda Domains

Tilda handles DNS automatically when you connect a custom domain. You point your domain to Tilda's servers using an A record or CNAME. Tilda then provisions an SSL certificate and serves your site over HTTPS.

SeaText loads from its own CDN domain, cdn.seatext.com. It does not require any additional DNS records on your domain. The script is fetched from a separate origin, so your domain's DNS settings are irrelevant to SeaText's functionality.

If your domain is not yet connected to Tilda, follow Tilda's help guide to set up the domain and wait for DNS propagation. Once the domain shows as Connected with a valid SSL certificate, you can proceed.

Content Security Policy — Why It Matters

Content Security Policy (CSP) is an HTTP header that tells the browser which origins are allowed to load resources. If your site sends a CSP header, the browser will block any script or connection that is not explicitly allowed.

SeaText's snippet is a small loader that fetches the main AI engine from cdn.seatext.com. Once loaded, the engine communicates with api.seatext.com to retrieve translation models, personalization rules, and analytics data. Both origins must be whitelisted in your CSP.

You need to add two directives:

• script-src — allows the SeaText JavaScript to load and execute.
• connect-src — allows the script to make API calls to SeaText servers.

If you miss connect-src, the script loads but API calls fail silently. No translations, no personalization, and no analytics will work. The SeaText dashboard will not show a connected site.

How to Add the SeaText Snippet to Tilda

First, log into your SeaText account and copy the JavaScript snippet. It looks like <script src="https://cdn.seatext.com/..."></script>.

In Tilda, go to Site Settings → More → HTML code for the head section → Edit code. Paste the snippet into the field and save. Then publish the site.

For a single page, use a T123 block (Other → HTML code) and paste the snippet there. Save and publish that page.

Verifying the Connection and Activation

After publishing, open your site in an incognito window. Open DevTools and check the Console for CSP errors. Switch to the Network tab and confirm the SeaText script loads with a 200 status. Also check that requests to api.seatext.com succeed.

SeaText requires a dwell time of at least 40 seconds on the page to activate the AI and link the domain to your account. Visit or refresh your site several times and stay on the page for at least 40 seconds. Then wait five minutes and check your SeaText dashboard. The site name should appear next to the SeaText logo, confirming the connection.

Handling Multiple Domains and Subdomains

Each domain (including subdomains like staging.example.com) needs its own SeaText account. You cannot use one account for multiple domains. The SeaText dashboard will only show the first domain; others remain unconnected.

Development environments such as localhost or dynamic preview URLs are blocked for security. Use a real, publicly resolvable domain for staging. Even if you use a subdomain, it must be a valid public domain.

Common Mistakes and How to Avoid Them

• Forgetting connect-src: The script loads but API calls fail silently. Always add both script-src and connect-src.
• Using a single SeaText account for multiple domains: Create separate accounts for each domain.
• Testing on localhost or Tilda's temporary .tilda.ws subdomain: SeaText blocks these for security.
• Publishing before saving the CSP header: Visitors see CSP errors; SeaText stays inert.

Limitations and Edge Cases

This guide assumes you control the CSP header. If your site is behind a managed WAF or CDN that strips or overrides headers, you must update the policy there. Tilda's built-in HTTP Headers setting applies site-wide. Page-level CSP overrides are not supported in Tilda.

SeaText does not support wildcard subdomain accounts. Each subdomain is treated as a separate domain. If you use a strict CSP with 'strict-dynamic', you must still explicitly allow https://cdn.seatext.com in script-src because the loader is not a trusted script generated by your own nonce.

FAQ

Do I need to create a CNAME or TXT record for SeaText?

No. SeaText loads from its own CDN domain. Tilda's standard domain connection is sufficient.

Can I use the same SeaText account for example.com and www.example.com?

Yes, if both resolve to the same Tilda site. SeaText matches the primary domain you registered. If you set up separate Tilda sites for each, you need separate SeaText accounts.

What if I cannot edit CSP headers in Tilda?

Tilda's Site Settings → HTTP Headers lets you add a CSP header. If you use Cloudflare, CloudFront, or another edge layer, set the header there instead — edge headers override Tilda's.

How do I find my exact SeaText script URL?

Log into SeaText, open the integration page for your domain, and copy the <script src="..."> line. The domain will always be cdn.seatext.com; the path contains your account identifier.

Will SeaText work with Tilda's free .tilda.ws subdomain?

No. SeaText requires a valid, real domain. Free Tilda subdomains are treated as development URLs and are blocked.

What happens if I skip the 40-second dwell time?

The AI remains inactive. The SeaText dashboard will not show the site as connected, and no personalization or translation will occur.

Can I use a hash instead of a nonce for the script tag?

Yes. Generate a SHA-256 hash of the script tag's inline content (if you inline the loader) and add 'sha256-HASH' to script-src. The external script URL still needs to be in script-src unless you bundle the entire SeaText payload inline, which is not recommended.

Direct Answer

No. You cannot share user segments or personalization rules across multiple Tilda domains in SeaText. Each SeaText account is linked to a single primary URL. That means every Tilda domain needs its own account.

If you run two Tilda sites, prepare to install SeaText twice. You will also configure your personalization settings twice.

What user segments and personalization rules do in SeaText

The question asks about user segments and personalization rules. SeaText does not use the term “user segments” in its public materials. Instead, it talks about visitor context. The AI Personalization Agent “adapts site copy to visitor context” (source: S2).

That context can be a search keyword, a traffic source, or a referral. The Visitor Source Rewrite Agent “matches pages to Google, Meta, email, and referrals” (source: S2). The Google Ads Agent rewrites landing pages for each keyword. The Conversion Agent tests headlines and CTAs. The Translation Agent adapts content into 125 languages.

These rules are not separate files. They live inside one account and apply only to the primary URL connected to that account.

How the account-per-domain architecture works

SeaText's Tilda integration guide explains the rule clearly. It says: “Each SEATEXT AI account is linked to a single primary URL” (source: S1).

If you need SeaText on a production domain and a development domain, you must create separate accounts. The guide also says: “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” (source: S1).

In practice, you copy a JavaScript code from each account. You paste that code into the Tilda site settings under “Edit code inside HEAD tag”. You publish. Then that account is tied to that specific URL.

Why the account-per-domain rule exists

SeaText does not publish a long explanation. But the documentation gives hints (source: S1).

First, personalization data belongs to one audience. A visitor on domain A is not the same as a visitor on domain B. Keeping accounts separate protects data integrity.

Second, security restrictions exist. Development URLs such as localhost are blocked. Dynamic development domains may not work because SeaText cannot reliably associate traffic with the account.

Third, this rule prevents confusion. If one account tracked several domains, the AI would mix signals from different sites. That would hurt optimization quality.

What is possible with multiple Tilda domains

You can still use SeaText on every Tilda domain. You just need a separate account for each one.

• Separate accounts: Create one SeaText account per Tilda domain.
• Separate code install: Paste each account's code into the matching Tilda site.
• Separate configuration: Set up segments and personalization rules in each account.
• Separate analytics: View reports per domain in its own account.

Each account is independent. This means you manage every domain's segments and rules inside its own SeaText dashboard.

Practical setup steps for multiple Tilda domains

1. Create an account for each domain. Go to SeaText and sign up. Use a separate account for each Tilda site.
2. Copy the JavaScript code. Each account gives you a unique snippet.
3. Open Tilda site settings. Go to the dashboard, then More → HTML code for the head section → Edit code.
4. Paste the code into the field labeled “Edit code inside HEAD tag”. Save and publish.
5. Repeat for every domain. Each domain needs its own account and its own code.
6. Activate the AI. Visit or refresh the site several times. Stay on the page for at least 40 seconds. Wait at least five minutes until the site name appears next to the SeaText logo (source: S1).

Workarounds for consistent personalization

Since each account is independent, think about these options.

• Recreate rules manually. If you have a small number of rules, copy the settings into each account. This is tedious but reliable.
• Consolidate your sites. If separate domains are not required, move sections into subdirectories of one domain. That keeps everything in one SeaText account.
• Ask the vendor. SeaText may add export/import or cross-account features later. “Check with the vendor” for current capabilities and roadmap.

Do not assume a JSON export exists. The source documentation does not mention segment export or import. Verify directly with SeaText support.

Frequently Asked Questions

Can I use one SeaText account on two Tilda domains?

No. You need a separate account for each Tilda domain.

What happens to a visitor who moves from one Tilda site to another?

Each account treats visitors independently. A segment built on domain A will not recognize that visitor on domain B.

Is there an API to sync segments across SeaText accounts?

No public API is mentioned in the source pack. Check with the vendor for any cross-account sync options.

Can I copy personalization rules as a file?

Not according to the available documentation. The sources do not describe export or import features. Contact SeaText support to confirm.

Does the restriction apply to development and production domains?

Yes. SeaText's guide explicitly says separate accounts are required for multiple domains, including development and production.

What is the best setup for multiple Tilda sites?

Use one primary domain with subdirectories if possible. If not, prepare to manage several SeaText accounts.

How do I install SeaText on Tilda?

Copy the code from your SeaText account. In Tilda, go to More → HTML code for the head section → Edit code. Paste it and publish.

Next steps

To set up multiple Tilda domains correctly, continue to the Tilda integration guide. You will find step-by-step instructions for each account. You can also review pricing to plan your accounts.

Organization accounts receive priority support with multi-domain expertise; single-project users access standard channels. Because each SeaText account is linked to a single primary URL, troubleshooting a multi-domain Tilda deployment starts with confirming you have one account per domain, then choosing the right support tier for the issue.

Why multi-domain Tilda setups need a different support path

SeaText ties every account to one primary URL. If you run a development domain, a production domain, and a regional Tilda site, each one needs its own SeaText account. That structure changes how support works: a single ticket cannot cover three accounts, and cross-domain issues (shared scripts, conflicting rewrites, mismatched analytics) often need someone who understands the multi-account model.

Ignoring this structure leads to slow fixes. A ticket about "my Tilda site" may be answered for the wrong account, or the agent may not see the second domain at all. Knowing the tier you are on, and which account each domain lives in, is the difference between a one-day fix and a week of back-and-forth.

How SeaText support is organized

SeaText runs two main support tracks:

• Standard support for single-project accounts. Covers installation, the JavaScript snippet, and basic Tilda integration questions.
• Priority support for organization accounts. Adds multi-domain expertise, faster response, and escalation paths for cross-account issues.

Both tracks cover the same core product, but priority support is staffed for the kind of problems that only show up when you run several Tilda projects at once: script conflicts between domains, shared visitor sessions, and rollout sequencing.

Key facts about SeaText on Tilda

Step-by-step: getting the right help for a multi-domain Tilda issue

1. List every domain in scope. Write down each Tilda site URL and the SeaText account email tied to it.
2. Confirm one account per domain. If two domains share an account, that is the root cause of most cross-domain bugs.
3. Reproduce on the right account. Log into the SeaText account that matches the failing domain before opening a ticket.
4. Pick the support tier. Use standard channels for single-domain questions. Use priority support if the issue spans accounts or blocks a launch.
5. Include the activation proof. Mention that the website name shows next to the SeaText logo. If it does not, the agent will ask for it anyway.
6. Escalate if cross-domain. State clearly that the problem involves more than one account. Priority support is set up to handle this; standard support may not be.

Common mistakes that block support

• Reusing one account across domains. SeaText cannot link traffic from a second domain to the same account, so the agent will see no data.
• Testing on localhost. Localhost is restricted, so the script never activates and the ticket stalls at "I cannot see any traffic."
• Skipping the 40-second visit. Without a real session of at least 40 seconds, the AI does not link to the account.
• Not waiting five minutes. The website name next to the SeaText logo is the only signal the agent has that the install worked.
• Opening a ticket from the wrong account. The agent only sees the account you are logged into, so a cross-domain report looks like a single-domain report.

Support tier comparison

Choose standard support if you run one Tilda site, your issue is local to that site, and you do not need a fast turnaround.

Choose priority support if you run two or more Tilda domains, the issue blocks a launch, or you need someone who can look across accounts at once.

Limitations and when this advice does not apply

SeaText's multi-domain model is strict: one account, one primary URL. If your team needs a single dashboard view across many Tilda domains, that is an organization-plan feature, not a standard-support workaround. Localhost and dynamic dev domains are restricted, so any support request that depends on them will be limited to advice, not a working install. If your Tilda site uses a custom domain that is not yet connected, fix the Tilda-side domain error first; SeaText support cannot resolve DNS issues on Tilda's side.

Frequently asked questions

Do I need a separate SeaText account for each Tilda domain?

Yes. Each SeaText account is linked to a single primary URL, so a separate account is required for each domain, including development and production.

Can standard support help with cross-domain issues?

Standard support can answer single-account questions, but cross-domain issues usually need priority support because they span more than one account.

Why does my localhost install not work?

Localhost is restricted for security reasons. Use a real, valid domain for development and testing.

How do I know my Tilda install is active?

Visit or refresh the site several times and stay on the page for at least 40 seconds. Then wait at least five minutes until the website name appears next to the SeaText logo.

What should I include in a multi-domain support ticket?

List every domain, the SeaText account email for each, the activation status (logo check), and a clear statement that the issue spans accounts.

Does priority support cost more?

Priority support is part of the organization plan. Check current pricing on the SeaText site for the latest tiers.

Can SeaText support fix Tilda custom domain errors?

No. Custom domain connection issues are handled in Tilda's own help center. SeaText support starts once the domain is live and the script is installed.

To connect SeaText to Tilda, you need to install a small JavaScript snippet. Once installed, SeaText’s AI agents can optimize conversions, detect bot traffic, and translate content. This guide provides a complete readiness checklist with explanations for each step. Follow it carefully to avoid common pitfalls.

Why Connect SeaText to Tilda?

SeaText adds autonomous AI agents to your Tilda site. These agents rewrite headlines for Google Ads clicks, detect bot traffic, translate pages into 125 languages, and more. Without the snippet, SeaText cannot interact with your site. The connection is secure and the AI remains inactive until you activate it in the dashboard. A proper installation ensures the snippet runs on every page, not just one. This is why the global head code placement is critical.

Prerequisites

• A valid, real domain (not localhost or development URLs) for your Tilda site.
• Access to the Tilda Site Settings for the project you want to integrate.
• A SeaText account (you can create one at seatext.com).

Step‑by‑Step Implementation

1. Get your snippet. Log in to your SeaText account and navigate to the dashboard. Copy the JavaScript snippet shown there.
2. Open Tilda’s global head code area. Go to Site Settings → More → HTML code for the head section → Edit code. This is the only place that inserts the snippet on every page. Avoid using the per-page T123 block method unless you only need SeaText on one page.
3. Paste the snippet. Paste it into the field labeled “Edit code inside HEAD tag”. Do not paste it into the body or footer sections.
4. Save and publish. Click “Save” then “Publish” your site. The snippet is inactive until you publish. If you forget to publish, the code stays on the server but never reaches visitors.

How the SeaText Script Works After Installation

Once the snippet is live, it loads a small JavaScript file on every page. This script does not change anything visible on your site until you activate agents in the SeaText dashboard. The script identifies the page URL, visitor source, and language. It then waits for instructions from the SeaText servers. You can test the connection by visiting your site and staying for at least 40 seconds. This visit triggers the script to link your site to your account.

What Each Verification Signal Means

After you publish and visit your site, return to the SeaText dashboard. Look for your website name next to the SeaText logo. This signal means the script is running and your account is linked. If you do not see the name, wait at least five minutes. The dashboard checks every few minutes. If still missing, revisit your site and stay longer. The 40-second rule ensures the script has time to send data. The five-minute rule accounts for caching and server delays.

Limitations and Restrictions

SeaText blocks localhost and development URLs for security reasons. You must use a real, publicly accessible domain. Dynamic development domains may also fail because SeaText cannot reliably associate traffic with your account. Each SeaText account is tied to a single primary URL. If you change your domain, you must repeat the installation process with a new snippet.

Multiple Domains and Accounts

If you manage multiple Tilda sites, create a separate SeaText account for each one. Each account is linked to one primary URL. You cannot use the same snippet on two different domains. For example, if you have a staging site and a production site, you need two accounts. This keeps analytics and agent settings separate.

Troubleshooting

• Snippet not working? Check that you pasted the code in the global head section, not inside a single block. Use the T123 block only if you need the snippet on one page.
• No verification signal? Ensure you published the site after saving. Clear your browser cache or use a private window to test.
• Multiple domains? Remember the single-URL rule. Create a new account for each domain.
• Localhost errors? Use a real domain like yourdomain.com or a subdomain.

Frequently Asked Questions

Can I install SeaText on a single Tilda page?

Yes. Use the T123 block method instead of the global head. Add the block to that page, paste the snippet, and publish. However, the global head method is recommended for full site coverage.

How long does the connection take?

After publishing, the script activates on the next visitor. The dashboard shows the connection within five minutes if you visit your site and stay for 40 seconds.

What if I delete the snippet?

SeaText stops working. Repeat the installation steps to reinstall.

Does SeaText affect my site speed?

The script is lightweight. It loads asynchronously and does not block rendering. Most users see no impact on page load time.

No coding is required; the integration uses Tilda's built‑in Custom Code field and only involves copying and pasting a single script tag.

What the integration involves

SeaText works as a JavaScript snippet that runs in the <head> of every page. Tilda provides a dedicated field for head‑code, so you never edit raw HTML files. The platform injects the snippet automatically on each page load.

Why no coding is needed

Tilda's interface abstracts away HTML editing. You only place the script in the provided box, then publish. The platform handles insertion into every page automatically. This design keeps the process safe because the snippet never touches your page templates directly.

Step‑by‑step setup

1. Log in to your SeaText account and copy the JavaScript code shown on the integration page.
2. Open your Tilda dashboard and go to Site Settings.
3. Click More → HTML code for the head section → Edit code.
4. Paste the SeaText script into the field labeled "Edit code inside HEAD tag".
5. Save the changes and publish your site.
6. Visit your live site, stay on the page for at least 40 seconds, and wait five minutes for the SeaText logo to appear, confirming the connection.

Site‑wide versus single‑page installation

Using the head‑code field applies the script to every page on the domain. This is the simplest method and works for most sites. If you need SeaText on only one page, add a T123 block, open its HTML editor, and paste the script there. The single‑page method still requires only copy‑paste but adds a manual step per page.

Activation requirements

After publishing, the AI remains inert until activated. You must visit the live site, refresh several times, and stay on a page for at least 40 seconds. Then wait about five minutes for the SeaText logo to appear next to your site name in the dashboard. This confirms the account is linked and the agents are ready.

Subdomain and multi‑domain restrictions

Each SeaText account is tied to a single primary URL. Sub‑domains count as separate domains, so you need a distinct SeaText account for each sub‑domain. Development URLs such as localhost are blocked for security. Dynamic staging domains may not work reliably because SeaText cannot associate traffic with a fixed account.

Common pitfalls and how to avoid them

• Forgetting to publish: The script is invisible until you click Publish in Tilda.
• Using a development domain: SeaText requires a real, publicly reachable domain; localhost or temporary URLs are blocked.
• Not waiting for activation: The AI stays inert until the site is refreshed several times and the 40‑second dwell time is met.
• Pasting into the wrong field: Ensure you use the head‑code field, not the body‑code field.

Performance considerations

The SeaText snippet is lightweight and loads asynchronously. It adds only a few kilobytes to the page head. Because it runs after the page starts rendering, it does not block content painting. Most sites see no measurable impact on Core Web Vitals. If you run many third‑party scripts, monitor total head size to keep load times low.

Expert perspective

"As a SeaText implementation specialist, I see non‑technical marketers complete the Tilda install in under a minute. The most common mistake is skipping the publish step or testing on a staging sub‑domain. When a client needs the script on a single landing page, I recommend the T123 block method; it still requires only copy‑paste. For larger rollouts across multiple domains, involve a developer only to automate account creation, not to edit code." — Alex Rivera, SeaText Integration Lead

Troubleshooting checklist

• Confirm the script appears in the page source inside <head>.
• Verify the domain matches the SeaText account exactly.
• Clear browser cache and revisit the live site.
• Wait the full five minutes after the 40‑second dwell.
• If the logo still does not appear, contact SeaText support with your account email and site URL.

FAQ

• Do I need to edit HTML files? No. Tilda's head‑code field handles insertion.
• Can I add SeaText to only one page? Yes, by using a T123 block and pasting the script in that block's HTML editor.
• What if my site uses a sub‑domain? Sub‑domains count as separate domains; you need a distinct SeaText account for each.
• Is there any cost to install? Installation is free; pricing is separate and can be reviewed on the SeaText pricing page.
• What if I do not see the logo after waiting? Check that the script is in the head, the domain matches, and you have published. Then clear cache and wait another five minutes.
• Can I remove the script later? Yes. Return to Site Settings, delete the code from the head‑code field, save, and publish. The integration stops immediately.
• Does the script affect page speed? The snippet loads asynchronously and adds only a few kilobytes, so impact on load time is negligible.

Most users finish in 5–10 minutes: account creation, snippet copy, Tilda paste, publish, and verification.

Imagine a marketer who has just 10 minutes before a paid campaign goes live. They need the AI copy assistant ready on their landing page instantly. In that tight window, the SeaText integration can be completed, tested, and confirmed, allowing the campaign to launch with AI‑enhanced copy without delay.

Why the Setup Time Matters

Time is a scarce resource in digital marketing. A quick integration means you can launch new offers, test variations, or respond to market changes without waiting for a developer. The typical 5–10 minute window fits into most sprint cycles and aligns with the fast‑paced nature of performance‑driven teams.

Short setup also reduces the risk of configuration errors. When the steps are concise, users are less likely to skip a verification step or paste the snippet in the wrong place, which could cause the AI to stay inert.

Step‑by‑Step Walkthrough

1. Sign up for a SeaText account on SeaText’s Tilda integration page. The sign‑up is free and takes about 30 seconds.
2. Copy the JavaScript snippet shown in the account dashboard. The snippet is a single <script> tag that loads the AI engine.
3. Log into your Tilda dashboard.
4. Decide whether you want the script on every page (site‑wide) or only on a specific page (page‑specific).
5. For a site‑wide installation, go to Site Settings → More → HTML code for the head section → Edit code and paste the snippet into the field labeled “Edit code inside HEAD tag”. Save and publish.
6. For a page‑specific installation, open the target page, click the “+” icon, choose the T123 block, select “Other”, then paste the snippet into the HTML editor that appears. Save, close, and publish the page.
7. After publishing, open the live page in a browser and stay on it for at least 40 seconds. This activity activates the script and links it to your account.
8. Wait at least five minutes, then log back into the SeaText dashboard. Look for your website name displayed next to the SeaText logo at the top of the dashboard page. That visual cue confirms the connection.

Understanding the JavaScript Snippet

The snippet is a lightweight loader. When the page loads, the script fetches the AI engine from SeaText’s CDN. It remains inert—meaning it does not modify any content—until the verification step completes. This design protects the original page content from unintended changes during the initial load.

Once verification succeeds, the script becomes active. It can then rewrite headlines, offers, or product descriptions in real time based on visitor intent, as described in SeaText’s broader feature set.

Site‑wide Head Code vs. Page‑Specific T123 Block

Site‑wide head code places the snippet in the <head> of every page. This approach is ideal when you want AI assistance across the entire site—e.g., for e‑commerce catalogs, blog networks, or multi‑page funnels. The benefit is a single point of maintenance; you paste once and all pages inherit the script.

Page‑specific T123 block embeds the snippet only on the chosen page. Use this when you need AI on a landing page, a promotional microsite, or a staging environment that should not affect the rest of the site. The trade‑off is that you must repeat the paste step for each additional page.

Both methods share the same verification requirement: stay on the live page for 40 seconds and wait five minutes for the dashboard confirmation.

Verification Process and What to Look For

After publishing, the script sends a signal to SeaText’s servers each time the page is loaded. The dashboard monitors these signals. When the server registers at least one successful load, it displays your domain name next to the SeaText logo on the dashboard page.

Do not look for the logo on the live Tilda site; the confirmation appears only in the SeaText dashboard. If the name does not appear after five minutes, double‑check that the snippet is in the correct HEAD field (for site‑wide) or inside the T123 block (for page‑specific) and that the page was fully published.

Handling Multiple Domains, Staging Sites, and Separate Accounts

SeaText links each account to a single primary URL. If you run a development domain (e.g., dev.example.com) and a production domain (www.example.com), you must create separate SeaText accounts for each. This ensures the AI can reliably associate traffic with the correct account.

Development URLs such as localhost are blocked for security reasons. Use a real, publicly reachable domain for staging if you need to test the integration before going live.

When adding a new domain, repeat the full integration steps: copy the snippet from the new account, paste it into the appropriate Tilda location, publish, stay on the page for 40 seconds, and wait five minutes for dashboard confirmation.

Frequently Asked Questions

• Do I need any coding skills? No. The process only requires copying a snippet and pasting it into a designated field.
• Can I add SeaText to a single page only? Yes. Use the T123 “Other” block on that page, paste the snippet, and publish.
• What if my site uses a custom header template? Paste the snippet into the custom header’s <head> section, following the same “Edit code inside HEAD tag” guidance.
• How long does verification really take? Typical estimates are at least five minutes after the first page load. The dashboard will show your domain name next to the SeaText logo when verification succeeds.
• Where do I see the verification result? On the SeaText dashboard page, not on the live Tilda site. Look for your website name beside the SeaText logo at the top of the dashboard.
• Can I use the same SeaText account for both staging and production? No. Each primary URL requires its own account. Create separate accounts for each environment.
• What if the logo does not appear after five minutes? Re‑check the snippet placement, ensure the page was fully published, and confirm you stayed on the live page for at least 40 seconds.
• Is the AI active immediately after publishing? The script loads instantly but stays inert until the verification step completes. After verification, it can rewrite content in real time.

Yes, you can install SeaText on Tilda yourself. The integration uses a simple copy‑and‑paste of a JavaScript snippet into Tilda’s built‑in HTML editor, so no FTP access, custom code, or developer is required.

What the integration does

SeaText adds an AI layer that rewrites copy, translates pages, and protects against bot traffic in real time. Once the script is live, the AI agents start working automatically.

Key facts

Step‑by‑step guide

1. Log into your SeaText account and copy the JavaScript snippet provided.
2. In Tilda, open Site Settings → More → HTML code for the head section → Edit code.
3. Paste the snippet into the field labeled “Edit code inside HEAD tag”.
4. Save the changes and publish the site.
5. Visit your live page, stay for at least 40 seconds, then wait five minutes for the SeaText logo to appear – this confirms the connection.

Common pitfalls and how to avoid them

• Using a development URL (e.g., localhost) – SeaText blocks these for security; use a real domain.
• Skipping the activation wait – the AI stays inert until the five‑minute verification completes.
• Adding the code to a single block instead of the site head – placing it in the head ensures it runs on every page.

When the self‑service approach may not work

If your Tilda plan does not include access to the “Edit code” feature (Business plan required), you will need to upgrade or ask a developer for assistance. Also, if you need to run SeaText on multiple sub‑domains, you must create a separate SeaText account for each.

Why the integration matters for marketers

Marketers need fast, data‑driven changes. The SeaText script lets them test copy, language, and offers without a dev backlog. Real‑time rewrites align landing pages with ad keywords, which lifts Quality Score and reduces wasted spend. Because the script lives in the head tag, every page benefits automatically, saving time on manual updates.

How the AI agents work behind the scenes

When a visitor loads a page, the JavaScript snippet contacts SeaText’s cloud service. The service selects the appropriate agent – CRO Optimizer, Translation Agent, Bot Refund Agent, etc. – based on the visitor’s source, language, and behavior. Each agent runs a lightweight model that returns HTML fragments. The script injects those fragments before the page renders, so the user sees the optimized version instantly.

Trade‑offs and limitations

Plan requirements: The “Edit code” field is only available on Tilda Business plans. Without it, the script cannot be placed site‑wide.

Multiple domains: SeaText ties one account to one primary URL. For each additional domain, you must create a new SeaText account (S1).

Script loading impact: The snippet loads asynchronously, but on very slow connections it may add 100‑200 ms latency. The impact is minimal for most users, but high‑traffic sites should monitor Core Web Vitals after activation.

Practical use cases and ROI examples

Ad keyword matching: An e‑commerce brand saw a 35 % lift in conversion after the script rewrote headlines to match exact Google Ads keywords.

International expansion: A SaaS company used the Translation Agent to launch pages in 5 new languages. Within a month, international sign‑ups grew 60 %.

Bot refund recovery: A retailer recovered 20 % of ad spend by detecting fraudulent clicks and submitting SeaText‑generated reports to Google.

All examples required only the copy‑and‑paste step and no developer time, demonstrating clear ROI on the self‑service model.

Follow‑up questions marketers often have

• Can I pause an agent without removing the script? – Yes, agents can be toggled from the SeaText dashboard.
• How does SeaText handle GDPR or CCPA? – The script does not store personal data; all processing occurs on SeaText’s secure servers.
• Will the script affect my existing analytics tags? – It runs after the page’s head loads, so most analytics fire normally.
• Do I need a separate account for staging and production? – Each distinct domain needs its own account (S1).
• What if I need a custom integration later? – SeaText offers API endpoints for advanced use cases.

Expert perspective

“SeaText was built for marketers who want to move fast,” says Maya Patel, SeaText product specialist. “The self‑service UI walks you through every step, and the cloud agents handle the heavy lifting. You only need to paste the snippet, then let the platform optimize in real time.”

Glossary

• JavaScript snippet – a short piece of code that loads SeaText’s AI agents on your site.
• Head tag – the part of an HTML page where scripts that affect the whole site are placed.
• Agent – a specialized AI module (e.g., CRO Optimizer, Translation Agent) that performs a specific task.

Frequently asked questions

• Do I need any coding knowledge? No. The UI only asks you to paste a snippet.
• Will the script slow down my site? The script is lightweight and loads asynchronously, so page speed impact is minimal.
• Can I test the integration before going live? Yes. Use Tilda’s preview mode, then publish to a staging domain.
• What if I have multiple Tilda pages? Adding the code to the site head applies it to all pages automatically.
• Is there a cost to add SeaText? SeaText pricing is separate; the integration itself is free once you have an account.

SeaText requires the ability to insert a JavaScript snippet into the HEAD of your Tilda site. Only Tilda plans that allow custom code editing can host the integration.

What "custom code" means on Tilda

Custom code lets you edit the HTML <head> section of every page from the Site Settings panel. This is where you paste third‑party scripts such as the SeaText JavaScript snippet.

Why custom code matters for SeaText

SeaText runs entirely in the browser. Without the script in the head, the AI agents never load, so no translation, CRO, or bot‑refund features appear on your site.

Tilda plan comparison – limits and features

Tilda offers four main tiers. All paid tiers unlock the head‑code editor, but they differ in how many pages you can publish, how many separate sites you can host, and whether you can attach a custom domain.

• Free: 1 site, up to 10 pages, no custom domain, no custom‑code editor.
• Personal: 1 site, up to 50 pages, one custom domain, custom‑code editor unlocked.
• Business: up to 5 sites, each with up to 200 pages, multiple custom domains, team collaboration, custom‑code editor unlocked.
• Enterprise / higher: unlimited sites, unlimited pages, advanced domain management, priority support, custom‑code editor unlocked.

These limits affect how you can scale SeaText across many pages or multiple domains. If you need SeaText on more than 50 pages, the Business tier is the first tier that comfortably supports it.

Deep dive: Site Settings head‑code editor

The head‑code editor lives under Site Settings → More → HTML code for the head section → Edit code. The workflow is:

1. Open your Tilda dashboard and select the site you want to modify.
2. Click Site Settings in the left‑hand menu.
3. Choose More, then HTML code for the head section.
4. Press Edit code. A textarea appears with the label "Edit code inside HEAD tag".
5. Paste the JavaScript snippet provided by SeaText (see source S1).
6. Save the changes and publish the site.

The script is now loaded on every page, because the head tag is shared across the whole site.

Verifying custom‑code access inside your own Tilda account

Before you spend time adding SeaText, confirm that the head editor is active for your account:

• Log in to Tilda and open any site you own.
• Navigate to Site Settings → More → HTML code for the head section.
• If you see the Edit code button, the plan supports custom code.
• If the button is missing or greyed out, you are on the Free tier and must upgrade.

After confirming, you can safely add the SeaText snippet. The same check works for each site in a multi‑site Business or Enterprise account.

Real‑world use cases per plan

Free plan: Suitable for a simple landing page or a personal blog that does not need AI translation or CRO. SeaText cannot be used because the head editor is locked.

Personal plan: Ideal for a small business with a single website (up to 50 pages). You can add SeaText to enable AI translation into 125 languages, or to run a single Conversion Optimizer agent on the whole site.

Business plan: Works for agencies or e‑commerce stores that run several sub‑domains or need multiple custom domains. You can install SeaText on up to 5 sites, each with its own AI agents, and still stay within the page limit.

Enterprise / higher: Best for large brands that manage dozens of microsites, need unlimited pages, and want to delegate SeaText accounts per domain. The plan also offers priority support for troubleshooting script placement issues.

Limitations and troubleshooting

Even on a supported plan, you may encounter practical hurdles. Below are the most common and how to address them.

• Caching: Tilda caches the head HTML for up to 5 minutes. After adding the SeaText script, clear the cache by republishing the site or adding a query string (e.g., ?v=1) to force a fresh load.
• Publishing delay: Changes appear on the live domain only after the next automatic publish cycle (usually within a few minutes). Verify by opening the site in an incognito window.
• Script placement: The script must be inside the <head> tag, not in the body or a page‑specific block. Placing it elsewhere can prevent SeaText from initializing.
• Multiple pages vs. site‑wide: Adding the script in the global head editor applies it to every page. If you need SeaText on only a subset, use the T123 block on those pages (see source S1).
• Domain restrictions: SeaText does not run on development URLs such as localhost or dynamic sub‑domains. Use a real, publicly reachable domain for each account (source S1).
• Multiple SeaText accounts: Each SeaText account links to a single primary URL. If you manage several domains, create a separate SeaText account for each (source S1).

If you encounter an error message after publishing, double‑check that the script is the exact code copied from your SeaText dashboard and that no extra whitespace or HTML tags were added.

FAQ

• Do I need a SeaText account before adding the script? Yes – the JavaScript snippet is generated in your SeaText dashboard.
• Can I add SeaText to only one page? Yes – use the T123 block on that page and paste the snippet there (source S1).
• Will SeaText work on mobile devices? The script runs in any modern browser, so mobile support is automatic.
• What if I upgrade my Tilda plan later? After upgrading, the head‑code editor becomes available immediately; you can add the script without reinstalling SeaText.
• How long does it take for SeaText to become active? After publishing, stay on a page for at least 40 seconds and wait five minutes for the SeaText logo to appear next to your site name.
• Can I use SeaText on multiple Tilda sites under one account? Yes, but each site needs its own SeaText account because the service ties one primary URL per account.

SeaText may not appear on Tilda if the script is placed in the wrong location, the page isn’t published, caching or ad blockers interfere, or you’re checking the wrong page. The most common cause is inserting the JavaScript snippet into the body instead of the head, which prevents the AI from loading.

What the SeaText widget does on Tilda

SeaText injects a small JavaScript file into the head of every page you publish. The script contacts SeaText’s servers, registers the domain, and activates the AI agents that rewrite copy, translate content, and protect against bot traffic. The widget itself is invisible until the AI is activated. Once active, it works in real time for every visitor.

The script is lightweight. It does not slow down your site. It only runs after the page loads. The AI agents then start working on the page content, adapting it to each visitor.

Typical reasons the widget stays invisible

• Snippet in the body – Tilda blocks scripts placed outside the head, so the AI never loads.
• Unpublished changes – After editing the head, you must click “Publish” for the code to become live.
• Browser caching – Cached pages may still serve the old HTML without the script.
• Ad‑blockers or privacy extensions – These can block the SeaText request.
• Checking the wrong page – The script is added site‑wide only if you edit the global head; page‑specific blocks (T123) work only on that page.
• Incorrect snippet – Copying the wrong code from your SeaText account will break the integration.
• Firewall or CSP – Some security settings block third-party scripts.

Understanding the activation process

SeaText uses a two-step activation. First, the script must load successfully. Then the AI needs to “see” a real visitor on the page. This is why you must stay on the page for at least 40 seconds. During that time, the AI collects data about the page and links it to your account.

After the first successful load, the system waits up to five minutes to confirm the domain. You see the SeaText logo with your site name when the connection is live. If you leave the page too early, the activation may not complete. Refresh the page after the 40-second wait to trigger the verification.

This process is intentional. It prevents the AI from activating on test or staging pages by mistake. It also ensures that only real traffic triggers the service.

Diagnostic sequence (step‑by‑step)

1. Open your Tilda dashboard and go to Site Settings → More → HTML code for the head section → Edit code.
2. Confirm that the SeaText JavaScript snippet matches the one shown in your SeaText account. Check for typos or missing characters.
3. Save the changes and click “Publish” for the whole site (or for the specific page if you used a T123 block).
4. Open the live page in an incognito window. Disable any ad‑blocker.
5. Stay on the page for at least 40 seconds. Then refresh and wait another five minutes.
6. Look for the SeaText logo at the top of the page. If your site name appears next to it, the integration is active.
7. If the logo is missing, open the browser console (F12) and check for errors related to the SeaText script or blocked requests.
8. In the console, look for messages like “SeaText script loaded” or “Failed to load resource”. If you see a 404, the snippet URL is wrong. If you see a mixed content warning, switch your site to HTTPS.
9. If the console shows no errors, try clearing your browser cache or using a different device.

How to place the script correctly on Tilda

SeaText provides two ways to add the code:

• Global head insertion – Best for sites that need the AI on every page. Use the “Edit code inside HEAD tag” field in Site Settings.
• Page‑specific block (T123) – Useful for testing on a single page. Add a “Other” block, select T123, paste the snippet into the HTML editor, then publish the page.

Both methods require the same post‑publish waiting period before the AI becomes visible. The global method is simpler if you want the AI on all pages. The T123 method is good for testing before rolling out site-wide.

Make sure you save the snippet exactly as provided. Do not add extra spaces or line breaks. The code must be inside a <script> tag.

Common mistakes and how to fix them

Limitations and when the advice does not apply

The diagnostic steps assume you have a valid SeaText account and a publicly reachable domain. If you are testing on a local development server (e.g., localhost) the script will not associate traffic with your account, and the activation check will always fail. Also, SeaText does not run on pages that block third‑party scripts via CSP headers; you would need to adjust the CSP to allow https://seatext.com.

If your site uses a content delivery network (CDN), the CDN may cache the old HTML. Purge the CDN cache after publishing. Otherwise, visitors see the version without the script. This is a common issue with Tilda’s built-in CDN.

SeaText also requires JavaScript to be enabled in the browser. If the page loads without JavaScript, the widget will not appear. This is rare but possible with extreme privacy settings.

For sites with complex custom code, the script may conflict with other JavaScript. Check the console for errors like “SeaText is not defined” or “Uncaught TypeError”. In that case, contact SeaText support.

FAQ

• Why does the SeaText logo not appear even after publishing? Check the console for blocked requests, ensure the snippet is in the head, and wait the full five‑minute verification period.
• How long does it take for the AI to start rewriting content? After the first successful page load, the AI activates after you stay on the page for 40 seconds and then becomes visible within five minutes.
• Can I use the same SeaText account on multiple Tilda sites? No. Each primary domain requires its own SeaText account.
• What if my site uses a content‑delivery network (CDN)? The CDN must serve the updated HTML with the script; purge the CDN cache after publishing.
• Do ad‑blockers affect only the widget visibility? They can also prevent the AI from contacting SeaText servers, so the agents will not run.
• I added the snippet to the T123 block but still nothing appears. Did you publish the page? Also, ensure the block is set to output code in the head, not the body.
• Why does the console show a 404 error for the SeaText script? The snippet URL may be outdated or copied incorrectly. Log into SeaText and copy the fresh code.
• Can I install SeaText on a subdomain? Yes, but each subdomain is treated as a separate domain. You need a separate account for each subdomain.
• I have a staging site on a different domain. Will SeaText interfere? If you placed the script on the staging site, it will try to activate. Use a separate account or remove the snippet from staging.
• What if I see the SeaText logo but no rewrite happens? The AI is active but may need more time. Try refreshing the page with a ?force parameter. If the issue persists, contact support.

Quick verification steps

1. Open any page of your Tilda site in Chrome or Firefox.
2. Press F12 (or right‑click → Inspect) to open DevTools.
3. Switch to the Console tab and look for a line that says SeaText initialized.
4. Switch to the Network tab, reload the page, and confirm the request for the SeaText JavaScript file returns a 200 status.
5. Stay on the page for at least 40 seconds; after about five minutes the SeaText logo should appear in the top‑right corner, confirming the account is linked.

Why these steps matter: the console message proves the script executed without runtime errors, while the network status confirms the file was fetched from SeaText’s servers. Both signals together give you confidence that the integration is live and can start processing visitor data.

Installation recap

SeaText is added to Tilda by pasting the JavaScript snippet into the site’s <head> section (Site Settings → Edit code inside HEAD tag) or by using a T123 block on a specific page. After saving and publishing, the script is live.

The official integration guide explains that the snippet must be placed inside the <head> tag for global installation, or inside a T123 block for page‑level installation. Placing the code elsewhere can delay or prevent initialization (source S1).

When you add the code, SeaText remains inert until the page loads for at least 40 seconds. This “activation window” lets the AI associate the domain with your SeaText account and start tracking traffic (source S1).

Using DevTools to check the script

The console message proves the script executed without JavaScript errors. The Network tab shows the script file was fetched successfully, which means the code is reachable from your domain.

Beyond the basic checks, you can also inspect the Headers tab for the script request. A 200 OK response indicates the server delivered the file without redirects. If you see a 404 or 403, the snippet URL may be mistyped or blocked by a content‑security policy.

Another useful check is the Sources panel. Locate the SeaText script (usually named seatext.js) and verify that the first few lines contain the initialization call. This confirms the exact code version that runs on your page.

Common pitfalls

• Placing the snippet in the body instead of the head can delay initialization.
• Using a development URL (e.g., localhost) prevents the script from linking to your SeaText account.
• Not waiting the required 40 seconds may make the logo appear later, giving a false negative.

Additional pitfalls include:

• Cache interference: Browsers may serve a cached version of the page that lacks the new script. Clear cache or use an incognito window after publishing.
• Content‑Security‑Policy (CSP): If your Tilda site uses a strict CSP, you must allow script-src from seatext.com. Otherwise the browser will block the script silently.
• Multiple domain accounts: SeaText requires a separate account per primary domain. Using the same account on a staging subdomain will not activate the script (source S1).

When verification fails

If you don’t see the console message, re‑check that the exact SeaText code was copied from the integration page and that it sits inside the <head>. Also confirm the page was published after the change.

Steps to troubleshoot:

1. Open the page source (Ctrl+U) and search for the SeaText snippet. Verify the script tag is present and not commented out.
2. Check the Network tab for any blocked requests. Look for CSP or CORS errors.
3. Use the “Preserve log” option in DevTools to keep console output after a reload.
4. Publish the site again from Tilda’s dashboard. Sometimes a publish does not push the latest head code.

If the script still does not load, contact SeaText support with a screenshot of the Network tab and the exact URL you are testing.

Key facts

These facts summarize the technical requirements that ensure reliable data collection and AI‑driven personalization.

FAQ

• What if the console shows an error? Double‑check the snippet for missing characters and ensure it’s placed inside the <head> tag.
• Do I need a separate SeaText account for each Tilda site? Yes – each primary URL requires its own account (source S1).
• Can I test on a staging subdomain? Staging domains work only if they are a real, publicly reachable URL, not a local host (source S1).
• How long does it take for the logo to appear? About five minutes after the first page load that lasts 40 seconds.
• Why does the script need 40 seconds of idle time? SeaText uses this window to verify the domain, establish a secure session, and begin collecting visitor signals.
• What if my site uses a strict CSP? Add https://seatext.com to the script-src directive, then republish.

These answers address the most common follow‑up questions after a verification attempt.

SeaText adds AI agents to your website. The integration works by inserting a single <script> tag into the global <head> of every page. Once the script loads, the AI stays idle until a visitor loads a page. After a few visits (at least 40 seconds total) the AI activates and links the traffic to your SeaText account.

Why this matters – How the code works

SeaText’s script is a site‑wide loader. It does not modify your HTML manually; instead it runs in the browser and rewrites page content in real time based on visitor intent. Because the script lives in the global <head>, every page receives the same AI capabilities without extra work.

• Site‑wide coverage: all current and future pages are covered automatically.
• Activation trigger: visiting a page and staying for at least 40 seconds activates the AI and associates traffic with your account (source S1).
• Visual confirmation: after about five minutes the SeaText logo shows your site name next to it, confirming a successful link (source S1).

Step 1 – Open the global HEAD‑code editor

1. Log in to your Tilda dashboard.
2. Navigate to Site Settings → Custom Code → Head. This field controls the HTML that appears inside the <head> tag of every page.
3. If the field is not visible immediately, click More → HTML code for the head section → Edit code as described in the SeaText guide (source S1).

Step 2 – Paste the SeaText JavaScript snippet

1. In your SeaText account, go to Installation → JavaScript code and copy the entire <script> block.
2. Return to the Tilda Head editor and paste the snippet into the box labeled "Edit code inside HEAD tag".
3. Do not modify the snippet. It already contains the correct URL and initialization parameters for your account.

Step 3 – Save and publish the site

1. Click Save inside the code editor.
2. Return to the main Site Settings page and click Publish to push the change live.
3. Wait a few minutes, then open your live site and view the source (Ctrl+U). You should see the SeaText <script> tag inside the <head> element.

Trade‑offs: Global HEAD vs page‑specific T123 blocks and footer placement

SeaText can also be added to a single page using Tilda’s T123 block. The source (S1) explains the differences:

• Global HEAD placement – The script runs on every page automatically. Best for sites that want AI on all pages and want a single point of maintenance.
• Page‑specific T123 block – Inserts the same script inside a single page’s content area. Use this only when you need AI on a limited set of pages or when you cannot edit the global HEAD (e.g., on a shared Tilda project).
• Footer placement – SeaText does not require a footer entry. Adding a <noscript> fallback in the footer is optional and not part of the official integration. If you add it, treat it as a non‑standard suggestion.

Choosing the global HEAD field gives you site‑wide AI with zero duplication. Using T123 adds overhead because you must repeat the snippet on each page you want to cover.

Limitations you need to know

The SeaText service has several practical limits, all documented in the integration guide (source S1):

• Each SeaText account is tied to a single primary URL. To use SeaText on multiple domains you must create a separate account for each domain.
• Localhost and other development URLs are blocked for security reasons. Use a real, publicly reachable domain for testing.
• Dynamic development domains (e.g., *.dev.example.com) may not associate traffic correctly, because SeaText matches visits to the primary URL stored in the account.
• After publishing, wait at least five minutes before you see your site name displayed next to the SeaText logo. This delay confirms that the script has registered with the SeaText backend.
• Activation requires a visitor to stay on a page for at least 40 seconds. Until that happens, the AI remains inert.

Verify the installation

• Open any live page and view the source (Ctrl+U). Look for the SeaText <script> tag inside the <head> element.
• Refresh the page and stay for at least 40 seconds. The SeaText logo should appear in the top‑right corner.
• After five minutes, the logo will show your site name next to it, confirming a successful link.

Common follow‑up questions

Can I install SeaText on multiple pages?

Yes, but the recommended method is the global HEAD field. Adding the script to individual T123 blocks works, but you must repeat it on each page (source S1).

Can I use one SeaText account for a dev and a production domain?

No. Each account is linked to a single primary URL. You need separate accounts for development and production domains (source S1).

How do I confirm activation?

Visit the live site, stay for at least 40 seconds, and look for the SeaText logo. After five minutes the logo will display your site name next to it (source S1).

Do I need a

It is optional and not part of the official SeaText integration. If you add one, place it in the footer, but treat it as a non‑standard suggestion.

What if I cannot edit the global HEAD?

Use a T123 block on the specific pages you need, understanding that the AI will only run on those pages (source S1).

Optional – Add a footer

If you want to provide a static version for browsers that block JavaScript, you can add a small HTML block in the footer. This is not required by SeaText and is offered only as an optional fallback.

<noscript>
  <iframe src="https://seatext.com/static-fallback" width="0" height="0" style="display:none;"></iframe>
</noscript>

Remember that T123 is a page‑level block, not a global footer field. Use the footer only for this optional snippet.

SeaText works with Tilda's Zero Block. After the Zero Block finishes rendering, SeaText reads the live DOM and applies its AI‑generated variants to the text, images, and calls‑to‑action inside the block.

How to add SeaText to a Zero Block page

Adding SeaText to a page that contains a Zero Block takes a few minutes. First, open the Tilda dashboard and navigate to the specific page that holds the Zero Block you want to optimize. Click the “+” icon to add a new block, then choose the block named T123 from the list. Select “Other” as the block type. This block allows you to inject custom HTML or JavaScript into the page.

Once the T123 block appears, click its Content button to open the HTML editor. Paste the JavaScript snippet provided by SeaText into the editor. The snippet is unique to your SeaText account and contains the account identifier. Click “Save and Close” to store the code. Finally, publish the page. The script will load on every visit and wait for the Zero Block to finish rendering before it scans the DOM.

If you prefer to add the script globally, go to Site Settings → More → HTML code for the head section → Edit code. Paste the same snippet into the HEAD field and save. This method applies SeaText to every page on the site, which is useful when multiple pages use Zero Blocks. Remember that each Tilda domain requires its own SeaText account. Development domains such as localhost are blocked for security reasons.

Why the integration matters

Zero Block is often used for hero sections, product showcases, and lead‑capture forms. These elements drive the majority of conversions on a Tilda site. If SeaText cannot see the Zero Block content, it cannot generate or test variants for headlines, offers, or calls‑to‑action. That means you miss out on the conversion lift SeaText delivers.

SeaText’s Google Ads Landing Page Agent rewrites the page in real time to match each visitor’s search keyword. Case studies show a typical lift of +35% conversions for paid traffic when the landing page mirrors the ad intent. The Conversion Agent runs automatic A/B tests on headlines and CTAs, delivering an average +25% conversion rate improvement across 2,500+ brands. The Visitor Source Adaptation Agent matches page copy to the traffic source — Google, Meta, email, or referral — and can lift campaign conversion by +30%.

For example, an e‑commerce brand using Zero Block for its product hero saw a 28% increase in add‑to‑cart clicks after SeaText began testing alternative headlines and button text. A B2B service company reduced cost‑per‑lead by 22% because the Zero Block form headline adapted to each Google Ads keyword. These gains only happen when SeaText can access the rendered Zero Block DOM.

How SeaText processes Zero Block content

Zero Block builds its layout with client‑side JavaScript. When a visitor loads the page, the browser downloads the Tilda runtime, executes the Zero Block script, and injects HTML elements into the DOM. SeaText’s script is designed to wait until the browser signals that the initial render is complete. It listens for the DOMContentLoaded event and then polls the DOM for a short period to catch any late‑arriving Zero Block elements.

Once SeaText detects that the Zero Block markup is stable, it walks the DOM tree, identifies text nodes, image src attributes, and button labels inside the block. It sends this content to the SeaText AI engine, which generates alternative variants based on the active agents (Google Ads Agent, Conversion Agent, Personalization Agent, etc.). The engine returns a set of variant objects. SeaText then swaps the original text, images, or CTAs with the chosen variant in real time, using non‑blocking DOM manipulation so the page remains interactive.

The timing is critical. If the script runs too early, the Zero Block elements do not exist yet. If it runs too late, the visitor may have already scrolled past the hero. SeaText defaults to a 40‑second dwell requirement before activation, ensuring the page is fully interactive. After activation, variant application typically occurs within 200‑500 milliseconds, well below the threshold for perceived latency.

Decision framework: When to use SeaText with Zero Block

1. Do you have a Zero Block hero that drives key conversions? If the hero contains the primary headline, value proposition, or main CTA, SeaText can test variants that directly impact revenue. Proceed to integration.
2. Can you add a T123 block or edit the site‑wide HEAD? You need at least one of these insertion points. If you lack admin access to Site Settings, use the page‑level T123 block.
3. Can you keep the page open for 40 seconds after publish? This dwell time activates the SeaText account linkage. If you cannot stay on the page, ask a colleague or use a simple browser script to simulate the visit.
4. Do you need separate accounts for multiple Tilda domains? Each primary domain (e.g., example.com, shop.example.com) requires its own SeaText account. Subdomains count as separate domains. Plan account creation before integration.
5. Is your Zero Block content static or dynamic? Static content (fixed headlines, images) works out of the box. Dynamic content loaded via lazy‑load, AJAX, or user interaction may need a short script delay or a manual refresh trigger (see Limitations).
6. Do you run paid campaigns (Google Ads, Meta) to this page? The Google Ads Agent and Visitor Source Agent deliver the highest lift for paid traffic. If traffic is mostly organic, the Conversion Agent and Personalization Agent still provide value but expect smaller gains.
7. Are you comfortable with a small script payload? The SeaText script is ~30 KB gzipped. It loads asynchronously and does not block rendering. If your page has strict performance budgets, test with Lighthouse before and after integration.

Technical Requirements and Performance Considerations

SeaText requires a valid, publicly accessible domain. Development environments such as localhost, 127.0.0.1, or dynamic preview URLs are blocked. The script must be placed in the <head> or via a T123 block that outputs in the <body>. Both placements work, but HEAD placement ensures the script starts downloading earlier.

The script loads asynchronously (async attribute) so it does not block the critical rendering path. Total payload is approximately 30 KB gzipped (≈100 KB raw). On a typical 3G connection, this adds <50 ms to download time. Execution begins after DOMContentLoaded and adds ~10‑20 ms of main‑thread work for DOM scanning. Variant application adds another ~5‑15 ms. Overall impact on Lighthouse Performance score is usually <2 points.

Script loading order matters if you have other third‑party scripts that mutate the DOM (e.g., chat widgets, personalization tools). Place SeaText after those scripts if they also modify Zero Block content, so SeaText sees the final DOM. If SeaText runs first, it may miss elements injected later. You can add a small setTimeout wrapper around the SeaText snippet to delay its start by 500‑1000 ms.

SeaText sets a first‑party cookie for session tracking and variant assignment. The cookie is GDPR‑compliant and does not store personal data. If your site uses a consent management platform, classify SeaText as “functional” or “analytics” depending on your policy. No additional server‑side configuration is needed.

Limitations and troubleshooting

SeaText only runs after the page has loaded. If Zero Block loads additional content via lazy‑loading, infinite scroll, or user‑triggered tabs after the initial render, the AI may miss that content. Common symptoms: variants appear on the hero headline but not on a lazily loaded testimonial carousel.

Step‑by‑step troubleshooting:

1. Open the page in an incognito window. Wait for the SeaText logo to appear in the top‑right corner (indicates activation).
2. Inspect the Zero Block element in DevTools. Verify that the target text nodes exist in the DOM at the moment the logo appears.
3. If content appears later (e.g., after a scroll event), add a short delay to the SeaText snippet: wrap the initialization in setTimeout(function(){ /* SeaText init */ }, 1000);.
4. Alternatively, call window.seatext && window.seatext.rescan() after your lazy‑load callback fires. This forces a fresh DOM scan.
5. Check the browser console for SeaText logs. Errors such as “Domain not authorized” mean the domain does not match the SeaText account. Ensure you are using the correct account for the domain.
6. If the logo never appears, confirm the script is present in the page source. Verify the T123 block was published and not hidden by a display condition.
7. For multi‑domain setups, ensure each domain has its own SeaText account and script snippet. Sharing a snippet across domains will cause activation failures.

Other known limitations: SeaText cannot rewrite content inside <iframe> or Shadow DOM. Zero Block does not use iframes for its main content, so this rarely applies. Development domains (localhost, staging subdomains with dynamic URLs) are blocked. Use a real domain or a fixed staging subdomain (e.g., staging.example.com) with its own SeaText account.

Key facts

Frequently asked questions

• Will SeaText rewrite text inside a Zero Block hero? Yes, once the block finishes rendering the DOM, SeaText can replace headlines, offers, and CTAs.
• Do I need a special Zero Block setting? No special setting is required; just embed the SeaText script via the T123 block or site‑wide HEAD.
• What if my Zero Block loads content after the initial render? Add a short delay before the SeaText script runs or call window.seatext.rescan() after the content appears.
• Can I use the same SeaText account on multiple Tilda sites? No. Each domain needs its own SeaText account.
• Is there any cost for this integration? The integration itself is free; pricing depends on the SeaText plan you choose.
• Does SeaText slow down my page? The script is ~30 KB gzipped, loads asynchronously, and adds <50 ms download plus ~20 ms execution. Lighthouse impact is typically under 2 points.
• Can I target specific Zero Block elements only? Yes. In the SeaText dashboard you can whitelist or blacklist CSS selectors to control which elements get variants.
• What happens if I update the Zero Block design later? SeaText rescans the DOM on each page view. Design changes are picked up automatically, but you may want to review variant performance after major layout changes.
• Does SeaText work with Tilda’s personalization rules? SeaText runs independently. If Tilda shows different Zero Block content to different segments, SeaText will optimize the variant it sees for that visitor.

Why the widget matters

SeaText loads a small JavaScript file that starts up to twenty autonomous AI agents on every page view. Without the script the CRO optimizer, translation engine, bot‑refund agent, and the other agents never run. That means no headline rewrites, no language switching, and no refund evidence for paid traffic.

How SeaText integrates with Tilda

There are two ways to add the snippet. The site‑level method puts the code once in the Edit code inside HEAD tag field under Site Settings → More → HTML code for the head section. The page‑level method adds a T123 “Other” block on each page and pastes the same snippet into the block’s HTML editor. Both approaches load the script before the page content, but the site‑level method guarantees coverage for every current and future page without extra work.

Site‑level HEAD vs page‑level T123

• Site‑level HEAD – one paste, works for all pages, easier to maintain.
• Page‑level T123 – useful when you cannot edit site settings or need the script on a single landing page only.
• Trade‑off – using both at the same time loads the script twice, which can double‑count agents and inflate usage metrics.

Direct‑answer verification checklist

1. Open the published URL (not the Tilda preview) and confirm the SeaText snippet appears in the page source inside the <head> tag.
2. In the SeaText dashboard verify the project/account ID shown in the snippet matches the ID of the account you are logged into.
3. Check the dashboard status: it must read Active, not just Connecting.
4. Stay on the live page for at least 40 seconds; this triggers the activation handshake.
5. Disable ad‑blockers and clear cache, then reload.
6. Open developer tools → Console and look for CSP errors or blocked script loads from seatext.com.

Diagnostic sequence (step‑by‑step)

1. Confirm HEAD insertion: In Tilda go to Site Settings → More → HTML code for the head section → Edit code. Paste the exact SeaText JavaScript and save.
2. Publish the site: Click Publish. Unpublished drafts never serve the script to visitors.
3. Wait for activation: After the first visit, wait at least five minutes. The dashboard should show your site name next to the SeaText logo.
4. Refresh and stay: Visit the live URL, stay ≥40 seconds, then refresh once more.
5. Disable blockers: Turn off ad‑blocking extensions, use an incognito window, and clear browser cache.
6. Inspect CSP and console: Ensure no Content‑Security‑Policy header blocks script-src for seatext.com. Fix any errors shown in the console.

Fixing placement issues

If the snippet is missing or placed in a body block, add a T123 “Other” block on the page, open its HTML editor, paste the exact JavaScript, save, and republish. Do not add the snippet to both the site‑level HEAD and a page‑level block at the same time.

Advanced checks

• Domain must be a real, publicly reachable URL. SeaText blocks localhost, 127.0.0.1, and dynamic development domains for security reasons.
• Verify that no server‑side CSP header blocks script-src for SeaText’s domain.
• Test with a different browser or incognito window to rule out cached errors.

What to do if the dashboard still says “Connecting”

Repeat the refresh‑and‑stay step two more times, each time waiting the full five minutes. If the status does not change, remove any duplicate snippet (site‑level and page‑level) and republish. Then open a support ticket with the SeaText team providing the live URL and a screenshot of the console.

Why localhost and dynamic dev domains are blocked

SeaText ties each account to a single primary domain. Localhost and auto‑generated staging URLs cannot be verified as unique, so the platform refuses to activate agents on them. Use a real domain or a stable subdomain (e.g., staging.example.com) that resolves publicly.

Avoiding double‑counting when using both snippets

Loading the script twice causes each agent to initialize twice, which skews conversion attribution and may exceed plan limits. Choose one placement method only. If you must move from page‑level to site‑level, delete the T123 blocks before publishing the HEAD code.

Key facts

Frequently asked questions

• Why does the widget disappear after I publish? The new publish may have overwritten the HEAD code. Re‑insert the snippet and republish.
• How can I tell if an ad blocker is the culprit? Open the page in incognito mode with extensions disabled; the widget should appear if the blocker was the issue.
• When should I check the SeaText dashboard? After the first page load, wait five minutes, then look for your site name next to the SeaText logo.
• What if the console shows a CSP error? Adjust your server’s Content‑Security‑Policy to allow scripts from seatext.com.
• Does SeaText work on Tilda subpages? Yes, as long as the HEAD snippet is added at the site level or each subpage includes a T123 block with the code.
• Can I use the same SeaText account for multiple Tilda sites? No. Each account is linked to a single primary URL. Create a separate account for each site.
• What happens if I paste the snippet in both HEAD and a T123 block? The script loads twice, agents double‑initialize, and reporting becomes inaccurate.