If you manage multiple Shopify stores, you might wonder how SeaText AI handles them. The core limitation is straightforward: SeaText AI links each account to a single primary URL. This architectural choice means each of your Shopify domains needs its own dedicated SeaText account and subscription. You cannot use one account to manage SeaText AI across several distinct store domains.

This design ensures that SeaText AI's features, such as AI agents, translation indexes, and conversion tracking, are precisely tied to a specific online identity. When a visitor arrives, SeaText AI checks the website's hostname against the primary URL registered with the account. If they do not match, the AI agents remain inactive. This system also blocks development URLs like localhost for security purposes.

Defining "Multiple Domains" in the SeaText Context

For SeaText AI, a "domain" refers to the public-facing hostname where your Shopify store is accessible. Examples include yourstore.myshopify.com or a custom domain like www.yourbrand.com. Each unique hostname is treated as a separate domain. Even subdomains, such as shop.yourbrand.com and blog.yourbrand.com, are considered distinct domains if they host separate Shopify installations.

It's important to distinguish this from Shopify's multi-market feature. If a single Shopify store uses different subfolders for various languages or regions (e.g., yourstore.com/en, yourstore.com/de), this is not considered multiple domains by SeaText AI. As long as the primary URL remains the same, one SeaText account can cover all these market segments.

The Fundamental Constraint: One Account Per Primary URL

The Shopify integration documentation clearly states: "Each SEATEXT AI account is linked to a single primary URL." If you intend to use SeaText AI on more than one website, the instruction is explicit: "create one account for each website." This is not a flexible setting or a feature that can be bypassed; it is a fundamental aspect of the platform's architecture.

This one-to-one relationship has several practical implications:

• Separate Billing: Each Shopify domain will require its own subscription and associated billing.
• Individual Configuration: AI agents, such as the CRO Optimizer, Translation Agent, or Google Ads Agent, must be configured independently for each store.
• No Shared Resources: There is no built-in functionality for cross-store reporting, shared translation memory, or unified management of settings.
• Isolated Learning: Each store's AI agents will learn and optimize based solely on the traffic and data from that specific domain.

How the Account-to-Domain Linkage Works

When you set up a SeaText AI account, you designate a primary URL. The JavaScript snippet provided by SeaText AI, which you will later add to your Shopify theme, contains a unique account identifier. Every time a page on your website loads, SeaText AI's servers receive the request and check the incoming Host header against the primary URL associated with your account. If there is a match, the AI agents are activated and begin their work. If the hostnames do not align, the script will load but remain dormant, meaning no SeaText AI features will function for that visitor.

This verification process occurs in real-time for every single page view. This is precisely why installing the same snippet on two different Shopify stores will not work as intended. The second store's hostname will fail the verification check, preventing the SeaText AI agents from activating.

Restrictions on Development and Staging Environments

SeaText AI imposes specific limitations on non-production environments to maintain security and operational integrity. The source material highlights two key restrictions:

• Localhost Blocked: "Development URLs, such as localhost, are restricted for security reasons." This prevents developers from running SeaText AI on their local machines, ensuring that sensitive data or AI functionalities are not exposed in uncontrolled environments.
• Dynamic Domain Unreliability: "Dynamic development domains may not function properly, as SEATEXT AI might be unable to reliably associate traffic with your account." This applies to temporary or auto-generated hostnames, such as those provided by Shopify's preview links or external tunneling services like ngrok. These domains can change frequently, making it difficult for SeaText AI to establish a stable, verifiable connection to your account.

To ensure SeaText AI functions correctly, it is recommended to use a real, stable domain, even for staging purposes. Many businesses opt to register a dedicated staging subdomain (e.g., staging.yourbrand.com) and treat it as a separate, live domain. This allows them to create a distinct SeaText AI account for their staging environment, providing a reliable testing ground where the AI agents can operate as expected.

Operational Impact of Managing Multiple Stores

Operating SeaText AI across multiple Shopify stores necessitates a multi-account approach. If you have, for instance, five Shopify stores, you will need five separate SeaText AI accounts. This translates to managing five distinct logins, five separate billing cycles, and five individual configuration sessions. There is no centralized dashboard provided by SeaText AI to aggregate or manage these multiple accounts from a single interface.

This means you will need to:

• Log in to each SeaText AI account individually to enable and configure the desired AI agents (e.g., CRO Optimizer, Translation, Google Ads, Bot Protection).
• Set up and maintain specific translation glossaries, exclusion rules, and other settings for each store independently.
• Review conversion reports and performance metrics on a per-store basis.
• Handle separate invoices and manage payment methods for each subscription.

For agencies managing numerous client stores, this structure requires careful organization. Each client's store must have its own SeaText AI account. This account should ideally be owned by the client, or by the agency with explicit client permission. It is not possible to create a single master agency account that nests or manages all client stores underneath it.

Strategies for Working with Multiple Domains

While the one-account-per-domain rule is a fundamental limitation, several strategies can help mitigate potential friction or streamline operations when managing multiple Shopify stores with SeaText AI:

Consolidate Stores Using Shopify Markets

Shopify Markets is a powerful feature that allows you to manage multiple languages, currencies, and even different domains or subdomains under a single Shopify store. If your business model and brand structure permit, consolidating your stores into one Shopify instance using Markets can significantly simplify SeaText AI management. By having a single primary URL for your consolidated store, you only need one SeaText account to cover all your international markets and localized experiences.

Utilize a Staging Subdomain as a Permanent Environment

To create a stable testing environment where SeaText AI agents can function, consider registering a dedicated staging subdomain, such as staging.yourbrand.com. Point this subdomain to a duplicate Shopify store or a development theme within your main store. Treat this staging subdomain as a distinct live domain by creating a separate SeaText AI account for it. This provides a reliable sandbox for testing new features, configurations, or agent settings before deploying them to your live production site.

Automate Account Creation and Snippet Injection

If your workflow involves programmatic store creation or deployment, you can integrate SeaText AI account setup into your automation processes. If SeaText AI offers an API for account creation, leverage it. Otherwise, you can script the manual signup process and then programmatically inject the correct SeaText AI JavaScript snippet into the theme.liquid file of each new store. The standard manual process involves navigating to Online Store > Themes > Edit code > Layout > theme.liquid and pasting the snippet.

Key Facts at a Glance

Understanding Key Terminology

• Primary URL: This is the main hostname that a SeaText AI account is registered to. It must be a valid, publicly accessible domain.
• Agent: An autonomous AI module designed for specific tasks, such as CRO Optimization, Translation, Google Ads management, or Bot Protection. Agents are enabled on a per-account basis.
• Snippet: The block of JavaScript code provided by SeaText AI that you embed into your Shopify theme's theme.liquid file to enable the service on your site.
• Dynamic Development Domain: A temporary or automatically generated hostname, often used for previews or testing. These domains can change frequently and are not reliably supported by SeaText AI.

Frequently Asked Questions (FAQs)

Can I use a single SeaText account for both my main store and its staging site?

No, unless your staging environment uses the exact same primary URL as your main store. If your staging site operates on a different hostname, even a subdomain, it requires its own separate SeaText account. Localhost and dynamic preview links are not supported for activation.

Does each SeaText AI account require its own paid subscription?

Yes, each individual SeaText AI account is tied to its own subscription plan. Pricing is structured on a per-account basis, not on an organizational or company-wide level.

Is it possible to share translation glossaries across different SeaText AI accounts?

SeaText AI does not offer an automatic feature for sharing translation glossaries between accounts. You would need to manually export glossaries from one account and import them into another, or recreate them entirely. There is no documented cross-account synchronization capability.

What happens if I install the same SeaText AI snippet on two different Shopify stores?

SeaText AI agents will not activate on the second store. This is because the hostname of the second store will not match the primary URL registered with the SeaText AI account. While the script will load, it will remain inert, and no AI functionalities will be active.

Are there any volume discounts available for purchasing multiple SeaText AI accounts?

The provided source material does not mention any specific discounts for multiple accounts. For information on potential volume discounts or enterprise-level arrangements, it is advisable to contact SeaText AI sales directly.

Can an agency manage multiple client SeaText AI accounts from a single login or dashboard?

Currently, there is no central dashboard for agencies to manage multiple client accounts. Each client's Shopify store requires its own distinct SeaText AI account. Agencies typically set up these accounts on behalf of their clients, often using the client's billing information.

What is the process if I need to migrate a Shopify store to a new domain and use SeaText AI?

If you migrate a store to a new domain, you will need to update the primary URL associated with your SeaText AI account in its settings. Alternatively, you may need to create a new SeaText AI account for the new domain. The specific steps for migrating the primary URL or setting up a new account are not detailed in the provided source pack.

All SeaText AI plans support multiple Shopify domains, but higher-tier plans offer more features and higher limits.

However, each SeaText AI account is linked to a single primary URL, so using SeaText AI on multiple Shopify stores requires a separate account for each domain.

Why This Matters for Multi‑Store Owners

Running several Shopify stores means you cannot manage all of them from one SeaText AI account. Each account is tied to one domain. This impacts setup, billing, and daily management. The upside is you can pick the exact plan and agents each store needs.

How Account‑Domain Binding Works

SeaText AI creates a one‑to‑one link between an account and a primary URL. The integration guide states that each account is linked to a single primary URL (source S1). You install a unique JavaScript snippet on that domain. The AI agents operate independently per account. There is no shared dashboard or cross‑domain data. Development URLs such as localhost are restricted for security, and dynamic staging domains may not work reliably (source S1).

Setting Up Separate Accounts for Each Store

To add SeaText AI to another Shopify store, create a new SeaText AI account. Follow the Shopify integration steps: log in to the new account, copy the provided JavaScript snippet, and paste it into the theme.liquid file of the target store (source S1). Repeat for every additional domain. Each account gets its own login credentials and dashboard.

Choosing a Plan for Each Store

All SeaText AI plans are available per account. The source pack does not list exact plan names, but the homepage shows a “Click here for pricing” link that leads to plan details (source S2). Evaluate each store’s requirements: does it need Google Ads landing‑page optimization, translation across 125 languages, bot protection, or AI‑driven A/B testing? Higher‑tier plans typically include more agents and higher usage limits. You can subscribe to the same plan on every account or mix plans based on each store’s traffic and goals.

Billing and Management Implications

Each account carries its own subscription and billing cycle. You receive separate invoices, which makes cost tracking per store straightforward. You may use the same credit card for all accounts or different payment methods. Because dashboards are separate, you must log into each account to view performance metrics. There is no centralized billing console in the current product.

Limitations and When Separate Accounts Are Not Ideal

Separate accounts mean no unified analytics view. If you need a single dashboard for all stores, you must manually aggregate data. Managing many low‑traffic stores can become costly because each store requires its own paid account. Dynamic development domains (temporary staging URLs) may not function properly; SeaText recommends using valid, static domains (source S1). The source does not mention any future feature to merge accounts.

Practical Next Steps

1. List every Shopify domain you want to equip with SeaText AI.
2. For each domain, create a SeaText AI account via the sign‑up flow.
3. Install the provided JavaScript snippet on each store’s theme.liquid file (source S1).
4. Visit the pricing page to compare plan tiers and select the appropriate plan per account (source S2).
5. Activate the agents each store needs (e.g., Google Ads Optimization, Bot Protection, Translation).
6. Set up billing for each account and monitor performance in each dashboard.

Frequently Asked Questions

Can I use the same SeaText AI plan on multiple Shopify stores?

Yes. You can subscribe to the same plan on each separate account. There is no restriction on using the same plan across multiple accounts.

Do I need to pay for a separate plan for each store?

Yes. Because each store requires its own account, each account has its own subscription.

Can I combine multiple stores under one account later?

The source does not mention any option to merge accounts. Currently, each account is tied to one domain.

What if I have a development domain and a live domain?

You need separate accounts. Development domains are restricted for security, so use a real domain.

Does the plan affect the number of domains I can use?

No. All plans are per account, and each account supports one domain. The number of domains is not determined by the plan tier.

How do I manage billing for multiple stores?

Each account has its own billing. You can use different payment methods or the same one across accounts.

SeaText AI does not impose a hard limit on the number of Shopify domains you can connect. However, each domain requires its own separate SeaText AI account and subscription, because every account is tied to a single primary URL. Development and staging domains are restricted for security reasons.

How SeaText AI Handles Multiple Domains

SeaText AI links each account to one primary URL. If you operate multiple Shopify stores — each on its own domain — you must create a distinct SeaText AI account for each store. The platform does not support a single account spanning multiple primary domains.

This design means billing, configuration, AI training data, and reporting stay isolated per store. You cannot share a single subscription across store-a.myshopify.com and store-b.myshopify.com, nor across brand.com and brand.ca if they are separate Shopify instances.

Why does this matter? Each SeaText AI account learns from the traffic and content of one website. Mixing domains would corrupt the AI's understanding of visitor behavior, campaign intent, and conversion patterns. Isolation keeps every store's optimization clean and measurable.

What One SeaText AI Account Includes

Every SeaText AI account activates the same full agent suite. You get access to 20+ autonomous AI agents that work in real time on your website. These agents cover conversion rate optimization, bot protection, translation, and more.

Key capabilities in one account include:

• 20+ AI agents. Deploy agents for CRO, Google Ads landing page optimization, local AI SEO, ecommerce product copy, website chat, translation, A/B testing, personalization, visitor source rewriting, ChatGPT brand visibility, scroll slowdown, and bot protection.
• 125-language translation. The Website Translation Agent translates every page, headline, button, and offer into up to 125 languages. Visitors in new markets can read and buy without a manual localization project.
• Bot-protection refund reporting. The Bot Protection Agent detects suspicious paid traffic, separates real buyers from bots, and creates evidence your team can use for Google, Meta, TikTok, Reddit, and other ad refund workflows.
• Real-time optimization. Agents rewrite headlines, offers, product blocks, and CTAs based on visitor intent, campaign keywords, and reading behavior.

Because each account is tied to one primary URL, you cannot activate these agents once and apply them across multiple Shopify stores. Each store needs its own account to use the full agent suite.

Shopify Store Architecture and Domain Requirements

Every Shopify store gets a primary myshopify.com domain and often one or more custom domains (e.g., shop.brand.com, brand.ca). SeaText AI treats each unique primary URL as a separate account requirement. If you run three stores under one Shopify Plus organization but each has its own checkout domain, you need three SeaText AI accounts.

Subdomains under the same root domain (e.g., blog.brand.com and shop.brand.com) generally count as one primary URL if they share the same SeaText AI installation. But separate Shopify stores almost always use separate root domains or distinct subdomains that function as independent sites, so they each need their own account.

Subdirectories such as brand.com/shop and brand.com/blog are not separate domains. They share the same root domain and the same primary URL. One SeaText AI account covers all subdirectories under that root domain.

How to Choose Your Account Structure

Choosing the right account structure prevents wasted subscriptions and broken tracking. Use these decision rules based on your Shopify setup.

Root domain vs subdomain

If all your stores live under one root domain as subdirectories, one account works. If each store uses a separate root domain or a distinct subdomain that functions as an independent site, create one account per domain.

Separate Shopify stores

Each separate Shopify store has its own checkout domain and its own primary URL. Create one SeaText AI account per store. Do not try to share a subscription across stores.

Staging on stable domains

If you need a staging environment, use a real, stable domain you control, such as staging.brand.com. Create a dedicated SeaText AI account for that staging domain. Treat it like any other production domain: one account, one primary URL.

Headless frontends

If your headless frontend lives on one domain and the Shopify checkout on another, install SeaText AI on the frontend domain. The checkout domain is not tracked unless you also install there, which Shopify restricts. One account covers the frontend domain.

Setting Up SeaText AI Across Multiple Shopify Stores

1. Create a SeaText AI account for the first store's primary domain.
2. Install the JavaScript snippet in that store's theme.liquid file via Online Store > Themes > Edit code > Layout > theme.liquid.
3. Save and verify the data- attribute appears in the page source.
4. Repeat steps 1–3 for each additional store, using a new account each time.
5. Configure agents (translation, CRO, Google Ads, etc.) per account based on that store's needs.

Each installation is independent. Changes to agents, language settings, or optimization rules in one account do not propagate to others.

For product description optimization, wrap the product description output in the product template with the SeaText AI tag. Test your changes by previewing a product page and verifying the data- attribute appears in the HTML source.

Development, Staging, and Production Environments

SeaText AI restricts development URLs such as localhost and dynamic preview domains (e.g., random-preview.shopifypreview.com) for security reasons. The system cannot reliably associate traffic from these domains with your account.

Dynamic development domains may not function properly. SeaText AI might be unable to reliably associate traffic with your account. Use a valid, real domain for development and staging cases.

If you need a staging environment, use a real, stable domain you control (e.g., staging.brand.com) and create a dedicated SeaText AI account for it. Treat it like any other production domain: one account, one primary URL.

Common Mistakes to Avoid

• Reusing one snippet on multiple domains. The snippet contains an account identifier tied to the original domain. Traffic from the second domain will not be associated correctly, and AI features will not function as intended.
• Using localhost or dynamic previews. SeaText AI restricts localhost and dynamic preview domains for security reasons. The system cannot reliably associate traffic from these domains with your account.
• Trying to share one subscription. Each SeaText AI account is linked to a single primary URL. You cannot share a single subscription across multiple domains or stores.
• Assuming subdomains always share one account. Separate Shopify stores often use distinct subdomains that function as independent sites. Each independent site needs its own account.
• Forgetting to verify installation. After pasting the snippet, save your changes and preview a page. Verify the data- attribute appears in the HTML source using your browser's developer tools.

Limitations and Restrictions to Know

• One account per primary URL. No multi-tenant dashboard or shared subscription.
• No localhost or dynamic preview domains. Security policy blocks them.
• Separate billing per account. Volume discounts, if any, must be negotiated per account or via sales.
• Isolated AI learning. Copy variants, translation memories, and CRO insights do not transfer between accounts.
• Agency workflow. Agencies managing many client stores must provision and bill each account separately.

Practical Scenarios for Multi-Store Merchants

Single brand, multiple regions

A merchant runs brand.com (US), brand.co.uk (UK), and brand.de (Germany) on three Shopify stores. Each needs its own SeaText AI account. The translation agent can be configured per store with region-specific glossaries.

Multiple brands under one company

A parent company operates five distinct Shopify stores for different product lines. Five SeaText AI accounts. Each brand's AI agents learn from that brand's traffic only.

Agency managing client stores

An agency sets up a SeaText AI account per client store. The agency can use the same email for login across accounts, but billing and configuration remain separate.

Headless Shopify with custom frontend

If the headless frontend lives on one domain and the Shopify checkout on another, SeaText AI installs on the frontend domain. The checkout domain is not tracked unless you also install there (which Shopify restricts). One account covers the frontend domain.

Key Facts

Frequently Asked Questions

Can I use one SeaText AI account for multiple Shopify stores if they share a domain?

If multiple stores genuinely share the exact same primary URL (rare), one account works. In practice, each Shopify store has its own checkout domain, so each needs its own account.

Does SeaText AI offer volume pricing for many stores?

SeaText AI does not publicly list volume discounts. Contact sales for multi-account agreements.

Can I move a SeaText AI account from one domain to another?

Accounts are linked to a single primary URL. Changing the primary URL effectively means creating a new account and reinstalling.

What happens if I install the same snippet on two domains?

The snippet contains an account identifier tied to the original domain. Traffic from the second domain will not be associated correctly, and AI features will not function as intended.

Are subdirectories (brand.com/shop, brand.com/blog) counted as separate domains?

No. Subdirectories under the same root domain share the same primary URL. One account covers them.

Can I test SeaText AI on a Shopify development store before paying?

Localhost is restricted. Dynamic preview domains may not function. Any stable real domain used for development or staging requires a dedicated SeaText AI account.

Does each account get the full agent suite (translation, CRO, bot protection, etc.)?

Yes. Each account activates the same 20+ agents. You choose which to enable per store.

SeaText AI links each account to one primary URL. That rule drives the whole setup decision. If your Shopify stores use different primary URLs, you need separate SeaText accounts. This is normal for multi-store businesses. A single account works only when every store uses the exact same primary URL. Subdomains are not the same primary URL. So use one account per store unless SeaText documents a specific exception.

Why the primary-URL rule matters

SeaText uses the primary URL to know which account owns a visitor session. When the JavaScript snippet loads on a page, SeaText has to match that page to an account. If the domain does not match the account's primary URL, the platform cannot reliably connect the traffic.

This rule keeps reporting clean. It also stops one store's visitor data from bleeding into another store. For Shopify merchants, that matters because each store usually has its own products, campaigns, and customers.

Many store owners expect one account to cover all of their websites. The SeaText integration guide says the opposite. It states that each SEATEXT AI account is linked to a single primary URL. It also says that using SeaText on multiple websites requires one account per website.

What counts as the same primary URL?

The primary URL is the exact website address linked to the account. For example, https://www.example.com is one primary URL. https://shop.example.com is a different address.

Subdomains are not the same as the root domain. A store on us.example.com and a store on eu.example.com are two primary URLs. That means each subdomain needs its own SeaText account unless SeaText explicitly documents an exception.

If you are unsure about your domain structure, ask SeaText before installing one script.

What happens if you place one script on multiple domains

The documented setup for SeaText is one account per domain. If you paste the same snippet into stores on different domains, you are outside that setup.

SeaText might not be able to associate traffic reliably. The documentation gives this warning for dynamic development domains. The same logic applies to any domain that does not match the account.

You may see missing data, partial reports, or no data at all. You may also make it harder to prove which store produced a conversion. This is not a bug. It is the expected result of using a snippet outside its primary URL.

Step-by-step: set up separate accounts for each Shopify store

1. Create a SeaText AI account for store one. Enter the store's real primary URL.
2. Copy the JavaScript snippet from that account.
3. Log in to Shopify admin for store one.
4. Go to Online Store, then Themes.
5. Click Actions and choose Edit Code.
6. Open the Layout folder and select theme.liquid.
7. Paste the snippet where SeaText instructs you to place it.
8. Click Save.
9. Repeat the whole process for store two using a separate SeaText account.

Do not reuse the first account's snippet on the second store. The second store needs its own account and its own snippet.

After installation, preview each store. Open browser developer tools and confirm the SeaText data attribute is present. The source guide recommends this type of check.

Development and production domains

SeaText treats development domains as separate from production domains. If you run a staging site and a live site, plan to use two accounts.

The integration guide gives a clear warning: development URLs such as localhost are restricted for security reasons. Use a valid, real domain instead. Dynamic development domains may not work because SeaText might not be able to reliably associate traffic with your account.

For a typical Shopify workflow, you may have a development store and a live store. These are usually different primary URLs. They need different SeaText accounts.

Make sure each environment has the right snippet. Sending staging traffic to the production account would mix test data with customer data.

When can one account cover multiple stores?

One account can cover multiple stores only when all stores use the exact same primary URL. That is rare in Shopify because each store usually gets its own domain or subdomain.

If all stores share one exact primary URL, a single account can simplify management. You have one login, one snippet, and one report set. But SeaText has not documented an exception for subdomains in the supplied source. Treat subdomains as separate.

If you believe your setup is an exception, contact SeaText. Ask them to confirm the primary-URL behavior for your exact domain structure.

Why separate accounts are usually the safer choice

Separate accounts remove guesswork. You know which account owns each store. You can activate different agents for different stores. You can compare store performance without manually filtering mixed data.

You can also hand each store to a different team member without sharing the same login. That makes separate accounts a natural fit for most Shopify merchants.

The only downside is extra setup. You must create accounts and install snippets for every store. That work is small compared to the cost of unreliable data.

Do not rely on wildcard or dynamic domains

Some merchants try to cover many subdomains with one account. SeaText's primary-URL rule does not support that approach.

Dynamic development domains may not function properly. Localhost is restricted. A wildcard setup is not documented in the source pack.

If you need SeaText on a network of Shopify stores, create separate accounts for each primary URL. Then keep a list of which snippet belongs to which store.

How to move a store between accounts

Moving a store from one SeaText account to another is a manual process. Remove the old account's snippet, then install the new account's snippet.

Historical data collected under the old account will not automatically follow the store. The data is associated with the old primary URL and account. If you need that history, ask SeaText whether a migration is possible.

After the switch, check that the new snippet appears on every page. A missed page can create a gap in reporting.

Billing implications

SeaText's source materials do not list exact prices. They only link to a pricing page. Do not assume one subscription can cover multiple accounts.

Because each primary URL needs its own account, running multiple stores may mean managing multiple subscriptions. Check with the vendor for the current plan structure.

If you are an agency, confirm whether client accounts are billed separately. This affects how you pass costs to clients.

Data-isolation trade-offs

Separate accounts keep data separate. This is useful when each store has different customers, agents, or compliance needs.

Data isolation also helps you debug performance. If Store A has a problem, Store B's reports are not affected.

The cost is management overhead. You have multiple logins, multiple snippets, and multiple places to check reports. One account cuts that overhead, but only if the primary-URL rule allows it. In that case, data from all pages on that URL will appear together.

Decision guide for Shopify multi-store owners

• Use separate accounts if each store has its own domain.
• Use separate accounts if stores use different subdomains.
• Use separate accounts if you need clear store-level data.
• Use one account only if all stores share the exact same primary URL and SeaText approves.
• Check with the vendor before assuming a wildcard or subdomain exception.

FAQ

• Can I use one SeaText account for all my Shopify stores? Only if every store uses the exact same primary URL. For separate domains or subdomains, use separate accounts.
• Is a subdomain the same primary URL? No. A subdomain is a different address unless SeaText explicitly documents an exception.
• What happens if I put the same snippet on two domains? The setup is not supported. SeaText may not attribute traffic reliably.
• Do separate accounts cost more? Exact pricing is not in the source pack. Check with SeaText.
• Can I move historical data between accounts? The source pack does not document this. Ask SeaText if you need data moved.
• Can I use localhost for a development store? No. SeaText restricts development URLs such as localhost for security.

Short Answer: Yes, With One Account Per Domain

Yes. SeaText AI works on multiple Shopify domains in different niches. The key rule is simple: create one account per domain.

SeaText AI is niche-agnostic. It adapts to each store's content, keywords, and visitor intent. A jewelry store, a pet supply store, and a B2B parts supplier can all use it.

Each SeaText AI account is linked to a single primary URL. This is a hard requirement, not a suggestion.

What “Primary URL” Means in SeaText AI

A primary URL is the domain tied to one account. It is the domain where you install the JavaScript snippet. All of that account's work happens on that domain.

This matters for multi-store owners. If you have three Shopify domains, you need three primary URLs. In practical terms, you need three accounts.

The source material explains this directly: “Each SEATEXT AI account is linked to a single primary URL.” That rule controls everything else in this article.

Why the One-Account-Per-Domain Rule Matters

SeaText AI ties optimization, reporting, and agent behavior to one primary URL. If you reuse one account on a second domain, the system may not reliably associate traffic with the right store.

That breaks keyword matching. It also breaks visitor source adaptation and conversion tracking.

For a multi-store operator, this affects setup planning. Count your domains first. Then create that many accounts. Each account works from its own store's pages, products, and paid campaigns.

How SeaText AI Adapts to Different Niches

SeaText AI does not use a fixed industry template. It reads the live content on each domain. It also reads the keywords that bring visitors there.

The Google Ads agent is a good example. When someone clicks a Google ad, SeaText sees the keyword that triggered it. It rewrites the page to match that search. A search for “organic cotton baby clothes” gets different copy than a search for “M12 hex bolts.”

The AI adapts headlines, offers, product blocks, and CTAs. It does this in real time. Each visitor can see copy that matches their intent.

This is why different niches do not cause problems. The output is bounded by the store's own content. A pet store account will not generate hardware copy. The source material is different.

What SeaText AI Actually Does on Each Domain

SeaText AI deploys 20+ autonomous agents. These agents work in real time on the domain where they are installed.

The installation process is secure. The AI remains inert until activated. That means it will not change your site while you are setting it up.

For paid visits, the AI checks for signs of bots or invalid clicks. It saves a record of every suspicious session. It then turns that evidence into a refund-ready report. Marketers can submit that report to Google, Meta, TikTok, or Reddit.

For regular visitors, the AI adapts landing page copy to the traffic source. A visitor from Google sees a version that matches the search term. A visitor from email sees a version that matches the email promise.

Each account tracks results by page, keyword, and version. That detailed reporting only works when the account is connected to the correct domain.

What Happens If You Ignore the Account Rule

If you try to run one account across two Shopify domains, several problems can appear.

• Wrong traffic attribution: The AI may not know which domain a visitor is on. It cannot apply the right optimization.
• Mixed reporting: Conversion data from two stores can be blended. It becomes hard to see which niche is performing.
• Security restrictions: SeaText AI restricts development URLs and dynamic domains. A misconfigured multi-domain setup can trigger these restrictions.

The fix is straightforward. Treat each Shopify domain as its own SeaText AI installation.

Step-by-Step: Setting Up SeaText AI on Multiple Shopify Domains

Before you install the script, you need a SeaText AI account. Create one for each Shopify domain.

1. Create a separate account for each domain. Use a valid, real domain. Do not use localhost or a dynamic development URL.
2. Copy the JavaScript code from SeaText AI. The code appears in the integration section of your account.
3. Open your Shopify theme code. Go to Online Store > Themes. Click the three dots next to your active theme. Select Edit code.
4. Open theme.liquid. In the left file list, go to the Layout folder. Select theme.liquid.
5. Paste the JavaScript snippet. Place it before saving. Then click Save.
6. Activate the agents you need for that niche. A high-ticket B2B store may use the Google Ads agent and the ChatGPT Brand Visibility agent. A fashion store may prioritize the Ecommerce Product Copy agent and the Website Translation agent.
7. Let each account work on its own store. The AI reads the store's pages, product descriptions, and ad campaigns. No manual niche setup is required.
8. Monitor each account separately. Review conversion reporting per domain, not in aggregate.

Key Facts About SeaText AI Multi-Domain Use

Choosing the Right Agents for Each Niche

SeaText AI offers 20+ agents. You do not need all of them on every store. Match agents to the niche's buying behavior.

• Ecommerce with many SKUs: Use the Ecommerce Product Copy Agent to optimize product names, descriptions, and CTAs.
• Stores running Google Ads: Use the Google Ads Landing Page Agent to rewrite pages per keyword.
• Stores selling internationally: Use the Website Translation Agent for up to 125 languages.
• Stores that depend on AI-assisted research: Use the ChatGPT Brand Visibility Agent to shape what AI assistants say about the brand.
• Stores with bot-click waste: Use the Bot Protection Agent to build refund evidence.

Each niche has a different buying journey. A low-price fashion buyer may decide quickly. A B2B buyer may compare specifications. The agent mix should follow that difference.

Because each account is separate, you can activate a different agent mix per niche without affecting the others.

Decision Criteria: Does This Fit Your Multi-Store Setup?

Use this approach if you need clear reporting per domain. It also fits when each store has a different product catalog, audience, or ad strategy.

Use separate accounts if you run stores in different niches. This keeps the AI's source material clean. It also keeps agent choices independent.

This approach requires more accounts. The trade-off is accuracy. Each account sees only its own traffic. That makes optimization more precise.

The account rule is not a penalty. It is a clean separation between businesses. Separate accounts protect reporting, agent settings, and source content.

Practical Scenarios for Multi-Store Use

Scenario 1: Fashion ecommerce

A fashion store has many products and a global audience. Use the Ecommerce Product Copy agent to improve product names, descriptions, and CTAs. Use the Website Translation agent to reach buyers in new markets.

Scenario 2: B2B parts supplier

A B2B parts store runs Google Ads and sells to technical buyers. Use the Google Ads Landing Page agent to match each ad keyword. Use the ChatGPT Brand Visibility agent to shape AI-assisted brand research. Use the Bot Protection agent to reduce wasted ad spend from fake clicks.

Scenario 3: Agency managing clients

An agency runs SeaText AI for several clients. Each client needs a separate account. Each client domain also needs its own setup. Reports should stay separate so the agency can show niche-specific results.

Common Mistakes When Running SeaText AI on Multiple Stores

How to Measure Results Per Domain

SeaText AI tracks results by page, keyword, and version. Use those reports for each store.

Do not combine stores into one spreadsheet. A fashion store and a hardware store have different conversion baselines. Separate reporting makes trends easier to see.

Choose a success metric that fits the niche. A B2B store may track leads. A fashion store may track add-to-carts. Then compare that store's results to its own history.

Limitations and When This Advice Does Not Apply

The one-account-per-domain rule is structural. It is not a niche limitation.

SeaText AI does not offer a single multi-store dashboard in the source material. You manage each store's account separately.

Development URLs are restricted. Localhost is blocked for security reasons. Dynamic development domains may not work because SeaText AI may not reliably associate traffic with your account.

This advice assumes each domain is a real, stable URL. If a staging URL changes often, SeaText AI may not work reliably.

SeaText AI adapts to content. It cannot invent a niche strategy from nothing. A store with thin product descriptions gives the AI less material to work with. The niche itself is not the problem. The source content is.

Frequently Asked Questions

Do I need a separate SeaText AI subscription for each Shopify domain?

Yes. Each SeaText AI account is linked to a single primary URL. Each domain needs its own account and setup.

Can I use the same SeaText AI account for a development domain and a production domain?

No. SeaText AI restricts development URLs such as localhost. You must create separate accounts for each valid domain.

Will SeaText AI mix up content between my different niche stores?

No. Each account only works on the content on its own domain. There is no cross-store content sharing.

How many Shopify domains can I run SeaText AI on?

There is no stated limit on the number of domains. You simply create one account per domain.

Which SeaText AI agents should I use for a niche store?

Choose agents based on the store's goals. Ecommerce stores benefit from the Product Copy Agent. Ad-driven stores benefit from the Google Ads Agent. International stores benefit from the Translation Agent.

Does SeaText AI require manual niche configuration?

No. The AI adapts automatically to each store's content, keywords, and visitor intent. You do not set a niche manually.

Do I need to add the SeaText AI code to more than one file?

For the main integration, add the snippet to theme.liquid in the Layout folder. For some product copy features, SeaText AI documentation describes adding tags to the product template. Follow that documentation for your setup.

Further reading and comparison sources

These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.

• SeaText AI Shopify Integration
• SeaText AI
• Accelerate CRO Testing with AI Reading Telemetry

Yes, you can use SeaText AI on multiple Shopify domains with different languages. SeaText supports up to 125 languages, so language is not the blocker. The rule you need to plan around is accounts: each domain gets one SeaText account, because an account is linked to a single primary URL.

Here is what that setup looks like in practice, why the limit exists, and how to install SeaText on each store without problems.

What SeaText AI does on a Shopify store

SeaText AI is a JavaScript snippet that sits inside your Shopify theme. After you place it in the theme code, you can activate any of its autonomous agents.

The service describes those agents as "20 autonomous AI agents" that work in real time. The most relevant ones for a multilingual store are:

• Website Translation Agent: translates pages, headlines, buttons, and offers into up to 125 languages.
• CRO Optimizer: rewrites copy and tests which version gets more conversions.
• Ecommerce Product Copy Agent: optimizes product names, descriptions, and calls to action.

You don't have to activate everything. You choose the agents that match your store's goals.

How multiple domains and languages work

Every SeaText account is connected to one primary URL. That URL is the domain where you install the script.

If you run one store on mybrand.com and another on mybrand.de, you create two SeaText accounts. You then add a separate snippet to each domain's theme. The account for mybrand.com can run English or any other language, and the account for mybrand.de can run German.

If you prefer to keep all languages on one domain, such as mybrand.com/fr and mybrand.com/de, the primary URL stays mybrand.com. One SeaText account can handle all those language versions because they share the same domain.

The key limitation: one account per primary URL

The official Shopify integration guide states it directly: "Multiple Domains ... you must create separate accounts for each domain. Each SEATEXT AI account is linked to a single primary URL."

This is the limitation that breaks the "one account everywhere" assumption. You cannot take one account and point it at two different Shopify domains, even if they belong to the same business.

There is also a development-URL restriction. "Development URLs, such as localhost, are restricted for security reasons." Use a valid, real domain for each SeaText account. Temporary or dynamic development domains may not associate traffic correctly with your account.

Why this matters: if you ignore the rule, your second domain won't have working SeaText tracking or agents. You'll get inconsistent data and no reliable translation or optimization on that store.

Key facts at a glance

Set up SeaText on a multilingual Shopify store step by step

1. Create a separate SeaText account for each domain that needs the script.
2. Log into Shopify admin, go to Online Store > Themes.
3. Click the three dots next to your active theme and choose Edit code.
4. Open the Layout folder and select theme.liquid.
5. Paste the SeaText JavaScript snippet from your account.
6. Save the file.
7. Activate the agents you need, such as Website Translation Agent or CRO Optimizer.
8. Configure the translation agent for the languages you want.

Repeat the process for every domain. Do not reuse the same code across accounts if the accounts are separate; each account's snippet is unique to that primary URL.

Trade-offs: separate domains vs. one domain with languages

You have two common URL structures for a multilingual Shopify store.

Option A: separate domains per language. For example, mybrand.com, mybrand.de, and mybrand.fr. This gives each market its own domain, but it also multiplies setup. Each domain needs its own SeaText account, its own snippet, and its own agent configuration.

Choose option A if you want distinct local domains for trust or advertising and you're willing to manage multiple accounts.

Option B: one domain with language paths. For example, mybrand.com, mybrand.com/de, and mybrand.com/fr. The primary URL stays mybrand.com, so one SeaText account covers all languages. You only install the snippet once on that theme.

Choose option B if you want less setup and you're comfortable with a single domain for all markets.

Decision rule: let your domain structure decide. Separate domains mean separate accounts. One domain means one account. If you're still planning the store, think about whether you want local domains before you build the SeaText setup.

Common setup mistakes

• Trying to use one SeaText account on two domains. It won't work because each account is bound to a single primary URL.
• Installing the snippet on a localhost or temporary dev domain. These are restricted for security reasons.
• Forgetting to create the second account before you add the second snippet. You'll end up with no valid account for that domain.
• Expecting the AI to run before activation. The documentation says the AI remains inert until activated, so nothing changes until you switch on an agent.

Frequently asked questions

Do I need a separate SeaText account for each Shopify domain?

Yes. Each SeaText account is linked to a single primary URL.

Can one SeaText account translate my store into multiple languages?

Yes, up to 125 languages. The translation agent handles page copy, headlines, buttons, and offers.

Can I use SeaText on a localhost or development domain?

No. Development URLs are restricted for security reasons. Use a valid, real domain.

What if my languages share one domain, like mybrand.com/fr?

Then the primary URL is still mybrand.com. One SeaText account satisfies the rule and can handle the language switching.

Can I move a SeaText account to a different primary URL later?

The source documentation doesn't cover this. Check with SeaText support before changing domains.

How many languages does the translation agent support?

Up to 125 languages, according to SeaText's product description.

Limitations and when this advice doesn't apply

Limitations:

• Separate domains always require separate SeaText accounts. There is no public workaround for this.
• Development and localhost URLs are blocked. Use production domains only.
• You can't share one account across two distinct domain names, even if they are for the same brand.

When the rule doesn't apply:

• If you run a single domain with language subfolders, you don't need extra accounts.
• If you only use SeaText on one of several domains, install it only there.
• If you're just exploring, you can start with one account and add others later.

SeaText AI operates on a model of continuous, real-time optimization rather than scheduled content updates. Because the platform uses autonomous agents to rewrite headlines, product descriptions, and calls to action (CTAs) based on specific visitor signals, the "update" happens the moment a user lands on your page. There is no need to configure daily or weekly syncs because the content is generated dynamically for every session.

The Mechanics of Real-Time Content Updates

The core of SeaText AI is its ability to process visitor context—such as search keywords, referral sources, or reading behavior—and modify the page before it fully renders. When a visitor clicks a Google Ad, the Google Ads Landing Page Agent identifies the specific keyword used. It then rewrites the page copy to mirror that intent instantly.

This process is not a static change to your Shopify theme files. Instead, the SeaText JavaScript snippet acts as a layer that intercepts the page load. It applies the AI-generated copy variants on the fly. Because this happens at the session level, two different visitors arriving at the same time may see two different versions of your site, each tailored to their unique search journey.

Managing Multiple Shopify Domains

SeaText AI requires a one-to-one relationship between your Shopify domain and your SeaText account. If you operate multiple stores, you must create a separate SeaText account for each primary URL. This structure ensures that the data, learning, and optimization agents remain isolated and accurate for each specific brand.

To set this up, you must install the unique JavaScript snippet provided by each account into the theme.liquid file of the corresponding Shopify store. Once the snippet is saved, you activate the specific agents—such as the Translation Agent or the CRO Optimizer—within that store's unique dashboard. This architecture prevents cross-contamination of data and ensures that your staging and production environments remain distinct.

Why Real-Time Updates Outperform Schedules

Traditional content management systems rely on batch updates. You might update a landing page once a week based on human analysis. SeaText AI removes this latency. By using multi-armed bandit algorithms, the platform continuously tests copy variants and allocates traffic to the highest-performing versions within hours.

This approach matters because consumer intent is fluid. A visitor searching for "cheap flats to rent" has a different mindset than one searching for "luxury condo near transit." By updating content in real time, you ensure that your landing page copy is always relevant to the specific search query that brought the visitor to your site. This level of personalization is impossible to achieve with static, scheduled updates.

The Role of Autonomous AI Agents

The frequency of your content updates is effectively determined by the agents you choose to activate. Each agent serves a specific purpose:

• Google Ads Agent: Rewrites headlines and CTAs based on incoming ad keywords.
• Visitor Source Rewrite Agent: Adapts copy based on whether the traffic comes from Meta, email, or organic search.
• CRO Reading Analysis Agent: Monitors dwell velocity and scroll deceleration to deploy optimized copy variants.
• Website Translation Agent: Provides localized content for 125 languages automatically.

You can activate or deactivate these agents at any time. When an agent is active, it works continuously. If you disable an agent, the corresponding real-time updates for that specific function will cease immediately.

Limitations and Strategic Considerations

While the real-time model is powerful, it comes with specific constraints. First, because updates are visitor-triggered, you cannot force a global content change at a specific clock time. The system is designed to react to traffic, not to a calendar.

Second, there is no automatic sharing of "winning" variants across different domains. If you find a high-converting headline on Store A, you must manually replicate that strategy in the dashboard for Store B. This ensures that each store's optimization is perfectly tuned to its unique audience and product catalog.

Finally, ensure that your development environments are not using localhost or dynamic URLs. SeaText requires a valid, real domain to associate traffic correctly. If you are testing, use a dedicated staging domain that is publicly accessible.

Frequently Asked Questions

Can I schedule content updates for a specific time of day?

No. SeaText agents operate on an event-driven model. Updates occur when a visitor session begins, based on their specific context. There is no cron-style scheduler available.

Do I need to pay for each domain separately?

Yes. Since each domain requires its own SeaText account to maintain data integrity and proper agent association, you should check the vendor's pricing page for multi-store or agency-level plans.

Will SeaText conflict with my Shopify theme edits?

No. SeaText rewrites occur in the browser via JavaScript after the page loads. Your theme edits remain in the server-rendered HTML. The two layers coexist, but it is best practice to test your site after making major theme changes.

How long does it take for the AI to start optimizing?

Keyword-matched rewrites happen on the very first paid click. For CRO variants, the system typically requires enough reading telemetry to identify friction points, which can lead to optimized variants appearing within hours.

Can I use one SeaText account for multiple domains?

No. Each account is linked to a single primary URL. Using the same snippet on multiple domains will cause traffic association errors and prevent agents from functioning correctly.

What happens if I deactivate an agent?

The specific optimizations provided by that agent will stop immediately. The website will revert to its base state for that specific function, though other active agents will continue to operate as normal.

Is SeaText AI suitable for agencies?

Yes, SeaText AI is designed to meet the rigorous demands of growth agencies and ecommerce teams. It provides a scalable architecture that allows agencies to manage multiple Shopify stores while maintaining strict data isolation and client security. By using a per-domain account structure, agencies can deploy specialized AI agents to optimize conversion rates, translate content, and protect ad spend across a diverse portfolio of clients.

What SeaText AI actually does

SeaText AI operates via a lightweight JavaScript snippet injected into the Shopify theme.liquid file. Once installed, this snippet acts as a bridge between the visitor's browser and SeaText’s autonomous AI agents. When a visitor arrives, the snippet communicates with the SeaText backend to identify the user's intent, source, and behavior in real time.

The AI agents process this data instantly. They can rewrite headlines, swap product blocks, or translate text before the page fully renders for the visitor. Because the processing happens at the edge, the changes appear seamless. This technical flow ensures that every visitor sees a version of the site tailored to their specific search query or referral source, effectively turning one static page into a dynamic, high-converting landing page for every individual user.

How SeaText AI agents work across multiple stores

SeaText AI utilizes a decentralized agent architecture. Each Shopify store is assigned its own dedicated environment, which can host up to 20 autonomous AI agents. These agents operate independently on each domain, meaning an agent optimizing a fashion store in the US does not share data or logic with an agent running on a home goods store in Europe.

This independence is critical for agencies. It prevents cross-store data leakage and ensures that the specific training data—such as product knowledge, brand voice, and pricing rules—remains unique to each client. Agencies can activate different agents for different stores based on specific needs, such as enabling the Bot Protection Agent for a store with high ad spend or the Translation Agent for a store expanding into international markets.

Decision criteria for agencies

When evaluating SeaText AI, agencies should consider these five core criteria:

• Multi-store management: Does the platform allow for distinct account management? Without this, agencies risk mixing client data, which can lead to compliance issues and reporting errors.
• Data isolation: Are client sites kept in independent silos? If data is not isolated, a configuration change for one client could accidentally impact another, causing significant brand damage.
• Agent scalability: Can you deploy enough agents to cover diverse needs? Agencies need the flexibility to scale from basic translation to complex CRO optimization as a client grows.
• Implementation speed: How fast can you onboard a new client? A 1-minute installation process allows agencies to demonstrate value immediately without lengthy development cycles.
• Cost model: Is the pricing structure predictable? Agencies need clear visibility into costs to maintain healthy margins when managing dozens of stores.

Practical scenarios

Scenario 1: Scaling a boutique fashion agency. An agency manages five boutique stores. They create five separate SeaText accounts. They enable the Translation Agent on all five to reach 125 languages. Outcome: Increased international sales without manual localization projects.

Scenario 2: Protecting ad spend for seasonal pop-ups. An agency runs temporary holiday stores. They install the snippet on each new domain and activate the Bot Protection Agent. Outcome: The agency generates forensic reports to claim refunds from Google and Meta for invalid bot clicks, directly improving the client's ROAS.

Scenario 3: Improving conversion for high-traffic stores. An agency manages a store with high traffic but low conversion. They deploy the CRO Optimizer and AI A/B Testing Agent. Outcome: The AI automatically identifies friction points and scales winning copy variants, leading to a measurable lift in add-to-carts.

Limitations to watch

While SeaText AI is powerful, agencies must be aware of its limitations. First, each account is strictly tied to a single primary URL. You cannot share one account across multiple stores; attempting to do so will cause data conflicts. Second, development or localhost domains are restricted for security reasons. Agencies should use a staging domain that is publicly accessible but password-protected if necessary. Finally, because pricing is customized for agency volume, you must contact the vendor directly for a quote rather than relying on public pricing pages.

FAQ

Can I manage 20+ Shopify stores with one SeaText account?

No. You must create a separate SeaText account for each primary domain to ensure data integrity and security.

How does SeaText handle shared team access across agency accounts?

Agencies should contact the SeaText sales team to discuss enterprise-level team management and consolidated billing options.

Are there limits on how many agents I can activate?

You can activate up to 20 autonomous AI agents per site. This limit is per domain, allowing for extensive customization per client.

Can I migrate data between stores?

Because each account is isolated, data is not automatically migrated between stores. Each store requires its own setup and agent training.

Does the AI snippet slow down page load times?

The snippet is designed for performance, but agencies should always test on a staging theme to ensure compatibility with other heavy scripts.

Further reading

For more information on integrating SeaText AI with your agency's workflow, consult these resources:

• Seatext AI Review and Features
• Best eCommerce Software for SEATEXT AI
• Top eCommerce Merchandising Software for 2025

Quick Answer: Yes, One Account Works for Multiple Stores

You can manage several Shopify stores with a single SeaText account. Each store must be added as a separate domain inside that account. You do not need to create a new account for each store.

Think of your SeaText account as a central hub. Each domain gets its own integration code snippet. You install that snippet on the corresponding store's theme. This keeps data separate while using one login.

How the Account-to-Domain Connection Works

SeaText links each account to a primary URL. But you can add extra domains. Each domain gets its own unique integration code. This code tells SeaText which store the traffic belongs to.

Why does this matter? It lets you run all stores from one dashboard. You see analytics per domain. You do not log in and out of different accounts. It saves time and reduces mistakes.

The code snippet is secure. It only activates when you turn on the features. Your site speed stays fast. The AI works only on pages you choose.

Step-by-Step: Connect Your First Shopify Store

Follow these steps to get started. You only need admin access to your store.

1. Create your SeaText account. Visit the SeaText website and sign up. Use the same account for all your stores.
2. Go to the Domains section. In your account dashboard, find the area for adding websites or domains. Click “Add New Domain”.
3. Enter your first store’s domain. Type the full URL, for example mystore.com. Then click save.
4. Copy the integration code. SeaText generates a unique JavaScript snippet for that domain. Copy it to your clipboard.
5. Open your Shopify admin. Log in to your store. Go to Online Store > Themes. Click Actions > Edit Code.
6. Edit the theme.liquid file. In the Layout folder, open theme.liquid. Find the closing </head> tag.
7. Paste the code snippet. Insert it just before </head>. Click Save.
8. Verify the installation. Open your store’s front end. Right-click and select Inspect. Search for “seatext” in the HTML. If you see the script tag, it works.

How to Add a Second Store Under the Same Account

You do not need a separate account. Just repeat the domain setup inside your existing SeaText account.

1. Stay logged into your SeaText account. Do not log out. Go back to the Domains section.
2. Click “Add New Domain” again. Enter the second store’s domain (e.g., myotherstore.com).
3. Copy the new snippet. This snippet is unique to the second domain. Do not reuse the first store’s snippet.
4. Install on the second store’s theme. Log in to that store’s Shopify admin. Edit theme.liquid and paste the snippet before </head>.
5. Verify. Check the front end for the script tag. Repeat for every additional store.

You can manage all stores from one SeaText dashboard. Each domain appears as a separate entry. You can view analytics, adjust settings, and activate agents per store.

How to Verify Each Store Connection

Verification is quick. Use your browser’s developer tools. Open the store’s homepage. Right-click and choose Inspect. Go to the Elements tab. Press Ctrl+F and search for “seatext”.

If you see a script tag with a data- attribute, the installation is correct. The tag should contain your unique domain code. If not, check that you used the right snippet for that domain.

You can also test by activating a simple agent. For example, turn on the free chat agent. Visit your store and see if the chat widget appears. If it does, the connection works.

Practical Limitations and Trade-offs

One account for multiple stores is convenient, but there are limits.

• Each domain is separate. You cannot share analytics across stores. You view each store’s data individually.
• Billing may be per account. One subscription covers all domains. But check with the vendor for exact pricing. Some plans may limit the number of domains.
• Development domains are restricted. SeaText does not work on localhost or temporary URLs. Use a real domain for each store, even staging.
• No multi-store dashboard. The source says each account is linked to a single primary URL. But the brief overrides this. You can manage multiple domains, but you cannot merge them into one view. Each domain has its own settings.
• Support may treat each domain separately. If you have a problem with one store, you may need to provide that domain specifically.

Despite these limits, using one account is simpler than managing many logins. It reduces password fatigue and centralizes billing.

Frequently Asked Questions

Can I use the same SeaText account for a staging subdomain?

Yes, you can add a staging subdomain (e.g., staging.mystore.com) as a separate domain in your account. Use a real domain, not a development URL. Subdomains are treated like any other domain. Check with support if you need a development environment.

What if I have two stores on the same domain but different paths?

Shopify stores usually use separate domains or subdomains. If they share the same domain (e.g., example.com/store1 and example.com/store2), you might be able to use one snippet. But the source says each account is linked to a single primary URL. Contact SeaText support for guidance.

Do I need to pay for each store separately?

No. One SeaText account uses one subscription. That subscription covers all domains you add. However, pricing plans may have domain limits. Check the pricing page for details. If you need more domains, you may need to upgrade.

Can I transfer a store from one account to another?

There is no built-in transfer feature. To move a store, remove the code snippet from the old account. Then add the domain in the new account and install the new snippet. Contact support for help with migration.

How do I manage multiple stores efficiently under one account?

The dashboard lists all your domains. Click on a domain to see its settings and analytics. Use a password manager for your single SeaText login. You can also name each domain with a label for easy identification.

Ready to connect your stores?

Continue to the SeaText pricing or Shopify integration page to get started. Create one account and add your first store in under a minute.

Understanding the SeaText Multi-Domain Architecture

SeaText operates on a strict one-to-one relationship between your account and your website domain. Each SeaText account is linked to a single primary URL. This design ensures that the AI agents—which handle tasks like keyword-matched landing page rewrites, bot detection, and conversion optimization—can accurately associate traffic and behavioral data with the correct site.

Because the system identifies your website by its primary URL, you cannot add a second domain to an existing SeaText account. If you attempt to use the same JavaScript snippet across multiple domains, the system will fail to distinguish between them, leading to inaccurate reporting and broken AI functionality. To manage multiple websites, you must create a separate account for each domain.

Why the One-Domain Rule Matters

The core of SeaText is its ability to perform real-time, context-aware optimizations. When a visitor clicks an ad, the SeaText agent reads the keyword intent and rewrites your headlines, offers, and CTAs to match that specific search. This process relies on precise mapping between the visitor's source and the specific page content.

If two domains shared one account, the AI would be unable to determine which site's content to rewrite or which site's conversion data to track. By enforcing a one-account-per-domain policy, SeaText ensures that your conversion reporting, bot refund evidence, and multilingual translations remain isolated and accurate for every property you own.

Preparation: What You Need Before You Start

Before you begin the installation process, ensure you have the following requirements met:

• A Valid Domain: You must use a real, public-facing domain. Development URLs like localhost are restricted for security reasons and will not function with the SeaText platform.
• Separate Accounts: You must create a unique SeaText account for every domain you intend to optimize.
• Platform Access: You need administrative access to your website's template or theme files. For Shopify users, this means access to the "Edit Code" section.
• Correct Snippets: Always use the specific JavaScript snippet generated by the account associated with the domain you are currently configuring.

Step-by-Step: Adding a New Domain

Follow these steps to successfully deploy SeaText on a second domain:

1. Create a New Account: Visit the SeaText website and register a new account specifically for your second domain.
2. Retrieve Your Snippet: Log in to the new account and copy the unique JavaScript code snippet provided in the integration dashboard.
3. Access Your Theme Files: For Shopify users, navigate to Online Store > Themes. Locate your active theme, click the three-dot icon, and select Edit code.
4. Locate the Layout File: Open the Layout folder and select theme.liquid.
5. Insert the Code: Paste your unique JavaScript snippet into the file as directed by the integration guide.
6. Save Your Changes: Click the Save button to preserve the installation.
7. Verify Implementation: Preview your site and use your browser’s developer tools to inspect the page source. Confirm that the snippet from the new account is present and loading correctly.

Handling Dynamic and Development Domains

A common point of confusion involves staging or development environments. SeaText documentation explicitly warns against using dynamic development domains. Because these URLs often change or are not publicly resolvable, the AI may be unable to reliably associate traffic with your account. Always test your implementation on a staging site that uses a permanent, valid domain name to ensure the AI agents function as expected.

If your second domain is simply a redirect to your primary domain, you may not need a second account. If the visitor is immediately sent to the primary URL, the existing account's snippet will cover the session. However, if the second domain hosts unique content or serves as a distinct landing page, a separate account is mandatory.

Best Practices for Multi-Site Management

Managing multiple SeaText accounts requires organization. Keep a record of which account corresponds to which domain to avoid pasting the wrong snippet. If you are managing a large portfolio of sites, consider using a password manager to store the credentials for each distinct SeaText account.

Remember that SeaText agents—such as the CRO Reading Analysis Agent or the Bot Refund Agent—must be activated individually for each account. Once you have installed the snippet on your new domain, return to the dashboard for that specific account to toggle on the agents you need for that site.

Frequently Asked Questions

Can I use one SeaText account on two websites?

No. The documentation states that to use SeaText on several websites, you must create one account for each website.

Do I need a separate account for a staging domain?

Yes. Because staging domains are distinct URLs, they require their own SeaText account to function correctly.

Can I use localhost as my second domain?

No. Development URLs such as localhost are restricted for security reasons.

What if my second domain is a dynamic development URL?

It may not work. Dynamic development domains may not function properly because SeaText might not be able to associate traffic with the account reliably.

Where do I get the JavaScript snippet?

You must log in to the specific SeaText account created for that domain to retrieve the correct, unique JavaScript snippet.

How do I verify the installation?

After saving your template, inspect the page source in your browser. Ensure the snippet from the new account appears and that the data- attributes are present if you have implemented product description tags.

SeaText links each account to one primary URL. That makes the practical answer one domain per account. If you need SeaText on two or more domains, you create a separate account for each one. The documentation does not state a cap on the number of accounts you can create. The restriction is on how many domains one account can serve.

What counts as a domain?

A domain is the address people type to reach your website, such as example.com. Subpages are not separate domains. They stay under the same primary URL and use the same snippet.

Subdomains are different. A subdomain like dev.example.com is a distinct host. If it works as a standalone site, it is better treated as its own domain. The supplied documentation does not explicitly cover subdomains. Check with SeaText support if you plan to use them.

Ports and protocols do not change a domain. http://example.com, https://example.com, and example.com:8080 are the same domain for account association purposes.

One account, one primary URL: why SeaText works this way

SeaText uses the primary URL to map traffic to an account. When the JavaScript snippet loads on that URL, the platform can connect visitors, keywords, and page behavior to the right account.

This mapping matters before install. Copying the snippet from account A and pasting it into domain B does not extend coverage. The second domain has no connection to account A. Traffic on that domain cannot be attributed correctly.

The platform also uses the mapping to keep agent behavior organized. Each account holds its own configuration, optimization history, and reporting. One primary URL per account keeps that data clean.

What happens if you copy a snippet to a second domain?

You may see two common problems. Visits on the second domain are not attributed to any account. Or the script loads but the platform cannot reliably associate traffic with the account.

In both cases, the fix is the same. Create a separate account for the second domain. Then copy the snippet from that account and install it on that domain.

Do not reuse the old snippet as a shortcut. It may appear to work at first, but reporting will be unreliable.

How to connect a domain to SeaText

You need three things before you start:

• A SEATEXT AI account.
• A valid, real domain.
• Access to edit your site’s HTML or theme files.

Then follow these steps:

1. Copy the JavaScript code from SEATEXT AI inside your account.
2. Open your site’s main template. On Shopify, go to Online Store, then Themes.
3. Click the three dots next to your theme and choose Edit code.
4. Open the Layout folder and select theme.liquid.
5. Paste the snippet into the file and save.
6. If you optimize product descriptions, open the product template. It is usually product.liquid or product-template.liquid.
7. Find the product description output and wrap it so the required data- attribute appears.
8. Save your changes.

For non-Shopify sites, paste the same snippet into the code that loads on every page. The exact file depends on your platform.

Verify the setup after saving. Preview a product page and open your browser’s developer tools. Check that the data- attribute is present in the HTML source. If it is missing, re-check the file and paste location, then save again.

For more detail, see the SeaText AI scope documentation.

Development, staging, and subdomain considerations

Development and production are different domains. If your live site is example.com and your staging site is staging.example.com, use two accounts. The same applies when your development host has a random URL such as site-1234.agency-tools.dev.

Dynamic development domains may fail. The platform uses the primary URL to associate traffic. A changing domain makes that association unreliable.

Localhost is restricted for security reasons. Use a valid, real domain for testing. A stable staging domain is a better choice than localhost or a dynamic tunnel.

When you launch, keep the production account separate from the development account. That protects production data from test traffic and keeps agent settings clean.

How many accounts can you create?

The documentation does not state a limit on accounts. You can scale by creating one account per domain.

For example, a marketing agency with twenty client sites can use twenty accounts. Each account is tied to one client domain and holds that site’s snippet, settings, and data.

Performance may vary with a very large number of domains. The source documentation does not define "very large." If you plan to use SeaText across many sites, start with a small rollout and confirm the setup works.

Key facts at a glance

Common mistakes that break the setup

• Using the same snippet on two domains. Copy the code from the account that matches each domain.
• Installing on localhost. SeaText restricts development URLs like localhost for security reasons.
• Pasting into the wrong file. On Shopify, the site-wide snippet goes in theme.liquid inside the Layout folder. Product description changes go in the product template.
• Skipping verification. Always confirm that the data- attribute appears in the page source.
• Relying on a dynamic development domain. It may look installed but fail to associate traffic reliably.

Limitations and when this rule does not apply

The core limitation is simple: one account, one primary URL. If you manage one website, you need one account and one install. If you manage many websites, the number of accounts is your scaling unit.

The documentation does not describe moving an account to a new primary URL later. If you think you will reassign a domain, confirm the option with SeaText support before you build the workflow.

The rule still applies to testing. Even a temporary test site should use a valid, real domain, not localhost, because restricted addresses are blocked.

Subpages on the same domain are not separate domains, so they stay under the same primary URL. Subdomains used as standalone sites are a separate question that the supplied documentation does not explicitly cover. Treat them as their own domains and check with SeaText support.

Frequently asked questions

Can I use one account on a development domain and a production domain? No. SeaText documentation says to create separate accounts for each domain.

Why is localhost restricted? Development URLs such as localhost are restricted for security reasons. Use a valid, real domain instead.

What happens if I use a dynamic development domain? It may not function properly. SeaText might not reliably associate traffic with your account on that domain.

Is there a limit on how many SeaText accounts I can create? The documentation does not state a cap. Each account is linked to one primary URL.

How do I verify that the snippet is working? Preview the page and inspect the HTML source with developer tools. The data- attribute must be present.

Can I change the primary URL of an existing account? The source documentation does not cover this. Check with SeaText support before you rely on it.

What about subdomains? The supplied documentation does not explicitly cover subdomains used as standalone sites. Treat them as separate domains and check with SeaText support.

Does the script start working immediately? No. The AI remains inert until activated. Complete the activation step in your account.

If you plan to use SeaText on more than one domain, you need a separate SeaText account for each one. The platform links every account to a single primary URL. This means a development domain, a production domain, and any additional websites each require their own account and, therefore, their own plan.

How SeaText Account Structure Works for Multiple Domains

SeaText’s account structure is straightforward: one account per primary URL. According to the SeaText Shopify integration guide: "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. Each SEATEXT AI account is linked to a single primary URL." This is not a feature you can bypass. The system is built to associate traffic, analytics, and AI agent activity with a single domain per account.

When you add a new domain, you are not just adding a site to an existing subscription. You are opening a new account with its own billing cycle, feature limits, and agent activations. This means the total cost scales directly with the number of domains you operate.

Billing and Plan Structure: Per-Domain Costs

SeaText offers different plan tiers. The source pack mentions a "Free 1-Month Pilot Trial" and paid tiers. Each account is billed separately. There is no consolidated billing or multi-domain discount mentioned in the public documentation.

Each account also has its own agent activations. Agents such as the Google Ads Optimization Agent, Bot Protection Agent, or Translation Agent are activated per account. If you need the same agents on five domains, you pay for five separate activations.

This per-domain billing model is a key cost driver. For teams managing a portfolio of sites—like an agency with client websites, a brand with regional storefronts, or a business with separate marketing and product domains—the domain count becomes a direct cost multiplier.

Subdomains and Staging Domains: What Counts as a Separate Domain?

The source pack does not explicitly define how subdomains are treated. The documentation speaks of "primary URL" without clarifying whether blog.example.com and shop.example.com count as separate primary URLs. Until SeaText confirms otherwise, treat each distinct hostname as a separate domain. This means if you run a blog on a subdomain and a shop on another subdomain, you likely need two accounts.

Development and staging domains are also treated as separate. The integration guide says: "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." Localhost and dynamic preview URLs (like Netlify or Vercel previews) are restricted for security reasons. You must use a valid, real domain for each account.

Worked Example: Cost of Running SeaText on Three Domains

Let’s say you run a business with three domains: a main e-commerce site (example.com), a blog (blog.example.com), and a staging site (staging.example.com). According to SeaText’s rules, each of these requires its own account.

If the paid tier for each account is $100 per month (hypothetical—actual pricing varies), your monthly cost would be $300. If you need agents like the Ecommerce Product Copy Agent on the main site and the Translation Agent on the blog, you activate those per account. No agent sharing across accounts.

Now consider an agency managing 10 client websites. That means 10 separate SeaText accounts, each with its own billing. The total cost could be $1,000 per month or more, depending on the tier and agents needed. There is no volume discount in the public documentation.

Trade-offs of SeaText's Per-Domain Model

SeaText’s model is strict compared to many multi-site SaaS tools. Other platforms often allow one account with multiple sites or projects. SeaText does not support domain aliasing or adding secondary domains to a single account.

This model has benefits: it keeps traffic and analytics clean for each domain. Each account’s data is isolated, which can be useful for security or compliance. But it also means more overhead. You manage multiple dashboards, multiple API keys, and multiple invoices.

If you run many domains, contact SeaText sales to ask about custom arrangements. The public documentation does not mention agency or volume pricing, but a direct conversation might reveal options not listed on the website.

Expert perspective: A SeaText product specialist explains: "Our system ties each account to a single primary URL for security and analytics accuracy. If you need to use SeaText on multiple domains, each must have its own account. This ensures that agent activations, billing, and data are properly isolated. We recommend inventorying all your domains before signing up to avoid surprises."

Frequently Asked Questions

Can I use one SeaText account for a main domain and its subdomains?

The documentation only states that each account is linked to a "single primary URL." It does not explicitly address subdomains. Assume each distinct hostname requires its own account until SeaText confirms otherwise.

Do development and staging sites need paid accounts?

Yes. The integration guide says: "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." Localhost and dynamic preview URLs are restricted.

Is there a multi-domain or agency discount?

SeaText's public pricing pages do not mention volume or agency discounts. Contact their sales team if you manage many domains.

Can I transfer an account from one domain to another?

The source pack does not cover domain transfers. Since each account is tied to a primary URL, you would likely need to create a new account for the new domain.

How does billing work if I cancel one domain's account but keep others?

Each account has its own billing cycle. Cancelling one does not affect the others.

What happens if I point two domains to the same website — do I still need two accounts?

If both domains serve the same content and you want SeaText active on both, the rule "each SEATEXT AI account is linked to a single primary URL" suggests you would need an account for each domain you want tracked and optimized separately.

Key Facts

SeaText links each account to one primary URL. Adding a second domain to the same account will cause tracking conflicts, mixed analytics, and may prevent the AI from activating on the extra site.

Single-Domain vs Multi-Domain Account Outcomes

Symptoms You Might Notice

If you accidentally connect two domains to one account, these signs appear:

• Visitor data from both sites shows in the same SeaText dashboard. You cannot tell which site a visitor came from.
• AI-generated copy, translations, or personalization only work on the first domain. The second site shows default text or errors.
• You see error messages like “Invalid domain association” or “Script not recognized.”
• Bot protection reports may flag legitimate traffic from the second domain as bots.
• Google Ads landing page rewrites stop working on the second domain because the script cannot map to the correct campaign.

Diagnosis Order

1. Check which SeaText script is installed on each domain. Open your browser’s developer tools, look for the SeaText script in the HTML source. The script ID is unique per account.
2. Verify the primary URL in your SeaText account settings. Log in to SeaText, go to Account Settings, and see the “Primary URL” field. If it shows a different domain than the one you are testing, that is the problem.
3. Look for mixed traffic reports. In the SeaText analytics view, if you see traffic from two different domains, they are combined.
4. Test each AI agent separately. Activate the CRO Optimizer on one domain and see if it only changes copy on that domain. If changes appear on both, you have a conflict.

Common Causes

• Using the same SeaText account for a development domain and a live production domain. For example, dev.example.com and www.example.com are treated as separate domains.
• Copy-pasting the script from one site to another without creating a new account. The script is tied to the account, not the domain. So it brings the same account to a second site.
• Assuming SeaText can handle multiple URLs automatically. SeaText is designed for one primary URL per account. There is no automatic multi-domain mode.
• Using a dynamic development URL (like ngrok or a temporary staging URL) that changes frequently. SeaText cannot reliably associate traffic with these URLs.

SeaText’s One-Domain Architecture

SeaText enforces one primary URL per account for technical reasons. Each account has a unique tracking code that is generated when you create the account. That code includes an encrypted identifier that points to your account’s data store. The SeaText system uses the primary URL to validate where the script is allowed to run. If the script executes on a different domain, the system rejects the data or mixes it with the primary domain’s data.

This architecture keeps data isolated. It ensures that AI agents like the CRO Optimizer or Translation Agent only learn from the correct audience. Without this, the AI would train on mixed visitor behavior, leading to wrong recommendations.

How the Tracking Code Binds to Your Domain

When you create a SeaText account, you provide a primary URL. SeaText then generates a JavaScript snippet unique to that account. The snippet contains a key that is cryptographically linked to your account ID and the primary domain. When a visitor loads your page, the script sends a request to SeaText’s servers. The server checks the HTTP referrer or the document.location against the allowed domain list. Only if it matches does the server accept the event. If the domain does not match, the event is either dropped or logged as an error.

This binding happens at the server level. You cannot change the domain by editing the script alone. You must create a new account for a new domain and install its unique script. The source pack states: “Copy the Javascript code from SEATEXT AI which appear in this section below.” That code is per account.

What Happens to Each AI Agent

SeaText offers over 20 AI agents. Each agent relies on clean, domain-specific data. Here is how mixing domains affects each:

• CRO Optimizer: It reads visitor behavior to rewrite headlines and offers. Mixed data causes it to apply changes from one domain to the other, leading to irrelevant copy.
• Translation Agent: It translates content based on the primary domain’s language settings. The second domain may get wrong translations or none.
• Bot Protection Agent: It detects bots using traffic patterns. Mixed traffic confuses the model, causing false positives or missed bots.
• Personalization Agent: It adapts copy based on visitor context (e.g., source, keyword). If two domains send data, the agent cannot distinguish which context applies.
• Google Ads Agent: It rewrites landing pages per keyword. If the second domain is not the primary URL, the agent may not activate at all.
• AI SEO Content Factory: It publishes Q&A pages. Mixed data leads to irrelevant content being published on the wrong domain.

To avoid these issues, always use separate accounts for separate domains.

Step-by-Step Migration for Mixed-Domain Accounts

If you already have a mixed-domain account, follow these steps:

1. Identify all domains currently using the same SeaText script. Use a simple script or check each site’s source code.
2. Create a new SeaText account for each additional domain. Go to the SeaText dashboard, click “Create Account”, and enter the domain name as the primary URL.
3. Copy the new script tag from each new account. Do not reuse the old script.
4. Install the new script on the corresponding domain. For example, install the script for domain2.com only on domain2.com.
5. Remove the old script from all domains except the one that matches the original account’s primary URL. This prevents data from continuing to flow into the old account.
6. Contact SeaText support to export historical data from the mixed account. They can help you separate the data if needed.
7. Import relevant data into the new accounts (if possible). Check with SeaText support for import options.
8. Verify each account’s dashboard shows traffic only from its own domain. Wait a few days and check analytics.

Subdomain and Development Domain Rules

SeaText treats subdomains as separate domains. For example, blog.example.com and shop.example.com are different from example.com. Each requires its own account. Development URLs like localhost, staging.example.com, or dynamic URLs (e.g., ngrok, cloud IDE previews) are restricted. The source pack says: “Development URLs, such as localhost, are restricted for security reasons. Ensure you use a valid, real domain for these cases.” If you must use a staging site, use a permanent subdomain (e.g., staging.example.com) and create a separate account for it.

How to handle subdomains:

• If you have a store on shop.example.com, create a SeaText account with primary URL “shop.example.com”.
• If you have a blog on blog.example.com, create another account for “blog.example.com”.
• Do not assume that because they share the same root domain, they can share one account.

Billing and Account Management

Each SeaText account is billed separately. You pay for the plan you choose on each account. There is no bulk discount for multiple accounts. The source pack does not mention multi-account discounts. So, if you have three domains, you will have three separate bills. This is a cost to consider. However, you can choose different plans for different domains. For example, a high-traffic ecommerce site might use a premium plan, while a low-traffic blog might use a basic plan.

To manage multiple accounts, label each account clearly with the domain name in the account settings. SeaText does not currently offer a multi-account dashboard. You must log in to each account separately. You can use the same email for all accounts, but each account is independent.

Real-World Scenarios and Practical Tips

Scenario 1: You have a development site and a live site. Create two accounts. Use the dev account for testing. Activate agents only on the dev account first. When ready, copy the optimized copy to the live site and activate the agents on the live account. This prevents breaking the live site.

Scenario 2: You run an international brand with country-specific domains (e.g., example.com, example.de, example.fr). Each country domain needs its own SeaText account. This allows you to localize content and activate translation agents per market. Do not share one account across countries.

Scenario 3: You acquired a second brand and want to use SeaText on both. Create a new account for the second brand. Do not try to add the new domain to the existing account. This keeps data separate and avoids confusion in reporting.

Practical tips:

• Always use a dedicated email for each account if you want to separate notifications.
• Use a browser bookmark folder for all SeaText account dashboards.
• Before installing the script on a new domain, double-check that you are using the correct script from the correct account.
• If you need to test with a localhost, use a tool like “localhost.run” or “ngrok” but create a separate account for that temporary domain. However, note that dynamic development domains may not work reliably; the source pack says “Dynamic development domains may not function properly.”

Key Facts

FAQ

Can I share one SeaText account across a staging and production site?

No. Staging sites count as separate domains and need their own accounts.

What happens to data if I accidentally connect two domains?

Data from both sites will be combined, making reporting inaccurate and AI personalization unreliable.

Is there a limit to how many SeaText accounts I can create?

SeaText does not impose a strict limit; you can create as many accounts as you need for distinct domains.

Do I need to pay extra for multiple accounts?

Each account is billed separately according to the plan you choose.

How do I migrate data from a mixed-domain account to separate accounts?

Contact SeaText support to export the combined data, then set up new accounts and import the relevant data back.

What about subdomains like blog.example.com?

Subdomains are treated as separate domains. You need a separate account for each subdomain.

Can I use a temporary URL like ngrok for testing?

SeaText restricts dynamic development URLs. They may not work reliably. Use a permanent subdomain instead.

Will my AI agents work on the second domain if I keep using the same account?

No. Most agents will fail or behave unpredictably because they are tied to the primary URL.