Can I Use a Single SeaText API Key for Multiple Tilda Domains?

The short answer is no. A SeaText API key belongs to one account. Each SeaText account is linked to one primary URL. You cannot use that key on another Tilda domain.

This is not a limit you can bypass. The key is tied to the domain you enter when you create the account. To run SeaText on multiple Tilda sites, you need one account per site and the correct key on each site.

This article explains the authentication model, the common mistake of reusing keys, installation steps, activation behavior, and how to manage many SeaText accounts cleanly.

How SeaText Authentication Works

SeaText identifies websites with API keys. When you create an account, you provide a primary URL. SeaText then gives you a JavaScript snippet with a unique key for that account.

Why is one key required for each domain? Because the key is the link between visitor traffic and your dashboard. If two domains used the same key, SeaText could not tell which domain created the data.

Data isolation is another reason. A company with several sites needs separate reports, agent settings, and bot evidence. Separate keys keep those records clean.

Security also matters. A unique key limits the damage if a key is exposed. One leaked key affects one domain, not your entire portfolio.

The validation process is simple. The JavaScript snippet sends the key with page requests. SeaText compares the requesting domain with the primary URL stored on the account. If they match, the site can connect. If they do not match, the request is ignored.

You do not need to run a server or configure DNS for this check. The snippet handles the request, and SeaText does the comparison automatically.

Think of the key as a door key. A key made for one front door will not open another door. The same idea applies here.

The Common Mistake: Reusing a Key Across Domains

The most common mistake is copying one SeaText snippet to multiple Tilda sites. The code loads on every page, so it looks like SeaText is installed. But the key still belongs to the original primary URL.

Here is a typical scenario. Your primary URL is www.example.com. You copy that snippet to www.second-example.com. When someone visits the second site, the snippet sends the key. SeaText checks the domain, sees a mismatch, and does not activate the AI.

Another common scenario involves staging. A developer takes the production key and puts it on a staging domain. The staging site never activates because its URL does not match the production primary URL.

What does that look like? The dashboard still shows only the original domain. The second site appears to have no data. Refresh, cache clearing, and repeated visits will not fix it.

The fix is always the same: create a new account for each new domain. Install the new account's snippet on that domain only.

Setting Up SeaText on Multiple Tilda Sites

Each Tilda domain needs the same setup process. Follow these steps for every domain:

1. Go to the SeaText integration page and create an account for the domain.
2. Enter the domain as the primary URL when you create the account.
3. Copy the JavaScript snippet from the SeaText page.
4. Open the Tilda dashboard for that site.
5. Go to Site Settings.
6. Click More, then HTML code for the head section, then Edit code.
7. Paste the snippet into the field labeled Edit code inside HEAD tag.
8. Save and publish the site.
9. Visit or refresh the site several times.
10. Stay on the page for at least 40 seconds.
11. Wait at least five minutes.
12. Check the integration page for your website name next to the SeaText logo.

If you only need the code on one page, use the T123 block method. Add the T123 block to the page, open Content, paste the snippet into the HTML editor, save, and publish.

Managing multiple Tilda accounts efficiently starts with a simple system. Do not rely on memory.

• Use an account name that clearly matches the domain, such as example-com.
• Use an email address you control for each account, or use aliases.
• Store each key in a password manager with the domain name.
• Keep a spreadsheet with domain, account email, key, install date, and status.
• Verify each domain in the SeaText dashboard before you start the next one.
• Use a separate browser profile for each account so you do not copy the wrong key.
• Mark the domain as connected after the website name appears next to the logo.

This routine takes a few minutes. It saves hours of debugging if something goes wrong later.

Key Facts at a Glance

Use this table as a quick checklist before you install SeaText on a new Tilda domain.

Limitations and Exceptions

SeaText does not support one key on multiple primary URLs. There is no shared-key mode or team project that changes that rule.

Staging and production sites are separate. If you run a development domain and a production domain, create one SeaText account for each.

Development URLs are restricted for security. localhost is blocked. Dynamic development domains, such as temporary URLs from cloud tools, may not work because SeaText cannot reliably connect their traffic to your account.

Use a real, valid domain for testing. This avoids a confusing setup where the code is present but no data appears.

A permanent domain change also creates a limitation. Your account was created with one primary URL, so the old key is unlikely to work on the new domain. Create a new account for the new URL. If you have a complex migration, check with the vendor.

Subdomains are separate primary URLs. For example, blog.example.com and www.example.com are different domains. Each one needs its own SeaText account.

Wildcard domain support is not mentioned in the source documentation. Treat each domain as an individual account.

Frequently Asked Questions

Can I use one SeaText account for two Tilda websites?

No. One account is linked to one primary URL. You need a separate account for each website.

What is a primary URL?

It is the domain you enter when you create the SeaText account. SeaText uses it to validate the API key.

Can I use the same account for a subdomain, like blog.mysite.com?

No. A subdomain is a different primary URL. Create a separate account for that subdomain.

What if I have a staging and a production domain?

Create one account for staging and another for production. Each account gets its own API key.

How does SeaText know the key is installed correctly?

After installation, visit or refresh the site and stay for at least 40 seconds. Wait five minutes. If your website name appears next to the SeaText logo, the key is working.

Can SeaText activate without visitor traffic?

No. The source instructions say you need to visit or refresh the site several times and stay on the page for at least 40 seconds. This triggers activation.

Is there a limit on the number of SeaText accounts I can create?

The source documentation does not mention a limit. You can create as many accounts as you need, one for each Tilda domain.

What if I accidentally reuse a key on another domain?

The second domain will not activate. Create a new account for that domain, install its unique key, and remove the old snippet.

Does SeaText support wildcard domains?

No. Each account is tied to a single primary URL.

Can I use localhost for testing?

No. localhost is restricted for security reasons.

Can I use a dynamic development domain for testing?

It may not work. SeaText might not be able to reliably associate traffic from dynamic development domains with your account. Use a real, valid domain instead.

How long does activation take after installation?

The source instructions say to wait at least five minutes. The website name should then appear next to the SeaText logo on the integration page.