How to Migrate SeaText AI Settings from Staging to Live
SeaText AI does not support direct settings migration between domains. Each domain requires its own SeaText AI account linked to a single primary URL. To move from staging to live, create a new account...
SeaText AI ties every account to one primary URL. There is no export/import feature that moves configuration from a staging domain to a production domain. The practical path is to create a fresh SeaText account for the live domain, install the script, activate it, and then rebuild the agent selection, variant rules, and translation preferences by hand.
Why a direct migration does not exist
SeaText AI's architecture binds each account to a single domain for security and billing reasons. The General Integration documentation states: "Each SEATEXT AI account is linked to a single primary URL" and "If you need to use SEATEXT AI on multiple domains (e.g., a development domain and a production domain), you must create separate accounts for each domain." This design prevents accidental cross-domain data leakage and ensures usage metrics stay isolated per site.
This means you cannot simply copy settings from one domain to another. The separation is intentional. It protects your live site from staging errors and keeps billing accurate. Understanding this helps you plan the migration without frustration.
Why this process matters
Migrating SeaText AI settings correctly avoids wasted time and broken functionality. If you skip steps, agents may not fire, translations may be missing, or bot detection may fail. That can cost you ad spend and conversions.
Manual reconfiguration is the only reliable method. It forces you to audit what you actually use on staging. You might discover old variants or agents you no longer need. This cleanup is a hidden benefit of the migration.
Also, the live account starts fresh. Historical A/B test winners and bot refund evidence do not transfer. That is fine because the live site's traffic patterns differ. Starting clean avoids inheriting stale data.
Prerequisites before you start
- A live domain that is publicly accessible (not localhost, not a dynamic preview URL).
- Admin access to insert JavaScript in the
<head>of every page on the live site. - A list of the agents, variant rules, and translation settings currently active on staging so you can replicate them.
- At least 15 minutes to complete installation, activation, and verification.
Step-by-step: set up SeaText AI on the live domain
- Create a new SeaText account for the live domain. Go to the SeaText signup page and register using the production URL. Do not reuse the staging account credentials.
- Copy the JavaScript snippet. After login, open the General Integration page. Copy the provided
SEATEXTCODEINTEGRATIONscript block. - Install the script on the live site. Paste the snippet into the
<head>of every page. If you use WP Engine, install the WP Engine plugin that allows custom JavaScript and apply it site-wide. - Activate the AI. Visit the live site, refresh several pages, and stay on a page for at least 40 seconds. This triggers the initial handshake.
- Wait for connection confirmation. Return to the SeaText dashboard. Within 5–10 minutes the live domain name should appear next to the SeaText logo at the top of the page. If it does not appear after 10 minutes, contact support.
- Enable the agents you need. Open the Main AI Hub. Activate each agent (Conversion Agent, Google Ads Agent, Translation Agent, etc.) that you had running on staging.
- Recreate variant rules. Navigate to Variants Edit in the left panel. For each URL and language, rebuild the automatic translations and manual variants you configured on staging.
- Adjust AI parameters. Open Configuration for each active agent and match the staging settings (tone, aggressiveness, exclusion rules, etc.).
- Test on a few key pages. Visit high-traffic pages with query parameters that trigger agent behavior (e.g.,
?utm_source=googlefor the Google Ads Agent). Verify that rewrites, translations, or bot detection fire as expected.
What settings must be recreated manually
| Setting category | Where to configure | Notes |
|---|---|---|
| Active agents | Main AI Hub | Toggle each agent on/off per domain |
| Agent parameters | Configuration panel per agent | Tone, exclusions, targeting rules |
| Variant translations | Variants Edit → URL + language | Manual edits do not copy over |
| Language list | Translation Agent settings | Select the 125 languages you need |
| Bot refund thresholds | Bot Refund Agent config | Sensitivity, evidence retention |
| CRO test variants | AI A/B Testing Agent | Winner history resets on new account |
Practical migration scenarios
Scenario 1: You have a simple staging site with only the Google Ads Agent active. Migration takes about 20 minutes. Create the live account, install the script, activate the agent, and copy the tone settings. No variants to rebuild.
Scenario 2: You have a complex staging site with 10 agents, 50 variant translations, and custom bot refund thresholds. Budget 1–2 hours. Take screenshots of every configuration panel before starting. Rebuild variants one by one using the staging variants as a reference.
Scenario 3: Your staging site uses a dynamic preview URL like pr-123.example.com. SeaText may not track that domain reliably. In that case, move to a stable staging subdomain before migrating. Or, if you have no stable staging, re-create settings from memory and documentation.
Verification checklist after go-live
- Domain name shows next to SeaText logo in dashboard.
- Each intended agent shows "Active" status.
- Test page loads show rewritten headlines for Google Ads traffic.
- Translation switcher works for at least two target languages.
- Bot Refund Agent logs suspicious clicks in the evidence report.
- No console errors related to the SeaText script.
Common mistakes to avoid
- Reusing the staging account on the live domain. The script will fail to associate traffic correctly because the account is bound to the staging URL.
- Using localhost or a dynamic preview URL for the live account. SeaText blocks localhost and may not reliably track dynamic development domains.
- Skipping the 40-second activation visit. Without it, the AI stays inert and the dashboard never shows the domain as connected.
- Assuming variant edits sync across accounts. They do not; each account maintains its own variant database.
- Forgetting to re-enable the Translation Agent. If you need 125-language support, you must turn it on and select languages again.
Limitations and when this advice does not apply
- If you run a multisite network where subdomains share a single codebase, you still need one SeaText account per subdomain.
- Enterprise customers with a dedicated contract should confirm with their account manager whether a bulk-provisioning tool exists; the public product does not expose one.
- Dynamic staging URLs (e.g.,
pr-123.example.com) may not function reliably; prefer a stable staging hostname. - Historical A/B test winners and bot-refund evidence do not transfer; the live account starts with a clean slate.
Key facts
| Fact | Detail |
|---|---|
| Account-to-domain binding | One SeaText account = one primary URL |
| Staging vs. live | Separate accounts required |
| Localhost support | Blocked for security |
| Dynamic dev domains | May not function properly |
| Activation requirement | Visit page, stay 40+ seconds |
| Connection confirmation | Domain appears next to logo in 5–10 min |
| Variant storage | Per-account, not portable |
| Agent activation | Manual per account in Main AI Hub |
FAQ
Can I export variants from staging and import them on live?
No. The Variants Edit interface does not have an export/import function. You must recreate each variant manually.
Does the staging account keep working after I set up the live account?
Yes. Each account operates independently. You can keep the staging account for future testing.
Will my billing change when I add a live domain?
Each domain counts toward your plan limits. Check your subscription details or contact sales for multi-domain pricing.
What if my live site is behind a password or VPN during setup?
SeaText needs public access to verify the domain. Temporarily allow public access or use a staging subdomain that is publicly reachable.
How long before agents start rewriting content on the live site?
After the domain shows as connected in the dashboard and agents are toggled active, rewrites begin immediately for new visits.
Can I use the same API key for staging and live?
No. The JavaScript snippet contains a domain-specific token. Using the staging snippet on live will not associate traffic with the live account.
What happens if I accidentally install the staging script on the live site?
Traffic will be attributed to the staging account, skewing analytics and preventing live-domain agents from activating. Remove the wrong script and install the correct one.
Should I delete the staging account after migration?
Not necessarily. Keep it for future testing or rollback scenarios. But remember the staging account continues to count toward your plan limit.
Can I copy agent configuration using screenshots?
Yes. Screenshots are a reliable way to record settings. Take a screenshot of each agent's configuration panel before deactivating the staging account.
Does the migration affect my live site's SEO?
No. The migration does not change your site's structure or content. It only affects how SeaText agents behave on the live domain. Proper testing ensures no negative SEO impact.
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.