SeaText Multi-Domain Restrictions: Account Rules, Development Limits, and Setup Process
Each SeaText account links to one primary domain. To use SeaText on multiple domains — including separate development and production environments — you must create a separate account for each domain. Localhost and dynamic...
SeaText ties each account to a single primary URL. If you need the service on more than one domain — for example, a staging site and a live site, or two different brand websites — you must open a separate SeaText account for every domain. Development addresses such as localhost or dynamically generated preview URLs are blocked for security reasons and because the system cannot reliably associate traffic with your account [S1].
Why SeaText Requires One Account Per Domain
SeaText uses the domain as the anchor for billing, configuration, and traffic attribution. The JavaScript snippet you paste into a site sends page-view and conversion data back to the account that owns the domain. If two domains shared one account, the platform could not separate their analytics, variant tests, or translation memories. The restriction also prevents a single subscription from being stretched across unrelated properties, which keeps pricing predictable for both sides [S1].
Each SeaText account is linked to a single primary URL. This design choice means that all agents — CRO Optimizer, Translation Agent, Bot Protection, and others — run under that account and only see traffic from the linked domain. Changing the primary URL later is not supported; you would create a new account instead [S1].
How the Account–Domain Link Works in Practice
When you sign up, you enter the primary URL (for example, https://shop.example.com). The dashboard then shows that domain next to the SeaText logo once the snippet is installed and the site receives a few visits. All agents run under that account and only see traffic from the linked domain. The connection is verified when the domain name appears next to the SeaText logo at the top of the dashboard page [S1].
The installation process is secure, and the AI remains inert until activated, ensuring the integrity of your website's content. Before you can install the script, you need a SeaText AI account. The JavaScript snippet must be pasted into the appropriate header field of your CMS. For Magento, this is Content > Design > Configuration > HTML Head > Scripts and Style Sheets [S1].
Development, Staging, and Preview Environment Restrictions
Localhost addresses (http://localhost, http://127.0.0.1) are explicitly restricted for security reasons. Dynamic preview URLs generated by platforms like Vercel, Netlify, or Shopify theme previews often change on every deploy. SeaText cannot reliably map those shifting hosts to a single account, so they may not function properly [S1].
The recommended workflow is to use a real, stable domain (or subdomain) for each environment — for example, staging.example.com and example.com — and provision a separate SeaText account for each. This ensures reliable traffic association and activation. Dynamic development domains may not function properly because SeaText AI might be unable to reliably associate traffic with your account [S1].
Managing Multiple Websites or Brands
Agencies and companies that run several distinct sites should treat each site as its own SeaText account. This keeps variant libraries, translation glossaries, and conversion reports isolated. The dashboard does not currently offer a multi-site view; you log in to each account separately. If you need centralized billing, contact SeaText sales — they can arrange a master invoice while keeping the technical accounts separate [S1].
To use SeaText AI on several websites, create one account for each website. This applies whether the sites are different brands, different regional storefronts, or separate client projects. Each account maintains its own configuration, AI agents, and reporting [S1].
Step-by-Step: Setting Up SeaText on a Second Domain
- Create a new SeaText account using the second domain's full URL (including
https://). - Copy the JavaScript snippet shown in the new account's integration page.
- Paste the snippet into the
<head>of the second site. For Magento: Content > Design > Configuration > HTML Head > Scripts and Style Sheets. Other CMSs have equivalent fields [S1]. - Save and publish the site.
- Visit the second site several times and stay on a page for at least 40 seconds. This activates the AI and links the domain to the new account [S1].
- Wait at least five minutes until you see your website name displayed next to the SeaText logo at the top of the dashboard page. This indicates that your website is connected and ready to proceed. If you do not see it after 10 minutes, contact support immediately [S1].
Activation Requirements and Troubleshooting
Activation requires real user visits. You must visit or refresh your website several times and stay on your page for at least 40 seconds. This will activate the AI and link it to your account. The system needs this dwell time to verify the domain connection and begin processing traffic [S1].
After the qualified visit, wait at least five minutes. The domain name should appear next to the SeaText logo in the dashboard. If it does not appear after 10 minutes, this could indicate an issue during the installation on your platform, and you may need assistance from the support team [S1].
Common issues include: snippet placed in the wrong location, caching preventing the new script from loading, or the domain not matching the one registered in the account. Verify the snippet is in the HTML Head section and that the domain matches exactly, including protocol (https://) and subdomain [S1].
Key Facts at a Glance
| Rule | Detail |
|---|---|
| Accounts per domain | One account per primary URL [S1] |
| Development domains | Localhost and dynamic preview URLs restricted [S1] |
| Stable staging domain | Use a real subdomain (e.g., staging.example.com) with its own account [S1] |
| Multi-site management | Separate logins; no unified dashboard [S1] |
| Activation requirement | Visit site, stay 40+ seconds; domain appears in dashboard within 10 minutes [S1] |
| Changing primary URL | Not supported — create a new account instead [S1] |
Limitations and When This Guidance Does Not Apply
- Enterprise contracts may include custom multi-domain terms; check your agreement or ask your account manager.
- If you migrate a site to a new domain permanently, you must create a new account — the old account stays tied to the old URL.
- Subdirectories (e.g.,
example.com/fr/) count as the same domain; one account covers them all. - Wildcard subdomains (
*.example.com) are not officially supported; each subdomain should have its own account for reliable tracking.
Frequently Asked Follow-Up Questions
Can I use one SeaText account for a main site and its staging subdomain?
No. The staging subdomain (e.g., staging.example.com) is a different host. You need a separate account for it [S1].
What happens if I paste the same snippet on two domains?
Data from both domains will flow into the single account, mixing analytics, variant results, and translation memories. This breaks reporting and is not supported [S1].
Do I pay twice if I have two accounts?
Yes, each account is billed independently. Enterprise customers can negotiate a combined invoice [S1].
Can I move an account from one domain to another?
No. The primary URL is fixed at account creation. Create a new account for the new domain [S1].
Are there any exceptions for local development?
Localhost and dynamic preview URLs are blocked. Use a real domain or subdomain pointed to your local machine via /etc/hosts or a tunneling service that provides a stable hostname [S1].
How long does activation take?
Usually under five minutes after the first qualified visit (40+ seconds on page). Allow up to ten minutes before contacting support [S1].
Where do I find the snippet for a new account?
Log in to the new account, go to the integration page for your platform (Magento, WordPress, Shopify, etc.), and copy the JavaScript code shown there [S1].
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.