Seeing an “API connection error” in your SeaText Shopify dashboard means SeaText cannot authenticate with your Shopify store. The stored connection between the two systems is not valid, so Shopify rejects the API calls SeaText needs to make.

Quick fix: Go to SeaText settings, click Re-authenticate, and refresh the dashboard. Most connection errors clear immediately.

If the error returns, the cause is usually the primary URL, the account, or the code snippet in your theme. Use the steps below to find and fix it.

What the API connection error means

The error is a status message, not a full system failure. SeaText still loads in the dashboard, but it cannot complete the secure connection to Shopify. Without that connection, SeaText cannot read product data or push changes to your store.

Think of the connection as a locked door. The API connection error tells you the door is locked. Re-authentication gives SeaText a new key. Domain checks make sure SeaText is trying to open the right door.

The message can appear after a routine login, after a domain change, or after you edit the theme. It can also appear when the account linked to the store is not the one loading the dashboard.

How SeaText authenticates with Shopify

The integration starts with a SEATEXT AI account. Without an account, you cannot install the script. The official guide says the installation process is secure and the AI remains inert until you activate it.

To install, open your Shopify admin and go to Online Store, then Themes. Click the three dots next to the active theme and choose Edit code. In the Layout folder, open theme.liquid and paste the JavaScript snippet. Save the file.

That snippet is the starting point for the connection. It tells SeaText which website is making requests. The SeaText backend then uses the account credentials to call Shopify’s API.

Each SeaText account is tied to a single primary URL. If you need SeaText on multiple domains, create a separate account for each one. This is a deliberate security design. It also means the primary URL has to match the live store exactly.

Development URLs are restricted. The official guide says localhost is blocked. Dynamic development domains may not work because SeaText cannot reliably associate traffic with your account. Use a valid, real domain for the integration.

Common causes of the API connection error

The error usually comes from one of four things:

• Expired credentials. The saved connection can lose validity. Re-authentication refreshes it.
• Domain mismatch. The primary URL in SeaText does not match the live store domain. This often happens when you move from staging to production.
• Missing or edited snippet. If theme.liquid no longer contains the SeaText script, the backend cannot identify the store correctly.
• Wrong account. Using one SeaText account for multiple domains conflicts with the product model. Each website needs its own account.

Permission changes can also break the connection. If the integration loses the permissions it needs, API calls will fail. The dashboard will then show the error.

Diagnostic sequence: find the cause in four checks

Work through this order. It is quick and covers the most common failure points.

1. Open the SeaText settings page. Look for the account connection area and the Re-authenticate control.
2. Compare the primary URL. The URL in SeaText should match the live store domain exactly. Do not use a staging subdomain, localhost, or a temporary preview domain.
3. Verify the theme snippet. In Shopify, go to Online Store, Themes, Edit code, then Layout and theme.liquid. Search for the SeaText JavaScript code. If it is missing, add it again and save.
4. Check the account. Confirm the dashboard belongs to the account linked to the domain. If not, switch accounts or create a separate account for that domain.

After each check, refresh the dashboard. If the error clears, you have found the cause.

Step-by-step fix for the API connection error

Start with the fastest fix: re-authenticate.

Step 1: Re-authenticate. In the SeaText settings page, click Re-authenticate. This refreshes the stored connection. After the flow finishes, return to the dashboard and refresh the page. The error banner should disappear.

Step 2: Correct the domain. If the primary URL is wrong, edit it in the SeaText settings. Use the exact domain that is live in production. Remember that development URLs are blocked for security reasons.

Step 3: Restore the snippet. If the theme was updated or replaced, the snippet may be gone. Reopen theme.liquid and add the SeaText script. Save the file. Then test a product page to confirm the SeaText data attribute is present. That attribute is a small HTML marker SeaText uses to read the product description.

Step 4: Create separate accounts for separate domains. Do not try to manage a staging site and a live store with one SeaText account. The guide is clear: multiple domains require separate accounts.

Step 5: Confirm permissions. If the integration cannot access the product data it needs, Shopify will reject the API calls. Re-grant the needed permission if it was removed. Then run re-authentication again.

If these steps do not clear the error, contact SeaText support from the dashboard. Include a screenshot and the exact domain you are using.

Why ignoring the error hurts your store

The API connection error is not just a status message. It pauses every SeaText agent that depends on Shopify data.

SeaText markets 20 autonomous agents that work in real time. They are designed to increase conversion rate, recover ad spend lost to bot traffic, translate content across 125 languages, and optimize the visitor journey. The homepage describes those agents as active tools.

When the API connection fails, these agents cannot act. Product copy remains unchanged. Translations do not update. Headline rewrites do not fire. Bot detection and refund evidence workflows stall. Paid traffic keeps arriving, but the page cannot adapt to it.

For an ecommerce store, this means lost momentum. The longer the connection stays down, the longer the store runs without the optimization layer SeaText is supposed to provide.

Frequently asked questions

• Why does the error appear suddenly? The stored connection can expire, or the primary URL can become invalid. SeaText then cannot authenticate with Shopify.
• Will re-authenticating change my website? No. It only refreshes the backend connection. The front-end code stays in place.
• Can I use SeaText on a staging domain? Not with the production account. Development URLs are restricted. Create a separate SeaText account for the staging domain if you need it.
• What is the first thing I should check? The primary URL. If it does not match the live store, the API connection will keep failing.
• Do I need to reinstall the theme code? Only if the snippet is missing. Check theme.liquid first, then re-authenticate.
• How do I know the connection is working? The dashboard will stop showing the error. The active agents will resume their normal activity.
• Can support fix it for me? Yes. Use the support ticket in the SeaText dashboard. Include the exact URL and an error screenshot.

If SeaText AI is not appearing on your Shopify store, the culprit is almost always a theme setting that silently blocks third‑party scripts. The most common cause is the App Embeds setting in the Shopify Customizer being toggled off. Some themes disable app embeds by default, so you need to manually enable them. Below is a checklist of the exact settings to verify, along with explanations of why each setting blocks scripts, how to confirm the setting is the problem, and what trade‑offs you accept when you change it.

Comparison of Common Theme Settings That Affect Third‑Party Scripts

1. Check the App Embeds Section

Go to Online Store → Themes → Customize. In the theme editor, open the Theme Settings (usually a sidebar icon) and look for the App Embeds tab. Find SeaText in the list and make sure the toggle is set to On. If it is off, no app script will load. Why this blocks SeaText: Shopify’s app embed system only injects the script when the toggle is active. How to verify: After toggling on, reload the storefront and open the browser console; you should see a request to seatext.com. Trade‑off: Enabling app embeds may add a few milliseconds to page load, but the conversion lift from SeaText typically outweighs that cost.

2. Verify the Script Placement in theme.liquid

SeaText requires a JavaScript snippet to be pasted in the theme.liquid file. According to the official integration guide (source S1), you must: 1) Access your Shopify admin, navigate to Online Store > Themes, click Actions > Edit Code. 2) Open the Layout folder and click theme.liquid. 3) Paste the SeaText code near the top of the <head> section. 4) Click Save. Why this matters: The snippet registers the SeaText embed with Shopify; without it, the App Embeds toggle has nothing to activate. How to verify: View page source and search for seatext. If missing, re‑paste and save. Trade‑off: Editing theme code directly can be overwritten by theme updates; consider using a theme app extension if available.

3. Confirm the Theme Does Not Disable Third‑Party Scripts

Some Shopify themes include a “Disable third‑party scripts” or “Performance mode” toggle. This setting is often found in the theme's advanced settings or in the Customizer under Theme Settings → Performance. Turn it off if it is active. Why this blocks SeaText: The theme adds a CSP or removes script tags for any non‑first‑party domain. How to verify: Disable the setting, reload, and check the console for SeaText network requests. Trade‑off: Disabling performance mode may increase page weight slightly; monitor Core Web Vitals after the change.

4. Look for Content Security Policy Restrictions

Certain themes add a Content-Security-Policy header that blocks inline scripts. Check your theme’s layout/theme.liquid for any <meta http-equiv="Content-Security-Policy"> tag. If present, remove it or add seatext.com to the script-src directive. This is rare but can silently prevent loading. Why this blocks SeaText: CSP tells the browser to refuse scripts from unlisted origins. How to verify: Open the Network tab, filter by “blocked”, and look for a CSP violation referencing seatext.com. Trade‑off: Relaxing CSP reduces security posture; only add the specific domain you trust.

5. Ensure No Caching or Minification Interference

Some themes bundle scripts or use a minifier that strips inline JavaScript. If you see the SeaText code in the source but it does not execute, try disabling any “Minify JavaScript” or “Combine scripts” options in the theme settings. Also check that your CDN or caching app (e.g., Cloudflare, NitroPack) is not blocking the SeaText domain. Why this blocks SeaText: Minifiers can rename variables or remove comments that SeaText relies on; CDNs may cache an old version without the snippet. How to verify: Disable minification, purge CDN cache, and test in an incognito window. Trade‑off: Disabling minification increases JS payload size; consider a targeted exclusion for the SeaText snippet instead.

6. Test with a Minimal Theme

If you have gone through all the above and SeaText still does not load, temporarily switch to a default Shopify theme (e.g., Dawn). If the script loads, the issue is specific to your custom theme. Contact the theme developer with the list of settings you have checked. Why this helps: It isolates whether the problem is theme‑code or a platform‑level restriction. Trade‑off: Switching themes temporarily changes storefront appearance; do it during low‑traffic hours or on a duplicate theme.

Why SeaText AI Loading Matters for Conversions

SeaText deploys 20 autonomous AI agents that rewrite headlines, offers, and CTAs in real time to match each visitor’s search keyword, referral source, and reading behavior (source S2). When the script loads, it immediately begins analyzing dwell time, scroll depth, and friction points (source S3) and can lift conversion rates by 3‑5% or more (source S4). If the script is blocked, you lose all of that dynamic optimization, multilingual translation (up to 125 languages), bot‑click refund evidence, and personalized ABM experiences (source S7). In short, the script is the gateway to every revenue‑impacting feature SeaText provides.

Limitations of This Checklist

• Not all themes expose the same settings; some use different names (e.g., “Script Manager” instead of “App Embeds”).
• Settings described here are based on general Shopify theme practices and are not documented in the provided sources (S1–S7). Always consult your theme’s documentation or support.
• Third‑party apps (script managers, other AI assistants) can also inject CSP or minification rules that are not covered by theme settings alone.
• Server‑level CSP headers set by Shopify Plus or a headless setup cannot be changed from the theme editor.
• This checklist does not cover JavaScript errors thrown by other scripts that halt SeaText execution; use the browser console to diagnose those.

Key Facts About SeaText Integration

Frequently Asked Questions

Why is SeaText not showing in the App Embeds list?

Apps only appear in the App Embeds section after you have added the script to theme.liquid. If you have not done that, the embed will not show. Also, ensure you are using a supported theme (most modern themes work).

Can a third‑party app conflict with SeaText?

Yes, especially script managers or other AI assistants. Try disabling other apps one by one to see if SeaText loads. The most common conflicts come from apps that modify the theme.liquid head section.

Does the theme's “Lazy Load” feature affect SeaText?

Lazy loading applies to images and videos, not to JavaScript snippets in the head. SeaText should load regardless. However, if the lazy load plugin also delays all scripts, you may need to whitelist the SeaText domain.

What if the script is present but the console shows “blocked by CORS”?

This indicates a Content Security Policy issue. Check your theme for CSP headers and add seatext.com to the allowed origins. You may also need to update your script-src directive.

How long does it take for SeaText to activate after installation?

Once the script is saved and the App Embeds toggle is on, the AI activates immediately on the next page load. No delay.

What you’ll achieve

After these steps the SeaText AI widget on your Shopify store will display the most recent content, eliminating display glitches caused by old cached scripts.

Prerequisites

• Access to your Shopify admin panel.
• An active SeaText AI account (required to use the dashboard sync feature).
• A modern web browser with developer tools.

Why cached SeaText data causes display issues

SeaText AI changes your store’s content in real time based on visitor intent. This content is stored in multiple cache layers. When a cache holds old data, visitors see outdated headlines, offers, or product descriptions. This hurts conversion rates and makes your store look broken.

There are three main cache layers that can store stale SeaText data: the browser cache, the Shopify theme cache, and the SeaText server cache. Each layer acts independently. Clearing only one layer often leaves the problem unsolved.

For example, a hard reload clears the browser cache but does not touch the SeaText server cache. If you skip the server sync, the widget still loads the old AI response from SeaText’s servers. This is the most common reason why display issues persist after a simple refresh.

How browser cache vs. Shopify cache vs. SeaText server cache differ

Browser cache stores static files like JavaScript, CSS, and images on the visitor’s device. SeaText’s widget script is often cached here. A hard reload (Ctrl+F5 or Cmd+Shift+R) forces the browser to download the latest script from the server. This is fast but only affects one device.

Shopify theme cache holds compiled assets and Liquid templates. Saving any change in the theme editor (even without making edits) triggers Shopify to rebuild these files. This clears the theme cache. It ensures the SeaText code snippet is fresh. This step is optional but helpful if you modified the integration code.

SeaText server cache is the AI’s response cache. It stores the generated content for each visitor segment. The SeaText dashboard sync button (in Integrations > Shopify) clears this cache. After a sync, the widget receives new AI-generated content. This is the most important step for forcing the latest version of the widget output.

Source: SeaText integration documentation (S1) states that the code snippet is loaded from the SeaText servers, and the dashboard provides a sync function.

Step‑by‑step process

1. Hard‑reload your browser. Press Ctrl+F5 (Windows) or Cmd+Shift+R (Mac) while on any page of your store. This bypasses the browser cache and forces the latest scripts to load.
2. Clear Shopify theme cache (optional). In Shopify admin go to Online Store → Themes, click the three‑dot menu on your live theme, choose Actions → Edit code, then click Save without changes. Saving forces Shopify to rebuild its compiled assets.
3. Trigger a manual sync in the SeaText dashboard. Log into SeaText, navigate to Integrations → Shopify, and click the Sync now button. This clears the server‑side cache for the widget.
4. Refresh the store page again. Perform another hard reload to load the freshly synced widget.

When to use each cache‑clearing method

Use a hard reload when you are the only person testing changes. It is quick and works on your own device. But it does not fix the issue for other visitors.

Clear the Shopify theme cache after you edit the SeaText code snippet in the theme.liquid file. This ensures the new code is compiled and served to all visitors.

Use the SeaText dashboard sync whenever you update content in the SeaText AI dashboard. This is the only way to refresh the server cache. Without it, all visitors see the old AI responses. Do this after every major content update.

If you use a CDN or third‑party caching app, purge its cache after the dashboard sync. This ensures the CDN does not serve stale files.

How to verify the cache is cleared

• Open your store in an incognito/private window.
• Inspect the page source (right‑click → View source) and confirm the data‑seatext‑version attribute reflects the latest timestamp.
• Check that any recent copy changes you made in the SeaText dashboard appear on the live page.

Limitations and troubleshooting

SeaText dashboard sync may not work immediately. The sync button triggers a refresh, but the new content can take up to two minutes to propagate. Wait a minute, then hard reload.

Third‑party caching apps (like Cloudflare or a Shopify cache app) hold their own copies. You must purge those caches separately. The dashboard sync does not affect external caches.

Multiple domains require separate SeaText accounts. If you have a staging domain, create a separate account. The staging domain’s cache is independent. You must sync each account separately.

If the widget still shows old content after all steps, check the browser console for errors. A JavaScript error can prevent the widget from loading the new script. Common issues include ad blockers or script conflicts.

Remember: the SeaText server cache only stores AI responses. It does not affect product images or other static assets. If other content is stale, clear Shopify’s general cache or your CDN.

Frequently asked questions

How often should I clear the SeaText cache?

Only when you update content in the SeaText dashboard. There is no need to clear it on a schedule. The AI automatically updates content for each visitor based on the latest settings.

Will clearing the cache affect my store’s performance?

No. Clearing the cache does not remove any data permanently. It only forces a fresh load. Your store’s speed returns to normal after the first load.

Do I need developer skills to clear the cache?

No. The process uses simple browser shortcuts and a button in the SeaText dashboard. No coding is required.

What if the sync button is missing from my dashboard?

Ensure you have an active SeaText account and that your Shopify integration is connected. If the button is still missing, contact SeaText support. They can verify your integration status.

Additional tips

• If you use a CDN or third‑party caching app, purge its cache after the dashboard sync.
• Regularly repeat the sync after major content updates to keep the widget current.
• Test the widget in an incognito window after each sync to confirm the change is live.

To use SeaText AI on multiple domains, create one separate SeaText account for each domain. Each SeaText account is linked to a single primary URL, so there is no “add another domain” button inside one dashboard. You install that account’s JavaScript snippet on the matching website and repeat the process for each site.

This guide gives the exact steps, the verification check, and the limits you need to know before running multiple websites with SeaText.

Why this matters

SeaText's one-account-per-domain rule exists because each account is tied to a single primary URL for accurate traffic attribution. This design affects three common scenarios:

• Agencies managing client sites: Each client domain needs its own account so analytics, AI rewrites, and bot detection stay isolated per client.
• Businesses with staging and production domains: A staging domain (e.g., staging.example.com) requires a separate account from production (example.com) because dynamic development domains may not function reliably.
• Brands using regional domains: Separate accounts for example.com, example.co.uk, example.de ensure language-specific AI agents and conversion tracking align with each market.

Trying to share one account across these scenarios breaks the primary URL match, leading to misattributed traffic and unreliable AI actions.

What “managing multiple domains” means in SeaText

SeaText ties each account to one primary URL. That means one account equals one website. If you want to use SeaText on a development domain and a production domain, or on several client sites, you create a separate account for each domain.

The primary URL is the domain you associate with that account. SeaText uses that URL to match traffic to the account. When you install the snippet on your site, the account looks for that same domain.

You do not copy one snippet to many sites. Each snippet is tied to its own account and primary URL, so reusing a snippet on two websites will not give you accurate tracking on both.

Before you start

• A SeaText AI account for the first domain. If you don’t have one, create it first; installation requires it.
• A valid, real domain. Development URLs like localhost are restricted for security reasons.
• Access to edit your site’s code, such as the Shopify theme files or your site-wide header/footer area.

Step 1: Create a separate account for each domain

1. Create or log in to a SeaText account for the first domain.
2. Record which primary URL that account will serve.
3. Create another SeaText account for the second domain. Repeat until you have one account per website.

Using one account for multiple domains is not part of SeaText’s setup. The official instruction says: “you must create separate accounts for each domain.”

It helps to build a simple list that maps each domain to its account and snippet. This prevents you from accidentally installing the wrong snippet on the wrong site.

Step 2: Copy the JavaScript snippet from each account

After you log in to a SeaText account, go to the integration section for that account. Copy the JavaScript code that is shown there.

Important: copy the snippet from the account that belongs to the site you are installing on. Each snippet is linked to that account’s primary URL. If you mix up snippets, the traffic will be associated with the wrong account or may not be associated at all.

Step 3: Install the snippet on each website

For most websites, place the snippet in the site-wide header or footer so it loads on every page. For Shopify, the documented path is through the theme code.

1. Log in to Shopify admin.
2. Go to Online Store → Themes.
3. Click Actions → Edit code for your active theme.
4. Open the Layout folder and choose the file named theme.liquid.
5. Paste the SeaText JavaScript snippet where the integration instructions say to place it.
6. Click Save.

If your platform does not use theme.liquid, look for a global HTML file or a site-wide code injection area. The goal is the same: load the snippet on every page of that domain.

The installation process is secure, and the AI stays inactive until you activate it. That means you can add the snippet without changing your site content yet.

Step 4: Verify each domain connects to the right account

After saving, preview a page on that domain. Use your browser’s developer tools to view the HTML source and check that the data attribute described in the integration documentation is present. If it is missing, the snippet was not added correctly.

Then check your SeaText account for that domain to confirm traffic is being associated with the right primary URL. Repeat the same verification on every domain you set up.

This step matters because a snippet can be present in the code but still not send the right signal if the domain does not match the account. Always verify both the front-end and the account view.

Common mistakes to avoid

• Reusing one snippet on several domains. Each account is linked to a single primary URL, so the second site will not match.
• Using localhost. Development URLs are restricted for security reasons.
• Using dynamic development domains. They may not function properly because SeaText may be unable to reliably associate traffic with your account.
• Skipping verification. Always check the HTML source and the account, not just the front-end preview.
• Forgetting to update the account when you move from staging to production. Keep the primary URL in the account aligned with the real domain you are using.

Key facts for multiple domains

Limitations and when this advice does not apply

This process assumes you control the DNS and code for each domain, and that each domain is a separate website. If you are running one primary domain with many pages, you only need one account.

SeaText’s own documentation covers Shopify installation directly. For other platforms, you can follow the same site-wide snippet approach, but you should check the platform’s code editor or injection point.

Dynamic staging domains and localhost are outside the supported setup, so do not rely on them for testing. If you need a setup for wildcard domains, multiple subdomains under one account, or a large client network, check with SeaText because the official source instructions do not cover those cases.

Frequently asked questions

Can I add more than one domain to a single SeaText account?

No. Each SeaText account is linked to one primary URL. To cover multiple domains, create one account per domain.

What happens if I put the same snippet on two websites?

The account’s primary URL will only match one site. The other site’s traffic may not be associated with your account reliably.

Can I use localhost for testing?

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

Do I need a separate account for a staging domain?

If the staging domain is a real, valid domain and you need SeaText to track it separately, yes. Be aware that dynamic development domains may not function properly.

Where do I add the snippet in Shopify?

Go to Online Store → Themes → Actions → Edit code, open Layout → theme.liquid, paste the snippet, and save. Then preview the page and inspect the HTML source for the expected data attribute.

Does installing the script change my site immediately?

No. The AI remains inert until activated, so adding the snippet is safe and does not alter your content by itself.

Short answer: multiple domains, separate accounts

Yes, you can use SeaText on more than one domain. But each domain needs its own account. One account works with one primary URL. If you have two websites, create two accounts.

The official documentation 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. Each SEATEXT AI account is linked to a single primary URL.'

So the answer is yes — multiple domains are fully supported. Just set up one account per domain.

How a primary URL is tied to your account

Your primary URL is the main web address linked to your SeaText account. When you install SeaText, you copy a JavaScript code snippet from that account and paste it onto your site. SeaText uses that domain to associate traffic and activate agents.

Because the account is locked to one URL, all settings, reports, and agent activity stay scoped to that site. No data leaks between domains. This design keeps each site's analytics clean and your security tight.

Why can't you change the URL later? The source material does not describe a way to reassign a primary URL. If you need to move an account to a new domain, contact SeaText support first.

Step-by-step: setting up a second domain

Follow these steps to add SeaText to another website:

1. List every website that needs SeaText.
2. Create one SeaText account for each domain. The documentation says: 'To use SEATEXT AI on several websites, create one account for each website.'
3. For each account, copy that account's JavaScript code. The code appears in the integration section of your account dashboard.
4. Install the code on the matching domain. If your site uses Shopify, open your Shopify admin and go to Online Store > Themes. Click Actions > Edit Code.
5. In the Edit Code page, find the Layout folder and open theme.liquid. Paste the JavaScript snippet before the closing tag. Save your changes.
6. For product descriptions, locate the product template (usually product.liquid or product-template.liquid). Wrap the product description output with the SeaText tag. The source pack shows the exact code structure.
7. Use a real, valid domain for every installation. Do not use localhost. Development URLs are restricted for security reasons.
8. Activate the agents you want. The AI stays inactive until you turn it on. This ensures your site's content is not changed without your permission.

Each account has its own unique JavaScript snippet. Do not copy the code from one account to another domain. That would mix traffic data and break the association.

How traffic and reporting stay isolated per account

SeaText links every visitor session to the domain where the account's JavaScript is installed. Because each account has a different snippet, traffic from Site A goes to Account A, and traffic from Site B goes to Account B.

Reporting is completely separate. You see conversion rates, keyword matches, and agent activity only for that one domain. No cross-contamination. This isolation is critical for paid ad campaigns. If you run Google Ads, you need to know which keyword drove a conversion on which site. Separate accounts give you that clarity.

If you ignored the rule and used the same account on two domains, reports would blend data from both sites. You would not know whether a conversion came from a visitor on Site A or Site B. That makes optimization impossible.

One account vs. multiple accounts: a practical comparison

If you manage a single website, one account is enough. If you run several distinct businesses or need a development environment separate from production, use multiple accounts. Each account operates independently, so you can tailor agents and settings per site.

Edge cases and limitations

Changing a primary URL

The source pack does not state whether you can change the primary URL after signup. If you need to move an account to a new domain, contact SeaText support before assuming it is possible. Do not simply install the same code on a different domain — that mixes traffic.

Subdomain and staging setups

Staging sites often live on a subdomain like staging.example.com. The source material does not clarify whether a subdomain counts as the same primary URL. If your staging site is on a separate domain (e.g., staging-example.com), it needs its own account. For subdomains, check with SeaText support. Mixed-traffic risk: if you install the same account on both a production domain and a staging subdomain, visitor data from both will merge. That confuses your reports.

Mixed-traffic risks

Ignoring the one-account-per-domain rule leads to mixed data. You might see a conversion and not know which site caused it. Ad campaigns become harder to optimize. Refund claims for bot traffic become unreliable because you cannot trace the invalid session to a specific domain. Always use separate accounts for separate domains.

Development URLs are restricted

localhost and dynamic development domains are not allowed. SeaText cannot reliably associate traffic with your account when the domain changes or is not publicly accessible. Use a real, valid domain even for testing. If you must test locally, use a public staging domain with a separate account.

FAQ

Can I use one SeaText account for my main site and a test site?

No. If the test site is on a different domain, it needs its own account. Use a separate account for each domain.

What if I only want to run SeaText on a staging site?

You still need a valid real domain. Localhost is restricted. Dynamic development domains may not work. Create a separate account for the staging domain.

Can I install the same JavaScript code on two sites?

No. Each SeaText account has its own code linked to one primary URL. Use the code from the account made for each specific domain.

Do I need a separate login for every domain?

Yes, because you need a separate account. The documentation says to create one account for each website.

Can I change the primary URL later?

The source pack does not say. Contact SeaText support for the current policy on changing the primary URL.

Does SeaText support multiple websites at all?

Yes, multiple websites are supported — just not on the same account. Create one account per website.

To add a second domain, create a separate SeaText AI account for that domain and verify the new domain from that account. Each SeaText AI account is linked to a single primary URL. That is why you cannot simply add another domain to your existing account.

Option Comparison: One Account vs. Separate Accounts

Who Option A fits: It does not fit any SeaText AI setup, because the account model does not support it.

Who Option B fits: Anyone who needs SeaText AI on more than one domain, including development and production pairs.

Overview

SeaText AI links each account to one primary URL. This design keeps the script, verification, and traffic data tied to a single website. If you want to use SeaText AI on a second domain, you need a separate account for that domain.

This article explains why the rule exists, how the account-domain relationship works, and how to complete the setup. It also covers common mistakes, limitations, and useful follow-up questions.

Why Each SeaText AI Account Is Tied to One Domain

SeaText AI states that each account is linked to a single primary URL. The rule exists so the service can associate traffic with the right account.

When SeaText AI reads a visitor session, it needs to know which website it is working on. If one account could serve many domains, the service could not reliably tell which domain generated the traffic.

This matters because SeaText AI reacts to each visitor and each page. It rewrites headlines, offers, and CTAs. It also tracks results by page, keyword, and version. That data only makes sense when it is attached to one known domain.

The same logic applies when you use multiple websites. For each website, you create one account. The source pack says: “To use SEATEXT AI on several websites, create one account for each website.”

The Complete Step-by-Step Process

Follow these steps to add a second domain. They assume you already have a valid domain and access to its DNS or hosting settings.

1. Prepare the second domain

Make sure the domain is public and reachable. SeaText AI does not support development URLs such as localhost for security reasons.

You also need control over DNS records or file uploads. That control is required for verification.

2. Create a separate SeaText AI account

Go to the SeaText AI website and create a new account. Do not try to add the second domain to your existing account.

Use an email address you can access. You will need it to receive verification instructions and account updates.

If you have a development domain and a production domain, create a separate account for each. Do not share one account between them.

3. Get your script snippet

After account creation, SeaText AI gives you a JavaScript snippet. Copy it exactly as provided.

For Shopify, open Online Store → Themes → Edit code. Find the layout file called theme.liquid. Paste the snippet there and save.

For other platforms, add the snippet to every page where SeaText AI should run. The installation process is secure, and the AI remains inert until activated.

4. Complete domain verification

SeaText AI needs to confirm that you control the domain. Follow the on-screen instructions. They may include adding a DNS record or uploading a verification file.

Verification is required before the domain can be used as an active site.

5. Confirm the domain appears as an active site

After verification succeeds, check your dashboard. The new domain should appear in your list of active sites.

You can also inspect your live page. View the page source and confirm the SEATEXT script is present. A data- attribute should appear after integration.

Domain Verification and What Happens After

Verification proves that you control the domain. It also links the new account to the correct primary URL.

Once the script is installed, open the page in a browser and use developer tools to inspect the HTML source. Confirm that the SEATEXT script is present.

After integration, a data- attribute should appear. That attribute helps confirm the script is active on the page.

The script remains inactive until you activate it. This protects your website content during setup.

After activation, SeaText AI can start reading visitor behavior. It may then adapt copy, test variants, translate content, or run other agents you enabled.

Common Mistakes and How to Avoid Them

Trying to add a second domain to one account

This fails because one account is linked to one primary URL. Create a separate account instead.

Using localhost or temporary URLs

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

Using dynamic development domains

Dynamic development domains may not function properly. SeaText AI may not reliably associate traffic with your account on those domains. Use a stable public domain.

Forgetting to verify the domain

Verification is required before active use. Without it, the domain will not appear as an active site.

Installing the script only on one page

For full coverage, add the snippet to the site layout or all pages. On Shopify, theme.liquid is the standard place.

Checking for the wrong markers

Inspect the source for the SEATEXT script. After integration, a data- attribute should appear. Do not rely on an invented domain-specific marker.

Limitations and Security Restrictions

SeaText AI restricts some URLs by design. Here is what the source pack says.

Development URLs such as localhost are restricted for security reasons. You must use a valid, real domain.

Dynamic development domains may not function properly because SeaText AI may be unable to reliably associate traffic with your account.

This means you should avoid frequently changing subdomains, preview URLs, or temporary hosting links. They may not work even if they are publicly reachable.

Each account remains limited to one primary URL. This is the core security and data boundary.

If you need SeaText AI on multiple websites, create one account for each website. This applies to development and production domains as well.

Frequently Asked Questions

Can I use the same email for two domains?

Each domain needs its own separate SeaText AI account. The source pack does not say that you must use different email addresses.

For reliable setup, use an email address you can access for each account. Check with the vendor if your email provider or account rules create a conflict.

Do I need separate accounts for development and production domains?

Yes. The source pack says that if you need to use SeaText AI on multiple domains, including a development domain and a production domain, you must create separate accounts for each domain.

Do not share one account across both. Each account is linked to a single primary URL.

What counts as a valid domain?

A valid domain is a real, publicly reachable domain that you control. It must not be localhost or a restricted development URL.

Dynamic development domains may not work reliably. Choose a stable domain for testing if you need SeaText AI to associate traffic correctly.

When will the new domain be active?

The domain becomes active after you complete verification. SeaText AI says verification is needed before active use.

Check your dashboard for the domain to appear as an active site. Also confirm the script is present in the page source.

Can I switch a domain later?

The source pack does not describe a domain-switching process. It states that each account is linked to a single primary URL and that you should create separate accounts for additional domains.

If you need to change domains, contact SeaText AI support or check the vendor’s documentation. Do not assume you can move an account freely.

Key Facts

Does SeaText AI Support Subdomains for Different Stores?

Yes. SeaText AI treats subdomains as separate domains. If you run store1.example.com and store2.example.com you need a dedicated SeaText account for each subdomain.

Each account links to one primary URL. The platform does not allow a single account to cover both example.com and shop.example.com.

How SeaText AI Handles Subdomains

When you add a subdomain SeaText creates a distinct website entry. The integration code you copy from the dashboard is unique to that account.

According to the Shopify integration guide, multiple domains require separate accounts because each account is linked to a single primary URL.

This architecture prevents cross‑domain data mixing. AI agents such as the Google Ads Landing Page Agent or the Ecommerce Product Copy Agent operate only on the domain they are configured for.

Why This Matters for Multi‑Store Setups

Separate accounts give each store its own:

• AI agents and settings (CRO optimizer, translation agent, personalization agent)
• Analytics and conversion tracking
• Integrations with Shopify, Google Ads, Meta Ads, or other platforms
• Billing and subscription plan

Isolation helps when you test new features on a staging subdomain before rolling out to production. It also keeps regional stores such as us.example.com and eu.example.com independent.

Setting Up SeaText AI on a Subdomain

1. Create a new SeaText account for each subdomain. Visit seatext.com and sign up.
2. Copy the integration code from the account dashboard. The code is unique to that account.
3. Install the code on your subdomain. For Shopify follow the theme.liquid steps in the Shopify Integration guide. For other platforms paste the code just before the closing tag.
4. Activate the AI agents you need for that store (Google Ads Agent, WooCommerce Agent, etc.).
5. Test that agents work by previewing a page on the subdomain and checking for the data‑attribute in the HTML source.

Key Facts About SeaText Subdomain Support

Source: SeaText Shopify Integration page

Limitations and Considerations

The main limitation is that you cannot manage multiple subdomains under one SeaText account.

• Separate logins and billing for each subdomain.
• Settings and agents must be configured individually.
• Cross‑store analytics or unified dashboards are not available inside SeaText.

This separation protects data. A configuration error on one store does not affect others. It also lets you assign different team members to different stores.

If you manage many subdomains consider consolidating under a single domain with subdirectories (example.com/store1, example.com/store2). SeaText supports subdirectories within one account because the primary URL covers the whole domain.

Comparison: Subdomains vs Subdirectories

Choose subdomains when stores need completely independent branding, compliance, or billing. Choose subdirectories when you want centralized management and lower overhead.

Billing and Plan Management Across Accounts

Each SeaText account carries its own subscription. Pricing details are on the pricing page. You pay per account, not per domain group.

If you need volume discounts contact sales. The platform does not automatically aggregate usage across accounts.

Security, Compliance, and Development Environments

SeaText restricts development URLs such as localhost for security reasons. Dynamic development domains generated by some hosting platforms may not work reliably.

Use a static, publicly resolvable subdomain (e.g., staging.example.com) for testing. The integration guide explicitly warns that localhost and similar addresses are blocked.

Team Collaboration and Access Control

Because each subdomain has its own account you can invite different users to each account. This lets a regional team manage eu.example.com while another team manages us.example.com.

There is no built‑in cross‑account role management. You must configure permissions separately in each dashboard.

Migration, Cloning, and Workarounds

SeaText does not provide a one‑click clone of an account. To replicate settings you must manually recreate agents, integrations, and custom rules in the new account.

Export any custom dictionaries or translation memories from the old account and import them into the new one if the feature supports it. Check the documentation for current import/export capabilities.

Frequently Asked Questions

Can I use the same SeaText account for example.com and blog.example.com?

No. Each subdomain is considered a separate domain. You need a separate account for blog.example.com.

What about subdirectories like example.com/blog?

Subdirectories are part of the same domain. A single SeaText account for example.com covers example.com/blog automatically.

Do I have to pay for each subdomain separately?

Yes. Each subdomain requires its own subscription. Check the pricing page for current plans.

Can I use a staging subdomain like staging.example.com for testing?

Yes, if it is a real domain. Dynamic development domains may not work reliably. Use a static subdomain.

How do I transfer settings from one subdomain account to another?

There is no built‑in cloning feature. You must manually reconfigure each agent and integration for the new account.

Does SeaText support wildcard subdomains?

Not directly. Each subdomain needs its own account and code snippet. Wildcard setups are not supported.

Your AI-generated content stays on the account that created it. When you add a new domain to SeaText, the content from your original domain is not copied, moved, or overwritten. SeaText links each account to a single primary URL, so a new domain needs its own account. That new account starts clean.

In short: old content stays, new content grows separately. That is by design, not an accident.

Diagnosis: why it might look like your content disappeared

If you added a new domain and now see no AI-generated content, check the account first.

• Symptom: The new domain shows no descriptions, translations, or rewritten headlines.
• Likely cause: The new domain is not linked to the account that generated the content.
• Check 1: Confirm which primary URL is attached to your SeaText account.
• Check 2: Confirm whether you created a separate account for the new domain.
• Check 3: Confirm the domain is a real, valid domain, not localhost or a dynamic development URL.

If you ignore the one-account-per-domain rule, you might install SeaText on the new domain and see nothing appear. The system may not associate traffic with that account, and the content you expect will not show up.

How SeaText treats domains and accounts

SeaText expects one account per primary URL. The integration guide says: 'If you need to use SEATEXT AI on multiple domains, you must create separate accounts for each domain.' That is the supported setup, not a workaround.

You have two practical choices:

• Create a separate account for the new domain. This gives clean tracking and keeps original content untouched.
• Try to reuse an existing account. This is not supported for multiple domains and risks misattributed traffic.

See the SeaText integration guide for the exact steps.

Types of AI-generated content affected

SeaText can generate several kinds of content on your site. The types include product descriptions, translations, rewritten headlines, and calls to action. None of that content is moved, copied, or overwritten when you add a new domain.

• Product descriptions and names. Agents like the Ecommerce Product Copy Agent optimize product names, descriptions, and CTAs.
• Translations. The Website Translation Agent translates pages, headlines, buttons, and offers into up to 125 languages.
• Rewritten headlines and offers. Agents rewrite headlines and offers to match keywords, campaigns, and visitor intent.
• Calls to action. CTAs can be rewritten for each paid click, visitor source, or reading context.

Each of these is tied to the account and primary URL that produced it. A new domain has its own account and starts with none of that history.

Why the separation exists

Separate accounts protect content and keep tracking reliable. If one account served many domains, SeaText could not tell which domain a visit came from. That would make traffic reporting and content association muddy.

The separation also keeps your existing content safe. The installation process is secure, and the AI remains inert until activated. Installing a script does not rewrite, delete, or move anything by itself.

What to do when you add a new domain

Follow this order:

1. Create a separate SeaText account for the new domain. Do not reuse the account tied to the old domain.
2. Use a real domain. Localhost is restricted. Dynamic development domains may not connect.
3. Install the SeaText script on the new domain. The integration guide shows where to paste the code snippet.
4. Activate the agents you need. The AI remains inert until activated, so nothing changes until you turn it on.
5. Leave the original account alone. It continues to serve the content it already generated.

If the new domain runs on Shopify, the integration guide also explains where to place the tag in your theme and product template.

Step-by-step Shopify setup for a new domain

The Shopify integration guide gives exact file locations. Use these steps after you create the new SeaText account.

1. Log in to Shopify admin. Go to Online Store and then Themes.
2. Open the theme editor. Click the three dots next to your active theme and select Edit code.
3. Add the SeaText tag to theme.liquid. In the file list on the left, open the Layout folder, then open theme.liquid. Paste the SEA text code snippet where the guide instructs, then click Save to preserve your changes.
4. Place the tag in the product template. Still in Edit code, locate the file that renders the product description, typically product.liquid or product-template.liquid. Wrap the product description output with the tag.
5. Verify the placement. Save your changes and preview a product page to ensure the description displays correctly. Use browser developer tools to inspect the HTML source and confirm the data attribute is present.

Verification matters. A tag that is missing or placed in the wrong file will not generate the content you expect. The saved change should be visible in the page source before you activate any agents.

Trade-offs: why one account per primary URL

One account per primary URL protects attribution. Attribution tells SeaText which domain generated a visit, which content changed, and which agent earned a result.

If you reuse one account across domains, traffic becomes blurred. A visitor on the new domain may be recorded against the old domain, or the account may not associate with the new domain at all. Content reports become unreliable. The AI may not know which site to rewrite or translate.

Another risk is accidental overwrite. The source pack states that shared accounts are not supported. Even if a script installs cleanly, the account still points to the original primary URL. The new domain is not a supported target, and the content you expect may never appear.

The supported path is simple: create a separate account, install its tag, and leave the original account untouched. This costs a few minutes and keeps each domain's data clean.

Hypothetical scenario: adding a second store

This example is hypothetical, but it follows SeaText's account rules.

Imagine you sell coffee at northsidecoffee.com and you open a second shop at southsidecoffee.com. Your first account has already generated product descriptions, translations, and page copy. When you add southsidecoffee.com, none of that content carries over automatically. You create a separate SeaText account for the new domain, install the script, and activate the agents you want. The new domain starts fresh. Your northside content stays on northsidecoffee.com.

That is the cleanest mental model: each domain is its own content world.

Key facts at a glance

Limitations and exceptions

The biggest limitation is the one-account-per-domain rule. You cannot attach two primary domains to one SeaText account. Trying to do so can break traffic association and content tracking.

Development domains are a common trip point. Localhost is blocked for security reasons. Dynamic development domains may not work because SeaText might not be able to reliably associate traffic with your account. If you need a test site, use a stable real domain.

This article covers adding a new domain. It does not cover changing your primary domain or merging accounts. The source pack does not describe a migration path, so treat any domain replacement as a separate setup.

Terms you might see

• Primary URL: the single domain that a SeaText account is linked to.
• Development domain: a test URL, usually localhost or a staging site.
• Dynamic development domain: a URL that changes, such as a temporary preview link.
• Activation: the point where you turn on the AI agents after installing the script.

Frequently asked questions

Will my existing AI-generated content be deleted if I create a new account?

No. The original account stays with its primary URL and its content. A new account for a new domain does not erase anything.

Do I need a separate SeaText account for each domain?

Yes. Each SeaText account is linked to a single primary URL, so multiple domains mean multiple accounts.

Can I use one account for development and production domains?

No. You must create separate accounts. Development URLs like localhost are restricted, and dynamic development domains may not work reliably.

What happens if I install SeaText on a new domain with my old account?

The account is already linked to the original primary URL, so the new domain may not associate correctly with that account. The supported path is a new account for the new domain.

Will installing the script change my content?

No. The AI remains inert until you activate it, so the installation by itself does not modify content.

Does this article cover changing my primary domain?

No. Changing the primary domain is a separate process. The source pack does not describe a migration or domain-switch path, so treat it as a new setup decision.

What should I do if the new domain is a development or staging URL?

Use a stable, real domain instead. Localhost is restricted, and dynamic development domains may not work because traffic cannot be reliably associated with the account. Create the new account with a valid domain before testing.

Why One SeaText Account Cannot Serve Multiple Domains

SeaText is built around a strict rule: each account is linked to exactly one primary URL. The integration script you install on your site reports back to that single account. When the same script runs on a second domain, SeaText cannot tell which site the traffic belongs to.

This causes visible problems fast. Translations written for one brand can appear on another. Headline rewrites tested on a staging site can leak to your live homepage. Conversion-rate agents can swap CTAs across sites that target different audiences.

The fix is simple but non-negotiable: create one SeaText account for every domain you want to manage. This includes production sites, staging sites, development environments, subdomains you treat as separate businesses, and unrelated brand sites under the same company.

How Account-to-Domain Binding Actually Works

When you sign up, you set a primary URL inside the account settings. SeaText stores that URL as part of the account identity. The JavaScript snippet you receive contains a unique account reference. When a visitor loads a page, the snippet reads that reference and ships page data, keyword data, and reading telemetry to the matching account.

If you paste the same snippet on two domains, both sites send data into the same bucket. SeaText then treats every visitor as if they came from the primary URL you registered. Analytics get blurred. A/B variants trained on one audience get served to another. Translation memory gets shared, which is dangerous when the two brands use different tone, pricing, or compliance language.

The system also checks the domain that loads the page. If the domain does not match the account's primary URL, behavior is unreliable. Localhost is blocked. Dynamic tunneling URLs (like ngrok subdomains that change every session) often fail to associate traffic at all.

Common Mistake: Sharing One Account Across Environments

The most common mix-up we see is the staging-to-production copy-paste. A team installs SeaText on a staging site, runs tests, likes the results, then copies the same snippet into the live theme.

From that moment, two things go wrong:

• Staging experiments bleed into production. A headline variant still being tested shows up on the live site.
• Production traffic pollutes staging data. Real customers get attributed to a test environment, skewing reading telemetry.

The same mistake happens with brand sites. A company running two stores under different names installs one snippet to save time. Within days, the translation agent rewrites both sites with the same tone. One brand ends up sounding like the other.

Another frequent error is treating subdomains as part of the parent domain. blog.example.com and shop.example.com look related, but to SeaText they are different URLs. If you want separate content rules, headlines, or translations per subdomain, create a separate account for each.

Step-by-Step Setup for Multiple Domains

What You Need Before You Start

• One SeaText account per domain (sign up at seatext.com)
• Access to edit the HTML, theme, or template files on each domain
• A valid, real domain for every environment (no localhost, no dynamic tunneling URLs)
• A separate email or distinct account label so you can tell accounts apart

Steps

1. Create the first account. Sign up and set the primary URL to your first domain. Copy the integration snippet the dashboard shows you.
2. Install the snippet on the first domain. For Shopify, go to Online Store, then Themes, click the three dots next to your theme, choose Edit code, open the Layout folder, and paste the snippet inside theme.liquid before the closing </body> tag. For other platforms, follow the matching guide and paste before </body>.
3. Create the second account. Use a different email or a clear account name like "Brand A Production" or "Brand A Staging". Set its primary URL to the second domain.
4. Install the second snippet on the second domain. Repeat the same theme or template edit, but use the new snippet from the second account.
5. Verify each domain. Open each site in a browser, view the page source, and confirm the data- attribute SeaText adds is present. This proves the right account is active on the right domain.
6. Repeat for every additional domain. Every staging site, dev site, brand site, and language site gets its own account and its own snippet.

Decision Criteria: When You Need a Separate Account

Not every site needs its own SeaText account. Use this checklist to decide.

• Different brand voice or audience. If two sites target different buyers or use different tone, separate accounts keep translation and CRO agents from cross-contaminating.
• Different environment. Production, staging, and development always need separate accounts. Real traffic should never mix with test traffic.
• Different subdomain with independent content rules. If blog.example.com and shop.example.com run separate content strategies, give each its own account.
• Different compliance or language requirements. Sites serving regulated industries or different language markets need isolated translation memory.

If you run a single site with multiple sections, you do not need multiple accounts. SeaText agents can manage different sections inside one account tied to one URL.

Practical Scenarios and How to Handle Them

Scenario 1: Two brands under one company

You run Brand A at branda.com and Brand B at brandb.com. Create two SeaText accounts. Each account gets its own translation memory, CRO experiments, and reading telemetry. The Translation Agent will not leak Brand A's tone into Brand B's pages.

Scenario 2: Production plus staging

Your live site is example.com. Your staging site is staging.example.com. Create two accounts, one for each URL. Never copy the production snippet into staging, or vice versa. When you finish testing on staging, remove the snippet before promoting the theme.

Scenario 3: Multilingual sites on subdomains

You serve es.example.com and fr.example.com. If you want Spanish and French content to evolve independently, give each subdomain its own account. If you want one unified translation memory across both, you can keep one account and treat language switching as a single-domain problem, but only if both subdomains are part of the same business logic and you accept the shared memory trade-off.

Scenario 4: Local development before launch

You build a new site at localhost:3000. SeaText will not work on localhost. Set up a real dev domain like dev.example.com, register it as a separate account, and test there. Move the snippet to production once you launch.

Limitations and Edge Cases

SeaText's one-account-per-domain rule is strict on purpose. There is no official workaround. The system will not let one account serve multiple distinct primary URLs.

Wildcard domains are not supported. Each distinct hostname needs its own account.

Dynamic development URLs are unreliable. If your tunneling tool gives you a new hostname every session, SeaText cannot bind traffic to your account consistently. Use a fixed dev domain instead.

The integration snippet is safe to install and the AI stays inactive until you turn it on, so you can stage and test without changing what visitors see.

Installation usually takes under one minute for standard platforms, but verification, environment setup, and per-domain account creation can add time when you manage many sites.

Frequently Asked Questions

Can I use one SeaText account on a staging site and a live site?

No. Create two accounts, one for staging and one for production. Using one account causes test content to leak into your live site.

What happens if I accidentally use the same account on two domains?

SeaText may apply translations, headlines, or CTAs trained on one domain to the other. Remove the snippet from the wrong domain, then create a new account for that domain.

Do subdomains need separate accounts?

Yes, if you want independent content, CRO, or translation rules. blog.example.com and shop.example.com are separate URLs to SeaText.

Can I use the same email to create multiple accounts?

Yes. Use a clear account name per domain so you can tell accounts apart in the dashboard.

Does SeaText support wildcard domains?

No. Each distinct hostname needs its own account and snippet.

Will SeaText work on localhost?

No. Localhost and similar development URLs are restricted. Use a real dev domain with its own account.

How long does installation take?

Under one minute for most platforms, plus the time to create and verify a separate account per domain.

Is the integration snippet safe to install?

Yes. The AI stays inert until you activate it, so installation does not change what visitors see.

SeaText AI ties every account to one primary URL. There is no option to manage several domains from the same account. If you need SeaText AI on more than one domain, create one account for each domain.

The real limitation: one account, one domain

SeaText AI does not cap the number of domains you can own. Instead, each SeaText AI account can handle exactly one primary domain. That means the limit is not about how many domains you can manage total, but how many domains one account can manage.

If you run two websites, you need two SeaText AI accounts. If you run ten websites, you need ten accounts. The source documentation confirms: "Each SEATEXT AI account is linked to a single primary URL."

So the direct answer to the question is: yes, there is a limit per account — one domain each. But there is no stated maximum number of accounts, so the total number of domains you can cover depends only on how many accounts you create.

Why SeaText AI links each account to one domain

SeaText AI optimizes pages, rewrites copy, and attributes behavior to a specific site. That work only makes sense if the traffic data is associated with the correct domain.

The documentation warns that SeaText AI might be unable to reliably associate traffic with your account when a development domain is dynamic. The same logic applies across different domains. If one account tracked two separate sites, reporting and agent decisions would blur together.

Separate accounts keep each domain's sessions, conversions, and bot-detection evidence clean and auditable. You can compare performance across domains without mixing the numbers.

How to set up SeaText AI for multiple domains

You can manage multiple domains by giving each one its own account and its own installation code. The setup is the same for each site.

1. Create a SeaText AI account for the first domain.
2. Copy the JavaScript installation code from that account.
3. Add the code to the domain's site. For Shopify, go to Online Store, then Themes, then Edit Code, and paste the snippet into theme.liquid.
4. Save the changes and test the page to confirm the script loads.
5. Repeat steps 1–4 for every additional domain, using a fresh account for each one.

Do not reuse the same account across two domains. The script is tied to the account's primary URL, so reuse will not work reliably.

How to verify each domain is connected

After you paste the SeaText AI code, check that the page still loads normally and that the script appears in the source.

1. Open the page in your browser.
2. Right-click and choose Inspect or View Source.
3. Search for the SeaText AI installation code or the data attribute mentioned in the integration guide.
4. Save a test page and confirm the code is present.
5. Repeat this check for every domain you attach to an account.

For Shopify, the documentation specifically mentions verifying the data- attribute is present in the HTML source after editing the product template.

Common mistakes to avoid when adding domains

• Reusing the same account code on a second domain. It will not associate traffic correctly.
• Using localhost as a development URL. SeaText AI restricts localhost for security reasons.
• Relying on dynamic development domains. They may not function because traffic cannot be tied to your account.
• Forgetting to test after installation. Always preview the page and inspect the source to confirm the code is present.
• Creating a new account but forgetting which URL it is linked to. Keep a record of the primary URL for each account.

How this limitation affects development and staging workflows

If you follow a typical website workflow, you have a development site, a staging site, and a production site. With SeaText AI, each of those requires its own account, because each has a distinct URL.

You might be tempted to install the production script on a staging site temporarily. That creates a risk: the script expects to receive traffic for its primary URL, and staging traffic may not match the account correctly.

The safer path is to use separate accounts for development and production, or to run SeaText AI only on the production domain and keep development testing outside the script.

Restrictions and security you should know

• Localhost is restricted. You must use a valid, real domain.
• Dynamic development domains may not function properly because SeaText AI cannot reliably associate traffic.
• Each account is linked to one primary URL. For a development domain and a production domain, use separate accounts.

Key facts from the SeaText AI documentation

What this means for your day-to-day workflow

Plan your SeaText AI accounts the same way you plan your domains. Each site needs its own account, its own installation code, and its own settings.

If you run a staging site, treat it as a separate domain with a separate account. Do not point a valid production domain at a local host or a dynamic subdomain and expect reliable data.

Keep a simple list of which account belongs to which domain. That makes it easier to manage billing, agent settings, and reports as you add new sites.

A quick decision framework for adding more domains

Not every domain needs SeaText AI right away. Start with the sites that generate or receive the most paid traffic, because those are where keyword-aware rewriting and bot refunds have the most impact.

Add a separate account for each production domain that runs paid ads, sells products, or needs translation. Defer development and testing domains until you can give them a valid, real URL that SeaText AI can track reliably.

Frequently asked questions

Can I use one SeaText AI account for two different websites?

No. Each account is linked to one primary URL, so you need one account per website.

Is there a maximum number of SeaText AI accounts I can create?

The documentation does not state a maximum number of accounts. If you need many domains, you can create an account for each one.

Can I use a subdomain as the primary URL?

The documentation does not specify subdomains. Treat a subdomain as a separate URL and confirm with SeaText before relying on it.

Can I test on localhost and then move to production?

No. Localhost is restricted for security reasons. Use a valid, real domain for testing, or use a separate real development domain.

Do I need to install the code separately for each domain?

Yes. You copy the installation code from each account and add it to that account's assigned domain.

How to Remove a Domain

Remove a domain from SeaText AI by navigating to Settings > Domains, selecting the domain you want to remove, and clicking Remove. This action severs the link between your SeaText AI account and that website, stopping all AI agents from running on the domain.

Prerequisites

• You must have an active SeaText AI account with the domain you want to remove.
• Only the account owner (or an admin) can remove the domain.
• Removing a domain is permanent and cannot be undone from the same account.
• Ensure you have exported any historical data or custom settings you wish to keep before proceeding.

Step-by-Step Instructions

1. Log in to your SeaText AI account.
2. Click the Settings icon in the top navigation bar.
3. Select Domains from the left menu.
4. Find the domain you want to remove in the list.
5. Click the Remove button next to that domain.
6. Confirm the action when prompted. The domain is removed immediately.

What Happens After Removal

After removing the domain, all SeaText AI agents stop working on that website. The tracking script becomes inactive, and no new data is collected. Any historical data associated with the domain remains in your account for a limited time, but you can no longer use the account to optimize that domain. According to SeaText AI documentation, each account is linked to a single primary URL, so removal effectively deactivates the account's connection to that site. You should export reports, copy variants, and custom configurations before removal if you need them for reference or migration.

Key Facts About Domain Management

Limitations and Considerations

Removing a domain does not delete your SeaText AI account itself. The account remains active but without any domain assigned. You can later add a new domain to the same account, but this is only possible if the account is not already linked to another domain. If you need to switch domains entirely, you may need to create a new account for the new domain and delete the old account.

There is no way to temporarily pause a domain; removal is permanent for that account. To preserve settings, consider creating a new account and transferring any custom configurations manually before removal. Switching domains versus adding a new domain: if you remove a domain and immediately add a different one to the same account, the account must have no domain assigned at that moment. If you attempt to add a new domain while the old one is still attached, the system will prevent it. Manual preservation of settings involves exporting copy variants, agent configurations, and historical reports, then reapplying them in the new account.

Common Mistakes When Removing a Domain

One common mistake is removing a domain without exporting historical data first. Once removed, you lose access to the dashboard for that domain, and while data may be retained for a period, you cannot retrieve it through the interface. Another mistake is assuming you can re-add the same domain to the same account later. The system prevents re-adding a previously removed domain to the same account; you must create a new account for that domain. Users also forget to update the SeaText AI script on their website after removal, leaving dead code that can affect page load performance. Finally, some users try to use a single account for multiple domains by removing and adding domains repeatedly, which violates the one-account-per-domain policy and can lead to account suspension.

Frequently Asked Questions

Can I undo a domain removal?

No. Once removed, you cannot re-add the same domain to the same account. You would need to create a new account for that domain.

Does removing a domain delete my account?

No, the account remains but becomes inactive since no domain is attached. You can delete the account separately if needed.

What happens to my AI agents and settings?

All agents stop running on the removed domain. Custom settings, copy variants, and historical data may be retained for a period but cannot be used without an active domain.

Can I remove a domain and add a different one to the same account?

Yes, but only if the account currently has no domain assigned. If you remove a domain, you can immediately add a new domain to that account.

How long does it take for the removal to take effect?

Removal is instant. The SeaText AI script on your website will stop working within minutes as the servers update.

Can I transfer my account to another domain?

You cannot transfer an account to another domain directly. Each SeaText AI account is permanently linked to a single primary URL. To use SeaText AI on a different domain, you must create a new account for that domain and manually recreate any desired settings.

Will removing a domain affect my other SeaText AI accounts?

No. Each SeaText AI account operates independently. Removing a domain from one account does not impact other accounts you may own. However, if you use the same email for multiple accounts, you will still access each account separately.

Direct Answer: Can You Transfer SeaText Settings?

Yes, you can duplicate settings from an existing domain when creating a new one. SeaText does not support moving an account from one domain to another. Each account is tied to one primary URL. To use SeaText on a new domain, you create a separate account and manually rebuild the configuration.

Why Each SeaText Account Is Tied to One Primary URL

SeaText reads visitor behavior and rewrites content in real time. The service must know which traffic belongs to which account. The documentation states: "Each SEATEXT AI account is linked to a single primary URL." This one-to-one link keeps analytics, session data, and AI rewrites clean. If one account served two domains, the AI would mix up customizations such as CRO settings, translation preferences, and ad-campaign rewrites.

The same rule applies to multiple websites. The guide says: "Using SEATEXT AI on Multiple Websites To use SEATEXT AI on several websites, create one account for each website." This rule is the authoritative source for all domain-related limits.

What You Can Reuse When Setting Up a New Domain

You do not lose the product capabilities. SeaText includes agents for CRO optimization, website translation, Google Ads landing page rewriting, bot protection, and more. When you create a new account, you can activate the same agents again. However, there is no export or clone feature. You must manually note which agents were active and any custom rules such as translation languages or keyword-specific headline changes. Then you recreate those choices in the new dashboard.

Step-by-Step: Manually Duplicate Settings to a New Account

Follow these steps to replicate your configuration on a new domain:

1. List every active agent in the old account (CRO Optimizer, Translation Agent, Google Ads Agent, etc.).
2. Record any custom rules: target languages, keyword rewrite rules, bot protection thresholds, personalization settings.
3. Create a new SeaText AI account for the new primary URL. The integration guide says: "Before you can install the script, you need a SEATEXT AI account."
4. Copy the JavaScript snippet from the new account's dashboard.
5. Add the snippet to the new domain's HTML. For Shopify, go to Online Store > Themes > Actions > Edit Code, open Layout > theme.liquid, paste the code, and save.
6. Preview the site and verify the script loads using browser developer tools.
7. In the new dashboard, activate each agent from your list and reapply the recorded custom rules.
8. Test key pages to confirm rewrites, translations, and tracking work as expected.

This process works for staging-to-production moves, rebrands, or launching a second store.

Development vs. Production Domains: Special Considerations

Many users ask about transferring settings because they have a staging site and a live site. SeaText treats them as two different primary URLs. You need a separate account for each. The documentation warns: "Development URLs, such as localhost, are restricted for security reasons." A local address like http://localhost:3000 will not work. Also, "Dynamic development domains may not function properly" because SeaText might not reliably associate traffic with your account. Use a real, stable domain for testing.

Common Mistakes and How to Avoid Them

• Trying to use one account on two domains. The one-account-per-domain rule prevents this.
• Assuming a domain name change automatically updates the SeaText account. You must create a new account.
• Testing on localhost or temporary preview URLs. These are restricted or unreliable.
• Skipping the manual replication checklist. Without it, agents and rules may be missed.
• Deleting the old account before verifying the new one works. Keep the old account until the new setup is confirmed.

FAQ

Does SeaText offer an export or clone feature for account settings?

No. The documentation does not mention an export or clone feature. You must manually recreate settings.

Can I use a single SeaText account for a development domain and a production domain?

No. The guide says you must create separate accounts for each domain.

Will my settings transfer automatically if I point my domain to a new site?

No. The account remains linked to the original primary URL. No automatic transfer occurs.

What should I do if I need the same agents on a new domain?

Create a new account, then manually activate the same agents and configure the same rules.

Direct answer: one SeaText account per domain

To manage multiple domains with SeaText, you must create a separate SeaText account for each domain. This account‑per‑domain setup is the most useful feature because it provides isolated analytics, independent SEO settings, and independent agent activation. Each account links to a single primary URL (Source S1).

Decision guide: single account vs. separate accounts

Below is a quick comparison to help you decide which option fits your situation.

Decision rule: If you manage two or more domains, create one SeaText account per domain.

How to set up multiple SeaText accounts

1. Log in to SeaText and click “Create account”. Enter the exact domain you want to track. SeaText will link this account to that primary URL (Source S1).
2. Copy the unique JavaScript snippet shown in the account dashboard.
3. Paste the snippet into the <head> of the target website’s HTML. Save and publish.
4. Repeat steps 1‑3 for every additional domain you own.

Do not reuse the same snippet on another domain. The script will only record traffic for the URL it is tied to, and using it on a different site will corrupt data (Source S1).

Installing the snippet for each account

SeaText’s snippet is a small <script> tag. It loads the AI agents only after the page loads, so it does not slow down the user experience. Follow these steps for each account:

• Open the website’s theme editor (e.g., Shopify → Online Store → Themes → Edit code).
• Locate the main layout file (often theme.liquid or header.html).
• Insert the snippet just before the closing </head> tag.
• Save and verify that the HTML contains a data-seatext-id attribute matching the account ID.

After installation, SeaText remains inert until you activate agents from the dashboard.

Configuring agents per account

Each account has its own agent list. You can turn on any of the 20+ agents independently:

• SEO Agent – sets keyword targets, local SEO, and content recommendations for that domain.
• Google Ads Optimization Agent – rewrites landing‑page copy in real time for each ad keyword.
• Translation Agent – translates pages into up to 125 languages.
• Bot Protection Agent – detects and logs bot traffic for refund claims.

Because agents are activated per account, you can run the SEO Agent on a blog site while only enabling the Bot Protection Agent on a high‑traffic e‑commerce store.

Billing, analytics, and reporting separation

Each account is billed separately. Choose a plan that matches the traffic volume of that domain. SeaText’s dashboard shows conversion rate, traffic growth, and ad‑spend recovery per account, so you can compare performance without manual filtering.

Analytics are stored only for the primary URL of the account. Development URLs such as localhost are blocked for security reasons, and dynamic development domains may not work reliably (Source S1). Use a real, publicly reachable domain for testing, then create a separate account for the production site.

Limitations and edge cases

The account‑per‑domain model works best when each domain serves a distinct audience. Subdomains (e.g., blog.example.com) are considered part of the same primary URL and share the same account. If you need separate data for subdomains, contact SeaText support for guidance.

SeaText does not currently offer bulk account creation or a multi‑domain dashboard. Managing dozens of domains means handling multiple logins and separate invoices.

Attempting to install the same snippet on two domains will cause mixed data and broken agent behavior. Always use the unique snippet from the account that matches the domain (Source S1).

Frequently asked questions

Do subdomains require a separate SeaText account?

Subdomains are covered by the primary URL of the account. If you need isolated data for a subdomain, you must create a separate account and use a distinct domain.

Can I use a development domain like localhost?

No. Development URLs are restricted for security reasons. Use a real domain for testing and create a separate account for the production site (Source S1).

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

The snippet will only report data for the domain it is linked to, causing mixed analytics and unreliable agent activation. Install the unique snippet from each account.

Can I transfer settings from one account to another?

SeaText does not provide an automated transfer tool. You must manually configure agents and SEO settings in each new account.

Is billing per domain or per account?

Billing is per account. Since each domain needs its own account, you pay per domain.

Will the same SEO settings apply to all my domains?

No. SEO settings are stored per account, so each domain can have its own keyword targets, local SEO configuration, and content strategy.

Next steps

Now that you understand why a separate SeaText account per domain is essential, you can start creating accounts for each of your sites.

Why Separate Accounts Matter

SeaText AI ties its AI agents, analytics, and traffic attribution directly to the primary URL of each account. This design ensures that every visitor interaction is correctly matched to the right domain. When you keep each domain in its own account, the data stays clean and the security controls work as intended.

If you try to mix multiple domains inside a single account, the system cannot reliably tell which traffic belongs to which site. This causes data conflicts, breaks attribution reports, and may prevent the SeaText script from running at all. Keeping accounts separate protects the accuracy of your conversion data and the performance of your AI agents.

The platform enforces a single-primary-URL restriction on every account. This means each account can only be linked to one main domain. This rule is not a workaround but a core part of how SeaText AI validates traffic, manages security, and delivers results. Understanding this early saves you from setup failures later.

How to Set Up a Blog Domain

To run SeaText AI on a separate blog domain, you must sign up for a new account using the blog's URL as the primary domain. Each account is independent, so you will manage it through its own dashboard. Think of each account as a standalone workspace for that specific domain.

Once the account is created, copy the JavaScript snippet from the blog domain's account dashboard. Then paste that snippet into the <head> section of your blog's theme. On Shopify, this means editing the theme.liquid file inside the Layout folder. On other platforms, open the header file and insert the code in the same place.

After saving the changes, verify that the data- attribute appears in the page source. You can check this using your browser's developer tools. Once verified, activate the AI agents you need, such as translation, CRO, or chat. The same integration steps apply to every domain, so the process is repeatable and straightforward.

Technical Architecture of Multi-Domain Management

Each SeaText AI account operates as an independent unit. It holds its own configuration, agent settings, analytics data, and billing relationship. The architecture is deliberately separated so that no domain can interfere with another. This isolation also improves security because each account validates traffic only for its own primary URL.

The single-primary-URL restriction is the backbone of this architecture. When you create an account, SeaText AI binds it to one specific domain. All traffic, bot detection, and agent actions are scoped to that domain. If you add a second domain, the system has no way to associate it with the first account, so a new account is required.

Development URLs such as localhost are blocked for security reasons. SeaText AI cannot reliably associate traffic from temporary or local addresses with your account. Dynamic development domains may also fail because the system needs a stable, publicly reachable URL to function correctly. Always use a live, fully qualified domain before setting up SeaText AI.

Trade-Offs: Separate Accounts vs Single-Account Management

Running separate accounts for each domain gives you clean data isolation and accurate analytics. Every domain gets its own reports, its own agent behavior, and its own billing. The downside is that you manage multiple dashboards and pay for each domain individually. There is no built-in way to merge accounts or share configurations across them.

A hypothetical single-account management approach would simplify billing and let you toggle agents across domains from one place. However, SeaText AI does not currently offer this. The platform's architecture treats each domain as a separate site by design. Until the company adds cross-domain management features, separate accounts remain the only supported method.

The trade-off comes down to control versus convenience. Separate accounts give you precise control over each domain's setup, but they require more administrative effort. If you run two or three domains, the extra work is manageable. If you run many domains, you may want to request multi-account management features from the SeaText AI team.

Practical Use Cases for Multiple Domains

One common setup is an ecommerce store paired with a content blog. The store handles transactions and the blog drives organic traffic. Running SeaText AI on both lets you translate product pages and blog posts, optimize conversions on the store, and analyze reading behavior on the blog. Each domain gets agents tuned to its specific goals.

International subdomains are another strong use case. A brand might run shop.example.com and blog.example.com as separate primary URLs. Even though they share the same root domain, SeaText AI treats each subdomain as a distinct primary URL. You need a separate account for each subdomain to ensure proper traffic attribution and agent activation.

Staging versus production environments also benefit from this structure. You might run SeaText AI on a production domain while using a staging domain for testing changes. Because development URLs are blocked, you would set up the production account first and use it as the reference. The staging domain would need its own account only if it is a real, publicly reachable URL.

Advanced Configuration and Shared Settings

SeaText AI does not currently offer a shared-settings panel across multiple accounts. Each account stores its own configuration independently. If you want the same agents active on both domains, you must manually replicate the selections in each account. This includes choosing translation languages, CRO settings, and chat configurations.

Cross-domain tracking is not built into the platform. Because each account is tied to a single primary URL, analytics data stays within that account. If you need unified reporting across domains, you would need to export data from each account and combine it externally using your own analytics tools.

Billing consolidation is also not supported at this time. Each domain account follows its own pricing plan and generates its own invoice. If you are on a paid plan, you will receive separate bills for each domain. Some teams request consolidated billing from SeaText AI, but as of now, each account is billed independently.

Common Pitfalls and Troubleshooting

The most common mistake is trying to reuse the same SeaText AI account for multiple domains. This triggers the single-primary-URL restriction and prevents the script from running on the second site. If the script fails to load, check that you are using a separate account for each domain. Create a new account and install the snippet again on the affected site.

Another frequent issue is using a development or temporary URL. SeaText AI blocks localhost addresses and may not work with dynamic development domains. If your script does not activate, confirm that the domain is fully qualified and publicly reachable. Switch to a live URL before proceeding with the setup.

Sometimes the script appears to load but agents do not activate. This usually happens when the data- attribute is missing from the page source. Double-check that you pasted the snippet into the <head> section and saved the theme file. Use your browser's developer tools to inspect the HTML and confirm the attribute is present. If the issue persists, review the account dashboard for any activation errors.

Limitations and Requirements

SeaText AI requires one account per domain. You cannot share an account across multiple sites. This rule applies to subdomains as well; each subdomain counts as a separate primary URL and needs its own account. There is no technical limit to how many domains you can run, but each one requires its own account and billing.

Only fully qualified, publicly accessible domains are accepted. Development URLs such as localhost are restricted for security reasons. Temporary or dynamic URLs may not function properly because SeaText AI needs a stable domain to associate traffic with your account. Always verify that your domain is live before starting the setup.

Each domain on a paid plan follows its own billing cycle. There is no shared or consolidated billing across accounts. If you upgrade or change plans on one domain, it does not affect the plans on other domains. Keep this in mind when budgeting for multiple domains.

FAQ

• Do I need to pay for each domain separately? Yes. Each domain account follows its own pricing plan. If both your main store and blog are on paid tiers, you will receive separate bills for each account.
• Can I copy settings from one account to another? You can manually replicate agent selections, translation languages, and CRO settings, but each account stores its own configuration independently. There is no built-in clone or export feature.
• What if I use a subdomain instead of a separate domain? Subdomains count as separate primary URLs. Even if your store is at shop.example.com and your blog is at blog.example.com, you still need a new account for the blog subdomain.
• Is there a limit to how many domains I can run? No technical limit exists, but each domain requires its own account and billing. Manageability becomes the practical constraint as you add more domains.
• Why is my script not loading on the blog domain? The most common cause is using the same account for both domains. Create a separate account for the blog, install the snippet in the <head> of the blog theme, and verify the data- attribute in the page source.
• Can I use SeaText AI on a localhost or staging URL? No. Development URLs such as localhost are blocked for security reasons. You must use a real, publicly reachable domain for SeaText AI to function correctly.
• Does SeaText AI support cross-domain tracking between accounts? Not at this time. Analytics data stays within each account. You would need to export and combine reports externally if you want unified tracking across domains.
• How do I manage multiple accounts efficiently? Keep a spreadsheet or internal wiki that lists each domain, its account credentials, the plan tier, and the billing cycle. This helps you track settings, renewals, and agent configurations across all domains.
• Will adding a blog domain slow down my main site? No. Each account operates independently. The script on your blog domain runs separately from the script on your main domain, so there is no performance impact on either site.
• Can I switch a domain from one account to another? There is no direct transfer tool. You would need to create a new account for the domain and reinstall the script. Plan your account structure before committing to a domain setup.

For deeper guides on integration and agent configuration, visit the relevant page on the client website.

Symptoms of Domain Issues in SeaText

When you use SeaText on more than one domain, the symptoms are usually clear. The AI may not appear on one site. Changes made in one account may seem to affect another domain. Visitor traffic or conversion data may show up in the wrong place. You may see an invalid URL error.

These symptoms are signals of a configuration problem. SeaText links each account to one primary URL. If the account and the domain do not match, SeaText cannot associate traffic with the right account.

Why this matters: a mismatch makes your data unreliable. You cannot tell which domain produced the result. You might optimize the wrong page or miss a conversion problem. The fix starts with a simple diagnostic order.

Diagnostic Order: Step-by-Step Troubleshooting

Follow this sequence in order. Do not skip directly to reinstalling code. The account-to-domain mapping is the most likely cause and the easiest to verify.

1. Confirm separate accounts. Log in to your SeaText dashboard. Count how many accounts you have. Each domain needs its own account. If one account is used on two sites, that is the root cause.
2. Check the primary URL. Open the account settings and look at the primary URL. It must match the domain where the code is installed. Include the full hostname. This means the string in the account and the address in the browser should look exactly alike.
3. Inspect the integration code. Copy the JavaScript code from the SeaText account. Confirm that the same code appears on every page of that domain. On Shopify, this is usually done in theme.liquid.
4. Use a real, public domain. Development URLs such as localhost are restricted for security reasons. A localhost test will not work as a valid domain.
5. Avoid dynamic development URLs. Some hosting providers create temporary URLs for previews. SeaText may not be able to associate traffic with those dynamic addresses.
6. Recheck after each fix. Save the account change, update the code, clear the cache, and test in an incognito window.

Why this order works. The first steps cost a few seconds and remove the most common causes. Reinstalling code is important, but it will not help if the account is wrong. A logical sequence saves time and prevents repeated installations.

Root Causes and Their Fixes

Cause 1: One Account Used for Multiple Domains

The official SeaText integration instructions say that each account is linked to a single primary URL. If you need SeaText on multiple domains, you must create separate accounts for each domain.

When one account sends traffic from two sites, SeaText cannot reliably decide which domain the visitor came from. Data becomes mixed, and optimization stops working correctly.

Fix: create a new account for the second domain. Use the account dashboard to generate its own integration code.

Cause 2: Integration Code Is Missing or Misplaced

The code snippet is the bridge between the page and the account. If it is missing, the AI will not activate.

Fix: copy the code from the correct account and place it in the site-wide layout file. For Shopify, paste it into theme.liquid. Save the file and test again.

Cause 3: Development or Localhost URLs

Development URLs are restricted for security reasons. Localhost is a common example. Dynamic development domains may also fail because SeaText cannot reliably associate their traffic.

Fix: use a valid, real domain. If you need a staging environment, choose a stable public domain and give it its own account.

Cause 4: Primary URL Does Not Match the Site

Every SeaText account is linked to one primary URL. If the URL in the account is different from the domain where the code sits, the connection is broken.

Fix: update the primary URL to the exact domain you are using. Then reinstall the integration code from that account.

Installing SeaText on Shopify: Exact Steps

Shopify is a common setup. The source integration page gives clear steps. Here is the full process.

1. Log in to your Shopify admin.
2. Go to Online Store and choose Themes.
3. Find the active theme and click the three dots icon.
4. Select Edit code.
5. Open the Layout folder and click theme.liquid.
6. Paste the SeaText JavaScript code.
7. Click Save.

Before you can install, you need a SeaText AI account. You can create one on the SeaText website. The installation process is secure. The AI remains inert until it is activated.

Why theme.liquid? This layout file loads on every page of the Shopify store. Placing the code there means the integration is site-wide instead of limited to one page.

If you manage multiple Shopify stores, repeat these steps for each store. Do not use the same code from one account on another store. Each account has its own code because each account is linked to its own domain.

Recommended Setup for Multiple Domains

The arrangement that works depends on your situation. The table below shows practical patterns.

Decision criteria are simple. If the URL is a separate website, it needs a separate account. If the URL is a development domain, it may not work at all. If the URL is real and public, use it as the account's primary URL.

Consider a team with two stores on different domains. If they use one account, the AI cannot know which visitors belong to which store. Traffic from both sites will enter the same report. The fix is two accounts and two code snippets. Each snippet is installed only on its own domain.

The same logic applies when you need a production domain and a development domain. Create two accounts. Do not install one code on both. The development account will still need a real domain because localhost is restricted.

Limitations and Escalation Path

SeaText's model is simple but strict. These are the main limits to remember:

• An account is linked to one primary URL.
• Development URLs, such as localhost, are restricted.
• Dynamic development domains may not function.
• You cannot use one account on multiple websites.

These limits protect data quality. They also mean you should plan your domain architecture before installing the code.

If you have followed every step and the issue remains, check the official documentation. The integration page points to https://seatext.com/documentation-ai-scope for additional details. You can also use the SeaText website to find the latest support options.

One final check: confirm that the AI is actually activated for the account. The code is inert until activated. A code that is present but not activated will not change your site.

Frequently Asked Questions

Why does each domain need its own SeaText account?

Each account is linked to a single primary URL. Separate accounts let SeaText associate traffic with the correct domain. This keeps conversion data clean.

Can I test on localhost?

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

Can I use one integration code on two websites?

No. The code comes from an account, and that account is tied to one primary URL. Create one account for each website.

What should I do if my staging domain is dynamic?

Dynamic development domains may not function. SeaText cannot reliably associate traffic with an address that changes. Use a stable, real domain.

Where do I find my integration code?

Log in to SeaText and open the integration page. Copy the JavaScript code shown there for that account.

Is SeaText active as soon as I paste the code?

The AI remains inert until it is activated. The installation is secure, but the system must be turned on for the account.

Further Reading

Official sources for this troubleshooting guide:

• SeaText Shopify Integration
• SeaText Documentation: AI Scope
• SeaText Website

SeaText AI ties every account to a single primary URL. If you want to run the platform on more than one domain, you must create a separate account for each one. The total cost equals the per-account price multiplied by the number of domains. There is no bundled subscription that covers multiple domains.

This per-account model is a deliberate architectural choice. It keeps each domain isolated for security, tracking, and agent configuration. The trade-off is linear cost growth. If you operate three websites, you need three accounts. A development or staging domain counts as a separate domain and requires its own account.

Quick comparison: separate accounts vs. single account

How SeaText AI handles multiple domains

Each SeaText AI account links to one primary URL. That URL is the website where you install the JavaScript snippet. The AI agents on that account only operate on that domain. To use the same agents on a second domain, you must create a second account and install the snippet there.

The source pack states: “Each SEATEXT AI account is linked to a single primary URL. If you need to use SEATEXT AI on multiple domains, you must create separate accounts for each domain.” This rule cannot be bypassed. It is a core part of the architecture.

Development URLs such as localhost are restricted for security reasons. Dynamic development domains may not function properly because SeaText AI cannot reliably associate traffic with your account. You must use a valid, real domain for each account.

Why the per-account model matters for cost

The primary cost driver is the number of domains you need to manage. There is no discount for adding more domains to an existing account. Cost grows linearly: N domains = N account fees. A main site, a staging site, and a second brand site require three accounts.

Because pricing is per account, you cannot reduce cost by grouping domains under one subscription. The only way to lower per-domain cost is to choose a lower-priced account tier if one exists. Check the current pricing page for available plans and their per-account rates. The homepage and several landing pages link to a pricing page and mention a free one-month pilot trial, but specific plan prices are not published in the source pack.

Practical scenarios for multi-domain setups

Agencies managing client sites need one account per client domain. Each client’s data, agents, and analytics stay isolated. This simplifies compliance and reporting.

Businesses running multiple brands (e.g., brandA.com, brandB.com) need separate accounts. Each brand gets its own agent configurations, translation settings, and CRO experiments.

Development, staging, and production environments each count as a separate domain. You need an account for dev.example.com, staging.example.com, and www.example.com. This ensures test traffic does not pollute production analytics.

International sites on separate country-code domains (example.de, example.fr, example.jp) each require an account. The Translation Agent can run on each, but configuration and reporting remain separate.

Decision criteria for multi-domain budgets

Count every distinct registered domain you plan to use. Include development, staging, and any microsites.

Estimate the per-account price from the current pricing page. Multiply by the domain count. This is your baseline monthly cost.

Factor in management overhead. Each account requires separate login, agent activation, and snippet installation. Agencies may need team access controls per account.

Evaluate security needs. The per-account model provides natural isolation. A compromise on one domain does not expose data from others.

Consider analytics requirements. Separate accounts give clean, per-domain conversion reports, reading telemetry, and agent performance data.

Check for volume discounts. The source pack does not mention any. Contact SeaText sales if you manage many domains.

Key facts about SeaText AI and domains

Limitations and when this advice applies

The per-account rule applies to every SeaText AI agent, including the Google Ads Agent, Translation Agent, CRO Optimizer, Bot Protection Agent, and all others listed on the homepage and blog pages. It does not change based on the plan or feature set you choose.

Subdomains (e.g., blog.example.com and shop.example.com) may be treated as part of the same primary domain if they share the root domain. The source pack does not clarify this. Check with SeaText support before assuming subdomains are covered.

Wildcard domains or multi-domain SSL certificates do not change the account requirement. Each distinct primary URL needs its own account.

This advice applies to anyone managing multiple websites: different brands, separate markets, development and production environments, or client sites. If you plan to use SeaText AI on more than one domain, budget for one account per domain.

Frequently asked questions

Can I use one SeaText AI account for multiple domains?

No. Each account is linked to a single primary URL. You must create a new account for each additional domain.

Is there a discount for multiple accounts?

The source pack does not mention any volume discount. Check the pricing page or contact SeaText for current offers.

What about subdomains – do they count as separate domains?

Subdomains under the same root domain may or may not require separate accounts. The source pack does not specify. Verify with SeaText support before setting up.

How do I add a second domain?

Create a new SeaText AI account for that domain, then install the JavaScript snippet on the new website. Follow the same steps as for the first domain.

Can I use a wildcard domain to cover multiple subdomains?

The source pack does not mention wildcard support. It is likely not supported. Use separate accounts.

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

The snippet is tied to one account and one primary URL. Using it on another domain may cause tracking issues or errors. Always create a new account for each domain.

Does the free trial apply to each new account?

The Google Ads landing page advertises a free one-month pilot trial. It is not clear if the trial applies per account or per organization. Check with the vendor.

Can I manage multiple accounts from a single dashboard?

The source pack does not describe a multi-account dashboard. You likely log in to each account separately. Check with the vendor for agency or enterprise management features.

Verdict: Use separate SeaText accounts for each domain. SeaText ties an account to one primary URL, so a single account cannot reliably serve multiple sites.

What the SeaText Account Model Means

SeaText AI accounts are bound to a single primary URL. This binding is fundamental to how the platform operates. When you create an account, you specify the primary domain where SeaText will run. The platform uses that primary URL to associate traffic, AI-generated copy, and analytics with the correct site.

If you try to use the same account on a different domain, SeaText detects the mismatch. According to the official integration documentation, each SeaText account links to one primary URL. The system validates that the JavaScript snippet on your page matches the registered domain. If the domains do not match, SeaText blocks the request or records data incorrectly.

You cannot share a single billing profile across unrelated domains without creating separate accounts. The one-domain-per-account rule is enforced at the platform level. This means you must create distinct accounts even for related sites, such as separate country-code domains or subdomains for different brands.

Why It Matters for Your Business

The one-domain-per-account model affects three key areas of your marketing operations:

• Accurate reporting: Each account logs visitor behavior only for its domain. This gives you clean conversion data without cross-contamination. If you mixed domains under one account, the analytics would show blended data that does not reflect any single site's performance.
• Security compliance: Development and staging domains are restricted. Using separate accounts prevents accidental exposure of test data to production environments or to visitors on live sites.
• Feature isolation: AI agents such as the CRO optimizer, translation agent, and bot protection operate independently per account. A change on one site will not affect another site if they have separate accounts.

For agencies managing multiple client websites, this model means each client gets their own isolated environment. Client A's traffic data never mixes with Client B's data. Each client's AI agents respond only to visitors on their own domain.

How SeaText Account Binding Works

When you install SeaText, you paste a unique JavaScript snippet into your website's code. This snippet contains an account token that identifies your SeaText account. The installation process follows these steps:

1. Create a SeaText account and specify your primary domain during signup.
2. Copy the JavaScript code provided in your SeaText dashboard.
3. Add the code to your website's theme.liquid file in the Layout folder.
4. Save the changes and verify the snippet loads correctly.

SeaText validates the token against the primary URL stored in your account. If the snippet is placed on a domain that does not match the registered primary URL, the validation fails. The platform then either blocks the request entirely or logs the data under an error state. In both cases, the AI features remain inactive for that mismatched domain.

This validation happens server-side. You cannot override it by editing the JavaScript snippet or changing settings in your account dashboard. The only way to use SeaText on a new domain is to create a new account registered to that specific domain.

Step-by-Step Multi-Domain Setup Walkthrough

When you need SeaText on multiple websites, follow this workflow for each domain:

Step 1: Create Separate Accounts

Go to the SeaText signup page for each domain you want to cover. During each signup, enter the specific domain as your primary URL. For example:

• Account 1: primary URL = example.com
• Account 2: primary URL = example.co.uk
• Account 3: primary URL = staging.example.com

Each account requires its own email address and login credentials. You cannot reuse the same email for multiple accounts on the same domain.

Step 2: Install the Snippet on Each Domain

For each website, copy the unique JavaScript snippet from the corresponding SeaText account. Install it in your website's code using the standard integration method:

• Log in to your Shopify admin or website CMS.
• Navigate to the Themes section.
• Click Actions, then Edit Code.
• Locate the theme.liquid file in the Layout folder.
• Paste the snippet just before the closing tag.
• Click Save.

Step 3: Verify Each Installation

After saving, preview a page on each domain to confirm the snippet loads. Check your browser's developer tools to ensure the data-seatext attribute appears in the HTML source. If the snippet does not load, check for JavaScript errors or domain mismatch warnings in your SeaText dashboard.

Step 4: Configure AI Agents Per Account

Once installed, activate the AI agents you need for each domain independently. Account 1 might run the CRO Optimizer and Translation Agent. Account 2 might run Bot Protection and Google Ads Agent. Each account's agent settings are independent.

Domain-to-Account Mapping Example

Here is how a realistic multi-domain setup might look:

• Production site (main brand): yoursite.com – Account A with CRO Optimizer, Translation Agent, and Bot Protection activated.
• UK market site: yoursite.co.uk – Account B with localized content and UK-specific bot protection.
• Staging environment: staging.yoursite.com – Account C with test configurations. This account is used only internally and is restricted from public traffic.
• Development environment: localhost or dev.yoursite.local – SeaText blocks these URLs for security. You must use a valid, publicly accessible domain for testing.

Note that dynamic development domains may not function properly. SeaText documentation states that the platform might be unable to reliably associate traffic with your account if you use non-standard development URLs. For reliable testing, use a subdomain pointed to a staging server with a real domain name.

Cost and Management Breakdown

Using separate accounts has direct cost implications:

• Subscription cost: Each account requires its own subscription. If you have three domains, you pay for three subscriptions. Check the SeaText pricing page for current rates and any volume discounts.
• Billing management: You receive separate invoices for each account. This can simplify expense tracking if each domain belongs to a different client or business unit.
• Login overhead: You must maintain multiple login credentials. Consider using a password manager to track credentials for each SeaText account.
• Renewal tracking: Each account has its own renewal date. Set calendar reminders to avoid lapses in coverage for any domain.

The trade-off is between higher total cost and full compliance. Attempting to save money by using one account across multiple domains will result in validation errors and inactive AI features. The money saved is not worth the loss of functionality.

Decision Framework

Use this framework to decide how to organize your SeaText accounts:

1. Count your domains: How many distinct domains need SeaText? If the answer is one, use one account. If the answer is two or more, you need separate accounts.
2. Assess budget constraints: Can you afford multiple subscriptions? If budget is severely limited and you have more than one domain, prioritize the most important domain and expand later.
3. Evaluate isolation needs: Do you need separate reporting for each domain? Do different domains serve different brands or client accounts? If yes, separate accounts are necessary.
4. Consider team access: Will different team members manage different domains? Separate accounts allow granular access control.
5. Check compliance requirements: Some industries require strict data separation between websites. Separate accounts provide the strongest isolation.

Troubleshooting Validation Errors

If you encounter validation errors after installing SeaText, here is how to diagnose and fix them:

• Mismatched domain error: This occurs when the JavaScript snippet is installed on a domain that does not match the primary URL in your account. Verify that the domain in your SeaText account matches the domain where you installed the snippet exactly. Check for www vs. non-www differences and http vs. https.
• AI features inactive: If the snippet loads but AI features do not activate, check your SeaText dashboard for validation warnings. The account may be suspended or the domain may not be verified.
• Data not appearing in analytics: If you see traffic in your website analytics but not in SeaText, verify the snippet is installed on all pages. Some pages may use different templates that exclude the snippet.
• Localhost or development URL blocked: SeaText restricts development URLs for security. You cannot use SeaText on localhost or non-public URLs. Set up a staging subdomain with a real domain name for testing.
• Subdomain issues: Subdomains count as part of the domain hierarchy. If your primary URL is example.com, the account is registered to that domain and its subdomains. However, SeaText still expects the main domain to match. If you need subdomains to operate independently, create separate accounts for each subdomain.

Practical Scenarios

• Multiple brand sites: If you manage separate brands with different websites, create a distinct SeaText account for each brand. This keeps branding, AI copy, and analytics completely separate. Brand A's conversion data will not mix with Brand B's data.
• Development vs. production: Use a production account for your live domain and a separate test account for your staging environment. Create a subdomain like staging.yourdomain.com and register it as the primary URL for your test account. This lets you experiment with AI configurations without affecting live traffic.
• International markets: If you run country-specific domains such as yoursite.com and yoursite.co.uk, give each its own account. This allows you to track local performance separately and configure language-specific AI agents for each market.
• Client agencies: If you manage websites for multiple clients, each client should have their own SeaText account. This ensures client data is isolated, billing is clear, and each client can access only their own analytics and settings.

Limitations

SeaText does not support a single account covering multiple primary URLs. Attempting to use one account across domains will result in validation errors and inactive AI features. You also cannot share a single billing profile across domains without creating separate accounts.

Dynamic development URLs and localhost are restricted for security. SeaText requires a valid, publicly accessible domain to associate traffic correctly. If you need to test SeaText before launch, use a staging subdomain with a real domain rather than a local development environment.

There is no built-in way to transfer data between accounts. Historical data stays with the original account and domain. If you later decide to consolidate, you would need to export data manually from each account.

Frequently Asked Questions

• Can I add a subdomain to an existing account? Subdomains are part of the primary URL hierarchy. If your primary URL is example.com, the account is linked to that main domain. Subdomains like blog.example.com or shop.example.com will work under the same account, but they are not independent. If you need full isolation for a subdomain, create a separate account registered to that subdomain as the primary URL.
• What if I have a staging domain like dev.example.com? Development URLs are restricted for security reasons. SeaText blocks localhost and dynamic dev URLs. Create a separate test account registered to a staging subdomain on a public domain for reliable testing.
• Is there a discount for multiple accounts? SeaText pricing is per-account. Check the SeaText pricing page for any bundle offers or volume discounts that may apply.
• Will separate accounts increase page load latency? No. Each account runs its own JavaScript snippet, which loads independently. The performance impact is the same regardless of whether you use one account or multiple accounts.
• Do I lose data when I create a new account? Data is scoped to the account's domain. Historical data stays with the original account and domain. Creating a new account does not affect data from the previous account.
• Can I use the same email for multiple SeaText accounts? Typically, each account requires a unique email address. Check with SeaText support if you ne

Yes. SeaText AI lets you set up scheduled content updates and run them on several domains at the same time. The platform's AI agents rewrite pages automatically, so you can push the same change to every site without manual copy-pasting.

What automation means in SeaText AI

SeaText AI's agents watch visitor behavior and rewrite page copy in real time. When you set a schedule, the AI applies the same rule at the chosen time. For example, you can replace a product description, add a new promotion, or update a banner across all sites.

Automation is not the same as simple find-and-replace. The AI reads the page, understands the context, and rewrites the relevant copy. It can generate variants for headlines, offers, product blocks, and calls to action. The platform also runs A/B-style testing to scale the wording that performs best.

This matters for multi-domain teams because the same marketing message often needs to appear in several places at once. Instead of logging into each content management system and editing files by hand, you define the job once per SeaText account and let the agents execute it.

How scheduled automation works

Each SeaText AI account is linked to one primary URL. That URL is the domain where the script collects data and activates agents. To automate updates across multiple domains, you create an account for every site you manage.

Inside each account, you use the Automation section to define a content change. You choose the element to rewrite, such as a headline, product name, description, or CTA. You also set the date and time for the job to run.

When the scheduled time arrives, the AI agents in every account execute the change. The execution is near-simultaneous because each account runs its own job independently. If you start the jobs at the same time, visitors on all domains see the update at roughly the same moment.

The script remains inert until you activate it. That means installing the code does not change anything by itself. Activation happens when you create a job and turn on the agent in the dashboard.

Manual workflows vs. automated multi-domain updates

Manual updates require someone to open each site, edit the content, publish the change, and verify it. That process is slow and error-prone. With three domains, you might spend an hour. With ten domains, you can lose most of a day.

Automated workflows remove the repetitive part. You prepare the job once, schedule it, and let the agents handle execution. The main cost is setup time, not ongoing effort.

Automation also reduces drift. When a human edits five sites by hand, one site often gets a slightly different version. A scheduled SeaText job applies the same rule consistently, so the wording stays aligned.

There are still risks. You must create an account for every domain, or the update will not run there. You also need to keep schedules identical across accounts. If you change the time in one account but not the others, the rollout becomes unsynchronized.

Time savings and potential risks

Consider a team managing five regional stores. A manual banner update might take 20 minutes per site, or 100 minutes total. With SeaText, the same job runs across all accounts in seconds, after the initial setup.

The savings grow as you add more domains. Translation updates are another example. SeaText can work in 125 languages, and each domain can have its own language version. A coordinated schedule lets you publish a new offer in every market without waiting for a translator to paste text.

The biggest risk is missing an account. If you add a new domain but forget to create a SeaText account, the automation skips that site. Before every rollout, check your domain list against your account list.

Another risk is schedule drift. If you update the job in one dashboard but not the others, some sites go live late. Use a spreadsheet or a management script to track the scheduled jobs. You can also trigger jobs through the SeaText API for a single command.

Practical scenarios

Seasonal promotion: A holiday discount banner needs to appear on five regional stores at midnight. Create the same scheduled banner job in each account and launch them together.

Regulatory notice: New privacy language must be added to every site within 24 hours. Use the automation feature to push the text change across all domains at once.

Multi-time-zone rollout: You manage stores in New York, London, and Tokyo. Schedule each account to activate at midnight local time instead of forcing one global time.

Content rollback: Suppose a campaign underperforms. You can disable the scheduled job in any account before it runs. If the update is already live, you can create a rollback job that restores the previous wording.

Domain-specific customizations: You can let one regional site keep its local pricing while the others use the default offer. Each account controls its own content rules, so you are not forced into a single global version.

Step-by-step: Automating updates for several domains

1. Create a SeaText AI account for every domain you own.
2. Install the SeaText script on each site. The script stays inert until you activate it.
3. In each account, go to the Automation section and define the content change you want.
4. Set the date and time for the update. Save the job.
5. When the scheduled time arrives, the AI agents on all accounts execute the change simultaneously.
6. Verify the live page after the run, then log the job in a central tracker.

Security and compliance considerations

SeaText requires a distinct account for every primary URL. Development or localhost URLs are blocked for security, so you cannot use a single account for a staging and a production site.

This rule protects website integrity. The AI remains inert until activated, which means an unactivated script cannot alter content. You control when each agent starts working.

For compliance, keep a record of which accounts hold which domains. If a domain changes, you must create a new account for the new primary URL and set up the schedules again. You should also review the content changes before publishing, especially for regulated industries.

Performance impact of real-time rewrites

SeaText agents rewrite pages in real time for paid visits and scheduled jobs. The platform tracks results by page, keyword, and version, so you can see whether a rewrite lifted conversions.

Real-time rewrites do not create new pages. The script changes the copy a visitor sees on the existing page. That keeps the URL structure stable and avoids duplicate-content problems.

Performance depends on the agents you activate. Google Ads matching, translation, and CRO testing can run together. SeaText reports conversion metrics such as +35% conversion lift for ad landing page matching, but your results depend on traffic, offer, and setup.

If you run many domains, monitor each account's dashboard. A heavy rewrite schedule may increase server load during the activation window. Stagger non-urgent updates to avoid a spike across all sites.

Limitations you need to know

Each SeaText AI account is linked to a single primary URL. There is no built-in dashboard that manages every domain from one place. You must sign in to each account or use the API to coordinate.

Dynamic development domains may not function properly because SeaText might be unable to reliably associate traffic with your account. Stick to valid, real domains for production scheduling.

The platform does not impose a hard limit on how many domains you can manage, but licensing costs scale with accounts. Before you expand, confirm your plan supports the number of primary URLs you need.

FAQ

• Do I need to log in to each account to start a schedule? You can start jobs from each dashboard, or trigger them via the SeaText API for a single command.
• Can I use the same content schedule for all domains? Yes, but you must create the same job in each account. Keep the dates and times identical to avoid drift.
• How does SeaText handle domain-specific customizations? Each account controls its own content rules. You can customize offers, language, or timing per domain without blocking the global rollout.
• Can I pause an update after it's started? Yes, you can disable the scheduled job in any account before it runs.
• Is there a limit to how many domains I can manage? The platform does not impose a hard limit, but each domain requires its own account, which may affect licensing costs.
• What if a domain changes its URL? You must create a new SeaText AI account for the new primary URL and set up the schedules again.
• Does automation work for translated content? Yes. SeaText translates into 125 languages, and you can schedule translation updates per account for each market.

What "wrapping" means for SeaText

Wrapping is placing your product description inside a special HTML element that carries a SeaText data‑attribute. The AI agents scan the DOM for that attribute to identify which text they may rewrite, translate, or A/B test. Without the wrapper, the agents treat the description as ordinary content and leave it unchanged.

Why the exact wrapper format matters for AI parsing

SeaText’s parser looks for a precise attribute string: data-seatext="product-description". Any deviation—missing quotes, extra spaces, wrong attribute name, or a self‑closing tag—causes the parser to skip the element. For example, <div data-seatext=product-description> (no quotes) or <span data-seatext="product-desc"> (typo) will both fail. A valid block‑level wrapper looks like:

<div data-seatext="product-description">
  Your product description goes here.
</div>

To test, open a product page, right‑click the description, choose Inspect, and verify the attribute appears exactly as shown. If it is absent, the wrapper was not saved correctly or the theme caches an older version.

Required HTML format

Use a block‑level element—commonly <div> or <section>—with the attribute data-seatext="product-description". Inline elements such as <span> work but may break layout if the description contains block‑level children. The wrapper must enclose the full description text, including any HTML markup you want the AI to consider.

Step‑by‑step implementation in Shopify

1. Open your theme code. In Shopify admin, go to Online Store → Themes → Actions → Edit code.
2. Locate the product template. Find product.liquid (older themes) or a file inside the sections folder such as main-product.liquid or product-template.liquid (Online Store 2.0 themes).
3. Identify the Liquid variable. Search for {{ product.description }} or {{ product.description | escape }}. This is the raw description output you will wrap.
4. Handle escaped HTML. If the variable uses the escape filter, remove it so the AI receives clean HTML. Replace {{ product.description | escape }} with {{ product.description }} inside the wrapper.
5. Insert the wrapper. Replace the raw output with:

<div data-seatext="product-description">
  {{ product.description }}
</div>

6. Confirm the SeaText JavaScript snippet is loaded. In theme.liquid (inside the <head> tag) verify the SeaText integration script is present. The snippet is provided in your SeaText dashboard and must be pasted before the closing </head> tag. Without it, the wrapper exists but no agent runs.
7. Save and preview. Click Save, then open a product page. Inspect the HTML to confirm the data-seatext attribute wraps the description.
8. Test AI behavior. Activate the Ecommerce Product Copy Agent in your SeaText dashboard. Visit the product page; the description should change within seconds. Use dev tools to compare original and rewritten text.

How the wrapper interacts with SeaText's AI agents

Once the wrapper and the JavaScript snippet are present, SeaText deploys up to 20 autonomous agents. The Ecommerce Product Copy Agent reads the wrapped description, generates variants, and serves the highest‑converting version to each visitor. The Website Translation Agent detects the visitor’s language and replaces the wrapped text with a translation in one of 125 languages. The AI A/B Testing Agent runs continuous multi‑armed bandit tests on the wrapped copy, allocating traffic to winning variants without manual 50/50 splits. The Visitor Source Rewrite Agent adapts the description to match the keyword or referral source that brought the visitor. All these actions happen in real time because the wrapper gives each agent a reliable DOM anchor.

Trade‑offs: wrapping vs. other integration methods

SeaText also offers a JSON API and a Shopify app block. The wrapper method is the fastest to implement—no app install, no API keys, no server‑side code. However, it relies on client‑side JavaScript, so search crawlers that do not execute JS will see the original description. The JSON API gives you server‑side control and works with headless storefronts but requires backend development. The app block provides a no‑code UI in the theme editor but is limited to Online Store 2.0 themes. Choose the wrapper when you need a quick, zero‑dependency integration on a standard Shopify theme; choose the API for headless or custom platforms; choose the app block if you prefer visual editing and use a compatible theme.

Practical troubleshooting steps

• Wrapper not appearing: Clear Shopify’s theme cache (save the file again) and browser cache. Verify you edited the correct template—some themes render descriptions in a snippet included via {% render 'product-description' %}.
• AI not rewriting: Confirm the SeaText script loads (check Network tab for seatext.js). Ensure your domain is a valid, publicly reachable URL—localhost and password‑protected dev stores are blocked.
• Partial rewrites: If only part of the description changes, check for nested wrappers or multiple data-seatext attributes on the same page. Only the first match per agent is used.
• Translations missing: Verify the Website Translation Agent is activated and the visitor’s browser language is among the 125 supported.
• Multiple product templates: If your store uses different templates for different product types (e.g., product.liquid and product-bundle.liquid), repeat the wrapper insertion in each template file.
• Dynamic content loaded via AJAX: The wrapper must exist in the initial HTML. If descriptions are injected after page load, re‑initialize SeaText by calling window.seatext && window.seatext.refresh() after the injection.

Limitations and edge cases

• Shortcode or attribute wrapping: Placing the description inside a shortcode attribute (e.g., [product_desc data-seatext="product-description"]) does not work—the parser only scans real DOM attributes.
• Nested elements: A wrapper inside another data-seatext element confuses the parser. Keep one wrapper per description.
• Non‑Shopify platforms: The wrapper format is platform‑agnostic, but the SeaText JavaScript snippet must be loaded on the page. Platforms that restrict script injection (some hosted builders) may prevent integration. Check with the vendor.
• Development domains: SeaText ignores localhost, 127.0.0.1, and dynamic preview URLs (e.g., *.myshopify.com preview links). Use a real custom domain or a stable staging domain with a valid SSL certificate.
• Multiple domains: Each distinct domain requires its own SeaText account. A single account cannot serve both example.com and shop.example.com.
• Script loading order: The SeaText snippet must load before the wrapper is parsed. Place it in <head>, not at the bottom of <body>.

Key facts

Terminology

• Data‑attribute: An HTML attribute that starts with data- and stores custom data for scripts.
• Theme code: The set of Liquid, HTML, CSS, and JavaScript files that define a Shopify store’s appearance.
• AI rewrite: SeaText’s automatic generation of alternative copy based on the wrapped text.
• Multi‑armed bandit: An algorithm that continuously shifts traffic to the best‑performing variant instead of fixed splits.
• Reading telemetry: Millisecond‑level tracking of scroll, dwell, and re‑read behavior used to detect copy friction.

FAQ

Do I need to wrap every product description?

Yes. Each description you want SeaText to optimise must have the data-seatext wrapper.

Can I use a different HTML tag?

Any block‑level element works as long as it carries the exact attribute.

What if I have multiple languages?

SeaText will generate translations automatically once the wrapper is present and the Translation Agent is active.

Will wrapping affect SEO?

No. The attribute is invisible to search engines and does not alter the visible content.

Is there a cost to use this feature?

The wrapping itself is free; you need an active SeaText AI subscription to see the AI‑generated changes.

Can I wrap descriptions on a headless Shopify storefront?

The wrapper format works, but you must ensure the SeaText script loads on the client side. Server‑side rendering frameworks may require the JSON API instead. Check with the vendor.

What happens if I change the theme later?

Re‑apply the wrapper in the new theme’s product template and verify the script is still in theme.liquid.

How do I know which agent rewrote the text?

In the SeaText dashboard, the Conversion Agent report shows which agent (Ecommerce Product Copy, Translation, etc.) produced each variant.

SeaText AI can read HTML tags that you add around product descriptions. This lets the AI target specific text for translation, optimization, or dynamic rewriting. Use tags only where they add clear structure; excess markup can confuse the model.

What does "wrapping" a product description mean?

Wrapping means placing an HTML element—such as a <div> or <span>—around the description text. The element can carry a custom data- attribute that SeaText looks for when it scans the page.

Why add HTML tags?

• Targeted AI actions: SeaText can apply translation, copy‑testing, or keyword‑matching only to the tagged block.
• Cleaner code: Tags give you a predictable hook for future updates.
• Performance: The AI skips unrelated markup, reducing processing time.

Why tag wrapping matters for AI targeting

SeaText AI processes the page in real time. It needs a reliable anchor point to know which text to modify. A well‑placed wrapper tells the script exactly where to read and write.

If the wrapper is ambiguous, the AI may pick up surrounding navigation links or footers. That leads to unwanted changes and can break the user experience.

Using a dedicated wrapper also isolates AI work from other scripts. This reduces the chance of conflicts with third‑party widgets.

Technical details of data‑attribute scanning

When the page loads, SeaText’s JavaScript runs a DOM query similar to document.querySelectorAll('[data-seatext]'). It collects every element that contains the configured attribute.

For each element, the script extracts element.innerText. The text is sent to the AI model over a secure endpoint. The model returns the transformed text, which the script then writes back to element.innerHTML.

The scan happens once per page load. If the page updates via AJAX, SeaText can re‑run the scan if you call its Seatext.refresh() method.

Valid tag examples and custom data attributes

Any HTML element works, as long as it carries a data- attribute that SeaText is configured to read.

• <div class="product-description" data-seatext="true">…</div>
• <span data-seatext="true">…</span>
• <p data-custom="seatext">…</p> (if you set the custom attribute name in the dashboard)
• <section data-seatext="true" data-lang="en">…</section>

Do not use attributes that start with data- but are unrelated to SeaText, as they will be ignored.

Semantic HTML vs. generic div tags

Semantic tags (<article>, <section>, <aside>) convey meaning to browsers and assistive technologies. They also help SEO tools understand page structure.

SeaText does not require semantic tags, but using them can improve overall accessibility. If you choose generic div tags, ensure you add clear class names and ARIA labels where needed.

Trade‑off: semantic tags may add a few extra characters, but they provide long‑term benefits for maintainability and compliance.

Nesting and AI processing

SeaText processes only the outermost element that matches the attribute. If you nest two wrapped elements, the inner one is ignored.

Example of a bad pattern:

<div data-seatext="true">
  <span data-seatext="true">{{ product.description }}</span>
</div>

Keep nesting shallow. Use one wrapper per description block.

Handling dynamic (JavaScript‑rendered) descriptions

Some stores load product descriptions via AJAX after the initial page load. In that case, the wrapper must exist in the DOM before the content is injected.

Place the wrapper in the static template, then let JavaScript fill its inner HTML. SeaText will detect the wrapper once the content appears, provided you call Seatext.refresh() after the AJAX call.

Testing dynamic content:

1. Open the product page.
2. Open DevTools (F12) and go to the Elements panel.
3. Locate the wrapper element.
4. Confirm that the description text appears inside the wrapper after the page finishes loading.
5. Trigger a manual refresh with Seatext.refresh() in the console and observe any AI changes.

Step‑by‑step implementation

1. Open your Shopify theme editor. From the admin, go to Online Store → Themes → Actions → Edit code.
2. Locate the product template. Usually product.liquid or a file inside the sections folder.
3. Find the description output. Look for a line that resembles {{ product.description }} or similar.
4. Wrap the output with a tag. Example using a semantic section:

   <section class="product-description" data-seatext="true">{{ product.description }}</section>

5. Save the file. Click the Save button in the editor.
6. Test the change. Open a product page, right‑click → Inspect, and confirm the data-seatext attribute appears in the HTML source.
7. Refresh the AI. If you use dynamic loading, open the browser console and run Seatext.refresh().

Common pitfalls and limitations

SeaText can handle most standard tags, but there are limits:

• Do not nest multiple SeaText‑specific tags inside each other; the AI will only process the outermost one.
• Avoid placing tags inside <script> or <style> blocks—those are ignored.
• Dynamic development domains (e.g., localhost) are blocked for security reasons, so testing on a real domain is required.
• Only one data-seatext attribute is processed per page. If you need multiple blocks, configure additional custom attribute names in the SeaText dashboard.

Verification checklist

1. Open a product page in a browser.
2. Open developer tools (F12) and locate the description element.
3. Confirm the custom data- attribute is present.
4. Refresh the page after activating SeaText AI; the description should update if the AI makes a change.
5. If the description loads via JavaScript, run Seatext.refresh() in the console and verify the AI response.

Key facts

FAQ

• Can I use multiple different data attributes? Yes, but each must be unique; SeaText will only act on the one it’s configured to read.
• Will the tags affect SEO? Properly used tags do not impact search rankings; they are invisible to crawlers that ignore unknown data- attributes.
• Do I need to reinstall SeaText after adding tags? No. The AI reads the DOM on each page load.
• What if the AI changes the text incorrectly? You can disable the agent or edit the tag’s content manually.
• Can I use class‑based selectors instead of data attributes? SeaText only looks for the configured data‑ attribute. Classes help CSS but not AI targeting.
• What happens if the attribute is missing? The AI skips the element entirely. No errors are thrown, but the text will not be processed.