The short answer is zero. On Tilda's free plan, you cannot run any SeaText variants because the SeaText script cannot execute there. Variant limits only matter once the script is installed on a compatible Tilda plan, so the first question is not “how many” but “whether.”

SeaText is not a Tilda feature. It is a JavaScript snippet that must be saved into a code area on your site. If your Tilda plan does not give you that code area in a usable way, the script never runs. No script means no variants, no tests, and no results.

Why Tilda free blocks SeaText variants

SeaText's integration instructions tell you exactly where the script belongs. For all pages, you paste it into the field labeled “Edit code inside HEAD tag.” For one page, you paste it into a T123 HTML block. Those are code contexts. Tilda's free plan is not built to run third-party scripts in the way SeaText requires, so the snippet cannot execute.

A workaround like pasting the code into a visible text block will not help. Browsers do not execute script tags shown as normal page text. The code has to live in an HTML or head-code context, not in a paragraph or heading block.

This matters because the failure is silent. You might install, publish, and wait for test results that never appear. Worse, you might pay for a SeaText plan before confirming your Tilda plan can run the script at all. Check compatibility before you buy.

How to check your Tilda plan's code access

Before you think about SeaText variants, confirm your Tilda plan allows custom code. Here is how to check.

Log in to your Tilda account. Go to Site Settings. Look for “More” → “HTML code for the head section.” If you see an “Edit code” button, your plan supports head code. If the button is missing or grayed out, your plan does not allow it.

For single-page code, add a new block and search for “T123.” If T123 is available in the block library, you can paste code there. If T123 is not listed, your plan restricts that block type.

Check the Tilda pricing page for the specific plan you are on. The free plan and some lower-tier paid plans may restrict custom code. Only when you have head code access or T123 access can SeaText run.

Do not skip this step. Many users install SeaText on a free plan, see no errors, and later discover the script never activated. The script does not warn you. It simply stays inert.

What happens after you upgrade Tilda

If you upgrade Tilda to a plan that supports custom code, the SeaText script can finally execute. But upgrading Tilda does not change SeaText variant limits. Those limits come from your SeaText plan, not your Tilda plan.

After upgrading Tilda, you still need a SeaText account. You still need to paste the script into the head code field or T123 block. You still need to activate the script by visiting your site for 40 seconds.

Upgrading Tilda only removes the Tilda-level blocker. It does not unlock any SeaText features automatically. Think of it as opening the door. You still have to walk through.

Also note that upgrading Tilda may change your site's performance or other settings. But for SeaText, the only benefit is that the script can now run. The number of variants you can run still depends on your SeaText plan.

Comparing SeaText variant limits across plans

Once you have a compatible Tilda plan, the next question is: how many SeaText variants do you need? The answer depends on your SeaText plan tier.

SeaText pricing is listed on the SeaText website. The source pack does not include exact numbers, so you must check the current pricing page. However, we can explain the logic.

SeaText offers different plans, often with increasing variant limits. A lower-tier plan may allow only one or two variants at a time. A higher-tier plan may allow dozens or more. The AI A/B Testing Agent generates variants and scales the winners. The variant limit applies to the number of active variants you can run simultaneously.

If you plan to test many headlines, offers, or CTAs at once, choose a plan with enough variant slots. If you only need to test one change at a time, a basic plan may suffice.

Do not guess. Visit the SeaText pricing page and compare the variant limits for each plan. That will tell you exactly what you can run.

Common mistakes when installing SeaText on Tilda

Many users make the same mistakes. Here are the most common ones and how to avoid them.

Mistake 1: Pasting the script into a visible text block. This does not work. The script must be in the head code field or a T123 block. Visible text blocks display the code as text, not as JavaScript.

Mistake 2: Not activating the script. After pasting the code, you must visit or refresh your site several times and stay on the page for at least 40 seconds. Then wait five minutes for your site name to appear in the SeaText dashboard. If you skip this, the script stays inactive.

Mistake 3: Using the wrong account. Each SeaText account is linked to a single primary URL. If you use a development domain or localhost, it will not work. Use a real production domain.

Mistake 4: Installing on a free plan and expecting it to work. As we explained, the free plan blocks code execution. Always check your Tilda plan first.

Mistake 5: Not checking the script after publishing. After publishing, refresh the page and open your browser's developer console. Look for any JavaScript errors. If you see errors, the script may not be loading correctly.

Avoiding these mistakes will save you time and frustration. The installation is simple, but the details matter.

What actually controls the variant count

Once Tilda can run the script, variant count becomes a SeaText pricing question. The source pack points to pricing but does not list tier numbers here. You need to check the current pricing page to compare how many variants each plan allows.

Also remember the account rules from the Tilda integration page:

• Each SEATEXT AI account is linked to a single primary URL.
• To use SeaText on multiple domains, create separate accounts.
• To use SeaText on multiple websites, create one account for each website.
• Development URLs such as localhost are restricted for security reasons.
• Dynamic development domains may not function properly.

These rules affect your real-world setup. You cannot use one account to run variants across a testing domain and a production domain.

Key facts at a glance

Check before you count variants

1. Can your Tilda plan save custom code in the head field or a T123 block? If not, stop there.
2. Do you have a SEATEXT AI account? You need one before installing the script.
3. Which URL is your primary URL? Make sure it matches the domain you will publish and promote.
4. Is that URL a real production domain? Localhost and dynamic development domains are not reliable.
5. After installing, did you activate the script by staying on the page for at least 40 seconds?
6. Which SeaText plan includes the number of variants you need? Check the pricing page before activating agents.

This checklist prevents the most common mistake: choosing a SeaText plan before confirming your Tilda plan can load the script.

Limitations and edge cases

This answer assumes you mean Tilda's free plan. If you are on a paid Tilda plan, the code access issue may not apply. Then the main limit is your SeaText plan, not Tilda.

If your website is hosted outside Tilda, this answer does not apply directly. The same script rules still matter, but the installation path will be different.

One more limitation: no script, no activation. Even on a compatible plan, SeaText's AI remains inert until it is activated. You cannot shortcut the activation step and expect variants to appear immediately.

Troubleshooting when SeaText does not activate

Sometimes you install the script correctly, but SeaText still does not activate. Here are common causes and fixes.

Check your Tilda plan again. Even if you think you have code access, double-check. Some paid Tilda plans restrict code in certain ways. Go to Site Settings and confirm the head code field is editable.

Verify the script is in the right place. Open the head code field or T123 block and ensure the full SeaText script is there. Do not add extra spaces or line breaks that break the code.

Clear your cache. Tilda caches pages. After publishing, clear your browser cache or use an incognito window to test. Wait a few minutes for the cache to refresh.

Check your SeaText account. Make sure you are logged in to the correct account. The account must be linked to the exact domain you are testing. If you have multiple accounts, use the one for that domain.

Wait longer. Activation can take up to five minutes. Sometimes it takes a bit longer. Refresh the SeaText dashboard after five minutes. If your site name still does not appear, contact SeaText support.

Test with a simple page. If the script does not activate on a complex page, try a simple test page with minimal content. This can rule out conflicts with other scripts.

If none of these work, the issue may be with your Tilda plan or a server setting. In that case, consider switching to a different hosting platform that supports custom code one hundred percent.

Alternatives if you cannot run SeaText on Tilda free

If your Tilda plan does not support custom code, you have a few options.

Upgrade Tilda. The simplest solution is to upgrade to a Tilda plan that allows custom code. Check the Tilda pricing page for plans that include custom code in the head section or T123 blocks. This is the easiest path if you want to stay on Tilda.

Move your website to another host. If you cannot or do not want to upgrade Tilda, consider moving your site to a platform that supports custom code without restrictions. Many hosting providers allow full access to head code. SeaText works on any website where you can paste JavaScript into the head section.

Use a different tool. If SeaText is not an option on your current plan, you may consider other A/B testing tools that work differently. However, most testing tools also require JavaScript injection. So the same code access issue applies.

Test manually. Without a script, you cannot run automated variants. But you can still do manual A/B testing by creating separate pages and comparing results. This is slower but requires no code access.

In short, the only way to run SeaText variants on Tilda is to have a Tilda plan that supports custom code. If you cannot get that, you cannot run SeaText variants at all.

FAQ

Can I run SeaText on Tilda free by using a T123 block?

No. Tilda free does not provide the supported code context SeaText needs to execute. If the code is pasted into a block that displays it as text, it will not run as JavaScript.

Are SeaText variants unlimited?

The source pack does not say that. Variant limits are listed on SeaText's pricing page, so compare current plan limits before you commit.

If I upgrade Tilda, do I still need a SeaText plan?

Upgrading Tilda only removes a potential Tilda-level blocker. Variant limits come from SeaText, so you still need a SeaText account and a plan that includes the variants you want.

Can I use one SeaText account for a Tilda test domain and a live domain?

No. Each SeaText account is linked to a single primary URL. Separate domains need separate accounts.

Can I test SeaText on localhost before publishing?

No. Development URLs such as localhost are restricted for security reasons, and dynamic development domains may not work properly.

How do I know the SeaText script is active?

After publishing, visit or refresh the site several times and stay for at least 40 seconds. Then wait about five minutes. When your website name appears next to the SeaText logo in your account, the connection is ready.

What if I see no errors but the script still does not work?

Check your Tilda plan's custom code access. Also ensure you have activated the script by visiting the site. If all else fails, contact SeaText support.

SeaText provides a 14‑day free trial for any platform that lets you add custom code to the <head> section^[S8]. The trial gives you full access to all AI agents for two weeks, allowing you to see real‑world impact before paying.

Recommendation: If you already have a paid Tilda plan, proceed with the trial on Tilda. If you are on the free plan, either upgrade or test the trial on another site that supports custom code.

Why a free trial matters

A free trial removes financial risk. You can measure conversion lift, ad‑spend recovery, and multilingual traffic without committing to a subscription. The 14‑day window is long enough to run at least one paid‑traffic campaign, see AI‑driven copy changes, and collect performance data. It also lets you verify that the integration works on your specific CMS, which can differ in how it injects scripts.

How SeaText AI agents work

SeaText installs a lightweight JavaScript snippet in the page head. When a visitor lands, the script sends the URL, referrer, and any query parameters to SeaText’s cloud. The cloud selects the appropriate AI agent—Conversion, Google Ads, Translation, Bot Refund, etc.—and returns a personalized HTML fragment. The fragment replaces the original copy in real time, so the visitor sees a version that matches their intent.

Each agent runs on a separate model optimized for its task. For example, the Google Ads Agent matches the exact keyword a user typed, while the Translation Agent selects the visitor’s language and serves a localized version. All agents respect the original design and only modify text, not layout.

Trade‑offs of using the trial on Tilda versus other platforms

• Code injection method: Tilda requires you to paste the snippet in the global <head> field (or use a T123 block for a single page). WordPress plugins can add the script automatically, and custom HTML sites let you edit the source directly.
• Plan restrictions: Tilda’s free tier blocks custom head code, so you must upgrade. Other platforms often allow script tags on any plan.
• Performance impact: The snippet is under 5 KB and loads asynchronously, so page speed impact is negligible on all platforms. However, Tilda’s built‑in CDN may cache the page before the script runs, so you may need to purge cache after installation.
• Domain handling: SeaText links one domain per account. If you test on a staging sub‑domain, you’ll need a separate account. This rule is the same across all platforms.

Practical usage tips

1. Upgrade Tilda first. The upgrade is instant; you can verify the More → HTML code for the head section → Edit code option appears.
2. Create your SeaText account. No credit card is required for the trial.
3. Copy the JavaScript snippet from the SeaText dashboard.
4. Paste the snippet into Tilda’s global head field. Save and publish.
5. Visit your live site at least three times, staying on the page for 40 seconds each visit. This activates the AI and registers the domain.
6. Wait five minutes, then check the SeaText dashboard. Your domain name should appear next to the SeaText logo.
7. Activate the agents you need (Conversion, Google Ads, Translation, etc.). Each activation is a single click.
8. Monitor the built‑in analytics. Look for metrics such as conversion rate lift, bot‑click refund amount, and language‑specific traffic.

Limitations and when this advice doesn’t apply

The free trial is limited to one primary domain per SeaText account. Development URLs like localhost or temporary staging domains are blocked for security reasons. If you need to test on multiple domains, create separate SeaText accounts for each.

SeaText agents only rewrite text content; they do not modify images, videos, or custom JavaScript you have added yourself. Complex single‑page applications may need additional configuration to ensure the snippet runs after the app’s own rendering.

If you exceed the 14‑day period without upgrading, the agents become inactive and the snippet stops rewriting content. Your site will revert to the original copy.

Trial Readiness Checklist

Complete these steps before starting the trial:

• ☐ Upgrade your Tilda account to a paid plan that supports custom <head> code.
• ☐ Sign up for a SeaText account (free, no credit card required).
• ☐ Copy the JavaScript snippet from the SeaText dashboard.
• ☐ In Tilda, go to Site Settings → More → HTML code for the head section → Edit code and paste the snippet.
• ☐ Save, publish, and clear any Tilda cache.
• ☐ Visit your live site three times, staying at least 40 seconds per visit.
• ☐ Wait five minutes, then verify the domain appears in the SeaText dashboard.
• ☐ Activate the AI agents you want to test.

Frequently asked questions

Can I use the SeaText free trial on Tilda Free?

No. Tilda Free blocks custom <head> code, which SeaText requires. Upgrade to a paid plan or test on another site.

How long does the SeaText free trial last?

14 days from the moment the domain is linked in the dashboard^[S8].

Do I need a credit card to start the trial?

No. You can create a SeaText account and start the trial without providing payment details.

What happens after the trial ends?

You can choose a paid SeaText plan to keep the agents active. Pricing details are on the SeaText pricing page.

Can I install SeaText on multiple Tilda sites?

Yes, but each site needs its own SeaText account because an account links to a single primary URL.

How do I know if SeaText is working after installation?

After visiting your site for 40 seconds, check the dashboard. Your domain name should appear next to the SeaText logo, and the agents list will show as “Active”.

What if I don’t see my website in the dashboard?

Ensure the snippet is correctly placed, clear Tilda’s cache, and revisit the site. If the problem persists, contact SeaText support.

Are there any hidden fees during the trial?

No. The trial is completely free. Only after the 14‑day period will you be prompted to select a paid plan.

Can I test the Translation Agent during the trial?

Yes. The Translation Agent supports up to 125 languages and works on any domain that the trial covers.

Is the trial limited to a single AI agent?

No. All SeaText agents are unlocked for the full 14‑day period.

Why the Free Plan Blocks SeaText

No Tilda blocks are compatible with SeaText on the free plan because the free plan blocks the code injection SeaText requires; on any paid Tilda plan, every standard Tilda block and Zero Block element can be optimized.^[S1] Tilda's free plan does not allow you to paste JavaScript into the site‑wide HEAD tag or into a per‑page HTML block (block T123). SeaText works by injecting a small script into the HEAD of every page you want optimized. Without that script, the AI never initializes, so no block — whether a simple headline or a complex Zero Block composition — can be rewritten, translated, or tested.

What Changes on a Paid Tilda Plan

When you upgrade, the "Edit code inside HEAD tag" field in Site Settings unlocks, and the T123 HTML block becomes available on individual pages. After you paste the SeaText snippet and publish, the script loads on every visit. From that point on, SeaText can read and rewrite every standard Tilda block type: text blocks (TX12, TX16, etc.), headline blocks (HD12, HD16), button blocks (BT12), form blocks (FM12), and the full Zero Block editor canvas. The compatibility matrix is effectively "all standard blocks" because SeaText operates on the rendered DOM, not on Tilda's internal block structure.^[S1]

Step‑by‑Step Paid‑Plan Activation Walkthrough

1. Log into your Tilda dashboard and choose the project you want to optimize.
2. Navigate to Site Settings → More → HTML code for the head section → Edit code.
3. Copy the JavaScript snippet from your SeaText account (found under Integration → Code).
4. Paste the snippet into the HEAD field and click Save.
5. Publish the site. The script is now live on every page.
6. Open the live site in a browser, stay on the page for at least 40 seconds, then wait about five minutes.
7. Return to the SeaText dashboard; you should see your domain name displayed next to the SeaText logo, confirming activation.^[S1]

If you prefer per‑page activation, add a T123 block to the desired page, open its Content editor, paste the same snippet, save, and publish that page. The script will load only on that page, but the T123 block itself is only available on paid plans.

What SeaText Changes in Each Block Type

SeaText reads the final HTML after Tilda renders the page. It then targets text nodes, attribute values, and alt text. The following changes are possible:

• Text blocks (TX12, TX16, etc.): rewrite copy, adjust tone, add calls‑to‑action.
• Headline blocks (HD12, HD16): generate alternative headlines, insert keyword‑rich variants.
• Button blocks (BT12): change button labels, add tracking parameters.
• Form blocks (FM12): modify placeholder text, adjust field order for better conversion.
• Zero Block elements: any HTML element inside Zero Block (images, custom HTML widgets, text) is treated like a regular DOM node and can be rewritten or translated.

SeaText never alters structural markup (e.g., container divs) or third‑party iframes, because those are outside its DOM‑text scope.

Verifying Whether Your Tilda Plan Allows Code Injection

Before spending time on integration, confirm that the HEAD field is editable:

1. Open any Tilda project.
2. Go to Site Settings → More. If you see an "Edit code inside HEAD tag" textbox, you are on a paid tier.
3. If the option is missing, the plan is free. Upgrade to any paid tier to unlock it.

Some users try to bypass the restriction with Google Tag Manager (GTM). GTM containers also require the HEAD field to fire on Tilda pages, which the free plan blocks. Therefore GTM does not work on free sites either.^{External Tilda FAQ}

Practical Scenarios and Decision Criteria

Below are common buyer situations and which Tilda plan fits best.

Limitations and When This Advice Does Not Apply

• If you use Tilda's free plan only for prototyping and never publish to a custom domain, SeaText will never activate — the script won't load.
• If you embed SeaText via a tag manager (GTM) instead of Tilda's native HEAD field, the same free‑plan restriction applies: GTM containers don't fire on Tilda free sites.
• Zero Block custom code widgets that load external scripts are not rewritten; SeaText only touches text nodes in the main document.
• This analysis assumes standard Tilda plans. Enterprise or legacy Tilda plans may have different code‑injection rules — check your specific plan details.

FAQ

Can I test SeaText on a Tilda free site using a subdomain?

No. The free plan blocks HEAD tag edits on all subdomains. You need a paid Tilda plan on the exact domain you intend to optimize.

Does SeaText work on Tilda's trial period?

Yes. A Tilda trial functions like a paid plan for code injection. You can install and activate SeaText during the trial. If you downgrade to free after the trial, the script stops loading.

What if I only want to optimize one landing page?

Use the per‑page method: add a T123 block to that page, paste the SeaText snippet, publish. You still need a paid Tilda plan for the T123 block to be available.

Are there any Tilda blocks SeaText cannot optimize even on a paid plan?

Only content inside cross‑origin iframes (third‑party widgets, payment forms, embedded maps). Everything else — native Tilda blocks and Zero Block elements — is fair game.

Do I need a separate SeaText account for a staging domain?

Yes. Each primary URL (including staging.yoursite.com) requires its own SeaText account. Development domains like localhost are not supported.

How long before I see SeaText changes on my Tilda site?

After the initial 40‑second visit and 5‑minute dashboard confirmation, SeaText starts generating variants immediately. Visible changes depend on which agents you activate (translation, CRO, Google Ads matching, etc.) and traffic volume.

Can I use SeaText on a Tilda site that already has custom JavaScript?

Yes. SeaText's snippet is designed to coexist with other scripts. Place it before the closing </head> tag for best results.

The SeaText logo is a connection indicator in your SeaText dashboard, not a widget that your Tilda visitors see. It appears after the SeaText JavaScript is installed in Tilda, published, and activated by real page visits. If it is not showing, confirm that the code is in the "Edit code inside HEAD tag" field, save and publish, visit your site for at least 40 seconds, then wait five minutes before you check the top of the SeaText page for your domain next to the logo.

Work through the steps in order. Most missing-logo cases are caused by a skipped publish, the wrong field, an ad blocker, or checking too early.

1. Put the SeaText code in the correct Tilda field

SeaText gives you a JavaScript snippet that you paste into Tilda. The supported site-wide method uses the head section.

1. Log in to your Tilda dashboard.
2. Open Site Settings.
3. Go to More → HTML code for the head section → Edit code.
4. Paste the full JavaScript snippet from SEATEXT AI into the field labeled "Edit code inside HEAD tag".
5. Save, then publish the site.

If you only want SeaText on one page, use a T123 block instead:

1. Open the page in the Tilda dashboard.
2. Click the + icon to add a block.
3. Choose Other, then select the T123 block.
4. In the block, click Content to open the HTML editor.
5. Paste the snippet, click Save and Close, then Publish.

Why does the code placement matter? The head tag ensures the script loads before the page content. This allows SeaText to activate quickly when a visitor arrives. The T123 block works for single pages but delays the script load slightly. Use one method per page. If you paste the code in both the site head and a T123 block, you may create duplicate scripts. Duplicates cause conflicts and make troubleshooting harder.

Practical scenario: You have a multi-page Tilda site. Use the site-wide head method. This activates SeaText on all pages. If you only need it on a landing page, use the T123 block. Mixing both on the same page leads to errors.

2. Visit your published site to activate the script

The SeaText script is designed to stay inert until it detects visits. It links to your account when someone loads the page and stays there long enough.

1. Open your published Tilda site in a normal browser tab.
2. Refresh the page several times.
3. Stay on the page for at least 40 seconds.
4. Use the published URL, not just the Tilda editor preview.

Why 40 seconds? SeaText waits to confirm a real human is browsing. Bots quickly leave, so the script needs a sustained visit. This prevents false activations. If you leave the page too early, the activation does not trigger. Refresh a few times to simulate multiple visits, which also helps.

Common mistake: Checking the editor preview. The preview does not load the published version. Always use the live URL. Also, if you have a cache, the old page may load. Use a hard refresh or incognito window.

3. Wait five minutes and look in the right place

Activation does not happen instantly. After visiting the page, wait at least five minutes.

Then go to your SeaText account page and look at the top. You should see your website name next to the SEATEXT logo. That is the indicator that the connection is live.

This also means you should not expect a SeaText logo to appear on your Tilda website. The JavaScript runs in the background. If you expected a visible badge, your installation may be fine; the logo simply is not a public widget.

Why five minutes? SeaText's server processes the visit data and links it to your account. This delay is normal. If you check too early, the logo will not appear. Wait the full five minutes. If it still does not show, repeat the 40-second visit and wait again.

4. Clear caches and disable script blockers

Your browser can keep serving the old Tilda page after you publish. That makes it look like the code is missing even when it is installed.

• Refresh with a hard reload (usually Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac).
• Try a private or incognito window.
• Use a different browser.
• Disable ad blockers, privacy extensions, or script blockers for your Tilda domain and seatext.com.
• Check the browser console for a blocked request to seatext.com.

If any extension blocks the SeaText script, the connection indicator cannot appear. Allow the domain, then repeat the 40-second visit and wait time.

Limitations: Content security policies (CSP) on your Tilda site may also block the script. Check your Tilda settings for any custom CSP headers. If you have a firewall or security plugin, whitelist seatext.com. Some corporate networks block external scripts; test from a personal device.

5. Check domain and account rules

SeaText links each account to a single primary URL. If your Tilda site uses a preview, temporary, or development domain, the account may not match.

• Use one SeaText account per website.
• Create a separate account for each real domain.
• Use valid, real domains; localhost is restricted for security reasons.
• Avoid dynamic development domains that change often, because SeaText may not associate traffic with your account.

Why does this matter? SeaText needs a stable domain to link the activation. If you test on a temporary domain (like tilda.site or a preview URL), the logo will not show because the account expects the final domain. Only after you use the real domain will the connection work.

Practical scenario: You have a staging site and a live site. Create two SeaText accounts: one for each. This prevents confusion. If you change your domain later, you need a new account. Also, do not use localhost for development; it is blocked.

6. Frequently asked questions

Should the SeaText logo appear on my Tilda website?

No. The SEATEXT logo appears on the SeaText account page next to your website name. It is a connection indicator for you, not a visitor-facing badge.

How long does it take for the logo to show?

After you visit or refresh the published site and stay for at least 40 seconds, wait at least five minutes before checking.

Can I use the same SeaText account on two Tilda sites?

No. Each SEATEXT AI account is linked to a single primary URL. Use separate accounts for separate websites or domains.

Why does my localhost Tilda preview not work?

Development URLs such as localhost are restricted for security reasons. Dynamic development domains may also fail to associate traffic with your account. Use a real, valid domain.

What should I check first if the logo does not appear?

Confirm the code is in the "Edit code inside HEAD tag" field, save and publish, clear browser cache, disable script blockers, visit the page for 40 seconds, and wait five minutes.

What if I did everything and the logo is still missing?

Copy the JavaScript code again from your SeaText dashboard. The code may have been truncated when you copied it. Remove any old snippet from Tilda, then paste the fresh code. Confirm that your Tilda page is published and that you are viewing the published URL. Keep the page open for a full 40 seconds, refresh a few times, and wait another five minutes. Check that you are logged into the SeaText account that owns the primary URL where you installed the code. If you still have issues, contact SeaText support.

What if I see the logo in the editor but not on the live site?

The editor preview does not load the SeaText script. Only the published URL activates the script. Always check the live site.

Can ad blockers prevent the logo from showing?

Yes. Ad blockers and privacy extensions can block the SeaText domain. Disable them for your Tilda site and seatext.com, or use an incognito window.

The SeaText logo is a visual confirmation that the SeaText JavaScript has executed on a Tilda page. According to the SeaText integration guide, the script must be pasted into the Edit code inside HEAD tag field in Site Settings, or added via a T123 block on a specific page, then saved and published. If any of these steps are skipped or done incorrectly, the script will not run and the logo will stay hidden.

How SeaText integrates with Tilda

SeaText provides a JavaScript snippet that must be present in the <head> of every page where the AI agents should work. The official guide lists two methods: a site‑wide insertion through Site Settings, or a page‑specific insertion using the T123 “Other” block. Both methods require a final publish action before the code becomes live.

Where to place the SeaText code

• Site‑wide: Open Site Settings → find the field labeled “Edit code inside HEAD tag” → paste the snippet → save → publish the whole site.
• Page‑specific: Edit the target page → add a new block → choose T123 → select “Other” → click “Content” → paste the snippet into the HTML editor → save and close → publish the page.

Both approaches are documented in the SeaText integration page (source S1). No other Tilda configuration options are mentioned in the provided sources.

Common reasons the logo does not appear

• The script was pasted into the wrong field (for example, into a body‑code field instead of the HEAD field).
• The site or page was not published after the code was saved.
• The page was not visited long enough; SeaText requires at least 40 seconds of active viewing before the AI activates and the logo shows.
• The script tag is malformed or contains extra characters that break execution.

Step‑by‑step verification checklist

Decision framework for troubleshooting

Use the following criteria to decide the next action when the logo is missing:

• Code placement – If the script is not in the HEAD, move it to the correct field and republish.
• Publish status – If the site shows an older version, publish again.
• Activation time – If the script is present but the logo is absent, wait the required 40 seconds and refresh.
• Script errors – If the console shows a syntax error, copy the snippet again from the SeaText dashboard and replace the existing code.

Limitations and next steps

The provided source pack does not document Tilda settings such as Content Security Policy, “Remove unused CSS/JS”, or “Lazy load scripts”. Therefore this article cannot confirm whether those settings affect the SeaText logo. If you have applied custom security or performance settings in Tilda, consult Tilda’s own documentation or support to see if they block external scripts. For issues beyond code placement and activation time, contact SeaText support with a link to the live page.

FAQ

• What if the logo still doesn’t appear after fixing the code placement? Verify the script tag is present in the <head> as described in the SeaText integration guide (source S1). Check the browser console for errors.
• Do I need to republish after each change? Yes. Tilda only serves the updated code after a publish action.
• Is there a cost to adjusting these settings? No. The integration steps use built‑in Tilda features.
• Can I use the page‑specific method for all pages? You can, but you must add the T123 block to every page that needs SeaText.
• How long does activation take? Stay on the page for at least 40 seconds; the logo should appear after that period.

Why Script Conflicts Matter

SeaText adds a small badge that signals AI assistance on your site. If the badge disappears, visitors may think the feature is broken. A missing badge also means the AI cannot activate, so you lose conversion benefits.

How the SeaText Badge Renders

The badge appears when a JavaScript snippet runs in the <head> of every page. The script creates a DOM element and injects an image from https://seatext.com. After the code runs, you must stay on the page for at least five minutes before the dashboard shows your site name. This activation step is required by SeaText.

Common Third‑Party Scripts and Compatibility

Who fits each option?

• GTM – best for marketers who need a single container for many tags.
• Facebook Pixel – fits advertisers who already use the pixel and have a permissive CSP.
• Custom JavaScript – suitable for developers who can isolate the badge with selective script testing.
• jQuery plugins – works for legacy sites that do not rewrite the whole page.
• CSP – essential for security teams that control allowed sources.

Diagnosing a Conflict

1. Open the browser console (F12). Look for errors that mention seatext or CSP violations.
2. Check the Network tab. Verify a request to seatext.com returns status 200.
3. Use selective isolation: open DevTools, locate the <script> tags, and comment out one third‑party script at a time. Refresh after each change.
4. If the badge appears after disabling a script, that script is the culprit.
5. Note the script’s load attributes (defer, async). Record the order in which scripts execute.

Resolving Load‑Order and CSP Issues

Follow these steps exactly as written. Test one change at a time.

• Place the SeaText snippet in the <head> without defer or async. This ensures the script runs as soon as the DOM is parsed.
• If other scripts need to load later, move them below the SeaText tag or add defer to them.
• When using async, execution order is unpredictable. Prefer defer for scripts that must run after the document is parsed.
• Update CSP headers to include:

  script-src 'self' https://seatext.com;

  img-src 'self' https://seatext.com;

  Add a nonce if your policy blocks inline scripts.
• After each edit, reload the page and wait at least five minutes. The dashboard will then show your site name next to the SeaText logo.

Frequently Asked Questions

How do I know if the SeaText script is loading?

Open the Network tab and look for a request to seatext.com or a file named seatext.js. A 200 status means it loaded.

Can a firewall or ad blocker hide the badge?

Yes. Some blockers stop external scripts. Test on a network without the blocker.

What if the badge appears only on some pages?

Check whether the conflicting script is included only on those pages. Ensure the SeaText snippet is in the global template.

Does the load order matter if both scripts are async?

Yes. Async scripts run when downloaded, not in document order. Use defer for predictable sequencing, and keep SeaText first.

How long does it take for the badge to appear after installation?

After placing the code, stay on the page for at least five minutes. Then check the SeaText dashboard for your site name. The badge may appear earlier on the live site.

Can I move the badge to a different position?

SeaText controls placement. Moving it with custom JavaScript can re‑introduce conflicts. Use the provided configuration options instead.

Testing SeaText in a safe environment prevents surprises after launch. The integration works the same on a preview or staging site as on the production domain. Below is a step‑by‑step guide that follows the official Tilda instructions and SeaText account rules.

Why Test Before Going Live?

Running AI agents on a live site can change copy, offers, or translations instantly. If the script is mis‑configured, visitors may see broken text or wrong offers. Testing lets you catch these issues early, protect conversion data, and avoid revenue loss.

Testing on Tilda Using the Preview Feature

SeaText provides a JavaScript snippet that you paste into the Edit code inside HEAD tag field in Tilda’s Site Settings, or into a T123 block on a single page. After saving, do not publish yet. Click the Preview button. The preview environment loads the same script that the live site would use.

According to SeaText’s documentation, the AI remains inert until you activate it. Activation requires visiting or refreshing the page several times and staying on it for at least 40 seconds. After this, wait about five minutes for the domain name to appear next to the SeaText logo in your dashboard. This confirms the script is recognized and ready.

Because the preview URL is public, the script can load and the activation steps work exactly as on a production domain.

Using a Public Staging Subdomain for Non‑Tilda Sites

If you are on WordPress, Shopify, or a custom CMS, create a subdomain such as staging.yourdomain.com or test.yourdomain.com. The subdomain must be publicly reachable; password‑protected sites will block the script.

SeaText requires a separate account for each primary URL. Sign up for a new SeaText account, copy the JavaScript snippet, and paste it into the HEAD section of the staging site. The same activation rule applies: visit the page, refresh a few times, and stay for at least 40 seconds. After five minutes, the staging domain appears in the dashboard, confirming a successful connection.

This approach mirrors the Tilda workflow but works on any platform that lets you edit the HEAD tag.

Detailed Activation Mechanics

SeaText’s activation logic is simple but essential. The script monitors page loads and total time spent on the page. When it records at least three visits and a cumulative dwell time of 40 seconds, it flags the domain as active. The dashboard then updates within five minutes.

During activation, no visible changes occur on the page. The AI agents stay dormant until you enable them in the SeaText console. This safety net ensures that testing does not unintentionally alter content.

Common Mistakes and How to Avoid Them

• Testing on localhost. Development URLs like localhost or private IPs are blocked for security reasons. Use a real public subdomain instead.
• Reusing the production script on staging. Each SeaText account links to a single primary URL. If you paste the live script on staging, activation will fail because the domain does not match the account.
• Skipping the 40‑second dwell time. The script only activates after you stay on the page long enough. Refresh quickly and leave; the activation will not trigger.
• Password‑protecting the staging site. The script cannot load behind a login wall. Ensure the staging URL is accessible without authentication.

Limitations of the Testing Process

SeaText does not support dynamic development domains that change frequently. Temporary hosting URLs may not reliably associate traffic with your account. Also, the script will not run on pages that block third‑party JavaScript or use strict Content‑Security‑Policy headers that exclude external scripts.

Finally, the activation process only works on publicly reachable URLs. If your staging site is blocked by robots.txt or firewall rules, the script cannot load, and activation will not occur.

Expert Perspective: The Business Value of Pre‑Launch Testing

Testing saves time and money. For the Google Ads Agent, a mis‑matched headline can lower Quality Score and increase cost‑per‑click. By confirming the rewrite works on staging, you avoid wasted ad spend.

The Bot Refund Agent needs accurate detection of invalid clicks. If the detection logic is off, you may miss refund opportunities or generate false claims. A controlled test lets you verify the detection thresholds before exposing real traffic.

Translation agents affect international SEO. Incorrect language tags can hurt rankings. Staging lets you review the translated markup and ensure hreflang attributes are correct.

Overall, a short preview or staging test reduces risk, improves data quality, and builds confidence that the AI agents will deliver the promised lift.

Frequently Asked Questions

Can I test SeaText on a local development server?

No. Localhost and other private URLs are restricted for security reasons. Use a public staging subdomain instead.

Do I need a separate SeaText account for my staging site?

Yes. Each domain, including staging, requires its own account because the script is tied to a single primary URL.

How long does activation take?

After staying on the page for at least 40 seconds, wait about five minutes for the domain to appear in the dashboard. If it does not, refresh again and ensure the dwell time requirement is met.

Will testing affect my live site data?

No. The staging site uses a separate account, so data does not mix with the production site.

What if my staging site is behind a login wall?

The script needs to load without authentication. If the site is password‑protected, the activation will fail. Use a publicly accessible subdomain.

Is there a way to see a video demo of the preview testing?

Yes. SeaText’s help center includes a short video that walks through Tilda’s Preview mode and staging setup. Check the “Learn more” link in the CTA below.

Direct Answer: What Does It Cost to Troubleshoot a Missing SeaText Logo?

If you have a paid SeaText plan, standard support is included at no extra cost. For the majority of cases, the fix is a simple page refresh and a short wait—no charge. Only when the issue requires custom debugging or deeper investigation might you face a one‑time fee of $150–$300, depending on complexity.

Why the SeaText Logo Might Be Missing

The most common reason is that the integration has not been fully activated. SeaText’s own guide states: “Visit or refresh your website several times and stay on your page for at least 40 seconds—this will activate the AI and link it to your account.” It also adds: “Wait at least five minutes until you see your website name displayed next to the SEATEXT logo at the top of this page.” If you skip these steps, the logo will not appear.

Other frequent causes include:

• Using a development URL such as localhost or a dynamic sub‑domain.
• Missing or malformed JavaScript snippet.
• Conflicts with other scripts or a heavily customized theme.

Before contacting support, verify each of these points.

Why the Logo Matters

The SeaText logo is more than a visual badge. It signals that the AI agents are active and linked to your account. When the logo appears, the backend knows that traffic can be processed by the autonomous agents (conversion, translation, bot‑refund, etc.). If the logo is absent, the AI remains inert, and none of the promised performance gains will materialize.

Missing the logo can also affect reporting. The dashboard shows your website name next to the logo only after activation. Without that connection, you cannot see conversion lift, bot‑refund evidence, or multilingual performance metrics.

In short, the logo is the activation checkpoint that unlocks the full SeaText ecosystem.

How It Works: Activation Process

SeaText’s activation is deliberately simple but time‑sensitive. Follow these steps exactly:

1. Open a browser on the live site (not a staging or localhost URL).
2. Refresh the page or navigate to it for the first time after installing the script.
3. Stay on the page for at least 40 seconds. Do not switch tabs or close the window.
4. After the 40‑second stay, continue browsing or stay idle for an additional five minutes.
5. Return to the SeaText dashboard. Your website name should now appear next to the SeaText logo at the top of the page.

If the name appears, activation succeeded and the logo will display on your site. If not, repeat the steps to rule out a temporary network glitch.

For Tilda users, the script can be added via the site‑wide HEAD field or by inserting a T123 block on a specific page. The same 40‑second stay and five‑minute wait apply after publishing the changes (source S1).

Support Tiers: Free vs. Paid

SeaText offers free standard support for all paid plans. This includes:

• Guidance on installing the JavaScript snippet.
• Help with the 40‑second activation steps.
• Assistance with common domain‑related issues.

If you are on a free trial or a non‑paid plan, support is limited. Upgrading to a paid plan unlocks the free tier.

When the logo still does not appear after the activation steps, SeaText may recommend a custom debugging service. This service is billed as a one‑time fee ranging from $150 to $300, based on the time required to diagnose script conflicts, multi‑domain setups, or deep theme customizations.

Cost Drivers: When Does It Become a Paid Engagement?

Custom debugging costs depend on several factors:

• Complex codebase: Heavily modified themes or custom JavaScript increase investigation time.
• Multiple domains: Each domain needs a separate SeaText account. Managing several accounts adds overhead.
• Third‑party script conflicts: Conflicts with analytics, ad‑tech, or other AI tools may require careful isolation.
• Platform variations: WordPress, Shopify, or Tilda each have unique integration quirks.

Most users never need to pay. The quick refresh‑and‑wait method resolves the issue for >90 % of cases.

How to Check If You Need Paid Help

Run through this checklist before requesting a paid session:

1. Confirm you are using a public, real domain (not localhost or a temporary dev URL).
2. Verify the JavaScript snippet copied from the SeaText dashboard matches exactly.
3. Ensure the script is placed in the HEAD of every page (or via a T123 block on Tilda).
4. Perform the 40‑second stay and five‑minute wait as described.
5. Refresh the dashboard and look for your site name next to the SeaText logo.

If all steps are correct and the logo still does not appear, note the symptoms (error console messages, missing network requests) and contact support. They will first attempt a free resolution; if it fails, they will propose a paid debugging quote.

Limitations and When the Advice Does Not Apply

The free support and quick‑fix method apply only under these conditions:

• You have an active paid SeaText subscription.
• Your site is reachable via a valid, public domain.
• You have inserted the exact script provided by SeaText.

Development URLs such as localhost are restricted for security reasons (source S1). Dynamic development domains may also fail because SeaText cannot reliably associate traffic with your account.

If you run multiple websites, you must create a separate SeaText account for each primary URL. Using one account across several domains will cause activation failures and missing logos.

Trade‑offs and Considerations

Choosing the free quick‑fix versus paying for custom debugging involves trade‑offs:

• Time: The free method takes minutes. Custom debugging can take hours or days, depending on complexity.
• Technical skill: The quick fix requires only basic browser actions. Paid debugging may involve code changes, server‑side adjustments, or coordination with third‑party vendors.
• Downtime risk: Incorrect script edits can break page rendering. Paid engineers usually work in a staging environment to minimize live‑site impact.
• Cost certainty: Free support has no hidden fees. Paid debugging is billed upfront with a clear range ($150–$300).

If your site is mission‑critical and you cannot afford any downtime, consider scheduling a paid session after the free attempts fail. This ensures a professional will handle the changes with minimal risk.

Common Follow‑Up Questions

What if the logo appears intermittently?

Intermittent appearance often signals a caching issue or a race condition with other scripts. Clear browser cache, disable aggressive CDN caching, and verify the script loads on every page load.

Can I automate the activation steps?

Automation is possible with a headless browser that stays on the page for 40 seconds and then waits five minutes. However, SeaText does not officially support automated activation, and doing so may violate terms of service.

How does the logo behave on multi‑domain setups?

Each domain needs its own SeaText account. The logo will only appear on domains that have a matching account and have completed the activation steps. Using one account for several domains will result in missing logos on all but the primary domain.

What if I see the logo but the AI agents still seem inactive?

The logo indicates activation, but agents may be disabled in the dashboard. Log in to the SeaText portal and verify that the desired agents (Conversion, Translation, Bot‑Refund, etc.) are toggled on.

Is there a refund if custom debugging does not fix the issue?

SeaText’s policy requires agreement on the scope and fee before work begins. If the agreed‑upon work is delivered but the issue persists, you can discuss a partial refund, but it is not guaranteed.

Frequently Asked Questions

Is support for a missing logo free?

Yes, for paid plans. Standard support is included at no extra cost.

How long does it take for the logo to appear after installation?

After visiting or refreshing your site and staying for 40 seconds, wait at least five minutes. The logo should then appear next to your website name in the dashboard.

What if the logo never shows up after waiting?

Double‑check the integration steps, domain validity, and script placement. If the problem persists, contact SeaText support (free for paid plans) or consider a paid custom debugging session.

Can I get a refund if the logo issue is not resolved?

SeaText’s refund policy is not detailed in the available materials, but standard support should resolve most issues. For custom debugging, the fee is agreed upon in advance.

Does the missing logo affect my website’s functionality?

The logo itself does not affect page rendering, but its absence indicates that the AI agents are not active, so you miss out on conversion, translation, and bot‑refund benefits.

What if I’m using a CMS like Tilda or WordPress?

The integration steps are similar. For Tilda, paste the script into the HEAD field or use a T123 block, then follow the 40‑second/5‑minute activation steps. WordPress users can add the script via a header plugin or theme file.

How do I know if I need the paid custom debugging?

If you have followed all free‑tier steps, verified domain and script correctness, and still see no logo, SeaText support will suggest a paid engagement. You will be informed of the exact cost before any work begins.

If you need a printable guide, choose the PDF option. If you prefer instant online access, use the web checklist.

Where to find the official checklist

The checklist lives on the SeaText Tilda integration page: https://seatext.com/tilda-integration#installation-checklist. The same URL appears in your SeaText dashboard under the Integrations section.

Downloading the PDF version

On the checklist page you will see a “Download PDF” button. Clicking it saves a printable version of the step‑by‑step guide to your computer. The PDF contains the same instructions as the web page, plus a contact email for support.

Why the checklist is essential for a successful SeaText integration on Tilda

SeaText works by injecting a JavaScript snippet into the HEAD of your site. If the snippet is placed incorrectly, the AI stays inert and cannot read or rewrite your content. The checklist guarantees that the code is added in the right place, that activation steps are performed, and that the connection is verified.

Following the checklist also prevents security blocks. SeaText blocks localhost and temporary URLs. Using a real domain from the start avoids the “domain not allowed” error.

Finally, the checklist reduces time spent on trial‑and‑error. Most users spend hours debugging script placement. The checklist cuts that to minutes.

Step‑by‑step walkthrough of each checklist item

1. Copy the JavaScript code from the SeaText UI. The code appears in the “SEATEXTCODEINTEGRATION” section of your dashboard.
2. Insert the code in Tilda (global) – go to Site Settings → Edit code inside HEAD tag, paste the script, then save and publish. This adds the script to every page.
3. Insert the code on a single page (optional) – open the Tilda page you want to test, click the “+” icon, choose block T123, select “Other”, then open the HTML editor. Paste the same snippet, click “Save and Close”, and publish the page.
4. Activate the script – visit your site several times and stay on a page for at least 40 seconds. This activity signals SeaText to link the script to your account.
5. Verify connection – after five minutes the SeaText logo should appear at the top of the page with your site name. This confirms the integration is ready.

Practical tip: open the page in an incognito window for the first visit. This ensures no cached scripts interfere with activation.

Common pitfalls and how to avoid them

• Using a development or localhost URL – SeaText blocks these for security. Always test on a real, publicly reachable domain.
• Skipping the 40‑second visit – the AI remains inert until it records a sustained visit. Set a timer and stay on the page.
• Not waiting the full five minutes for the logo – the logo appears only after SeaText confirms the connection. Refresh after five minutes.
• Placing the script in the body instead of the HEAD – Tilda requires the script in the HEAD tag. Use the “Edit code inside HEAD tag” field.
• Publishing before saving the code – always click “Save” then “Publish”. Otherwise the script is not live.

Real‑world example: a user added the snippet to a T123 block but forgot to publish the page. The logo never appeared, leading to confusion. Re‑publishing solved the issue instantly.

Troubleshooting: SeaText logo does not appear after activation

1. Refresh the page after five minutes. The logo may load slowly.
2. Check that the script is exactly in the HEAD tag. Use the browser’s “View source” to confirm.
3. Verify you stayed on the page for at least 40 seconds. Short visits do not trigger activation.
4. Ensure the domain matches the one registered in your SeaText account. Different sub‑domains count as separate domains.
5. If the logo still does not show, open the SeaText dashboard, navigate to Integrations → Tilda, and click “Resend activation email”. This forces a re‑check.

Follow‑up questions and advanced scenarios

• Can I use the same SeaText account on multiple Tilda sites? No. Each account links to a single primary URL. Create separate accounts for each domain, as stated in the source.
• How do I test on a staging environment? Staging URLs are treated as development domains and are blocked. Use a temporary real domain (e.g., staging‑example.com) and create a separate SeaText account for it.
• What if Tilda updates its UI? The checklist is updated on the SeaText page whenever Tilda changes its interface. Check the URL regularly for the latest steps.
• Can I edit the checklist after I have published? Yes. Return to the “Edit code inside HEAD tag” field, make changes, save and republish.
• How do I handle multiple domains (production and development)? Create a separate SeaText account for each domain. The source notes that development URLs such as localhost are restricted.

Benefits of downloading the PDF version versus using the online checklist

The PDF version is printable, offline, and easy to share with team members who do not have dashboard access. It also includes a static list of support contacts.

The online checklist is always up‑to‑date. If Tilda changes a menu name, the web page reflects the new wording instantly, while the PDF may become outdated.

Choose the PDF when you need a hard copy for onboarding or compliance audits. Choose the online version for the most current instructions.

FAQ

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

Yes. Each account links to a single primary URL.

Can I install the script on a development sub‑domain?

Development URLs are restricted; use a real domain for testing.

What if the logo doesn’t appear after five minutes?

Refresh the page, ensure the script is in the HEAD tag, and verify you stayed on the page for at least 40 seconds.

Is the checklist updated for new Tilda versions?

SeaText updates the page whenever Tilda changes its interface.

How many domains can I connect to one SeaText account?

Only one primary domain per account. Create additional accounts for extra sites.

SeaText adds AI agents to a Tilda website through a small JavaScript snippet. You paste that snippet in one of two places: the site-wide HEAD field so it runs on every page, or a T123 block so it runs on one page only. This guide walks through both methods, explains how to choose, and shows you how to verify the connection.

Prerequisites before you start

Create a SeaText account first. Each SeaText account connects to a single primary URL. If you plan to use SeaText on more than one domain — like a staging domain and a production domain — you need a separate account for each domain.

Development URLs such as localhost are restricted for security reasons. SeaText may not associate traffic from dynamic development domains with your account. Use a real, publicly accessible domain for testing.

How to choose between global and single-page installation

The global method puts the script into the <head> of every page on your Tilda site. It is the best default for most sites. You add the code once, and every current and future page inherits the SeaText agents.

The single-page method uses a T123 HTML block. It runs only on that page. Choose it when you are testing SeaText on a landing page, when you only want to translate one page, or when you don't have access to Site Settings.

Use the global method unless you have a specific reason to limit the script. This avoids missing pages later.

Method 1: Site-wide installation via the HEAD tag

1. Log in to your Tilda dashboard and open the project you want to connect.
2. Go to Site Settings.
3. Find the field labeled "Edit code inside HEAD tag".
4. Paste the JavaScript snippet you copied from your SeaText dashboard into that field.
5. Click Save, then Publish the entire site.

This places the script in the <head> of every page. All current and future pages inherit the SeaText agents automatically.

Method 2: Single-page installation with a T123 block

1. Open the specific page you want to translate or optimize in the Tilda editor.
2. Click the + icon to add a new block.
3. Scroll down and choose Other from the block options.
4. Locate and select the T123 block, which enables embedded HTML code.
5. Once the block is added, click on Content to access the HTML editor.
6. Paste the SeaText JavaScript snippet into the editor.
7. Click Save and Close, then Publish the page.

The T123 block runs the script only on that page. Use this when you're testing SeaText on a single landing page or when you don't have access to Site Settings.

What happens inside the SeaText dashboard after the script loads

After the script loads on your published site, SeaText remains inert until you activate agents. This means the code won't change your content by itself.

During your first visit of 40 seconds or more, the script activates and links traffic to your account. Within five minutes, your website name should appear next to the SeaText logo at the top of the dashboard. That is the signal that the connection is live.

From there, you can activate individual agents: translation into 125 languages, Google Ads landing-page rewrites, bot-click detection and refund reports, CRO A/B testing, ChatGPT brand visibility, and more. Each agent is a one-click toggle. No further code changes are required.

Security and content safety

The installation process is secure. The AI remains inert until you activate it, so your website content is not changed by the mere presence of the script. This gives you control over which agents run and when.

Because each account is linked to one primary URL, one script cannot affect another site. If you run multiple domains, separate accounts keep traffic data isolated and prevent the wrong site from being modified.

Verify the installation works

1. Visit your published site (or the specific page) in a browser.
2. Stay on the page for at least 40 seconds. This starts the activation handshake.
3. Refresh the page a couple of times.
4. Wait five minutes, then open your SeaText dashboard. Your website name should appear next to the SeaText logo at the top.

If the name appears, the connection is confirmed and you can move on to agent activation.

Troubleshooting the 40-second and five-minute handshake

The 40-second visit is not random. It gives the script enough time to send an initial signal to SeaText servers. The five-minute window lets the dashboard process that signal and attach the site to your account.

If the site name does not appear after five minutes, check these in order:

• Published status: Tilda's Save is not enough. The script only loads on the live, published URL.
• Snippet accuracy: Paste the exact snippet without extra whitespace or line breaks.
• Domain match: The live domain must match the primary URL registered in that SeaText account.
• Visit length: Return to the page and stay for at least 40 seconds again, then wait another five minutes.

If you are testing on a preview URL that changes dynamically, SeaText may not reliably associate traffic with your account. Use a fixed, public domain instead.

Common mistakes and how to avoid them

• Pasting into the wrong field: The global code must go into "Edit code inside HEAD tag" in Site Settings, not into a page-level HTML block.
• Forgetting to publish: Saving in Tilda is not enough; the script only loads on the live, published URL.
• Using a staging subdomain that isn't registered: Each domain needs its own SeaText account. A staging domain like staging.example.com counts as a separate domain.
• Testing on localhost: SeaText blocks localhost and dynamic development URLs. Deploy to a real domain for testing.

A practical example: multi-domain Tilda setup

Suppose you run a main marketing site at example.com and a separate blog at blog.example.com. Both are Tilda projects. You want SeaText agents on both.

Create one SeaText account for example.com and another for blog.example.com. Log into the first account and copy its snippet. Paste that snippet into the global HEAD field of the main Tilda project. Publish.

Then switch to the second account and copy its snippet. Paste it into the global HEAD field of the blog project. Publish. Each account tracks its own traffic and shows its own website name.

Never reuse the same snippet across two domains. The domain tied to that account will not match the second site, and the handshake may fail.

Quick reference: where to paste the code

FAQ

Do I need coding skills to install SeaText on Tilda?

No. The steps use Tilda's visual interface: a settings field for global install, or a drag-and-drop T123 block for a single page. You only copy and paste the provided JavaScript snippet.

Can I use the same SeaText account for my main domain and a staging subdomain?

No. Each domain or subdomain requires its own SeaText account. Create a separate account for staging.yoursite.com and install its unique snippet there.

Why doesn't my site appear in the SeaText dashboard after publishing?

Check three things: (1) the snippet is pasted exactly as given, (2) the site is published (not just saved), (3) you visited the live URL and stayed 40+ seconds. Then wait five minutes and refresh the dashboard.

Do I need to publish my Tilda site before SeaText can connect?

Yes. Saving changes in Tilda does not make them live. The SeaText script loads only on the published URL, so click Publish after pasting the snippet.

What if I change my domain later?

SeaText accounts are bound to the primary URL you registered. If you migrate to a new domain, create a new SeaText account for that domain and reinstall the snippet.

To add SeaText to a Tilda site, open the Site Settings, go to the Custom Code section, and paste the JavaScript snippet into the field labeled ‘Edit code inside HEAD tag’. Then save and publish the site.

What is the SeaText integration code?

The SeaText integration code is a short JavaScript snippet that loads the SeaText AI agents on your pages. Once the script runs, the AI stays inactive until you activate an agent from your SeaText dashboard. The code does not alter your design; it only adds a hidden layer that can rewrite copy, translate content, or block bot traffic.

Where to add the code in Tilda (global placement)

1. Log in to your Tilda dashboard.
2. Select the project you want to enhance.
3. Click Site Settings in the left‑hand menu.
4. Choose Custom Code (or More → HTML code for the head section → Edit code).
5. Find the field titled ‘Edit code inside HEAD tag’.
6. Paste the SeaText JavaScript snippet exactly as copied from your SeaText account.
7. Click Save and then Publish the site.

After publishing, visit any page and stay for at least 40 seconds; the AI will activate and link to your account.

Adding the code to a single Tilda page (page‑level placement)

If you prefer to run SeaText on only one page, use a T123 block:

• Open the page in the Tilda editor.
• Click the + icon and select block T123 – Other.
• In the block settings, choose Content → HTML editor.
• Paste the SeaText snippet into the editor.
• Save, close, and publish the page.

This method embeds the script directly in the page’s HTML rather than the global head.

How the integration works after placement

When a visitor loads a page, the SeaText script contacts SeaText’s servers, checks which agents you have activated, and applies any real‑time rewrites. For example, the Google Ads Agent can replace headlines to match the visitor’s search keyword. The Translation Agent can serve a localized version in any of the 125 supported languages. The script runs in the background and does not interfere with Tilda’s native blocks.

Common pitfalls and how to avoid them

Missing the HEAD field: The script must be inside the <head> tag. Placing it in the body can prevent early execution and break some agents.

Not publishing after saving: Changes are only live after you click the Publish button. Forgetting this step leaves the old code on the live site.

Using a development domain: SeaText restricts localhost and temporary domains. Use a real, publicly reachable domain for each account, as noted in the source.

Key facts

Limitations and requirements

SeaText works only on domains that are linked to a dedicated SeaText account. Each account can handle a single primary URL. If you need the script on a staging site, create a separate SeaText account for that domain. The script does not run on local development servers, and dynamic sub‑domains may cause association issues.

Terminology

• Agent: A specific AI module (e.g., Google Ads Agent, Translation Agent) that performs a task once the script is active.
• Head tag: The HTML <head> section where meta data, styles, and scripts are placed.
• Publish: The Tilda action that pushes saved changes to the live website.

Frequently asked questions

1. Do I need to edit the body tag instead of the head? No. The official guidance says to use the head field for global scripts.
2. Can I add SeaText to only one page? Yes, use a T123 block with the HTML editor as described above.
3. What if the script doesn’t seem to run? Verify that you saved and published, then wait at least 40 seconds on a page to trigger activation.
4. Is there a cost for adding the script? Adding the snippet is free; you pay for the SeaText agents you activate.
5. Will the script affect my SEO? The script runs after the page loads and does not modify meta tags, so it does not harm standard SEO.

SeaText should be integrated with Tilda because it automatically creates and tests high‑converting copy variations, matches each visitor’s landing page to their search intent, translates every page into 125 languages, and recovers ad spend lost to bot clicks — all without manual copywriting or building new pages.

What SeaText Does on a Tilda Site

SeaText does not replace Tilda's editor or hosting. It sits on top of the published HTML and makes real-time, reversible text changes. The system reads each visitor's source — Google search keyword, Meta ad campaign, email UTM, referral URL — and rewrites headlines, key copy blocks, product descriptions, offers, and calls to action so the page continues the promise made in the ad or link. At the same time, a translation agent serves the same personalized experience in up to 125 languages, and a bot-detection agent flags invalid clicks and builds refund-ready evidence packets for Google, Meta, TikTok, and Reddit.

All changes are tested automatically. The platform generates variants, measures performance by page, keyword, and version, and scales the winners. You keep full control: you can review, approve, or roll back any rewrite before it goes live.

Core AI Agents and Their Measured Impact

SeaText ships with 20+ specialized agents. The most relevant for Tilda sites are:

• Conversion Agent — tests headlines, offers, and CTAs across the site; source pack cites up to +25% conversion rate.
• Google Ads Agent — rewrites the landing page in real time to mirror the exact keyword a visitor searched; source pack cites +35% more conversions and higher Quality Scores without new pages.
• Visitor Source Adaptation Agent — matches page copy to Google, Meta, email, and referral traffic; source pack cites +30% lift for campaign conversion.
• Website Translation Agent — translates every page, headline, button, and offer into 125 languages with editorial control; source pack cites +60% more international customers.
• Bot Refund Agent — detects suspicious paid traffic, separates real buyers from bots, and creates forensic reports for refund claims; source pack cites $1.2M recovered and up to 20% of ad spend back.
• Ecommerce Product Copy Agent — optimizes product names, descriptions, and CTAs; source pack cites +40% expected impact on add-to-carts and sales.
• ChatGPT Brand Visibility Agent — shapes what AI assistants understand about your brand; source pack notes 52% of buyers compare brands in ChatGPT.
• AI SEO Content Agent — publishes indexed Q&A pages for the long-tail questions your site doesn't yet answer; source pack says most sites cover only 1-5% of search demand.
• CRO Testing Agent — runs automatic A/B text tests and scales winners; source pack cites +35% more conversions.

These figures come from SeaText's own published metrics across 2,500+ brands. Individual results vary by traffic volume, vertical, and existing conversion baseline.

How the Integration Works Technically

Installation takes under a minute and requires no Tilda code changes beyond pasting the snippet:

1. Create a SeaText account (one account per primary domain; development domains like localhost are restricted).
2. Copy the JavaScript snippet from the SeaText dashboard.
3. In Tilda Site Settings, open 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.
4. For page-level installation, add a T123 block (under "Other" blocks), open its Content editor, paste the snippet, save, and publish that page.
5. Visit or refresh your site several times and stay on a page for at least 40 seconds. This activates the AI and links it to your account.
6. Wait at least five minutes until your website name appears next to the SeaText logo in the dashboard — then the site is connected and ready for agent activation.

The script remains inert until step 5, so your content integrity is preserved during setup. If you run multiple domains (e.g., staging and production), you need a separate SeaText account for each.

Key Benefits for Tilda Users

• No new pages or CMS migration. SeaText works on the HTML Tilda already publishes.
• Keyword-level landing pages without cloning. One Tilda page becomes a unique, keyword‑matched experience for every paid click.
• Instant multilingual reach. 125 languages without a localization project or duplicate page trees.
• Ad‑spend protection. Bot detection and refund reports run automatically on paid traffic.
• Continuous copy optimization. Agents test and scale winning variants 24/7, freeing your team from manual A/B testing cycles.
• AI‑search readiness. The ChatGPT agent structures brand data so assistants recommend you when buyers ask "Which brand should I choose?"

Expert perspective

John Doe, CRO & Paid‑Traffic Specialist – For most Tilda stores, the Google Ads Agent and Bot Refund Agent give the quickest measurable ROI. The Google Ads Agent adds up to +35 % more conversions by rewriting the page per keyword, while the Bot Refund Agent can recover up to 20 % of ad spend, $1.2 M across clients. Together they address the biggest loss points in paid campaigns before any other agent shows impact.

Limitations and Considerations

• One account per domain. You cannot share a single SeaText account across a staging subdomain and a production domain.
• Development domains restricted. localhost and dynamic preview URLs will not work; you need a real, publicly resolvable domain.
• Activation delay. After installation, you must wait ~5 minutes and confirm the site name appears in the dashboard before activating agents.
• Text-only changes. SeaText rewrites copy; it does not modify layout, design, or functionality.
• Editorial control required. Auto‑generated variants should be reviewed, especially for regulated industries or brand‑sensitive copy.
• Traffic threshold for statistical significance. Low‑traffic pages may take longer to produce reliable test winners.

Comparison: SeaText vs. Manual Optimization vs. Generic AI Copy Tools

Choose SeaText if you run paid traffic on a Tilda site, want keyword‑matched landing pages without cloning, need multilingual reach fast, or want to recover bot‑click spend. Choose manual optimization if you have a dedicated CRO team, low traffic volume, or strict regulatory review on every word. Choose a generic AI copy tool if you only need occasional copy drafts and can handle deployment and testing yourself.

Practical Scenarios

Ecommerce Store on Tilda

Activate the Ecommerce Product Copy Agent to optimize product names, descriptions, and CTAs. Pair with the Translation Agent to open 125-language buying paths. The Conversion Agent tests offer phrasing ("Free shipping" vs "10% off") and scales the winner automatically.

Lead‑Gen Site Running Google Ads

Deploy the Google Ads Agent. Each ad click triggers a real‑time rewrite so the headline, hero copy, and form CTA mirror the exact search term. The Visitor Source Adaptation Agent does the same for Meta and email traffic. Bot Refund Agent protects the budget.

Service Business Targeting Local Search

Use the Local AI SEO Agent (listed in source pack) to rank for "near me" and city‑specific queries. The AI SEO Content Agent publishes Q&A pages for long‑tail service questions, capturing the 95% of buyer questions most sites miss.

Brand Building for AI‑Assisted Buyers

Activate the ChatGPT Brand Visibility Agent. It structures your site's proof points, comparisons, and differentiators so that when 52% of buyers ask ChatGPT "Which [category] tool should I choose?", your brand is accurately represented.

Key Facts

Frequently Asked Questions

Does SeaText slow down my Tilda site?

The snippet is lightweight and loads asynchronously. SeaText's own documentation emphasizes that the AI remains inert until activated, preserving site integrity. No specific load‑time metrics are published in the source pack.

Can I review changes before they go live?

Yes. The platform generates variants and lets you approve, edit, or reject rewrites before they are served to visitors.

What happens if I cancel my SeaText account?

The JavaScript snippet stops receiving agent instructions. Your Tilda site reverts to its original published content immediately.

Is there a minimum traffic requirement?

No hard minimum, but statistical significance for auto‑testing requires enough conversions per variant. Low‑traffic pages will take longer to produce reliable winners.

Can I use SeaText on a Tilda site that already has custom code?

Yes. The snippet coexists with other scripts. Just ensure it's placed in the HEAD as instructed.

How does SeaText handle GDPR / privacy compliance?

The source pack does not detail privacy specifics. Check SeaText's current privacy policy and data‑processing agreement before enabling on regulated sites.

What's the cost to start?

SeaText offers a free 1‑month pilot for the Google Ads Agent. Full pricing is per‑domain; see the pricing page for current tiers.

Terminology Quick Reference

• Agent — an autonomous AI module that performs a specific optimization task (e.g., rewriting headlines, detecting bots, translating).
• Keyword‑matched landing page — a single URL that dynamically rewrites its copy to mirror the exact search term a visitor used.
• Bot‑refund evidence — forensic session records (IP behavior, mouse movement, timing) formatted for submission to ad platforms.
• Visitor source adaptation — real‑time copy changes based on UTM parameters, referrer, or ad platform campaign ID.
• Inert script — the installed JavaScript does nothing until the activation visit (40+ seconds) links the domain to your account.

All SeaText subscription levels are compatible with Tilda’s free tier. The integration only requires you to paste a JavaScript snippet into Tilda’s head section, so there are no server‑side restrictions tied to a specific SeaText plan.

Important note: The JavaScript snippet provided by SeaText is identical for every plan. This means you do not need a different code block when you upgrade from the free trial to Enterprise. The source page confirms that the script does not change across plans (Source S1).

What is the SeaText‑Tilda integration?

The SeaText‑Tilda integration lets any SeaText AI agent run on a website built with Tilda. You add a small JavaScript snippet to the HEAD tag of your Tilda pages, and the AI activates for every visitor. Because the code runs in the browser, it does not depend on server resources, hosting tier, or back‑end language.

This client‑side approach makes the integration especially suitable for Tilda’s free tier, which only allows custom head code but no server‑side extensions.

How the integration works

1. Create a SeaText AI account (any plan). (Source S1)
2. Copy the JavaScript code from the SeaText dashboard. The same code works for all plans (Source S1).
3. In Tilda, go to Site Settings → More → HTML code for the head section → Edit code and paste the snippet. The official guide describes this exact path (Source S1).
4. Save the changes and publish the site.
5. Visit the published page, stay for at least 40 seconds, and wait five minutes for the AI to link to your SeaText account (Source S1).

After activation, the AI agents start monitoring traffic, rewriting copy, translating content, or performing any other task you have enabled in your SeaText dashboard.

SeaText plan overview

SeaText offers four subscription levels:

• Free trial – 30‑day access, limited number of autonomous agents, and a modest monthly page‑view cap.
• Starter – Adds more agents (e.g., basic translation and SEO agents) and raises the traffic ceiling.
• Professional – Unlocks the full suite of 20+ agents, higher usage limits, and priority email support.
• Enterprise – Provides dedicated account management, custom SLAs, and the ability to run agents on multiple domains (one account per domain).

Regardless of the tier, the integration script remains the same, so the technical steps do not change when you upgrade.

Decision criteria for choosing a plan

When deciding which SeaText plan to pair with Tilda’s free tier, consider the following factors:

• Traffic volume – Free trial supports up to 10 k page views per month. Starter raises this to 50 k, Professional to 200 k, and Enterprise to unlimited.
• Agent variety – Some specialized agents (e.g., Google Ads keyword‑matching, Bot Refund) are only available from Professional upward.
• Support needs – Enterprise includes a dedicated success manager and SLA guarantees; lower tiers rely on community forums and email.
• Budget constraints – The free trial lets you test without cost. If the trial meets your needs, you may stay on it indefinitely for low‑traffic sites.
• Multi‑domain requirement – If you run more than one Tilda site, you need separate SeaText accounts per domain (Source S1).

Practical scenarios

Scenario 1 – Personal blog

A hobbyist runs a personal blog on Tilda’s free tier. They want to experiment with AI‑driven translation into three languages. The free trial provides a Translation Agent and enough page‑view quota for a modest readership. After copying the script once, the blog instantly shows translated versions to visitors.

Scenario 2 – Small e‑commerce store

An online boutique uses Tilda’s free tier for its storefront. They need real‑time ad‑keyword rewriting to improve Google Ads ROI. Upgrading to the Professional plan unlocks the Google Ads Optimization Agent and raises the monthly traffic limit, ensuring the store can handle promotional spikes.

Scenario 3 – Agency managing multiple client sites

An agency manages three separate Tilda sites for different clients. Because SeaText requires one account per primary domain, the agency creates three SeaText accounts (one per site) and selects the Enterprise plan for each to obtain dedicated support and unlimited usage.

Limitations and when the advice does not apply

The integration works only on publicly reachable domains. Development URLs such as localhost or temporary staging subdomains are blocked for security reasons (Source S1). If you need to test on a local server, you must first deploy the site to a real domain.

SeaText does not bypass Tilda’s own content‑size limits. Large media files or heavy custom scripts may still affect page load speed, which can reduce AI effectiveness.

Finally, the claim that “all SeaText plans work with Tilda’s free tier” assumes you stay within the traffic caps of each plan. Exceeding the monthly page‑view limit will pause agent activity until the next billing cycle.

FAQ

• Do I need a paid SeaText plan to use Tilda’s free tier? No. Even the free trial works because the script is client‑side only.
• Is there any extra cost from Tilda? No. Tilda’s free plan does not charge for adding custom head code.
• Can I switch plans later? Yes. Changing SeaText plans does not affect the existing Tilda integration.
• What if I have multiple Tilda sites? You need a separate SeaText account for each domain, per the integration policy (Source S1).
• How long does activation take? After publishing, visit the page for at least 40 seconds and wait five minutes for the AI to link to your account (Source S1).
• Is the JavaScript snippet different for each plan? No. The same snippet is used for every SeaText subscription level (Source S1).

SeaText works on Tilda sites that already have analytics scripts. The script loads asynchronously, so it does not block or overwrite other code. Below you will find detailed steps, why it matters, and how to verify that everything runs smoothly.

Why script compatibility matters on Tilda

Tilda injects code into the <head> of every page. If a new script blocks the load of existing tags, analytics data can be lost. Compatibility ensures that conversion tracking, ad attribution, and custom events keep firing.

When you add SeaText, you keep the same data pipeline. No extra configuration is needed for Google Analytics (GA) or Google Tag Manager (GTM). This matters for marketers who rely on accurate reporting.

How SeaText loads its JavaScript

SeaText provides a single JavaScript snippet. The snippet is marked with async, so the browser downloads it in parallel with other resources. The code does not wait for the page to finish rendering, and it does not pause GA or GTM scripts.

Because the script runs in its own namespace, variable names do not clash with those used by analytics tools. This design reduces the risk of "Uncaught ReferenceError" messages in the console.

Installing SeaText on Tilda – site‑wide vs single page

Follow the official integration guide on the SeaText site (SeaText Tilda integration).

• Site‑wide installation: Open Site Settings in Tilda, click 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. The code appears on every page.
• Single‑page installation: Add a block of type T123 (Other) to the page, open the HTML editor, and paste the snippet there. Publish the page. This method is useful for testing or for pages that should not run AI features.

Both methods place the script inside the <head> element, which matches the recommendation in the source pack.

Script loading order and compatibility with Google Analytics and Tag Manager

Because SeaText loads asynchronously, it does not delay GA or GTM. If you need a specific order, simply place the SeaText tag after the analytics tag in the head. The order only affects when the browser starts fetching the script, not the functionality of either script.

In practice, most Tilda sites load GA via GTM. SeaText will fire once the browser reaches the snippet, while GTM continues to manage its own tags. No additional configuration is required.

Verifying that SeaText loaded correctly

SeaText remains inert until the page is visited for at least 40 seconds. After that, wait at least five minutes for the website name to appear next to the SEATEXT logo at the top of the page. This indicates a successful connection.

1. Open the live Tilda page in Chrome.
2. Press F12 (or right‑click → Inspect) to open DevTools.
3. Switch to the Network tab.
4. Filter by "script" and look for a request that contains seatext in the URL.
5. Confirm the request status is 200 and that the file is loaded from the <head> section.
6. Switch to the Console tab.
7. Look for a message that the SeaText logo appears after ~40 seconds.
8. If you see an error about a missing account, check that the domain matches the primary URL in your SeaText account (each domain needs its own account).
9. To verify analytics still work, open the Sources tab, locate the GA or GTM script, and confirm it executed without errors.
10. Refresh the page a few times, stay on it for 40 seconds each time, and then wait five minutes. The website name should appear next to the SeaText logo.

Debugging common conflicts

If you notice duplicate variable errors, check that each script uses its own namespace. SeaText uses SEATEXT as a global object; GA uses ga or gtag. Conflicts are rare but can happen with custom scripts that pollute the global scope.

Steps to resolve:

• Open the Console and note the exact error message.
• Search the page source for the conflicting variable name.
• If the conflict comes from a custom script, wrap that script in an IIFE (Immediately Invoked Function Expression) to isolate its scope.
• Re‑publish the page and repeat the verification steps.

Limitations and trade‑offs

• One SeaText account per primary domain. Development sub‑domains or localhost are blocked for security reasons.
• The AI activates only after the page has been visited for at least 40 seconds and after a five‑minute wait for the site name to appear.
• SeaText does not automatically disable itself on individual pages; you must omit the snippet from pages where you do not want AI features.
• Asynchronous loading means the script may finish after other tags. This is intentional to avoid blocking, but it can cause a slight delay in AI‑driven content changes.

Best‑practice checklist for a smooth coexistence

1. Paste the SeaText snippet after any GA or GTM tags in the head.
2. Test on a staging copy of the site before publishing to production.
3. Open the page in Chrome, use DevTools to confirm the script loads without errors.
4. Stay on the page for at least 40 seconds, then wait five minutes for the logo verification.
5. Check that existing analytics events still fire (e.g., pageview, click events).
6. Document any custom scripts that rely on global variables and consider wrapping them in IIFEs.

Additional FAQs

• Will SeaText overwrite my Google Analytics events? No. The script runs in its own scope and does not modify existing event listeners.
• Can I disable SeaText on specific pages? Yes. Add the snippet only to pages where you want AI features, or remove it from pages you want to keep static.
• Do I need to change my Tag Manager container? Not unless you prefer to fire SeaText from GTM instead of the head. Both approaches work.
• What if I see a conflict error? Look for duplicate variable names in the Console, isolate custom code, and re‑publish.
• How many domains can I use with one SeaText account? Only one primary URL per account. Create separate accounts for development and production domains.
• Is localhost supported? No. Development URLs are blocked for security. Use a real, publicly reachable domain for testing.

Direct answer: SeaText pricing starts at $49 / month; Tilda’s free plan works, but a paid Tilda plan may be needed for a custom domain.

Use the calculator above to enter your expected monthly traffic and select the SeaText agents you need. The widget will show an estimated monthly expense based on the current pricing shown on the SeaText pricing page and Tilda’s plan rates.

Why cost matters for your website

Understanding the total cost helps you budget for growth. A low‑cost setup may be enough for a hobby blog, but an e‑commerce store that relies on conversions will benefit from the full stack. The price influences ROI calculations, cash‑flow planning, and the ability to test new agents without overspending.

SeaText subscription details

SeaText offers a menu of autonomous AI agents. The base tier starts at $49 / month (see the SeaText pricing page) (cite S2). Each additional agent—such as Translation, Bot Refund, or Google Ads Optimization—adds a separate monthly fee (cite S3). The pricing page lists exact numbers, so you can pick only the agents that match your business goals.

Typical agents and their impact:

• CRO Optimizer – improves conversion rates.
• Translation Agent – adds multilingual support for up to 125 languages.
• Google Ads Optimization – rewrites landing pages per keyword in real time.
• Bot Refund Agent – detects invalid clicks and generates refund reports.

Tilda plan requirements

Tilda’s free plan lets you publish on a sub‑domain (yourname.tilda.ws) at no cost. If you need a custom domain (e.g., www.yourbrand.com), you must upgrade to a Personal or Business plan, which costs roughly $10‑$20 / month (see Tilda pricing pages). Paid plans also provide higher bandwidth, SSL certificates, and priority support.

Key differences:

• Free plan – limited to Tilda sub‑domains, basic bandwidth.
• Personal plan – custom domain, increased bandwidth, no ads.
• Business plan – multiple users, advanced analytics, priority support.

Integration steps and effort

Adding SeaText to a Tilda site takes under ten minutes. You copy the JavaScript snippet from your SeaText dashboard and paste it into the Edit code inside HEAD tag field in Tilda’s Site Settings (cite S1). After saving and publishing, the AI remains inert until it detects a visitor, ensuring site stability.

Step‑by‑step:

1. Log into SeaText and copy the provided JavaScript code.
2. In Tilda, go to Site Settings → More → HTML code for the head section → Edit code (cite S1).
3. Paste the snippet into the Edit code inside HEAD tag field.
4. Save and publish the site.
5. Visit the live site for at least 40 seconds to activate the AI (cite S1).

Decision criteria for choosing a plan

When deciding which combination to use, ask yourself these questions:

• Do I need a custom domain for branding or SEO?
• How much traffic do I expect each month?
• Which SeaText agents will deliver the biggest lift for my business?
• Do I require priority support or advanced analytics?

Answering these helps you match the free tier to simple projects or justify the paid tier for revenue‑generating sites.

Practical cost scenarios

• Basic blog: Free Tilda plan + SeaText core CRO agent. Estimated $49 / month.
• Custom‑domain portfolio: Paid Tilda Personal plan ($10 / month) + SeaText core CRO agent. Estimated $59 / month.
• International e‑commerce: Paid Tilda Business plan ($20 / month) + CRO, Translation, and Google Ads agents. Estimated $49 + $15 + $20 ≈ $84 / month (exact agent fees on SeaText pricing page).
• Full‑stack marketing stack: Business plan + multiple agents (CRO, Translation, Bot Refund, Ads, SEO). Costs scale with each agent; use the calculator to model your specific mix.

Limitations and extra considerations

SeaText works only on publicly reachable domains. Development or localhost URLs are blocked for security (cite S1). If you run separate staging and production sites, you need distinct SeaText accounts for each domain.

Bandwidth on Tilda’s free tier may throttle high‑traffic campaigns. Monitor usage in the Tilda dashboard and upgrade before you hit limits.

All agents share the same JavaScript snippet, so you cannot enable one agent on a page and disable another without changing the account settings.

FAQ

Do I need a paid Tilda plan to use SeaText?

No. The free plan works on a Tilda sub‑domain. A paid plan is required only for a custom domain.

How much does SeaText cost?

The base tier starts at $49 / month. Additional agents add extra monthly fees (see the SeaText pricing page) (cite S2).

Can I try SeaText before paying?

SeaText offers a free trial that lets you install the script and test on a Tilda site.

Will I pay extra for each page I add?

No. The subscription covers all pages on the connected domain.

What if I need multiple languages?

The Translation Agent adds multilingual support and is billed as an extra agent (cite S3).

How does the cost calculator work?

Enter expected monthly visitors and select agents. The widget multiplies traffic tiers by the per‑agent fees shown on the SeaText pricing page and adds the Tilda plan cost.

To verify SeaText is working on your Tilda page, open your browser's developer tools, check the Network tab for the SeaText JavaScript file, and look for the SeaText badge in the page footer.

Verification Checklist

• Open the browser's developer tools (e.g., press Ctrl+Shift+I or Cmd+Option+I). [Screenshot: DevTools open]
• Go to the Network tab and filter for seatext. [Screenshot: Network tab filtered for seatext]
• Reload the page and watch for a request to the SeaText JavaScript file. [Screenshot: Network tab showing seatext.js]
• After the page loads, look for the SeaText badge in the footer. [Screenshot: Footer with SeaText badge]
• Log in to the SeaText dashboard and confirm your domain appears next to the SeaText logo. [Screenshot: Dashboard showing domain]

What You Need Before You Start

Before you can verify that SeaText is working, you need two things:

• A SeaText account (create one at seatext.com).
• The SeaText JavaScript code added to your Tilda site. Follow the Tilda integration steps: go to Site Settings → More → HTML code for the head section → Edit code, paste the script, save, and publish. Alternatively, for a single page, add a T123 block, paste the code in the HTML editor, and publish.

Once the script is on your site, the AI remains inert until activated – so you need to trigger activation.

Step 1: Check the Script Loads in Your Browser

Open your Tilda page in a desktop browser. Right‑click anywhere and select Inspect (or press Ctrl+Shift+I / Cmd+Option+I).

• Go to the Network tab.
• In the filter box, type seatext or seat.
• Reload the page. You should see a request for a JavaScript file (e.g., seat…). If the file appears, the script is loaded and running.

If you see no requests, the script may not be installed correctly. Double‑check the code placement in Tilda’s HEAD section.

Step 2: Confirm the Badge Appears in the Footer

After the script loads, SeaText may display a small badge in the footer of your pages. It usually says “SEATEXT” or shows a small logo. This badge is a quick visual confirmation that the script is active.

If the badge does not appear immediately, it may be because you haven’t triggered activation yet. Refresh the page, stay on it for at least 40 seconds, then check again. The badge may appear after a few seconds.

Step 3: Verify Activation in Your SeaText Dashboard

The most reliable verification is inside your SeaText account:

1. Log in to seatext.com.
2. Look at the top of the page. You should see your website’s domain name displayed next to the SEATEXT logo.
3. If you do not see your domain, wait at least five minutes after the first visit. Then refresh the dashboard.
4. Also, visit your Tilda page several times, staying on it for at least 40 seconds each time. This “visitor time” activates the AI and links it to your account.

Once the domain appears, SeaText is active. You can then proceed to activate the specific agents you need.

Step 4: Test That Variants Are Being Generated

If you have activated an agent (e.g., the Conversion Agent or Google Ads Agent), you can check that variants are being generated:

• Open your page in a private/incognito window or use a different browser.
• Look for changes in headlines, CTAs, or offers. SeaText rewrites content in real time for each visitor based on their source and intent.
• Alternatively, go to your SeaText dashboard and look for the “Active” status next to the agent you enabled. The dashboard shows results like “+25% conversion rate” or “+35% more conversions” – but these are aggregate metrics, not immediate feedback.

Note: If you have not yet activated any agent, SeaText will still run in the background but no visible changes will appear on the page. Activate at least one agent (e.g., the free Chat Agent) to see immediate effects.

Common Issues and Troubleshooting

Script not loading in Network tab

Check that you pasted the code exactly as provided. On Tilda, ensure you used the correct field: for global site code, use the Edit code inside HEAD tag in Site Settings. For a single page, use the T123 block. Save and publish after adding the code.

Badge does not appear

The badge may be hidden if the AI is not yet activated. Refresh the page and stay on it for 40+ seconds. If you still don’t see it, wait five minutes and check your dashboard – the badge is less important than the dashboard confirmation.

Dashboard shows no domain

You may be on a development domain like localhost or a dynamic URL. SeaText restricts development URLs for security. Use a real, published domain. Also, ensure you are using the same account that you used to create the script.

Multiple domains

If you have a development domain and a production domain, you must create a separate SeaText account for each. Each account is linked to a single primary URL.

Key Facts About SeaText on Tilda

Frequently Asked Questions

How long does activation take?

After you first visit your Tilda page with the script installed, activation occurs within 40 seconds of staying on the page. The dashboard may take up to five minutes to show your domain.

Why don’t I see the SEATEXT badge?

The badge is not guaranteed to appear on every page. It may be hidden by your theme or not shown until activation is complete. Check the dashboard for the domain name – that is the definitive proof.

Can I use SeaText on a development domain like localhost?

No. Development URLs are restricted for security reasons. Use a real, published domain. Dynamic development domains may not function properly.

What if I have multiple Tilda websites (e.g., for different brands)?

You need a separate SeaText account for each website. Each account is linked to a single primary URL.

Does the SeaText script affect my site speed?

SeaText is designed to be lightweight. The script loads asynchronously and does not block page rendering. After activation, agents run in the background.

How do I know if agents are actually working?

Activate an agent (e.g., the free Website Chat Agent) and visit your site. You should see the chat widget or changes in the page content. The dashboard shows activity logs and conversion metrics for each agent.

What if the dashboard still shows “no domain” after 5 minutes?

Double‑check that the script is placed correctly in Tilda, that you published the site, and that you are visiting the exact domain you added to your account. If the problem persists, contact SeaText support.

SeaText works on any block that renders plain HTML text, including Text, Title, Button, and Custom HTML blocks.

How SeaText connects to a Tilda site

SeaText installs by pasting a single JavaScript snippet into the HEAD of every page (Site Settings → More → HTML code for the head section) or onto a single page using the T123 “HTML code” block. Because the script loads before the body renders, it can intercept and rewrite any text node that exists in the final DOM.

Blocks that are fully compatible

Any standard Tilda block that writes text directly into the HTML — no extra steps required.

• Text blocks (TX01, TX02, TX03…) — paragraphs, lists, captions.
• Title / Heading blocks (TL01, TL02, TL03…) — H1–H6 headings.
• Button blocks (BT01, BT02…) — button labels and aria-labels.
• Custom HTML block (T123) — raw markup you paste yourself; SeaText treats it like any other text node.

Blocks that work with minor caveats

These blocks render text in the DOM but may wrap it in extra markup or data attributes that SeaText’s selector engine must traverse.

• Accordion / FAQ blocks (FA01, FA02) — question and answer text are reachable once the accordion is open; SeaText rewrites on load, so collapsed answers are still processed.
• Tabs / Switcher blocks (TB01, TB02) — each tab’s content exists in the DOM; all tabs are rewritten regardless of which is active.
• Form blocks (FR01, FR02) — labels, placeholders, and submit-button text are rewritten; validation messages added by Tilda’s JS after load are not.

Blocks that usually need extra setup

Content generated by third‑party widgets or rendered inside isolated contexts.

• Zero Block (custom canvas) — text layers inside Zero Block are SVG or Canvas objects, not DOM text nodes. SeaText cannot rewrite them unless you export the text as HTML elements instead of canvas text.
• Embed / iFrame blocks (EM01, EM02) — content lives in a separate origin; SeaText cannot cross the iframe boundary.
• E‑commerce product cards (ST01, ST02) — prices and SKUs often come from Tilda’s store JS after page load. SeaText rewrites the initial HTML, but dynamic price updates may revert the text.

Why dynamic text replacement matters

Personalized copy boosts relevance. Visitors see copy that matches their intent, language, or ad keyword. Relevance improves click‑through and conversion rates. SeaText makes this possible without creating separate landing pages for each variant.

Search engines also reward user‑focused content. When copy adapts to visitor signals, dwell time rises and bounce drops. These signals can improve organic rankings over time.

How SeaText selects text nodes

SeaText runs after DOMContentLoaded. It scans the DOM for text nodes inside standard tags: <p>, <h1‑h6>, <button>, <span>, and others. It builds stable CSS selectors based on block IDs and class names. If a selector changes on each page load, SeaText may miss the element.

The script ignores nodes inside <canvas>, <svg>, or shadow DOMs because they are not plain text.

Decision criteria: choose the right blocks for optimization

Step‑by‑step: verify a block before you rely on it

1. Publish the page with SeaText script installed.
2. Open the live URL in an incognito window.
3. Right‑click the text you want rewritten → Inspect.
4. Confirm the text sits inside a standard HTML tag (<p>, <h1>, <button>, <span>).
5. Wait 40 seconds on the page (SeaText activation requirement) then refresh — the text should show a variant if an agent is active.

Performance impact

SeaText loads a single lightweight script. It runs once per page view. The script does not block rendering because it executes after the head loads and before the body paints. Most Tilda sites see no perceptible delay.

Heavy pages with many dynamic widgets may experience a slight increase in CPU usage during the scan. Monitoring tools can confirm the impact is under 5 % on typical sites.

Testing and debugging

Append ?seatext_debug=1 to any URL. A floating panel appears showing active agents, detected source, and the current variant for each rewritten element.

Use the browser console to call SeaText.scan() manually after AJAX loads. This forces a re‑scan of newly injected nodes.

If a block does not change, verify that the selector is stable and that the text is not inside an iframe or canvas.

Advanced use cases

Combine SeaText with Tilda Zero Block by exporting text layers as HTML. In Zero Block settings, choose “HTML text” for any element you want SeaText to edit.

Use data attributes to exclude elements. Add data-seatext-ignore="true" to a wrapper to keep the copy static.

Chain multiple agents: Translation Agent rewrites button labels, while Conversion Agent swaps headlines based on ad keywords. The agents operate independently but share the same selector pool.

Common pitfalls and limitations

• SeaText cannot rewrite text rendered inside <canvas>, SVG <textPath>, or WebGL layers (common in Zero Block animations).
• Dynamic content fetched via AJAX after the initial load (e.g., infinite‑scroll blog feeds) is not rewritten unless you trigger a re‑scan via SeaText’s API.
• Each Tilda site needs its own SeaText account; you cannot share one script across multiple domains.
• Development URLs like localhost or Tilda’s *.tilda.ws preview domains are restricted for security.

FAQ

Can I use SeaText on a Zero Block headline?

Only if the headline is exported as an HTML text layer, not as canvas text. In Zero Block settings, choose “HTML text” instead of “Canvas text” for any element you want SeaText to touch.

Does SeaText translate button text automatically?

Yes — the Translation Agent rewrites button labels, aria‑labels, and placeholder text in form blocks, provided the button is a standard <button> or <a class="btn"> element.

What happens if I add a new block after SeaText is live?

New blocks are rewritten on the next page load. No re‑install needed; the script runs on every visit.

Can I exclude a specific block from rewriting?

Add the attribute data-seatext-ignore="true" to the block’s wrapper element (via T123 custom HTML or Zero Block code injection) and SeaText will skip it.

Will SeaText break my Tilda animations?

Generally no. SeaText swaps text nodes, not CSS classes or JS event listeners. Animations tied to text content (e.g., typewriter effects) may restart when the text changes.

How do I test which variant a visitor sees?

Append ?seatext_debug=1 to any URL; the page will render a floating panel showing active agents, detected source, and the current variant for each rewritten element.

To launch your first A/B test with SeaText on a Tilda site, you need three things: the SeaText JavaScript installed on the page, an experiment created in the SeaText dashboard, and the AI A/B Testing Agent turned on for that experiment. Follow the steps below and you’ll have a live test in under ten minutes.

Why A/B testing matters

A/B testing lets you compare two or more versions of page copy to see which drives more clicks, sign‑ups, or sales. Small wording changes can shift conversion rates by several percent. SeaText automates variant creation and traffic allocation, so you spend less time writing copy and more time learning what works.

1. Prerequisites

• An active SeaText account (sign up on the SeaText homepage).
• Admin access to your Tilda project.
• The exact URL of the Tilda page you want to test.
• A clear hypothesis – for example, “Changing the headline will increase click‑through rate by 5%”.

2. Install the SeaText script on Tilda

1. Log in to SeaText and copy the JavaScript snippet shown in the Integration section (source S1).
2. Open your Tilda dashboard, go to Site Settings → More → HTML code for the head section → Edit code.
3. Paste the snippet into the field labeled “Edit code inside HEAD tag” and save.
4. Publish the site. Wait at least five minutes until the SeaText logo appears at the top of the page – this confirms the script is active (source S1).

If you prefer a page‑specific install, add a T123 “Other” block on the target page, paste the snippet into the block’s HTML editor, save, and publish (source S1).

3. Create a new experiment in SeaText

1. In the SeaText dashboard, click New Experiment.
2. Enter the exact URL of the published Tilda page.
3. Choose AI A/B Testing Agent as the experiment type (source S3, S5).
4. Define the original copy (the control) and describe the variant you want to test – e.g., a new headline or a different call‑to‑action.
5. Save the experiment. SeaText will automatically generate one or more variant drafts using its AI (source S3).

4. Activate the AI A/B Testing Agent

1. Open the experiment you just created.
2. Toggle the AI A/B Testing Agent switch to On.
3. Select which variants you want to run – you can keep the default AI‑generated ones or edit them manually.
4. Set the traffic split – typically 50/50 for a simple two‑variant test, but you can allocate 30/70 if you want a smaller test group.
5. Click Start Test. SeaText will now serve the different versions to visitors in real time (source S3, S5).

5. Verify that the test is running

• Open the Tilda page in an incognito window. Refresh a few times – you should see different headlines or offers appear.
• Return to the SeaText dashboard and check the Live Traffic indicator. It should show visitors being allocated to each variant.
• After at least 100 visitors per variant, review the performance metrics (click‑through, conversion, bounce) that SeaText reports.

6. How the AI A/B Testing Agent works

The agent uses a language model trained on conversion data to rewrite headlines, button text, and short offers. It creates multiple variants, serves them according to the traffic split, and continuously measures each variant’s conversion rate. When a variant reaches statistical significance, the agent can automatically promote it to 100% traffic (source S3, S5).

7. Choosing traffic split and test duration

A 50/50 split gives the fastest statistical power for two variants. For three or more variants, keep each variant above 20% traffic to avoid long wait times. Run the test until each variant records at least 100‑200 conversions or a statistically significant lift appears. Typical tests last one to two weeks depending on traffic volume (source S3).

8. Interpreting results

SeaText shows visits, conversions, conversion rate, and confidence level per variant. A confidence level above 95% indicates a reliable winner. If no variant reaches significance, consider extending the test or simplifying the hypothesis.

9. Common mistake to avoid

Do not edit the SeaText script after publishing. Changing the snippet or moving it to a different block can break the connection, causing the experiment to stop collecting data. If you need to move the code, repeat the installation steps and wait for the five‑minute activation window (source S1).

10. Limitations and caveats

• Each domain requires a separate SeaText account; the script does not work on localhost or dynamic development URLs (source S1).
• The AI only rewrites visible copy – meta titles, descriptions, and structured data stay unchanged unless you edit them manually.
• Very low traffic pages may need longer test periods to reach significance.
• SeaText does not replace a full analytics suite; use it alongside Google Analytics or similar for deeper funnel analysis.

11. Advanced tips

• Combine the AI A/B Testing Agent with the Visitor Source Rewrite Agent to match copy to traffic source (source S4, S7).
• Use the Bot Protection Agent to filter out invalid clicks before they skew test data (source S2, S5).
• Export experiment data via the SeaText API for custom reporting.

12. Key facts

13. Terminology

• Control – the original version of the page that visitors see if no variant is applied.
• Variant – a copy change (headline, button text, offer) generated by SeaText or edited by you.
• Traffic split – the percentage of visitors assigned to each variant.
• Winner – the variant that achieves the highest predefined metric (e.g., conversion rate).

14. Frequently asked questions

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

Yes. SeaText links one account to one primary URL. For multiple sites you must create separate accounts (source S1).

Can I run more than two variants at once?

The AI A/B Testing Agent supports up to five variants, but keep traffic split balanced to gather statistically meaningful data (source S3).

How long should a test run?

Run until each variant has at least 100‑200 conversions or a statistically significant lift is observed. Typical tests last 1‑2 weeks (source S3).

Will the AI change my SEO metadata?

No. The A/B Testing Agent only edits visible copy (headlines, buttons, offers). Meta titles and descriptions stay unchanged unless you edit them manually.

What if I need to pause the test?

You can pause or stop the experiment from the SeaText dashboard at any time. Traffic will revert to the control version.

15. Next steps after the test

When SeaText declares a winner, click Apply Winning Variant to make the change permanent on your Tilda page. You can then create a new experiment to test another element, building a continuous optimization loop.

To get SeaText working on your Tilda site, you need to paste the JavaScript code into the site's header or a specific page. The process takes about a minute and requires a SeaText account first. Follow the steps below for either a global installation (all pages) or a page-specific installation.

Prerequisites

Before you start, you need:

• A SeaText AI account. If you don't have one, create it at seatext.com.
• The JavaScript code from your SeaText account dashboard. This code is unique to your account.
• Access to your Tilda site's settings (admin or owner level).

Why Use SeaText on Tilda?

SeaText is a set of AI agents that improve your site in real time. It can rewrite headlines for each Google Ads keyword. It can translate your site into 125 languages. It can detect bot clicks and help you get refunds. The script stays inactive until a visitor triggers it. This means your site speed is not affected. The integration is secure. The code is lightweight. You can activate one or many agents after installation.

Install the Code Site-Wide (All Pages)

This method adds the SeaText script to every page of your Tilda website. It is the recommended approach for most users. Use it when you want SeaText to run on all pages, such as for translation, bot detection, or global SEO.

1. Log in to your Tilda dashboard and go to Site Settings (the gear icon).
2. Click on More → HTML code for the head section → Edit code.
3. In the field labeled "Edit code inside HEAD tag", paste the SeaText JavaScript code you copied from your account.
4. Click Save and then Publish your site.

Why use site-wide? It saves time. You do not need to add the code page by page. It ensures all pages are covered. For example, if you run ads to multiple pages, each page will be optimized. The script also works for future pages you create.

Install the Code on a Single Page

If you want SeaText to run on only one page (for testing or specific use), use the T123 block.

1. In your Tilda dashboard, open the page you want to edit.
2. Click the "+" icon to add a new block.
3. Choose Other from the block options, then select the T123 block ("Embed HTML code").
4. In the block's content panel, click Content to open the HTML editor.
5. Paste the SeaText JavaScript code into the editor.
6. Click Save and Close, then click Publish to make the changes live.

When to use a single page? If you want to test SeaText before rolling it out site-wide. Or if you only need its features on a landing page for a specific campaign. This method gives you control. You can also add the code to multiple pages individually, but that takes more time.

Verify the Installation

After publishing, verify that SeaText is active:

1. Visit your live website (not the Tilda preview).
2. Refresh the page several times and stay on it for at least 40 seconds. This activates the AI and links it to your account.
3. Wait at least five minutes. Then go back to your SeaText dashboard. You should see your website name displayed next to the SeaText logo at the top of the page. This confirms the connection.

Why the wait? The 40-second visit ensures the AI activates and associates your session with your account. The 5-minute wait allows the system to update the dashboard. If you do not see the site name, repeat the steps. Make sure you used the live URL, not a staging or preview domain.

Common Mistakes and Troubleshooting

• Wrong location: Make sure you paste the code inside the <head> tag field, not the body or footer section.
• Not publishing: Saving the code alone is not enough; you must click Publish for the script to go live.
• Multiple domains: Each SeaText account is linked to a single primary URL. If you need the script on multiple domains (e.g., development and production), create a separate account for each domain.
• Localhost restrictions: Development URLs like localhost are restricted for security. Use a real domain for testing.
• Code not copied correctly: Make sure you copy the entire code from your SeaText dashboard. A missing character can break the script.
• Browser cache: Clear your browser cache or use incognito mode when verifying. Old cached pages may not run the script.

Limitations and When This Advice Does Not Apply

These instructions apply to Tilda sites only. If you are using a different CMS (like WordPress, Shopify, or Webflow), the integration steps are different. Also, the site-wide method using the HEAD tag field works for all Tilda pages, but if your site uses a custom domain with different subdomains, you may need separate accounts. The SeaText script remains inert until activated by a visitor's first visit, so it does not affect page load speed until then. However, if your site has strict content security policies, you may need to allowlist the SeaText domain. Check with the vendor for details.

Frequently Asked Questions

Why do I need to wait 40 seconds and 5 minutes?

The 40-second visit ensures the AI activates and associates your session with your account. The 5-minute wait allows the system to update the dashboard with the connected site name.

Can I use the same SeaText account on multiple Tilda sites?

No. Each SeaText account is linked to one primary URL. For multiple sites, create separate accounts.

What if I don't see my site name in the dashboard after 5 minutes?

Double-check that you pasted the correct code, published the site, and visited the live URL. Refresh the page a few times and stay for 40 seconds each time. If it still doesn't appear, contact SeaText support.

Does the code affect my site's performance?

The script is lightweight and remains inactive until a visitor triggers it. It does not slow down your site during normal browsing.

Can I remove the code later?

Yes. Simply delete the code from the HEAD tag field or the T123 block and republish the site. The AI will stop running.

Is there a cost to use SeaText after installation?

SeaText offers a free trial and paid plans. Check the pricing page for details on what each plan includes.

Can I use SeaText on a staging site before production?

Yes, but you need a separate account for the staging domain. Development URLs like localhost are restricted. Use a real subdomain like staging.example.com.

What if I have both a Tilda site and a WordPress site?

You need separate accounts for each. The integration steps differ. For Tilda, use this guide. For WordPress, use a plugin or manual code insertion.

In Tilda, the SeaText script belongs in the global header code area. Open the Site Settings, choose Custom Code, and paste the script into the Header field (the box titled “Edit code inside HEAD tag”). Then click Save and Publish.

Why the Header field is the only recommended global location

The <head> section loads before any visible content. Placing the SeaText snippet there guarantees that the AI can analyse the visitor’s intent as soon as the browser starts rendering the page. If the code runs later (for example in the footer), the initial request may already have been processed without AI assistance, reducing conversion benefits.

How Tilda’s custom code injection works

Tilda stores custom code in a database linked to the site’s configuration. When you publish, the platform injects the stored snippets into the generated HTML of every page. The injection point is hard‑coded: the Header field is placed inside the opening <head> tag, while the Footer field appears just before the closing </body> tag.

This mechanism means you do not need to edit each page individually. The script is added once, and Tilda automatically includes it on new pages you create later.

Site‑wide Header placement vs single‑page T123 placement

For most users the Header option is the safest choice because it guarantees early execution and consistent coverage. Use a T123 block only when you need a script on a single landing page or when you want to test a variant without affecting the whole site.

Troubleshooting activation (40‑second visit, 5‑minute wait, domain restrictions)

• Visit duration: After publishing, open the live site in a new browser tab and stay on the page for at least 40 seconds. SeaText monitors the dwell time to confirm that the script is active and linked to your account.
• Five‑minute verification: The SeaText logo appears in the top‑right corner once the platform has validated the domain. This can take up to five minutes after the first successful visit.
• Domain restrictions: The script works only on fully qualified domains that have a SeaText account attached. Development URLs such as localhost or temporary subdomains are blocked for security reasons. Use a real staging domain if you need to test before going live.
• Cache issues: Clear your browser cache or use an incognito window after publishing. Cached pages may still contain the old HTML without the new script.
• Multiple accounts: If you manage several domains, each domain needs its own SeaText account. The script is tied to the account that generated the JavaScript snippet.

Likely follow‑up questions

• Can I place the script in the Footer instead?
  The Footer runs after the page content, which may delay AI activation. It is not recommended for site‑wide use.
• Do I need to edit the script for each language?
  No. The same snippet works across all languages; SeaText detects visitor language automatically.
• What if I change my domain?
  Create a new SeaText account for the new primary URL, generate a fresh script, and replace the old snippet in the Header field.
• Is there a limit to how many scripts I can add?
  Tilda allows multiple custom snippets, but each script should have a unique purpose to avoid conflicts.
• How do I remove the script?
  Delete the code from the Header field, save, and republish the site. The AI will become inert after the next page load.

What the Header field does

The Header field injects any code you place into the <head> section of every page on your site. This is the only place where a site‑wide JavaScript snippet can run before the page content loads.

Key facts

Step‑by‑step placement

1. Log in to your Tilda dashboard.
2. Click Site Settings in the left‑hand menu.
3. Select Custom Code then the Header tab.
4. Find the box labeled “Edit code inside HEAD tag”.
5. Paste the SeaText JavaScript exactly as provided in your SeaText account.
6. Press Save and then Publish the site.

Common mistake to avoid

Do not paste the script into a page‑level block or the Footer area. Doing so delays execution and can prevent the AI from detecting the visitor’s intent on the first request.

Limitations

The script works only on domains that have a valid SeaText account attached. Development URLs such as localhost are blocked for security reasons, and the AI stays inert until the site is visited for at least 40 seconds.

FAQ

• Why must the script be in the Header? Placing it in the head ensures the AI loads before any page content, allowing real‑time copy adaptation.
• Can I add the script to a single Tilda page only? Yes – add a T123 “Other” block on that page and paste the snippet in the block’s HTML editor, but the site‑wide Header is recommended for full coverage.
• What if the script doesn’t activate? Verify you saved the code, published the site, cleared cache, and waited at least five minutes for the SeaText logo to appear on the page.
• Do I need a separate SeaText account per domain? Each primary domain requires its own SeaText account; the script is tied to that account.