Seatext library

Do You Need a Separate Seatext AI Account for Each Website?

Yes. You need a separate Seatext AI account for each website. Each account links to a single primary URL. The script will not work across multiple domains from the same account. This rule applies...

Yes. If you want to run Seatext AI on more than one website, you must create a separate account for each one. Every Seatext AI account is tied to a single primary URL. The script will not work across multiple domains from the same account.

This rule applies whether the sites are completely different businesses, a staging environment and a production site, or any other combination of domains. The platform enforces a one-account-per-domain model for security, tracking, and billing reasons.

Why the one-account-per-domain rule exists

Seatext AI links each account to a specific domain during activation. When you install the JavaScript snippet, the system verifies that the traffic originates from the registered URL. This connection lets the platform attribute conversions, track variant performance, and apply the correct AI agents to the right site.

The API key embedded in the script is bound to the domain via hostname verification. The script checks the domain of the current page against the registered domain. If they don't match, the AI agents stay inert. This prevents someone from stealing your key and using it on another site.

This design also ensures accurate billing. You only pay for the traffic and features used on each domain. Each account has its own plan and usage limits. There is no way to share a single plan across multiple domains.

What counts as a separate domain

Any distinct primary URL requires its own account. This includes:

  • Different root domains (example.com vs. another-site.com)
  • Subdomains that function as separate sites (shop.example.com vs. blog.example.com)
  • Development, staging, and production environments (dev.example.com, staging.example.com, example.com)
  • Country-specific domains (example.co.uk, example.de, example.fr)

Localhost and dynamic development URLs are explicitly restricted for security reasons. You must use a valid, publicly resolvable domain for each account.

But what if a subdomain is just a section of the same site? For example, docs.example.com that is part of the main example.com site. The rule is: if the subdomain is the exact primary URL registered in the account, then it works. If you registered example.com, then docs.example.com will not work unless you create a separate account for docs.example.com. The only exception is when the subdomain is the same as the primary URL. For instance, if you register blog.example.com as your primary URL, then the script works on that exact subdomain. But you cannot use that same account on example.com or shop.example.com.

Decision criteria: When to create a new account

Here are practical scenarios to help you decide:

  • Different businesses: If you run two separate companies on different domains, you need two accounts. Each account has its own dashboard, agents, and billing.
  • Staging and production: Always create a separate account for your staging environment. This lets you test changes without affecting live data. The staging URL must be a valid public domain, not localhost.
  • Multiple language domains: If you use country-specific domains (example.fr, example.de), each needs its own account. But if you use language paths on the same domain (example.com/en/, example.com/de/), one account covers all of them.
  • Client sites for agencies: Each client domain gets its own account. You manage them separately. There is no multi-client dashboard.
  • Subdomains for different functionality: If you have a main site and a separate blog on a subdomain, treat them as separate accounts if they serve different purposes. But if they are the same site with different sections, you might be able to use one account if the subdomain is the registered primary URL.

When in doubt, create a new account. The activation process is quick. You can always create a free account for testing.

How to set up multiple sites correctly

  1. Create the first account at seatext.com using an email address you control.
  2. Install the provided JavaScript snippet on the first website.
  3. Visit the site several times and stay on a page for at least 40 seconds to trigger activation.
  4. Wait up to 10 minutes for the site name to appear next to the Seatext logo in your dashboard.
  5. Repeat steps 1–4 for each additional website, using a new account (and email) each time.

Each account gets its own API key, dashboard, and agent configuration. You manage them independently. The activation process is the same for every account. If the site name does not appear after 10 minutes, contact support. This could indicate an installation issue.

Managing multiple accounts in practice

Agencies and teams handling many client sites typically use a consistent naming convention for accounts (e.g., clientname-prod, clientname-staging) and a password manager to track credentials. There is no multi-site dashboard or master account that aggregates data across separate Seatext accounts.

If you need centralized reporting, you must export data from each account individually or use your own analytics layer (Google Analytics, Mixpanel, etc.) that sits above the Seatext layer.

Each account requires a unique email address at sign-up. You cannot use the same email for multiple accounts. Plan your email management accordingly. Some teams use plus addressing (e.g., seatext+client1@gmail.com) if their email provider supports it.

Key facts

RuleDetails
Account-to-domain ratioOne account per primary URL
API key scopeValid only for the domain registered to that account
Staging/productionSeparate accounts required for each environment
Localhost / dynamic dev URLsRestricted; not supported
Activation requirementVisit site, stay 40+ seconds, wait up to 10 minutes for dashboard confirmation
Multi-site dashboardNot available; each account is independent

Common misconceptions

"I can just copy the same script to another site." The script contains an API key bound to the original domain. It will not activate on a different domain.

"Subdomains share the root domain account." Only if the subdomain is the exact primary URL registered. A separate subdomain acting as a distinct site needs its own account.

"I can use one paid plan across multiple accounts." Billing is per account. Each account selects its own plan tier. There is no volume discount or multi-site bundle.

"I can merge accounts later." No account merging or domain transfer feature is documented. If you change primary domains, you create a new account.

When you might think you need multiple accounts but don't

If you have a single domain with multiple language paths (example.com/en/, example.com/de/) or multiple pages on the same domain, one account covers all of them. The Translation Agent handles up to 125 languages within that single account.

Similarly, if you run multiple campaigns or landing pages on the same domain, the Visitor Source Rewrite Agent and Google Ads Agent adapt content per visitor without requiring additional accounts.

Also, if you have a subdomain that is merely a different section of the same site (e.g., docs.example.com under the main example.com), you might be able to use one account if you register that subdomain as the primary URL. But then the main domain would not work. Plan carefully.

Limitations and exceptions

  • No wildcard or multi-domain API keys exist.
  • No account merging or domain transfer feature is documented; if you change primary domains, you create a new account.
  • Localhost and ephemeral preview URLs (e.g., Netlify deploy previews, Vercel preview deployments) will not activate reliably.
  • Each account requires a unique email address at sign-up.
  • Dynamic development domains (like those generated by cloud hosting) may not work because the domain changes frequently.

Terminology

  • Primary URL — The single domain or subdomain registered to a Seatext AI account during activation.
  • API key — The unique identifier embedded in the JavaScript snippet that authenticates the script to your account.
  • Activation — The process where Seatext verifies live traffic on the registered domain and links the site to the dashboard.
  • AI agents — Specialized modules (CRO Optimizer, Translation Agent, Google Ads Agent, etc.) you enable per account.

FAQ

Can I use one email for multiple Seatext accounts?

No. Each account requires a unique email address at registration.

What happens if I install the script on a second domain without a new account?

The script loads but the AI agents stay inert. The dashboard will not show the second domain as connected, and no optimization or translation occurs.

Do I pay separately for each account?

Yes. Each account chooses its own plan (free or paid). There is no volume discount or multi-site bundle mentioned in the public documentation.

Can I move an account from one domain to another?

The source material does not describe a domain transfer process. The standard path is to create a new account for the new domain.

How long does activation take for each new account?

Up to 10 minutes after you visit the site and stay on a page for 40+ seconds. If the site name does not appear after 10 minutes, contact support.

Does the free plan allow multiple accounts?

Yes. You can create as many free accounts as you have domains. Each free account includes the base agent set.

What if I'm an agency managing 50 client sites?

You create 50 separate accounts (one per client domain), each with its own email, API key, and dashboard. Use a password manager and consistent naming to stay organized.

Can I test a new domain without creating a paid account?

Yes. Create a free account for the test domain. The free plan includes the base agents. You can upgrade later if needed.

Will changing my domain's DNS or migrating to a new URL affect my account?

If you change the primary URL, the existing account will no longer work. You need to create a new account for the new domain. The old account remains active for the old domain until you stop using it.

Learn more

Visit the website for more information.