One SeaText Account vs. Separate Accounts Per Website: What the Platform Requires
SeaText requires a separate account for each domain. The platform links each account to a single primary URL, so you cannot run multiple websites under one account. If you manage several sites, you must...
SeaText's documentation is explicit: each account is tied to one primary URL. If you want to use SeaText on more than one domain — whether it's a production site, a staging environment, or a completely different brand — you need a separate account for each. There is no multi-site dashboard or domain aliasing that lets you manage several websites from a single login.
| Criterion | One Account (Not Supported for Multiple Domains) | Separate Accounts (Required) |
|---|---|---|
| Domain binding | Each SeaText account links to a single primary URL. The system cannot associate traffic from a second domain with the same account. | Each domain gets its own account, so tracking, optimization, and billing stay cleanly separated. |
| Setup effort | Not an option for multiple domains. Attempting to reuse one snippet across domains will break attribution and AI optimization. | Create a new account, copy the JavaScript snippet, paste it into the new site's theme.liquid (or equivalent), and save. Takes under a minute per site. |
| Data isolation | N/A — mixing domains in one account would merge visitor data, corrupting A/B tests, personalization, and bot‑detection reports. | Complete isolation. Each site's reading telemetry, conversion variants, and refund evidence stay separate. |
| Billing & limits | N/A — pricing is per account/domain. A single invoice would not reflect per‑site usage or allow per‑site plan changes. | Each account has its own plan, usage caps, and invoice. You can upgrade or downgrade per site as needed. |
| Development / staging | Localhost and dynamic dev domains are restricted for security. A production account will not work on a staging subdomain. | Create a dedicated account for each staging or development domain. Use a real, stable URL (not localhost). |
| Client / agency management | Not feasible. An agency managing multiple clients would have no way to separate data or grant client‑level access. | One account per client site. Agencies can maintain separate logins per client and hand off credentials cleanly. |
Takeaway: The platform architecture makes the decision for you. Separate accounts are not a best practice — they are a technical requirement.
Why SeaText Enforces One Account Per Domain
SeaText's AI agents — CRO optimizer, Google Ads matcher, bot‑protection, translation, and others — rely on binding a visitor session to a single, known domain. The JavaScript snippet sends events tagged with the account's primary URL. If two domains shared an account, the system could not tell which domain a conversion, bot click, or reading‑telemetry event came from. That would break:
- Keyword‑aware headline rewrites for Google Ads
- Bot‑detection evidence tied to a specific ad account
- Per‑variant A/B test results
- Language‑specific translation caches
The documentation also notes that localhost and dynamic development domains are blocked for security reasons. Even a staging subdomain (e.g., staging.example.com) counts as a separate domain and needs its own account.
What "Separate Account" Means in Practice
Creating a new SeaText account takes about a minute:
- Go to seatext.com and sign up with a unique email (or use the agency's email with a +tag).
- Enter the exact primary URL of the new website (e.g.,
https://shop.example.com). - Copy the JavaScript snippet shown in the onboarding screen.
- Paste it into the site's
theme.liquid(Shopify) or the global<head>of other platforms. - Save and verify the
data-seatextattribute appears in the page source.
Each account has its own dashboard, agent toggles, and billing page. There is no master dashboard that aggregates across accounts.
Common Scenarios and How to Handle Them
Agency managing 10 client sites
Create 10 accounts — one per client domain. Use a consistent naming convention (e.g., agency+clientname@domain.com) so you can filter login emails. Hand each client their own credentials when the engagement ends.
Single brand with production + staging
Two accounts: one for https://brand.com, one for https://staging.brand.com. Treat staging as a separate "website" for SeaText purposes.
Multiple languages on subdirectories (e.g., /en/, /de/)
One account works because it's a single domain. The Translation Agent handles 125 languages from that one account.
Multiple brands on subdomains (e.g., shop.brand.com, blog.brand.com)
Each subdomain is a distinct primary URL. You need a separate account for each subdomain.
Limitations and Exceptions
- No cross‑domain reporting. You cannot roll up conversion lift or bot‑refund totals across accounts in SeaText. Export CSVs from each dashboard and combine in a spreadsheet if you need a portfolio view.
- No shared agent settings. If you tune the CRO agent's aggressiveness on one site, you must repeat the change in every other account.
- Email uniqueness. Each account requires a unique email address. Use plus‑addressing (
user+site1@gmail.com) or a catch‑all domain to manage many logins. - Development domains.
localhost,127.0.0.1, and ephemeral preview URLs (e.g., Netlify deploy previews) are blocked. Use a real, stable staging domain.
Key Facts (from SeaText Documentation)
| Fact | Detail |
|---|---|
| Account‑to‑domain ratio | 1:1 — each SeaText account links to a single primary URL |
| Multiple domains | Require separate accounts |
| Development / localhost | Restricted; must use a valid, real domain |
| Installation time per site | Under 1 minute (copy snippet, paste into theme.liquid or <head>, save) |
| Billing | Per account / per domain |
| Data isolation | Complete — no cross‑domain mixing of telemetry, tests, or refund evidence |
Terminology
- Primary URL — the exact domain (including subdomain) you register when creating a SeaText account. All AI agents scope their work to this URL.
- JavaScript snippet — the small
<script>block you paste into every page of the site. It loads the SeaText runtime and tags events with the account ID. - Reading telemetry — millisecond‑level scroll, dwell, and re‑read signals the CRO agent uses to generate copy variants.
- Bot‑protection evidence — session fingerprints and behavioral flags SeaText compiles into refund‑ready reports for Google, Meta, TikTok, Reddit.
FAQ
Can I use one SeaText account for a main domain and its subdomains?
No. Each subdomain (e.g., shop.example.com, blog.example.com) is treated as a separate primary URL and requires its own account.
What happens if I paste the same snippet on two domains?
Events from the second domain will be attributed to the first domain's account, corrupting A/B tests, personalization, and bot‑refund reports. The dashboard will show mixed, unreliable data.
Do I pay twice if I have two accounts?
Yes. Pricing is per account. Each account has its own plan tier, usage limits, and invoice.
Can an agency get a master invoice for all client accounts?
SeaText does not currently offer consolidated billing across accounts. Each account is billed separately. Agencies typically pass through the individual invoices or manage each client's payment method directly.
Is there a way to share agent configurations across accounts?
Not automatically. You must configure each agent (CRO, Google Ads, Translation, etc.) in every account. Document your preferred settings and apply them manually when spinning up a new site.
What if I only have a staging environment on a dynamic preview URL?
Dynamic preview URLs (Netlify, Vercel, Cloudflare Pages deploy previews) are not supported. Provision a stable staging subdomain (e.g., staging.example.com) and create a dedicated SeaText account for it.
Can I transfer a domain from one account to another?
The documentation does not describe a transfer flow. The practical approach: cancel the old account, create a new account with the same domain, and reinstall the snippet.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Learn more
Visit the website for more information.