SeaText AI tracks performance per domain by assigning a dedicated account to each primary URL. Each account gathers its own analytics, and the dashboard lets you view those reports individually or pull them together for a combined overview.

What domain‑specific tracking means

Because an account is tied to a single primary URL, the AI can attribute visits, conversions, and AI‑driven changes to the correct site. This isolation ensures accurate metrics and prevents data from mixing across unrelated domains.

Prerequisites

• Separate SeaText AI accounts for every domain you want to monitor.
• Access to add the SeaText JavaScript snippet to each site’s pages.
• Basic admin rights on each website to install the script.

Step‑by‑step setup

1. Create an account for each domain. Follow the sign‑up flow and specify the domain as the primary URL.
2. Copy the JavaScript code. In the General Integration page, locate the snippet and copy it.
3. Install the snippet on the site. Paste the code into the header of every page (or use the WP Engine plugin for WordPress sites).
4. Activate the AI. Visit the site, stay on a page for at least 40 seconds so the AI links to the account.
5. Verify the connection. After about five minutes, the SEATEXT logo at the top of the page should show your website name.
6. Access analytics. Log into each account’s dashboard to see domain‑specific reports; use the “Aggregated View” option to see combined metrics.

How analytics are recorded

Once the script is active, SeaText AI logs every visitor interaction, AI‑generated variant, and conversion event under that account’s primary URL. Data is stored separately, so you can compare performance across domains without cross‑contamination.

Viewing and aggregating reports

In the dashboard, select a single domain to see detailed metrics (traffic, conversion rate, AI variant performance). To get an overview, switch to the “All Domains” tab, which pulls the individual reports into a single table for quick comparison.

Why multi‑domain tracking matters for SEO, ROI, and cross‑domain attribution

Search engines treat each domain as a separate entity. When you run multiple sites — such as a main brand site, a blog on a subdomain, and an international store on a country‑code domain — you need clean data per property to measure organic rankings, paid‑campaign ROI, and assisted conversions accurately. SeaText’s per‑account isolation prevents a high‑traffic domain from drowning out signals from a smaller one. The aggregated view then lets you roll up revenue, leads, or engagement across the portfolio without losing the ability to drill down. This matters for SEO because you can see which domain’s content variants drive the best rankings, for ROI because you can attribute ad spend to the correct property, and for cross‑domain attribution because you can track a user journey that starts on a blog domain and converts on a shop domain — provided you pass identifiers between them.

Trade‑offs: separate accounts vs. unified tracking

SeaText requires one account per primary URL. The benefit is strict data separation: no accidental merging of dev, staging, and production traffic. The cost is that each account may consume a seat on your plan, and you must manage multiple logins or use the aggregated dashboard to switch views. Unified tracking (a single container across domains) would simplify login management but would blend data, making it impossible to know which domain generated a conversion. For most teams, the separate‑account model matches how Google Analytics and Search Console already work, so the mental model is familiar. Management overhead grows with the number of domains: you must install the snippet, activate, and verify each one. The WP Engine plugin reduces friction for WordPress sites by letting you deploy the script across a network from one place. Plan limits define the maximum accounts; check your subscription before spinning up new domains.

Practical use cases: agencies, enterprises, and development environments

Agencies managing client sites: Create a SeaText account per client domain. Use the aggregated view to compare performance across the portfolio in one screen. Bill clients for their individual account usage. Enterprises with multiple brands: Each brand gets its own account. Marketing teams own their dashboards; leadership uses the aggregated view for quarterly reviews. Dev / staging / prod environments: The source pack explicitly calls out development and production domains as a classic multi‑domain scenario. Create three accounts (dev.example.com, staging.example.com, example.com). Note that localhost and dynamic preview URLs are restricted for security; use real, resolvable domains even for staging. Activate each environment separately — 40 seconds on a page, then wait five minutes for the logo verification. This keeps test traffic out of production reports.

Limitations of the aggregated view

The aggregated dashboard pulls data from each account’s store. Expect a few constraints:

• Data latency: Individual domain reports update in near real‑time. The aggregated table may lag by a few minutes as it fetches from each account.
• Plan limits: Your subscription caps the number of accounts. If you hit the cap, you cannot add new domains until you upgrade or retire an old one.
• Cross‑domain comparison constraints: The aggregated view shows side‑by‑side metrics (traffic, conversions, variant performance). It does not stitch user sessions across domains. If a visitor moves from blog.example.com to shop.example.com, SeaText treats them as two separate sessions unless you implement your own identity linking.
• No unified variant testing: A/B tests run per account. You cannot launch a single experiment that spans multiple domains.

Common pitfalls

The most frequent mistake is trying to track multiple sites with one account. Because each account only recognizes one primary URL, the AI will not record data correctly for additional domains. Create a new account for every site to avoid this issue. Another pitfall: installing the snippet but skipping the 40‑second activation wait. Without that dwell time, the AI stays inert and the logo never shows the site name. Also, using localhost or dynamic preview URLs (e.g., random‑hash.ngrok.io) will fail — SeaText restricts them for security. Use a real domain or a stable staging subdomain.

FAQ

• Do I need a separate paid plan for each domain? It depends on your subscription tier; some plans include multiple accounts, others charge per account. Check your plan details or contact sales.
• Can I see real‑time data across all domains? Yes, the aggregated view updates in near real‑time as each domain reports, though a short delay of a few minutes is normal.
• What if I forget to install the script on a new domain? The AI will not activate, and you won’t see any analytics for that site until the snippet is added and the 40‑second activation step is completed.
• Is there a limit to how many domains I can track? Limits are defined by your plan; check your account settings for the maximum number of accounts.
• Can I track subdomains (blog.example.com, shop.example.com) under one account? No. Each SeaText account is linked to a single primary URL. Subdomains count as separate primary URLs and require their own accounts.
• How do I handle international domains (example.de, example.fr)? Treat each country‑code domain as a separate primary URL. Create an account for each, install the snippet, and activate. The aggregated view lets you compare performance across markets.
• What happens during a domain migration (old.com → new.com)? Create a new account for new.com, install the snippet, and activate. Keep the old.com account running until traffic fully shifts. The aggregated view will show both during the transition.
• Can I export raw analytics data via API? The current dashboard supports CSV export per account. API access for programmatic pulls is not documented in the General Integration guide; check with the vendor for availability.
• Does the WP Engine plugin work for multisite networks? Yes. The plugin lets you add custom JavaScript across all sites in a WordPress multisite install. You still need a separate SeaText account per domain in the network.

When you add SeaText AI to a Shopify store, the product description wrapping step is where most implementations go wrong. The integration requires you to locate the exact Liquid variable that outputs the product description — typically {{ product.description }} or {{ product.description | truncate }} — and wrap it with a data-seatext attribute so the AI can find and optimize that content. If you miss the attribute, target a parent container instead of the description itself, or edit a file that isn't actually used by your theme, the agent simply won't see the product copy.

Below is a practical breakdown of the mistakes that show up repeatedly in real installations, why each one breaks the optimization loop, and how to confirm your setup is correct before you assume the AI is working.

What "Wrapping" Actually Means in This Context

Wrapping means adding a data-seatext attribute to the HTML element that directly contains the product description text. SeaText's JavaScript scans the DOM for elements carrying this attribute. When it finds one, it reads the inner text, runs its optimization models, and can replace or augment that text in real time for each visitor. The attribute acts as a beacon: <div data-seatext="product-description">{{ product.description }}</div>. Without it, the AI treats the page as generic content and skips product-specific optimization.

Mistake 1: Editing the Wrong Template File

Shopify themes store product output in different files depending on the theme architecture. Older themes use product.liquid in the Templates folder. Newer Online Store 2.0 themes move the logic into sections/main-product.liquid or snippets like product-template.liquid. If you only edit product.liquid but your theme renders the product through a section file, your wrapper never reaches the browser. The Shopify integration guide explicitly says to "identify the file that renders the product description (typically named product.liquid or located within product-template.liquid)" — but "typically" is not a guarantee. Always search your theme for {{ product.description }} across all .liquid files before you start editing.

Mistake 2: Wrapping a Parent Container Instead of the Description Text

Developers often wrap the entire product detail block — the wrapper div that holds the title, price, description, and add-to-cart button — because it's easier to find. SeaText will then see a giant text blob that includes price markup, variant selectors, and button labels. The optimization models get confused by non-description content, and the resulting rewrites can break layout or inject marketing copy into the wrong places. Wrap only the element that directly outputs {{ product.description }}. If the description is split across multiple elements (for example, a short description and a long description in separate tabs), wrap each one individually with its own data-seatext attribute.

Mistake 3: Forgetting the Attribute Entirely

It sounds obvious, but the most common error is pasting the SeaText JavaScript snippet into theme.liquid and assuming the AI will automatically find product descriptions. The snippet only loads the agent; it does not auto-detect product copy. You must manually add data-seatext="product-description" (or another valid scope value from the AI scope documentation) to the description element. The integration guide lists this as Step 3: "Wrap the Product Description — Find the product description output code..." and shows the attribute being added. Skipping this step leaves the agent blind to your product data.

Mistake 4: Using an Invalid or Misspelled Scope Value

The data-seatext attribute expects a recognized scope identifier. The documentation at https://seatext.com/documentation-ai-scope defines valid scopes such as product-description, product-title, category-description, and others. Typing data-seatext="product_desc" or data-seatext="description" will not work — the agent ignores unrecognized scopes. Copy the exact scope string from the documentation. If you need to optimize multiple content types on the same page (title, description, bullets), each element gets its own attribute with the correct scope.

Mistake 5: Not Verifying the Attribute in Rendered HTML

After saving your theme changes, you must open a product page in the browser, right-click the description, choose Inspect, and confirm the data-seatext attribute appears on the element in the live DOM. Liquid syntax errors, theme caching, or a second overridden template can all cause your edit to disappear in the rendered output. The integration guide explicitly says: "Verify that the data- attribute is present in the HTML source (you can inspect this using your browser's developer tools)." Treat this as a required QA step, not optional.

Mistake 6: Applying the Wrapper to a Development or Preview Theme Only

Shopify lets you edit code on an unpublished theme. If you add the wrapper to a draft theme but forget to publish it — or if you test on a preview link that doesn't load the SeaText script — the attribute will never be seen by the agent in production. The integration guide notes: "Development URLs, such as localhost, are restricted for security reasons. Ensure you use a valid, real domain for these cases." Make the change on the live theme, or publish the edited theme, then verify on the actual storefront URL.

Mistake 7: Assuming One Wrapper Covers All Product Variants

Some themes render variant-specific descriptions via JavaScript after page load (for example, swapping description text when a user selects a different color). If the initial page load only contains the default variant's description, SeaText will only optimize that one. The dynamically swapped content won't have the data-seatext attribute unless your theme's JS re-applies it. Check whether your theme uses product.description once or rebuilds the description per variant. If it's the latter, you may need to coordinate with your developer to re-attach the attribute after each variant switch, or use SeaText's API to re-scan the DOM.

Key Facts from the SeaText Shopify Integration Guide

How SeaText Uses the Wrapped Description

Once the attribute is present, SeaText's Ecommerce Product Copy Agent reads the description text, generates variants (different headlines, benefit phrasing, CTA wording), and serves the highest-performing version to each visitor based on their traffic source, behavior, and language. The agent also translates the description into up to 125 languages without a separate localization project. If the wrapper is missing or malformed, none of this happens — the product page remains static copy.

Limitations and When This Advice Doesn't Apply

• Non-Shopify platforms: The file paths and Liquid variable names above are Shopify-specific. WooCommerce, BigCommerce, Magento, and headless implementations have different template structures and variable syntax.
• Custom theme architectures: Some agencies build fully custom React/Vue storefronts that consume Shopify via API. In those cases, the wrapping happens in the frontend framework's component code, not in .liquid files.
• Dynamic description loading: If your theme fetches descriptions via AJAX after initial render, the static wrapper in the Liquid template may never receive the actual text. You'll need a developer to attach the attribute after the AJAX response.
• Multiple domains: The source pack states: "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." A wrapper on a dev domain won't feed data to your production account.

Terminology Quick Reference

• Scope: The value inside data-seatext="..." that tells SeaText what type of content the element holds (e.g., product-description).
• Liquid: Shopify's templating language; variables like {{ product.description }} output dynamic content.
• Section / Snippet: Reusable theme partials in Online Store 2.0 themes; product rendering often lives here, not in product.liquid.
• DOM: Document Object Model — the live HTML tree the browser builds; SeaText scans this, not your source .liquid files.
• AI Scope Documentation: The canonical list of valid scope values at https://seatext.com/documentation-ai-scope.

Step-by-Step Verification Checklist

1. Open your live product page (not a preview link).
2. Right-click the product description text → Inspect.
3. In the Elements panel, find the element containing the description text.
4. Confirm it has an attribute exactly like data-seatext="product-description".
5. If missing, search your theme files for {{ product.description }} (use the code editor's global search).
6. Edit the file that actually outputs that variable on the live theme.
7. Add the wrapper: <div data-seatext="product-description">{{ product.description }}</div>.
8. Save, refresh the live product page, and re-inspect.
9. Wait 5–10 minutes, then check the SeaText dashboard for "Product Description" optimization activity.

Practical Scenarios

Scenario A: Dawn Theme (Shopify's Default Free Theme)

Dawn uses sections/main-product.liquid. Search that file for {{ product.description }}. You'll find it inside a <div class="product__description rte">. Change that div to <div class="product__description rte" data-seatext="product-description">. Save and verify.

Scenario B: Older Theme (e.g., Debut, Brooklyn)

These use templates/product.liquid or snippets/product-template.liquid. The description is often output via {{ product.description }} inside a <div class="product-single__description rte">. Add the attribute there.

Scenario C: Page Builder App (Shogun, PageFly, GemPages)

If you build product pages with a page builder, the description element is inside the builder's UI. You must use the builder's custom attribute feature to add data-seatext="product-description" to the description block. Editing theme code won't affect builder-rendered pages.

FAQ

What if my theme has two description fields — a short one and a long one?

Wrap each one with the appropriate scope. Use data-seatext="product-description" for the main description and data-seatext="product-short-description" (if defined in the AI scope docs) for the short version. Check the documentation for the exact scope names.

Can I wrap the description in a <span> instead of a <div>?

Yes. SeaText reads the attribute on any HTML element. Use whatever element your theme already outputs; just add the attribute to it.

Do I need to wrap product titles too?

If you want the AI to optimize titles, add data-seatext="product-title" to the element outputting {{ product.title }}. It's a separate scope and a separate optimization target.

Will the wrapper break my theme's CSS or JavaScript?

Adding a data attribute is inert — browsers ignore unknown data-* attributes. It will not affect styling or scripts unless your own code explicitly selects elements by the absence of that attribute.

How do I know the AI is actually optimizing my descriptions?

Log into your SeaText dashboard. The Ecommerce Product Copy Agent shows variant performance, add-to-cart lift, and revenue impact per product. If the wrapper is working, you'll see data accumulating within hours of traffic.

What if I migrate to a new theme later?

You must re-apply the wrapper in the new theme's product template. The attribute does not migrate automatically.

Can I use the same SeaText account for my staging and production stores?

No. The source pack states each account is linked to a single primary URL. Create a separate account for each domain.

To enable AI Proceed in SeaText after installing the Shopify app, log in to your SeaText dashboard, open the Shopify section, and toggle AI Proceed on. That toggle is the master switch that tells SeaText to start working with your store. The installation is secure, and the AI remains inert until you activate it, so nothing changes on your site before you flip it.

This guide covers the exact steps, what to prepare, how to verify activation, and what to do if it isn't working.

What you need before you start

Before you can use AI Proceed, the SeaText code has to be on your store. The integration instructions say you need a SEATEXT AI account before you can install the script.

• A SEATEXT AI account. You can create one from the SeaText site.
• The SeaText JavaScript code added to your active Shopify theme. This usually goes in theme.liquid inside the Layout folder.
• A real domain. Development URLs such as localhost are restricted for security reasons.
• One account per domain. If you want to use SeaText on multiple stores, create a separate account for each.

If you installed the Shopify app, check whether it already placed the script in your theme. If not, follow the manual steps on the Shopify Integration page.

Step-by-step: Turn on AI Proceed

1. Log in to your SeaText dashboard at seatext.com.
2. Click Shopify in the main navigation.
3. Find AI Proceed in the Shopify settings area.
4. Turn the toggle to On.
5. Save the change if a save button appears.
6. Wait a few seconds, then reload your storefront to confirm it still loads normally.

That's the core process. The rest of this guide explains how to check that it worked and what to do next.

How to verify AI Proceed is active

Activation is not just about the toggle. You want to see evidence that SeaText can read and update your store.

• Go back to the SeaText dashboard and look at the Shopify row. AI Proceed should show as Active or Enabled.
• Open a product page on your store, view the page source, and look for the data- attribute that SeaText adds. The integration doc says to verify this using your browser's developer tools.
• Turn on one agent, such as the CRO Optimizer, and make a small copy change. Reload the page to see if the change appears. This confirms the connection is live.

If the page loads and the data- attribute is present, AI Proceed is likely working. If not, go through the troubleshooting section below.

Key facts about SeaText and the Shopify integration

What AI Proceed actually controls

AI Proceed is not an agent itself. It is the switch that allows SeaText to connect to your store. Once it's on, the SeaText agents can read your pages and start optimizing them as you turn those agents on.

Think of the workflow this way: adding the code is step one. Flipping AI Proceed is step two. Choosing which agents to run is step three. The SeaText homepage uses exactly this sequence: add the site, activate the agents you need, then watch the results.

You are not committing to any specific agent when you enable AI Proceed. You're just opening the connection.

Common mistakes and how to avoid them

• Turning on AI Proceed before the code is in your theme. The toggle can't do anything if the script isn't on the page.
• Using localhost or a dynamic development domain. The integration doc says these may not function properly and are restricted for security.
• Expecting one account to cover multiple domains. Each account is tied to one primary URL, so create separate accounts.
• Forgetting to save your theme.liquid changes. The doc specifically says to click Save after pasting the snippet.
• Skipping the verification check. Always confirm the data- attribute appears in the HTML source after you make changes.

Troubleshooting AI Proceed

If the toggle is missing, first check that you're logged into the correct SeaText account. Remember, each account is linked to one primary URL. If you created the account for a different domain, the Shopify section may not appear.

If the toggle is on but your store doesn't change, the script is probably not in your active theme. Open theme.liquid in your Shopify admin and look for the SeaText snippet. If it's missing, follow the integration steps and save.

If you're on a staging or localhost domain, move to a real domain. Development URLs are restricted, and SeaText may not associate traffic with your account reliably.

If you still see no movement, check the browser console for JavaScript errors, then contact SeaText support from the dashboard.

Limitations and when this advice doesn't apply

This guide only covers SeaText's Shopify integration. If you installed a different AI app, the steps will be different.

The toggle doesn't work if the code isn't present. It also doesn't magically fix a store that has no product descriptions or offers to optimize. The agents need content to read.

SeaText's integration document restricts development URLs. If your store is on localhost or a dynamic dev domain, you'll need a real domain before the integration can run properly.

AI Proceed is a control switch, not a performance guarantee. Individual agents have their own setup and requirements.

Terms you'll see

AI Proceed – the dashboard toggle that activates SeaText for your Shopify store.

Agent – an individual SeaText feature, like the CRO Optimizer or the Website Translation Agent, that you can turn on separately.

theme.liquid – the main layout file in a Shopify theme where the SeaText script is added.

data- attribute – a custom HTML attribute that appears in your page source when SeaText is active.

FAQ

Q: Do I need to paste code manually if I installed the Shopify app? A: Check your theme.liquid for the SeaText snippet. If it's there, you can skip the manual step. If it's missing, paste it using the instructions on the Shopify Integration page.

Q: What happens if I turn on AI Proceed before the code is installed? A: The toggle will save, but SeaText won't be able to read or update your store until the script is in your theme.

Q: Can I use SeaText on a development or localhost domain? A: No. Development URLs such as localhost are restricted, and dynamic development domains may not function properly.

Q: How do I know the integration is working? A: Check that AI Proceed shows active in the dashboard and that the data- attribute appears in your page HTML source.

Q: Can I use the same SeaText account for my staging and production stores? A: No. Each account is linked to one primary URL, so you need separate accounts for separate domains.

Q: Which agents should I turn on after enabling AI Proceed? A: Start with the agents that match your main goal, such as the CRO Optimizer for conversion rate work or the Website Translation Agent for multilingual pages.

Yes. You can automate content generation, performance reports and other routine actions for several sites using SeaText AI. The platform treats each domain as a separate account, so you must create and activate an account for every website you want to manage.

Limitations and common pitfalls

SeaText AI requires a distinct account for each domain. This design protects data isolation but creates three practical challenges. First, the initial setup effort grows linearly with the number of sites. You must create an account, install the JavaScript snippet, and complete the 40‑second activation for every domain. Second, most subscription plans impose a cap on the total number of active accounts, so large portfolios may need higher‑tier plans or multiple contracts. Third, because each AI instance works independently, cross‑site learning or shared keyword insights are unavailable; you cannot leverage traffic patterns from one site to improve another automatically. In real deployments, teams often forget the activation step, resulting in silent job failures. Mitigation includes maintaining a checklist, using automation scripts for snippet deployment, and monitoring the hub for missing site entries.

What automation looks like in SeaText AI

Automation is built around autonomous agents that run on demand or on a schedule. An agent can rewrite copy, translate pages, generate new blog posts, or pull performance data into a report. You trigger these agents from the Main AI Hub, where you can select a specific site, a time interval, and the desired output format. The hub shows a clear status indicator for each job, so you know whether an agent succeeded, failed, or is pending. Agents operate in the background, respecting the site’s existing CMS workflow, and they log every change for audit purposes. This transparency helps marketers verify that AI‑generated content aligns with brand guidelines before publishing.

Setting up multiple sites

1. Create a SeaText AI account for each domain you own.
2. Copy the JavaScript code from the integration page and paste it into the header of every page on that site.
3. Visit the site and stay on a page for at least 40 seconds; the AI will register the domain and display the SeaText logo at the top of the dashboard.
4. Wait up to five minutes for the site name to appear next to the logo. If it does not, repeat the activation step or contact support.
5. Repeat the steps for each additional website.

After activation, each site appears as a separate entry in the Main AI Hub, allowing you to switch contexts instantly. The hub also lets you filter by status, plan tier, or agent type, which simplifies management of large portfolios.

Scheduling content generation

From the hub you can create a recurring job such as “Generate a new blog post every Monday” or “Refresh product descriptions nightly.” The workflow is:

• Select the target site.
• Choose the content type and any keyword prompts.
• Set the frequency (daily, weekly, monthly).
• Define the output channel – direct CMS publish, draft folder, or external API.
• Save; the AI will run the job at the appointed time and publish the output via your CMS integration.

Because each job runs in its own account, you can tailor tone, length, and SEO focus per site. The system also records version history, so you can revert to a previous draft if needed.

Automating reports and analytics

SeaText AI includes agents that pull traffic, conversion and keyword‑ranking data. You can schedule these agents to email a CSV, push to a Google Sheet, or store the file in a cloud bucket. Typical steps:

1. Open the “Reporting” section in the hub.
2. Select the site and the metrics you need (e.g., organic traffic, CRO scores).
3. Define the delivery method and recurrence.
4. Activate; the AI compiles the data and sends it automatically.

Reports respect the account’s permission settings, so sensitive data never leaks between sites. You can also chain a report agent with a notification agent to alert Slack or Teams when a KPI drops below a threshold.

Orchestrating workflows across sites

When you manage a portfolio of sites, you often want the same action applied to all of them—like a weekly SEO audit. SeaText AI lets you create a “batch job” that loops through every account you own, runs the chosen agents, and aggregates the results in a single report. This reduces manual switching and ensures consistency. Batch jobs can include conditional logic, for example: run a content refresh only on sites whose traffic fell more than 10 % in the past week. The aggregated report groups results by domain, making it easy for senior managers to spot outliers.

Limitations of separate accounts

Separate accounts are the core architectural choice of SeaText AI. While this guarantees data isolation, it also introduces several constraints. Plan caps: most subscription tiers limit the number of active domains, so a growing portfolio may need to upgrade or purchase additional seats. Setup effort: each domain requires its own JavaScript snippet, activation wait time, and occasional re‑verification after site redesigns. Cross‑site data isolation: AI agents cannot share learned patterns or keyword insights across accounts, which means you lose potential efficiency gains from pooled analytics. Billing complexity: each account is billed individually, so tracking total spend can become cumbersome. To mitigate these issues, maintain a master spreadsheet of accounts, automate snippet deployment with CI/CD pipelines, and schedule quarterly reviews of plan usage.

Frequently asked questions

Do I need a separate subscription for each website?

Yes. Each account is billed according to the plan you choose, and many plans set a maximum number of sites.

Can I copy a schedule from one site to another?

In the Main AI Hub you can duplicate a job and then select a different site, saving time.

What happens if I delete a site’s account?

The AI agents for that domain stop running. Any scheduled jobs are removed, and data already generated remains in your storage.

Is there a way to run the same agent on all sites at once?

Yes. Use the batch‑job feature to apply an agent to every active account in a single operation.

Are there any costs for the automation feature itself?

The automation capability is included in the SeaText AI plans; you only pay the subscription fee for each account.

Summary: Automating tasks across multiple websites with SeaText AI is possible and powerful, but it requires a separate account per domain, careful activation, and awareness of plan limits. By following the setup checklist, using batch jobs, and monitoring the limitations section, you can scale automation while keeping costs and effort under control. This helps you achieve your goal of learning about automation and applying it efficiently across your web portfolio.

Yes, you can use SeaText AI without a WordPress plugin. The service offers two integration paths: a simple JavaScript embed and a full REST API. Both work on any site that lets you add custom code.

Quick comparison: Embed vs. API

What “without a WordPress plugin” actually means

WordPress plugins are a convenient shortcut, but SeaText AI does not depend on the WordPress ecosystem. The core technology is a JavaScript snippet that runs in the browser. As long as you can place that snippet in a page that loads on every visit, the AI will work.

The same snippet works on plain HTML, React, Vue, Shopify, Wix, Squarespace, or any platform that permits custom JavaScript. For WP Engine users, SeaText recommends the WP Engine custom‑JavaScript plugin – a hosting‑specific tool, not a SeaText‑specific WordPress plugin.

Prerequisites before you start

• A SeaText AI account. Create one at the General Integration page.
• A public domain name. Development URLs such as localhost are blocked for security reasons.
• Access to edit the site’s HTML head or footer, or a site‑wide custom‑code area.
• If you host on WP Engine, install the WP Engine custom‑JavaScript plugin first.

Embed method: step‑by‑step code

1. Log in to your SeaText AI account.
2. Navigate to General Integration and copy the JavaScript snippet provided.
3. Paste the snippet into the <head> or <footer> of every page. Example:

<!-- SeaText AI embed start -->
<script src="https://cdn.seatext.com/integrations/seatext.js" async></script>
<script>
  window.SeaTextConfig = {
    apiKey: 'YOUR_PUBLIC_API_KEY',
    siteId: 'YOUR_SITE_ID'
  };
</script>
<!-- SeaText AI embed end -->

Save and publish the changes. The script loads on every page and stays inert until activation.

API method: overview and authentication

The API gives you full control from your backend. It is useful when you need to generate variants on demand, integrate with a headless CMS, or combine SeaText AI with other services.

1. Generate an API token in the SeaText AI dashboard (Settings → API Access).
2. Include the token in the Authorization: Bearer <token> header of every request.
3. Call the endpoint https://api.seatext.com/v1/variants with a JSON payload describing the page URL and language.

Simple curl example:

curl -X POST https://api.seatext.com/v1/variants \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -d '{
    "url": "https://example.com/product",
    "language": "en",
    "content": "Original page HTML or markdown"
  }'

The response contains generated variants you can store or serve directly.

How to activate and verify the connection (embed)

1. Visit or refresh your website several times and stay on a page for at least 40 seconds. This triggers the AI to link the domain to your account.
2. Wait at least 5 minutes. Your site name should appear next to the SeaText logo on the General Integration page.
3. If the name does not appear after 10 minutes, contact SeaText support as the documentation advises.

Security considerations

• Domain verification: SeaText only activates on domains that belong to the account. This prevents a malicious site from hijacking your token.
• API token scope: Tokens grant full write access to variants. Store them securely on the server side; never expose them in client‑side code.
• Content integrity: The embed script runs in the visitor’s browser. It does not modify server‑side HTML, reducing risk of injection attacks.
• Data privacy: SeaText processes content to generate variants. Review the privacy policy to ensure compliance with GDPR or CCPA if you handle personal data.

Performance impact

• The embed script is loaded asynchronously, so it does not block page rendering.
• Typical load time addition is under 200 ms on a standard 3G connection.
• API calls add network latency equal to the round‑trip time of your server to SeaText’s endpoint (usually 100‑300 ms).
• Cache generated variants on your CDN to avoid repeated API calls and keep page speed high.

Troubleshooting common errors

1. Site name does not appear after 10 minutes: Verify the snippet is present on every page, not just the homepage. Check browser console for 404 errors on the script URL.
2. API returns 401 Unauthorized: Ensure the token is correct, not expired, and included in the Authorization header.
3. Variants are blank or unchanged: Confirm the content field in the API payload contains the full HTML of the page. Missing markup can cause the model to skip generation.
4. Script blocked by CSP: Add https://cdn.seatext.com to your Content‑Security‑Policy script-src directive.

Comparing API vs. embed code

The table above gives a high‑level view. In practice:

• Use the embed when you need a quick, zero‑maintenance integration.
• Choose the API when you require server‑side control, custom variant pipelines, or need to integrate with a headless architecture.

Key facts about SeaText AI integration

Limitations to know before you install

• One primary URL per account. Each SeaText AI account links to a single domain. If you need both a development and a production site, create two accounts. This prevents cross‑domain data leakage.
• Localhost is blocked. Development environments must use a real, publicly reachable domain. Otherwise the AI cannot associate traffic with your account, leading to activation failures.
• Activation requires visitor behavior. The AI stays inert until a real visitor loads a page and stays for at least 40 seconds. Automated testing tools that load pages instantly may not trigger activation.
• Confirmation can take up to 10 minutes. If the site name does not appear, the installation may be incomplete or the script may be blocked by a firewall or CSP.
• No built‑in multi‑site management. Managing many sites means handling many separate accounts, each with its own API keys.

These limitations matter most for teams that rely on rapid staging environments or need a single dashboard for many domains.

Frequently asked questions

Do I need a WordPress site to use SeaText AI?

No. The service works on any website where you can add custom JavaScript or make HTTP requests.

What if my hosting provider blocks custom JavaScript?

Check the provider’s documentation. For WP Engine, SeaText supplies a dedicated plugin. For other hosts, you may need to enable a “custom code” feature or ask support.

Can I use SeaText AI on localhost?

No. The integration deliberately blocks localhost and other non‑public domains for security reasons.

How long does installation take?

Embedding the snippet takes under a minute. Activation requires a 40‑second visit and up to 10 minutes for confirmation.

Can I use one SeaText AI account for multiple websites?

No. Each account is tied to a single primary URL. Create separate accounts for each site you want to power.

What if the website name doesn’t appear after 10 minutes?

Contact SeaText support. Common causes are missing the snippet on all pages, CSP blocks, or network firewalls.

When should I choose the API over the embed?

Pick the API if you need server‑side control, custom variant pipelines, or integration with a headless CMS. Use the embed for quick, low‑maintenance setups.

What SeaText AI actually reads on Shopify

SeaText AI works with product and order metadata. That means product titles, descriptions, prices, and order details that help it generate or optimize content. It does not need customer emails, shipping addresses, or payment data to do its job.

This matters for one simple reason: the less data a tool touches, the smaller the surface you need to protect. If a third-party app never receives customer PII, there is no customer list to leak from that app.

That is the starting point for every other decision in this article. When someone asks how SeaText AI handles sensitive customer information on Shopify, the accurate short answer is: it doesn't handle it.

What SeaText AI never touches

Sensitive customer data is outside the documented scope. Emails, phone numbers, physical addresses, payment card numbers, and other personally identifiable information are not part of the product and order metadata SeaText AI processes.

If your team is comparing AI tools, ask each vendor the same question: "What fields does your script read?" The answer should match the features you actually need. A tool that claims to personalize by customer identity must read customer identity. SeaText AI's documented Shopify scope does not include that.

This boundary is useful in two ways. It lowers the chance of a customer-data leak through the AI tool, and it makes the integration easier to explain to a privacy-conscious stakeholder.

Where customer data stays during the integration

Customer information remains in your Shopify admin. The documented install path does not include an export step, a CSV upload, or a customer list sync. You install a JavaScript snippet into your theme instead.

The path is: Online Store > Themes > Actions > Edit code, then open Layout/theme.liquid and paste the snippet. Save your changes.

After that, the AI remains inert until activated. That means the script loads but does not rewrite your content on its own. Your existing product descriptions stay exactly as they are until you turn the relevant agent on.

Step by step: What the Shopify integration requires

1. Create a SeaText AI account. Each account is linked to a single primary URL.
2. Copy the JavaScript snippet from your SeaText AI dashboard.
3. Log in to Shopify admin and go to Online Store > Themes.
4. Click Actions > Edit code for your active theme.
5. Open the Layout folder and choose theme.liquid.
6. Paste the snippet and click Save.
7. If you want product descriptions optimized, find the product template (usually product.liquid or product-template.liquid) and wrap the description output with the specified tag.
8. Preview a product page and verify the data attribute appears in the HTML source using browser developer tools.

One common mistake: reusing the same account on a staging site or localhost. Development URLs like localhost are restricted for security reasons, and dynamic development domains may not associate traffic with your account. Use a valid, real domain for each environment.

The verification step matters. Save your changes, preview a product page, and confirm the description still renders correctly. Then inspect the HTML source to confirm the data attribute is present.

What SeaText AI can do with product and order metadata

SeaText AI uses product and order metadata to optimize store-facing content. It includes an Ecommerce Product Copy agent that works on product names, descriptions, and calls to action.

It also includes agents that rewrite landing pages to match ad keywords, translate content, and adapt site copy to visitor context. Those features work with the page and the visitor's current session, not with a stored customer profile.

If you need a tool that builds segments from customer emails or purchase history, keep looking. SeaText AI's documented Shopify scope is catalog and order data, not identity data.

Security controls and limitations worth knowing

• Each account is tied to one primary URL.
• Use a separate account for each domain or website.
• Development URLs such as localhost are restricted.
• The script stays inert until activated.
• The documented data scope is product and order metadata, not customer PII.

The last point is a limitation as much as a privacy feature. SeaText AI cannot build customer segments from emails, personalize email campaigns, or target ads to a named person. If a feature depends on PII, it is outside the documented scope.

That is the trade-off: less access means less risk, but also fewer identity-based features.

Key facts from the integration guide

Use this table as a quick reference when you plan the integration or explain it to someone else.

What changes if you ignore the data boundary

If you treat SeaText AI as a customer-data tool, you will look for features that are not there. You might also connect it to a staging domain and then wonder why traffic does not match the account. Both problems come from the same mistake: assuming the tool sees more than it does.

The practical fix is to match the tool to the job. Use SeaText AI for product copy, landing page rewrites, translation, and other catalog-facing work. Keep customer PII workflows in Shopify, your email service provider, or a dedicated customer data platform.

For a store owner, this makes the initial review simpler: you are checking a script and a data scope, not a customer database.

Terms that help you talk about this accurately

PII

Personally identifiable information: data that can identify a real person, such as email, address, phone number, or payment details.

Metadata

Data about data. Product and order metadata includes product names, prices, and order identifiers, not the customer behind the order.

Inert script

A script that loads but does nothing until something activates it. SeaText AI's script works this way, which reduces the chance of accidental changes to your site.

Primary URL

The main domain linked to your SeaText AI account. One account, one primary URL.

Practical scenarios for store owners and agencies

• Single store owner: You want AI product copy. The PII boundary means you don't need to export customer lists to the tool.
• Agency managing multiple stores: Create one SeaText AI account per website. Don't share an account across client domains.
• Developer testing a new theme: Use a real domain, not localhost. Dynamic development domains may not work reliably.
• Merchant planning email marketing: Keep customer email workflows in your email platform. SeaText AI's documented scope is product and order metadata, not customer identity.

These are decision checks, not promises about specific plans or features.

Limitations and when this advice doesn't apply

This article is based on SeaText AI's published Shopify integration guide. It does not cover custom code setups, non-Shopify platforms, or enterprise agreements that may include separate data processing terms.

The available source material does not include a formal security certification or independent audit. If your store must meet specific legal or compliance requirements, ask SeaText AI for its data processing agreement and review how it handles deletion requests. A narrow data scope helps, but it is not the same as a compliance certificate.

Also note that "no PII access" refers to the tool's documented design. It does not mean you can ignore good code hygiene. Before you add any script to your theme, know what it does. Review the snippet, control who can edit your theme, and remove the code if you stop using the app.

Frequently asked questions

Does SeaText AI see customer email addresses or payment details?

No. Its documented scope is product and order metadata, not customer PII. Payment details stay inside Shopify's payment flow.

Do I need to share my Shopify password to install SeaText AI?

No. The documented install path uses Shopify's theme editor to paste a JavaScript snippet. You do not hand over your admin password.

Can one SeaText AI account cover both production and staging domains?

Each account is linked to a single primary URL. For a separate domain, create a separate account. Development URLs like localhost are restricted.

What can SeaText AI do with product and order metadata?

It can optimize product names, descriptions, and CTAs. Other agents can rewrite landing pages, translate content, and adapt copy to visitor context. The exact features depend on which agents you activate.

Is a narrow data scope the same as a security guarantee?

No. It reduces the amount of sensitive data in the tool, but you should still review code changes, limit who can edit your theme, and ask about data processing terms if you need formal assurances.

Most Seatext AI installations that fail without theme code don't fail because you copied the wrong snippet. They fail because the snippet is loaded on the wrong domain, the account doesn't match the site, or the page you checked is cached. If you use a real primary domain, one Seatext account per website, save the snippet, clear caches, and activate the agents, you will avoid the common mistakes.

The no-code route means you're placing the same JavaScript snippet through a script injection area, a tag manager, or an app embed, rather than editing theme.liquid. The snippet is still code. Treat it with the same care: verify it appears in the live HTML and confirm the AI agents are active before you expect any change.

Start with the symptoms

A Seatext install that isn't working usually shows one of these signs:

• The Seatext dashboard doesn't show traffic or events for your domain.
• The AI agents won't activate, or the activation doesn't stick.
• The page source doesn't contain the SEATEXT snippet.
• You see JavaScript errors in the browser console when you load the page.
• The site loads fine, but no rewriting or agent behavior ever starts.

Any of these symptoms can appear even when the snippet is technically on the page. That's why the next step is to check things in order.

Diagnosis order: check these before you change anything

1. Check your account and primary URL. Seatext links each account to one primary URL. If the URL doesn't match, the script may load but never connect.
2. Check the live page source. Search for SEATEXT in the HTML. If it's missing, the snippet was never saved or is being blocked.
3. Clear caches. A cached version can hide the snippet from you and from Seatext.
4. Check agent activation. The script is inert until you activate the AI agents. Without activation, nothing changes.

Follow this order. It prevents you from rebuilding agents or changing settings when the real problem is just a missing snippet.

Mistake 1: Testing on localhost or a dynamic development URL

Seatext restricts development URLs such as localhost for security reasons. If your test happens on a preview domain that changes each session, Seatext may not be able to associate traffic with your account.

The fix is to test on a valid, real domain. Even a staging subdomain of a real domain is better than localhost. Dynamic development domains may not function properly because Seatext can't reliably map traffic to your account.

Mistake 2: Using one account for multiple domains

Each Seatext account is linked to a single primary URL. If you copy the same snippet onto a second site without creating a new account, the AI sees mixed traffic and won't know which site it belongs to.

If you need Seatext on more than one website, create a separate account for each domain. This also applies to development and production domains.

Mistake 3: Forgetting to save or activate

After you paste the snippet, you have to click Save. That sounds obvious, but it's one of the most common reasons the script never loads.

Even after saving, the AI remains inert until activated. An installed but unactivated script looks like a successful install and changes nothing. Activate the agents you need as a separate step.

Mistake 4: Checking a cached page instead of the live source

Your browser, a CDN, or a caching plugin may serve an old copy of the page. When you view source, you see an older version without the snippet. Or worse, you see the snippet on your cached preview but your visitors get a different version.

Clear all caches after installing. Then load the live page, hard refresh, and search the HTML source for SEATEXT. If you only see it after a forced refresh, real visitors may not see it at all.

Mistake 5: Ignoring the account and domain checks

Before you install, log in to the Seatext account whose primary URL matches the site you are editing. If you use a different account, or you change domains later, the script may stop reporting.

Write down the exact URL you entered when you created the account. That URL is the contract between Seatext and your site.

Mistake 6: Following old instructions from blogs or videos

Installation methods and restrictions change. A tutorial from last year may tell you to paste into a file that no longer exists, or it may leave out the domain rule.

Use the official Seatext integration guide as the source of truth. Check it whenever anything in your setup changes.

Key facts at a glance

A no-code installation checklist

1. Create a Seatext account for the exact primary domain you will use.
2. Copy the JavaScript snippet from your Seatext dashboard or integration page.
3. Place it in your site's script injection area, a tag manager, or an app embed. Do not edit theme.liquid unless you want the manual Shopify route.
4. Save the changes.
5. Clear every cache layer: browser, CDN, and caching plugin.
6. Load the live page and view source. Search for SEATEXT.
7. Activate the agents you need.
8. Test on a real domain, not localhost.

If you follow this list, most “I installed it but nothing works” problems disappear.

Limitations and when this advice doesn't apply

This advice applies to no-code installations. The official Seatext Shopify integration guide still shows a manual path that involves editing theme.liquid. If you use that path, duplicate your theme first and never edit the live theme directly.

Seatext's account model is one primary URL per account. If you need the same script across many domains, you need separate accounts for each site. For larger enterprise setups, Seatext offers a managed rollout through its enterprise sales team.

If your website platform doesn't offer script injection or tag managers, you may have no choice but to edit theme files. In that case, the manual integration guide is the right reference.

Frequently asked questions

Do I need a Seatext account before adding the snippet?

Yes. Seatext says you need a SEATEXT AI account before you can install the script.

Can I use the same Seatext account on my staging and live sites?

No. Each account is linked to one primary URL. Use a separate account for each domain.

The snippet is in my page source. Why don't I see changes?

Because the AI remains inert until activated. Open the agent list and activate the ones you need.

How do I check my work after installing?

View the live page source and search for SEATEXT. Clear caches first, and make sure you saved the snippet.

Is localhost okay for testing Seatext?

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

What if my installation still doesn't work?

Go through the diagnosis order again, then read the official integration guide to confirm you used the right method and domain.

To test the SeaText AI JavaScript integration, use browser developer tools to check for console errors, test the AI functionality, and ensure the API calls are successful. You also need one visual confirmation: the SeaText logo at the top of the page must show your website name.

Readiness Checklist

Use this checklist before you start. Every item below is required for a reliable test.

• A SeaText AI account with a valid API key.
• Ability to edit your site's HTML or inject custom JavaScript.
• Modern browser with developer tools (Chrome, Firefox, or Edge).
• A real domain that is not localhost.
• Access to every page you want to test.
• Page refreshed several times before the final wait.
• At least 40 seconds of dwell time after the last refresh.
• SeaText logo showing your site name at the top of the page.

Why Testing the Integration Matters

A JavaScript integration can look installed and still fail silently. The script may load, but it may never link to your account. That leaves you with a page that appears ready while the AI does nothing.

Testing catches the three common failure points:

• Broken API keys that stop the script from authenticating.
• Wrong page placement that prevents the script from starting.
• Domain mismatches that keep your account from recognizing the site.

The source pack says the installation process is secure and the AI remains inert until activated. In practical terms, nothing changes on your website until the test passes and you activate agents. A silent failure can therefore last for days. The test below gives you a clear pass or fail signal.

How the SeaText Script Works

SeaText gives you a JavaScript snippet after you create an account. In the dashboard, copy the code provided by SEATEXT AI.

Paste the snippet just before the closing </body> tag on every page you want to use. If you use a CMS, put it in the custom-code field. On WPEngine, install the WP Engine plugin that lets you add custom JavaScript, then apply it across all pages.

The snippet is the connector between your website and your SeaText account. It tells the service which primary URL should be associated with visitor traffic. Each SeaText account is linked to a single primary URL.

The script does not rewrite content by itself. The source pack is explicit: the AI remains inert until activated. The snippet only becomes active after you test, confirm the connection, and turn on the agents you need in the Main AI Hub. Because the AI remains inert, you cannot fully test agent behavior until you activate an agent there. The integration test proves the connection; the agent activation proves the behavior.

What the 40-Second Activation Means

The SeaText integration guide gives one rule that many people skip: visit or refresh your website several times and stay on your page for at least 40 seconds. This action activates the AI and links it to your account.

The 40 seconds are a handshake window. The script needs time to load, register the page view, and send the connection signal to SeaText. If you leave before the window closes, the handshake may never finish.

Refresh several times first. This prevents an old cached page from being the only signal SeaText receives. Then stay for the full 40 seconds. Use a stopwatch if you have to.

Verifying the Visual Confirmation

After the 40-second activation, wait at least five minutes. Then look at the top of the page. You should see the SeaText logo and your website name next to it.

The official instruction says: “Wait at least five minutes until you see your website name displayed next to the SEATEXT logo at the top of this page. This indicates that your website is connected and ready to proceed to the next step.”

Do not skip this step. The logo is the only visible proof that the script is connected to the correct account. If you move to agent activation without it, you may activate agents on a site that SeaText cannot reach.

Troubleshooting When the Logo Does Not Appear

If the logo does not appear within 10 minutes, work through this list in order.

1. Open the browser console. Red errors that mention SeaText usually point to a missing API key, blocked script, or incorrect placement.
2. Open the Network tab and check for failed calls to SeaText. A successful test shows API calls returning without errors.
3. Confirm the URL in the browser matches the primary URL in your SeaText account. A www version and a non-www version can create a mismatch.
4. Confirm you are not on localhost. Localhost is restricted for security reasons and will not link to your account.
5. Check that the snippet is placed just before the closing </body> tag. A script placed in the <head> can block rendering or fail to connect.
6. Refresh the page several times again and stay for another 40 seconds.
7. If the logo still does not appear after 10 minutes, contact SeaText support immediately. This could indicate an installation problem on your platform.

Account and Domain Restrictions

SeaText links each account to one primary URL. If you need SeaText on multiple domains, create a separate account for each domain.

This includes development and production pairs. For example, a development domain and a production domain need two different SeaText accounts.

Localhost is restricted for security reasons. Use a valid, real domain instead. Dynamic development domains may not function because SeaText cannot reliably associate traffic with your account.

If you run several websites, create one account for each website. This keeps agent settings, reporting, and activation separate by domain.

Frequently Asked Questions After Testing

How do I know my API key is valid?

If the script loads without console errors and the logo appears, your API key is working. If you see a key error, copy the full snippet from your dashboard again and repeat the test.

Can I test on a staging site?

You can test on staging if the staging site uses a real domain. Localhost is restricted for security reasons. Dynamic development domains may not work. If the staging domain is different from production, it needs its own SeaText account.

What should I do after the logo appears?

Go to the Main AI Hub and activate the AI agents you need. Click Configuration to adjust the AI parameters. SeaText also provides an initial round of automatic translations and variants for testing. You can review or edit them under Variants Edit in your account.

Why did the logo appear but the AI did not change anything?

The AI remains inert until activated. The logo only proves the connection. You still need to activate agents from the Main AI Hub before the AI starts working.

Can I test the AI before activating agents?

No. The integration test only proves the script is installed and linked. The AI functionality starts after you activate an agent from the Main AI Hub.

How long should I wait before contacting support?

If the logo does not appear after 10 minutes, contact support immediately. The delay may mean the script was not installed correctly on your platform.

Domain management in SeaText is under Settings > Domains in the dashboard. That is where you will see the primary URL linked to your account. If you came looking for a registrar-style panel with DNS records, you are in the wrong place: this setting is about which website address SeaText associates with your account.

SeaText keeps this setting deliberately small. The source documentation says each SEATEXT AI account is linked to a single primary URL. That one rule drives most of the decisions below.

What the domain settings control

The domain setting has one main job. It identifies the website that the account will work on. You use it to confirm the primary URL before you copy the JavaScript code and add it to your site.

For a single website, the workflow is short. Check the primary URL, install the code on that domain, then activate the script. The docs note that the installation process is secure and the AI remains inert until activated.

For multiple websites, the workflow changes. You do not add another domain to the same settings page. You create a separate account for each website.

Why one account is tied to one primary URL

SeaText runs from a JavaScript snippet placed on your site. That snippet needs to send data back to the correct account. The platform links traffic to a primary URL so it knows which website the data belongs to.

Because each SeaText account is linked to a single primary URL, the primary URL acts like the identity of the account. It is not a preference you can flip later to cover a second site.

What changes if you ignore this? Traffic on an unlinked domain may not be associated with your account. The documentation warns that dynamic development domains may not function properly, because SeaText may be unable to reliably associate traffic with your account. That is the same logic you should apply to any domain that does not match the primary URL.

When you need a separate account

Create one SeaText account for each domain you want to use. This is the rule from the source pack: if you need to use SEATEXT AI on multiple domains, you must create separate accounts for each domain.

• Multiple websites: each website gets its own account.
• Development and production: a development domain and a production domain are two separate accounts.
• Client sites or separate brands: each client domain gets its own account.

Example: you operate shop.example.com and shop.example.org. Those are two domains, so you need two accounts. Example: you test on dev.example.com and launch on www.example.com. Those are also two accounts if both domains are used.

What the restrictions mean in practice

SeaText restricts development URLs such as localhost for security reasons. That is not a temporary bug; it is a boundary.

If you plan to test before launch, use a valid, real domain. Dynamic development domains may not work reliably because SeaText may not be able to associate traffic with your account. Stable, real domains are the safer choice.

How to check the domain setting before installation

1. Sign in to your SeaText account.
2. Open Settings, then open Domains.
3. Confirm the primary URL matches the website where you will paste the JavaScript code.
4. If the domain shown is not the site you are about to install on, set up a separate account for the correct domain instead of reusing this one.
5. Copy the JavaScript code from SeaText, paste it into your site, and save the changes.
6. Preview your site and inspect the page source to confirm the code is present.

Step 4 is the one people skip. Reusing one account across several domains may create the wrong association. The source pack says separate accounts for separate domains.

Key facts at a glance

SeaText domain settings vs registrar domain management

When people search for domain management, they often expect DNS records, nameservers, renewals, and transfers. Those controls belong to the registrar or hosting provider, not to SeaText.

SeaText's Settings > Domains answers a different question: which website is this account attached to? Keep the two tools separate. Use the registrar for DNS. Use SeaText's domain setting to confirm the primary URL.

Practical scenarios for choosing a domain

• Scenario A: one production website. Confirm the primary URL, install the snippet, and activate the agents you need. Small setup, one account.
• Scenario B: staging plus production. Use a real staging domain and a real production domain. Create one account for each. Check that the staging domain is stable before you rely on it.
• Scenario C: multiple client websites. Create one account for each client domain. That keeps traffic, settings, and reports separate.

Limitations and boundary cases

• One account is tied to one primary URL. That is the central limit.
• localhost is restricted. Do not use it as the domain for a live account.
• Dynamic development domains may not work reliably.
• Adding another website means creating another account, not adding a second domain to an existing one.
• DNS and nameserver settings are not part of this page. Handle those at the registrar.

Terms you may see

Primary URL

The single domain linked to a SeaText account. It is the website address the account is expected to work on.

Account

The login and installation identity for one website. One account, one primary URL.

Code snippet

The JavaScript code you copy from SeaText and place on your site before activation.

Activation

The point when the AI script starts working. The script remains inert until activated.

Development domain

A testing address. Localhost and dynamic development domains have restrictions or may not work reliably.

Frequently asked questions

Where exactly is Settings > Domains in SeaText?

Sign in, open Settings, then open Domains. That is the account-level location for the primary URL.

Can one SeaText account manage two domains?

No. Each account is linked to a single primary URL, and using multiple domains requires separate accounts.

Can I use localhost for testing?

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

Why might a dynamic development domain fail?

SeaText may be unable to reliably associate traffic with your account. If traffic is not associated, the script may not behave as expected.

Do I need a separate account for each website?

Yes. The source pack says to use SEATEXT AI on several websites, create one account for each website.

What if the domain in Settings doesn't match my site?

Do not install the code on a mismatched domain. Use an account whose primary URL matches the site, or create a new account for that domain.

When you add a new Shopify domain to SeaText AI, you create a separate SeaText account for that domain, paste the provided JavaScript snippet into your theme's theme.liquid file, and then activate whichever AI agents you need — such as conversion optimization, translation, or bot protection. Each SeaText AI account is linked to a single primary URL, so every additional store gets its own account.

What "adding a domain" actually means in SeaText AI

SeaText AI does not let you manage multiple websites from one dashboard. Instead, each domain — each Shopify store — gets its own SeaText account. The account creation process gives you a unique JavaScript snippet. That snippet is what connects your store to SeaText's AI agents. Until you paste that snippet into your theme and save, the AI remains inert and does not touch your content.

This design keeps data isolated. Traffic, experiments, and translations for one store never leak into another. It also means billing, user seats, and agent configurations stay per-store.

Prerequisites before you start

• A live, publicly accessible Shopify domain. Development URLs such as localhost are restricted for security reasons, and dynamic development domains may not function properly because SeaText AI cannot reliably associate traffic with your account.
• Admin access to the Shopify store so you can edit theme code.
• A SeaText AI account created specifically for this domain. If you already use SeaText on another store, you still need a new account for the new domain.

Step-by-step: Create account, install on Shopify, activate agents

1. Create the SeaText account for the new domain. Go to SeaText and sign up using the new store's primary URL. You will receive a JavaScript snippet unique to that account.
2. Access your Shopify theme code. In Shopify admin, navigate to Online Store > Themes. Click the three-dot menu next to your active theme and choose Edit code.
3. Open theme.liquid. In the left file list, open the Layout folder and select theme.liquid.
4. Paste the SeaText snippet. Place the JavaScript code just before the closing </head> tag (or wherever the SeaText documentation instructs for your setup).
5. Save the file. Click Save to preserve changes.
6. Verify installation. Visit a page on your store, open browser developer tools, and confirm the SeaText script appears in the HTML source.
7. Activate agents. Log into your new SeaText dashboard. Enable the agents you want — for example, the CRO Optimizer, Website Translation Agent, Bot Protection Agent, or Google Ads Optimization Agent. Each agent can be toggled on independently.

If you also want to optimize product descriptions, locate your product template (usually product.liquid or product-template.liquid) and wrap the description output with the SeaText data attribute as described in the documentation.

Common restrictions to know

• No localhost or staging subdomains. SeaText blocks development URLs for security. Use a real, public domain.
• Dynamic preview URLs may fail. Shopify's temporary preview links (like myshopify.com preview URLs) can change, breaking the domain-to-account association.
• One account per domain. You cannot add a second primary URL to an existing SeaText account. Plan for separate logins, separate billing, and separate agent settings per store.

What happens after installation

Once the snippet is live and agents are activated, SeaText starts working in real time:

• CRO Optimizer analyzes visitor reading behavior and tests copy variants using multi-armed bandit allocation, shifting traffic to better-performing wording within hours.
• Website Translation Agent translates pages, headlines, buttons, and offers into up to 125 languages, with control over what gets translated.
• Bot Protection Agent detects suspicious paid traffic, records evidence, and generates refund-ready reports for Google, Meta, TikTok, and Reddit.
• Google Ads Optimization Agent rewrites landing page headlines, offers, and CTAs to match the keyword that triggered each ad click.
• Visitor Source Rewrite Agent adapts page copy for visitors arriving from Google, Meta, email, referrals, and other sources.
• Ecommerce Product Copy Agent optimizes product names, descriptions, and CTAs, scaling the variants that drive more add-to-carts and sales.

All agents run automatically once activated. You can edit rewrites manually or let the AI continue optimizing.

Managing multiple Shopify stores

If you run several Shopify stores — for example, a main brand store, a wholesale store, and a regional store — you will have a separate SeaText account for each. There is no multi-store dashboard. You log into each account individually to check reports, adjust agent settings, or review translation overrides. This separation keeps experiments clean: a winning headline on your US store does not auto-apply to your EU store unless you choose to replicate it.

SeaText's homepage notes the platform is "trusted by 2,500+ brands, ecommerce teams, and growth agencies," and each store follows the same one-account-per-domain model.

Key facts

Limitations

• No centralized multi-store view. You must log into each account separately.
• No support for localhost or non-public domains. You cannot test on a private staging environment before launching.
• Dynamic development domains (like Shopify preview links) may not work reliably.
• Each account has its own billing. Volume discounts across stores are not mentioned in the source materials.
• Agent configurations do not sync across accounts. You replicate settings manually.

Terminology

• Primary URL — The single domain a SeaText account is bound to.
• JavaScript snippet — The unique code block that connects a store to SeaText's AI agents.
• Agent — A specialized AI module (e.g., CRO Optimizer, Translation Agent, Bot Protection Agent) that you activate per account.
• Multi-armed bandit — An algorithm that allocates more traffic to better-performing copy variants in real time, rather than splitting traffic 50/50.
• Reading telemetry — Millisecond-level tracking of how visitors scan, dwell, and re-read page sections, used to detect copy friction.

FAQ

Can I use one SeaText account for my main store and a development store?

No. Development URLs such as localhost are restricted, and each SeaText account is linked to a single primary URL. You need a separate account for each live domain.

Does SeaText work on Shopify's myshopify.com preview links?

Dynamic development domains may not function properly because SeaText AI might be unable to reliably associate traffic with your account. Use a real, custom domain.

What agents are available for a new Shopify store?

You can activate any combination: CRO Optimizer, Website Translation Agent (125 languages), Bot Protection Agent, Google Ads Optimization Agent, Visitor Source Rewrite Agent, Ecommerce Product Copy Agent, AI A/B Testing Agent, AI Personalization Agent, ChatGPT Brand Visibility Agent, Scroll Slowdown Agent, and Free Website Chat Agent.

Is there a free trial for the new domain?

Yes. SeaText offers a free 1-month pilot trial for new accounts.

How long does installation take?

SeaText states you can add the script to your site in under 1 minute. The Shopify theme edit adds a few more minutes.

Can I manage all my stores from one dashboard?

No. Each store has its own SeaText account and dashboard. There is no multi-store view.

What if I want the same translation settings across stores?

You configure translation overrides and preferences separately in each account. Settings do not sync automatically.

Seatext AI handles product page optimization through autonomous agents that analyze visitor reading patterns, match ad keywords, generate copy variants, and allocate traffic to winning versions — all without manual A/B test setup. Manual optimization means your team writes, tests, and updates product descriptions, headlines, and CTAs by hand, typically using traditional A/B testing tools that need thousands of visitors per variant to reach statistical significance.

How Seatext AI Optimizes Product Pages

Seatext deploys 20 autonomous agents once you paste a JavaScript snippet into your site's theme.liquid file on Shopify (or equivalent on other platforms). The Ecommerce Product Copy Agent optimizes product names, descriptions, and CTAs. The AI CRO Reading Analysis Agent (z8y) tracks millisecond-level reading behavior — eye-line dwell velocity, friction points where visitors re-read, and scroll deceleration at key sections — to identify exactly where copy loses buyers. Instead of 50/50 traffic splits, a multi-armed bandit algorithm pushes 80%+ of traffic to winning variants within hours. The Google Ads Optimization Agent rewrites the landing page in real time to mirror the exact keyword a visitor searched, so one product page becomes a keyword-matched experience for every paid click. The Website Translation Agent renders all page elements in up to 125 languages without a separate localization project. The Bot Protection Agent flags suspicious paid sessions and compiles evidence for ad platform refund claims.

What Manual Product Page Optimization Involves

Manual optimization starts with a content audit: identifying low-converting product pages, analyzing heatmaps, reviewing customer support tickets for objections, and drafting new copy. You then build test variants in a tool like VWO, Optimizely, or Google Optimize, configure 50/50 or 90/10 splits, and wait for statistical significance. On a page with 5,000 monthly visitors, a single headline test can take 3–4 months. You repeat this for each element — headlines, bullets, CTAs, trust badges, shipping copy. For paid traffic, you either build dedicated landing pages per keyword cluster or use dynamic text replacement, both of which require developer time to maintain. Translation means exporting copy, sending to agencies, reviewing, re-importing, and QAing each language. Bot detection and refund claims are separate workflows, often manual or handled by a different vendor.

Key Trade-offs in Practice

Speed vs. oversight. Seatext goes live in minutes; the first AI-generated variants appear within hours. Manual optimization takes weeks before the first test launches. If you need results this quarter, Seatext wins. If your legal or brand team must approve every comma, manual gives that gatekeeping — though Seatext lets you review and edit AI drafts before they publish.

Low traffic vs. high traffic. The source pack notes that 90% of B2B and niche ecommerce sites lack the volume for reliable A/B tests. Seatext's reading telemetry extracts signal from every session, not just conversions. Manual testing only makes economic sense when you have 20,000+ monthly visitors per test page and stable seasonality.

Scale of keyword matching. A typical ecommerce brand bids on 100+ keywords. Building 100 manual landing pages is unrealistic. Seatext's Google Ads Agent handles this automatically — the moment a visitor clicks an ad, the page rewrites to match that keyword. Manual dynamic insertion covers headlines but rarely extends to product blocks, offers, and CTAs holistically.

International expansion. Adding one language manually costs $0.10–$0.25 per word plus project management; 125 languages is a six-figure program. Seatext includes translation in the base agent suite. If you only sell in English, this doesn't matter. If you're testing a new market, Seatext lets you validate demand before committing to human localization.

When to Choose Each Approach

Choose Seatext AI if:

• You have product pages that get traffic but convert poorly, and you don't have a dedicated CRO team
• You run Google Ads or Meta campaigns with many keywords and want each click to land on a matching page
• Your traffic is too low for traditional A/B testing to reach significance in a reasonable timeframe
• You want to test international markets without hiring translators upfront
• You want bot detection and ad refund evidence built in
• You prefer reviewing AI suggestions over writing test hypotheses from scratch

Choose Manual Optimization if:

• Your brand voice is highly distinctive and any AI-generated phrasing feels off-brand even after editing
• You have a mature CRO program with statistically valid tests running continuously
• You only optimize a handful of high-revenue pages where every word has legal or regulatory implications
• You have in-house copywriters and CRO specialists with bandwidth to run 10+ tests per quarter
• You need full audit trails for compliance (e.g., pharma, finance) where AI decision logic must be explainable

Implementation Considerations

Seatext integration on Shopify: access Online Store > Themes > Actions > Edit Code, open theme.liquid in the Layout folder, paste the JavaScript snippet before the closing </head> tag, and save. For product description optimization, wrap the description output in product.liquid or product-template.liquid with the required data- attribute. Each domain needs its own Seatext account; development URLs like localhost are restricted. The AI remains inert until you activate agents in the dashboard. A free 1-month pilot trial is available. Manual optimization requires no code changes but does need a testing tool subscription, developer support for variant deployment, and analytics configuration.

Limitations and Caveats

Seatext's claims — +35% conversion lift from Google Ads intent matching, up to 20% ad spend recovery from bot clicks, 2,500+ brands using the platform — come from the vendor's own materials. Independent third-party benchmarks are not in the source pack. The AI's reading telemetry (z8y) and multi-armed bandit allocation are proprietary; you cannot export the raw model or retrain it on your own data. Creative control is "edit or approve" — you cannot fully disable AI generation for a specific element without turning off the agent. Pricing details are not public in the source pack; the homepage and feature pages link to a pricing page and a free demo. Manual optimization's limitations are well-documented in CRO literature: sample size requirements, test duration, winner obsolescence due to seasonality or creative fatigue, and the operational burden of continuous hypothesis generation.

Frequently Asked Questions

Can I run Seatext and manual tests at the same time?

Yes. Seatext's agents operate on the live page. You can still run your own A/B tests on top, though traffic allocation gets complex. Most teams pick one primary optimization method per page to avoid interference.

Does Seatext work on platforms other than Shopify?

The source pack documents Shopify integration specifically. The JavaScript snippet approach works on any site where you can inject code in the <head>, but platform-specific instructions for WooCommerce, BigCommerce, Magento, or headless builds are not detailed in the provided sources.

What happens if the AI writes something factually wrong about my product?

You can review and edit AI-generated variants before they go live. The source pack describes an "edit rewrites manually or with AI" step. There's no automatic fact-checking against your PIM or feed; you own the final publish decision.

How does the bot protection agent build refund evidence?

For each paid visit, Seatext checks for bot signals, saves suspicious session records, and turns that evidence into a refund-ready report submittable to Google, Meta, TikTok, or Reddit. The source pack doesn't specify the detection methodology or success rate of claims.

Is there a minimum traffic threshold for Seatext to work?

The source pack emphasizes that reading telemetry works on low-traffic sites where A/B testing fails. No minimum visitor count is stated. The multi-armed bandit algorithm needs some traffic to allocate, but the claim is that it functions where traditional testing cannot.

Can I use Seatext for just translation without the CRO agents?

The Website Translation Agent is one of 20+ agents. The source pack describes "one-click activation" per agent, implying you can activate only Translation. However, the pricing model (bundle vs. à la carte) isn't detailed in the sources.

What's the typical timeline to see measurable results?

The source pack cites "within hours" for multi-armed bandit allocation to winners and "Month 1 / Month 6 / Month 12" progression graphics. No specific median time-to-lift is provided. Manual A/B testing typically shows first conclusive results at 3–4 months on low-traffic pages.

If your internet disconnects during the 40-second activation wait, the activation usually does not finish. The visit never gets recorded as a complete activation event, so SEATEXT cannot link your website to your account. Reconnect to the internet and repeat the process: visit or refresh your website and stay on the page for the full 40 seconds.

This article explains why that happens, how to diagnose it, and what to do next. If you ignore the failed wait, the script stays inert and none of the agents can run. You will only discover the issue later when nothing changes on your site.

What Actually Happens When the Connection Drops

SEATEXT's instructions say you need to visit or refresh your website and stay for at least 40 seconds so the AI can be activated and linked to your account. If the connection drops before that full stay, the backend may not reliably associate the traffic with your SEATEXT account.

Hypothetical scenario: You add the SEATEXT JavaScript, open your site, and at second 25 your Wi-Fi goes down. The page might still be visible from cache, but the activation event is incomplete. The fix is simple: reconnect and repeat the 40-second wait.

There is no penalty for a failed activation attempt. The script remains inert until activation succeeds, so your website content is not changed by a failed try.

How the 40-Second Activation Wait Works

SEATEXT activation is a short sequence that connects the script on your website to your SEATEXT account. The 40-second stay is the part where that connection is confirmed.

1. Create a SEATEXT AI account if you do not have one.
2. Copy the JavaScript code from the General Integration page and add it to your site. WPEngine users should install the WP Engine plugin that allows custom JavaScript on all pages.
3. Visit or refresh your website several times. Stay on the page for at least 40 seconds. This activates the AI and links it to your account.
4. Wait at least five minutes. Look at the top of the SEATEXT page for your website name next to the SEATEXT logo.
5. If the name does not appear, wait until 10 minutes have passed, then contact SEATEXT support.

The AI does nothing until it is activated. That means a failed activation does not start rewriting your site or publishing changes.

Diagnosis Order: Find Where Activation Broke

When activation fails, work through this order. It separates a connection problem from a setup problem.

1. Check your internet connection. If Wi-Fi, Ethernet, or your VPN dropped, the 40-second session was not continuous. Reconnect and retry.
2. Check whether your website name appeared. If not, activation has not finished yet.
3. Confirm you stayed for 40 seconds. Leaving the page early, refreshing too many times, or switching tabs can interrupt the visit. Treat it as an incomplete activation if you are not sure.
4. Confirm you are using a real domain. localhost is restricted. Dynamic development domains may not work because SEATEXT cannot reliably associate traffic with your account.
5. Confirm the account matches the domain. Each account is linked to a single primary URL.
6. If all of the above look correct, wait 10 minutes and then contact support.

Most Likely Causes and Fixes

This table shows likely causes. The first row is the one that matches the question directly: an internet disconnect during the wait.

Step-by-Step: Retry After a Disconnect

1. Reconnect to the internet. Confirm your connection is stable before starting again.
2. Open your website. Do not use localhost. Use the real domain linked to your SEATEXT account.
3. Refresh your website several times. The instruction says visit or refresh several times; do at least one full 40-second stay.
4. Stay on the page for at least 40 seconds. Do not switch tabs or leave the page during that window.
5. Go back to SEATEXT and wait five minutes. Look for your website name next to the SEATEXT logo.
6. If nothing appears after 10 minutes, contact support.

If your internet is unreliable, repeat the process until you get one uninterrupted 40-second visit.

Key Facts at a Glance

The table below sums up what the SEATEXT instructions say about activation.

Limitations and Edge Cases

This guidance covers activation, not normal post-activation use. If your site is already showing the website name in SEATEXT, an internet drop afterward is a separate network issue, not an activation issue.

If the disconnect happens after the 40-second wait but before the five-minute check, the important visit may already be recorded. Do not immediately restart from zero. Wait and look for your website name. If it does not show up, repeat the 40-second wait.

The instructions are specific about domains. Development URLs such as localhost are restricted. Dynamic development domains may not function because SEATEXT may not be able to reliably associate traffic with your account. In that case, no number of 40-second waits will help until you switch to a real domain.

Each SEATEXT account is tied to one primary URL. If you test on a development domain and a production domain, create a separate account for each domain.

Activation Terms, Briefly

• Activation wait: The period during which you visit or refresh your website and stay for at least 40 seconds so SEATEXT can link the site to your account.
• Primary URL: The single website URL tied to a SEATEXT account.
• Inert: The script is loaded but does not change your content until activation succeeds.
• Dynamic development domain: A temporary URL that changes; SEATEXT may not reliably recognize traffic from it.

Frequently Asked Questions

Why does SEATEXT need 40 seconds?

SEATEXT's instructions say that staying on the page for at least 40 seconds after visiting or refreshing activates the AI and links it to your account. It is the recognition step for the connection.

What if I disconnect at second 39?

Treat it as incomplete. Reconnect and repeat the 40-second stay. It costs less than a minute and avoids the risk of moving forward with an unactivated script.

How do I know activation worked?

After at least five minutes, your website name should appear next to the SEATEXT logo at the top of the SEATEXT page. If it does not appear after 10 minutes, contact support.

Can I activate SEATEXT on localhost?

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

Do I need a separate account for each website?

Yes. Each SEATEXT account is linked to a single primary URL. Use one account per website or per domain.

What if my internet drops after the 40-second wait?

If the website name already appeared, activation is complete. A later internet drop is a normal network issue, not an activation failure.

What does “connected but not working” mean?

You see a green “connected” indicator in the SeaText dashboard. But the AI agents do not rewrite copy, translate pages, or block bot traffic. This is a false positive. The dashboard only confirms that the script reached SeaText’s servers. It does not mean the AI is active on your site.

The connection indicator shows your domain name next to the SeaText logo. That means the script loaded successfully. However, the AI agents need to be activated separately. They also need a clean script environment to run. JavaScript errors, an expired API key, or a cached version of the page can block them.

In short, “connected” is not the same as “working”. You need to diagnose why the AI agents are not executing.

Why does this happen? (Root causes)

Five main reasons cause this false positive connection:

• Script not installed correctly. The JavaScript snippet must be placed before the closing </head> on every page. If you use WP Engine, install the official plugin. The script must be present on all pages, not just the homepage.
• JavaScript errors. Other plugins or themes can conflict with the SeaText script. Open the browser console (F12) and look for red error messages. They often reveal the exact conflict.
• Expired or missing API key. The AI needs a valid API key to function. Check the dashboard’s API settings. If the key expired, generate a new one.
• Cache or CDN serving an old version. If your site uses a caching plugin or a CDN (like Cloudflare), it may deliver a page without the SeaText script. Purge all caches.
• Activation wait time not met. After installing the script, you must stay on any page for at least 40 seconds. Then wait five minutes for the dashboard to update. Without this, the connection may not fully register.

Additionally, SeaText links one account to one primary URL. If you use multiple domains (e.g., a development domain and a production domain), you need separate accounts per domain. Localhost and other development URLs are restricted for security reasons. They will not show as connected.

Step-by-step diagnostic sequence

Follow this order to find the exact cause. Do not skip steps.

1. Open the SeaText General Integration page. Copy the latest JavaScript code from General Integration.
2. Reinstall the script. Paste it into your site’s global header (before </head>). If you use WP Engine, use the provided plugin. Save and publish.
3. Visit any page on your site. Stay on that page for at least 40 seconds. This activates the AI and links it to your account.
4. Wait five minutes. Refresh the SeaText dashboard. Look for your site name next to the SeaText logo at the top. If it appears, the connection is established.
5. Check the browser console. Open developer tools (F12) and go to the Console tab. Resolve any red error messages. Common errors: “SeaText is not defined”, “API key missing”, or “Failed to load script”.
6. Clear your cache. Clear the browser cache, or use an incognito window. Also purge any CDN or site cache plugin.
7. Verify the API key. Log into the dashboard, go to API settings. Ensure the key is active and not expired. If expired, generate a new key and update the script.
8. Test again. Reload the page. Wait 40 seconds. Check the dashboard for green status on each agent.

If the site name still does not appear after 10 minutes, contact support immediately. This indicates a deeper installation issue.

How to fix each common cause

Script not loading or placed in the wrong location. Reinstall from the General Integration page. Ensure the script appears before the closing </head> tag. Use the WP Engine plugin if you are on that platform. The script must be on every page, not just the homepage.

JavaScript errors. Open the console and look for errors. Common fix: temporarily disable other plugins or scripts to isolate the conflict. If the error is “SeaText is not defined”, the script did not load. Check your header file for missing code.

Expired or missing API key. In the dashboard, navigate to API settings. Copy the key. Ensure it is included in the script snippet. If you recently changed the key, update the script on your site. The key is essential for AI to function.

Cache or CDN serving an old version. Clear your site’s cache plugin (e.g., WP Rocket, W3 Total Cache). If you use a CDN, purge the CDN cache. Also clear your browser cache or test in incognito mode. This ensures the latest script is served.

Insufficient activation wait time. After installing the script, stay on a page for at least 40 seconds. Then wait five minutes for the dashboard to update. Do not navigate away during those 40 seconds. The AI needs to see a real visitor session to activate.

Multiple domains or development URLs. Each domain needs its own SeaText account. Development URLs like localhost or staging sites are not allowed. Use a real domain for testing. If you need to test on a development domain, contact support for options.

How to verify the AI is truly active

After the steps above, you should see real-time changes. For example, headlines may rewrite, translations may appear, or bot traffic alerts may show. The easiest way to verify is to check the agents panel.

Go to the SeaText homepage. Log in and view the agents panel. Each agent you activated should show a green “Active” status. If an agent shows “Inactive” or “Error”, click on it to see details.

You can also test by visiting a page on your site. Look for changes in the page content. For example, if you activated the Translation Agent, the page may appear in a different language. If you activated the CRO Optimizer, headlines may change based on visitor source.

If you still see no changes after 10 minutes, the AI is likely still blocked. Re-run the diagnostic sequence. Pay special attention to the console errors and API key.

Frequently asked questions

• Why does the dashboard say “connected” but nothing changes on my site? The connection indicator only tells you the script reached SeaText’s servers. The AI agents must be activated separately. Also, the script must run without errors. Check the console and agent activation status.
• How long should I wait after installing the script? Stay on a page for at least 40 seconds. Then wait five minutes for the dashboard to update. If you don’t see the site name after 10 minutes, contact support.
• Can a CDN prevent the AI from working? Yes. If the CDN caches a page without the new script, the AI cannot run. Purge the CDN cache and also clear your browser cache.
• Do I need a separate account for each domain? Yes. SeaText AI links one account to one primary URL. Using multiple domains requires separate accounts. Development URLs like localhost are restricted.
• What if I see JavaScript errors but can’t fix them? Common errors are caused by conflicting plugins. Temporarily disable other plugins one by one to find the conflict. You can also contact SeaText support with the console error logs.

If you have completed all steps and the AI still does not work, contact SeaText support. Provide them with the console errors, the exact URL where the script is installed, and a screenshot of the dashboard connection status. Support can check backend logs for further issues.

SeaText AI usually does not delay on its own. The most common reason a store seems stuck is an unfinished setup step: the JavaScript snippet was pasted but not saved, the data- attribute was never added to the product description template, or the agents were never activated in your dashboard.

A smaller number of cases come from an account/domain mismatch, a development URL that SeaText blocks, or Shopify taking a few extra seconds to process the theme change. The good news is that each cause has a different fix, and you can find it with one short diagnostic sequence.

Why setup mistakes look like delays

SeaText installs as a JavaScript snippet in your theme.liquid file. The source integration page says the installation is secure and the AI remains inert until activated. That design protects your store, but it also means a single missed step produces no visible change at all.

When a setup step is missing, the effect is identical to a delay: your store looks the same and nothing happens. The difference matters because waiting will not fix a missing snippet. You need to find the unfinished step and complete it.

The four causes that explain most activation delays

• The agents were never activated. A correctly installed script still does nothing until you choose which agents to turn on in the SeaText dashboard.
• The snippet was not saved in theme.liquid. Pasting code and closing the editor without clicking Save means the theme still runs without SeaText.
• The data- attribute was not added to the product template. SeaText uses that marker to find the product description. Without it, the script has no place to work.
• The account's primary URL does not match the store, or you are using a restricted development URL. Each account is linked to a single primary URL, and localhost is blocked for security reasons.

Diagnostic sequence: check these in order

Work through this list top to bottom. It is ordered from the most common cause to the least common.

1. Confirm you have a SeaText account. The integration guide says: “Before you can install the script, you need a SEATEXT AI account.” Without an account, there is nothing to activate.
2. Open your active theme. In Shopify admin, go to Online Store > Themes, click Actions > Edit Code, then open Layout > theme.liquid. Look for the SeaText JavaScript snippet.
3. Save the file after any change. “Once the code snippet has been successfully pasted, click on the 'Save' button to preserve your changes.” An unsaved edit is the same as no edit.
4. Check the product template. Open product.liquid or product-template.liquid and confirm the data- attribute is wrapped around the product description output.
5. Verify the account's primary URL. Each account is linked to one primary URL. That URL must be your real store domain, not a staging or localhost address.
6. Activate the agents. Log in to your SeaText dashboard and activate the autonomous agents you need. The script stays intentionally inert until this step.

After each fix, save the theme, reload a product page, and inspect the HTML source with your browser's developer tools. If the snippet and attribute are present, move to the next checkpoint.

What looks like a delay but is actually a restriction

Some cases never finish because SeaText is deliberately blocking the setup, not because it is slow.

• Multiple domains. If you use a development domain and a production domain, you need a separate account for each. One account cannot cover both.
• localhost or dynamic development URLs. Development URLs such as localhost are restricted for security reasons. A dynamic development domain may not work because SeaText cannot reliably associate traffic with your account.

These restrictions do not resolve with time. You have to change the URL or create another account.

What does not cause a delay

Clearing your browser cache, disabling other Shopify apps, or waiting longer will not add the snippet to theme.liquid. If the script and data- attribute are already present, the next likely cause is agent activation, not a Shopify outage.

If the agents are active and the page still shows no change, go back to the beginning of the diagnostic sequence. The missing step is usually simpler than it seems.

Scope: what activation actually includes

Activation means the SeaText script is installed and at least one agent is switched on. It does not mean every agent runs at once. The dashboard lets you choose which autonomous agents you need, from translation to product copy to CRO.

Until you activate an agent, the script is inert. That is intentional: it protects your content from changes you did not ask for. It also means a store with a script but no active agents will look exactly like a store with no script at all.

Key facts: SeaText AI on Shopify

Terminology that helps when troubleshooting

• theme.liquid – the Shopify layout file where the SeaText JavaScript snippet is placed.
• data- attribute – the marker added around product description output so SeaText can read it.
• primary URL – the single real domain linked to a SeaText account.
• agent – a specific SeaText function that you turn on after the script is installed.
• inert – installed but not active; the script does not change content until you activate an agent.

Limitations and exceptions

The above advice assumes you are editing the active theme. If you pasted the snippet into a duplicate theme or a theme that Shopify is not currently using, the product page will not load the script.

Another exception is a store behind a dynamic development domain. Even with a valid-looking URL, SeaText might not be able to reliably connect traffic to your account. In that case, use a real, stable domain for testing.

If every item in the diagnostic sequence is correct and the agents are active, then the remaining variable is Shopify's own processing of the theme save. Save the theme once, give it a moment, and reload the page. If nothing changes, repeat the sequence rather than assuming a server outage.

FAQ

Why did SeaText activate on my staging site but not on my live store?

Each account is linked to one primary URL. A staging domain and a live store are different domains, so each needs its own SeaText account. Development URLs such as localhost are restricted for security reasons.

How long should I wait before troubleshooting?

Do not wait long. The bottleneck is usually a missing setup step, not a queue. Save theme.liquid, check for the snippet, confirm the data- attribute, and activate agents. If all three are correct, activation is complete.

Does SeaText change my product descriptions before I activate agents?

No. The source pack says the AI remains inert until activated. It should not alter content before you turn on an agent.

Can I use the same SeaText account for two stores?

No. The source pack says to use separate accounts for separate domains. The same rule applies to a development domain and a production domain.

What if I saved the snippet but still see no change?

Check the data- attribute in the product template, then confirm the agents are active. If both are correct, revisit the primary URL in your account. One of those three is almost always the cause.

What does 'the AI remains inert' mean for troubleshooting?

It means you can install the script safely and nothing will happen until you want it to. It also means a delay is probably not a slow server; it is an unactivated agent or a missing setup step.

Direct Answer: Reversibility Depends on Your Backup Strategy

Using SeaText AI on a development store allows you to configure SEO settings, generate content, and test integrations before launch, saving time and avoiding errors. The platform treats every domain as a separate account, so a development store and a production store each need their own SeaText account linked to a valid, real domain — localhost and dynamic preview URLs are restricted.

SeaText AI does not allow you to share the same settings across multiple domains. Each domain needs its own SeaText AI account. Settings are tied to that account. If you try to use one account for several domains, the AI will not activate correctly because each account is linked to a single primary URL.

If Seatext AI doesn't work on your product pages, the problem is usually in the setup, not the tool. Check three things first: the JavaScript snippet is installed on the exact page template, the product description is wrapped in the required element with a data- attribute, and the account you are logged into is linked to the same primary URL as your product-page domain. Work through those checks, then inspect the live page with your browser's developer tools. If everything passes and you still see no changes, contact Seatext support with your account URL and a screenshot of the HTML.

This article is a diagnostic guide. It moves from symptoms to likely causes to fixes. It also covers the common mistake that makes Seatext AI look broken on product pages even when the rest of the site works.

Check the basics first

Before you change any code, answer these questions:

• Do you have a Seatext AI account? The script is copied from your account area. Without an account, there is no script to install.
• Is the script installed on the same domain as your product pages? Each Seatext account is linked to a single primary URL. A script from one account will not run reliably on another domain.
• Is the domain a real, stable domain? Development URLs such as localhost are restricted, and dynamic development domains may not work.
• Have you activated at least one agent after installing the script? Seatext AI stays inert until you activate it.

Use this diagnostic sequence

Follow this order. It rules out cheap fixes first.

1. Open one product page in a regular browser window.
2. Use View Page Source or developer tools to confirm the Seatext script appears in the HTML.
3. Look for the data- attribute on the product description element.
4. Check the domain in your address bar against the primary URL for your Seatext account.
5. Log into Seatext and confirm the agents you need are active.
6. Save any template changes, clear your page cache if you have one, and reload the product page.
7. If nothing changes after step 6, contact support.

On Shopify, check theme.liquid and the product template

Shopify has a specific install path. The Seatext integration guide uses these steps:

1. In your Shopify admin, go to Online Store > Themes.
2. Next to your active theme, click the three dots icon and choose Edit code.
3. Open the Layout folder and find the file named theme.liquid.
4. Paste the Seatext JavaScript snippet and save the file.

Saving theme.liquid loads Seatext on your Shopify pages. But product descriptions need one more step. The product description is usually rendered in a file named product.liquid or product-template.liquid. Find the line that outputs the product description and wrap it with the required element that includes the data- attribute Seatext looks for. Save the file, then preview a product page.

To confirm it worked, open the same product page in your browser's developer tools and inspect the HTML source. The product description element should include the data- attribute. If it is missing, the template edit did not save, or you edited the wrong template.

The most common mistake: wrong domain or wrong account

The most common reason Seatext AI doesn't work on product pages is that the page is being viewed on a domain that does not match the Seatext account. Each Seatext account is linked to a single primary URL. When you paste the script on a second domain or on a staging URL, the account may not associate that traffic with your site. The result looks like a product-page bug, but it is an account mismatch.

This mistake happens often in product-page testing because you can have a development copy of your store at a URL like staging.example.com while the live store is at www.example.com. Seatext treats those as different domains. Create a separate account for each domain, and only test on a real domain. Localhost is blocked. Dynamic development domains may also fail because Seatext cannot reliably associate traffic with your account.

Why the agent may be active but nothing changes

Installing the script is not the same as turning on the feature. Seatext says the AI remains inert until activated. After you add the script, go to your Seatext dashboard and activate the agents you want on product pages. If the script is installed but no agent is active, the page will load normally and no copy changes will appear.

On product pages, the relevant agents are usually the ecommerce product copy agent, the translation agent, or the personalization agent. Which agents you need depends on your goal. The key point is that activation is a separate step from installation. Check that step before you dig into template code.

Symptom table: likely causes and fixes

When this advice does not apply

This guide is based on the official Seatext integration instructions, which currently give the most detail for Shopify. If your product pages run on a custom CMS or a different ecommerce platform, the generic script steps still apply: copy the JavaScript snippet from Seatext, paste it into your site's shared layout file, and make sure the product description markup includes the required data- attribute. The exact file names will be different.

This advice will not fix server errors, database issues, checkout failures, or problems caused by another app that rewrites your theme files. If a browser extension blocks third-party scripts, that can also look like a Seatext failure. Test in a normal browser window or an incognito window before assuming the installation is wrong.

Key facts at a glance

Terminology you may see in the docs

• Primary URL: the single domain linked to your Seatext account.
• theme.liquid: Shopify layout file that loads scripts across the theme.
• Product template: the Shopify file that renders product details, often product.liquid or product-template.liquid.
• Data- attribute: a custom HTML attribute that starts with data- and helps Seatext identify product description content.
• Activation: turning on an agent in the Seatext dashboard after installing the script.

FAQ

Why does Seatext AI work on my homepage but not on product pages?

Homepage and product pages often use different template files. The script may be in theme.liquid, but the product description still needs the required data- attribute wrapper in product.liquid or product-template.liquid. If it is missing, Seatext does not know which content to optimize.

Can I test Seatext on localhost?

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

Do I need a separate Seatext account for my staging site and my live site?

Yes. Each account is linked to a single primary URL. If you use a development domain and a production domain, create separate accounts for each.

I installed the script. Why is nothing changing on my product page?

Check that you activated an agent after installation. Seatext AI stays inert until activated. Then verify the product description markup has the data- attribute.

How do I verify the installation myself?

Open the product page in your browser, use developer tools to view the HTML source, and look for the Seatext script. Then find the product description element and confirm it contains the data- attribute.

What should I tell Seatext support if I still need help?

Send the primary URL of your Seatext account, the exact product-page URL, and a screenshot of the HTML source showing whether the script and data- attribute are present. That lets support compare your account against the page quickly.

Most installation failures on WP Engine come from a short list of fixable causes: an outdated PHP version, a missing cURL extension, a low PHP memory limit, plugin conflicts, and a missed WP Engine-specific step. On WP Engine, you also need the official custom JavaScript plugin and a valid SEATEXT account. Use the checklist below to find which one is blocking your install before you change any code.

When a website won't connect, the biggest mistake is jumping to complex fixes before ruling out simple ones. Most connection failures come from DNS cache, browser cache, firewall rules, or the server itself. Start with the visitor side, then move to the network layer, then the server, then the application. Skipping steps or testing out of order wastes hours and leads to wrong fixes.