Common Mistakes When Using SeaText AI on Multiple Domains
SeaText AI requires a separate account for each domain because every account links to one primary URL. The most frequent errors are trying to run multiple sites on one account, using localhost or dynamic...
SeaText AI ties each account to a single primary URL. If you manage more than one site — production, staging, a client project, or a microsite — you must create a distinct account for each one. The platform will not let you switch domains inside a dashboard, and it blocks localhost or dynamic development addresses for security reasons. The mistakes below show up repeatedly in support tickets and onboarding calls.
Why SeaText AI enforces one domain per account
The architecture isolates content analysis, variant testing, and conversion tracking per site. When an account connects to a primary URL, the AI crawls that domain, builds a sitemap, and starts generating variants scoped to its pages. Sharing an account across domains would mix traffic data, dilute A/B results, and break the keyword-to-landing-page matching that the Google Ads and Visitor Source agents rely on. The restriction is deliberate, not a missing feature.
Mistake 1: Trying to add multiple domains to one account
Users often look for an "Add domain" button inside the dashboard. There isn't one. The General Integration guide states: "Each SEATEXT AI account is linked to a single primary URL" and "To use SEATEXT AI on several websites, create one account for each website." Attempting to paste the same JavaScript snippet on two different domains under the same account leads to one of two outcomes: the second domain never shows as connected, or the first domain's data gets polluted by the second's traffic.
Fix: Create a new SeaText AI account for each domain. Use a distinct email or the same email with a new registration flow. Install the unique snippet that the new account provides on that domain only.
Mistake 2: Using localhost, staging subdomains, or dynamic preview URLs
The integration docs explicitly restrict development URLs such as localhost and warn that "dynamic development domains may not function properly, as SEATEXT AI might be unable to reliably associate traffic with your account." Teams that point the snippet at a Netlify preview link, a Vercel deployment URL, or a .local hostname see the AI stay inert or the domain never verify.
Fix: Use a real, publicly resolvable domain for every environment. For staging, provision a fixed subdomain like staging.example.com with a valid SSL certificate. Treat it as its own account, just like production.
Mistake 3: Skipping the 40-second activation visit
After pasting the snippet, the guide says: "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." Many developers install the script, check the console, see no errors, and move on. The AI remains dormant until a real session meets the dwell threshold.
Fix: Open the live page in a browser, wait 40–60 seconds, scroll, click a link. Repeat on a few pages. Then return to the dashboard.
Mistake 4: Not waiting for the domain-verified badge
The same guide instructs: "Wait at least five minutes until you see your website name displayed next to the SEATEXT logo at the top of this page. This indicates that your website is connected and ready to proceed." Impatient users jump straight to the Main AI Hub, activate agents, and wonder why no variants appear. The badge is the handshake confirmation; without it, the backend has not bound the account to the domain.
Fix: After the activation visit, wait 5–10 minutes. If the domain name does not appear next to the logo, contact support — the docs say "please contact our support team immediately" because it often signals an installation issue on the platform (CSP, tag manager misfire, Cloudflare Rocket Loader, etc.).
Mistake 5: Copying the same snippet across accounts
Each account generates its own JavaScript snippet. The snippet contains an account identifier. If you copy the production snippet onto a staging site that belongs to a different account, the staging traffic feeds into the production account, and the staging account stays empty. Conversely, the production site loses its connection.
Fix: Treat snippets like API keys. Label them in your tag manager or repo: seatext-prod.js, seatext-staging.js. Deploy the correct file per environment.
Mistake 6: Assuming settings sync across accounts
Because each domain gets its own account, configuration — language lists, variant approval rules, agent activation states, exclusion selectors — lives per account. There is no global settings panel. Teams that configure the Translation Agent for 12 languages on the production account must repeat the setup on every other account.
Fix: Document your standard configuration as a checklist. Run it for each new account. Consider a small internal runbook: create account → install snippet → activate visit → wait for badge → enable agents → set languages → add exclusion selectors → test a variant.
Key facts
| Rule | Detail | Source |
|---|---|---|
| Account-to-domain ratio | One account per primary URL; no multi-domain support inside a single account | S1 |
| Development domains | Localhost and dynamic preview URLs are restricted; use real domains | S1 |
| Activation requirement | Visit the live page, stay ≥40 seconds, repeat on several pages | S1 |
| Verification signal | Domain name appears next to SeaText logo within 5–10 minutes | S1 |
| Support escalation | If badge missing after 10 minutes, contact support immediately | S1 |
| Snippet uniqueness | Each account generates its own snippet; do not reuse across domains | S1 |
Limitations and when this advice does not apply
The one-account-per-domain rule applies to every SeaText AI plan. There is no enterprise exception that merges domains. If you manage hundreds of client sites, you will have hundreds of accounts. The platform does not currently offer a multi-tenant dashboard or API to provision accounts programmatically. Agencies should plan for manual account creation per client domain.
Subdomains count as separate domains. blog.example.com and shop.example.com each need their own account if you want SeaText AI active on both. The only way to share a single account across subpaths is to keep everything under one primary URL (e.g., example.com/blog and example.com/shop).
FAQ
Can I use one SeaText AI account for a main site and its staging subdomain?
No. The integration guide treats each domain — including subdomains — as a separate primary URL requiring its own account. Use a fixed staging subdomain with a real SSL cert and create a dedicated account for it.
What happens if I install the same snippet on two domains?
The first domain to complete the activation handshake will claim the account. The second domain will never verify, and its traffic will either be ignored or attributed to the first domain, corrupting variant data.
How long does domain verification take?
Typically 5 minutes after the 40-second activation visit. If the domain name does not appear next to the SeaText logo after 10 minutes, the installation likely has a blocker (CSP, tag manager, edge cache). Contact support at that point.
Do I pay extra for each additional account?
Pricing is per account. Check the pricing page for volume or agency discounts; the source pack does not publish specific multi-account rates.
Can I automate account creation via API?
Not currently. The source pack shows no provisioning API. Each account must be created through the web sign-up flow.
What if I migrate a site to a new domain?
Create a new account for the new domain, install its snippet, run the activation visit, wait for verification, then deactivate the old account. Settings do not transfer; reconfigure agents manually.
Does the 40-second visit need to be from a real user or can it be a bot?
It must be a real browser session that executes JavaScript. Automated health checks or curl requests will not satisfy the dwell requirement.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
How SeaText AI helps with multi-domain management
SeaText AI gives each domain its own isolated account so conversion data, variant tests, and agent configurations never bleed across sites. You get accurate per-domain reporting, clean A/B results, and keyword-matched landing pages for every paid campaign. The trade-off is manual account creation and configuration per domain — there is no central dashboard or API to automate this today. Plan for a short runbook per new domain: create account, install unique snippet, run the 40-second activation visit, wait for the verification badge, then enable the agents you need.