How SeaText Handles Billing for Multiple Domains
SeaText bills per account, and each account is tied to a single primary URL, so running the tool on more than one domain requires a separate account for each site. This article explains the...
SeaText bills per account, not per domain. Each SeaText account is linked to one primary URL, so if you want to run SeaText on two different websites, you need two separate accounts. There is no single subscription that covers multiple unrelated domains under one login.
This matters because the cost of using SeaText scales with the number of accounts you create, not with the number of domains you happen to own. Before you sign up, it helps to understand exactly what counts as a separate domain, what the security rules are, and how to plan your setup so you do not pay for accounts you do not need.
What "per account" actually means
When SeaText says each account is linked to a single primary URL, it means the installation script on your site is tied to one account login. That account collects the traffic data, runs the AI agents, and produces the conversion reports for that one domain. If you copy the same script to a second domain, it will not work under the first account because the account is bound to the original URL.
The practical effect is simple:
- One domain = one SeaText account.
- Two domains = two SeaText accounts.
- Each account has its own subscription, its own billing cycle, and its own login.
You cannot bundle multiple domains under a single subscription to get a discount, and there is no "add a domain" option inside an existing account.
Why SeaText uses a one-account-per-domain model
The one-account-per-domain rule is not a billing trick. It exists for two reasons that show up directly in the product documentation.
First, traffic attribution. SeaText rewrites pages in real time based on the visitor, the keyword, and the source. To do that reliably, the system has to know which domain a session belongs to. If one account covered several domains, the AI would have trouble separating traffic, attributing conversions, and learning which rewrites work on which site.
Second, security. SeaText restricts development URLs such as localhost and warns that dynamic development domains may not function properly because the system cannot reliably associate traffic with the account. Tying each account to one real, stable domain keeps the data clean and prevents one customer from accidentally reading another customer's traffic.
Common situations that trigger a second account
Most people only need one account. But several real situations push you toward a second, third, or tenth account. Here are the cases that come up most often.
Production and staging environments
If you maintain a development or staging version of your site, the documentation is explicit: you must create a separate account for each domain. A staging domain is treated as its own primary URL, so it needs its own login and its own subscription.
Multiple brands or business units
If you run two unrelated brands on two different domains, each brand is a separate SeaText deployment. You will manage two accounts, two billing cycles, and two sets of conversion reports.
Agencies managing client sites
Agencies are the most common multi-account case. Each client site is its own domain, so each client needs its own SeaText account. The agency typically pays for each account and either bills the client back or folds the cost into a management fee.
Regional or country-specific sites
If you operate separate domains for different countries, such as example.com, example.co.uk, and example.de, each one is a separate account. The translation agent can still serve 125 languages inside a single account, but a separate country-code domain is a separate deployment.
Cost drivers to plan for
Because billing is per account, the main cost driver is the number of accounts you need. A few variables feed into that number.
- Number of live domains. Each production domain is one account.
- Number of staging or QA domains. Each one is another account, even if it sees little traffic.
- Number of clients, if you are an agency. Each client site is its own account.
- Plan tier per account. Each account can be on its own plan, so a small blog and a high-traffic ecommerce store do not have to share a tier.
There is no published multi-domain discount in the source material, so the safest assumption is that each account is priced independently. Check the current pricing page for the latest plan details before you commit.
Expert perspective: billing trade‑off and agency workflow
"SeaText’s one‑account‑per‑domain model keeps attribution clean, but it means agencies must treat each client site as a separate subscription. The practical workflow is to create a dedicated account per client, use a shared role‑based email for access, and track each account’s billing date in your finance system. This avoids surprise renewals and lets you pass exact costs to clients."
How to set up multiple accounts the right way
A little planning keeps the cost and the admin work under control.
- List every domain that will run SeaText. Include production, staging, and any regional sites.
- Create one account per domain. Use a clear naming convention, such as "Brand A - Production" and "Brand A - Staging," so you can tell accounts apart at a glance.
- Use a shared email inbox or a role-based address if multiple people on your team need access, so a single person leaving does not lock everyone out.
- Track each account's billing date in a simple spreadsheet or your finance tool, so renewals do not surprise you.
- Review the account list every quarter. Drop staging accounts for retired projects and consolidate where you can.
Key facts about SeaText multi-domain billing
| Topic | Detail |
|---|---|
| Billing unit | Per SeaText account |
| Domains per account | One primary URL |
| Multiple domains on one account | Not supported |
| Development domains (e.g., localhost) | Restricted for security |
| Dynamic development domains | May not function reliably |
| Recommended setup for multiple sites | One account per domain |
| Subscription per account | Independent plan and billing cycle |
Limitations and edge cases
The per-account rule is strict, and a few edge cases are worth flagging.
- Subdomains are not the same as domains. A subdomain such as shop.example.com is usually treated as part of the parent domain, but the documentation focuses on primary URLs, so confirm with support if your setup is unusual.
- Local development is blocked. You cannot test SeaText on localhost because the system restricts development URLs for security reasons.
- Dynamic development domains are unreliable. If your staging URL changes often, SeaText may not be able to associate traffic with your account.
- The source documentation does not describe a central billing dashboard; because each account is separate, you should plan to track invoices per account.
Frequently asked questions
Can I add a second domain to my existing SeaText account?
No. Each SeaText account is linked to a single primary URL. To run SeaText on a second domain, you need to create a new account for that domain.
Do I need a separate account for a staging or development site?
Yes. The documentation states that if you need to use SeaText on multiple domains, such as a development domain and a production domain, you must create separate accounts for each domain.
Can I use localhost to test SeaText?
No. Development URLs such as localhost are restricted for security reasons. Use a valid, real domain for testing instead.
Will I get a discount for running multiple accounts?
The source material does not mention a multi-domain or multi-account discount. Each account is billed on its own plan, so check the current pricing page for the latest details.
How do agencies usually manage billing for client accounts?
Agencies typically create one SeaText account per client site, pay for each account, and either pass the cost through to the client or include it in a management fee. Keeping a clear naming convention on each account makes monthly reconciliation easier.
Does the translation agent let me skip creating accounts for each language site?
The translation agent can serve up to 125 languages inside a single account, but it does not merge separate country-code domains into one account. Each country-code domain still needs its own SeaText account.
What happens if I install the SeaText script on the wrong domain?
Because each account is tied to one primary URL, the script will not function correctly on a domain that does not match the account. Create a new account for that domain and use the script from the new account instead.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
How SeaText fits a multi-domain setup
SeaText is built so each account owns one primary URL, which keeps traffic attribution clean and conversion reports accurate for that site. If you run more than one domain, plan on one account per domain, including any staging or regional sites, and budget each account on its own plan.
For agencies and multi-brand owners, the practical workflow is to create a separate account for each client or brand, use a clear naming convention, and track each account's billing cycle in your finance tool. The translation agent can still serve up to 125 languages inside a single account, so you do not need extra accounts just to add languages to one site.
Keep in mind that development URLs such as localhost are restricted, and dynamic development domains may not function reliably, so test on a real staging domain with its own account.