See how this page can help with your next step.
Direct Answer: To migrate SeaText AI from a development store to a live store, you must create a separate SeaText account for the live domain, install the JavaScript snippet on the live store, and manually replicate your agent settings and content configurations. SeaText ties each account to a single domain, so there is no automated export-import feature—you will need to note your development settings and apply them to the new account.
SeaText AI links each account to one primary URL. That means a development store and a live store cannot use the same account. You must create a new account for the live domain. The platform has no automated export-import tool. So careful manual documentation is required.
Why does SeaText enforce one domain per account? The JavaScript snippet collects visitor data from that domain. If the same account were used on two domains, the system could not reliably associate traffic with the correct store. That would break agent behavior, reporting, and refund evidence.
This restriction also affects development URLs. Localhost is blocked for security reasons. Dynamic development domains may not work either. SeaText needs a stable, real domain to track traffic accurately.
The practical result is that migration is a manual process. But it is not difficult if you plan. Most simple setups can be moved in under an hour.
Before you start, gather these items:
You also need to know which agents you use. Common ones include CRO Optimizer, Google Ads Landing Page Agent, Translation Agent, and Free Website Chat Agent.
Make sure the live store is ready. It should have a theme, products, and pages. The SeaText script is inert until you activate agents. So you can install it safely before launch.
Log into the SeaText account for your development store. Open each agent and write down its configuration.
Pay attention to:
Take screenshots. Copy text into a document. Do not skip this step. Without a record, you will rebuild everything from memory.
Keep in mind that some content is domain-specific. Q&A pages published by the AI SEO Content Factory are indexed for the development URL. They will not move to the live store automatically.
This is also a good time to review which agents actually helped. You may not need to move all of them. For example, if you never used the Bot Protection Agent, you can leave it behind.
Document the exact domain format from your development account. Note whether it includes www or not. You will need to match that format on the live account.
Go to seatext.com and sign up. Use the live store's domain as the primary URL.
Do not reuse the development account. The system will not work on a different domain. Even subdomains count as separate domains.
SeaText offers a free 1-month pilot trial for new accounts. Use that trial to test the migration before paying. The setup is reversible, but the trial gives you time to verify.
When entering the domain, be exact. Include the protocol and subdomain if needed. For example, use https://www.yourstore.com and not yourstore.com if the live store redirects to www.
If you have multiple live stores, create a separate account for each. The source pack confirms that each website needs its own account.
The integration process is the same as for any Shopify store. Follow these steps:
</head> tag.The source pack says the AI remains inert until activated. So installing the script does not change your live site. It simply adds the tracking and control layer.
After saving, verify the snippet is present. View the live page source and search for the SeaText script. You can also use browser developer tools to inspect the network requests.
The same integration steps apply to most platforms, but Shopify is the documented example. If you use another platform, check SeaText's integration guide for your specific theme.
A common mistake is editing the wrong theme. Make sure you edit the active theme, not a duplicate or an unpublished one.
In the new SeaText account, activate the same agents you documented in Step 1. Enter the same rules, keywords, and overrides.
This step is manual. But the agent interfaces are designed for quick setup. If you have many custom rules, work through one agent at a time.
For content-based agents like the AI SEO Content Factory, you may need to regenerate content for the live domain. The content is tied to the store URL. There is no way to copy it between accounts.
Use the live store's pages and products to test each agent. For example, the Translation Agent should translate the live site's text. The Google Ads Landing Page Agent rewrites pages based on ad keywords.
Do not forget to configure bot protection and refund settings if you used them. The Bot Protection Agent records evidence for refund claims. That evidence is domain-specific.
If you used the ChatGPT Brand Visibility Agent, you may need to rebuild your brand profile for the live domain. The agent shapes what AI assistants understand about your brand, and that data is tied to the domain.
For the AI Personalization Agent, copy any audience segments or visitor context rules you had. These rules likely reference your development store's pages. Update them to match the live store's URLs.
Do not turn on every agent at once. Start with a low-risk one like the Free Website Chat Agent or the Scroll Slowdown Agent. Confirm that it works on the live store.
Then activate more impactful agents. The Google Ads Landing Page Agent changes page copy in real time. The AI CRO Optimizer rewrites headlines and offers. If something breaks, you want to know which agent caused it.
Test each agent by visiting the live store as a normal visitor. Check that expected changes appear. Use developer tools to look for SeaText data attributes.
Also watch the SeaText dashboard. It should show traffic and events for the live domain. That confirms the snippet is sending data correctly.
If an agent behaves differently on the live store, compare its settings with your documentation. A small difference in a keyword or rule can change behavior.
Run a final checklist after all agents are active.
If something is missing, double-check the domain in your account settings. A mismatch between www and non-www can cause issues.
Also check that the snippet is still in the theme after any theme updates. Some updates overwrite code changes. You may need to re-add it.
Keep your development account active until the live store is stable. That gives you a fallback reference if you need to check a setting.
| Fact | Detail |
|---|---|
| Each domain requires its own account | You cannot use one SeaText account on multiple domains. Create a new account for the live store. |
| No automated export/import | Settings must be manually documented and re-entered in the new account. |
| Development store restrictions | Development stores must use a real, valid domain. Localhost and dynamic development URLs are not supported. |
| Free trial available | SeaText offers a 1-month free pilot trial for new accounts – useful for testing the live store setup. |
| Content is domain-specific | Content generated by agents (e.g., SEO pages, translations) is tied to the domain and cannot be transferred. |
No, SeaText does not currently offer an export feature. You must manually copy your settings.
For a simple setup with a few agents, the migration can be completed in 30–60 minutes. For complex configurations with many custom rules, allow 1–2 hours.
No, the SeaText snippet is lightweight and will not affect site performance. Agents remain inactive until you activate them, so you can migrate without downtime.
No, the free 1-month pilot trial is per account. You can start a new trial for the live store.
SeaText restricts localhost for security reasons. You must use a real, valid domain for the development store to test SeaText. If you are using a localhost dev environment, you will not be able to install SeaText there.
Yes, because the snippet is tied to the specific SeaText account (which is linked to the domain). You must install the new snippet from the live store's account.
Start with the Free Website Chat Agent, Scroll Slowdown Agent, or Visitor Source Rewrite Agent – these are low risk and easy to verify.
Yes, but keep the accounts separate. Changes you make to the live account will not affect the development store.
Create one SeaText account per domain. Each account is tied to a single primary URL.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: SeaText AI offers a free 1‑month pilot trial for development stores, but premium agents, multiple domains, and usage beyond the trial may require paid plans. No hidden fees are listed, but you should verify current pricing on the SeaText website.
SeaText AI lets you test its 20 autonomous agents on a development store for free for one month. After the trial, you may need to pay for continued use, premium agents, or additional domains.
SeaText does not have a separate price for development stores. Pricing is based on the number of domains you connect and the agents you keep active after the trial.
Each domain needs its own SeaText account. A development store at dev.example.com and a live store at example.com each require a separate account.
The pilot trial lasts 30 days. During this period you can activate all 20 agents at no cost.
To start, create a SeaText account for the domain you want to test. The trial begins when you activate the account.
After 30 days the trial ends automatically. SeaText does not charge you unless you choose a paid plan.
SeaText’s pricing page (linked in the source) lists the paid plans. The source pack does not give exact numbers, but it confirms that a paid subscription is required to keep agents running.
Typical cost drivers include:
Base plans likely include a core set of agents. Premium agents—like advanced translation or bot‑protection—may be add‑ons.
When deciding whether to upgrade, consider these factors:
Scenario A – Small Shopify shop testing CRO
The shop uses a development store to test the CRO Optimizer agent. The free trial covers the entire test period. No payment is needed unless the shop wants to keep the agent live on the production store.
Scenario B – Agency managing multiple client sites
An agency has 5 client domains. Each domain requires its own SeaText account. The agency must budget for 5 separate subscriptions, even if all clients share the same plan tier.
Scenario C – International brand needing translation
The brand activates the Website Translation Agent after the trial. Translation is a premium feature, so the brand must select a plan that includes it or pay an add‑on fee.
SeaText does not work on localhost or dynamic development URLs. You must use a real, publicly reachable domain.
Each account is locked to a single primary URL. Switching a domain from development to production requires a new account for the production URL.
The free trial does not transfer between domains. If you finish the trial on a development store, you must start a new trial on the production store.
SeaText will not charge you automatically after the trial. You must actively choose a paid plan and enter payment details.
Yes. The 1‑month pilot trial works on any real domain, including development stores.
Yes. SeaText requires one account per primary URL. Development and production stores each need their own account.
No. SeaText does not auto‑renew. You must select a paid plan and provide payment information.
The source pack does not list which agents remain free. Check the pricing page or contact SeaText for details.
The source pack mentions no hidden fees. Costs arise only from paid plans, premium agents, or additional domains.
No discount is mentioned. Pricing appears the same for all domains.
The source pack does not specify usage caps for the trial. If limits exist, SeaText would likely pause the agents until you upgrade.
No. The trial is tied to the domain used when the account was created. A new trial must be started for the production domain.
Yes. Translation and other advanced agents are likely premium add‑ons that require a higher‑tier plan.
Simply let the trial expire. Your agents stop working, and no charge is applied.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Yes, SeaText AI provides SEO audits, keyword suggestions, and content optimization that work on development stores, helping you prepare for launch. Each domain needs a separate account, and localhost or dynamic URLs are not supported.
Launching a new store without SEO preparation means starting from zero visibility. Search engines need time to crawl, index, and trust new pages. By optimizing during development, you ensure that product pages, category structures, and technical foundations are search-ready on day one. This reduces the post-launch ramp-up period and protects early marketing spend. SeaText AI lets you run audits, generate keyword maps, and publish long-tail Q&A content before any real visitors arrive.
SeaText AI deploys 20 autonomous agents that operate via a JavaScript snippet installed in your theme.liquid file. On a development store, the snippet loads but remains inert until you activate specific agents in the dashboard. The AI SEO Content Factory agent crawls your site structure, identifies gaps in search coverage, and publishes indexed Q&A pages that target long-tail queries. Other agents like the Ecommerce Product Copy Agent rewrite product titles and descriptions for clarity and keyword relevance. The Local AI SEO agent optimizes for "near me" and city-specific searches. All agents read your live DOM, so they work on any valid domain, including password-protected development stores.
On a development store you can activate and test most SEO agents. The AI SEO Content Factory creates crawlable answer pages for buyer questions, which helps capture traffic from Google AI Overviews and ChatGPT referrals. The Ecommerce Product Copy Agent runs automated A/B tests on product names, descriptions, and CTAs, scaling the variants that drive more add-to-carts. The Visitor Source Rewrite Agent adapts page copy to match the referral source — Google, Meta, email, or referral — so each visitor sees a message aligned with their intent. The Website Translation Agent renders pages in up to 125 languages without a manual localization project. The Free Authority Link Builder connects your content to relevant editorial resources, boosting domain authority signals. The AI CRO Reading Analysis Agent tracks millisecond-level reading behavior to spot friction points and generate copy fixes. The Bot Protection Agent detects invalid clicks in paid campaigns and builds refund-ready reports for Google and Meta.
The process is secure; the script does not modify content until agents are turned on.
Pre-Launch Optimization: Agencies and merchants can build a full SEO foundation — technical audits, keyword maps, long-tail Q&A pages, translated content — before the store goes public. This means launch day traffic hits optimized pages immediately.
Staging Environment Testing: You can experiment with different content strategies, A/B test product copy variants, and measure reading telemetry without affecting the live site. The AI CRO Reading Analysis Agent provides dwell-time and scroll-depth data even with low traffic.
Client Approval Workflows: Agencies configure SeaText on a client's development store, demonstrate SEO improvements, and get sign-off before migrating to production.
Trade-Offs: Features that rely on live traffic — real-time conversion tracking, bot-click refund evidence, personalized headline rewrites for paid clicks — will not produce actionable data until the store receives real visitors. You can still configure the rules and templates in development, but the optimization loop closes only when traffic flows.
When you move to production, create a new SeaText AI account for your live domain (e.g., example.com). Export any keyword lists, content templates, and agent configurations from the development dashboard if the platform supports it; otherwise, recreate them manually. Re-install the JavaScript snippet on the live theme. Activate the same agents. Review all SEO settings — meta templates, Q&A page structures, translation languages, bot-protection rules — and ensure they match the live site's architecture. Because accounts are domain-specific, historical data (reading telemetry, A/B test results, bot reports) stays with the development account. Plan to rebuild that data on the live account within the first few weeks.
SeaText AI restricts localhost to prevent unauthorized access and ensure data integrity. The platform needs a valid, publicly resolvable domain to associate traffic and enforce account boundaries.
Create separate SeaText AI accounts for each domain. This is mandatory because each account is linked to a single primary URL. You will manage two dashboards, two subscriptions, and two sets of agent configurations.
Pricing is based on the account, not the store type. Check the SeaText pricing page for details on plans and trials. A free 1-month pilot trial may be available for new accounts.
You can activate and configure most agents, but agents that require live traffic — such as the Google Ads Optimization Agent, Bot Protection Agent, and Visitor Source Rewrite Agent — will not generate meaningful results until real visitors arrive.
Data is tied to each account's domain. When you launch, set up a new account for the production domain and reconfigure your SEO settings there. Historical telemetry and test results do not transfer automatically.
It provides automated SEO audits, keyword suggestions, long-tail Q&A page generation, product copy optimization, multi-language rendering, and authority link building — all configurable without live traffic.
Most features are available for configuration. Real-time personalization, conversion tracking, and bot-click refund evidence require live traffic to function fully.
Yes, as long as the domain is valid and publicly resolvable. The SeaText snippet loads behind the password gate; agents crawl the rendered DOM once activated.
Account creation and snippet installation take under 10 minutes. Agent configuration depends on how many features you enable; a typical SEO-focused setup takes 30–60 minutes.
Visit the SeaText AI Shopify integration guide and pricing page for step-by-step instructions and plan details tailored to your development environment.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Yes, SeaText AI lets you manage several Shopify stores from one login, but each store needs its own SeaText account because the integration snippet is tied to a single primary domain.
SeaText AI links a JavaScript snippet to a single primary URL. The snippet contains a unique data- attribute that identifies the account and the domain it belongs to. When the page loads, SeaText reads that attribute and activates the AI agents only for the matching account (source S1). If the same snippet is placed on a different domain, SeaText cannot associate traffic with the original account, so the agents stay inactive. Creating a separate account for each store guarantees that data, settings, and billing stay isolated.
Connecting SeaText AI is a three‑step process:
data-seatext attribute.theme.liquid. In Shopify admin, go to Online Store → Themes → Actions → Edit code. Open the Layout/theme.liquid file and insert the snippet just before the closing </head> tag. This placement ensures the script loads early on every page.data- attribute present, confirming the script is active.The snippet does not alter your theme’s design. It simply loads SeaText’s AI library, which then reads the page content, product data, and visitor behavior to provide real‑time copy suggestions, translations, or bot‑protection.
Follow these exact steps for each additional store you want to manage.
theme.liquid. In the left‑hand file list, expand the Layout folder and click theme.liquid.</head> tag. Do not place it inside another script block.data-seatext attribute appears in the <script> tag.If the attribute is missing, the snippet was not saved correctly or was placed in the wrong file. Re‑insert it and save again.
SeaText provides an account‑switcher in the top‑right corner of the dashboard. After you log in, click your profile picture and select the store you wish to edit. The switcher loads the configuration for that specific account, keeping each store’s AI settings separate (source S1).
Because each account is independent, you can set different agent combinations, language targets, or bot‑protection rules per store. Billing is also per‑account, so you can assign each store to a different team member’s credit card if needed.
localhost are blocked for security reasons (source S1). Use a real domain for testing, or create a separate account for a staging domain.store*.example.com), create a distinct account for each sub‑store.data- attribute points to a single URL.Symptom: AI agents do not appear on a newly connected store.
Check 1 – Snippet placement. Verify the snippet is directly before </head> in theme.liquid. If it sits inside another tag, the script may not load.
Check 2 – Correct account. Open the SeaText dashboard and confirm you are logged into the account that generated the snippet. The account switcher must show the store’s name.
Check 3 – Domain match. In the dashboard, the primary URL listed must exactly match the store’s live domain (including https://). Mismatched www vs non‑www versions cause a mismatch.
Check 4 – Cache. Clear your browser cache or open the page in incognito mode. Shopify may serve a cached version of theme.liquid that does not include the latest changes.
If all checks pass and agents still do not load, contact SeaText support with the account ID and a screenshot of the data-seatext attribute.
No. Each primary URL needs its own account. Development URLs like localhost are blocked, and a staging domain counts as a separate website (source S1).
Theme updates that replace theme.liquid can overwrite custom code. After a major theme upgrade, reopen the file and re‑paste the snippet if it is missing.
SeaText does not impose a hard limit, but each store requires a separate account and subscription (source S1).
All AI settings, training data, and usage logs for that account are removed. Data is not transferred to another account automatically.
Yes. You can use the same credit card for each subscription, but each account is billed individually.
data-seatext attribute matter?The attribute tells SeaText which account’s configuration to apply. Without it, the script loads but remains inert, so no AI agents appear on the page.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Using SeaText AI across multiple Shopify stores saves time, ensures consistent SEO practices, and provides a unified analytics view. However, each store requires its own separate account, which is a key design requirement for security and accurate tracking.
Using SeaText AI across multiple Shopify stores saves time, ensures consistent SEO practices, and provides a unified analytics view. You can deploy the same AI agents on each store without copying work by hand. There is one key rule: each store needs its own SeaText account. This rule protects store data and keeps performance reporting accurate.
Running one store is already hard. Running several stores multiplies the work. Each store may target a different country, currency, or customer group. Each one needs its own SEO strategy, product copy, and ad landing pages.
Without a shared system, you repeat tasks many times. You update a headline in one store, then copy it to another. You test an offer in one market, then manually set up the same test elsewhere. Small changes become large projects.
This is why multi-store owners look for automation. They want one approach that works everywhere. They also need clear data for every store. SeaText AI fits that need, but it uses a specific account structure.
SeaText AI gives you access to 20+ AI agents that work automatically. These agents help increase conversion rates, recover ad spend lost to bot traffic, translate content, and improve the visitor journey. The agent library includes the CRO Optimizer, Google Ads Landing Page Agent, Translation Agent, Bot Refund Agent, and AI A/B Testing Agent.
For a single store, the setup is simple. You add a JavaScript snippet to the theme.liquid file. Then you activate the agents you need. The source integration guide says the process takes under one minute.
For multiple stores, you repeat that process for each store. You create an account per store and add the snippet to each theme. Then you activate the same agents across all stores. The result is consistent optimization without manual copying.
Each agent works for the store where it is activated. A Google Ads click on a U.S. store sees copy that matches that keyword. A click on a U.K. store sees a local version. The same logic runs on every store, but the output is tailored to each domain.
The integration guide is clear: each SeaText account is linked to a single primary URL. If you need SeaText on multiple domains, you must create separate accounts. This applies to a U.S. store and a U.K. store. It also applies to a development domain and a production domain.
This is not a bug. It is a design choice. Separate accounts keep data isolated. Agent settings, analytics, and billing stay separate for each store. That makes it easier to see which store performs best.
There is also a security layer. Development URLs like localhost are restricted. You must use a valid real domain. Dynamic development domains may not work because SeaText cannot reliably associate traffic with your account.
For an agency, this structure is useful. You can bill per store and give each client a dedicated view. You can also run the same strategy across client stores without mixing metrics.
Separate accounts do not mean separate dashboards. You log into the same platform to view each store. The platform provides conversion reporting by page, keyword, and variant for each store.
This gives you a practical advantage. You can compare how the same agent performs on different domains. You can see which headline works in the U.S. and which works in the U.K. You can then apply winning ideas to other stores.
Unified analytics matter for budget decisions. If one store wastes ad spend on bot clicks, the Bot Refund Agent builds a report for that store. If another store has strong international demand, the Translation Agent can expand its language coverage.
Because accounts are separate, the numbers stay clean. You never mix visitors from two stores. Each store's conversion rate reflects only that store's traffic. This is critical for accurate reporting.
The most useful agents for multi-store teams include:
These agents do the same job on every store. But each store's data stays separate. That lets you measure the true impact of each feature per domain.
SeaText AI fits several types of multi-store teams.
Ecommerce brands with region-specific stores can keep copy local. A U.S. store and a U.K. store can run the same agents but show local offers. That is useful for currency, language, and seasonality.
Agencies managing client stores can use separate accounts to protect data. Each client gets clean reporting. The agency can deploy the same proven strategy across accounts without mixing results.
Stores with both development and production domains need separate accounts. This keeps test traffic out of production analytics. The source guide says dynamic development domains may not work, so use real domains.
If you run dozens of stores, the overhead is higher. You must create and manage one account per store. The available source material does not mention multi-store discounts. Check with SeaText for current pricing options.
| Fact | Detail |
|---|---|
| Account requirement | One account per domain. Each account linked to a single primary URL. |
| Agent library | 20+ AI agents. |
| Integration time | Under 1 minute per store. |
| Languages supported | Up to 125 per store. |
| Conversion lift | Source reports up to +35% conversion lift. |
| Bot refund potential | Recover up to 20% of ad spend. |
| Adoption | Trusted by 2,500+ brands. |
The one-account-per-store rule has tradeoffs. You cannot use a single license across multiple stores. You must repeat the integration for each store. That takes under a minute per store, but it is still a manual step.
Billing may be separate per account. The available source material does not explain multi-store billing. Check with the vendor for exact details.
Development URLs are restricted. Use a valid real domain for every store. This is a security measure, but it can slow down pre-launch testing.
Each account keeps its own data. The source guide does not describe cross-account data sharing. This keeps reporting clean, but you cannot compare internal AI learning across stores. You compare final metrics instead.
If your product lines are very different, the same agent settings may not suit every store. Review each store's agents and adjust them for local market conditions.
From an SEO manager's point of view, the main win is consistency. You can roll out the same optimization playbook across every store. You can also prove what works by comparing store-level reports.
The one-account-per-store rule is not a blocker. It is a reporting control. It prevents one store's noise from hiding another store's results. For a performance marketer, that separation is valuable.
For agencies, separate accounts create clear scope. Each client gets its own configuration. Each client gets its own reporting view. This makes audits and billing simpler.
The real value appears over time. As each store accumulates data, you can see which markets respond to which offers. You can then scale the winners across the network.
No. Each account is linked to a single primary URL. You need a separate account for each domain. This keeps data isolated and reporting accurate.
Create an account for each store. Add the JavaScript snippet to each store's theme.liquid file. Activate the agents you need. The integration takes under one minute per store.
Yes, you can activate the same agents. Each agent uses that store's traffic and data. Results may vary by market.
Yes. The Translation Agent can translate each store's content into up to 125 languages independently.
Yes. The Bot Refund Agent runs on each store and creates separate refund reports for each store's campaigns. This helps recover ad spend lost to invalid clicks.
The available material does not mention multi-store discounts. Check with SeaText for current pricing options.
Use a separate account and a real domain. URLs like localhost are restricted for security.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: To set up SeaText AI for multiple Shopify domains, create a separate SeaText account for each domain, because one account is linked to a single primary URL. Then install each account's JavaScript snippet in that store's theme.liquid file and save it. Use a real production domain; localhost and dynamic development domains are restricted.
To set up SeaText AI for multiple Shopify domains, create a separate SeaText account for each domain. One account is linked to one primary URL, so a single account cannot manage two stores. Then install each account's JavaScript snippet in the correct store's theme.liquid file and save it.
That rule applies whether you are running a production store and a development store, or two completely separate websites. The setup works the same way for each one: one account, one domain, one code snippet.
Before you open any theme files, gather these items:
Why this matters: the code snippet is the bridge between your store and your SeaText account. If you paste the wrong account's code, that store will report to the wrong domain, and you won't get reliable results.
Work through these steps for each Shopify domain you want to add. Do not try to combine multiple domains into one account.
Common mistake: using one SeaText account code on two stores. That will not work, because each account is linked to a single primary URL. Each store needs its own account and its own code.
After you save the theme, verify the snippet on that specific domain. The integration guide asks you to check for a data attribute in the HTML source. This is the clearest confirmation that the code is present.
Use these steps on every store:
data-.If the attribute is missing, go back to the theme editor. Confirm that you saved theme.liquid. Also confirm you are inspecting the same domain that owns the code. A development preview URL may not match the account's primary URL.
Note: dynamic development domains may not work reliably. Test on a real production domain for the final check.
SeaText uses the primary URL to associate traffic and activity with your account. When a visitor loads your site, the installed script tells SeaText which domain it came from. If two domains use the same account, SeaText cannot reliably tell those stores apart.
Development domains have extra restrictions. localhost is blocked entirely because it is not a real public domain. Dynamic development domains, such as temporary preview URLs generated by some hosting tools, may also stop working because SeaText may not be able to reliably associate their traffic with your account.
If you have both a development store and a production store, plan for two accounts from the start. The integration guide uses this exact example. The development domain gets one account. The production domain gets another.
Practical workflow:
This separation keeps testing data clean. You will not mix staging traffic with real visitor traffic in reporting.
If you ignore the one-account-per-domain rule, you may see confused reporting, missing traffic attribution, or a store that never activates properly. The dynamic development domain restriction means a temporary preview URL could fail without a clear reason.
Also, the script is inert until activated. So installing the same code on several stores does not immediately break anything. It just means all of those stores are pointing at one account. Once you activate agents, the account will try to treat the traffic from multiple domains as if it came from one primary URL. That is the situation the integration guide warns you to avoid.
This matters for maintenance too. If you later need to change settings, add agents, or review performance, separate accounts keep each store's data clean and easy to manage.
Sometimes the script does not show up. Work through these checks.
First, verify the code is in the right file. Open Online Store > Themes > Edit code. Look under Layout for theme.liquid. Search for your snippet. If it is not there, paste it again and save.
Second, check that you copied code from the correct account. Each account's code points to that account's primary URL. Using code from another store will cause the wrong association.
Third, clear the storefront cache. Some themes and apps cache the HTML. After saving the theme, a cached version may still be served. Preview with a cache-busting query string like ?nocache=1 or open an incognito window.
Fourth, confirm the product template includes the data attribute. The integration guide says to wrap the product description output. Find product.liquid or product-template.liquid and make sure the tag is placed correctly.
Fifth, replace old snippets completely. If a previous SeaText code exists, remove it before pasting the new one. Two copies of a snippet can conflict and may produce duplicate requests.
Sixth, remember that dynamic development domains may fail. If the preview URL is temporary, the script may not load. Test on the real domain.
Finally, the AI stays inert until you activate it. A lack of visible changes is normal. Look at the source code, not the page, to confirm installation.
| Fact | What it means |
|---|---|
| Account-to-domain link | Each SeaText account is linked to a single primary URL. |
| Multiple domains | Create a separate account for each domain, such as a development domain and a production domain. |
| Multiple websites | Create one account for each website. |
| Development URLs | localhost is restricted. Use a valid real domain. |
| Dynamic development domains | May not function correctly because SeaText might not reliably associate traffic with your account. |
| Installation | Paste the JavaScript code into theme.liquid in the Layout folder and save. |
| Activation | The AI remains inert until activated. |
No. Each SeaText account is linked to a single primary URL. For each domain, create a separate account.
localhost is restricted for security reasons. SeaText also needs to associate traffic with your account, and localhost is not a real domain. Use a valid, real domain for staging or testing.
After you paste the code and save the theme, preview a product page. Use browser developer tools to inspect the page source and confirm the expected data attribute appears. The integration guide describes this exact check.
Create a separate SeaText account for each store. Then copy the code from each account, replace the code in the matching store's theme.liquid, save, and test each one.
No. Use separate accounts for each domain. The integration guide calls out this example directly. Keep the development account on the staging store and the production account on the live store.
No. The installation process is secure and the AI remains inert until activated. After the code is in place, you activate the agents you want for that account.
The SeaText site includes a pricing link. Because you will need one account per domain, check pricing before you create multiple accounts.
Start with one domain. Create the first SeaText account, copy its integration code, and install it in that store's theme.liquid. Once that store is working, repeat for every additional Shopify domain.
Use the official Shopify Integration page to copy the current code and follow the latest setup steps. That page also includes the pricing link if you need to review plans before creating accounts.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: SeaText AI operates on a one-account-per-primary-URL basis. This means each distinct Shopify domain requires its own SeaText account and subscription. Development environments like localhost are restricted, and dynamic staging domains may not function reliably. Individual configuration and management are necessary for each store.
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.
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 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:
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.
SeaText AI imposes specific limitations on non-production environments to maintain security and operational integrity. The source material highlights two key restrictions:
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.
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:
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.
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:
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.
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.
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.
| Fact | Detail | Source |
|---|---|---|
| Account-Domain Binding | Each SeaText AI account is strictly linked to one primary URL. | S1 |
| Multiple Websites Requirement | For use on several websites, a separate SeaText AI account must be created for each one. | S1 |
| Localhost Restriction | Development URLs like localhost are blocked due to security protocols. | S1 |
| Dynamic Domain Reliability | Dynamic development domains may not work consistently with SeaText AI. | S1 |
| Installation Method | The JavaScript snippet is pasted into the Layout/theme.liquid file within the Shopify theme editor. | S1 |
| Agent Activation | AI agents remain inactive until the installation is complete and they are activated. | S1 |
theme.liquid file to enable the service on your 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.
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.
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.
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.
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.
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.
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.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: All SeaText AI plans support multiple Shopify domains, but higher-tier plans offer more features and higher limits. Each SeaText AI account is linked to a single primary URL, so multi‑store use requires a separate account for every domain. You can choose any plan per account, giving flexibility to match each store’s needs.
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.
| Criterion | Single‑domain account | Separate accounts per domain |
|---|---|---|
| Domains per account | One primary URL per account (source S1) | One primary URL per account; create a new account for each additional domain (source S1) |
| Multi‑store setup | Not possible on one account | Create an account for each store; install the unique JavaScript snippet on each domain (source S1) |
| Plan selection | Any plan can be chosen for the single account | Choose the same or different plans per account; higher tiers unlock more agents and higher limits (source S2) |
| Billing | One subscription, one invoice | Each account has its own subscription and invoice; you can use the same payment method across accounts (source S1) |
| Analytics | Unified dashboard for that domain only | Separate dashboards per account; no cross‑store view (source S1) |
| Best for | Single‑store merchants | Merchants running multiple Shopify stores who want tailored plans per store |
| Recommendation: Choose a separate account per store and select higher‑tier plans only for stores that need advanced agents such as Google Ads optimization or bot protection. | ||
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.
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).
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.
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.
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.
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.
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.
Yes. You can subscribe to the same plan on each separate account. There is no restriction on using the same plan across multiple accounts.
Yes. Because each store requires its own account, each account has its own subscription.
The source does not mention any option to merge accounts. Currently, each account is tied to one domain.
You need separate accounts. Development domains are restricted for security, so use a real domain.
No. All plans are per account, and each account supports one domain. The number of domains is not determined by the plan tier.
Each account has its own billing. You can use different payment methods or the same one across accounts.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: 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.
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.
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.
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:
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.
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.
Choosing the right account structure prevents wasted subscriptions and broken tracking. Use these decision rules based on your Shopify setup.
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.
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.
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.
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.
theme.liquid file via Online Store > Themes > Edit code > Layout > theme.liquid.data- attribute appears in the page source.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.
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.
data- attribute appears in the HTML source using your browser's developer tools.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.
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.
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.
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.
| Factor | Detail |
|---|---|
| Hard limit on domains | None |
| Accounts per domain | One |
| Subscription model | Per account |
| Development domains (localhost, dynamic previews) | Restricted |
| Staging on real domain | Allowed, requires own account |
| AI data sharing across accounts | Not supported |
| Installation method | JavaScript snippet in theme.liquid |
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.
SeaText AI does not publicly list volume discounts. Contact sales for multi-account agreements.
Accounts are linked to a single primary URL. Changing the primary URL effectively means creating a new account and reinstalling.
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.
No. Subdirectories under the same root domain share the same primary URL. One account covers them.
Localhost is restricted. Dynamic preview domains may not function. Any stable real domain used for development or staging requires a dedicated SeaText AI account.
Yes. Each account activates the same 20+ agents. You choose which to enable per store.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: SeaText AI links each account to one primary URL. Most multi-store Shopify setups need one account per store because different stores use different domains. Use separate accounts unless SeaText documents an exception.
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.
| Decision factor | One account for all stores | Separate account per store |
|---|---|---|
| Primary URL rule | Works only for the exact same primary URL | Meets SeaText's one-account-per-primary-URL rule |
| Management | Single login and one snippet | More logins and one snippet per store |
| Data isolation | Mixed data across stores | Clear separation of data and settings |
| Setup effort | Low if the rule is met | Medium: create and configure each account |
| Billing | Check with the vendor | Check with the vendor |
| Who it fits | Stores that share one exact primary URL | Most Shopify stores with separate domains or subdomains |
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Yes, SeaText AI is niche-agnostic and can handle multiple Shopify stores in different industries. Each domain needs its own SeaText AI account. The AI adapts to each store's content, keywords, and visitor intent, so a fashion store and a hardware store can both use it without cross-contamination.
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.
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.
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.
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.
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.
If you try to run one account across two Shopify domains, several problems can appear.
The fix is straightforward. Treat each Shopify domain as its own SeaText AI installation.
Before you install the script, you need a SeaText AI account. Create one for each Shopify domain.
| Fact | Detail |
|---|---|
| Niche compatibility | Niche-agnostic; adapts to each store's content and keywords |
| Account structure | One SeaText AI account per primary URL |
| Shopify installation | Paste JavaScript snippet into theme.liquid via Online Store > Themes > Edit code |
| Development domains | Restricted; use a valid, real domain |
| Agent selection | Choose agents per store based on that niche's goals |
SeaText AI offers 20+ agents. You do not need all of them on every store. Match agents to the niche's buying behavior.
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.
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.
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.
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.
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.
| Mistake | Why It Hurts | Fix |
|---|---|---|
| Reusing one account for two domains | Traffic attribution and reporting break | Create one account per domain |
| Using localhost or a development URL | SeaText AI restricts these for security reasons | Use a valid production domain |
| Activating all agents on every store | Wastes budget and creates irrelevant optimizations | Pick agents per niche goal |
| Comparing aggregate metrics across stores | Hides niche-specific performance | Review each account separately |
| Pasting the snippet in the wrong theme file | The integration may not load on all pages | Use Layout > theme.liquid |
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.
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.
Yes. Each SeaText AI account is linked to a single primary URL. Each domain needs its own account and setup.
No. SeaText AI restricts development URLs such as localhost. You must create separate accounts for each valid domain.
No. Each account only works on the content on its own domain. There is no cross-store content sharing.
There is no stated limit on the number of domains. You simply create one account per domain.
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.
No. The AI adapts automatically to each store's content, keywords, and visitor intent. You do not set a niche manually.
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.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Yes, you can use SeaText AI on multiple Shopify domains with different languages. SeaText supports up to 125 languages, but each domain needs its own SeaText account because one account is tied to a single primary URL.
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.
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:
You don't have to activate everything. You choose the agents that match your store's goals.
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 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.
| Item | SeaText requirement or capability |
|---|---|
| Language support | Up to 125 languages for page copy, headlines, buttons, and offers. |
| Account structure | One account per primary URL. Separate domains need separate accounts. |
| Installation | Add the JavaScript snippet to the theme.liquid file in Online Store > Themes > Edit code. |
| Development URLs | localhost is restricted. Use a real production domain. |
| Multiple websites | Create one account for each website you want to use SeaText on. |
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.
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.
Yes. Each SeaText account is linked to a single primary URL.
Yes, up to 125 languages. The translation agent handles page copy, headlines, buttons, and offers.
No. Development URLs are restricted for security reasons. Use a valid, real domain.
Then the primary URL is still mybrand.com. One SeaText account satisfies the rule and can handle the language switching.
The source documentation doesn't cover this. Check with SeaText support before changing domains.
Up to 125 languages, according to SeaText's product description.
Limitations:
When the rule doesn't apply:
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: SeaText AI does not use scheduled batch updates. Instead, it employs autonomous agents that rewrite page content in real time for every individual visitor. Each Shopify domain requires a dedicated account to manage these visitor-triggered optimizations independently.
| Criteria | SeaText AI | Traditional CMS |
|---|---|---|
| Update Frequency | Real-time (per visitor) | Batch/Scheduled |
| Trigger | Visitor intent/context | Manual/Calendar |
| Multi-Domain | Separate account per URL | Centralized |
| Optimization | Autonomous AI agents | Manual A/B testing |
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 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.
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.
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 frequency of your content updates is effectively determined by the agents you choose to activate. Each agent serves a specific purpose:
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.
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.
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.
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.
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.
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.
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.
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.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Yes. SeaText AI is built for agencies, offering multi-store support, separate client accounts, and scalable AI agents that can handle many Shopify sites.
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.
| Criteria | SeaText AI | Best For |
|---|---|---|
| Multi-store management | Separate accounts per domain | Agencies needing clean data separation. |
| Client security | Isolated account environments | Agencies managing competing brands. |
| Scalability | 20 autonomous agents per site | High-growth stores needing deep optimization. |
| Setup effort | 1-minute JS snippet | Teams prioritizing rapid deployment. |
| Pricing | Check with the vendor | Agencies requiring custom volume plans. |
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.
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.
When evaluating SeaText AI, agencies should consider these five core criteria:
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.
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.
For more information on integrating SeaText AI with your agency's workflow, consult these resources:
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Yes, you can use one SeaText account for multiple Shopify stores. You must connect each store domain separately within the same account. No separate accounts are needed.
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.
| Criteria | Detail |
|---|---|
| Stores per account | Multiple, but each domain connected separately |
| Integration method | JavaScript code snippet per domain |
| Install time per store | Under 1 minute |
| Account management | Single login for all connected stores |
| Billing | One account, one subscription (check with vendor) |
| Development domains | Restricted; use real domains |
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.
Follow these steps to get started. You only need admin access to your store.
</head> tag.</head>. Click Save.You do not need a separate account. Just repeat the domain setup inside your existing SeaText account.
</head>.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.
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.
One account for multiple stores is convenient, but there are limits.
Despite these limits, using one account is simpler than managing many logins. It reduces password fatigue and centralizes billing.
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.
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.
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.
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.
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.
Continue to the SeaText pricing or Shopify integration page to get started. Create one account and add your first store in under a minute.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: SeaText requires a unique account for every domain you manage. Learn why this architecture exists, how to set up multiple accounts, and the steps to install your JavaScript snippets correctly.
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.
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.
Before you begin the installation process, ensure you have the following requirements met:
localhost are restricted for security reasons and will not function with the SeaText platform.Follow these steps to successfully deploy SeaText on a second domain:
theme.liquid.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.
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.
No. The documentation states that to use SeaText on several websites, you must create one account for each website.
Yes. Because staging domains are distinct URLs, they require their own SeaText account to function correctly.
No. Development URLs such as localhost are restricted for security reasons.
It may not work. Dynamic development domains may not function properly because SeaText might not be able to associate traffic with the account reliably.
You must log in to the specific SeaText account created for that domain to retrieve the correct, unique JavaScript snippet.
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.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: SeaText links each account to one primary URL. The practical answer is one domain per account. To use SeaText on several domains, you create a separate account for each website. Development URLs such as localhost are restricted, and dynamic dev domains may not work reliably.
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.
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.
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.
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.
You need three things before you start:
Then follow these steps:
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 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.
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.
| Question | Answer from SeaText documentation |
|---|---|
| How many domains can one account use? | One primary URL per account. |
| Can I use SeaText on multiple websites? | Yes. Create one account for each website. |
| Can I install on localhost? | No. Development URLs such as localhost are restricted for security reasons. |
| Do dynamic development domains work? | They may not function properly because traffic association can fail. |
| Is the script active right after install? | No. The AI remains inert until activated. |
| How do I confirm the install? | Check that the data- attribute appears in the HTML source using browser developer tools. |
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.
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.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: SeaText requires a separate account and plan for every domain you want to use. Each account is tied to a single primary URL. This means managing multiple websites means setting up and paying for multiple SeaText accounts.
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.
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.
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.
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.
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.
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."
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.
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.
SeaText's public pricing pages do not mention volume or agency discounts. Contact their sales team if you manage many domains.
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.
Each account has its own billing cycle. Cancelling one does not affect the others.
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.
| Fact | Detail |
|---|---|
| Account-to-domain ratio | 1:1 (one account per primary URL) |
| Development domains | Require separate accounts; localhost restricted |
| Multi-site billing | No consolidated billing documented |
| Agent activation | Per account |
| Subdomain policy | Not explicitly defined |
For more details on SeaText’s multi-domain setup, refer to the official documentation:
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: SeaText accounts support only a single primary domain. If you add more than one domain to the same account, data can mix, tracking breaks, and the AI may stop working correctly.
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.
| Criterion | Single Domain Account | Multi-Domain Account (One Account for Multiple Domains) |
|---|---|---|
| Data isolation | Each domain’s data is stored separately and never mixed. | Data from all domains is combined into one dashboard, making per-domain analysis impossible. |
| AI activation | All AI agents activate correctly on the single domain. | AI agents may fail to activate on the second domain or behave unpredictably due to mixed signals. |
| Tracking accuracy | Visitor analytics, personalization, and bot detection are accurate for that domain. | Tracking becomes unreliable. Bot detection may see false positives. Personalization uses wrong data. |
| Billing | One account, one plan, one bill. | You still pay for one account, but the service is broken. You end up creating separate accounts anyway. |
| Setup effort | Simple: install the single script tag on your domain. | Confusing. You must reinstall different scripts and migrate data, costing extra time. |
If you accidentally connect two domains to one account, these signs appear:
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.
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.
SeaText offers over 20 AI agents. Each agent relies on clean, domain-specific data. Here is how mixing domains affects each:
To avoid these issues, always use separate accounts for separate domains.
If you already have a mixed-domain account, follow these steps:
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:
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.
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:
| Fact | Detail |
|---|---|
| Account scope | One primary URL per SeaText account |
| Tracking code | Each domain needs its own SeaText script tag |
| Development domains | Localhost or dynamic URLs are not supported |
| Subdomains | Treat as separate domains; each needs its own account |
| Billing | Each account is billed separately |
| Data isolation | Only possible with separate accounts |
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: To set up SeaText for multiple Shopify domains, install the SeaText app on each store and connect each store’s domain to its own SeaText account via the dashboard. This article walks through the exact Shopify steps, the one-account-per-domain rule, trade-offs, limitations, and common follow-up questions.
To set up SeaText for multiple Shopify domains, install the SeaText app on each store and connect each store’s domain to its own SeaText account via the dashboard. This guide shows the exact Shopify steps and explains why the one-account-per-domain model matters.
| Criteria | Separate SeaText accounts per domain | Single store with multiple domains |
|---|---|---|
| Setup complexity | Repeat the install for each store. | Lower setup if supported, but SeaText links one account to one primary URL. Check with the vendor. |
| Ongoing maintenance | Manage one script and account per store. | Simpler if supported; verify that all domains report into one account. |
| Cost per domain | Each account has its own pricing plan. | One account may cost less, but only if multi-domain support exists. Check with the vendor. |
| Reporting clarity | Clean, separate reports per store. | Could mix traffic from multiple domains. Check with the vendor. |
| Best for | 3+ stores, client work, separate brands. | One store with a single primary URL and redirects. |
If you manage 3+ stores, use separate accounts. Otherwise consider a single store with multi-domain support, but first confirm that SeaText supports that setup.
SeaText links each AI account to a single primary URL. That URL is the main address SeaText uses to match visitors and measure results. If you connect two domains to one account, the system cannot tell which domain should receive the rewrite or which one produced the conversion.
This design keeps reporting clean. Each store’s traffic stays in its own account. Settings, product tags, translations, and AI agents also stay separate. For agencies managing client stores, that separation is essential.
The downside is more accounts to maintain. You need one account per domain, one script per store, and one set of settings per account. Plan for that before you start.
localhost are restricted for security reasons.*.shopify.dev preview URL.Repeat these steps for every store. Do not copy the same account snippet into multiple stores.
Go to seatext.com and create a separate account for each domain. Enter the real domain for that store when SeaText asks for the primary URL. This connection becomes the basis of your setup.
Log in to the Shopify store that matches that domain. In admin, go to Online Store > Themes.
Click Actions > Edit Code for the active theme. This opens the theme code editor.
In the file list, open the Layout folder and select theme.liquid.
Copy the JavaScript snippet from your SeaText account for this exact domain. Paste it into theme.liquid, then click Save.
SeaText also uses an HTML tag for product descriptions. Follow these steps:
product.liquid or product-template.liquid.{{ product.description }}.data- attribute.Preview a product page and check that the data- attribute appears in the HTML source. Use your browser’s developer tools to confirm.
Visit the real domain and confirm the page loads normally. Verify the SeaText script is present in the page source. Check a product page for the product description tag.
Create another SeaText account for the next domain. Get that account’s snippet, open the next store’s theme code, paste it, save, add the product tag, and test. Do not reuse a snippet from a previous store.
Shopify can connect multiple domains to a single store. This is useful for country or campaign domains. But SeaText links an account to a single primary URL. If you want one store and one SeaText account, choose one primary URL and use redirects from the other domains to that URL.
Check with the vendor whether Shopify Markets or multi-domain redirects are supported for your setup. This is not guaranteed by the standard SeaText account model.
SeaText restricts development URLs such as localhost for security reasons. Dynamic development domains like *.shopify.dev may not function properly because SeaText cannot reliably associate traffic with your account. Use a valid, real domain for staging and testing.
If multiple domains show the same content, search engines may split ranking signals. The standard fix is a 301 redirect to the primary domain. With SeaText, that primary domain is the one registered on the account. This keeps your SEO signals and SeaText reporting aligned.
Use a real domain. SeaText restricts localhost and may not work on dynamic development domains.
For the standard SeaText setup, yes. Each domain gets its own account and its own store. If you have one store with multiple domains pointing to it, choose one primary URL and check with the vendor.
Use 301 redirects from the extra domains to the primary domain. This is a Shopify setting or DNS-level redirect. After that, SeaText sees traffic on the primary URL.
Each account has its own pricing. Visit the SeaText pricing page for current plans. Budget for one plan per domain.
Confirm the store uses its own account’s snippet. Check that the domain is real and not a development URL. Inspect the page source for the script and the data- attribute.
Shopify Markets can create regional domains. SeaText’s standard model uses one primary URL per account. Check with the vendor to see whether Market domains can be handled under one account or need separate setup.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.