How to Add Multiple Websites to SeaText AI: Step-by-Step Process
SeaText AI requires a separate account for each website you want to manage. For every domain, you create a new account, install the JavaScript snippet, verify ownership by visiting the site for at least...
SeaText AI ties each account to a single primary URL. If you need the platform on several websites — for example, a production store, a staging environment, and a separate marketing microsite — you must create one account per domain. The workflow is identical for every site: register, paste the provided JavaScript code into the site's <head>, browse the live site for at least 40 seconds to trigger activation, then confirm the connection in the SeaText dashboard.
Why Separate Accounts Are Required
SeaText AI associates all AI agents, variant history, translation memories, and conversion data with the primary URL registered to an account. The platform uses that URL to attribute traffic, match paid-click keywords, and build the evidence files used for ad-refund claims. Mixing two domains under one account would break attribution, corrupt A/B test results, and prevent the bot-protection agent from issuing clean refund reports. The documentation states this constraint explicitly: "Each SEATEXT AI account is linked to a single primary URL."
Prerequisites Before You Start
- A valid, publicly resolvable domain for each website (no
localhost, no dynamic preview URLs). - Access to edit the
<head>section of every page on each site, or a tag manager / plugin that can inject JavaScript site-wide. - An email address you can use for each new SeaText account (the system sends activation and billing emails per account).
- Five to ten minutes of uninterrupted time per site to complete the verification wait period.
Step-by-Step Process for Each Website
- Create a new SeaText account. Go to the registration page and sign up with a unique email. The account creation flow will immediately show you the JavaScript snippet assigned to that account.
- Copy the JavaScript code. The snippet is unique to the account and contains the account identifier. Do not reuse a snippet from another account.
- Install the snippet on every page of the target domain. Paste it into the
<head>tag, or use your CMS / tag manager to deploy it site-wide. If you host on WP Engine, install the dedicated WP Engine plugin that allows custom JavaScript injection. - Visit the live site. Open the homepage (or any page with the snippet) in a browser. Stay on the page for at least 40 seconds. Refresh once or twice. This activity signals the SeaText servers that the domain is live and owned by you.
- Wait for dashboard confirmation. Return to the SeaText dashboard for this account. Within five minutes — up to ten in rare cases — the site name should appear next to the SeaText logo at the top of the page. That label means the domain is connected and ready for agent activation.
- Activate the agents you need. Open the Main AI Hub, choose Configuration, and enable the agents relevant to this site (CRO Optimizer, Google Ads Landing Page Agent, Translation Agent, etc.).
- Repeat steps 1–6 for every additional domain. Each domain gets its own account, its own snippet, its own dashboard, and its own billing.
Verification and Activation Details
The 40-second visit is not a suggestion — it is the mechanism SeaText uses to bind the live traffic to the account. Without it, the dashboard will not show the site name, and the AI agents will remain inert. The documentation warns: "If you do not see it at the top of the page after 10 minutes, please contact our support team immediately. This could indicate an issue during the installation on your platform, and you may need our assistance."
After the site name appears, you can immediately start configuring agents. The first automatic translations and copy variants are generated once the agents are turned on. You can then review or edit them under Variants Edit in the left panel.
Common Limitations and Restrictions
- No localhost or staging subdomains that resolve to non-public IPs. The system blocks development URLs for security reasons.
- Dynamic preview URLs (e.g., Netlify deploy previews, Vercel preview deployments) often fail. SeaText may be unable to reliably associate traffic with your account on such domains.
- One snippet per account. You cannot move a snippet between accounts or reuse it across domains.
- Separate billing per account. Each account carries its own subscription; there is no multi-site discount mentioned in the current documentation.
- No cross-account reporting. Conversion data, bot-refund evidence, and translation memories stay siloed per account.
Key Facts
| Item | Detail |
|---|---|
| Account-to-domain ratio | 1:1 — each SeaText account supports exactly one primary URL |
| Installation method | JavaScript snippet in <head> (or WP Engine plugin) |
| Activation trigger | Visit live site, stay ≥ 40 seconds, refresh once or twice |
| Dashboard confirmation | Site name appears next to SeaText logo within 5–10 minutes |
| Unsupported environments | localhost, dynamic preview URLs, any non-public domain |
| Post-activation step | Enable desired agents in Main AI Hub → Configuration |
Terminology
- Primary URL — the single domain permanently linked to a SeaText account during registration.
- JavaScript snippet — the unique code block that loads SeaText's autonomous agents onto your pages.
- Activation — the moment SeaText servers detect live traffic from the primary URL and bind it to the account.
- AI Hub — the dashboard section where you toggle individual agents (CRO, translation, bot protection, etc.) on or off.
- Variants Edit — the interface for reviewing, creating, or manually adjusting the automatic translations and copy variants SeaText generates.
Frequently Asked Questions
Can I manage two subdomains (e.g., shop.example.com and blog.example.com) under one account?
No. The documentation treats each distinct domain as requiring its own account. Subdomains on different root domains count as separate websites.
What if I accidentally install the wrong snippet on a site?
The dashboard for that account will never show the site name. You must remove the incorrect snippet, install the correct one, and repeat the 40-second visit.
Is there a bulk-import or API method to create many accounts at once?
Not documented in the current integration guide. Each account is created manually through the registration flow.
Do I need a separate email for every account?
Yes. The system sends activation, billing, and support emails per account. Using the same email for multiple accounts is not supported.
Can I transfer an existing account's data to a new domain?
No. Variant history, translation memories, and bot-refund evidence are bound to the original primary URL and cannot be migrated.
What happens if my staging domain later becomes the production domain?
Create the account on the final production domain from the start. Staging domains that are dynamic or non-public will not activate reliably.
Where do I get the JavaScript snippet for a new account?
Immediately after registration, the snippet is displayed in the account's integration section. You can also find it later under the integration settings in the dashboard.
Quick Reference Checklist
- [ ] Register new account with unique email
- [ ] Copy the account-specific JavaScript snippet
- [ ] Deploy snippet site-wide via
<head>or tag manager - [ ] Visit live site, stay 40+ seconds, refresh
- [ ] Confirm site name appears in dashboard (5–10 min)
- [ ] Activate needed agents in AI Hub → Configuration
- [ ] Review auto-generated variants under Variants Edit
- [ ] Repeat for each additional domain
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.