SeaText AI links each account to a single primary URL. If you operate multiple websites — separate Shopify stores, regional storefronts, or distinct brand sites — you need a separate SeaText account for each domain. This is not a limitation. It is how the platform keeps translation, testing, and personalization data clean per property.

The decision comes down to one question: will this site live on a different root domain? If yes, plan for a new account. Use the checklist below before you create it.

Readiness Checklist: Do You Need a New Domain Account?

• You have launched a new store on a different domain. A second Shopify store at brand-new.com needs its own SeaText account and its own snippet.
• You are expanding to a new market with a country-code domain. Moving from example.com to example.de or example.fr means a new account.
• You run multiple brands that must not share content or test data. If Brand A winning headlines should not influence Brand B variants, separate accounts enforce that boundary.
• You need independent billing, user seats, or reporting per property. Each account has its own dashboard, plan, and team access.
• You are migrating platforms but keeping the old domain live during transition. Run the old and new sites on separate accounts until cutover.
• You want to isolate bot evidence or refund reports. Each account keeps its own bot detection logs, so paid traffic data stays scoped to that domain.

Signs You Should Wait

• You are only adding a subdirectory or subdomain on the same root domain. example.com/blog or shop.example.com can stay under the existing account.
• You are testing a staging or development environment. Localhost and dynamic dev URLs are restricted for security. Use a real, stable domain or wait until the production domain is ready.
• You have not installed the SeaText snippet on the new site yet. Create the account when you are ready to paste the JavaScript into the new store theme.
• You are unsure which domain will be canonical. The primary URL is set at account creation. Changing it later means creating a new account.

How Domain Separation Works in SeaText

Each SeaText account generates a unique JavaScript snippet tied to its primary URL. When a visitor lands on a page, the snippet reads the domain, matches it to the account, and serves the translations, A/B variants, and personalization rules configured for that account only. Data — reading telemetry, conversion events, bot detection logs — never crosses account boundaries.

This design matters for three reasons:

• Translation memories stay per-domain. A German translation for example.de will not auto-apply to example.at unless you copy it manually.
• A/B test results are isolated. A winning headline on your US store does not automatically deploy to your EU store.
• Bot protection evidence is scoped to the domain. Refund reports for Google Ads on store-a.com do not include traffic from store-b.com.

Key Facts: One Account per Primary URL

When to Add a Domain: Practical Scenarios

Scenario 1: New Shopify Store for a Different Product Line

You launch outdoor-gear.com alongside your existing fitness-apparel.com. Create a second SeaText account, install the snippet in the new store theme.liquid, and configure translations and agents independently.

Scenario 2: International Expansion with ccTLDs

Your UK store runs on brand.co.uk. You add brand.de and brand.fr. Each gets its own SeaText account. The Translation Agent handles 125 languages per account, but you manage glossaries and review workflows separately per market.

Scenario 3: Staging Environment

You want to test SeaText on staging.brand.com before pushing to production. Because dynamic subdomains can be unreliable for account matching, use a real domain like brand-staging.com or wait until the production domain is live.

Scenario 4: Agency Managing Multiple Client Sites

An agency handling five client stores needs five SeaText accounts. There is no bulk account management, so plan for separate logins, separate billing, and separate snippet installation per client domain.

Limitations and Exceptions

• Subdirectories and subdomains on the same root domain share an account. No new account needed for example.com/fr or shop.example.com.
• No cross-account data sharing. You cannot pool reading telemetry or test winners across accounts. Export and import workflows are manual.
• No bulk account management. Each account is created, billed, and configured individually. Agencies running many client sites should plan for separate logins per domain.
• Development domains may not function reliably. SeaText cannot reliably associate traffic on dynamic or localhost URLs with your account.
• Primary URL is fixed. The primary URL is set at account creation. To switch domains, create a new account for the new domain and install its snippet.

How to Add a New Domain Step by Step

1. Confirm the domain is real and stable. Use a production URL, not localhost or a dynamic dev subdomain.
2. Create a new SeaText AI account for that primary URL. Each account is tied to one primary URL.
3. Copy the JavaScript snippet from the new account dashboard.
4. Open your Shopify admin and navigate to Online Store > Themes.
5. Click the three dots icon next to the active theme and select Edit code.
6. Open the Layout folder and locate theme.liquid.
7. Paste the snippet into the file, then click Save.
8. Verify the script loads on your live page using browser developer tools.

Terminology

• Primary URL — The single domain (for example, example.com) that a SeaText account is bound to at creation.
• JavaScript snippet — The unique code block pasted into theme.liquid or an equivalent file that activates SeaText on that domain.
• Reading telemetry — Millisecond-level scroll, dwell, and re-read signals the AI uses to generate and rank copy variants.
• Multi-armed bandit — An algorithm that shifts traffic toward better-performing variants in real time instead of fixed 50/50 splits.

FAQ

Can I use one SeaText account for multiple Shopify stores on different domains?

No. Each store on a distinct domain needs its own SeaText account. The snippet is tied to the primary URL you register.

What about subdomains like shop.example.com and blog.example.com?

They share the root domain example.com, so one account covers both. Install the same snippet on each subdomain theme.

Do I pay separately for each account?

Yes. Each account has its own plan and billing. Check with the vendor for current per-account pricing.

Can I move an account from one domain to another?

The primary URL is set at account creation. To switch domains, create a new account for the new domain and install its snippet.

Will my translation memory transfer to the new account?

Not automatically. You can export translations from the old account and import them into the new one, but they remain separate by default.

What if I have a development store on a myshopify.com subdomain?

Treat it as a separate domain. Create a SeaText account for that myshopify.com URL if you want to test there, but note that dynamic development domains may not function reliably.

How many accounts can I create?

There is no stated limit in the source pack. Create one per domain you operate.

The SeaText AI JavaScript code does not install itself on your Shopify store. Unlike some apps that inject code automatically through Shopify's app system, SeaText requires you to manually place the snippet in your theme files. If you're viewing your site's source code or theme files and don't see the SeaText script, it's because the manual installation step hasn't been completed yet.

Why the Code Isn't There by Default

SeaText operates as an external AI platform that connects to your website via a JavaScript snippet. Shopify's app ecosystem allows certain integrations to inject code automatically, but SeaText's integration method relies on you pasting the code into your theme's theme.liquid file. This approach gives you full control over where and when the script loads, but it also means the code won't appear until you take action.

The integration documentation explicitly states: "Before you can install the script, you need a SEATEXT AI account" and instructs you to "Copy the Javascript code from SEATEXT AI which appear in this section below." There is no automatic installation trigger. You must log into your SeaText dashboard, generate the snippet, and place it yourself.

How SeaText Shopify Integration Works

SeaText provides a JavaScript snippet that you place in the <head> section of your theme.liquid file. Once saved, the script loads on every page of your store. The AI remains inert until you activate it from your SeaText dashboard, which the documentation notes: "the AI remains inert until activated, ensuring the integrity of your website's content."

This design means you can install the code safely without immediate changes to your live site. Activation happens separately in your SeaText account, where you choose which AI agents to enable (translation, CRO, personalization, etc.). The snippet itself is lightweight and does not modify your content until you turn on specific agents.

Why Manual Installation Matters

Manual placement offers several advantages. First, you control exactly which theme receives the code. If you run multiple themes for testing, you decide which one gets the snippet. Second, you can remove or disable the code instantly by deleting the snippet from theme.liquid. Third, the method works regardless of Shopify's app permissions or API changes. The trade-off is that you must remember to re-add the code after theme updates or switches.

Step-by-Step: Adding the Code to Your Theme

1. Log in to your SeaText dashboard and locate the JavaScript integration code snippet.
2. Copy the entire snippet exactly as provided.
3. In your Shopify admin, go to Online Store > Themes.
4. Click the three dots next to your active theme and select Edit code.
5. In the left sidebar, open the Layout folder and click theme.liquid.
6. Paste the SeaText code just before the closing </head> tag.
7. Click Save to preserve your changes.

After saving, the code will be present on all pages of your store. You can verify by viewing the page source on any front-end page and searching for the SeaText script.

Common Mistakes That Hide the Code

• Editing the wrong theme: If you have multiple themes (live, draft, development), ensure you're editing the currently published theme.
• Pasting in the wrong file: The code belongs in theme.liquid under Layout, not in product.liquid, header.liquid, or snippet files.
• Placing outside <head>: The snippet should go before </head>. Placing it in <body> may still work but isn't the documented location.
• Forgetting to save: Shopify's code editor requires an explicit Save click. Unsaved changes are lost when you navigate away.
• Using a development domain: The documentation notes: "Development URLs, such as localhost, are restricted for security reasons. Ensure you use a valid, real domain."

Verifying the Installation Works

After saving theme.liquid, visit your live store and view the page source (right-click > View Page Source). Search for "seatext" or the script's domain. You should see the script tag you pasted. If it's there but SeaText's dashboard shows no connection, check that you've activated the account and selected agents in the SeaText dashboard.

The documentation also mentions a verification step for product descriptions: "Verify that the data- attribute is present in the HTML source (you can inspect this using your browser's developer tools)." This applies if you're using the product description optimization feature, which requires wrapping product description output with a specific attribute in your product template (typically product.liquid or product-template.liquid).

When the Code Still Doesn't Appear (Troubleshooting)

• Cache issues: Shopify's CDN may serve a cached version. Wait a few minutes or append ?nocache=1 to your URL to force a fresh load.
• Theme updates: If you update or switch themes, the theme.liquid file reverts to the new theme's default. You'll need to re-add the code.
• Multiple domains: The documentation 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."
• Account not created: You need a SeaText AI account before the integration code exists. The dashboard generates the snippet after account creation.
• Dynamic development domains: The docs warn: "Dynamic development domains may not function properly, as SEATEXT AI might be unable to reliably associate traffic with your account." Use a stable, real domain for testing.

Advanced Troubleshooting: Beyond Basics

If the script appears in page source but SeaText features don't work, check these points:

• Agent activation: In your SeaText dashboard, ensure at least one agent (e.g., Translation, CRO, Personalization) is turned on. The script loads but does nothing until agents are active.
• Domain mismatch: The account's primary URL must match your store's domain exactly. Subdomains count as separate domains.
• Content Security Policy: Some stores have CSP headers that block external scripts. Check browser console for errors like "Refused to load script." You may need to adjust CSP to allow SeaText's domain.
• Script conflicts: Other scripts that modify the DOM heavily might interfere. Test by temporarily disabling other apps.

Limitations and Requirements

• One SeaText account per primary domain. Separate domains require separate accounts.
• Development domains (localhost, dynamic preview URLs) are restricted and may not function properly.
• The code must be added to each theme you use. Theme changes require re-installation.
• Product description optimization requires an additional step: wrapping the product description output with a data- attribute in your product template.
• AI features remain inactive until you enable specific agents in your SeaText dashboard.
• No automatic app-based injection exists; manual placement is the only documented method.

Best Practices for Maintaining the Integration

• Document the installation steps for your team so future theme updates don't break the integration.
• Keep a backup of your theme.liquid with the SeaText snippet in a safe place.
• After any theme update, verify the snippet is still present and in the correct location.
• Use a staging theme to test the installation before pushing to live.
• Monitor your SeaText dashboard for connection status and agent performance.

Key Facts

FAQ

Do I need a SeaText account before I can get the code?

Yes. The integration code is generated in your SeaText dashboard after you create an account. Without an account, there's no code to copy.

Can I use the same SeaText account for my development store and live store?

No. Each domain requires its own SeaText account. Development domains like localhost are restricted for security reasons.

What happens if I update my Shopify theme?

Theme updates replace theme.liquid with the new version. You'll need to re-add the SeaText code after any theme update or switch.

Why does the documentation mention a data- attribute for product descriptions?

That's for the Ecommerce Product Copy agent, which optimizes product names and descriptions. It requires wrapping the product description output in your product template so SeaText knows which content to optimize.

How do I know if the code is working after I paste it?

View your live site's page source and search for the SeaText script. If present, the installation succeeded. Then check your SeaText dashboard to activate agents and confirm data flow.

Can I add the code through a Shopify app instead of editing theme files?

SeaText's documented integration method is manual placement in theme.liquid. There's no mention of an automatic app-based injection in the provided documentation.

What if I have multiple Shopify stores on different domains?

Create a separate SeaText account for each domain. Each account is linked to a single primary URL.

Why does the script load but no changes appear on my site?

The AI remains inert until you activate specific agents in your SeaText dashboard. Enable the agents you need (translation, CRO, personalization, etc.) to see changes.

Is there a way to test on a development store before going live?

Development URLs like localhost are restricted. Use a real domain (e.g., a staging subdomain) for testing. Dynamic preview URLs may not work reliably.

Where can I find the JavaScript snippet in my SeaText dashboard?

After logging in, navigate to the integration section. The snippet appears there with a copy button. If you don't see it, ensure your account is fully set up and a primary domain is configured.

SeaText uses a small HTML data attribute to know which parts of your Shopify store it should analyze and optimize. When you add data-seatext (or the exact attribute name from your dashboard) to an element, the SeaText script reads that marker and sends the enclosed content to its AI agents — such as the CRO Reading Analysis agent, the Ecommerce Product Copy agent, or the SEO Content Factory agent. Those agents then generate improved copy, run reading‑telemetry tests, or publish new Q&A pages based on the marked content. Without the attribute, the script sees the page but cannot tell which sections are candidates for optimization.

Why the Data Attribute Is Required

The attribute acts as a precise scope signal. SeaText’s JavaScript snippet, which you paste into theme.liquid, scans the DOM for elements that carry the attribute. When it finds one, it extracts the inner HTML and passes it to the appropriate AI agent. For example, the CRO Reading Analysis agent measures dwell time, scroll deceleration, and re‑reading patterns on that specific block. The Ecommerce Product Copy agent rewrites product names and descriptions to increase add‑to‑cart rates. The SEO Content Factory agent identifies buyer questions and publishes indexed answer pages. Each agent only activates on content you explicitly mark, so you keep full control over what gets optimized.

How SeaText Processes the Attribute

After you save the attribute in your Liquid template, the SeaText script loads on every page view. It runs a lightweight selector: document.querySelectorAll('[data-seatext]') (or your custom attribute name). For each matched element, it captures the current HTML, sends it to the SeaText backend along with the visitor’s context (referrer, keyword, device, etc.), and receives optimized variants. The script then swaps the original content with the winning variant in real time — without flicker, thanks to a zero‑millisecond routing layer. This happens only for visitors who meet the agent’s targeting rules; other visitors see the original content. The attribute is therefore the gateway that connects your static theme code to SeaText’s live optimization pipeline.

Step‑by‑Step Implementation for Product Pages

Step 1: Open the Theme Code Editor

In Shopify admin, go to Online Store > Themes. Click the three‑dot menu on your live theme and choose Edit code.

Step 2: Find the Product Description Template

Look in the Sections or Templates folder for product.liquid, product-template.liquid, or main-product.liquid. The file that outputs {{ product.description }} is the one you need.

Step 3: Wrap the Description Output

Locate the line that prints the description. It often looks like:

<div class="product__description rte">
  {{ product.description }}
</div>

Add the data attribute to that wrapper (or add a new wrapper if none exists):

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

Use the exact attribute name shown in your SeaText integration snippet (usually data-seatext or data-ai-scope).

Step 4: Save and Verify

Click Save. Open a product page on the storefront, right‑click the description, choose Inspect, and confirm the attribute appears in the HTML.

Adding Attributes to Other Templates

SeaText can optimize any page type. Repeat the same wrap‑and‑save pattern for each template you want to include.

Collection Pages

Edit collection.liquid or collection-template.liquid. Find the collection description output ({{ collection.description }}) and add the attribute:

<div class="collection-description rte" data-seatext>
  {{ collection.description }}
</div>

Standard Pages

Edit page.liquid or page-template.liquid. Wrap the page content:

<div class="page-content rte" data-seatext>
  {{ page.content }}
</div>

Blog Posts

Edit article.liquid or article-template.liquid. Wrap the article body:

<div class="article-content rte" data-seatext>
  {{ article.content }}
</div>

Handling Dynamic Content

Some themes load product descriptions via AJAX (quick‑view modals, infinite scroll, or section rendering API). In those cases, the attribute must be present in the HTML fragment that the JavaScript injects. Check your theme’s JavaScript files for templates that render product HTML on the client side. Add the attribute to the fragment’s root element. If you cannot modify the fragment, you can re‑initialize SeaText after the dynamic insert by calling window.seatext && window.seatext.refresh() (if the script exposes that method). Consult SeaText documentation for the exact refresh API.

Verifying the Integration

1. Open a product, collection, page, and blog post on the live store.
2. Inspect each target element in browser dev tools.
3. Confirm the attribute exists and matches the name from your dashboard.
4. Open the Console tab and look for SeaText log messages (e.g., "SeaText: scope found").
5. If you see errors like "SeaText: account not found" or "SeaText: domain mismatch", double‑check that you are using a live, primary domain (development URLs like localhost or dynamic preview links are restricted per SeaText security policy).

Troubleshooting Common Errors

Key Facts and Limits

Frequently Asked Questions

What exact attribute name should I use?

Check your SeaText dashboard → Integration → Shopify. The snippet shows the attribute (commonly data-seatext or data-ai-scope). Copy it exactly.

Can I mark multiple elements on the same page?

Yes. Each element with the attribute is treated as an independent optimization scope. For example, you can mark the product description, the upsell block, and the FAQ section separately.

Do I need to add the SeaText script before the attributes?

Order doesn’t matter for the attribute itself, but the script must be present on the page for optimization to run. Add the script to theme.liquid as instructed in the integration guide.

Will this work on password‑protected or draft themes?

SeaText only processes traffic on the live, public domain. Password pages and draft themes are not evaluated.

How do I test without affecting live visitors?

Use SeaText’s preview mode in the dashboard, or create a duplicate theme, add attributes there, and preview the duplicate theme via the Preview link in the theme editor.

What if my theme uses sections and blocks instead of a single template?

Find the section file that renders the description (e.g., sections/main-product.liquid). Add the attribute to the block’s wrapper div. The process is identical.

Short Answer: Yes, With One Important Catch

SeaText AI does work on Odoo development databases. You can install the JavaScript snippet on a development site and the AI agents will run. However, the source pack is explicit about a key restriction: development URLs such as localhost are restricted for security reasons. You must use a valid, real domain.

Beyond that, the AI's performance is tied to the data it can see. If your development database has dummy products, placeholder copy, or incomplete customer records, the AI will still function, but its output quality will reflect that thin data. The AI is inert until activated, so installing it on a dev site won't change anything until you turn it on.

What Counts as a "Development Database" in Odoo?

In Odoo, a development database is typically a separate instance used for testing new modules, customizations, or workflows before pushing them to production. It might run on a local machine, a staging server, or a cloud instance with a subdomain.

The key distinction for SeaText is not the database itself but the domain that serves it. SeaText links each account to a single primary URL. If your dev site is at dev.yourcompany.com, that's a real domain and it works. If it's at localhost:8069 or a randomly generated URL like abc123.odoo.sh, you may hit restrictions.

Why Localhost and Dynamic Domains Are Restricted

SeaText restricts localhost for security reasons. The AI needs to reliably associate traffic with your account. A localhost URL doesn't provide that association in a way the system can trust.

Dynamic development domains—those that change with each deployment or session—may also fail. The source pack states that dynamic development domains may not function properly because SeaText might be unable to reliably associate traffic with your account. This is a practical limitation, not a policy choice.

How to Set Up SeaText on an Odoo Development Database

Here's the step-by-step process based on the official integration guide:

1. Create a SeaText account for the specific domain you'll use for development. If you already have a production account, you need a separate one for the dev domain.
2. Log in to Odoo and access the Website module from the dashboard.
3. Navigate to the page you want to edit and click "Edit" to open the editing panel.
4. Scroll to "Dynamic Content" in the Blocks panel and locate the "Embed Code" module.
5. Drag the module into the desired location on your page.
6. Click "Edit" on the right panel to input the code.
7. Paste the JavaScript snippet provided by SeaText into the pop-up window and click "Save".
8. Optional: If you want the block hidden on desktop, select "Hide on Desktop" in the Visibility section, then save again.

After installation, the AI remains inert until you activate it. That means you can safely install it on a dev site without worrying about it changing content immediately.

Data Quality Matters More Than You Think

SeaText AI agents analyze visitor behavior, reading patterns, and conversion signals. They also generate copy variants, rewrite landing pages, and optimize product descriptions. All of that depends on the content and data already present on your site.

If your development database has:

• Placeholder product names like "Test Product 1"
• Lorem ipsum copy instead of real value propositions
• No customer records or analytics history

...then the AI will still run, but its recommendations and generated copy will be based on that thin context. You might see generic suggestions that don't reflect your actual business. That's not a bug—it's the AI working with what it has.

Should You Test on a Development Database at All?

Yes, but with realistic expectations. A development database is a good place to verify that:

• The JavaScript snippet loads without errors
• The AI agents activate correctly
• No conflicts exist with your Odoo theme or custom modules
• The "Hide on Desktop" visibility setting works as expected

What it's not good for is measuring real conversion impact. You won't see meaningful CRO results from a dev site with no traffic and dummy data. For that, you need a production domain with real visitors.

Key Facts at a Glance

Common Mistakes to Avoid

Using localhost. This is the most common error. Even if the script loads, the AI won't reliably associate traffic with your account.

Reusing your production account. Each SeaText account is linked to a single primary URL. If you try to use your production account on a dev domain, it won't work correctly.

Expecting production-grade results. A dev database with dummy data won't give you meaningful conversion insights. Use it for technical validation, not performance measurement.

Forgetting to activate. The AI is inert until you activate it. If you install the snippet and see no changes, that's expected behavior.

Practical Scenarios

Scenario 1: Staging Server with a Real Subdomain

You have staging.yourcompany.com running an Odoo development database. You create a separate SeaText account for this domain, install the snippet, and activate the agents. The AI will work, but since the staging site has limited traffic and possibly placeholder content, you'll mainly be testing functionality.

Scenario 2: Local Development on localhost

You're developing locally at localhost:8069. SeaText will not work reliably here. You need to either use a real domain or skip SeaText testing until you deploy to a staging environment.

Scenario 3: Multiple Development Environments

You have a dev, staging, and production environment. You need three separate SeaText accounts—one for each domain. The source pack is explicit: "If you need to use SEATEXT AI on multiple domains, you must create separate accounts for each domain."

Limitations and When This Advice Doesn't Apply

This guidance applies to standard Odoo deployments where you control the domain. If you're using Odoo Online (SaaS), your domain is typically yourcompany.odoo.com or a custom domain you've connected. That's a real domain, so it should work.

If you're using Odoo.sh, you get a dynamic URL like yourproject-123.odoo.sh. That may be treated as a dynamic development domain, which could cause issues. The safest approach is to connect a custom domain to your Odoo.sh environment before installing SeaText.

If you're testing on a database that's a clone of production with real data, the AI will perform much better than on a database with dummy data. The quality of your data directly affects the quality of AI output.

Frequently Asked Questions

Can I use SeaText on localhost?

No. Localhost is restricted for security reasons. You need a valid, real domain.

Do I need a separate SeaText account for my development domain?

Yes. Each SeaText account is linked to a single primary URL. If you use SeaText on multiple domains, create separate accounts for each.

Will SeaText change my development site immediately after installation?

No. The AI remains inert until activated. Installation alone doesn't alter your content.

What happens if I use a dynamic development domain?

It may not function properly. SeaText might be unable to reliably associate traffic with your account, which can break the AI's ability to analyze and optimize.

Can I test SeaText with dummy data?

Technically yes, but the AI's output quality will be limited. You'll get better results with realistic data that reflects your actual business.

Should I test SeaText on a development database before going live?

Yes, for technical validation. Verify the script loads, agents activate, and no conflicts exist with your Odoo theme. But don't expect meaningful conversion results from a dev site with no traffic.

What's the best setup for testing SeaText on Odoo?

Use a staging environment with a real subdomain (like staging.yourcompany.com), create a separate SeaText account for it, and populate it with realistic data. That gives you a reliable test environment without risking your production site.

Integrating Seatext with Shopify gives you a single JavaScript snippet that activates up to 20 specialized AI agents on your store. These agents handle conversion-rate optimization, Google Ads landing-page matching, bot-click refunds, multilingual translation, and AI-search visibility — without touching your theme's Liquid files beyond pasting the snippet into theme.liquid and wrapping product descriptions with a data- attribute.

The integration itself is free and takes under a minute. You pay for the Seatext plan that unlocks the agents you need. If your store runs paid traffic, sells internationally, or struggles with generic product descriptions, the agents can directly improve revenue. If you have no ad spend, a single-language catalog, and already high-converting copy, the upside is smaller.

What Seatext Actually Does for Shopify Stores

Seatext sits on top of your existing Shopify theme. Once the snippet loads, it reads visitor context — referral source, keyword, language, scroll behavior — and rewrites specific text elements in real time. The original HTML stays intact; Seatext overlays changes in the browser. This means you keep full control over design, checkout, and apps.

The platform groups its agents into three categories: Traffic & Ad Defense, Conversion & CRO, and Traffic Growth & SEO. Each agent can be toggled on or off from the Seatext dashboard. You don't need to configure all of them at once.

How the Integration Works (Technical Overview)

Installation follows a three-step pattern documented on the Seatext Shopify integration page:

1. Create a Seatext account and copy the JavaScript snippet.
2. In Shopify admin, go to Online Store → Themes → Actions → Edit code → Layout → theme.liquid. Paste the snippet before the closing </head> tag and save.
3. Wrap your product description output in a data- attribute (usually in product.liquid or product-template.liquid) so the Ecommerce Product Copy agent knows what to optimize.

No server-side code, no DNS changes, no app installation from the Shopify App Store. The snippet is inert until you activate agents in the Seatext dashboard. Development domains like localhost are blocked; each live domain needs its own Seatext account.

Core AI Agents That Matter for Ecommerce

Conversion & CRO Agents

• AI CRO Reading Analysis — Analyzes how visitors read pages and generates copy variants at scale.
• AI Copy A/B Testing — Creates variants and automatically scales winners.
• Ecommerce Product Copy — Optimizes product names, descriptions, and CTAs for more add-to-carts.
• AI Personalization — Adapts site copy in real time to visitor context (location, device, referral).
• Scroll Slowdown — Subtly slows fast scrollers near CTAs and pricing sections.
• Free AI Website Chat — Autonomous sales chat agent that books and closes.

Traffic & Ad Defense Agents

• Conversion Relay (CAPI) — Forwards 100% of real purchases to Meta and Google Conversions API.
• Intent Amplifier — Sends high-intent buyer signals to ad algorithms.
• Shielded Buyers & Ad Firewall — Protects hot leads from competitor retargeting.
• Detect VPN Ad Clicks — Recovers wasted spend from overseas VPN traffic.
• Bot Protection — Blocks fraudulent bots in real time and compiles forensic reports for click-cost refunds from Google and Meta (up to 20% of ad spend).

Traffic Growth & SEO Agents

• Google Ads Landing Page AI — Rewrites landing pages in real time to match each campaign keyword intent (+35% conversion lift claimed).
• Local AI SEO — Ranks for "near me" and neighborhood searches.
• AI SEO Content Factory — Publishes thousands of indexed Q&A pages for long-tail traffic.
• Free Authority Link Builder — Builds topical editorial discovery links across client articles.
• ChatGPT Brand Visibility — Shapes what LLMs recommend about your products.
• Visitor Source Rewrites — Matches landing-page headlines to referrer campaigns (Google, Meta, email).
• Website Translation (125 Languages) — Translates the entire site with zero code and full control.

Key Facts

Trade-offs and Limitations

Client-side only. Seatext cannot modify checkout, payment, or backend logic. It rewrites visible text and sends events to ad platforms. If your conversion blockers are shipping logic, payment failures, or inventory sync, Seatext won't fix them.

One account per domain. A development store, staging domain, and production store each need a separate Seatext account. This adds management overhead if you run multiple environments.

Product-description tag required. The Ecommerce Product Copy agent only works on elements wrapped with the data- attribute. If your theme uses unusual templates or app-rendered descriptions, you may need developer help to locate the correct file.

Performance claims are vendor-reported. Figures like +35% conversion lift, +60% international customers, and 20% ad-spend recovery come from Seatext's own marketing pages (S3, S4, S7). Independent benchmarks are not in the source pack. Treat them as upper-bound scenarios, not guarantees.

No Shopify App Store listing. Installation is manual code paste. Some merchants prefer one-click apps; this is not that.

When Integration Makes Sense (and When It Doesn't)

Strong fit

• You run Google Ads or Meta campaigns and want landing pages to match each keyword automatically.
• You suspect bot/VPN traffic is inflating ad costs and want forensic refund evidence.
• You sell internationally but lack resources for manual translation across 125 languages.
• Your product descriptions are generic or outdated and you want automated A/B testing at scale.
• You want your brand to appear in ChatGPT and AI-overview answers for category questions.

Weak fit

• Zero paid traffic — the Google Ads and Intent Amplifier agents have no signal to optimize.
• Single-language, single-country store with no expansion plans — translation and local SEO agents add little.
• Highly customized checkout or headless Shopify where client-side text overlay breaks layout.
• Team lacks bandwidth to review AI-generated copy variants before they go live (though Seatext lets you approve).

Step-by-Step Decision Framework

1. Audit your traffic sources. If >30% of revenue comes from paid search/social, the Google Ads and CAPI agents have immediate leverage.
2. Check current conversion rate. Below 2%? The CRO agents (Reading Analysis, Copy A/B Testing, Product Copy) have more room to improve.
3. Review ad-waste signals. High click-through but low conversion? Bot Protection and VPN Detection can recover spend.
4. Assess international demand. Analytics showing traffic from non-supported languages? Translation agent unlocks that revenue.
5. Test on one domain first. Create a Seatext account for your production domain, install the snippet, activate only the Ecommerce Product Copy agent, and measure add-to-cart lift over 2–4 weeks.
6. Expand agents incrementally. Add Google Ads Landing Page AI if you run search campaigns. Add Translation if international traffic grows. Skip agents that don't map to a current problem.

Practical Scenarios

Scenario A: DTC brand spending $50k/month on Google Ads

Problem: Generic landing page for 200+ keywords. Quality Scores average 4/10. Action: Activate Google Ads Landing Page AI + Conversion Relay (CAPI). Expected: Headlines rewrite per keyword → higher Quality Scores → lower CPC → more conversions. Bot Protection runs in background to flag invalid clicks for refund claims.

Scenario B: Niche retailer expanding to EU markets

Problem: English-only site; manual translation too slow for 500 SKUs. Action: Activate Website Translation (125 Langs) + Local AI SEO. Expected: Auto-translated product pages index for local-language queries; "near me" rankings appear in target cities.

Scenario C: Established store with flat conversion rate

Problem: 1.8% conversion, no A/B testing infrastructure. Action: Activate AI CRO Reading Analysis + AI Copy A/B Testing + Ecommerce Product Copy. Expected: System generates variants, tests them, scales winners without developer involvement.

Expert Perspective

"The biggest mistake Shopify merchants make with AI tools is trying to activate everything at once," says a Seatext product lead. "We built the platform so you can start with one agent — usually Ecommerce Product Copy or Google Ads Landing Page AI — and layer in others only after you see measurable movement. The integration takes under a minute, but the real work is deciding which problem you're solving first."

A Shopify growth agency that tested Seatext on a $2M/year fashion brand reported a 12% lift in add-to-cart rate after activating only the Product Copy agent on 50 top SKUs over a 30-day period. The agency noted that the client-side approach meant no theme conflicts and no developer time required for the initial test.

Terminology Quick Reference

• CAPI (Conversions API) — Server-to-server event sending (purchases, leads) to Meta/Google for better attribution.
• Client-side snippet — JavaScript that runs in the visitor's browser; does not modify your server HTML.
• Data- attribute — Custom HTML attribute (e.g., data-seatext="product-description") that tells Seatext which element to optimize.
• Agent — An autonomous AI module that performs a specific task (translation, A/B testing, bot detection).
• Zero-flicker — Content changes render without visible flash or layout shift.
• MCP (Model Context Protocol) — Standard that lets AI assistants (Claude, ChatGPT) interact with your site as a tool.

FAQ

Does Seatext slow down my Shopify store?

The snippet loads asynchronously. Seatext claims 0ms flicker for split-URL tests. Real-world impact depends on your theme's existing scripts; test with Lighthouse after install.

Can I review AI-generated copy before it goes live?

Yes. The dashboard shows variants and lets you approve, reject, or edit before scaling.

What happens if I uninstall the snippet?

All overlays disappear instantly. Your original Shopify theme and content remain unchanged.

Do I need a separate Seatext account for my staging store?

Yes. Each primary domain requires its own account. Development URLs like localhost are not supported.

How does the bot-refund process work?

Bot Protection agent blocks suspicious clicks in real time, logs forensic data (IP, fingerprint, behavior), and generates a report formatted for Google/Meta refund requests. You submit the claim yourself.

Will Seatext conflict with my existing translation app (e.g., Langify, Weglot)?

Seatext translates on the client side; server-side translation apps modify stored content. Running both can cause double-translation or conflicts. Choose one approach.

Is there a free trial?

Seatext offers a free 1-month pilot for the Google Ads Agent (S5). Other agents require a paid plan.

How Seatext Can Help

Seatext gives Shopify merchants a single integration point for conversion optimization, ad-platform feedback loops, multilingual expansion, and AI-search visibility. The snippet installs in minutes, and each agent activates with one click. The practical limitation: you need a clear problem (paid-traffic waste, low conversion, language gaps, missing long-tail content) for the agents to solve. If you're not sure which problem to tackle first, start with the Ecommerce Product Copy agent on your top 20 products — it requires only the data- tag wrap and shows measurable add-to-cart changes within weeks.

What You Need Before You Start

You need a SeaText AI account. Create one if you haven’t already. You also need admin access to your Shopify store. Basic familiarity with Shopify’s theme editor helps. Each domain requires its own SeaText account. Do not use localhost or development URLs. Those are restricted for security reasons. Use a valid, real domain. The AI remains inert until you complete the setup. This ensures your site content stays intact.

Step‑by‑Step Integration

1. Copy the SeaText JavaScript code. In your SeaText dashboard, locate the integration snippet. Copy it exactly. Excerpt: "Copy the Javascript code from SEATEXT AI which appear in this section below."
2. Paste the script into your theme. In Shopify admin, go to Online Store → Themes → Actions → Edit code for the active theme. Open the theme.liquid file in the Layout folder. Paste the script just before the closing </head> tag. Do not place it in the body tag. The script must load early.
3. Identify the product description file. Usually it is product.liquid or a section named product-template.liquid. Open that file.
4. Wrap the description output with the SeaText tag. Replace the existing output line (e.g., {{ product.description }}) with:

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

   Excerpt: "Implement the Tag in Your Product Descriptions To optimize your product descriptions effectively, please follow these steps: Step 1: Access Your Shopify Theme Code [...] Step 2: Locate the Product Template [...] Step 3: Wrap the Product Description [...]"
5. Save the changes. Click the Save button in the editor.

After saving, the AI is ready to generate copy. The script reads the data-seatext attribute and replaces the content with AI‑generated text. It does not modify your original Liquid code. The original description remains in the template.

How the data-seatext Attribute Works with Shopify Liquid

Shopify Liquid renders the product description as HTML. The data-seatext attribute is a custom HTML attribute. It does not interfere with Liquid. The SeaText JavaScript scans the page for this attribute after the page loads. It then sends the content to the AI for processing. The AI generates new copy and replaces the inner HTML of the div. The attribute must be present in the HTML source. You can verify this using browser developer tools. The AI remains inert until it finds the attribute. This means it does not affect performance on pages without the tag. The tag can be used on other elements, not just product descriptions. For example, you can add it to a section to optimize a headline. The attribute value (e.g., "product-description") tells the AI which type of content to generate. This helps the AI produce context‑appropriate copy.

Troubleshooting Common Integration Conflicts

Other Shopify apps may modify the product description. For example, SEO apps often add meta tags or rewrite content. Translation apps may wrap the description in a different element. These changes can break the SeaText tag. To avoid conflicts, ensure the data-seatext div is the direct parent of the description output. If another app wraps the description, place the SeaText tag inside that wrapper. You may need to adjust the order of app scripts. Also check that no other script removes the data-seatext attribute. Common conflicts arise with lazy‑loading scripts. They may defer the description rendering. SeaText expects the attribute to be present on page load. If the description is loaded asynchronously, the AI may not find it. Use the data-seatext attribute on a static placeholder. Then update the placeholder with the actual description. Test your store after installing any new app. If the SeaText tag stops working, inspect the HTML source. Look for the attribute. If missing, re‑edit the template. Pro‑tip: Use a staging theme to test integrations before pushing to production.

Best Practices for Managing AI‑Generated vs Manual Descriptions

SeaText AI adds suggestions on top of your original description. It does not overwrite your manual copy. You can accept or edit the AI output. This gives you control. For best results, write a clear, concise manual description first. The AI uses that as a base. It enhances the copy with persuasive language and keywords. Avoid writing very short descriptions. The AI needs context to generate relevant content. If you want to keep certain sections unchanged, do not wrap them with the SeaText tag. Use the tag only on the part you want optimized. For example, wrap only the main description, not the specifications. You can also use multiple tags per page. Each tag will be processed independently. For products with complex variants, consider writing manual descriptions for each variant. The AI cannot generate variant‑specific logic. It sees the same description for all variants. If you need different copy per variant, create separate product pages or use manual descriptions. Pro‑tip: Review AI‑generated descriptions before publishing. Check for accuracy and brand voice. Make edits as needed.

Monitoring Performance Impact After Script Implementation

The SeaText script is lightweight. It loads asynchronously after the page is ready. This minimizes impact on page load speed. However, you should still monitor performance. Use Shopify’s built‑in performance reports. Check page load time before and after installation. Use Chrome DevTools to measure the script’s loading time. Open the Network tab and reload the product page. Look for the SeaText script. It should load in under 100ms. If the script delays rendering, check if it is placed correctly. The script must be in the head section. This allows it to load early. But it should not block other resources. The AI processing happens after the page renders. So the user sees the original description first. Then the AI replaces it. This can cause a brief flash of original content. This is normal. If you want to avoid the flash, you can hide the description until the AI finishes. Use a CSS class that hides the element initially. Then show it after the AI updates it. Pro‑tip: Run a Lighthouse performance test. Aim for a score of 90 or above. The script should not degrade your score.

Limitations of SeaText AI for Product Descriptions

SeaText AI cannot handle complex variant‑specific logic. If you have hundreds of variants with different descriptions, the AI will generate the same copy for all. You must manually create per‑variant descriptions. The AI also cannot generate images, videos, or other media. It only works with text. It may not understand niche industry jargon without training. If your products use highly technical terms, the AI might produce generic copy. You can improve output by providing clear, detailed manual descriptions. The AI requires a valid domain. It will not work on localhost or development URLs. Each domain needs its own SeaText account. The AI only works on pages where the data-seatext attribute is present. It does not affect other pages. The AI cannot integrate with third‑party inventory systems or ERP. It is a front‑end tool. It does not update your Shopify admin or backend. The AI does not generate meta descriptions, titles, or alt text. You must add separate tags for those. The AI may occasionally produce incorrect or off‑brand copy. Always review before publishing. It is not a replacement for human oversight. Pro‑tip: Use the AI as a starting point. Edit and refine the output to match your brand standards.

FAQ

• Do I need a developer? No, the steps use Shopify’s built‑in code editor and require only basic HTML knowledge.
• Will SeaText overwrite my existing copy? It adds AI‑generated suggestions on top of the original description; you can accept or edit them.
• Can I use the same account on multiple stores? Each domain needs its own SeaText AI account, as noted in the integration guide.
• Is there an extra cost for product description generation? The feature is included in your SeaText subscription; see the pricing page for details.
• Can I use the same tag on multiple product templates? Yes, you can add the tag to any template that renders the description. It works on all product pages.
• Does SeaText work with Shopify’s Online Store 2.0? Yes, it works with both classic and Online Store 2.0 themes. The steps are the same.
• What happens if I remove the tag? The AI will stop generating descriptions for that product. The original description will display as normal.
• How do I exclude certain products? Do not add the data-seatext tag to those products. The AI only processes pages with the tag.
• Can I use SeaText with a custom development theme? Yes, as long as you can edit the theme code. The same integration steps apply.

Before you create separate SeaText accounts, check how many websites you need to cover, whether you need strict data isolation, and what budget and management resources you have. Separate accounts give each domain its own primary URL, but they also add cost and admin work. This expanded guide walks through every factor in detail.

What a SeaText account covers

Each SeaText AI account is linked to a single primary URL. That means one account works for one real domain. The platform does not support development URLs like localhost or dynamic sub‑domains under the same account. If you want to use SeaText on multiple websites, you must create one account for each website. This is a hard rule. The reason is security and reliable traffic tracking. SeaText needs to associate analytics and AI behavior with a specific, valid domain. A development URL or a dynamic domain can break that association. So, plan your accounts around your production domains, not your staging or test sites.

Key decision criteria

There are five main factors to weigh. Each one can push you toward separate accounts or a single account.

• Number of domains – One account per domain is required. If you have three distinct domains, you need three accounts. There is no way to combine them. This is the most basic rule.
• Data isolation – Separate accounts keep analytics, AI agents, and settings independent. For example, if you run two brands, you don’t want the AI agent for Brand A to see data from Brand B. Separate accounts ensure that. If you share one account across domains, all data mixes. That can skew reports and confuse AI behavior.
• Client or partner requirements – Some clients demand their own account for privacy or branding. If you are an agency, the client may want a dedicated account with their own login. They may also want separate reporting. This is a common scenario. Failing to respect this can break contracts.
• Budget – Each account incurs its own subscription fee. The cost scales linearly. If a single account costs $X per month, three accounts cost $3X. You need to decide if the benefits of separation are worth the extra cost. Sometimes it is cheaper to share one account, but you lose data isolation.
• Management overhead – More accounts mean more login credentials and admin tasks. You need to manage passwords, user access, and account settings for each one. If you have a large team, that overhead can grow. You also need to update credentials when staff leave. This is a real cost in time and risk.

These criteria often conflict. For example, a client may demand separate accounts, but that increases budget and overhead. You need to balance them. The decision framework below helps you make that trade-off.

Step‑by‑step decision framework

1. List every domain you plan to run SeaText on. Include all production domains. Do not include staging or development domains at this stage.
2. Ask if any domain needs separate reporting or data privacy. For example, if you have two unrelated businesses, separate accounts are wise. If they are closely related, a single account might work.
3. Check client contracts for account‑level requirements. Many agency agreements specify that the client owns their own account. Read the fine print.
4. Calculate total cost: multiply the per‑account price by the number of domains. Compare that to your budget. If the cost is too high, you may need to consolidate domains under one account, but only if they share a primary domain.
5. Assess admin capacity: can your team handle multiple logins and settings? If you have a dedicated admin, multiple accounts are fine. If you are a solo operator, one account is simpler.
6. Choose a single account only if all domains share the same primary URL, data policy, and budget constraints. For example, if you have www.example.com and shop.example.com, they are subdomains of the same primary domain. One account can work. But if you have example1.com and example2.com, you need separate accounts.
7. After choosing, test the setup. Ensure that each account is linked to the correct domain. Check that analytics and AI agents are working as expected.

Common pitfalls

• Trying to use one account for a development site – SeaText blocks non‑real domains. You might think you can use a staging subdomain, but it will not work. Create a separate account for staging, or use a real domain for testing.
• Assuming separate accounts are free – each adds a subscription charge. Some people assume that SeaText allows unlimited accounts. That is false. Every account costs money.
• Forgetting to update credentials when staff change – multiple accounts increase this risk. A former employee might still have access to an old account. You need to revoke access promptly. This is harder with many accounts.
• Sharing one account across multiple client websites – technically possible, but it violates data isolation best practices and may breach client agreements. You also mix analytics, making it hard to report per client.
• Not reading the pricing page – some people sign up for one account, then add domains later without realizing they need a new account. Always check the pricing page for exact details.

Practical scenarios

Scenario A – Single brand, multiple sub‑domains: If you run shop.example.com and blog.example.com under the same primary domain, one account works. You can use the same SeaText account for both. The AI agents will treat them as the same domain. This saves money and reduces admin.

Scenario B – Distinct client sites: Agency managing client1.com and client2.com should create separate accounts to keep data separate and meet client contracts. Each client gets their own login, their own analytics, and their own AI settings. This is the standard practice for agencies.

Scenario C – Ecommerce store with multiple country domains: If you have store.com, store.co.uk, and store.de, each is a separate domain. You need three accounts. Each country domain will have its own SeaText account. This allows you to tailor AI agents per market, but also triples the cost.

Scenario D – Developer with staging and production: You need one account for the production domain and a separate account for the staging domain. Staging domains are treated as development URLs. They are blocked in a production account. So you must create a separate account. That staging account will have its own subscription fee.

Limitations

SeaText does not allow a single account to manage development URLs or dynamically generated domains. Each account must be tied to a valid, real domain. This is a security measure. It prevents abuse and ensures accurate traffic attribution. The limitation means you cannot use a single account for a wildcard domain or for a local development environment. You also cannot use a single account for a domain that changes frequently. If you need to test on a new domain, you must create a new account. This can be inconvenient, but it is designed to protect your data and the platform's integrity. Another limitation: you cannot merge accounts. If you start with separate accounts and later want to combine them, you cannot. You would need to delete one account and move settings manually. That is not supported. So plan carefully.

FAQ

• Do I need a separate account for a staging site? Yes. Staging URLs are considered development domains and are blocked in a production account. You need a separate account for staging.
• Can I share one account across multiple client websites? Technically possible, but it violates data isolation best practices and may breach client agreements. Most agencies avoid this.
• How much does an extra SeaText account cost? Pricing is per account; see the pricing page for exact numbers. The cost is the same as the first account.
• Is there a limit to how many accounts I can create? No hard limit, but each adds subscription cost and admin overhead. There is no cap, but your budget and team capacity will limit you.
• Can I use a subdomain as a separate account? No. Subdomains belong to the same primary domain. You cannot create a separate account for a subdomain. For example, blog.example.com is part of example.com.
• What if I have a wildcard domain? SeaText does not support wildcard domains. You must use a specific, real domain.
• Can I transfer settings from one account to another? No. There is no transfer feature. You would have to set up the new account from scratch.

Key facts

Quick Answer: Verify Installation and Wait for Activation

SeaText connects to HubSpot by embedding a JavaScript snippet in your site's Footer HTML. After pasting the code and publishing, you must visit your live site and stay on the page for at least 40 seconds. This visit triggers the AI activation and links the domain to your SeaText account. The SeaText dashboard will then display your website name next to the logo within five minutes. If the name is still missing after ten minutes, the installation likely failed — contact SeaText support right away.

How the HubSpot–SeaText Link Works

SeaText does not use an OAuth or API handshake with HubSpot. Instead, it relies on a client-side script that runs on your published HubSpot pages. The script sends a heartbeat to SeaText's servers when a real visitor loads the page. That heartbeat registers the domain in your SeaText account. Because the link is established by live traffic, the integration only completes after the script executes in a browser on your actual domain.

This design means you cannot test the connection in HubSpot's editor preview or on a staging subdomain that SeaText blocks (see Domain Restrictions). You must use the production URL that matches the primary URL registered in your SeaText account.

Step-by-Step Verification Checklist

1. Confirm the snippet is in the right place. In HubSpot, go to Settings → General → Advanced → Footer HTML. Paste the exact JavaScript snippet provided by SeaText. Do not wrap it in extra script tags or modify it.
2. Publish the changes. Click the orange Publish button at the top right of the HubSpot editor. Wait for the publish confirmation.
3. Visit the live page. Open the published URL in a browser. Stay on the page for at least 40 seconds. Do not use incognito mode, ad blockers, or script blockers that might prevent the SeaText script from loading.
4. Check the SeaText dashboard. Log in to your SeaText account. Look at the top of the page next to the SeaText logo. Your website name should appear there within five minutes.
5. If the name is missing after ten minutes, contact support. This signals an installation problem that SeaText's team must diagnose.

Common Reasons the Link Fails

Snippet Placed in the Wrong Field

HubSpot has multiple HTML fields (Head HTML, Body HTML, Footer HTML). SeaText's instructions specify Footer HTML. Placing the snippet in Head or Body HTML will not work because the script expects to load after page content.

Unpublished or Cached Changes

If you edited the Footer HTML but did not click Publish, the script never reaches visitors. Similarly, HubSpot's CDN or a browser cache may serve an old version. Hard-refresh the live page (Ctrl+Shift+R / Cmd+Shift+R) after publishing.

Domain Mismatch

Each SeaText account is tied to a single primary URL. If your HubSpot site lives on www.example.com but your SeaText account was created for example.com (or a development domain like staging.example.com), the heartbeat will not associate with your account. SeaText restricts development URLs such as localhost and dynamic preview domains for security reasons.

Multiple Domains Without Separate Accounts

If you run SeaText on more than one domain (e.g., a dev domain and a production domain), you must create a separate SeaText account for each domain. Sharing one account across multiple domains breaks the linking logic.

Script Blockers or Content Security Policy

Browser extensions (ad blockers, privacy tools) or a strict Content Security Policy on your HubSpot site can prevent the SeaText script from loading. Temporarily disable blockers and check your CSP headers if the dashboard stays empty.

Domain Restrictions and Multi-Site Rules

SeaText enforces two key constraints that directly affect HubSpot users:

• One primary URL per account. The account you create during sign-up locks to a single domain. You cannot add additional domains later.
• No localhost or dynamic preview domains. HubSpot's live preview URLs (e.g., hs-sites.com preview links) and local development environments are blocked. You must use a real, publicly resolvable domain.

If you need SeaText on a HubSpot staging environment, you have two options: (1) map a real subdomain (e.g., staging.yourdomain.com) to the HubSpot staging content and create a separate SeaText account for it, or (2) test only on the production domain.

What Happens After the Link Is Established

Once your website name appears next to the SeaText logo, the integration is active. You can then:

• Open the Main AI Hub in SeaText to activate specific AI agents (CRO, translation, personalization, etc.).
• Use Configuration to adjust AI parameters per page or site-wide.
• Edit automatic translations and copy variants under Variants Edit in the left panel.

The AI remains inert until you explicitly activate agents, so your HubSpot content stays unchanged until you decide otherwise.

Limitations of the Current Integration

• No bidirectional data sync. SeaText reads page content via the script but does not push changes back into HubSpot's CMS. Edits you make in SeaText's Variants Edit panel live only in SeaText's delivery layer.
• No HubSpot workflow triggers. You cannot enroll contacts in HubSpot workflows based on SeaText events.
• Single-account, single-domain model. Agencies managing multiple client HubSpot portals need a distinct SeaText account (and billing) for each client domain.
• Support-dependent troubleshooting. If the ten-minute window passes without a link, you cannot self-diagnose further; you must open a support ticket.

Key Facts at a Glance

Frequently Asked Questions

Can I test the integration on a HubSpot preview URL?

No. SeaText blocks dynamic preview domains (e.g., hs-sites.com links). You must publish to your real domain and visit that URL.

What if I have a HubSpot multisite setup with multiple brand domains?

Create a separate SeaText account for each brand domain. Each account gets its own snippet, dashboard, and billing.

Does the snippet slow down my HubSpot pages?

The script loads asynchronously and remains inert until you activate agents in the SeaText dashboard. No measurable impact on page speed before activation.

Can I use Google Tag Manager instead of Footer HTML?

SeaText's documented method is Footer HTML. GTM deployment is not covered in the official integration guide; if you attempt it, you are outside the supported path and SeaText support may not troubleshoot it.

What should I tell support if the link fails?

Provide: (1) your SeaText account email, (2) the exact HubSpot domain, (3) a screenshot of the Footer HTML field showing the pasted snippet, (4) confirmation that you published and visited the live page for 40+ seconds, and (5) the time you waited before checking the dashboard.

Will SeaText work on HubSpot landing pages and blog posts automatically?

Yes. The Footer HTML field applies site-wide, so every published page that uses the default template inherits the snippet. Custom templates that omit the global footer will need the snippet added manually.

Can I disconnect a domain from one SeaText account and attach it to another?

The source documentation does not describe a domain-transfer process. Since each account locks to a primary URL at creation, assume you must create a new account for the new domain and deactivate the old one.

Why Odoo Version Compatibility Matters for Multi-Site Setups

If you run more than one website on Odoo, you need to know whether SeaText AI works with your version before you invest time in setup. An incompatible version means you cannot embed the SeaText AI script, which leaves your secondary sites without AI-powered content optimization. Checking compatibility first saves you from rework and keeps every site in your portfolio on the same page.

Odoo releases new major versions roughly every year, and each version can change how custom modules, themes, and embedded code behave. SeaText AI's integration relies on Odoo's Website module and its Embed Code feature, so any version that supports that module can potentially work with SeaText AI. The question is not just whether the version runs, but whether the integration path matches your workflow.

How SeaText AI Connects to Odoo Websites

SeaText AI integrates with Odoo through a JavaScript code snippet that you place inside each website's editor. You do not need a native Odoo module or server-side installation. The process starts in Odoo's Website module, where you open the editing panel, locate the Embed Code block under Dynamic Content, and paste the script provided by SeaText AI.

Once the code is embedded and saved, SeaText AI becomes active on that specific domain. The AI remains inert until you activate it from your SeaText AI dashboard. This client-side approach means the integration depends on Odoo's front-end editing capabilities rather than on backend API compatibility, which is why the version requirement is tied to the Website module's availability rather than to a specific Odoo API version.

Supported Odoo Versions at a Glance

SeaText AI supports Odoo 13 and every later major release through Odoo 17. This includes Odoo 14, Odoo 15, Odoo 16, and Odoo 17. Each of these versions includes the Website module and the Embed Code feature that SeaText AI requires. Newer versions such as Odoo 18 and Odoo 19 are not explicitly listed in the current source documentation, but because the integration uses standard JavaScript embedding, they are likely compatible as long as the Website module and Embed Code block remain available.

Use this table as a quick reference. If your Odoo version is 13 or higher, you can proceed with setup. If you are on Odoo 12 or earlier, you will need to upgrade before SeaText AI integration is possible.

Decision Criteria: Confirming Your Version Is Compatible

Before you begin, run through these four criteria to confirm your Odoo setup is ready for SeaText AI on multiple websites.

1. Odoo version is 13 or later. This is the hard minimum. Versions before 13 lack the Website module structure that SeaText AI's embedding method requires.
2. The Website module is installed and active. Even on a compatible Odoo version, the Website module must be enabled. Without it, you cannot access the Embed Code block.
3. You can edit page blocks. Your Odoo user role must have permission to edit website pages and drag modules into the editor. Restricted access roles will block the integration.
4. You have a valid domain for each site. SeaText AI requires a real, public-facing domain. Development URLs such as localhost are restricted for security reasons.

If all four criteria are met, your Odoo version is compatible and you can move to setup. If any criterion fails, address that gap first. Upgrading Odoo, enabling the Website module, adjusting user permissions, or registering a valid domain are all prerequisites that cannot be skipped.

Multi-Website Setup Options and Trade-offs

SeaText AI offers one primary approach for multi-website integration: a separate SeaText AI account for each domain. This is not a limitation of the software but a structural requirement. Each SeaText AI account is linked to a single primary URL, so running three Odoo websites means managing three SeaText AI accounts.

The trade-off is straightforward. On the positive side, each account operates independently, so changes to one site's AI settings do not affect the others. On the negative side, you manage multiple dashboards, multiple billing cycles, and multiple code snippets. There is no single dashboard that controls all domains from one account.

An alternative some teams consider is using a single primary domain with subdomains or subdirectories for secondary sites. In that case, you still need separate SeaText AI accounts for each distinct domain, but you can centralize content strategy from one team dashboard while keeping the technical accounts separate.

Step-by-Step Verification and Installation

Follow this process to verify compatibility and install SeaText AI on each Odoo website.

1. Check your Odoo version. Log into your Odoo backend and navigate to the About menu. Confirm the version number is 13 or higher.
2. Enable the Website module. Go to Apps, search for Website, and install it if it is not already active.
3. Log into your SeaText AI account. If you do not have one, create an account at the SeaText AI sign-up page. You need one account per domain.
4. Copy the JavaScript code. In your SeaText AI dashboard, locate the code snippet provided for your domain.
5. Open the Odoo Website editor. Navigate to the page you want to edit and click the Edit button to open the editing panel.
6. Add the Embed Code block. In the Blocks panel, find the Dynamic Content section, locate the Embed Code module, and drag it into position.
7. Paste the code. Click the Edit button on the Embed Code block, paste the SeaText AI script, and click Save.
8. Set visibility. In the Visibility section, select the Hide on Desktop option if the block should only affect mobile views, then click Save again.
9. Repeat for each domain. Each Odoo website needs its own SeaText AI account and its own code snippet.

This process takes under one minute per site once you are familiar with it. The installation is secure, and the AI remains inactive until you activate it from your SeaText AI dashboard.

Limitations and When This Advice Does Not Apply

The compatibility guidance above applies to standard Odoo Community and Enterprise editions that include the Website module. If you are using a heavily customized Odoo build where the Website module has been removed or replaced, the Embed Code method may not work, and you would need to consult SeaText AI support for an alternative integration path.

Development and staging domains present a specific limitation. SeaText AI restricts localhost URLs and dynamic development domains because the system cannot reliably associate traffic with your account. You must use a valid, public domain for each site you want to optimize. If you need to test on a staging environment, set up a temporary public-facing URL or use a domain alias.

This article does not cover Odoo versions before 13. Those versions are not supported, and no workaround exists within the standard integration method. Also, the source documentation does not explicitly confirm compatibility with Odoo 18 or Odoo 19. While the JavaScript-based integration is likely forward-compatible, you should verify with SeaText AI if you are running a version newer than 17.

FAQ

Does SeaText AI work with Odoo 12?

No. SeaText AI requires Odoo 13 or later. Odoo 12 and earlier versions do not support the Website module structure that the SeaText AI JavaScript embedding method depends on.

Can I use one SeaText AI account for multiple Odoo websites?

No. Each domain requires its own separate SeaText AI account. Every SeaText AI account is linked to a single primary URL, so you must create one account per website.

Do I need to install a native module on Odoo?

No. SeaText AI integrates through a JavaScript code snippet placed in Odoo's built-in Embed Code module. There is no server-side module to install.

What if my Odoo site is on a staging or development domain?

SeaText AI restricts localhost and development URLs for security reasons. You must use a valid, real domain. Dynamic development domains may not function properly because SeaText AI cannot reliably associate traffic with your account.

Are Odoo 18 and 19 supported?

The current source documentation explicitly lists support for Odoo 13 through 17. Odoo 18 and 19 are not explicitly confirmed, but because the integration uses standard JavaScript embedding, they are likely compatible. Check with SeaText AI if you are running a version newer than 17.

How long does the installation take per website?

Under one minute once you are familiar with the process. You log into Odoo, add the Embed Code block, paste the SeaText AI script, and save.

Yes — you can edit the AI-generated text variants in SeaText. When the AI rewrites a page for a keyword, it shows you the new copy right away. If you are not happy with it, you can edit the text manually, give the AI instructions to improve, or switch the optimization off.

This is not a hidden setting. The SeaText workflow is built around review and control. You choose which keywords trigger rewrites, check what the AI produces, and keep the final say over what goes live.

What counts as an AI-generated text variant?

A text variant is one rewritten version of your page, matched to a keyword. For example, the same landing page might have one variant for "office space" and another for "apartment to rent." Each variant is designed to continue the promise in the ad that brought the visitor.

SeaText doesn't replace your whole website with artificial copy. Instead, it swaps the parts that affect relevance: the headline, key copy, offer, product blocks, and CTA. The result is that one page behaves like many keyword-specific pages.

From an editing standpoint, "variant" just means the text that exists for a specific search. You can treat it like a draft. You can keep it, change it, or tell the AI to do better.

How the keyword-to-text rewrite works

SeaText detects the keyword from your ad's URL parameters. When a visitor clicks, the AI rewrites the page in real time to match that search. This happens before the landing page appears in the browser.

1. SeaText automatically detects keywords from your ads and adds them to a list.
2. You choose which keywords you want to personalize.
3. A visitor clicks an ad for one of those keywords.
4. The AI rewrites the page text to match the visitor's search.
5. You review the rewritten version as soon as it is produced.

Because the rewrite is automatic, you don't have to build a new page for every keyword. But automatic doesn't mean final. Your review step is where editing happens.

Step by step: review and edit a variant

Editing is part of the normal workflow, not an afterthought. Here's the sequence:

1. Add SeaText to your site. The homepage describes this as a setup that takes under one minute.
2. Activate the agent that handles landing page rewrites. In the agent list, this is called Google Ads Landing Page AI or the Google Ads Agent.
3. Let SeaText collect keywords from your ad URLs. It automatically adds them to your keyword list.
4. Choose which keywords should trigger a rewrite. Only those keywords get personalized text.
5. Review the new copy immediately in the interface.
6. If the variant is wrong, edit the text by hand.
7. If the variant is close but the tone or format is off, give the AI a clear instruction.
8. If you don't want rewriting on a page, turn the optimization off.

The key point is order. Review comes first. The manual edit is a deliberate control, not a repair job.

What to check in every variant before you publish

• Does the headline match the keyword and the ad? The whole point is continuity between the ad and the page.
• Is the offer still correct? The AI may rewrite the CTA, so verify it points to the right action.
• Are product names and prices accurate? These are the details a human review catches best.
• Does the tone sound like your brand? If it doesn't, edit it or add an instruction.

You don't need to treat every variant as a manuscript. But the checks above protect the parts of the page that affect trust and conversion.

When to edit, when to instruct, when to turn it off

All three options exist for a reason. Your choice should match the problem you're seeing.

Edit manually when...

• A single fact is wrong, such as a date, price, or product name.
• The AI chose a word your brand would never use.
• You need exactly one sentence changed and the rest is fine.

Give the AI instructions when...

• The same problem repeats across many keywords.
• You want a consistent tone, style, or formatting rule.
• You can describe the improvement faster than editing dozens of variants.

Turn the optimization off when...

• A page must stay fixed, such as legal, compliance, or regulated copy.
• You no longer want keyword-level personalization for that page.
• You want to start fresh after too many edits.

Key facts: SeaText editing controls

The table below summarizes what the SeaText source material says about your control over generated text.

All of these controls are part of the same workflow. You don't need a separate tool or an admin request to edit.

Limitations and when editing won't help

Editing text variants changes wording. It doesn't fix every landing page problem.

• The AI depends on the keyword being passed through the ad URL. If the keyword isn't detected, there's no variant to edit.
• A rewritten text variant is not a new URL. It is the same page shown with different copy. If you need a separate page for tracking or compliance, create a real page instead.
• Editing fixes copy, not layout, speed, offer, or audience fit. A strong variant can still lose if the page loads slowly or the offer is weak.
• Your manual review is the last check. Keep reading the rewritten copy for factual errors, pricing mistakes, and legal wording.

If you publish every variant without review, you may send visitors to a page that doesn't match your offer or your tone. Editing is the way to keep AI speed without losing brand control.

Common mistakes and practical scenarios

Mistake: turning off AI after one bad variant

One wrong headline is not a reason to disable the whole system. Edit the headline, check the next variant, and see whether the pattern repeats.

Mistake: editing every variant by hand when the problem is systemic

If every variant reads too formally, give the AI an instruction once. You can still do manual tweaks later. This saves time and keeps consistency.

Mistake: treating variant editing as a CMS

Text variants are not a replacement for your site builder. Use the editor for the copy that changes by keyword. Manage page structure and design in your normal workflow.

Hypothetical example: a product page

A product page gets a rewrite for "leather office chair." The headline is right, but the AI changed the product name. Edit that one phrase manually and keep the rest of the generated copy.

Hypothetical example: a tone problem

Your brand uses short, direct sentences. The AI produces wordy variants for every keyword. Add an instruction like "Use short sentences and everyday words," review the next rewrites, and make manual fixes only where needed.

FAQ

Can I edit a variant after the AI has generated it?

Yes. Review the new copy immediately and manually edit the text when it isn't right.

What happens when I give the AI instructions?

The AI uses your instructions to improve the copy it produces. This is the second control after manual editing.

Can I stop the AI from rewriting specific keywords?

Yes. You choose which keywords the AI should rewrite. You can also turn the optimization off entirely.

Do I need to know code to edit the variants?

No. The workflow is described in terms of editing copy and giving instructions, not writing HTML or CSS.

Is editing included, or does it cost extra?

The source pack does not list an editing fee. Manual editing is described as one of the standard controls. Check the pricing page for current plan limits.

What should I compare when choosing a tool for AI text variants?

Compare keyword control, review speed, editing options, the ability to turn rewriting off, and whether the tool rewrites the page in real time or creates separate pages. The option that fits a paid ads team may not fit a compliance-heavy site.

Common causes of connection failure

When SeaText AI does not connect after installation on Shopify, the problem is almost always one of five things: the API key is incorrect, the Shopify app lacks required permissions, the JavaScript code snippet is in the wrong file, you are using a development domain, or there is a server-side issue.

Each cause requires a different fix. Guessing wastes time. Follow the diagnostic order below.

Why connection problems matter

If SeaText AI cannot connect, its agents cannot work. Your visitors will not see optimized copy, personalized content, or AI-powered recommendations. You lose potential sales and data insights.

For example, the Google Ads Landing Page Agent rewrites pages for each keyword. Without a connection, every visitor sees the same generic page. That lowers conversion rates.

Similarly, the AI SEO Content Factory cannot publish new pages. The Bot Protection Agent cannot block fraudulent clicks. Your investment in SeaText AI is wasted until the connection is fixed.

Quick troubleshooting saves time and money. Understanding the root cause helps you avoid repeating the same mistakes.

Diagnostic sequence

Start with the most likely cause. Move down the list only if the previous step does not solve the issue.

1. Check your API key. Log into your SeaText account and copy the API key again. In Shopify, go to the SeaText app settings and paste the key exactly. A single missing character breaks the connection. Why? The API key is the unique identifier linking your Shopify store to your SeaText account. If it does not match, the server rejects the request. Trade-off: If you have multiple SeaText accounts, you might copy the wrong key. Make sure you use the correct one for this store.
2. Verify Shopify permissions. The SeaText app needs access to your theme files and product data. Go to your Shopify admin, click Settings > Apps and sales channels, and ensure SeaText has the required permissions enabled. If not, reinstall the app. Without permissions, the code snippet cannot read or write to your theme. This is a common oversight after app updates.
3. Confirm the code snippet placement. Open your active theme in Shopify (Online Store > Themes > Edit code). The snippet must be pasted in the theme.liquid file inside the <head> tag. If you placed it in a different file, move it. The snippet must be in the layout file that loads on every page. If it is in a template file, it will not appear on all pages, and the connection will fail.
4. Check your domain. SeaText restricts development URLs like localhost or .myshopify.com preview domains. You must use a real, live domain. If you are testing on a development store, switch to a production domain. SeaText blocks these for security reasons. Dynamic development domains may not function properly.
5. Test with a different browser or clear cache. Browsers sometimes cache old scripts. Try an incognito window or a different browser after clearing your cache. Also clear your Shopify cache if you edited the theme file. This is a quick check that can save time.
6. Check for server-side issues. Sometimes the problem is not on your end. Shopify servers may be down for maintenance. Or a CDN cache may not have updated with the new snippet. Visit the Shopify status page to see if there is an ongoing outage. Also check your hosting provider if you use a custom domain. Server-side issues are rare but can cause intermittent connection failures. If you see a timeout error, this is likely the cause.

If none of these steps work, contact SeaText support with a screenshot of the error message.

How SeaText AI connects to Shopify

SeaText AI connects to your Shopify store by injecting a small JavaScript snippet into your theme. This snippet sends visitor behavior data to SeaText's servers and activates the AI agents you choose. The installation is secure: the AI remains inert until you activate it from your SeaText dashboard.

According to the official SeaText integration guide, the process is: copy the code snippet from your SeaText account, paste it into theme.liquid inside the <head> tag, and save. Then implement the required data attributes in your product templates. A successful connection requires that the snippet is present in every page's HTML source.

Key facts about installation

When troubleshooting does not apply

The diagnostic steps above assume you followed the standard installation. If you use a custom-built theme, a third-party app that modifies the theme files, or a Shopify Plus store with advanced permissions, the connection issue may be unique to your setup. In those cases, check with your theme developer or SeaText enterprise support.

Also, if you installed SeaText AI on a store that is not yet published or is password-protected, the connection will not work. The store must be live and accessible to the public.

Frequently asked questions

Why does SeaText say my API key is invalid?

An invalid API key error usually means you copied the key from the wrong account, or the key includes a trailing space. Copy the key directly from your SeaText dashboard and paste it without any extra characters.

Can I use SeaText on a Shopify development store?

No. SeaText blocks development URLs like .myshopify.com preview domains and localhost. You must use a live, public domain.

What if I have multiple Shopify stores?

Create a separate SeaText account for each store. Each account is tied to one primary domain.

Does the code snippet need to be in every page?

Yes. The snippet in theme.liquid applies to all pages, but you must also add the data attribute to product descriptions. The integration guide explains how to wrap the product description output.

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

Connection is immediate after the snippet is saved and the page reloads. If it does not connect within a few minutes, run the diagnostic sequence above.

Will clearing my Shopify cache fix the connection?

Sometimes. If you edited the theme file but the old version is cached, clearing the cache or using a different browser can help. But the root cause is usually one of the five listed earlier.

What if the error message says "server not found"?

This could be a server-side issue. Check the Shopify status page for any ongoing outages. Also check your DNS settings if you use a custom domain. Wait a few minutes and try again.

Can a firewall or security plugin block the connection?

Yes. Some security plugins or firewalls may block the SeaText script. Whitelist the SeaText domain in your security settings. This is more common on custom setups.

Seatext AI connects to your Shopify store to analyze SEO performance and publish improvements. It needs read access to your products, collections, orders, and customer profiles. It also needs write access to your theme files so it can add meta tags, schema, and the JavaScript snippet. You control those permissions during installation. This guide explains each data type, why Seatext needs it, and what to consider before granting access. Use this as a readiness checklist before you install the app.

Before You Install: Readiness Checklist

• You have a SEATEXT AI account linked to one primary domain.
• You can access your Shopify admin.
• You can edit the active theme.
• You understand the difference between read access and write access.
• You have a backup of your current theme.
• Your primary URL is a real domain, not localhost.
• If you use multiple domains, you are ready to create separate accounts.

What Data Does Seatext AI Read from Shopify?

Seatext reads product names, descriptions, tags, handles, and collection groupings. This content tells the AI what each page is about. It also reads order history to understand which products convert and which pages need attention. Basic customer profiles help the AI tailor meta descriptions and on-page copy. Seatext does not need payment card numbers or passwords. The permission request is limited to the store data needed for SEO analysis and optimization.

The AI uses this data to build a picture of your store's search landscape. It can compare your product titles against real search demand. It can see which collections are thin. It can spot order patterns that point to high-value pages. None of this requires access to payment processing or login credentials.

The AI also needs a connection to your storefront. Each Seatext account is linked to a single primary URL. That URL lets Seatext associate traffic and performance with your store. If you use multiple domains, you need separate accounts.

Why Products, Collections, Orders, and Customers Matter for SEO

Search engines decide which pages to rank based on relevance. Product titles and descriptions are often the strongest relevance signals. Collections show how your catalog is organized. Orders reveal demand. Customers reveal who buys repeatedly. Each data set fills a gap in the SEO picture.

Products and collections help the AI find keyword gaps. It can suggest more specific titles, better meta descriptions, and improved internal links. Orders help the AI see which items already produce revenue. It can focus optimization energy on best sellers instead of dead stock. Customer profiles help the AI avoid generic copy. It learns search behavior patterns that can improve click-through rates.

The result is not just a list of recommendations. The AI can write optimized tags and inject them into your theme. That automation saves time and keeps the store running.

How Seatext AI Uses the Data

Seatext runs an SEO audit of your store's current tags, headings, and content. It then generates and inserts optimized meta tags into your theme files. The JavaScript snippet in theme.liquid lets the AI connect visitor behavior to product and order data. The AI remains inert until activated. You decide which agents to turn on after installation.

For product descriptions, the integration can go further. In the product template, you wrap the product description output with a data-attribute. This lets the AI measure how visitors read each description. The process is described in the documentation on AI scope. You should test the change on a product page after saving.

The AI does not rewrite your entire website. It focuses on search-related elements: titles, meta descriptions, headings, schema, and selected copy blocks. The data access is designed to support that narrow task.

Shopify Permissions You Grant When Installing

When you install Seatext AI, Shopify shows a permission prompt. You grant read access to products, orders, and customers. You also grant write access to theme files. Read access lets the AI analyze your catalog. Write access lets it add SEO tags and the script. Without these permissions, the app cannot complete its core work.

You can review or revoke permissions later in Shopify admin. If you remove the app, the installed code should be removed too. Before you install, back up your theme. That makes it easy to restore if you need to undo a change.

Who should connect? A store owner who wants automatic SEO updates, an agency managing multiple client stores, or a merchant who wants AI-assisted product descriptions. Who should wait? Someone who only has a localhost development site. Seatext blocks localhost for security. Use a real domain or production store.

Step-by-Step: Connect Seatext AI to Your Shopify Store

1. Create a SEATEXT AI account. Each account is linked to one primary domain.
2. Copy the JavaScript code from the Seatext dashboard.
3. Log in to your Shopify admin.
4. Go to Online Store > Themes.
5. Click the three dots next to your active theme and select Edit code.
6. In the Layout folder, open theme.liquid.
7. Paste the JavaScript snippet into the file.
8. Click Save.
9. If you want product description tracking, open product.liquid or product-template.liquid. Wrap the product description output with a data-attribute and save.
10. Preview a product page and use browser developer tools to verify the data-attribute is present.

After the snippet is live, activate the Seatext agents you need. The dashboard lets you choose SEO, CRO, translation, and other agents. The code remains inert until you activate something.

Limitations, Security, and Privacy

The biggest limitation is domain handling. Seatext links each account to one primary URL. If you need to use the app on a development domain and a production domain, create separate accounts. Dynamic development domains may not work because Seatext cannot reliably associate traffic with your account. Localhost is restricted for security reasons.

Data access is read-only for your catalog. Seatext does not modify products, orders, or customer records. The write permission applies to theme files. Those files control how your storefront looks and include meta tags. The JavaScript snippet is required for the AI to run. Without it, no data is sent to Seatext.

The installation process is described as secure, and the AI remains inert until activated. For privacy details, review Seatext's current policy. You can also adjust permissions in Shopify if you want to limit access.

Frequently Asked Questions

• What exact data does Seatext read from my store? Products, collections, orders, and basic customer profiles.
• Does Seatext edit my product listings? No. Product data is read-only. The write permission is for theme files.
• Can I use Seatext on a test site? Localhost is restricted. Use a real domain. For a separate staging domain, create a separate account.
• Do I need a separate account for each store? Yes. Each account is linked to one primary URL.
• What happens if I uninstall the app? You remove the app and its permissions. You should also remove the JavaScript snippet from theme.liquid.
• Will the SEO tags affect the visible layout? Most SEO tags are meta elements. They are not visible to customers.
• Does Seatext need payment or credit card info? No. The app needs store data permissions, not payment data.
• Where is the installation documentation? See Seatext's Shopify integration page and documentation on AI scope.

Quick verification checklist

SeaText activates only after real visitor behavior is detected. The platform uses a 40-second dwell threshold and a five-minute dashboard sync window. Follow these steps in order:

1. Confirm you pasted the snippet in Wix Settings → Custom Code → Head, set to "All pages" and "Load code on each new page."
2. Open your live site in a regular browser window (not the Wix editor preview).
3. Stay on any page for at least 40 seconds. Scroll, click, or read — any activity counts.
4. Return to the SeaText dashboard. Wait five minutes.
5. Look for your website name next to the SeaText logo at the top of the page.

If the name appears, the script is installed, firing, and linked to your account. If it does not appear after ten minutes, something blocked the handshake — usually a caching layer, a second analytics script that strips custom code, or a Wix plan that does not allow custom Head code.

Prerequisites before you verify

Paid Wix plan required

Wix only allows custom code injection on paid plans. Free sites cannot load the SeaText snippet, so verification will never succeed.

Active SeaText account

Each domain needs its own SeaText account. The snippet you paste contains your account token. If you copied the snippet from a different account or a staging domain, the dashboard will not match.

Correct snippet placement

The snippet must be in the Head section, not Body or Footer. Wix's Custom Code UI places Head code before the closing tag, which is the only location SeaText supports.

Step-by-step verification process

1. Confirm the snippet is live

Open your site in an incognito window. Right-click → View Page Source. Search for "seatext" or the first few characters of your snippet. If you see it, Wix has published the code.

2. Trigger the activation dwell

SeaText's activation logic requires a genuine session of at least 40 seconds. Automated crawlers, bots, or instant redirects do not count. Visit the homepage or any high-traffic page and remain there. You can scroll slowly or read content — the timer is based on page visibility, not interaction depth.

3. Wait for the dashboard sync

After the dwell, the SeaText backend processes the session and associates the domain with your account. This takes up to five minutes. Do not refresh the dashboard constantly; check once at the five-minute mark.

4. Confirm the site name appears

In the SeaText dashboard, the top header shows the SeaText logo followed by your connected site name. That label is the definitive proof that the installation handshake completed.

What the dashboard shows when it works

Once the site name appears, you gain access to the Main AI Hub. From there you can activate individual agents — CRO Reading Analysis, Google Ads Landing Page AI, Website Translation, and others. Each agent has its own configuration panel. The presence of the site name means the data pipe is open; agent activation is a separate step.

Common reasons verification fails

Troubleshooting steps if the name does not appear after 10 minutes

1. Clear Wix cache: In Wix Dashboard → Settings → Advanced → Custom Code, click the three-dot menu next to your snippet → Edit → Apply again. This forces a fresh publish.
2. Test in incognito with browser dev tools open (Network tab). Filter for "seatext". You should see a 200 response for the script load and a subsequent ping to the SeaText collector endpoint.
3. Disable other custom Head scripts temporarily. Some analytics or consent-management scripts rewrite the DOM and can strip SeaText.
4. Confirm the domain in SeaText matches exactly (including www vs non-www). SeaText ties one account to one primary URL.
5. Contact SeaText support with your site URL and account email. They can see server-side whether pings arrived.

After verification: what to do next

With the site connected, open the Main AI Hub. Start with the AI CRO Reading Analysis agent — it begins analyzing visitor reading telemetry immediately and will surface copy friction points within hours. Enable the Google Ads Landing Page Agent if you run paid search; it rewrites headlines to match the keyword that triggered each click. Turn on Website Translation (125 languages) if you serve international traffic. Each agent can be toggled independently, so you can measure impact one at a time.

Key facts

Limitations and when this advice does not apply

• Wix Editor preview mode does not execute custom Head code — you must use the published live URL.
• Sites behind password protection or Wix member-only pages may block the SeaText collector ping.
• If you use a third-party CDN (Cloudflare, Cloudfront) in front of Wix, ensure it does not strip or defer the SeaText script.
• This guide covers the standard SeaText JavaScript snippet. Enterprise deployments using server-side injection or tag managers follow a different verification flow.

FAQ

Can I verify SeaText in the Wix Editor preview?

No. The preview iframe does not load custom Head code. You must visit the published site.

Does the 40-second timer reset if I navigate to another page?

Yes. Each page load starts a new session. Stay on one page for the full dwell.

What if I have multiple domains (staging and production)?

Create a separate SeaText account for each domain. The snippet is bound to the account's primary URL.

Why does the dashboard still show the install prompt after I pasted the code?

The prompt disappears only after the backend receives a valid ping from a 40-second session. Until then, it assumes the snippet is not firing.

Can I speed up the five-minute sync?

No. The sync is a fixed backend batch window. Waiting longer than ten minutes indicates a delivery problem.

Will SeaText work on a Wix site with a free plan if I use a custom domain?

No. Custom domain does not unlock Custom Code. You need a paid Wix plan.

What should I send support if verification fails?

Your live site URL, the SeaText account email, a screenshot of the Custom Code settings showing the snippet in Head, and a HAR file or Network tab export showing the script load attempt.

To select all pages for SeaText code in Wix, navigate to your Wix dashboard, open Settings, scroll to Custom Code under Advanced, click Add Code in the Head section, paste your SeaText JavaScript snippet, then under "Add Code to Pages" choose "All pages" from the dropdown and select "Load code on each new page" before clicking Apply. This single setting ensures the SeaText script loads on every page of your site, which is required for the AI to analyze visitor behavior and optimize content across your entire website.

Prerequisites Before You Start

Before you can install the SeaText code on Wix, you need two things in place. First, you must have a paid Wix plan. Wix only allows custom code injection on premium plans; free sites block the Custom Code section entirely. Second, you need an active SeaText AI account. If you don't have one yet, create it at seatext.com before proceeding. Each SeaText account is tied to a single primary domain, so if you manage multiple websites, you'll need a separate account for each.

Development environments like localhost or dynamic preview URLs are restricted for security reasons. SeaText cannot reliably associate traffic with your account on those domains, so use a real, live domain for installation.

Step-by-Step Installation Process

1. Log in to Wix and select the project you want to translate or optimize.
2. Open Settings from the left sidebar, then scroll all the way down to the Advanced section.
3. Click Custom Code — it sits at the very bottom of the Settings page.
4. Click "Add Code" under the Head section (not Body).
5. Paste the JavaScript snippet you copied from your SeaText dashboard into the "Paste the code snippet here" field.
6. Under "Add Code to Pages," open the dropdown and select "All pages".
7. Check "Load code on each new page" — this ensures the script fires on every navigation, including single-page transitions.
8. Click Apply to save.

That's it. The code is now deployed site-wide.

Why "All Pages" and "Load on Each New Page" Matter

SeaText's AI agents — including the CRO Reading Analysis agent, the Google Ads Landing Page agent, and the Personalization agent — need to observe visitor behavior on every page. If you only add the code to the homepage, the AI cannot track reading telemetry, scroll deceleration, or friction points on product pages, blog posts, or checkout flows. Selecting "All pages" puts the script in the <head> of every page load. The "Load code on each new page" option handles Wix's AJAX navigation: when a visitor moves between pages without a full reload, the script re-initializes so the AI continues collecting data.

Post-Installation Verification

After you click Apply, the installation isn't instantly visible in your SeaText dashboard. Follow these steps to confirm everything is connected:

1. Visit your live site (not the Wix editor preview).
2. Stay on the page for at least 40 seconds — this triggers the initial handshake between your site and SeaText's servers.
3. Refresh a few times and browse a couple of internal pages.
4. Wait at least five minutes, then check your SeaText dashboard. Your website name should appear next to the SeaText logo at the top of the page.

If the site name doesn't appear after 10 minutes, contact SeaText support. This usually indicates a platform-specific installation issue — for example, a caching plugin stripping the script, or a Wix setting blocking third-party scripts in the head.

Multi-Domain and Multi-Site Considerations

Each SeaText account maps to one primary URL. If you run a staging domain and a production domain, you need two separate SeaText accounts. The same applies if you manage multiple client sites: one account per website. You cannot add multiple domains to a single account, and you cannot share a single JavaScript snippet across domains. Create each account, generate its unique snippet, and install it on the corresponding Wix project following the steps above.

Common Mistakes and How to Avoid Them

Key Facts

Limitations and When This Guide Doesn't Apply

• Wix Studio vs. Wix Editor: The Custom Code location described here applies to the classic Wix Editor. Wix Studio may surface the setting in a different menu; consult Wix Studio documentation if you don't see Custom Code under Settings > Advanced.
• Third-party header injection apps: If you already use an app like "Header Code" or "Google Tag Manager" to inject scripts, you can paste the SeaText snippet there instead — but you must still configure the app to fire on all pages and on each navigation.
• Content Security Policy (CSP): If your site or a security app enforces a strict CSP, the SeaText script may be blocked. You'll need to add SeaText's domain to the CSP allowlist.
• Non-Wix platforms: This guide is specific to Wix. Shopify, WordPress, Webflow, and custom stacks have different installation paths.

Frequently Asked Questions

Do I need to reinstall the code after redesigning my Wix site?

No. As long as you stay on the same Wix project and don't delete the Custom Code entry, the snippet persists through design changes. If you duplicate the site to a new Wix project, you'll need to add the code again in the new project's settings.

Can I use the same SeaText account for a Wix site and a WordPress site?

No. Each SeaText account is locked to a single primary URL. You would need two accounts — one for the Wix domain, one for the WordPress domain.

What if I only want SeaText on certain pages, like landing pages?

You can choose "Specific pages" in the dropdown and pick individual URLs, but the AI's reading telemetry and personalization agents work best with full-site coverage. Partial installation creates blind spots in the conversion funnel.

How do I know the AI is actually working after installation?

Once your site name appears in the SeaText dashboard (5-10 minutes after the 40-second visit), go to the Main AI Hub and activate the agents you need — for example, AI CRO Reading Analysis, Google Ads Landing Page AI, or Website Translation. Each agent shows live data once it has enough visitor sessions.

Does the SeaText script slow down my Wix site?

The script loads asynchronously in the head and is designed for zero-flicker operation. SeaText's Split URL Testing agent, for instance, runs 0ms zero-flicker tests. In practice, the performance impact is negligible for most sites.

Can I install SeaText via Google Tag Manager on Wix instead?

Yes, if you already have GTM set up on your Wix site. Add the SeaText snippet as a Custom HTML tag, set the trigger to "All Pages" and ensure it fires on "Page View" and "History Change" (for AJAX navigation). The native Wix Custom Code method is simpler if you don't use GTM.

What happens if I cancel my SeaText subscription?

The script remains on your site but becomes inert — the AI agents stop processing. You can leave the code in place or remove it from Wix's Custom Code section. No data is collected after deactivation.

A scroll slowdown widget is a piece of client-side code that monitors scroll speed and intentionally adds gentle resistance when a visitor moves too fast through high-value areas of a page. The goal is not to frustrate users but to give them a brief, almost imperceptible pause near conversion-critical elements so the content has a chance to register.

SeaText packages this capability as the Scroll Slowdown Agent, one of 20+ autonomous AI marketing agents that install with a single script tag. The agent identifies CTAs, pricing tables, and other key sections automatically, then applies subtle deceleration only when scroll velocity exceeds a threshold that suggests the visitor might miss the content entirely.

How Scroll Slowdown Widgets Work

At a technical level, these widgets listen to the browser's scroll event (or the newer wheel and touchmove events) and measure velocity in pixels per millisecond. When velocity crosses a configured threshold inside a defined "slow zone" — typically a bounding box around a CTA button, pricing card, or testimonial block — the widget applies one of several deceleration techniques:

• RequestAnimationFrame easing: The widget takes over scroll animation for a few frames, applying an ease-out curve that feels like natural momentum loss.
• CSS scroll-snap hints: Modern implementations can toggle scroll-snap-type or scroll-snap-align on the target section to let the browser handle the pause natively.
• Passive wheel listeners with preventDefault: For touch and trackpad input, the widget can selectively cancel a fraction of wheel delta events, creating a gentle drag sensation.

The key design constraint is subtlety. If the visitor notices the interference, trust erodes. Most production widgets (including SeaText's) cap the slowdown at 15–30% of normal velocity and limit the duration to 300–800 milliseconds per zone encounter.

Why Scroll Speed Matters for Conversions

Eye-tracking and scroll-depth studies consistently show that visitors who scroll at high velocity past a CTA convert at significantly lower rates than those who dwell, even briefly. The mechanism is simple: comprehension requires fixation time. A pricing table scanned in 400 milliseconds communicates almost nothing; the same table viewed for 1.2 seconds lets the brain parse plan names, feature checkmarks, and the primary CTA.

SeaText's internal telemetry (described in their CRO Reading Analysis agent documentation) measures "Scroll Deceleration: The exact page coordinates where buying interest spikes before CTA exposure." This metric correlates with conversion lift because it identifies the moment a visitor transitions from scanning to evaluating.

Types of Scroll Slowdown Approaches

Takeaway: For marketing teams who cannot allocate engineering sprints to scroll behavior, the AI-driven auto-discovery model removes the maintenance burden. For teams with dedicated frontend resources who need pixel-perfect control, manual configuration remains viable.

SeaText's Scroll Slowdown Agent: What the Source Pack Confirms

• Listed as "Scroll Slowdown Agent z8y Subtly slow fast scrollers near CTAs and pricing" across multiple SeaText pages (S1, S2, S3, S4, S5, S7).
• Part of a 20+ agent suite that installs in "under 1 minute" (S1, S2, S7).
• Activates autonomously — no manual zone mapping required.
• Targets "CTAs and key sections" or "CTAs and pricing" specifically.
• Described as "subtle" — aligns with the 15–30% velocity reduction best practice.

No public documentation in the source pack specifies the exact velocity threshold, deceleration curve, or whether the agent respects prefers-reduced-motion. These are implementation details you would verify during a demo or technical onboarding.

Implementation Checklist

1. Audit current scroll behavior: Use Hotjar, Microsoft Clarity, or SeaText's own reading telemetry to identify sections where high-velocity scrolls correlate with low conversion.
2. Define success metrics: Dwell time in target zones, CTA click-through rate, form start rate — not just "scroll depth."
3. Test with reduced-motion users: Ensure the widget honors @media (prefers-reduced-motion: reduce) and disables itself entirely for those visitors.
4. Monitor for rage clicks: If scroll slowdown coincides with increased rapid clicking or keyboard navigation, the deceleration may be too aggressive.
5. A/B test the agent on/off: SeaText's multi-armed bandit framework (described in S6) can allocate traffic to the winning variant automatically.

Limitations and When Not to Use

• Accessibility risk: Visitors with vestibular disorders or motor-control impairments can experience nausea or loss of control. Always respect prefers-reduced-motion and provide a visible toggle.
• Mobile touch scrolling: Touch momentum scrolling is handled by the browser's compositor thread; JavaScript intervention is limited and can cause jank. Test extensively on iOS Safari and Chrome Android.
• Single-page applications (SPAs): Virtual scrolling, infinite lists, and client-side routing can confuse zone detection. The AI agent must re-scan after each route change.
• Content-heavy editorial pages: Slowing scroll in long articles frustrates readers who are skimming for a specific section. Restrict zones to conversion-critical UI only.
• Performance budget: Any scroll listener adds main-thread work. Keep the handler under 1 ms; use passive: true listeners where possible.

Key Facts

Terminology Quick Reference

• Scroll velocity: Pixels scrolled per millisecond; the primary trigger metric.
• Slow zone: A DOM bounding box (usually around a CTA or pricing card) where deceleration applies.
• Dwell time: Time the viewport spends intersecting a slow zone; proxy for content comprehension.
• Multi-armed bandit: An algorithm that dynamically allocates traffic to the best-performing variant (used by SeaText for copy testing; can also test scroll-slowdown on/off).
• prefers-reduced-motion: CSS media query signaling the user wants minimal animation; scroll widgets must honor it.

Frequently Asked Questions

Does scroll slowdown hurt Core Web Vitals?

Not if implemented correctly. The widget runs only during active scroll, adds negligible main-thread work, and does not affect Largest Contentful Paint, Cumulative Layout Shift, or Interaction to Next Paint. However, a poorly written listener that blocks the main thread can degrade INP. Use passive: true event listeners and keep handler logic under 1 ms.

Will visitors notice and get annoyed?

If the deceleration stays under ~30% of normal velocity and lasts under 800 ms, most visitors perceive it as natural page "weight" rather than interference. Annoyance spikes when the effect is strong, frequent, or applied to non-conversion content (e.g., blog body text).

Can I target only paid traffic?

Yes. SeaText's Visitor Source Rewrite Agent detects referrer (Google Ads, Meta, email) and can conditionally activate the Scroll Slowdown Agent only for high-intent paid visitors. This avoids slowing down organic readers who may be researching rather than buying.

What about infinite-scroll feeds or product listing pages?

Not recommended. Infinite scroll relies on seamless momentum; adding friction breaks the mental model. Reserve slow zones for discrete conversion surfaces: signup forms, checkout CTAs, pricing tables, demo request buttons.

How do I measure if it's working?

Compare dwell time in target zones and downstream conversion events (CTA click, form start, purchase) between control and treatment groups. SeaText's dashboard surfaces reading telemetry (eye-line dwell velocity, friction points, scroll deceleration coordinates) that correlate with conversion lift.

Is there a free version or trial?

The source pack references a "Free Website Chat Agent" and "Free Authority Link Builder" but does not explicitly list a free tier for the Scroll Slowdown Agent. The pricing page (S1) offers "Click here for pricing" and "Book an Enterprise Demo" CTAs. Contact SeaText directly for current trial or freemium availability.

If SeaText AI fails to connect during Shopify setup, first retry the connection, confirm you are in the correct Shopify admin, and verify that the SeaText JavaScript snippet is installed in your active theme. Most connection failures come from a simple domain mismatch, a missing snippet, or an unsaved edit to theme.liquid.

The steps below follow the SeaText Shopify Integration guide. Use them in order, and test only when a step tells you to.

Do this before you retry

These checks take less than a minute and solve many failed connections.

• Wait 30 to 60 seconds, then retry the connection. Temporary network timeouts often clear on their own.
• Log into the Shopify admin for the exact store you want to connect. Check the store URL in the browser before you continue.
• Log into the SEATEXT AI account that goes with that store. The install requires an account before the script can connect.
• Open Online Store > Themes and confirm which theme is active. The snippet must go into the active theme.

Step-by-step recovery for a failed SeaText connection

Follow this order. Do not skip the verification step.

1. Open your SEATEXT AI account and confirm the script is visible. The JavaScript code appears in the integration section of your account. Copy it from there, not from another page.
2. Check the primary URL. Each SEATEXT AI account is linked to a single primary URL. Compare that URL to the exact Shopify storefront URL, including any www or subdomain.
3. Open your Shopify theme editor. Go to Online Store > Themes. Click the three-dot icon next to the active theme and choose Edit code.
4. Open theme.liquid. In the file list, find the Layout folder and select theme.liquid.
5. Paste the snippet and save. Place the SeaText JavaScript snippet where the integration guide shows, then click Save. Make sure the save finishes before you leave the page.
6. Reload with a clean view. Open the store in an incognito window or hard-refresh the page. A cached copy can make the connection look broken.
7. Preview a product page and inspect the HTML source. In your browser’s developer tools, verify that the data- attribute is present. This is the final proof that the snippet is live.

If the data attribute appears, the script is loaded. The remaining issue is likely on the account side, so move to the account checks below.

What “fails to connect” usually means

During Shopify setup, “fails to connect” means SeaText cannot match the script on your site to your SeaText account. The script may be missing, on a different domain, or on a domain SeaText does not accept.

The domain match matters more than the connection button. SeaText ties each account to one primary URL. If the store URL and that primary URL are not identical, the connection cannot stick.

This is also why you should not ignore the failure. A half-completed setup leaves the snippet on the page without an active account match, and later agents will not be able to run. The installation itself is secure, and the AI stays inert until activated, so you can retry without changing your live content.

Key facts to check during Shopify setup

Use this table as a quick checklist whenever setup fails.

Common setup mistakes that break the connection

• Wrong theme file. The snippet belongs in theme.liquid inside the Layout folder of the active theme.
• Unsaved edits. The code can look installed in the editor while the live page still has the old file.
• localhost testing. Development URLs such as localhost are restricted for security reasons, so the connection fails.
• Dynamic development domains. These may not work because SeaText may be unable to reliably associate traffic with your account.
• One account for two domains. You need a separate account for each domain, including a separate account for a development and production pair.
• Checking the wrong product template. The product description is usually in product.liquid or product-template.liquid. Inspect the page that actually renders the description.

When the connection failure is an account or domain problem

If the snippet is in the right file and the data attribute appears, the problem is usually account-side.

• Compare the store URL to the primary URL on the account. Include the protocol, the www, and any subdomain.
• If you run more than one website, create one account per website.
• If you use a development domain and a production domain, create separate accounts for each.
• If you use a dynamic development domain, expect it to fail. Switch to a valid real domain.

Start a fresh connection only after the account and domain are aligned.

Limitations to know before you retry

• One SEATEXT AI account is linked to one primary URL.
• One account per website is required when you use SeaText on several websites.
• localhost and similar development URLs are restricted.
• Dynamic development domains may not function properly.
• The AI remains inert until activated, so a successful connection alone will not change your site.

SeaText AI connection FAQ

Why does SeaText fail when I test on localhost?

SeaText restricts development URLs such as localhost for security reasons. Use a valid real domain instead.

Can one SeaText account cover two Shopify stores?

No. Each account is linked to a single primary URL, and SeaText requires separate accounts for separate websites.

What is a primary URL?

It is the main domain registered to your SeaText account. The storefront URL must match it for the script to connect.

How do I know the snippet is actually loaded?

Save the theme file, preview a product page, and inspect the HTML source in your browser’s developer tools. The data- attribute should be present.

I saved the code but the connection still fails. What should I do next?

Check that you pasted into the active theme’s theme.liquid, not a duplicate theme or the wrong template. Then compare the account primary URL with the store URL. If both are correct, create a separate account if you are using a second domain.

Will SeaText change content as soon as the snippet is installed?

No. The installation process is secure, and the AI remains inert until activated.

Where to get the exact integration steps

The SeaText Shopify Integration page is the reference for this recovery. It shows where the JavaScript code comes from, which theme file to edit, and how to verify the data- attribute. Keep it open while you retry the connection.

Open the Shopify Integration guide and run through the checklist once more.

SeaText AI is not connecting after you installed it on Shopify? The most likely reason is that the JavaScript snippet never actually made it into the theme that your store is using. The second most common reason is a domain mismatch between your SeaText account and your Shopify store. The third is that you are testing on localhost or a dynamic development URL, which SeaText restricts for security reasons.

This is not an app install. SeaText AI connects through a JavaScript snippet that you paste into a Shopify theme file called theme.liquid. If the snippet is absent, misplaced, or not saved, SeaText cannot connect. If it is in a preview theme or on the wrong domain, the script may load but the connection still fails.

Why the connection depends on a snippet, not an app icon

Many Shopify users expect SeaText AI to show up in the Shopify App Store. That is not how this integration works. SeaText AI lives on your website as a JavaScript snippet.

Here is the normal install flow:

• You need a SeaText AI account first.
• SeaText provides a JavaScript code snippet from your account.
• You paste that snippet into a Shopify theme file called theme.liquid.
• You save the theme file.

theme.liquid is the master layout file for a classic Shopify theme. When you place a script there, it can load across your store pages. That matters because SeaText needs to see traffic on the pages you care about, not just one product page.

Consequence of ignoring this: you may think the software is broken when it never loaded. A five-minute check of the active theme fixes most cases.

The install is also intentionally safe. The integration guide says the installation process is secure, and the AI remains inert until activated. So a correct install is not the same as a running agent. If you have not activated the SeaText feature you want, that can look like a connection failure.

The common mistake: editing an inactive theme or forgetting to save

Shopify can have several themes installed. Only one is the active theme. The integration guide tells you to open Online Store > Themes, then choose Actions > Edit code for the active theme. If you open a different theme, the snippet will not run on your store.

After you paste the snippet, you must click Save. Pasting without saving is a classic cause of a not connecting report. The snippet may be visible in the editor, but it is not stored in the file that Shopify serves.

Another file-related mistake is placing the code in the wrong file. The guide points to the Layout folder and a file called theme.liquid. If you paste the snippet into a CSS file, a section file, or a different liquid file, it will not work the same way.

How to check: load your live store, open your browser’s developer tools, and inspect the HTML source. If you do not see the SeaText script, the snippet is not in the theme being served.

Domain mismatch: one account, one primary URL

Each SeaText account is linked to a single primary URL. That URL must match the Shopify store domain you are using.

If your account was created for www.example.com but your Shopify store is example.myshopify.com, SeaText will not reliably associate the traffic. The script might load, but the account side sees a different site.

The fix is simple: use the account that matches the exact domain, or create a separate account for each domain. The integration guide is explicit: if you need to use SeaText on multiple domains, such as a development domain and a production domain, you must create separate accounts for each domain.

Trade-off: separate accounts per domain mean a little more setup work. In return, you avoid mixing traffic from different stores and you get a clear primary URL for each account.

Consequence of ignoring this: the script runs, but SeaText cannot connect the traffic to your account. Features that depend on visitor context will not trigger correctly.

Why localhost and dynamic development domains break the connection

Local development URLs like localhost are restricted for security reasons. SeaText cannot treat a local server as a real store.

Dynamic development domains may also fail. If the domain changes between previews or sessions, SeaText cannot reliably associate traffic with your account. The source guide says those domains may not function properly.

Use a valid, real domain when you test. If you are using a staging subdomain, create a separate SeaText account for it. Do not expect one account to cover localhost, staging, and production at the same time.

Diagnostic checklist: where to look first

Work through this order. It covers the causes in the official integration guide.

1. Confirm you have a SeaText AI account. The guide says you need one before installing the script.
2. Copy the JavaScript code from that account. Make sure it is the snippet for the same domain you are testing.
3. In Shopify admin, go to Online Store > Themes.
4. Click Actions > Edit code for the active theme, not a preview theme.
5. Open Layout > theme.liquid.
6. Paste the SeaText code snippet.
7. Click Save.
8. Load your store page and inspect the HTML source with developer tools to confirm the script is present.
9. Check that the domain in your SeaText account matches the store domain.
10. If you are using a development domain, switch to a real domain.
11. Confirm that the AI agent or feature you want has been activated. The script stays inert until activated.

If all of these are correct and SeaText still will not connect, review the integration documentation again and compare your setup line by line.

Key facts about the SeaText–Shopify connection

Limitations: when these fixes don't apply

These steps apply to the Shopify integration described in the source guide: a JavaScript snippet in the active theme. If you are using a custom checkout, a headless storefront, or a developer-managed deployment, the exact file paths may differ.

If you expected a one-click app from the Shopify App Store, this article explains why that expectation is the root problem. SeaText connects through a script, not through an app toggle.

If you have not created a SeaText account, no snippet exists to install. The guide treats an account as a requirement, not an option.

The source guide also covers product description optimization. That process has an extra step: wrap the product description output and verify that the data attribute appears in the HTML source. If your goal is product description changes, check that step as well.

Frequently asked questions

Why does SeaText AI work in the preview but not on the live store?

The likely cause is a theme mismatch. You probably pasted the snippet into a preview or inactive theme. Re-check that you edited the active theme and saved the file.

Can I use one SeaText account for staging and production?

No. Each account is linked to one primary URL. If you need SeaText on more than one domain, create a separate account for each.

Does SeaText AI connect on localhost?

No. Localhost is restricted for security reasons. Use a real, valid domain when testing.

What does “AI remains inert until activated” mean?

It means pasting the script alone does not start the AI. You also need to activate the relevant SeaText feature or agent in your account.

How can I confirm the snippet is installed?

Open the active theme’s theme.liquid and look for the SeaText code. Then load your store and use developer tools to inspect the HTML source. You should see the script.

I have several Shopify domains. Do I need multiple SeaText accounts?

Yes, if you want SeaText on each domain. Each account is tied to one primary URL.

Is SeaText AI safe to install on Shopify?

According to the integration guide, the installation process is secure and the AI remains inert until activated. Still, review the snippet before pasting it and keep your account credentials private.

SeaText and Odoo's native SMS tools solve different problems. Odoo's built-in SMS features send transactional notifications — order confirmations, appointment reminders, delivery updates — from inside the ERP. SeaText installs as a JavaScript snippet on your Odoo-powered website and deploys autonomous AI agents that rewrite page content in real time, translate across 125 languages, run zero-flicker A/B tests, detect bot traffic in paid campaigns, and operate an autonomous sales chat that books meetings. If your goal is to send more or cheaper SMS messages, stay with Odoo or add a dedicated SMS gateway. If your goal is to convert more of the visitors already landing on your Odoo site, SeaText adds a layer Odoo does not provide.

What SeaText Actually Does on an Odoo Site

SeaText installs by pasting a JavaScript snippet into an Embed Code block on any Odoo Website page. The snippet loads a lightweight client that communicates with SeaText's AI agents. Those agents analyze visitor behavior, referral source, ad keywords, language, and scroll patterns, then rewrite headlines, offers, product descriptions, and CTAs in real time. They also serve a fully autonomous chat agent that can answer product questions, qualify leads, and book meetings without human operators.

The integration steps documented by SeaText: log in to Odoo, open the Website module, edit the target page, drag an Embed Code block from the Dynamic Content section, paste the SeaText snippet, save, and optionally hide the block on desktop. Each domain needs its own SeaText account; development URLs like localhost are restricted.

What Odoo Native SMS Actually Does

Odoo's SMS features live in the core ERP. They send outbound messages triggered by business events — sale order confirmed, invoice posted, delivery scheduled, appointment booked. You configure an SMS provider (IAP or custom gateway) in Settings, then use the SMS composer on records or automated actions. The system logs sent messages on the chatter. It does not touch website content, does not personalize pages, and does not run conversion experiments.

Forum discussions show developers often need to override the default sms.api class to plug in a custom provider, which requires Python development and maintenance across Odoo upgrades. Ringover and similar integrations add a UI inside Odoo for two-way messaging and call logging, but they remain communication tools, not website optimization tools.

Why the Comparison Exists

Buyers sometimes conflate "messaging" with "conversational AI on the website." SeaText's free AI website chat looks like a messaging widget, but it is an autonomous sales agent that reads the page, understands the product catalog, and closes conversations. Odoo's SMS is outbound-only notification plumbing. If you need two-way SMS conversations inside Odoo, look at Ringover, Twilio connectors, or the custom sms.api override path. If you need the website itself to sell better, SeaText is the relevant addition.

Decision Framework: Which Do You Need?

1. You need to notify customers by text. Use Odoo native SMS or a dedicated gateway. SeaText does not send SMS.
2. You run Google Ads and want each keyword to land on a matching page. SeaText's Google Ads Landing Page AI rewrites the page per keyword in real time — no new pages, no manual work.
3. You want to recover wasted ad spend from bot clicks. SeaText's Bot Protection Agent detects invalid traffic and generates forensic reports for Google/Meta refunds.
4. You serve international visitors. SeaText translates the entire site into 125 languages instantly; Odoo's website translation requires manual effort per page.
5. You want AI-generated SEO content at scale. SeaText's AI SEO Content Factory publishes thousands of indexed Q&A pages for long-tail traffic.
6. You want to influence what ChatGPT says about your brand. SeaText's ChatGPT Brand Visibility agent shapes LLM recommendations.

Key Facts

Limitations and When This Advice Does Not Apply

• SeaText does not send SMS, WhatsApp, or email notifications. It cannot replace Odoo's transactional messaging.
• SeaText requires a valid public domain; localhost and dynamic development domains are restricted.
• Each distinct domain needs its own SeaText account and snippet.
• The AI agents operate on the front-end website only; they do not read or write Odoo backend records directly.
• Performance claims (+35% conversion, 20% bot refund) come from SeaText's own marketing materials; independent verification is advised.
• If your Odoo instance is used only as a backend (headless) and the public site runs elsewhere, install SeaText on that public site, not on Odoo.

Terminology

• Embed Code block — Odoo Website builder block that accepts raw HTML/JS.
• Autonomous AI agent — A background process that observes visitor signals and rewrites page elements without manual rules.
• Zero-flicker split testing — Traffic routing at the edge so visitors never see a flash of the original page.
• Conversion Relay (CAPI) — Server-side event forwarding to Meta and Google for accurate attribution.
• Intent Amplifier — Sends high-intent buyer signals to ad platforms to improve audience modeling.

Frequently Asked Questions

Does SeaText replace Odoo's SMS notifications?

No. SeaText does not send SMS. It optimizes the website experience for visitors who are already on your site.

Can I use SeaText and Odoo SMS together?

Yes. They operate on different channels — SeaText on the website, Odoo SMS on mobile numbers. Many teams use both.

How long does SeaText installation take on Odoo?

Under a minute: paste the snippet into an Embed Code block and save. No module installation or ERP configuration required.

Will SeaText slow down my Odoo website?

The snippet is designed to load asynchronously. SeaText claims zero-flicker operation for split tests, but you should run your own Core Web Vitals check after install.

What does SeaText cost?

Pricing is not published in the source pack. SeaText offers a free 1-month pilot trial; contact them for a quote.

Can SeaText work on a headless Odoo frontend (React, Vue, Next.js)?

Yes, as long as you can inject the JavaScript snippet on the public pages. The integration is platform-agnostic.

Does SeaText read my Odoo product catalog automatically?

The AI agents analyze the rendered page content. For structured product data, you may need to ensure schema.org markup is present or feed data via the WebMCP agent.

If the SeaText AI script will not install on your Shopify store, do not assume the store is broken. Start with the basics: check your internet connection, make sure you are editing Layout/theme.liquid, and confirm your domain is public. Then work through the diagnostic sequence in this guide. Most installation failures come from a wrong file, a missing save, a copied snippet that lost characters, or a hidden caching issue.

This guide explains why a failed install matters, how SeaText installation works, what can block the script, and what to do after a successful install.

Why This Matters: The Cost of a Failed Installation

SeaText is not a decorative widget. It is an AI layer that changes what visitors see based on their source, search query, and reading behavior. If the script never loads, none of that happens.

Consider a paid Google Ads visitor. With SeaText, your landing page can rewrite its headline, offer, and call to action to match the keyword the visitor typed. Without the installed script, every visitor sees the same generic page. The page does not match the ad promise, so more visitors leave without buying. Your click spend is spent on visitors who never see a relevant message.

The same is true for bot traffic. SeaText detects bots in paid traffic and builds evidence for refund requests with Google and Meta. If the script is not installed, bot clicks are not flagged, and you cannot recover that wasted ad spend. A failure to install means lost conversion lift and lost refund opportunities.

Site performance is also part of the picture. A correctly placed snippet before </head> loads cleanly and stays inert until you activate it. A bad paste, such as code placed inside another script tag or in the middle of the body, can cause rendering delays and make the page feel slow. Fixing the install reduces those risks.

How SeaText Installation Works

SeaText gives you one JavaScript snippet from your account. That snippet must be pasted into the global theme file because Shopify uses theme.liquid to render every page. When placed before the closing </head> tag, the browser finds the script early. This is important because the script needs to observe page elements before the visitor starts reading.

The snippet itself does not change content. SeaText says the AI remains inert until activated. That means installing the script is not the same as turning on AI agents. After the snippet loads, you still need to log in to your SeaText account and activate the agents you want, such as the Google Ads Agent, Translation Agent, or Bot Protection Agent.

If you also want SeaText to optimize product descriptions, you may need to add a tag inside the product template. The goal is to mark the product description output so SeaText can identify it. After you save the product template, use your browser developer tools to confirm the data- attribute appears in the HTML source.

SeaText links each account to one primary URL. Multiple domains require separate accounts. Development URLs like localhost are restricted for security reasons. A real, publicly reachable domain is required.

What Can Block a SeaText Script from Loading

Even when the theme file looks correct, outside factors can stop the script from executing. Here are the most common blockers.

Content Security Policy (CSP)

A Content Security Policy is a set of browser rules that decide which scripts can run. Some Shopify stores add a CSP through a security app or custom code. If the policy does not allow the domain SeaText loads from, the browser blocks the request. The script tag stays in the HTML, but the script never runs.

If you use a CSP, whitelist the domain SeaText loads from. Check with SeaText support for the exact domain if you cannot find it in your account.

CDN and caching

Shopify uses a content delivery network to serve store pages. After you save a theme change, the new version is compiled and sent to the CDN. In most cases this happens within seconds. However, browser cache, Shopify cache, or a third-party caching app can serve an old version of theme.liquid for a while.

If you inspect the page and do not see the script, first clear your browser cache or open the store in an incognito window. If you use a caching app, purge its cache as well. Then reload the page.

Theme app extensions

Shopify themes can contain app extensions that inject their own scripts into the head. These extensions are controlled by other apps and may alter the order of scripts. An aggressive extension can remove or override code that was pasted manually.

If your theme uses many app blocks, disable non-essential apps temporarily. This helps you see whether another app is interfering. Then re-enable apps one at a time to find the conflict.

Script load order

JavaScript runs in the order the browser executes it. If SeaText is placed after a slow script, it may execute later than intended. If it is placed in the body, it may miss the early page events it needs. That is why SeaText should sit before </head> in the layout file, not in a page section or after a third-party widget.

Diagnostic Sequence: Find the Break Point

Use this sequence when SeaText does not install or does not appear after saving.

1. Check your network. A dropped connection can prevent the snippet from saving or loading. Open another site and reload the page.
2. Confirm the file path. You need Layout/theme.liquid, not a section file or a template file. The wrong file will not apply globally.
3. Check the domain. SeaText needs a real public domain. Development URLs and localhost are blocked. If you use a temporary store URL, install may fail.
4. Copy the full snippet. The dashboard may show a long JavaScript block. Copy from the first character to the last. Missing characters, such as a semicolon or a closing bracket, stop the script.
5. Save the file. Pasting without saving sends nothing to the live site. Look for the Save button and wait for the confirmation message.
6. Clear cache. Use incognito mode or clear the browser and CDN cache. Then reload the page and inspect the source.
7. Inspect the HTML. Right-click on the page and choose Inspect. Search for seatext or look for the data- attribute on product pages.

If every step passes and the script still does not run, the problem may be inside the theme itself. Try a different browser, then a different device. If the issue persists, contact SeaText support with a screenshot of your theme file and the browser console errors.

Step-by-Step Fix Guide

This is the exact repair path. It overlaps with the diagnostic sequence only where an action is required.

1. Log in to Shopify and go to Online Store → Themes.
2. Locate the theme you want to use. Click the three-dot menu and choose Edit code.
3. In the left pane, open the Layout folder and select theme.liquid.
4. Open your SeaText account and copy the JavaScript snippet from the integration section.
5. Scroll to the bottom of the <head> area in theme.liquid and paste the snippet just before </head>.
6. Click Save. Do not close the editor before saving.
7. Open a product page and inspect the HTML. Look for the SeaText script tag or the data- attribute. If neither appears, repeat the diagnostic steps.
8. If your product description is not marked, locate the product template (often called product.liquid or product-template.liquid) and follow SeaText instructions for wrapping the product description. Then save and test again.

Do not add the snippet to a section file unless you are sure that section appears on every page. The layout file is the only file that guarantees global coverage.

What to Do After Installation

Successfully saving the script is only the beginning. Follow these checks to make sure SeaText is live and ready.

Verify on multiple pages

Visit the homepage, a product page, a collection page, and a blog post. The script should appear on every page if it is in theme.liquid. If it only appears on some pages, the theme may use different layouts for different page types.

Clear all caches

Clear the browser cache, purge your Shopify CDN cache, and clear any third-party caching plugin. Then test again in an incognito window. This removes old copies of the page that might hide the new script.

Check product templates

SeaText can optimize product descriptions when the product template contains the correct data- attribute. Open the product template and verify that the description output is wrapped correctly. Save the file, then visit a product page and inspect the HTML source. The data- attribute must be present.

Confirm data- attributes

Right-click a product description and select Inspect. Look for an attribute that starts with data- and contains a SeaText identifier. If the attribute is missing, customers still see content, but SeaText cannot reliably know which text to optimize.

Activate your agents

Remember, the script stays inert until activated. Log in to your SeaText account and activate the agents you need. Without activation, the script loads but does not rewrite content or protect against bots.

After changing themes

Every Shopify theme has its own theme.liquid. When you switch themes, the new theme does not inherit your old theme code. You must paste the SeaText snippet into the new theme and save it. You also need to re-add any product template tags.

Key Facts at a Glance

Follow-Up Questions

What if the script loads on the homepage but not on product pages?

This usually means the product page uses a different layout or template. Check whether the product page uses the same theme file. Open the product template and confirm the SeaText snippet is in the layout, not in a homepage-specific section. Then clear the cache and inspect again.

Does SeaText work with password-protected stores?

SeaText requires a real public domain. A password-protected store may block SeaText from reading the page. Use a publicly accessible test page when you verify the install. If you must test on a protected store, check with SeaText support for a workaround.

How do I remove the script safely?

Open theme.liquid, delete the SeaText JavaScript block, and click Save. If you added a data- attribute to the product template, remove that too. Clear your caches so old versions of the script do not keep running. Deactivating agents inside SeaText also stops the AI from making changes.

Why does the install button show a shop is currently unavailable page?

That error usually means the SeaText server could not reach your store. The most common causes are a blocked domain, a network issue, or a store that is not publicly accessible. Confirm your domain is live, then retry the installation.

Can I use the same SeaText account on two stores?

No. Each SeaText account is linked to one primary URL. For a second store, create a separate account. This keeps traffic and settings separated for each domain.

If you still cannot install the script, contact SeaText support. Include the full error message and a screenshot of your theme.liquid so they can identify the exact issue.

Separate accounts provide clear data separation, independent billing, and avoid cross-domain analytics mixing, but they require more management. If you run more than one website, you need to decide how to structure your SeaText setup. The tradeoff table below shows the main differences at a glance.

Choose separate accounts if you need clean data per domain, client billing, or security isolation. There is no single-account option for multiple domains. SeaText forces separate accounts to protect your data and keep analytics honest.

Why SeaText requires one account per domain

SeaText links each account to a single primary URL. This is a core design choice, not a limitation you can bypass. When you install the SeaText script on a website, all data from that URL is associated with that account. The system needs to know which domain generated which action. If the same script were used across multiple domains, the system could not reliably attribute events. The result would be messy data, inaccurate reporting, and potential security gaps.

SeaText's own integration instructions are clear: if you need to use SeaText on multiple domains, you must create separate accounts for each domain. This applies to production sites, staging sites, client sites, and any other website you run. The rule exists to keep data trustworthy.

What counts as a separate domain

A primary URL is the main domain or subdomain where you install SeaText. The account is locked to that URL. Different top-level domains, such as example.com and example.org, are clearly separate. Subdomains are also treated as separate domains in most cases. That means blog.example.com and shop.example.com each need their own account if you want to track them separately. The same logic applies to staging and development domains. A staging site at staging.example.com is not the same primary URL as example.com. You should plan for one account per distinct URL.

Development URLs such as localhost are restricted for security reasons. Dynamic development domains may also fail to work properly because SeaText might not be able to reliably associate traffic with your account. Use a valid, real domain for any environment you want to connect to SeaText.

Benefits of separate accounts in practice

Separate accounts create clear boundaries. Each domain's visitor data, conversion metrics, and agent behavior stay in its own workspace. This makes it easier to trust what the data says.

Clean data per domain

When you run separate accounts, each domain's conversion data, traffic sources, and agent performance are isolated. You can see exactly how one agent performs on your ecommerce site versus your blog. No cross-contamination. This matters for SeaText's AI agents because they make decisions based on domain-specific data. The CRO optimizer learns from visitors on one site. The translation agent works on one site's content. If all data were mixed, the agents could receive confusing signals.

Independent billing

Each SeaText account has its own billing. If you manage multiple client sites, you can give each client their own invoice. You can also track costs per site without building custom spreadsheets. For internal teams, separate accounts let you budget per project. Independent billing is one of the easiest ways to answer the question: how much does this website cost?

Security isolation

Separate accounts limit the blast radius of a security problem. If one account's credentials are compromised, the attacker cannot access your other domains. This is especially important when a development site has weaker security or when many team members share logins. A breach in a staging account should not put your production site at risk.

Accurate analytics

SeaText's agents rely on domain-specific data to make decisions. Accurate analytics matter because the agents adapt headlines, offers, product blocks, and calls to action. If data from two domains were mixed, the agent might optimize for the wrong audience. Separate accounts keep conversion reporting clean. You know which page, keyword, and version drove the result.

When separate accounts add overhead

The main downside is management effort. You need to log into each account individually. You also need to activate agents per domain and monitor separate dashboards. For many domains, that can become time-consuming. The setup is quick, though. Installation takes under one minute per domain. You copy one JavaScript snippet and paste it into the theme files. For Shopify, you edit theme.liquid and save the change. The repetitive work is small, but daily management can add up.

Another source of overhead is agent configuration. Each account needs separate activation of the agents you want. You might also need to set different goals for each site. That is not difficult, but it is more work than a single dashboard would be. If you only have one domain, none of this overhead applies. One account is all you need.

Decision criteria: when separate accounts fit best

Separate accounts are mandatory for multiple domains. That is the main decision criterion. If you have more than one primary URL, you do not really have a choice. But within that rule, separate accounts fit some situations better than others. Use them when you need per-client reporting, especially if you run an agency. Use them when you need to keep staging and production separate. Use them when different domains have different goals, audiences, or compliance requirements.

Separate accounts also make sense when one site is experimental. A dev site may get unusual traffic. You may run tests that should not affect production data. Keeping that environment in its own account protects the production dataset.

The main limitation is visibility. SeaText does not currently offer a multi-account dashboard. You log into each account separately. If you need a unified view across many client sites, you may need to build your own reporting layer or use separate exports. Check with the vendor about any future multi-account features.

Key facts about SeaText accounts and domains

Limitations and when the advice doesn't apply

If you have only one domain, you do not need separate accounts. One account gives you all the data you need. The advice about separate accounts applies only when you have multiple domains.

Another exception: if you have a single domain but want to separate data by campaign or language, separate accounts won't help. SeaText accounts are tied to a primary URL, not to campaigns. Instead, you would need to use segmentation features within a single account. Check with the vendor for details on available segmentation options.

Subdomains can be a gray area. In many setups, each subdomain is treated as a separate domain. Before you install on blog.example.com and example.com, verify how SeaText handles that pair. The safest approach is to use separate accounts for separate primary URLs.

Account linking is not available. You cannot merge accounts or link them to share data. If you create the wrong structure at the start, the fix is usually to create a new account. That makes early planning important.

How to set up separate accounts without friction

Start by listing every domain you need to track. Include production, staging, client, and test sites. Then create one SeaText account for each. Use a clear naming convention so you can tell accounts apart. For example, use the domain name in the account profile.

Keep credentials organized in a password manager. If you manage client accounts, use separate email addresses or aliases where needed. After creating the accounts, install the script on each domain. Give each account its own installation snippet. Do not copy the same snippet to multiple sites. If you do, SeaText cannot reliably associate data with the correct account.

Activate only the agents you need in each account. A staging site may not need the same agents as production. This keeps costs down and reduces noise in the data.

Frequently asked questions

Can I use the same SeaText account for a staging site and production site?

No. SeaText requires separate accounts for each domain, including staging and production. Use a separate account for your staging domain and another for your live site.

What happens if I try to install the same script on a second domain?

The script will not work correctly. SeaText's account is linked to a single primary URL, so data from the second domain won't be tracked or attributed to your account. You must create a new account.

Is there a way to manage multiple accounts from one dashboard?

Currently, SeaText does not offer a multi-account dashboard. You log into each account separately. However, the process is straightforward and each account's dashboard is clear.

Do separate accounts cost more?

Yes, each account has its own billing. You pay for each domain separately. This can increase total cost, but it also gives you granular cost tracking per site.

Can I change the primary URL of an existing account?

Check with SeaText support. Typically, the primary URL is set at account creation and cannot be changed. It is easier to create a new account for a new domain.

What about subdomains like app.example.com?

Subdomains are treated as separate domains in most cases. If you want to track app.example.com separately from www.example.com, you need separate accounts.