SeaText Multi-Site vs Separate Accounts: When to Choose Each Approach
SeaText does not offer a multi-site installation. Each account links to one primary URL. You must create a separate account for every domain, subdomain, or staging environment. This article explains why, how it works...
| Criterion | Multi-site installation (not available) | Separate accounts (actual option) |
|---|---|---|
| Account management | Would need single dashboard | One login per domain |
| Analytics isolation | Would share data across sites | Fully isolated per domain |
| Billing | Would need volume pricing | Per-account billing |
| Setup complexity | One script for all sites | Unique script per domain |
| Client ownership | Agency retains control | Client owns their account |
| Scalability | Centralized scaling | Manual per-site scaling |
Why SeaText Requires Separate Accounts Per Domain
SeaText ties each account to a single primary URL. The platform uses that URL to track traffic, attribute conversions, and secure the AI connection. According to the official installation guide, the JavaScript snippet contains an account-specific identifier that only activates when the domain matches the registered primary URL. If you paste the same script on a different domain, it will not connect. The dashboard will not show the second site. This design choice affects tracking accuracy, billing separation, and data ownership.
The restriction exists for three reasons. First, the AI associates reading telemetry and conversion signals with a specific domain. Mixing domains would corrupt the behavioral data that drives copy optimization. Second, billing is per account. Each account represents a distinct website with its own traffic volume and feature usage. Third, security policies block localhost and dynamic preview URLs because they cannot be reliably verified as belonging to the account holder.
How Account Separation Works in Practice
When you create a SeaText account, you provide a primary URL during signup. The system generates a unique JavaScript snippet. You paste that snippet into the header of your site, typically via a plugin like "Headers and Footers by WPBeginner" on WordPress. After saving, you must visit the live site and stay for at least 40 seconds. This visit activates the AI and links the domain to your account. Within 5 to 10 minutes, the site name appears in the top-left corner of the SeaText dashboard next to the logo. If it does not appear after 10 minutes, the documentation advises contacting support.
Each domain requires its own signup, its own snippet, and its own 40-second activation visit. You cannot reuse a snippet across domains. Subdomains like blog.example.com and shop.example.com count as separate primary URLs if they host distinct content. Each needs its own account. Staging environments on real domains (e.g., staging.example.com) also need separate accounts. Localhost and dynamic preview deployments (Netlify, Vercel preview URLs) are explicitly restricted and will not work reliably.
Readiness Checklist: When Separate Accounts Are Required
- You manage more than one live domain (e.g., example.com and shop.example.com)
- You run a staging or development site on a real domain (not localhost)
- You handle multiple client websites as an agency
- You operate separate brands with distinct domains
- You need isolated analytics, billing, or user access per site
- You use subdomains as separate websites with different content
- You test SeaText on a temporary domain before production launch
If any of these apply, you must create a new SeaText account for each domain. There is no workaround within the current platform architecture.
Agency and Multi-Brand Workflows
Agencies cannot manage multiple client sites from a single master account. Each client needs their own SeaText account tied to their domain and email. The agency can assist with installation by guiding the client through the signup and script placement, but the account lives under the client's credentials. This keeps data ownership clear: the client owns their account, their reading telemetry, their conversion data, and their billing. The agency does not get a unified dashboard across clients. If you need to review performance across accounts, you must log into each one separately or ask clients to share dashboard access.
This model differs from WordPress Multisite, where a single installation manages many sites. SeaText is not a CMS. It is a JavaScript layer that sits on top of any website. The WordPress multisite vs separate installations debate does not apply. Even on a WordPress Multisite network with domain mapping, each mapped domain needs its own SeaText account.
Limitations and Exceptions
- No multi-site dashboard or unified reporting across accounts
- No shared billing or volume discounts mentioned in public documentation
- Subdomains with distinct primary URLs count as separate domains
- Localhost and dynamic preview URLs (Netlify, Vercel previews) are not supported
- Domain transfers are not documented; assume a new account is needed for a new domain
- No centralized user management across accounts
If you manage 10 or more sites, the documentation suggests contacting sales to ask about volume pricing. No public information exists on enterprise multi-account arrangements.
Decision Framework: Choose Separate Accounts When
- You have two or more distinct domains — always required
- You need isolated conversion data per site — always required
- You want the client to own their account and data — agency work
- You're testing on a real staging domain — treat it like a separate site
- You run separate brands that must not share analytics
- You need separate billing for each website
There is no scenario where a single SeaText account serves multiple domains. The platform does not support it. Plan for one account per primary URL from the start.
Practical Scenarios
Scenario 1: Ecommerce brand with main site and separate shop subdomain
A brand runs example.com for content and shop.example.com for transactions. These are two primary URLs. They need two SeaText accounts. The content site gets its own copy testing and reading analysis. The shop site gets its own product copy optimization and conversion tracking. Data stays isolated. Billing is separate.
Scenario 2: Agency managing five client websites
The agency creates five SeaText accounts, one per client domain. Each client signs up with their own email. The agency helps paste the snippet. The agency does not see a combined dashboard. If the agency wants to compare performance, they must request view access from each client or schedule separate reviews.
Scenario 3: Development team with staging and production
The team uses staging.example.com for QA and example.com for production. Both are real domains. They need two accounts. The staging account tests copy variants without affecting production data. The production account runs live optimization. Localhost development cannot use SeaText at all.
Scenario 4: Company migrating from olddomain.com to newdomain.com
The documentation does not cover domain transfers. The safe approach: create a new account for newdomain.com. Run both in parallel during migration. Deactivate the old account after traffic fully shifts. Contact support if you need to preserve historical data.
Key Facts From SeaText Documentation
| Aspect | Rule | Source |
|---|---|---|
| Account-to-domain ratio | One account per primary URL | S1 |
| Multiple websites | Create one account for each website | S1 |
| Development domains | Localhost restricted; dynamic dev domains may not work | S1 |
| Activation requirement | Visit site, stay 40+ seconds to link account | S1 |
| Dashboard confirmation | Site name appears in top-left within 5-10 minutes | S1 |
FAQ
Can I use one SeaText account for a main domain and its subdomains?
No. Each primary URL requires its own account. If blog.example.com and shop.example.com are separate sites with separate content, they need separate accounts.
What about a staging site on staging.example.com?
That's a separate domain. Create a separate SeaText account for it. Localhost and dynamic preview URLs won't work reliably.
Can I transfer a SeaText account to a different domain later?
The documentation doesn't address domain transfers. Since each account is linked to a single primary URL, assume you'd need a new account for a new domain. Contact support for edge cases.
Does SeaText offer volume pricing for multiple accounts?
Not mentioned in the public documentation. Check with sales if you're managing 10+ sites.
Can I install SeaText on a WordPress Multisite network?
You can install the script on each subsite, but each subsite with its own domain mapping needs its own SeaText account. The WordPress Multisite setup doesn't change SeaText's one-account-per-domain rule.
What happens if I paste the same script on two domains?
Only the domain matching the account's registered primary URL will connect and show in the dashboard. The other domain won't activate.
Why doesn't SeaText support multi-site like WordPress?
SeaText is a JavaScript analytics and optimization layer, not a content management system. Its AI ties reading behavior and conversion signals to a specific domain for accuracy. Mixing domains would break the attribution model that powers copy testing, keyword matching, and bot detection.
Can I use the same billing method for multiple accounts?
Each account bills separately. The platform does not offer consolidated invoicing in the public documentation. You would manage payment methods per account or ask sales about enterprise arrangements.
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.
Learn more
Visit the website for more information.