You add the SeaText snippet by going to Online Store > Themes > Edit Code, opening theme.liquid, pasting the JavaScript before </head>, and saving. The whole process usually takes under one minute. You do not need to be a developer to do it. You only need access to your Shopify admin and the code from your SeaText account.

What is the SeaText snippet?

The SeaText snippet is a small piece of JavaScript that connects your Shopify store to your SeaText account. Once it is installed, you can activate AI agents that work in real time. These agents can rewrite headlines, offers, and calls to action. They can also detect bot traffic, translate content into 125 languages, and optimize each visitor’s journey.

The snippet is inert until you activate agents from your SeaText account. That means it will not change your store by itself. It only starts working when you choose which agents to turn on.

This matters for two reasons. First, it keeps your store safe during installation. Second, it gives you control over what the AI does on your site.

Prerequisites for adding the snippet

Before you start, check that you have these three things:

• A SeaText AI account. You need an account to get your unique JavaScript code. You can create one at the SeaText Shopify integration page.
• Shopify admin access with theme editing rights. The store owner or a staff member with Edit Code permissions can complete this task.
• A valid, real domain. Development URLs such as localhost are restricted. Each domain also needs its own SeaText account.

If you manage multiple websites, create one SeaText account for each site. A single account is linked to one primary URL. This prevents traffic from being mixed up across domains.

How the Shopify code editor works

Shopify’s built-in code editor is part of your theme settings. It lets you view and edit the files that make up your storefront. You do not need to download anything or use a separate tool.

The editor opens inside your Shopify admin. It shows a list of theme files on the left side. Each file is listed under folders such as Layout, Templates, Sections, Snippets, and Assets.

You can search for files by name. You can also use the folder navigation to find what you need. The editor includes basic text editing features like undo and redo. Once you finish a change, the Save button at the top right preserves your work.

Because the editor is built into Shopify, it is safer than editing code on your own computer. There is no separate upload step. Your changes go live as soon as you save.

What is theme.liquid

Every Shopify theme has a main layout file called theme.liquid. It sits in the Layout folder. This file controls the overall structure of every page on your store.

It contains the HTML skeleton, the <head> section, and the <body> section. It also includes the global header and footer areas. Almost every page on your store loads through this file.

That is why it is the ideal place for the SeaText snippet. When you paste the code before </head>, it loads on every page. The snippet becomes available storewide, not just on one product page or landing page.

Shopify themes, including Online Store 2.0 themes like Dawn, still include theme.liquid. The exact folder and file name may vary slightly, but the Layout folder is the standard location.

Step-by-step: Add the SeaText snippet to theme.liquid

1. Log in to your Shopify admin dashboard.
2. Go to Online Store > Themes.
3. Locate your active theme.
4. Click the three dots (⋯) next to the theme.
5. Select Edit Code.
6. In the left file panel, open the Layout folder.
7. Click theme.liquid.
8. Scroll toward the end of the <head> section.
9. Paste the SeaText JavaScript code just before the closing </head> tag.
10. Click Save.

Do not paste the code after the </head> tag. Position matters. Code placed before the head closes is processed as part of the page header. This is also where the SeaText integration instructions say to insert the snippet.

If you are unsure whether the file is theme.liquid, check the folder. The file should be inside the Layout folder. If your theme uses a different structure, contact your theme developer or check the vendor documentation.

Step-by-step: Wrap product descriptions with the data- attribute (optional)

To let SeaText rewrite product descriptions, you need to add a data- attribute to the HTML element that displays the description. This step is optional but recommended for stores that want dynamic product copy.

1. Stay in the Edit Code page or reopen it from Online Store > Themes.
2. Open the file that renders the product description. This is usually product.liquid or product-template.liquid.
3. Find the output for the product description. It often looks like {{ product.description }}.
4. Wrap it with a div that includes the data-seatext-description attribute.

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

5. Save the file.
6. Preview a product page and open your browser’s developer tools to verify the attribute is present.

This tag tells SeaText where the product description lives on the page. It lets the AI target that content for rewriting. You can repeat the same pattern for other page elements if needed, but the basic setup only requires this one wrapper.

Exact placement and why it matters

The correct placement for the SeaText snippet is before the closing </head> tag. This is not a random choice. Scripts in the head section load early in the page lifecycle.

When the snippet loads in the head, it can observe the page as soon as a visitor arrives. It can then prepare the right experience for that visitor. If the code were placed in the footer, the whole page might render before the snippet becomes active. That would create a slower response and less accurate personalization.

Placement also affects security. Shopify themes expect certain code to live in the head. The SeaText integration steps explicitly instruct you to paste the code there. Following the expected placement reduces the chance of broken layouts or unexpected behavior.

Optional data- attribute details

The data- attribute is a simple HTML attribute that carries extra information. In this case, data-seatext-description marks the product description container.

You can add it manually. You do not need to change the snippet itself. The snippet looks for the attribute on your page and uses it to find the content it should rewrite.

Make sure the attribute is spelled exactly as data-seatext-description. A typo in the attribute name means SeaText may not find the correct element. Use lowercase letters and keep the hyphen between words.

If you want to verify the attribute, save the file and preview the product page. Then use your browser’s developer tools to inspect the HTML. You should see the wrapper and the attribute in the source code.

Troubleshooting the SeaText snippet in Shopify

Most installation problems come from a few common mistakes. Here are the ones to check first.

• Pasting in the wrong file. The snippet must go in theme.liquid, not a CSS or JavaScript asset file.
• Pasting after the closing tag. The code must go before </head>.
• Copying an incomplete code block. Make sure you copy the entire JavaScript code from your SeaText account.
• Using the wrong account. Every domain needs its own SeaText account. If the domain does not match, the snippet may not work.
• Using a development URL. Localhost or dynamic development domains are restricted. Use a valid, real domain.
• Not saving the file. The Save button must be clicked for changes to take effect.

If the snippet still does not work, check the page source in your browser. Right-click the page and select View Page Source. Look for the SeaText code in the head section. If you see it, the snippet is installed. Then check your SeaText account to confirm you have activated the agents you need.

Security and performance considerations

The SeaText snippet is designed to be safe for your store. It remains inert until you activate agents from your SeaText account. This means that merely installing the code will not change your content or tracking setup.

The snippet is also lightweight. It loads asynchronously, which helps avoid delays in page rendering. Under normal conditions, it should not noticeably slow down your store.

Real-time AI features may add some work to the server side, but the visitor experience is designed to stay smooth. If you are concerned about performance, test the store after each agent activation. Watch your page speed metrics and adjust your agents if needed.

Security best practices still apply. Only paste code from sources you trust. Keep your SeaText account credentials private. If you remove an agent, the snippet may remain harmless, but you can always delete the code from theme.liquid when you no longer need it.

Limitations and restrictions

• One domain per account. You cannot use the same SeaText snippet on multiple domains. Create a separate account for each website.
• No localhost. Development URLs are restricted for security reasons. Use a staging domain that is publicly accessible.
• Dynamic development domains may fail. Services like Ngrok may not work because SeaText may not be able to associate traffic with your account reliably.
• Theme compatibility. The snippet works with all standard Shopify themes. If your theme heavily customizes the Layout or product template, you may need to adjust where you place the code.
• Activation required. The snippet alone does not change your content. You must activate specific agents for SeaText to rewrite, translate, or analyze your pages.

Frequently asked questions

Do I need coding experience to add the snippet?

No. You only need to copy and paste one block of JavaScript. The Shopify code editor makes the rest simple.

Will the snippet slow down my store?

No. The snippet is lightweight and loads asynchronously. It should not affect page speed in a noticeable way.

Can I add the snippet to a theme that is not my active theme?

Yes. You can add it to any theme, but SeaText will only work on the theme that is currently published.

What if I need to remove the snippet?

Go back to Edit Code, open theme.liquid, delete the pasted JavaScript, and save. The store will no longer load the snippet.

Does SeaText work with Online Store 2.0 themes?

Yes. The snippet is placed in theme.liquid, which is present in all themes, including Dawn and other Online Store 2.0 themes.

What happens after I save the file?

The snippet is live on your store. Then go to your SeaText account, find the agents you want, and activate them. The AI starts working from that point.

Take the next step

Installing the snippet is the foundation. After that, the real work is choosing the right agents for your goals.

If you already have your SeaText code, open Online Store > Themes > Edit Code and paste it into theme.liquid before </head>; then activate your agents from your SeaText account.

The best way to install SeaText on WP Engine without errors is to create a SeaText account, download the WP Engine-specific custom JavaScript plugin from the SeaText General Integration page, install and activate it through the WP Engine dashboard, paste your unique JavaScript snippet site-wide, clear all WP Engine caches, and verify activation by visiting your pages for 40 seconds.

Prerequisites before you start

You need a SeaText AI account before any code touches your site. Each account links to a single primary URL, so if you run a staging domain and a production domain you will need two separate accounts. Development URLs such as localhost are restricted for security reasons and will not work reliably. Make sure you have a valid, public domain ready for each environment.

WP Engine does not allow arbitrary script injection through its standard dashboard. You must use the dedicated WP Engine plugin that adds a custom JavaScript field to every page. Without that plugin the SeaText snippet will never load.

Step-by-step installation process

1. Create your SeaText account. Go to the SeaText signup page and register. You will receive a unique JavaScript snippet tied to that account.
2. Download the WP Engine custom JavaScript plugin. SeaText provides a plugin built for WP Engine that creates a site-wide JavaScript injection point. Download the plugin zip from the SeaText General Integration page.
3. Upload and activate the plugin on WP Engine. In your WP Engine WordPress admin, go to Plugins → Add New → Upload Plugin, choose the zip, install, and activate. Do not use FTP or Git for this plugin; the WP Engine dashboard upload ensures correct file permissions.
4. Paste the SeaText JavaScript code. After activation, a new settings area appears (usually under Settings → SeaText or a similarly named menu). Copy the full JavaScript snippet from your SeaText account and paste it into the custom JavaScript field. Save changes.
5. Apply the snippet across all pages. The plugin includes an option to apply the code site-wide. Enable it so every page loads the script, not just the homepage.
6. Clear WP Engine caches. WP Engine caches aggressively. Use the WP Engine dashboard or the WordPress admin toolbar to purge all caches (page cache, object cache, CDN cache). This step is critical; without it the new script will not appear on the front end.

WP Engine specific configuration details

SeaText instructs WP Engine users to download the WP Engine plugin that enables custom JavaScript, install it, and apply it across all pages.

If you manage multiple environments (staging, production) on the same WP Engine account, repeat the plugin installation and snippet paste for each environment. Each environment needs its own SeaText account because the account-to-domain binding is one-to-one.

Verification and activation steps

1. Visit your live site. Open several pages in a browser. Stay on each page for at least 40 seconds. This dwell time triggers the SeaText AI to activate and associate the traffic with your account.
2. Wait for the dashboard connection. Return to your SeaText dashboard. After at least five minutes you should see your website name appear next to the SeaText logo at the top of the page. This confirms the script is loading and communicating.
3. If the name does not appear after 10 minutes, contact SeaText support. The General Integration page explicitly states: "If you do not see it at the top of the page after 10 minutes, please contact our support team immediately. This could indicate an issue during the installation on your platform, and you may need our assistance."
4. Activate the AI agents you need. Once connected, go to the Main AI Hub in your SeaText account. Click "Configuration" to adjust parameters, then enable agents such as the CRO Optimizer, Translation Agent, or Google Ads Landing Page Agent depending on your goals.

Common issues and how to fix them

• Script not loading after cache clear. Confirm the WP Engine plugin is active and the JavaScript field contains the exact snippet (no extra whitespace, no missing closing tags). Use browser dev tools → Network tab to verify the script request returns 200.
• "Website name" never appears in dashboard. Double-check that the domain in your SeaText account matches the live domain exactly (including www vs non-www). Mismatched domains break the handshake.
• Staging domain shows production data. This happens when the same SeaText account is used for two domains. Create a second SeaText account for the staging domain and install its unique snippet on the staging WP Engine environment.

Multi-domain and development environment considerations

SeaText enforces a strict one-account-per-domain rule. "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." Dynamic development domains (e.g., pr-123.myapp.com) may not function properly because SeaText cannot reliably associate traffic with your account. Use a stable, real domain for any environment where you need SeaText active.

Localhost and similar loopback addresses are restricted for security reasons. Do not attempt to test SeaText on localhost or 127.0.0.1; the script will not activate.

Key facts

Limitations

• SeaText does not support installation via FTP, Git, or standard WordPress header/footer plugins on WP Engine. The dedicated WP Engine plugin is mandatory.
• Each domain requires a separate paid or trial SeaText account; there is no multi-site license from a single account.
• Dynamic preview URLs (common in CI/CD pipelines) will not reliably connect to SeaText.
• The 40-second dwell requirement means automated health checks or crawlers will not activate the AI; real browser visits are needed.
• If the dashboard connection fails after 10 minutes, the only supported path is SeaText support — there is no self-serve debug endpoint documented.

FAQ

Can I use the free WordPress.org SeaText plugin on WP Engine instead?

The WordPress.org plugin "SEATEXT FREE Translation and Conversion Rate Boost" exists, but WP Engine's security layer blocks its script injection method. The SeaText documentation explicitly instructs WP Engine users to download and use the WP Engine-specific plugin that adds a custom JavaScript field. Use the WP Engine plugin, not the standard WordPress plugin.

Do I need to clear cache every time I update the SeaText snippet?

Yes. WP Engine caches the rendered HTML including the injected script. Any change to the JavaScript snippet in the plugin settings requires a full cache purge (page cache, object cache, CDN) before the new version serves to visitors.

What happens if I use the same SeaText account on staging and production?

Traffic from both domains will be attributed to one account, mixing analytics and causing the AI to optimize for a blended audience. The SeaText system expects one primary URL per account. Create a second account for staging.

How long does the initial activation take?

After pasting the snippet and clearing caches, visit your site and stay 40 seconds. The dashboard typically shows the connected site after at least 5 minutes. If it takes longer than 10 minutes, contact SeaText support — this is the escalation threshold SeaText publishes.

Can I install SeaText on a WP Engine multisite network?

Each subsite in a multisite network is a distinct domain (or subdomain). You need a separate SeaText account and a separate plugin configuration for each subsite. The WP Engine plugin settings are per-site, so configure the snippet individually on each subsite's admin.

What PHP version does the SeaText WP Engine plugin require?

The plugin works with current WP Engine-supported PHP configurations. Check with WP Engine for specific PHP version details.

Where do I find the JavaScript snippet after creating my account?

Log into your SeaText account. The General Integration page displays the snippet in a clearly marked section. Copy the entire block exactly as shown, including the opening and closing script tags.

SeaText installation on WP Engine fails most often because WP Engine does not allow direct script injection through theme files or standard WordPress plugin headers. The platform requires you to install a dedicated WP Engine plugin that adds a custom JavaScript field, then paste the SeaText code there and apply it site-wide. If you skip that plugin, the script never reaches the page. Other common causes include PHP version mismatches, missing cURL or mbstring extensions, low PHP memory limits, WP Engine's disallowed-plugins list, and aggressive server-side caching that serves stale pages without the new script.

WP Engine Requires a Custom JavaScript Plugin

According to SeaText's official integration guide, if you are using WP Engine you must download the WP Engine plugin that enables you to add custom JavaScript code to your pages. Install it and apply it across all your pages. Without this plugin, the SeaText snippet cannot be injected into the page output, so the AI never activates. This is the only supported method for adding custom JavaScript on WP Engine.

Missing or Incompatible PHP Extensions

If you see a fatal error on plugin activation such as Call to undefined function curl_init() or mb_strlen() errors, check whether the PHP cURL and mbstring extensions are enabled. SeaText's backend communication relies on these extensions. WP Engine's default PHP builds usually include them, but custom PHP versions or legacy stacks may not. Upgrade to a supported PHP version (8.1 or newer) and enable the required extensions in the WP Engine dashboard.

File Permission and Write Restrictions

If the SeaText WordPress plugin attempts to write a configuration file on first run and fails silently or logs permission errors, the wp-content directory may be mounted as read-only on production environments. Any plugin that tries to write files there — including SeaText if it caches variants locally — will fail. The workaround is to use the custom JavaScript plugin method instead of the WordPress plugin, or to stage the plugin on a writable environment (staging or local) and deploy via Git push.

Server-Side Caching Serves Stale Pages

WP Engine's caching layer caches full HTML responses. After you add the SeaText snippet via the custom JavaScript plugin, the cache must be purged before visitors see the script. If you forget to clear cache, the old HTML continues to serve without the SeaText code. The SeaText activation check (visit the page, wait 40 seconds, refresh several times) will fail because the script is not in the cached HTML. Always purge the WP Engine cache from the dashboard or via the WP Engine plugin after adding the snippet.

Disallowed Plugins List

WP Engine maintains a list of disallowed plugins that are automatically removed on deploy. If you install the SeaText WordPress plugin directly, it may be on that list because it injects scripts or modifies headers in ways WP Engine considers risky. The platform will delete it on the next Git push or environment sync. The supported path is the custom JavaScript plugin, not the SeaText WordPress plugin. Check the WP Engine disallowed plugins list before attempting any plugin install.

Domain and Account Mismatch

SeaText ties each account to a single primary domain. If you install the snippet on a development domain (e.g., staging.example.com) but the SeaText account is registered to example.com, the activation handshake fails. The SeaText dashboard will not show the site name after 10 minutes. You must create a separate SeaText account for each domain, including staging and local environments. Localhost and dynamic preview URLs are explicitly restricted for security.

Activation Handshake Not Completed

Even with the snippet in place, SeaText requires a live visit to complete the handshake. You must visit the page, stay at least 40 seconds, and refresh several times. The SeaText dashboard then shows the site name next to the logo within 5 minutes. If you only test with curl or headless tools, the handshake never fires. This step is mandatory and cannot be automated via cron or API.

Key Facts

Limitations and When This Advice Does Not Apply

This guidance covers the standard SeaText JavaScript integration on WP Engine's managed WordPress plans. It does not apply to:

• WP Engine headless or static-site deployments where the PHP layer is bypassed.
• Custom Docker or VPS setups that mimic WP Engine but lack the same caching or plugin enforcement.
• SeaText's server-side API integrations (rare; most users use the JS snippet).

Terminology

• Custom JavaScript plugin: A WP Engine-provided plugin that adds a textarea for global JS injection.
• Handshake: The first live visit that registers the domain with the SeaText account.
• Disallowed plugins: Plugins WP Engine automatically removes on deploy for performance or security reasons.

FAQ

Why does the SeaText dashboard not show my site after 10 minutes?

The handshake visit likely didn't meet the 40-second dwell requirement, or the script is not in the served HTML due to cache. Purge WP Engine cache, visit the live page, stay 40 seconds, refresh twice, then wait 5 minutes.

Can I use the SeaText WordPress plugin on WP Engine?

Not recommended. WP Engine's disallowed-plugins list often removes it on deploy. Use the Custom JavaScript plugin instead.

Do I need a separate SeaText account for staging?

Yes. Each domain (including staging, development, and production) requires its own SeaText account. Localhost and dynamic preview URLs are not supported.

What PHP version does SeaText need on WP Engine?

PHP 8.1 or newer with cURL and mbstring extensions enabled. Configure this in the WP Engine dashboard under PHP settings.

How do I purge WP Engine cache after adding the snippet?

In the WP Engine user portal, go to your environment → Caches → Clear all caches. Or use the WP Engine plugin in wp-admin → Purge Cache.

What if I see a PHP fatal error about curl_init()?

Your PHP build lacks the cURL extension. Enable it in the WP Engine PHP configuration or upgrade to a supported PHP version.

Can I automate the 40-second handshake with a cron job?

No. SeaText requires a real browser visit with JavaScript execution. Headless tools and server-side requests do not trigger the handshake.

Use Seatext to analyze and optimize your Shopify store’s meta tags, headings, and product copy. The process takes under five minutes and requires only a few edits in your theme files.

What is Seatext SEO integration?

Seatext reads product content and SEO metadata directly from your Shopify pages using a JavaScript snippet and a special HTML attribute. The AI agent scans the content wrapped in the data-seatext attribute. It then suggests or automatically applies improved titles, meta descriptions, headings, and product descriptions. This helps your pages rank higher in search results because the AI ensures keywords are included, tags are properly structured, and copy is clear and compelling.

Seatext does not change any content unless you enable automatic rewriting. The AI remains inert until activated. It can only read and modify content that is wrapped with the data-seatext attribute. The AI cannot change theme layout, images, URLs, or other non-text elements. It focuses on the parts of the page that affect search engine visibility: meta tags, headings, and product copy.

For Shopify stores, optimized meta tags and headings are critical for search visibility. Google reads these elements to understand what your page is about. Seatext helps you create better tags and headings without manual work. The AI also improves product descriptions, making them more likely to appear in search results for relevant queries.

Key Facts

These facts come directly from the Seatext integration documentation. Each account is linked to a single primary URL. You cannot use the same account for a development store and a live store. Development URLs like localhost are blocked for security reasons. Dynamic development domains may not function correctly.

Prerequisites

• Shopify admin access with permission to edit theme code. You need to be able to modify theme.liquid and product template files.
• Active Seatext AI account. Create one if you do not have it yet. The integration is free, but you need a paid plan to use the AI SEO features.
• A live, publicly reachable domain. Localhost or internal development URLs will not work. Use a real domain that is accessible over the internet.
• Knowledge of which theme is currently active. Editing an inactive theme will not affect your live store.

Step‑by‑Step Integration

1. Copy the Seatext script. Log into your Seatext AI dashboard. Navigate to the integration section. You will see a JavaScript code snippet. Click the copy button or select the code manually. The script is unique to your account.
2. Paste into theme.liquid. In Shopify admin, go to Online Store → Themes → Actions → Edit code. Open the Layout/theme.liquid file. Scroll to the bottom of the <head> section. Paste the script just before the closing </head> tag. Click the Save button. This step ensures the script loads on every page of your store.
3. Identify the product template. In the same Edit code page, look in the Templates folder. Find the file that renders your product page. It is usually named product.liquid or product-template.liquid. If you use a custom theme, the file name may differ. Open that file.
4. Wrap the description. Search for the line that outputs the product description. It often looks like {{ product.description }} or {{ product.content }}. Wrap this line with a div that has the data-seatext attribute. For example: <div data-seatext="true">{{ product.description }}</div>. Save the file. This attribute tells the Seatext AI which content to read and optimize.
5. Test the changes. Preview a product page on your store. Open your browser’s developer tools (F12 or right-click → Inspect). Go to the Elements tab. Search for the string data-seatext. If you see the attribute in the HTML, the integration is working. Then go to your Seatext dashboard. It should show the store as “connected”. If not, refresh the page and wait a few seconds.

Common Mistake to Avoid

Editing the wrong theme is the most common mistake. Shopify stores often have multiple themes. Only the active theme (marked as “Published” in the theme selector) serves pages to visitors. If you edit a duplicate or unpublished theme, the script never runs on your live store. Always confirm you are editing the active theme.

Another mistake is placing the script in the wrong location. It must be inside the <head> tag, not in the footer or body. If you place it elsewhere, the AI may not load correctly.

Forgetting to add the data-seatext attribute is also common. Without it, the AI cannot read the product description. The dashboard will show the store as connected, but no optimization will occur.

Verification Checklist

• JavaScript snippet is present in theme.liquid and saved.
• Product description markup includes the data-seatext attribute.
• Page source shows the attribute when inspected in browser dev tools.
• Seatext dashboard reports the store as “connected”.
• AI suggestions appear in the dashboard for the product pages you have tagged.

Limitations

Each Seatext account works with a single primary URL. You need separate accounts for development and production domains. This is a security measure to prevent cross-domain data leaks.

Development URLs like localhost are not supported. The AI cannot read content from non-public domains. If you use a dynamic development domain (e.g., a temporary URL from a service like ngrok), it may not work reliably. Use a real, public domain for testing.

If you place the snippet in an inactive theme, the integration will not work. The script must be in the theme that is currently published. Switching to a different theme will break the integration unless you also add the snippet to the new theme.

The AI only reads content that is wrapped in the data-seatext attribute. Other content on the page is ignored. This is intentional to give you control over what the AI optimizes.

Glossary

• JavaScript snippet: Small piece of code provided by Seatext that enables the AI to read page content. It is unique to your account and must be placed in the <head> of your theme.
• data-seatext attribute: HTML attribute that marks product description blocks for Seatext processing. It should be added to a div or other container around the product description.
• Theme.liquid: The main layout file in a Shopify theme where global scripts are placed. It contains the <head> and <body> tags.
• Active theme: The theme that is currently published and serving your store’s pages. Only changes to the active theme affect the live site.
• Product template: The file that controls how product pages are displayed. It typically contains the product description output.

FAQ

Do I need to know code to integrate Seatext?

No. You only paste a snippet and add a single attribute to the product template. The steps are simple and do not require programming skills.

Can I use Seatext on a development store?

Development URLs like localhost are blocked for security. Create a separate account for a public test domain. Do not use localhost.

Will Seatext affect my existing SEO settings?

Seatext reads current meta tags and can suggest improvements without overwriting them unless you enable automatic rewriting. You have full control over what changes are applied.

How do I know the integration works?

Check the page source for the data-seatext attribute and see the “connected” status in your Seatext dashboard. Also, look for AI suggestions in the dashboard.

Is there an extra cost for the Shopify integration?

The integration itself is free. You need a paid Seatext plan to unlock AI SEO features. The plan includes the ability to use the AI agents for optimization.

How long does the integration take?

Most users complete the process in under five minutes. The hardest part is copying and pasting the code into the correct files.

Can I use the same Seatext account on multiple stores?

No. Each account is linked to a single primary domain. You need separate accounts for each store or domain.

What if I have multiple product templates?

You must add the data-seatext attribute to each product template file that outputs descriptions. Otherwise, some products will not be optimized.

Does Seatext work with Shopify’s Online Store 2.0?

Yes, as long as you can edit the theme files and add the attribute to the product description section. The integration works with both classic and Online Store 2.0 themes.

How do I remove the integration?

Simply delete the JavaScript snippet from theme.liquid and remove the data-seatext attribute from the product templates. The AI will stop reading your pages.

To activate Seatext on your Wix site, you need to trigger the connection by loading your site in a browser, refreshing it several times, and staying on the page for at least 40 seconds. After that, wait up to five minutes for your website name to appear next to the SEATEXT logo in the dashboard. That confirms the script is live and linked to your Seatext account.

Before you start: two requirements

You need a Seatext account and a paid Wix plan. Wix only lets you add custom code on paid plans, not on the free plan. Also, each Seatext account is linked to a single primary URL. If you want to use Seatext on another domain, create a separate account for that domain.

Step-by-step: refresh your Wix site to activate Seatext

1. Log in to Seatext and copy the JavaScript snippet from the integration page.
2. In Wix, go to the admin area and open Settings.
3. Scroll down to Custom Code under Advanced.
4. Click Add Code in the Head section.
5. Paste the copied Seatext JavaScript into the “Paste the code snippet here” box.
6. Under “Add Code to Pages”, choose All pages.
7. Select Load code on each new page and click Apply.
8. Open your Wix site in a browser. Refresh it several times and stay on the page for at least 40 seconds.
9. Go back to your Seatext dashboard and wait for your website name to appear next to the SEATEXT logo.

This sequence matters. If you skip the refresh step or leave after a few seconds, the script may not link to your account.

Activation checklist

• Seatext account created and code copied.
• Paid Wix plan active.
• Code pasted under Head and set to All pages.
• Each new page loads the code.
• Site visited and refreshed several times.
• At least 40 seconds spent on the page.
• Website name visible in Seatext dashboard within 5 minutes.

Why the refresh step exists: technical mechanics

The Seatext script stays inert until it detects a real visit from a valid domain. When you load and refresh the page, that visit links to your Seatext account. The 40-second dwell time gives the script enough time to register the session and connect the URL to your account. This design prevents accidental activations from bots or preview modes. The script checks that the domain matches the primary URL registered to your Seatext account. Only a genuine browser visit with proper dwell time satisfies this check.

You don't need to update anything else in Wix. The refresh is just the activation trigger, not a content update. Once the connection shows in the dashboard, the script is ready for the next step. Keep the page open in your browser for at least 40 seconds before you refresh again. The exact number of refreshes isn't fixed; the goal is to create a valid session that matches your account's primary URL.

What “refresh” means in this context

In Wix, refreshing usually means updating your site's content. In this case, “refresh” means reloading your live site in a web browser. You can press F5 or click the reload icon while the site is open. This tells the Seatext script that a real visitor is on the page. Do not confuse this with Wix's “refresh” button in the editor. The activation requires the published, live URL that matches your Seatext account's primary domain.

How to verify activation in the dashboard

After the refresh, wait at least five minutes. The dashboard should show your website name at the top of the page next to the SEATEXT logo. If that name doesn't appear after 10 minutes, contact Seatext support immediately. This usually means the script was not installed correctly or the page was not visited with a valid domain. Seatext needs time to match the visit to your account. The dashboard name doesn't update instantly. Planning for a five-minute wait avoids checking too early and thinking something is broken. If 10 minutes pass with no name, support can check whether the script actually loaded on your domain.

Key facts: Seatext + Wix activation

Multiple domains and separate accounts

Seatext links each account to one primary URL. If you use a development domain and a production domain, create two Seatext accounts. Otherwise the script may not associate traffic with the right account. This is not a Wix limitation; it's how Seatext matches visits to a single site. For agencies managing client sites, each client domain needs its own Seatext account. You cannot use one account across multiple domains even if you own them all.

Limitations and edge cases

• Localhost addresses are blocked for security. Use a real domain.
• Dynamic development domains may not work because Seatext can't reliably match traffic to your account.
• If you have separate domains (for example, development and production), create a separate Seatext account for each.
• The code must be set to load on each new page; otherwise some pages may not activate.
• Activation requires a real visit. Refreshing and leaving immediately won't link the site.
• Wix free plan does not support custom code, so Seatext cannot be installed there.
• If you change your primary domain in Wix, you must update the Seatext account or create a new one.

Practical scenarios: when to use which approach

Single production site

Create one Seatext account for your live domain. Install the script once. Activate with the refresh process. Then configure agents in the Main AI Hub.

Development and production environments

Create two Seatext accounts: one for the dev domain, one for production. Install the script in each Wix project. Activate each separately. This keeps analytics and AI training data separate.

Agency managing multiple clients

Each client gets their own Seatext account tied to their domain. You can manage them from one login if Seatext supports team access; check with the vendor for current team features.

Temporary staging domains

If you use a temporary Wix staging URL, it may not activate reliably. Use a real custom domain for testing. Dynamic subdomains from Wix (like username.wixsite.com/sitename) can work but are less reliable than a custom domain.

What happens after activation: next steps in the Main AI Hub

Once your website name is visible, open the Main AI Hub in Seatext. Choose the pages where you want AI to work, then click Configuration to set the parameters. For example, you can turn on the Website Translation agent to translate your site into 125 languages, or enable AI CRO Reading Analysis to study how visitors read your copy. The activation step is done; the next step is choosing and tuning your agents.

Available agents include: AI CRO Reading Analysis, AI Split URL Testing, Google Ads Landing Page AI, AI Copy A/B Testing, Ecommerce Product Copy, AI Personalization, Scroll Slowdown, Website Translation (125 languages), Local AI SEO, AI SEO Content Factory, Free Authority Link Builder, ChatGPT Brand Visibility, Visitor Source Rewrites, Free AI Website Chat, Conversion Relay (CAPI), Intent Amplifier, Shielded Buyers & Ad Firewall, Detect VPN Ad Clicks, Bot Protection, and AI Agent Actions (WebMCP). Each agent has its own configuration panel.

Troubleshooting common activation problems

Website name never appears

Check that the script is in the Head section, set to All pages, and loading on each new page. Verify you used a paid Wix plan. Confirm the domain matches the primary URL in your Seatext account. Wait the full 10 minutes before contacting support.

Script installed but no activation after refresh

Ensure you stayed on the page for 40 seconds total across refreshes. Try a different browser or incognito mode to rule out caching. Make sure you're visiting the exact domain registered in Seatext.

Multiple sites showing in one account

This indicates a configuration error. Each account should show only its primary URL. Create separate accounts for each domain.

Frequently asked questions

Do I need a paid Wix plan to use Seatext?

Yes. Wix only allows custom code on paid plans. The free plan doesn't support adding JavaScript snippets.

Why doesn't my site show as connected after one refresh?

One quick load may not give the script enough time. Refresh several times and stay on the page for at least 40 seconds. Then wait five minutes.

Can I test Seatext on localhost?

No. Localhost is blocked for security reasons. Use a valid real domain.

I have two Wix sites. Do I need two Seatext accounts?

Yes. Each Seatext account is linked to a single primary URL. Create a separate account for each site.

What happens after my site name appears in the dashboard?

You can go to the Main AI Hub to activate the AI agents you need and click Configuration to adjust their parameters.

How long does the activation take from start to finish?

Installation takes about 5 minutes. The refresh and dwell step takes about 1 minute. Dashboard confirmation takes up to 5 minutes. Total: roughly 10-15 minutes.

Can I activate Seatext on a Wix site that uses a custom domain?

Yes. A custom domain is ideal. It matches the primary URL requirement and works reliably.

What if I change my Wix site's domain later?

You'll need to update the primary URL in your Seatext account settings or create a new account for the new domain. Check with the vendor for the exact process.

Security and privacy considerations

The Seatext script remains inert until activation. This means no data is collected or processed before you complete the refresh step. The script only begins analyzing visitor behavior and serving AI-driven optimizations after the dashboard shows your site as connected. Localhost and dynamic development domains are blocked to prevent unauthorized use and ensure traffic attribution accuracy. Each account's single-URL design prevents cross-domain data leakage.

Performance impact on your Wix site

The Seatext JavaScript snippet is lightweight and loads asynchronously. It does not block page rendering. Once activated, AI agents run in the browser or via edge workers depending on the agent type. Translation, personalization, and CRO agents operate with minimal latency. The initial activation visit adds no perceptible load time. Ongoing performance depends on which agents you enable; most are designed for zero-flicker operation.

Decision criteria: is Seatext right for your Wix site?

Consider Seatext if you want autonomous AI agents that optimize conversion rates, translate content, personalize copy, or recover ad spend from bot traffic. It fits sites with enough traffic to benefit from automated testing and personalization. If you run Google Ads, the Google Ads Landing Page AI rewrites pages per keyword in real time. If you serve international visitors, the Translation agent covers 125 languages without manual work. If you need to understand how visitors read, the CRO Reading Analysis agent provides telemetry beyond standard analytics. Small sites with very low traffic may not see immediate ROI from testing agents but still benefit from translation and chat.

What this article covers

This article explains what the sources say about Seatext AI pricing for Shopify integration. It also covers why plan and cost choice matters, how the per-account model works, cost drivers, trade-offs, practical Shopify setup steps, limitations, and likely follow-up questions.

Important: the reviewed sources do not publish a price list. Use the official “Click here for pricing” page to see current plans and prices.

Why plan and cost choice matters

Seatext AI is not a passive translation widget. It deploys autonomous agents that rewrite headlines, adapt product copy, translate content, and detect bot traffic. Each agent changes how a store behaves for visitors, so the right plan affects both results and budget.

For Shopify merchants, the main cost questions are usually: how many stores do I run, which agents do I need, and how much manual work am I willing to keep? Answering those questions first makes the pricing page easier to evaluate.

Sources show Seatext AI can rewrite landing pages for paid clicks, translate websites into 125 languages, generate FAQ pages, and create refund reports for invalid ad clicks. A store that needs only translation may spend differently from one that needs conversion optimization, bot protection, and AI chat.

Available AI agents and what they do

The source pack lists more than 20 AI agents. Some of the most relevant ones for Shopify include:

• Ecommerce Product Copy Agent – optimizes product names, descriptions, and CTAs.
• Google Ads Landing Page Agent – rewrites landing pages to match campaign keywords.
• Website Translation Agent – translates pages into 125 languages.
• AI CRO Reading Analysis Agent – analyzes visitor reading and generates copy.
• AI A/B Testing Agent – creates copy variants and scales winners.
• AI Personalization Agent – adapts site copy to visitor context.
• Bot Protection Agent – detects invalid traffic and prepares refund reports.
• Free AI Website Chat Agent – an autonomous sales chat agent.
• Local AI SEO Agent – ranks for “near me” and neighborhood searches.
• AI SEO Content Factory – publishes indexed Q&A pages.
• ChatGPT Brand Visibility Agent – shapes what AI assistants recommend.
• Conversion Relay (CAPI) – forwards purchases to Meta and Google CAPI.
• 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.
• AI Split URL Testing – runs zero-flicker URL split tests.
• Visitor Source Rewrites – matches headlines to referrer campaigns.
• Scroll Slowdown Agent – slows fast scrollers near CTAs.
• AI Agent Actions (WebMCP) – turns a website into an MCP server for Claude and ChatGPT.
• Free Authority Link Builder – finds editorial links across client articles.

These agents explain why plan selection matters. A growth-focused store may want the Google Ads agent and CRO agents. An international store may want translation and local SEO. A store with heavy paid traffic may want bot protection and CAPI agents.

How the per-account pricing model works

According to source S1, each Seatext AI account is linked to a single primary URL. If you need Seatext AI on multiple domains, you must create separate accounts for each domain. This is the clearest pricing-related fact in the source pack.

The per-domain model matters for Shopify merchants because many stores use more than one domain. Examples include a country-specific domain, a checkout subdomain, a development domain, or a separate campaign landing page. Each one may require its own account.

Development URLs such as localhost are restricted for security reasons. The source says dynamic development domains may not function properly because Seatext AI might be unable to reliably associate traffic with your account. Use a valid, real domain for production.

Because each account is tied to one primary URL, the cost of running Seatext AI can grow with the number of live storefronts. That is a key cost driver even when specific prices are not published.

Cost drivers and decision criteria

Plan and cost choice depends on several factors that come directly from the source material.

• Number of domains – one account per primary URL.
• Number of agents – each agent adds a different capability.
• Traffic source – stores with Google Ads may need the landing page agent.
• International audience – translation into 125 languages may be a priority.
• Ad fraud exposure – bot protection and refund reporting may reduce wasted spend.
• Support needs – sources mention support only in general terms; check current plan details.
• Custom integration – larger stores may need custom work that affects cost.

Before opening the pricing page, list the agents you must have and the agents you can do without. If you only need product copy improvements, you may not need the full agent suite. If you run a large paid acquisition program, conversion and bot agents may be more valuable.

Also decide which domains must be live immediately. Since each domain needs its own account, adding a second storefront may change your budget more than adding an agent.

Practical Shopify integration steps

Source S1 provides the official integration flow. These steps are useful when you are ready to test or buy.

1. Create a Seatext AI account. The installation script remains inert until activated, so your website content is not changed before you activate an agent.
2. Copy the JavaScript code from the Seatext AI dashboard section labeled “SEATEXTCODEINTEGRATION”.
3. In Shopify admin, go to Online Store > Themes.
4. Click the three dots next to your active theme and select “Edit code”.
5. Open the Layout folder and locate the theme.liquid file.
6. Paste the JavaScript code snippet before saving.
7. Click Save.

For product descriptions, the source also describes a tag-based method. In Shopify admin, go to Online Store > Themes, click Actions > Edit Code, locate the product template (often product.liquid), wrap the product description output with the required tag, save, and test a product page.

The source says installation takes under one minute. You can verify that the data attribute is present in the HTML source using browser developer tools. For additional technical details, the source points to the Seatext documentation page.

Free demo and pilot trial

Source S5 mentions two useful options for buyers who are not ready to commit:

• A free demo.
• A free 1-month pilot trial for the Google Ads Landing Page Agent.

A demo lets you see how the agents behave before you install code. A one-month pilot is especially useful for a Shopify store because you can measure conversion changes during a real traffic period.

Sources also say Seatext AI is “Trusted by 2,500+ brands” and “proven across 2,500 brands”. These statements are testimonials from the vendor, not independent third-party audits.

The source materials reference performance claims like +35% conversion lift, +25% conversion rate, +60% more international customers, and $1.2M recovered from ad fraud. Treat these as illustrative vendor examples unless you verify them with your own store results.

Limitations of the source pack

The provided sources do not disclose specific plan names, feature tiers, or prices. The homepage and several related pages show a “Click here for pricing” link, but the source pack does not include the pricing page itself.

Because of that, this article does not list Starter, Growth, or Enterprise plans as verified facts. If you see those names on the official pricing page, treat them as vendor-provided details rather than as facts from the source pack.

The source pack also does not state whether discounts exist for multiple domains, annual billing, agencies, or nonprofits. It does not list payment methods, refund policies, or contract lengths. Check with the vendor for these details.

Another limitation is that the source pack does not compare Seatext AI with other Shopify apps. It only explains what Seatext AI itself says about its agents. Independent reviews on sites like GetApp, Capterra, and Software Advice may help, but they are not part of the verified source pack.

Trade-offs to weigh before buying

Every AI agent changes how your storefront appears. That creates trade-offs even when the exact price is unknown.

Automation vs. control – Seatext AI can rewrite product copy and landing pages automatically. Merchants who want complete control may prefer to review changes before publishing. Merchants who want speed may accept automation.

Translation reach vs. manual quality – Machine translation across 125 languages can open new markets quickly. Human-reviewed translation may be better for nuanced brand voice, but it is slower and more expensive.

Multiple domains vs. single store – A single Shopify store needs one account. A multi-domain setup needs multiple accounts, which increases cost and management overhead.

Agent suite vs. targeted use – A full agent suite may create more optimization opportunities, but it also introduces more variables. A targeted setup with one or two agents is easier to measure.

Paid traffic focus vs. organic focus – Stores that depend on Google Ads may prioritize the Google Ads Landing Page Agent. Stores that depend on organic search may prioritize local SEO and content factory agents.

Who each option fits best

Because verified plan names are not available, use agent needs as your main decision guide.

Single-store Shopify merchants – likely need one account and only a few agents, such as ecommerce product copy and translation.

International sellers – likely need translation, local SEO, and personalization agents.

Paid advertising teams – likely need the Google Ads landing page agent, bot protection, CAPI forwarding, and VPN click detection.

Agencies managing multiple clients – need one account per client domain, so the per-account model may be a major budget factor.

Large brands with custom needs – likely need the full agent suite plus custom integration support. The source pack does not explain how Seatext structures such engagements.

Use the official “Click here for pricing” page to see the current plans and prices before making a purchase decision.

Key facts and sources

Plan names and prices are not disclosed in the provided sources. Always confirm current offerings on the official pricing page.

Frequently asked questions

What are the pricing plans for Seatext AI Shopify integration?

The reviewed sources do not publish plan names or prices. The official “Click here for pricing” page is the only reliable place to see current plans.

How is Seatext AI pricing calculated?

The main verified driver is the number of domains, because each primary URL needs its own account. The number of agents you activate and the support or integration level may also affect price, but that is not detailed in the sources.

Do I need a separate account for each Shopify store?

Yes, according to source S1. Each Seatext AI account is linked to a single primary URL, and separate accounts are required for multiple domains.

Can I use Seatext AI on a localhost or development domain?

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

Is there a free trial?

Source S5 mentions a free demo and a free 1-month pilot trial for the Google Ads Landing Page Agent. Other agents may have different trial conditions; check with the vendor.

Which agents are best for a Shopify store?

Common choices include the Ecommerce Product Copy Agent, Website Translation Agent, CRO reading analysis, AI A/B testing, personalization, and the free AI chat agent. Start with the agents that match your main goal.

Does Seatext AI replace my Shopify theme?

No. You add a JavaScript snippet to your theme.liquid file. The AI becomes active only after you activate an agent.

Will the translation agent replace manual localization?

The source says the Website Translation Agent can translate pages into 125 languages without a manual localization project. Quality and brand voice should still be reviewed for important content.

Can I get a refund for bot clicks with Seatext AI?

The Bot Protection Agent detects invalid traffic and builds refund-ready reports for ad platforms such as Google and Meta. Refund approval depends on the ad platform, not on Seatext AI.

Where can I see current prices?

Use the official “Click here for pricing” link on the Seatext AI website. The provided sources do not include the pricing page contents.

Next steps

Before buying, define your store goals and list the agents you need. Count your live domains because each one needs its own account. Use the free demo or the 1-month pilot trial to test the agents on a real domain.

Then visit the official

How SeaText AI Protects Your Shopify Account from Unauthorized Access

If SeaText AI doesn’t activate on Shopify within the expected time, don’t keep waiting—treat it as a setup problem and check three things first: your account’s primary URL matches the store domain, the JavaScript snippet is saved in theme.liquid, and the data- attribute is on the product description template. If all three are correct and you have activated the agents, the issue may be a short redeployment delay or something account‑specific. For long delays, contact SeaText support with your store details and any error messages for personalized assistance.

Why activation timing matters for your store

Activation timing directly affects revenue. SeaText AI rewrites product copy, titles, and CTAs in real time. If the AI stays inert, visitors see the original copy, which may be less persuasive. A delay of even a few minutes can mean missed conversions during high‑traffic events such as flash sales or holiday promotions.

From an SEO perspective, search engines cache the HTML they receive. If the AI never activates, the cached version lacks the optimized copy that could improve click‑through rates from search results. In short, delayed activation reduces the very benefits SeaText promises.

How SeaText activation differs from a standard Shopify app

Most Shopify apps install as native extensions that run on Shopify’s servers. SeaText uses a lightweight JavaScript snippet that runs in the visitor’s browser. The snippet reads the page, looks for a custom data- attribute, and then contacts SeaText’s cloud service to fetch generated copy.

This model has two practical consequences:

• The script is inert until you turn on agents in the SeaText dashboard. Installation alone does not change content.
• Because the script runs client‑side, any theme caching or CDN layer must serve the updated theme.liquid file before the AI can act.

In contrast, a native app can modify Shopify’s Liquid templates directly on the server, eliminating the need for a data‑attribute anchor. However, native apps require app store approval and may add extra load to Shopify’s backend.

Common setup mistakes and how to avoid them

Most activation delays stem from three simple oversights:

1. Primary URL mismatch. Each SeaText account links to a single primary URL. If your store uses example.myshopify.com but the account is set to example.com, the AI will not associate traffic with your store. Verify the URL in the SeaText dashboard.
2. Snippet not saved. After pasting the JavaScript into theme.liquid, you must click “Save”. The integration guide explicitly states this step (Once the code snippet has been successfully pasted, click on the “Save” button to preserve your changes).
3. Missing or malformed data‑ attribute. The attribute must wrap the product description output exactly as shown in the guide. A typo or missing closing tag prevents the script from finding its anchor point.

Double‑check each step with the browser’s developer tools. Look for the script tag near the bottom of the <head> and the data- attribute on the product description element.

Step‑by‑step verification checklist

1. Log in to your SeaText account and confirm the primary URL matches your Shopify domain.
2. In Shopify admin, go to Online Store > Themes > Actions > Edit code. Open Layout > theme.liquid.
3. Locate the SeaText JavaScript snippet. It should start with <script> (function(){...})(). If it is missing, copy it again from the dashboard.
4. Click Save and wait a few seconds for Shopify to propagate the change.
5. Open the product template file (product.liquid or product-template.liquid). Find the line that outputs the description, usually {{ product.description }}.
6. Wrap that line with the exact data- attribute provided by SeaText, e.g., <div data-seatext="product-description">{{ product.description }}</div>.
7. Save the template file.
8. Activate the relevant agents in the SeaText dashboard (e.g., “Ecommerce Product Copy”).
9. Open a product page in an incognito window. Use Ctrl+U to view source. Confirm both the script tag and the data- attribute appear.
10. If the script loads but no copy changes, clear browser cache or disable any ad‑blocker that might block external requests.

When to wait vs. when to contact support

Shopify may need up to two minutes to redeploy a theme change. If you have just saved theme.liquid, wait 2‑3 minutes and refresh the product page.

If after five minutes the script is present but the AI still shows no output, move to the next step:

• Check agent activation. Ensure the agents you need are turned on in the SeaText dashboard.
• Verify primary URL. A mismatch will silently block activation.
• Inspect console errors. Look for network failures to api.seatext.com.

If all checks pass and the problem persists, contact SeaText support. Provide the store domain, a screenshot of the page source, and any console error messages. This information lets support locate the issue quickly.

Preventing future activation issues

Adopt these habits to keep activation smooth:

• Document the exact snippet version you paste. When SeaText releases an updated script, replace it promptly.
• Maintain a single SeaText account per domain. For staging or development stores, create a separate account rather than reusing the production one.
• Avoid using localhost or dynamic development URLs. The integration guide warns that development URLs are restricted for security reasons.
• Include the verification checklist in your onboarding SOP. New team members can run it before launching any new product.

Trade‑offs: script‑based tool vs. native Shopify app

Using a script‑based tool like SeaText offers flexibility. You can add the snippet to any theme without waiting for app store approval. It also keeps the core Shopify platform untouched, reducing the risk of conflicts with other apps.

However, there are trade‑offs:

• Single‑domain limitation. Each SeaText account works with only one primary URL. If you need the AI on multiple stores, you must manage multiple accounts.
• Development URL restrictions. Localhost or temporary subdomains cannot be used. This can slow down testing workflows.
• Client‑side execution. The script runs after the page loads, which can add a fraction of a second to perceived load time. Native apps can modify HTML server‑side, eliminating that delay.
• Dependency on browser environment. Ad blockers or strict CSP headers may block the script, whereas native apps are less likely to be affected.

Choose the script approach if you value quick installation and want to keep your Shopify admin clean. Choose a native app if you need multi‑domain support, tighter security controls, or server‑side rendering.

FAQ

How long should I wait before troubleshooting?

After saving theme.liquid, wait up to three minutes. If the script still does not appear in the page source, start the checklist.

Can I use the same SeaText account on a staging and production Shopify store?

No. Each account is linked to a single primary URL. Create a separate account for each domain, including staging sites.

Why does the AI stay “inert” even after I paste the script?

Installation and activation are separate steps. The integration guide states the AI remains inert until activated. You must turn on the agents you want in the SeaText dashboard.

What if the snippet is in theme.liquid but product descriptions still don’t change?

Check the data- attribute in the product template. Without it, the script has no anchor point to replace the description.

How can I verify the snippet is actually loading in the browser?

Open developer tools, go to the Network tab, and filter for seatext.com. You should see a request to the SeaText CDN when the page loads. If the request is blocked, look for CSP or ad‑blocker warnings.

My theme uses a custom product template name. Will SeaText still work?

Yes, as long as you add the data- attribute around the description output in whatever file renders the product description. The script only looks for the attribute, not the file name.

What should I do if I see console errors about “blocked by CORS”?

Ensure your store’s CSP allows requests to https://api.seatext.com. Add an exception if needed, or disable any security extensions that interfere.

Is there a way to test SeaText on a staging environment without affecting live traffic?

Yes. Create a separate SeaText account for the staging domain, install the snippet there, and activate agents only on that account. Remember that development URLs like localhost are restricted.

Expert perspective: why most activation delays are setup errors

When someone reports that SeaText hasn’t activated on Shopify, the first thing to look for is not server status. It’s the difference between “I added the snippet” and “I saved the snippet and completed the data‑ attribute step.” The integration guide is short, but every step depends on the previous one.

In practice, a saved script with a missing data‑ attribute will load on the page but have no product content to work with. A missing save means the script isn’t there at all, even if the editor still shows it. And a wrong primary URL means the page may load, but SeaText won’t know which account to connect with. These three scenarios need three different fixes, so the fastest path is to check them in the order above.

One more habit helps: test on a real domain. Localhost and dynamically generated development domains are restricted because SeaText needs to reliably associate traffic with your account.

What to do if the checklist doesn’t help

If you have confirmed the account URL, the saved snippet, the data‑ attribute, and active agents, but SeaText still doesn’t activate, don’t keep guessing. Contact SeaText support with your store details, the exact domain, and any error messages. Those details help support find whether the issue is account‑specific or related to something in the store theme.

You should add the SeaText AI JavaScript code to your Shopify theme after you have created your SeaText account and connected your Shopify store, but before you launch any AI features. The installation process is secure and the AI remains inert until activated, so the code can sit in your theme without affecting your site until you enable agents in the dashboard.

Readiness Checklist: Are You Ready to Paste the Code?

• SeaText account created. You have signed up at SeaText and can log in to the dashboard.
• Primary domain confirmed. The account is linked to a valid, real domain (not localhost or a dynamic development URL).
• Shopify store accessible. You have admin access to the Shopify store you want to connect.
• Theme identified. You know which theme you want to edit (usually the live theme).
• Code snippet copied. You have the JavaScript snippet from the SeaText dashboard ready to paste.
• Backup taken. You have duplicated the theme or exported the current theme.liquid file in case you need to roll back.

If every item is checked, you can safely add the code now. If any item is missing, complete that step first.

Why Timing Matters

SeaText's script is designed to stay dormant until you activate agents. According to the integration guide, "the installation process is secure, and the AI remains inert until activated, ensuring the integrity of your website's content." This means the code itself does not change anything on your storefront until you flip a switch in the dashboard. Installing early lets you verify the snippet loads without errors, but it only makes sense after the account and domain are set up because each SeaText account is tied to a single primary URL.

Prerequisites Before Adding the Code

1. Create Your SeaText Account First

The integration documentation states: "Before you can install the script, you need a SEATEXT AI account. If you don't have an account yet, you can create one." Without an account, there is no dashboard to generate the unique JavaScript snippet, and no place to activate agents later.

2. Use a Valid, Real Domain

SeaText restricts development URLs such as localhost and dynamic development domains. The source notes: "Development URLs, such as localhost, are restricted for security reasons. Ensure you use a valid, real domain for these cases. Dynamic development domains may not function properly, as SEATEXT AI might be unable to reliably associate traffic with your account." If you are on a staging store, use a real subdomain (e.g., staging.yourbrand.com) rather than a Shopify myshopify.com address.

3. One Account Per Domain

If you run multiple stores or need SeaText on a development domain and a production domain, you must create separate accounts. The guide says: "If you need to use SEATEXT AI on multiple domains (e.g., a development domain and a production domain), you must create separate accounts for each domain. Each SEATEXT AI account is linked to a single primary URL."

Step-by-Step Readiness Verification

1. Log in to SeaText. Confirm you see the dashboard and the JavaScript snippet under the integration section.
2. Verify your primary domain. In account settings, check that the domain matches the Shopify store's primary domain exactly.
3. Open Shopify admin. Go to Online Store > Themes.
4. Duplicate the live theme. Click Actions > Duplicate on the current live theme. This gives you a safe fallback.
5. Edit code on the duplicate. Click Actions > Edit code on the duplicated theme.
6. Locate theme.liquid. In the left file tree, open the Layout folder and click theme.liquid.
7. Paste the snippet. Place the SeaText JavaScript just before the closing </head> tag.
8. Save. Click Save to preserve changes.
9. Preview. Use the theme preview (eye icon) to confirm the script loads in the <head> without console errors.
10. Publish when ready. Once verified, click Actions > Publish on the duplicated theme to make it live.

Common Mistakes and When to Wait

Exceptions and Special Cases

• Headless Shopify or Hydrogen. If you use a custom storefront, you must inject the snippet into your own <head> on every page render. The Shopify theme editor path does not apply.
• Multiple brands on one Shopify Plus organization. Each brand needs its own SeaText account and snippet, even if they share a theme codebase. Use theme settings or a snippet include to load the correct account's script per store.
• Agency managing client stores. Create the SeaText account under the client's email/domain, not your agency account, so the primary URL matches the client's domain.
• Theme updates. When you update the theme (e.g., Dawn 12.0 to 13.0), re-apply the snippet to the new theme.liquid after the update. The snippet does not persist across theme version changes.

Key Facts

Limitations

• The checklist assumes a standard Online Store 2.0 theme. Headless, Hydrogen, or heavily customized checkouts may need developer involvement.
• SeaText does not support localhost or ephemeral preview URLs; you must have a stable, publicly resolvable domain.
• The snippet only enables SeaText agents. It does not automatically translate, optimize, or personalize content until you activate specific agents in the dashboard.
• If you change your primary domain later, you must update the domain in SeaText settings and re-verify the snippet loads on the new domain.

FAQ

Can I add the code while my store is password-protected?

Yes. The script loads regardless of storefront password. However, SeaText agents cannot analyze live visitor behavior until the store is public and receiving traffic.

What if I paste the snippet but don't activate any agents?

Nothing changes on your site. The script remains inert. You can leave it there indefinitely until you are ready to turn on agents.

Do I need to add the code again after a theme update?

Yes. Theme updates replace theme.liquid. Re-paste the snippet into the updated file and save.

Can I use the same SeaText account for my main store and a staging store?

No. Each domain requires its own account. Create a second account for the staging subdomain.

Where exactly in theme.liquid should I paste the snippet?

Just before the closing </head> tag. This ensures the script loads early on every page.

How do I verify the script is loading?

Open the published theme preview, open browser DevTools (F12), go to the Network tab, filter for "JS", and reload. You should see the SeaText script request with a 200 status. No console errors should appear.

What happens if I activate agents before the snippet is live?

Agents will not function. The dashboard may show a warning that the script is not detected. Publish the theme with the snippet first, then activate agents.

Can you deactivate SeaText's AI when you don't need it? Yes. SeaText's AI stays inactive until you activate an agent, and you can leave agents off whenever you want. Turning off AI really means switching off the agents that rewrite, translate, or optimize your pages, or simply not activating them in the first place.

How SeaText AI agents work

SeaText describes its product as a set of autonomous AI agents. Each agent does one job. Some rewrite headlines and product blocks for paid clicks. Some translate pages into other languages. Some detect bot traffic and prepare refund evidence. Conversion rate optimization (CRO) agents test ways to turn more visitors into customers.

The AI remains inert until you activate an agent. This is confirmed by the Shopify integration page, which states that the AI remains inert until activated, ensuring the integrity of your website's content [S1]. The homepage also says you activate the autonomous agents you need [S2]. There is no separate "AI proceed" module; the effect is the sum of active agents.

How to turn agents off (and back on)

The controls live in your SeaText account where the agent list appears. You'll see activation buttons like the ones on the homepage agent cards. To deactivate an agent:

1. Log in to your SeaText account.
2. Open the agent list.
3. Find the agent that is currently active.
4. Switch it off.
5. Check a live page on your site to confirm the content now matches what you published.

To turn it back on, repeat the same steps and switch the agent on. The agent doesn't need to be deleted just because you paused it.

If you haven't installed the script yet, you can also choose your agents before installation. That's often the easiest way: only add the features you know you need. Remember that each SeaText account is linked to one primary URL. If you use a development domain and a production domain, you'll have separate accounts. Keep agents off in the account where you don't want changes [S1].

Key facts at a glance

These facts come from SeaText's own public pages. They give you the practical boundaries for deactivation.

When you might want to disable an agent

Turning an agent off makes sense in several situations.

• Your paid campaign ended and you no longer need landing pages rewritten for those keywords.
• Your team wants to run its own manual A/B test without AI changes interfering.
• You're in a regulated industry and need every product claim approved by a human before it appears.
• You only wanted one feature, like translation, and don't need the other agents.
• You're testing the script on a real domain before deciding which agents to keep.

There's also a seasonal use case. If you run a promotion, you might turn an agent on for that campaign and turn it off afterward when you want to test a new site design.

Before you switch off an agent, ask two questions. Is this agent helping an active campaign? Do I need this page to stay exactly as published? If either answer points to no, turn it off.

The trade-off is simple. When an agent is off, it isn't optimizing for you. If it was helping with conversion rate, you lose that help until you switch it back on.

What changes after you deactivate

After you deactivate an agent, SeaText stops making automatic changes to your pages. Visitors see the content you published, not a rewritten version. Your original content in the theme or CMS stays as it was.

You don't need to uninstall the whole script. With no active agents, the script simply sits there. It does not inject any changes because the AI remains inert until activated [S1].

Leaving agents off vs. uninstalling the script

You have two ways to stop AI activity: leave agents off or remove the script entirely. Both stop AI changes, but they differ in convenience and future use.

If you plan to use SeaText again, leaving agents off is faster. If you are sure you won't return, uninstalling keeps your site lighter.

Limitations to keep in mind

There are a few limits to know before you rely on deactivation.

• No centralized off switch is documented. You may need to turn off each active agent individually.
• Each account is tied to one primary URL. If you have multiple domains, you need one account per domain, and turning off agents affects only that account's domain [S1].
• Development URLs like localhost are restricted. You can't use SeaText to test on localhost, so plan to use a real domain for staging tests [S1].
• If you remove the script entirely, that also stops all AI, but you'll need to reinstall the snippet before you can reactivate agents.
• If you're on a managed plan where a human team runs agents for you, ask them to pause the agents. The public pages don't describe every plan-level control.

These limitations don't make deactivation hard. They just mean you should manage agents in the right account and use a real domain when testing.

Troubleshooting deactivation

If you switch off an agent but still see changes, check these common issues.

• Wrong account: Ensure you are logged into the SeaText account linked to the domain you are testing. Each account is tied to a single primary URL [S1].
• Cache: Clear your browser cache and any server-side cache (CDN, hosting cache) because old rewritten HTML may be served from cache.
• Multiple agents: Verify that all agents you want off are actually off. The dashboard shows each agent's status separately.
• Script still present: If you uninstalled the script but see changes, the snippet may still be in your theme files. Search your theme code for the SeaText snippet and remove it completely.
• Managed plan: If a team manages agents for you, contact them to confirm they have paused the agents on their end.

If none of these solve the problem, reach out to SeaText support with your account ID and the URL where you see unexpected changes.

Frequently asked questions

Will my pages go back to the original text?

Yes. When no agent is active, SeaText isn't rewriting your pages. Your original content from the theme or CMS is what visitors see.

Can I keep the script installed but turn off all agents?

Yes. The script is inert until you activate an agent. Keeping it installed does nothing by itself [S1].

Does turning off one agent stop the others?

No. Each agent activates separately. You can run translation while leaving the Google Ads or CRO agents off [S2, S3].

Can I turn an agent back on later?

Yes. Go back to the agent list, find the agent, and activate it again.

What if I don't need SeaText at all?

The simplest approach is to not activate any agent. If you already activated some, switch them off. You can also remove the script from your theme if you want a clean removal.

Adding the SeaText snippet to a store with multiple themes comes down to one question: which theme will a visitor's browser actually load? SeaText installs through a code snippet in each theme's theme.liquid file. A single store can hold many theme copies, but only the published theme is shown to shoppers. Draft themes, archived themes, and local previews do not run the snippet until you publish them and paste the code into their files.

Which themes should get the snippet

Use this simple filter: will this theme serve a real visitor on your primary domain? If yes, add the snippet. If no, wait until the theme becomes live. The table below shows the main cases.

Do not add the snippet to every copy in your theme library. That creates extra code in files that nobody visits. It also increases the chance of inconsistent versions when you later switch themes.

Manual per-theme install vs. app-based options

SeaText currently uses a manual per-theme installation. You edit code in each theme that you want to activate. An app-based alternative would install once and work across all themes automatically. At the time of writing, SeaText's Shopify integration guide does not describe an official app for this. If an app becomes available, it could remove the need to touch each theme. Check with the vendor for current options.

If you only have one theme, the manual path is simple. If you manage many client stores, an app could save time. Because the integration guide does not document an app today, treat the app row as a question to confirm, not a current promise.

What you need before you start

Before you open the Shopify code editor, collect three things.

• A SEATEXT AI account. The integration guide says you need an account before you can install the script.
• The JavaScript snippet from your SeaText account area.
• Shopify admin access with permission to edit theme code.

You also need a real, valid domain. SeaText restricts development URLs such as localhost for security reasons. The snippet must be tied to a production domain, not a local preview.

Step by step: install the snippet on one theme

Use this walkthrough for each theme that will serve visitors. The steps are the same for the first theme and every later theme.

1. Log in to your Shopify admin.
2. Go to Online Store > Themes.
3. Find the theme you want to use. Click the three dots icon next to it, then choose Edit code.
4. Look for the Layout folder on the left side of the screen.
5. Open the file named theme.liquid.
6. Paste the SeaText JavaScript snippet into that file.
7. Click Save to preserve your changes.

Repeat these same steps for every additional theme that will go live. There is no store-wide toggle in the SeaText integration guide. The snippet only works where you paste it.

Common mistakes when managing multiple themes

• Installing only on the current published theme. If you later publish another theme, SeaText will not load on it until you paste the snippet into that theme's theme.liquid.
• Adding the snippet to every draft copy. This creates needless code and makes future updates harder. Only add it to themes you intend to serve.
• Using one account across different domains. The integration guide is explicit: each account is linked to a single primary URL. For two live domains, create separate accounts.
• Skipping the product description tag. The main theme snippet goes in theme.liquid, but the product description tag belongs in the product template, usually product.liquid or product-template.liquid. Both parts are needed for full product coverage.
• Not backing up before editing. A small typo in one theme can break your storefront. Duplicate the theme or export a copy before you paste code.

How to keep the snippet working through theme updates

Shopify themes change over time. Developers release updates, and your team may edit files. The snippet lives directly in theme.liquid, so an update or manual rewrite can remove it.

Treat the snippet as a tracked file, not a one-time change. Before you edit a theme, save a copy of the current theme.liquid. If your team uses Git, keep the file in a repository. If not, download a zip of the theme from your admin. That backup lets you compare the old and new versions when something goes wrong.

When you install a theme update, open the updated theme.liquid and confirm the snippet is still present. Some updates replace entire files and discard your pasted code. Re-paste the snippet after each major update, then test the storefront.

Test before you publish. Put the updated theme in preview mode or on a staging domain that uses a real URL. The integration guide allows real production or development domains, but blocks localhost and unreliable dynamic domains. On a staging domain, create a separate SeaText account for that domain so the snippet can associate traffic correctly.

How to verify the snippet is live

After you save the theme, verify the install instead of assuming it worked.

1. Open a product page on your storefront.
2. Preview the page the way a visitor would see it.
3. Open your browser's developer tools.
4. Inspect the page's HTML source and look for the SeaText script or its data attribute.

If you are also implementing the product description tag, preview a product page and confirm the data- attribute is present in the HTML source. The integration guide points to this same verification step.

Limitations and edge cases

The snippet is not global across your theme library. If you switch to a new theme without pasting the snippet into it, SeaText will not load on that theme.

Duplicated themes. If you duplicate a theme in Shopify, the copy may keep the snippet because it inherits the files. Do not assume that. Open the copy's theme.liquid and confirm before publishing it that the snippet is present.

Staging environments. localhost is restricted. Use a real domain or a staging subdomain that SeaText can associate with an account. Because each account is tied to one primary URL, create a separate account for the staging domain. Do not paste a production snippet into a staging site unless you want its traffic attributed to that production account.

One account across multiple domains. You cannot reuse a single SeaText account for two live websites. The integration guide says to create one account for each website. Mixing accounts will cause the snippet to point traffic to the wrong primary URL.

Product template vs. theme.liquid. The main snippet belongs in theme.liquid. The product description tag belongs in the product template. Forgetting one of them means the page may load SeaText but not expose the full product data, or vice versa.

Dynamic development domains. Some hosting providers generate temporary URLs that change. SeaText may not be able to reliably associate traffic with your account on such domains. Stick to a stable domain when you need to test.

FAQ

How do I handle theme updates?

Store a backup of theme.liquid before each update. After the update, reopen the file and confirm the snippet is still there. If the update replaced the file, paste the snippet again and test.

Does the snippet affect theme performance?

The integration guide says the script is inert until activated. That means it does not change your content until you turn it on. For specific performance measurements, test on a staging copy and check with the vendor.

What do I do if the snippet is accidentally removed?

Paste it back into theme.liquid using the account that matches the domain. If you have a backup, restore the snippet from there. Then verify by previewing the storefront.

Do I need a separate SeaText account for each theme?

No. Themes on the same primary URL can share one account. You need a separate account only when the theme serves a different domain.

Can I use one account for multiple client websites?

No. The integration guide says to create one account per website. Each account is linked to a single primary URL.

Is it safe to test on localhost?

No. Development URLs such as localhost are restricted for security reasons. Use a real, valid domain, or a staging domain with its own SeaText account.

Prerequisites Before You Start

Before adding SeaText code to your Wix site, confirm two requirements. First, your Wix site must be on a paid plan — free Wix plans do not allow custom code installation. This is a hard platform limitation; the Custom Code section simply will not appear on free plans. Second, you need an active SeaText AI account. If you don't have one, create it at SeaText.com before proceeding. Each SeaText account connects to a single primary domain, so plan accordingly if you manage multiple websites. The account creation process takes under a minute and gives you the JavaScript snippet you will paste into Wix.

Why These Prerequisites Matter

The paid plan requirement exists because Wix reserves custom code injection for customers on premium tiers. This protects platform stability and security. The single-domain-per-account rule in SeaText ensures accurate traffic attribution. The AI uses your domain to associate visitor behavior, conversion events, and agent activity with the correct account. If you try to use one account across two domains, the dashboard will only show data for the primary URL. The other site will appear disconnected.

Step-by-Step Installation Process

1. Copy your SeaText JavaScript snippet. Log into your SeaText dashboard and copy the integration code provided in the integration section. The snippet is a single <script> tag that loads the SeaText runtime asynchronously. Do not modify it.
2. Open your Wix dashboard. Access your Wix account and navigate to the specific project (site) you want to translate or optimize. If you have multiple sites, pick the correct one from the site selector.
3. Go to Settings > Custom Code. In the left sidebar, click Settings, then scroll to the very bottom under Advanced to find Custom Code. This location is consistent across all standard Wix Editor sites.
4. Add code to the Head section. Click "Add Code" under the Head section. A pop-up window appears. The Head placement ensures the script loads early, before page content renders, which is required for zero-flicker AI rewrites.
5. Paste and configure. Paste the SeaText JavaScript into the "Paste the code snippet here" field. Under "Add Code to Pages," select "All pages" from the dropdown. Then choose "Load code on each new page" and click Apply. The "All pages" selection ensures the AI runs on every URL, including blog posts, product pages, and dynamic routes. The "Load code on each new page" option handles Wix's single-page-app navigation so the script re-initializes on route changes.
6. Save and publish. Click Save, then publish your site to make the code live. The Save button stores the configuration; Publish pushes it to your live domain. Both steps are required.

Multi-Domain and Development Environment Considerations

SeaText ties each account to one primary URL. If you run a development domain (staging.example.com) and a production domain (example.com), you need separate SeaText accounts for each. Localhost and dynamic development URLs are restricted for security reasons — SeaText cannot reliably associate traffic with your account on those environments. Use a real, publicly accessible domain for testing. This means you cannot test on localhost:3000 or Wix's free *.wixsite.com subdomains. A staging subdomain on your own domain (e.g., staging.yourdomain.com) works if it resolves publicly and uses HTTPS.

Activation and Verification

After publishing, the installation isn't complete. You must visit your live site several times and stay on a page for at least 40 seconds. This activity activates the AI and links it to your SeaText account. The 40-second threshold ensures the script has time to initialize, send a heartbeat, and register the session. Then wait at least five minutes. Check your SeaText dashboard — your website name should appear next to the SeaText logo at the top of the page. If it doesn't appear after 10 minutes, contact SeaText support; this usually indicates an installation issue on the Wix side that requires assistance. Common causes: the script was placed in Body instead of Head, "All pages" was not selected, or the site was not published after saving.

Troubleshooting Common Issues

• Code not saving: Ensure you're on a paid Wix plan. Free plans block the Custom Code section entirely. Upgrade first, then retry.
• "Load code on each new page" missing: This option appears only after selecting "All pages" in the dropdown. If you choose "Specific pages," the option disappears.
• Site not connecting after 10 minutes: Clear browser cache, revisit the site for another 40+ seconds, and wait. If still unresolved, contact support with your site URL and SeaText account email.
• Multiple sites under one Wix account: Each site needs its own SeaText account and separate code installation. The Wix dashboard lets you switch sites; repeat the process for each.
• Script appears in source but dashboard stays empty: Verify the script loads in the browser dev tools Network tab. Look for a request to SeaText's CDN. If blocked by a content security policy or ad blocker, the connection will fail.

What Happens After Successful Connection

Once your site appears in the SeaText dashboard, proceed to the Main AI Hub to activate the agents you need. Click "Configuration" on any agent to adjust its parameters. The AI remains inert until you explicitly turn each one on, so your site content stays unchanged until you're ready. Key agents include:

• AI CRO Reading Analysis — analyzes visitor reading patterns and generates winning copy at scale. It measures scroll depth, dwell time, and text engagement to identify underperforming sections.
• Website Translation (125 languages) — translates your entire site with zero code and full control. You can review, edit, or lock translations per language.
• Google Ads Landing Page AI — rewrites landing pages in real time to match each campaign keyword. When a visitor clicks an ad, the page adapts headlines, offers, and CTAs to the search term.
• AI Copy A/B Testing — generates variants and automatically scales winners. It runs continuous multi-armed bandit tests on headlines, CTAs, and product copy.
• Conversion Relay (CAPI) — forwards 100% of real purchases to Meta and Google CAPI. This restores conversion signals lost to browser privacy changes.
• Bot Protection Agent — detects fraudulent clicks and prepares refund claims for Google and Meta. It identifies bot traffic patterns and exports evidence for ad platform disputes.
• AI Personalization Agent — adapts site copy in real time to visitor context such as location, referrer, device, and behavior history.
• Local AI SEO — ranks for every "near me" and neighborhood search by generating localized landing pages automatically.

Key Facts at a Glance

Limitations and When This Guide Doesn't Apply

• Wix Editor vs. Wix Studio: These steps apply to the standard Wix Editor. Wix Studio may have a different Custom Code location or require a different workflow. Check Wix Studio documentation if you use that platform.
• Free Wix plans: Cannot install custom code at all. Upgrade first.
• Headless or React-based Wix setups: If you use Wix Headless or custom React components, the standard Custom Code method may not cover all routes. The script injects into the main document head but may not execute inside iframe-embedded apps or server-rendered paths.
• Immediate AI changes: The script loads instantly, but AI agents only run after you activate them in the SeaText dashboard. No content changes happen automatically.
• GDPR/cookie consent: SeaText loads via your Custom Code placement. If you use a consent management platform (CMP), ensure the script loads after consent or is categorized as essential/functional. Otherwise, the script may be blocked until the user accepts cookies, delaying activation.
• Single-page application navigation: Wix uses client-side routing. The "Load code on each new page" setting handles re-initialization, but custom hash-based routes or anchor links may not trigger a reload. Test key user flows after installation.

Practical Scenarios and Decision Criteria

Scenario 1: E-commerce store on Wix

You run a Shopify-level store on Wix. You want translation for 20 languages, AI A/B testing on product pages, and conversion relay to Meta CAPI. Follow the installation steps. After connection, activate Website Translation, AI Copy A/B Testing, and Conversion Relay. Configure each: select target languages, set test parameters for product titles and CTAs, and map your purchase event to the CAPI endpoint. Expect 40-second activation, then 5-10 minutes for dashboard connection.

Scenario 2: Lead generation site with Google Ads

You drive paid search traffic to a Wix landing page. You need Google Ads Landing Page AI to match headlines to keywords. Install the script. Activate Google Ads Landing Page AI. In configuration, connect your Google Ads account so the agent can read campaign keywords. The agent rewrites the page per visitor's search term. No new pages are created; the DOM updates in real time.

Scenario 3: Multi-language blog

You publish content in English and want automatic translation to Spanish, French, German. Install script. Activate Website Translation. Choose languages. The agent translates on-the-fly and caches translations. You can edit any translation in the dashboard. SEO metadata (hreflang, translated titles) is handled automatically.

Decision criteria for agent selection

• If you run paid ads → Google Ads Landing Page AI, Conversion Relay, Bot Protection.
• If you serve international visitors → Website Translation, Local AI SEO.
• If you optimize conversion rates → AI CRO Reading Analysis, AI Copy A/B Testing, AI Personalization.
• If you want AI chat → Free AI Website Chat (no extra setup).

Frequently Asked Questions

Do I need coding skills to install SeaText on Wix?

No. The process uses Wix's built-in Custom Code UI. You only copy and paste the provided JavaScript snippet — no editing required.

Can I use one SeaText account for multiple Wix sites?

No. Each SeaText account links to a single primary URL. Create a separate account for each domain.

How long until I see translation or optimization changes on my site?

After the site connects (5-10 minutes post-activation), you must enable specific agents in the SeaText dashboard. Changes appear only after you activate and configure each agent.

Will SeaText slow down my Wix site?

The script loads asynchronously. SeaText claims zero-flicker operation for split URL tests and real-time rewrites, but actual performance depends on your site's existing load and the agents you activate. Most sites see no measurable impact on Core Web Vitals.

What if I switch Wix templates or redesign the site?

The Custom Code persists across template changes because it lives in Settings, not the page design. However, always verify the code remains after major redesigns.

Can I install SeaText on a Wix site that uses a custom domain connected elsewhere?

Yes, as long as the domain points to the Wix site and you have a paid Wix plan. The domain registrar doesn't affect the Custom Code installation.

Is there a way to test SeaText on a staging site before going live?

Use a real staging domain (e.g., staging.yourdomain.com) with its own SeaText account. Localhost and Wix's free *.wixsite.com URLs may not work reliably for activation.

What happens if I cancel my SeaText subscription?

The script remains on your site but the agents deactivate. No AI changes occur. You can remove the script from Wix Custom Code at any time.

Does SeaText work with Wix's built-in SEO tools?

Yes. SeaText operates at the content layer. It does not conflict with Wix SEO patterns, meta tags, or structured data. Translated pages get proper hreflang tags automatically.

Can I exclude certain pages from SeaText?

In Wix Custom Code, you selected "All pages." To exclude pages, you would need to choose "Specific pages" and list every URL you want included. This is impractical for large sites. Instead, use SeaText dashboard configuration to disable agents on specific URL patterns.

How does SeaText handle dynamic content loaded via AJAX?

The "Load code on each new page" setting re-runs the SeaText initialization on Wix route changes. For AJAX content within a page (e.g., infinite scroll), the agent observes DOM mutations and processes new elements automatically.

What support channels exist if installation fails?

SeaText offers email support and live chat from the dashboard. Provide your site URL, SeaText account email, and a screenshot of the Wix Custom Code configuration. Most issues resolve within one business day.

To connect Seatext to Shopify, you don't use the Shopify Admin API. Seatext's standard Shopify connection uses a JavaScript snippet that you copy from your SEATEXT AI account and paste into your theme's theme.liquid file. Then you wrap your product descriptions with a tag that includes a data attribute so the script knows where the description lives.

This guide walks through the prerequisites, the exact template steps, and one final check to confirm everything is connected.

Before You Start: What You Need

These four things should be ready before you touch any code:

• A SEATEXT AI account. The integration instructions say: "Before you can install the script, you need a SEATEXT AI account." If you don't have one, create it first.
• Shopify admin access with permission to edit your theme code.
• A valid real domain. Development URLs such as localhost are restricted for security reasons.
• One account per domain. Each SEATEXT AI account is linked to a single primary URL.

How Seatext Actually Connects to Shopify

If you start by searching for "Shopify API," you might expect to create a custom app, generate API keys, and enter them somewhere. That's not how this integration works. Seatext connects through your theme, not through Shopify's Admin API.

The script loads on your store pages and does the work there. It can rewrite product copy, match landing pages to ad keywords, translate pages, and run other agents you activate. There are no API tokens to manage for this setup.

That's also why the product template needs a small edit. The script has to find your product description. The data attribute acts as a marker. Without it, the product description part of the integration won't run.

If your real goal is Shopify Admin API access, say to sync orders or inventory into your own system, that's a separate custom app project. This guide covers the Seatext theme-based connection.

Step-by-Step: Connect the Seatext Script to Shopify

1. Log in to your SEATEXT AI account. The code snippet lives there. The official steps say you must have an account before installing the script.
2. Copy the JavaScript code from the integration section of the Shopify Integration page. In the page, this appears as the SEATEXTCODEINTEGRATION block with your actual script.
3. Log in to Shopify admin and go to Online Store, then Themes.
4. Open the theme editor. Next to the theme you want to use, click the three dots icon and select “Edit code”.
5. Open theme.liquid. On the left side, expand the Layout folder and click theme.liquid.
6. Paste the snippet into the file. Choose a spot where the script will load on your store pages. If your theme has a scripts area, that's a natural place.
7. Click Save. The integration instructions say: "Once the code snippet has been successfully pasted, click on the 'Save' button to preserve your changes."

Add the Tag to Your Product Descriptions

The snippet alone is not the whole setup. Seatext also needs to know where product descriptions are rendered.

1. Keep the theme editor open. Find the product template. It is typically named product.liquid or product-template.liquid.
2. Find the product description output code. This is the block that prints the description on the product page.
3. Wrap the description output with the Seatext tag. The exact tag is shown in your Seatext instructions. It includes the data attribute that the script looks for. Copy it from the documentation rather than retyping it.
4. Save the file.

For additional context, Seatext points to its own AI scope documentation for details on what the agents can change.

Test the Connection

Don't skip this step. A quick test takes under a minute.

1. Open a product page on your live store and preview it.
2. Check the description. It should still display normally after the template edit.
3. Open your browser's developer tools (right-click, then Inspect).
4. Look for the data attribute. The official steps say: "Verify that the data- attribute is present in the HTML source (you can inspect this using your browser's developer tools)."

One thing to expect: the installation process is secure, and the AI remains inert until activated. So you won't see rewritten copy immediately after saving. Content changes appear after you activate the agents you want.

Key Facts About the Seatext-Shopify Connection

Limitations and When This Guide Doesn't Apply

• Localhost and dev domains. Development URLs such as localhost are restricted. Dynamic development domains may not function correctly because Seatext may not reliably associate traffic with your account.
• Multiple websites. Use one account per website. Don't reuse a single account across stores or domains.
• Real API projects. If you need Shopify Admin API access to read or write store data, this theme-based guide doesn't cover it. That requires a custom Shopify app.
• Non-standard storefronts. If you run a headless storefront or a custom front end, the theme.liquid approach may not apply. Check with Seatext for current options.

Common Mistakes to Avoid

• Editing the wrong theme. Make sure the theme you open is the one currently in use.
• Pasting into the wrong file. The snippet belongs in theme.liquid under the Layout folder.
• Skipping the product description tag. Without it, product descriptions won't be optimized.
• Reusing one account for several domains. Each account is tied to one primary URL.
• Testing on localhost. It's restricted and can look broken or fail.
• Forgetting to save. Theme changes only take effect after you click Save.

Frequently Asked Questions

Does Seatext use Shopify API keys or tokens?

No. The standard Seatext connection uses a JavaScript snippet in your theme. You don't create Shopify API credentials for it. If you need Admin API access for custom development, that's a separate custom app project.

Why does my product description need a data attribute?

The data attribute marks where the description is rendered in your template. Seatext's script uses it to find and optimize the content. Without it, that part of the integration can't run.

Can I test Seatext on localhost?

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

Can one Seatext account cover multiple stores?

No. Each SEATEXT AI account is linked to a single primary URL. Create a separate account for each website or domain.

Will Seatext change my content right after installation?

No. The installation process is secure, and the AI remains inert until activated. You'll see changes only after you activate the agents you choose.

Where do I find the snippet and the tag?

Both come from your SEATEXT AI account through the Shopify Integration page. Copy them from there so the code matches exactly.

What Permissions Does SeaText AI Need for Shopify?

SeaText AI needs no Shopify API permissions. It does not use OAuth, API scopes, or server-side app access. Instead, it connects by adding a small JavaScript snippet to your theme’s theme.liquid file.

This means you do not need to grant read or write access to products, orders, customers, or analytics data. The script runs in the visitor’s browser, not on Shopify’s server. Data stays on the frontend, and SeaText cannot change your Shopify backend records.

What you do need is admin access to your Shopify store so you can edit the active theme. That is the only permission required for the standard integration.

Why the Permission Model Matters for Store Owners

Many Shopify apps ask for broad API access during installation. They can read customer data, update inventory, or create orders. SeaText AI avoids that model. It lowers the security and privacy burden on the merchant.

Because no API scopes are granted, there is no separate permission page inside Shopify admin. There is no app installation window that lists required data access. The integration is code-based instead.

For stores with strict compliance rules, this is a clear advantage. You are not handing over customer records or order history. The script only changes how the page behaves for the visitor.

It also simplifies troubleshooting. If you ever want to remove SeaText, you delete the snippet from theme.liquid. No API credentials to revoke, no access tokens to expire.

Readiness Checklist: What You Need Before Connecting

Use this checklist before you start. It covers every requirement from the official SeaText Shopify guide.

• Active SeaText AI account – Create an account at seatext.com if you don’t have one yet. You need it to get your unique JavaScript snippet.
• Shopify admin login – You must be able to log in with staff access that lets you manage themes.
• Access to Online Store → Themes – Go to Online Store, then Themes, to find the theme you want to edit.
• Ability to open Edit Code – Click the three dots next to your active theme and choose Edit code.
• Access to the Layout folder – Open Layout in the file list and locate theme.liquid.
• Permission to save theme changes – Paste the snippet into theme.liquid and click Save.
• A real production domain – Localhost is restricted. Use your live store domain, not a mock URL.
• Separate account for each domain – If you test on a development domain, create a separate SeaText account for that domain.

If you can check every item, you are ready. The installation itself takes about one minute.

Common Questions About API Scopes and Backend Access

Below are the typical permission-related questions buyers ask during an editorial review.

Does SeaText need product read/write access?

No. The script does not call Shopify’s product API and cannot update product names, prices, or inventory.

Does SeaText need order or customer access?

No. SeaText cannot read orders or customer records. It also cannot create orders or modify customer accounts.

Does SeaText need analytics permission?

No. The code runs frontend-side. It does not pull Shopify analytics reports into SeaText.

Will Shopify show a permissions screen for SeaText?

No. Since the connection is made through theme code, there is no standard app permission screen. You just add the snippet and save the file.

What about Shopify API rate limits?

They do not apply here. Server-side API limits only matter when a tool makes API requests. SeaText does not make them.

How the Installation Works Step by Step

Here is the workflow from the official integration guide.

1. Log in to your Shopify admin.
2. Navigate to Online Store → Themes.
3. Find your active theme and click the three dots icon.
4. Select Edit code.
5. Open the Layout folder on the left side.
6. Select the file named theme.liquid.
7. Copy the JavaScript snippet from your SeaText AI account.
8. Paste it into the file in the correct location.
9. Click Save to preserve your changes.

After saving, the snippet is live. The AI itself remains inactive until you activate it from the SeaText dashboard. This gives you time to review the change before the agents start running.

For product description optimization, SeaText also provides steps to wrap the description output with a specific data attribute. You locate product.liquid or product-template.liquid, add the tag, and test the page in a browser.

Limitations and When This Connection Approach Does Not Fit

The code-based connection works well for standard Shopify themes. It has clear limits.

Headless storefronts. If your Shopify storefront is headless and does not use theme.liquid, the snippet cannot be placed in the same file. You may need a custom development path.

Server-side tasks. SeaText cannot modify orders, adjust inventory, or automate backend workflows. It only changes the frontend experience in the browser.

Multiple stores. Each website needs its own SeaText account. One account is linked to one primary domain.

Development domains. Localhost is blocked for security reasons. Dynamic development domains may also fail because SeaText cannot associate traffic with your account reliably.

Theme updates. If Shopify updates your theme or you install a new one, the snippet may be removed. You need to reinsert it after the update.

Script conflicts. The integration is safe and stays inert until activation, but another tool could block JavaScript execution. Check your tag managers and security scripts if the integration behaves unexpectedly.

Practical Scenarios: Who Should Choose This Integration?

This connection fits most Shopify merchants who want AI-driven frontend optimization. Typical use cases include rewriting landing page copy for Google Ads, translating pages into 125 languages, running A/B copy tests, and adding AI chat.

It also fits stores that want to protect customer data. Since no backend data is shared, there is less exposure if an account is compromised.

It does not fit merchants who need a server-side app. For example, if you want to sync inventory or run automated order updates, look for an official Shopify app with the right API scopes. Check with the vendor for supported alternatives.

If you run a development store for tests, create a separate SeaText account for the development domain. Keep your production account separate for the live store.

Frequently Asked Questions

Do I need to install SeaText as a Shopify app?

No. You add a JavaScript snippet to your theme. There is no app installation or API permission screen.

Can SeaText read my customer data?

No. The script works in the browser and does not receive customer lists or order details from Shopify’s backend.

Can SeaText change product prices or inventory?

No. Product changes require server-side API access. SeaText does not have it.

What happens if I use Shopify’s new theme architecture?

You still work through Edit code, but file names may differ. Open the Layout folder and find the equivalent of theme.liquid. Contact SeaText if the standard path is unavailable.

How do I remove SeaText later?

Delete the JavaScript snippet from theme.liquid and save the file. Then deactivate or delete your SeaText account if you want to stop all use.

Is this connection GDPR-safe?

The integration does not export Shopify customer data to a server. Still, check the SeaText privacy policy and your own compliance requirements.

When you build a Shopify store on a development domain, you need to know which SeaText AI capabilities are actually usable. The platform is built around live visitor data, so the environment you test in matters a lot.

Feature Availability on Development Stores

Why This Matters: Development vs. Production Environments

SeaText AI links every account to a single primary URL. The system validates that URL, then watches real visitors to decide when to rewrite copy, start chats, or block bots. Development URLs such as localhost or temporary preview domains are restricted for security reasons. Without a verifiable, publicly reachable domain, the AI cannot associate traffic with your account.

If you try to enable agents that depend on live data, they will stay idle. You may think the integration failed, when in fact the platform is simply waiting for the required signals.

How SeaText AI Works: Domain Dependency

The integration guide states: "Multiple Domains – If you need to use SEATEXT AI on 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. Development URLs, such as localhost, are restricted for security reasons. Dynamic development domains may not function properly, as SEATEXT AI might be unable to reliably associate traffic with your account."

This means the JavaScript snippet can be placed on a dev store, but most agents will stay inert until the domain passes validation and receives genuine visitor traffic.

How to Verify Agent Activation on a Dev Store

1. Open the SeaText dashboard and select the dev‑store account.
2. Look at the status column for each agent. "Active" means the script loaded, but "No data" indicates no live traffic.
3. Use browser developer tools (Network tab) to confirm the seatext.js file is fetched without errors.
4. Trigger a manual event that does not require live traffic, such as clicking the free chat widget. If the chat window appears, the basic UI agent is working.
5. For agents that need traffic, you will see a greyed‑out or "Waiting for visitors" label.

When you switch to a production domain, the same dashboard will start showing real‑time metrics.

Common Misconceptions About Development Stores

• "All agents work as soon as the script is installed." Only agents that generate static content operate without traffic.
• "Localhost is enough for testing." The platform blocks localhost for security; no agent will activate.
• "Dynamic preview URLs behave like real domains." They often change on each build, preventing reliable traffic association.
• "If the dashboard shows "Active", everything is functional." "Active" only confirms the script loaded; data collection still requires real visitors.

Comparing Dev Store vs. Production Store Behavior

Understanding these differences helps you plan a realistic testing workflow.

Practical Workflow for Testing SeaText AI on a Dev Store

1. Create a separate SeaText account for the dev domain (e.g., dev.yourstore.com).
2. Paste the JavaScript snippet into theme.liquid as described in the Shopify Integration guide.
3. Enable only the agents that do not need live traffic: SEO Content Factory, Translation, and basic Chat.
4. Open the site in an incognito window and verify the snippet loads (Network tab).
5. Use the dashboard to confirm the selected agents show "Active" but no visitor data.
6. When you are ready to go live, duplicate the settings to a production account linked to your live domain.

Step‑by‑Step: Setting Up SeaText Correctly for a Dev Store

1. Log into your Shopify admin and go to Online Store → Themes → Actions → Edit code.
2. Open the Layout/theme.liquid file.
3. Paste the SeaText JavaScript snippet just before the closing </head> tag.
4. Save the file.
5. In the SeaText dashboard, create a new account for the dev URL and link it to the same snippet.
6. Activate only the safe agents (Content Factory, Translation, basic Chat).
7. Test the UI components on the dev store. Remember that conversion‑related agents will stay idle.

Limitations and When This Advice Does Not Apply

The guidance applies to any non‑production URL, including Shopify development stores, localhost, and dynamic preview domains. If you host a staging site on a real subdomain (e.g., staging.example.com) and create a dedicated SeaText account for that subdomain, the same rules hold: agents that need real traffic will still be ineffective because visitor volume is low.

Only when the domain is publicly reachable and receives genuine traffic will the full suite of autonomous agents become operational.

Frequently Asked Questions

Can I use SeaText AI on a Shopify development store?

Yes, but only for content generation, translation, and basic chat testing. Real‑time optimization agents need a production domain.

Do I need a separate SeaText account for my dev store?

Yes. Each account is tied to a single primary URL, and development URLs are restricted.

Will the AI SEO Content Factory publish pages on my dev store?

It can generate the pages, but they will not be indexed by search engines if the dev store blocks crawling.

What happens if I install the script on localhost?

The script loads, but the platform will not activate any agents because localhost is blocked for security reasons.

Can I test the Google Ads Optimization Agent on a dev store?

No. That agent requires live ad clicks and keyword matching, which a dev store cannot provide.

How do I know if SeaText AI is working on my development store?

Check the agent status in the dashboard and use browser developer tools to verify the script loads. If agents show "Active" but no data, they are waiting for real traffic.

Is there a way to test SeaText without a production domain?

You can use a staging site on a real subdomain and a separate account, but full functionality still depends on real visitor traffic.

The short answer: SeaText does not give you a single dashboard for all your domains. Each domain gets its own account and its own dashboard. So organizing multiple domains really means creating a separate account for each domain and then keeping those accounts clearly labeled and easy to switch between. You can use custom tags or labels for each domain in your own workflow, and filter reports by domain simply by opening the correct account. The core rule from SeaText is one account per website.

Why per-domain accounts matter

SeaText ties every account to a single primary URL. This design keeps data isolated. If you ran two domains under one account, visitor metrics from site A would mix with site B. You could not tell which traffic belonged to which domain. Reports would be meaningless. The one-account-per-domain rule avoids this confusion. Each account sees only its own domain's data. No mixing. No guesswork. This is a deliberate choice by SeaText to ensure accurate reporting. As noted in the SeaText documentation, “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.”

What You Need Before You Start

Before you set up multiple domains, make sure you have:

• A SeaText account for each domain. Each account is linked to a single primary URL.
• A valid, real domain for each site. Localhost and dynamic development URLs are restricted.
• A password manager or a simple naming system to keep your logins separate and findable.

Step 1: Create One SeaText Account per Domain

SeaText's documentation is direct: “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 account is tied to one primary URL. Without separate accounts, you risk mixing data and confusing which domain the traffic belongs to.

Create a fresh account for each website you manage. Use the domain name when you sign up so the account is easily identifiable later.

Create your domain-to-account inventory

Before you start creating accounts, map out every domain you manage. Include production, staging, and any subdomains you plan to use. For each domain, decide on a clear account name. A good pattern is domain-environment. For example:

• mysite.com → account name: mysite-production
• staging.mysite.com → account name: mysite-staging
• client-acme.com → account name: acme-production
• dev.client-acme.com → account name: acme-dev

Store these accounts in a password manager. Create a folder named “SeaText Accounts” or “Multi-Domain Logins”. Inside that folder, create subfolders for each client or project. For example:

• SeaText Accounts
  ├── My Sites
  │ ├── mysite-production
  │ └── mysite-staging
  └── Client Work
  ├── acme-production
  └── acme-dev

Set each password entry's title to the same account name you used. Add a note with the domain URL. This way you can find the right login in seconds.

Step 2: Name Your Accounts Clearly

Use a consistent naming scheme for your accounts. Add the domain or a short label in the username line or the account profile. For example:

• For mysite.com, use mysite-production or just mysite.com.
• For staging.mysite.com, use mysite-staging.
• For a client site, use client-acme-main and client-acme-staging.

Store these logins in a password manager. Name each entry exactly the way you will search for it later.

Step 3: Use Tags and Labels in Your Own System

Since SeaText's dashboard is per-account, tagging and grouping happen outside the platform. Use your password manager's folders, tags, or notes to group domains by project, client, or environment. Create folders such as “Production Domains” and “Staging Domains”, or add tags like “dev”, “prod”, “clientA”, and “clientB”. This is the custom labeling that keeps your workflow organized.

Step 4: Filter Reports by Domain

Inside each SeaText dashboard, you will see only that account's domain data. Use the reporting tools to set date ranges, look at specific pages, or focus on a campaign. There is no cross-domain report, but each account's data is automatically filtered to its own domain. If you need a particular metric, select the right account first and then apply any additional filters.

Step 5: Isolate Development and Production Domains

SeaText restricts certain development URLs. “Development URLs, such as localhost, are restricted for security reasons.” Dynamic development domains may also fail to function properly because SeaText might not reliably associate traffic with your account. For testing, use a valid, real domain. A subdomain like staging.yourdomain.com works well, but it still needs its own SeaText account. Keep development data separate from production data so you don't accidentally read test traffic as real results.

Step 6: Verify You're in the Correct Account

Before checking reports or making changes, confirm which account you are in. Look at the primary URL shown in the account settings or dashboard header. Also check the website in your browser's address bar. This simple verification prevents you from adjusting the wrong domain's page or misreading another site's metrics.

Common multi-domain mistakes

Many users make the same errors when managing multiple SeaText accounts. Avoid these three pitfalls:

Same-account installs on multiple domains. Some try to install the same SeaText script on two different domains. This breaks the one-account-per-domain rule. Metrics get mixed. You cannot trust the data. Always create a separate account for each domain and install the corresponding script.

Using localhost or dynamic development URLs. SeaText restricts localhost and other non-real domains. Dynamic development URLs may not function properly because SeaText might not reliably associate traffic with your account. Always use a valid, real domain even for staging or testing. A subdomain like staging.example.com works.

Failing to verify the active account before editing reports. When you have multiple accounts open in different tabs, it is easy to edit the wrong one. Always check the primary URL in the account settings before making changes. This prevents accidental edits to the wrong domain's data.

Step 7: Switch Quickly with Browser Profiles

If you manage many domains, use separate browser profiles or a multi-login extension to stay signed in to multiple SeaText accounts at the same time. For example, create a Chrome or Firefox profile for each client or environment. Name the profiles after the domain: “mysite-prod”, “mysite-staging”, “client-acme”. This lets you switch with a click instead of logging in and out repeatedly.

Key Facts: SeaText Multi-Domain Setup

Limitations and Workarounds

SeaText does not offer a single aggregate dashboard for multiple domains. You must log in to each account separately. If you need a unified view, consider using a third-party reporting tool that can pull from each SeaText account, or just keep a bookmarked folder of all your SeaText dashboards.

Another limitation is that localhost and dynamic development domains are not supported. The workaround is to use a real domain, even for staging, and to create a separate account for that staging domain. This keeps development data isolated and ensures the script works reliably.

FAQ

Can I see all my domains in one SeaText dashboard?

No. SeaText ties each account to one primary URL, so there is no combined view. You need to log in to each account separately.

How many SeaText accounts do I need?

One account per domain. If you have three domains, you need three accounts. If you have a production and a staging site, you need at least two.

Can I use a subdomain as a separate domain?

Yes. A subdomain like staging.example.com is a valid real domain and works well for testing, but it still needs its own SeaText account.

Is localhost supported?

No. Localhost and similar development URLs are restricted for security reasons.

What if I accidentally install the same SeaText account on two domains?

SeaText's rule is to create separate accounts for each domain. Sharing one account across domains may lead to data mixing and unreliable traffic association. Create a new account for the second domain and reinstall the script with the correct code.

How do I keep my logins organized?

Use a password manager and save each account under a clear name. Add tags or folders for environment, client, or project. This makes it easy to find the right dashboard in seconds.

Quick Answer

SeaText works with Odoo 14, 15, 16, and 17. The integration does not rely on a deep backend module; it loads a JavaScript snippet through Odoo's standard "Embed Code" block inside the Website editor. If your Odoo instance has the Website module and the Dynamic Content section with an Embed Code block, you can install SeaText.

How the Integration Works

SeaText connects to Odoo by pasting a JavaScript snippet into an Embed Code block. You log in to Odoo, open the Website module, edit the target page, drag the Embed Code block from the Dynamic Content section into the page, paste the snippet, and save. The script stays inert until you activate it in your SeaText dashboard.

Why Version Compatibility Matters

Odoo releases a new major version each year. Older versions eventually lose security patches and official support. If you run an unsupported version, you risk compatibility issues with the Website module or the Embed Code block. Staying on a supported version (14–17 at the time of writing) ensures the integration surface SeaText uses remains stable.

Decision Criteria for Choosing an Odoo Version

Step-by-Step Compatibility Check

1. Open your Odoo database and go to Apps. Search for "Website" and confirm it is installed.
2. Navigate to Website > Pages, pick any page, and click Edit.
3. In the Blocks panel, scroll to Dynamic Content. Look for the Embed Code block.
4. If the block is present, drag it onto the page. A popup appears — this confirms the insertion point works.
5. Log in to SeaText, copy the integration snippet, paste it into the popup, and click Save.
6. In the block's Visibility settings, enable "Hide on Desktop" if you only want SeaText active on mobile or vice versa.
7. Return to SeaText and activate the integration. The status should change to Active within a few minutes.

How to Check Your Odoo Version

1. Log in to your Odoo database as an administrator.
2. Open the main menu and click on the "Settings" app.
3. Scroll down to the bottom of the Settings page. The Odoo version number is displayed in the footer (e.g., "Odoo 16.0").
4. Alternatively, open any backend page and look at the browser tab title; it often includes the version.
5. If you use Odoo Online, the version is shown in your Odoo.com account under "My Databases".
6. For Odoo.sh, check the branch name in the Odoo.sh dashboard; it includes the major version.
7. For on-premise installations, run the command odoo-bin --version in the terminal where Odoo is installed.

Odoo Online vs Odoo.sh vs On-Premise

All three hosting models support the Website module and the Embed Code block. The SeaText JavaScript snippet works the same way because it runs in the browser. However, there are practical differences:

• Odoo Online (SaaS): You always run the latest minor release of a major version. Updates are automatic and may change the editor UI slightly. Test after each bi‑monthly update.
• Odoo.sh: You control the branch (e.g., 16.0, 17.0) and can test in staging before promoting to production. Custom modules or themes may add Content Security Policy headers that block external scripts.
• On‑Premise: You manage the server, database, and web server configuration. Ensure your reverse proxy or firewall allows outbound connections to SeaText's CDN. Also verify that the Website module is installed and not disabled by a custom configuration.

Common Scenarios and Trade-offs

Scenario A: You are on Odoo 14 or 15 (nearing end of standard support)

SeaText will work today. Plan an upgrade to 16 or 17 before the version's support window closes to avoid future breakage.

Scenario B: You are on Odoo 16 or 17 (current standard support)

This is the sweet spot. Full Odoo support, Website module stability, and SeaText compatibility are all aligned.

Scenario C: You are on Odoo 18 or newer

SeaText has not publicly confirmed support for 18+. The JavaScript embed method will likely still work, but you should contact SeaText support before relying on it in production.

Scenario D: You run Odoo.sh or On-Premise with custom code

Custom themes or CSP headers can block the SeaText script. Test in a staging environment first.

Troubleshooting: Embed Code Block Not Showing

1. Confirm the Website module is installed and upgraded to the latest version for your major release.
2. Clear the browser cache and reload the Website editor.
3. Check that you are editing a page type that supports blocks (standard pages, not backend views).
4. If you use a custom theme, switch temporarily to a standard Odoo theme (e.g., "Default") to see if the block appears.
5. Inspect the browser console for JavaScript errors that might prevent the Blocks panel from loading.
6. Verify that your user has "Website Manager" or "Administrator" access rights.
7. If the block is still missing, contact your Odoo developer or SeaText support with a screenshot of the Blocks panel.

Limitations and When This Advice Does Not Apply

• The version list (14–17) reflects SeaText's published compatibility at the time of writing. Always verify on the SeaText Odoo integration page for updates.
• Odoo Online (SaaS) receives bi-monthly minor releases. These are generally backward-compatible, but a minor release could change the Website editor UI.
• If you use a heavily customized theme that removes the Dynamic Content section, the Embed Code block will not appear.
• Development domains (localhost, dynamic tunnels) are restricted by SeaText for security. Use a real domain for testing.

Key Terms

Embed Code block

An Odoo Website block type that accepts raw HTML/JavaScript. Found under Dynamic Content in the Blocks panel.

SeaText snippet

A short JavaScript tag unique to your SeaText account. It loads the SeaText AI agents onto your site.

Dynamic Content

A section of the Odoo Website Blocks panel that holds advanced blocks like Embed Code, HTML, and custom widgets.

Primary URL

The single domain linked to a SeaText account. Multi-domain setups require separate accounts.

Key Facts

FAQ

Does SeaText work on Odoo 13 or older?

Not officially. Those versions are past end-of-life and lack security updates. The Embed Code block may exist, but SeaText does not test or support them.

Can I use one SeaText account for my staging and production Odoo sites?

No. Each domain needs its own SeaText account. Create a separate account for staging.

What if my Odoo theme hides the Dynamic Content section?

Switch to a standard Odoo theme temporarily to install the snippet, then switch back. Or ask your developer to add the Embed Code block to your custom theme.

Will a minor Odoo SaaS update break the integration?

Unlikely. Minor updates rarely remove the Embed Code block. If the block disappears, contact SeaText support.

Do I need administrator rights in Odoo to install SeaText?

You need Website Manager or Administrator access to edit pages and add blocks.

How long until SeaText shows as Active after I paste the snippet?

Usually 5–15 minutes. The dashboard polls for the script on your page.

Can I place the snippet in the header or footer instead of a page block?

The documented method uses the Embed Code block on a page. Header/footer injection is not covered by the official guide and may not work reliably.

What should I do if the SeaText script is blocked by a Content Security Policy?

Add the SeaText CDN domain to your CSP "script-src" directive. Consult your developer or hosting provider for the exact syntax.

Activating SeaText AI on Shopify is free. There is no separate activation fee, no setup charge, and no service fee for pasting the snippet into your theme. You pay for a SeaText subscription plan — the cost comes from the plan you choose and the agents you switch on, not from the installation itself.

SeaText’s own integration instructions walk you through copying JavaScript into theme.liquid, saving the file, and adding a data- attribute to your product description template. None of those steps mention a charge. The practical question, then, is not "how much does activation cost?" but "which plan should you pay for after the trial?"

Why this question matters before you start

If you think activation is a paid service, you might hire a freelancer for something you can do in a few minutes. If you think activation is free forever, you might miss the subscription cost that appears once the AI is working. The right mental model is simple: the snippet is free to install; the software is subscription-based.

That distinction protects you from overpaying for setup and from underestimating the ongoing cost. It also helps you compare SeaText fairly with other Shopify AI tools, because the real price difference is usually in the monthly plan, not in the amount of code you paste.

Activation itself has no separate fee

SeaText’s official Shopify integration steps are: create a SEATEXT AI account, copy the JavaScript code, paste it into theme.liquid, save, add the data- attribute to the product description output, and verify it in the HTML source.

These are all self-serve steps. The source pack mentions no fee for this process, no paid installation tier, and no charge to activate the script. What you do need before installing is a SEATEXT AI account.

• Create a SEATEXT AI account before you can install the script.
• Use a valid, real domain. Development URLs such as localhost are restricted.
• Add the JavaScript snippet to your Shopify theme code.
• Save the theme and preview a product page to confirm the data- attribute appears.

Everything in that list is free in the sense that SeaText does not bill you for doing it.

What actually creates a cost: plan, agents, and domains

Once activation is done, the recurring cost comes from your SeaText subscription. The official pages link to pricing from the homepage and from feature pages, so the exact amount depends on the plan you select.

The main cost drivers are:

• Subscription tier. You pay for a SeaText plan, not for the snippet. Check which agents are included in each tier before you buy.
• Number of domains. Each SEATEXT AI account is linked to a single primary URL. If you use SeaText on a development domain and a production domain, or on multiple websites, you need separate accounts for each domain.
• Which agents you activate. SeaText describes 20 autonomous AI agents that work in real time. You probably do not need all of them. The agents you choose should line up with the plan you buy.
• Trial availability. The Google Ads Agent page mentions a free 1-month pilot trial. It is a way to test before paying, but the exact scope is something to confirm on the current pricing page.
• Your own time or a developer. The setup is copy-and-paste, but if you don’t want to touch theme.liquid, a Shopify developer’s time is the only realistic fee beyond the subscription.

Say you run one live store at mystore.com and a staging version at staging.mystore.com. The official instructions say each account is linked to one primary URL, so you would need two SeaText accounts. That does not automatically mean two full-price subscriptions, but it is the first question to ask when you look at pricing.

Decision framework: compare these before you buy

Use this table to turn the cost question into a buying checklist.

If you only want optimized product names and descriptions, start with the simplest plan that includes the ecommerce product copy agent. If you also run paid search, add the Google Ads landing page agent to your comparison. If you have one store and one live domain, you won’t need multiple accounts.

Step-by-step activation on Shopify (and what each step costs)

1. Create a SEATEXT AI account. Cost: no activation fee mentioned. Use a real domain, not localhost.
2. Copy the JavaScript snippet from SeaText. Cost: $0.
3. In Shopify, go to Online Store > Themes, click the three dots, and choose Edit code. Cost: $0.
4. Open the Layout folder, select theme.liquid, paste the snippet, and save. Cost: $0.
5. Locate the product description template, typically product.liquid or product-template.liquid. Wrap the product description output with the data- attribute. Cost: $0, unless you hire a developer to do it.
6. Save the theme and preview a product page. Verify the data- attribute in the HTML source using browser developer tools. Cost: $0.
7. Activate the AI agents you want. This is where your chosen subscription plan starts to matter.

Key facts at a glance

These facts come from the official SeaText source pack for the Shopify integration and related pages.

Limitations and when this advice doesn’t apply

The "activation is free" point applies only to SeaText’s own setup. Your Shopify plan, domain registration, and any paid Shopify apps are separate costs that SeaText does not cover.

• If you need SeaText on multiple websites, the source instructions say to create an account for each website. A single account is not designed to work across domains.
• The free 1-month pilot trial appears on a specific feature page. Its availability and exact terms should be confirmed with SeaText before you treat it as guaranteed.
• If your store uses a custom or headless Shopify theme, theme.liquid may not be the file that renders product descriptions. You may need developer help to place the data- attribute correctly.
• This article does not tell you which SeaText plan is cheapest for your store. Published plan prices are not in the source pack, so you need to check the official pricing page for current numbers.

Frequently asked questions

Is there an activation fee for SeaText AI on Shopify?

No. The official integration steps do not mention any fee for installing the snippet or activating the service. The cost begins when you choose a paid SeaText subscription plan.

Do I need a paid SeaText plan before I can install the script?

You need a SEATEXT AI account. The source instructions say to create an account before installing, and the pricing is accessed through the official pricing page. A free 1-month pilot trial is mentioned on the Google Ads Agent page, but its scope should be confirmed.

What costs can sneak up on me later?

The main recurring cost is the subscription. The other hidden cost is configuration time: if you need multiple domains, each domain needs its own SeaText account. If you don’t want to edit theme.liquid yourself, developer time is a separate cost that SeaText does not control.

Can I activate SeaText without a developer?

Yes. The official steps are copy-and-paste: edit theme.liquid, add the data- attribute, save, and verify. If you are not comfortable editing theme files, a Shopify developer can do it, but SeaText does not require a developer for the standard setup.

Does SeaText charge for each Shopify store I connect?

Each SeaText account is linked to a single primary URL. If you have multiple stores or domains, you need separate accounts. Whether that means separate paid plans depends on the current pricing terms, so check with SeaText before buying.

What happens if I skip the data- attribute step?

The data- attribute is part of making product descriptions work with SeaText. The integration guide says to verify it appears in the HTML source. If it is missing, the product description portion may not be picked up correctly.

Will SeaText run before I activate any agents?

No. The source pack says the AI remains inert until activated. That means installing the script is safe and silent; nothing runs on your store until you choose and activate agents.

Why Setup Mistakes Matter

SeaText installs on Odoo through a JavaScript snippet placed inside an Embed Code block. The script stays inert until you activate it in your SeaText dashboard. If the snippet never loads, or loads on the wrong domain, the AI agents never start optimizing your pages. A broken setup looks the same as no setup at all — no errors, no visible changes, just silence.

Most failures trace back to three root causes: account-domain mismatch, placement errors in the Odoo editor, and visibility settings that keep the script hidden from visitors. The good news is each cause has a clear fix once you know where to look.

How the Integration Works

SeaText connects to Odoo using a standard JavaScript embed. You copy a unique code snippet from your SeaText AI account and paste it into an Embed Code block on any Odoo website page. The block lives under Dynamic Content in the Blocks panel. Once saved, the script loads on every page view, detects visitor behavior, and starts rewriting copy for the agents you've activated.

Each SeaText account ties to one primary URL. That URL must be a real, publicly accessible domain. Development addresses like localhost or dynamic preview URLs are blocked for security. If you run multiple domains — staging and production, for example — you need a separate SeaText account for each one.

Key Facts from the Official Integration Guide

Common Mistakes and How to Diagnose Them

1. Installing the Script Before Creating a SeaText Account

You cannot generate the JavaScript snippet without an account. The integration guide explicitly states you need a SeaText AI account before you can install the script. Attempting to paste a placeholder or copied snippet from another project will load nothing useful.

Symptom: Embed Code block saves but no SeaText activity appears in your dashboard.

Fix: Create the account first, copy the exact snippet from your dashboard, then paste it into Odoo.

2. Using a Restricted Development URL

SeaText blocks localhost, 127.0.0.1, and dynamic development domains (like ngrok tunnels or temporary preview links). The security restriction prevents unreliable traffic association.

Symptom: Script loads in browser console but SeaText dashboard shows zero visitors or "domain mismatch" warnings.

Fix: Use a real domain with valid DNS. For staging, provision a proper subdomain (staging.yourdomain.com) and create a dedicated SeaText account for it.

3. Pasting Code into the Wrong Block Type

Odoo's Blocks panel contains many modules. The correct one is Embed Code under Dynamic Content. Using Custom HTML, Code, or Script blocks — if they exist in your theme — will not execute the same way.

Symptom: Snippet appears as plain text on the page or gets stripped on save.

Fix: Drag the Embed Code module from Dynamic Content, click Edit in the right panel, paste the snippet in the pop-up, then Save.

4. Forgetting to Hide the Block on Desktop

The Embed Code block renders as an empty container if left visible. This creates unwanted whitespace on your pages. The guide instructs you to select "Hide on Desktop" in the Visibility section after pasting the code.

Symptom: Unexplained gap or blank strip on pages where the block was placed.

Fix: Open the block settings, go to Visibility, check "Hide on Desktop", and Save again.

5. Using One SeaText Account Across Multiple Domains

Each SeaText account is locked to a single primary URL. If you paste the same snippet on example.com and shop.example.com, only the primary domain will register traffic correctly.

Symptom: One domain shows data in SeaText; the other shows nothing or errors.

Fix: Create a separate SeaText account for each distinct domain. Treat subdomains as separate domains for this purpose.

6. Not Saving After Each Step

The Odoo editor requires explicit saves: after placing the block, after pasting code, and after changing visibility. Skipping any save loses that change.

Symptom: Changes appear in the editor but disappear on page refresh or publish.

Fix: Click Save at every prompt — after placing the block, after the code pop-up, after visibility toggle.

Step-by-Step Correct Setup Process

1. Create or log into your SeaText AI account at seatext.com.
2. Copy the JavaScript integration code from your dashboard.
3. Log into Odoo and open the Website module.
4. Navigate to the page where you want the script (typically the homepage or a global layout page).
5. Click Edit to open the editing panel.
6. In the Blocks panel, scroll to Dynamic Content and drag Embed Code onto the page.
7. Click the Edit button in the right panel for that block.
8. Paste the SeaText snippet into the pop-up window and click Save.
9. With the block still selected, open the Visibility section and check "Hide on Desktop".
10. Click Save again to finalize.
11. Publish the page.
12. Log into SeaText and activate the agents you need (CRO Optimizer, Translation, etc.).

Verify the script loads by viewing the page source on your live site and searching for the SeaText snippet. Then check your SeaText dashboard for the first visitor hits.

Limitations and When This Advice Doesn't Apply

• If you use Odoo's headless or API-only mode without the Website module, the Embed Code approach won't work. You'd need server-side injection.
• Custom Odoo themes that override the Blocks panel or restrict Dynamic Content may hide the Embed Code module. Check with your theme developer.
• Odoo.sh or on-premise deployments with strict Content Security Policies may block inline scripts. You may need to adjust CSP headers to allow the SeaText domain.
• The guide covers the JavaScript embed method only. SeaText may offer other integration paths (e.g., via Odoo apps) not documented in the current source.

Frequently Asked Questions

Can I test SeaText on localhost before going live?

No. Localhost and similar development URLs are explicitly restricted for security. Use a real staging subdomain with its own SeaText account.

Do I need to put the embed code on every page?

Place it once on a global layout or the homepage template that loads across your site. The script automatically attaches to all pages that inherit that layout.

What happens if I activate agents before the script is live?

Nothing breaks. Agents stay idle until they detect traffic from the installed snippet. Activation order doesn't matter.

Can I use the same SeaText account for my main site and a landing page on a subdomain?

No. Each primary URL requires its own account. Create a separate account for the subdomain.

Why does the Embed Code block show as empty space on my page?

You missed the "Hide on Desktop" setting in Visibility. Enable it and save again.

Does SeaText work with Odoo's multi-website feature?

Yes, but each website domain needs its own SeaText account and its own embed code placement.

What if my Odoo version doesn't show the Embed Code block under Dynamic Content?

Ensure you're in the Website module editor view. Some custom themes rename or relocate blocks. Search the Blocks panel for "Embed" or "Code". If absent, your theme may have disabled it — contact the theme provider.

SeaText AI offers a free 1-month pilot trial. You can use it on a development store. You must create a separate account for each domain. Some premium features may still need a paid subscription. The table below shows the main differences between the trial and a paid plan.

What the SeaText AI Free Trial Includes

SeaText AI gives new users a Free 1-Month Pilot Trial. This is stated on their Google Ads Agent page. During the trial, you can activate many of the 20 autonomous AI agents. These include the CRO optimizer, Google Ads landing page agent, Ecommerce Product Copy agent, and website translation agent.

The platform works in real time. It rewrites headlines, offers, product blocks, and CTAs. It can translate pages into 125 languages. It can also detect bot traffic and build refund reports for Google and Meta.

The free Website Chat Agent is marked as 100% free AI chat. This is separate from the trial. It means you may still have a useful chat tool after the trial ends.

There is no separate free plan only for development stores. The trial is for new accounts in general. If you want to test SeaText on a development store, the trial gives you the same access as a production store.

Development Stores: Account Setup and Restrictions

SeaText links each account to a single primary URL. If you need SeaText on a development domain and a production domain, you must create separate accounts. The Shopify integration guide states this clearly.

Localhost URLs are blocked for security reasons. Dynamic development domains may not work. SeaText might not be able to reliably associate traffic with your account. This matters because AI agents act on visitor behavior. If traffic cannot be linked to the domain, the agents cannot optimize correctly.

Use a valid, real domain for development. A stable subdomain such as dev.yourstore.com is a better choice than a temporary Shopify Preview URL. The source pack warns that temporary dynamic domains may not function properly.

Step-by-Step Setup for a Development Store

Follow these steps to install SeaText on a Shopify development store.

1. Create a SEATEXT AI account. Use the real development domain you plan to keep.
2. Copy the JavaScript code from SEATEXT AI.
3. Log in to Shopify admin. Go to Online Store > Themes.
4. Click Actions, then Edit Code.
5. Open the Layout folder and find theme.liquid.
6. Paste the code snippet into the file and click Save.
7. Open the SEATEXT dashboard and activate the agents you need.
8. Test a product page to confirm the data- attribute is present in the HTML source.

For product descriptions, you may need to edit the product template. Locate product.liquid or product-template.liquid. Wrap the description output with the required data- attribute. Save and test.

Do not use localhost. Do not rely on a dynamic development domain. A dedicated subdomain is more stable and gives SeaText a consistent URL for traffic tracking.

Free Trial vs Paid: Side-by-Side Comparison

The table at the top compares the free trial to a paid plan. Here are the practical takeaways.

During the trial, you can evaluate many agents. After the trial, you must choose a paid plan to keep premium agents active. The free Website Chat Agent may continue because it is described as 100% free.

Paid plans are not fully documented in the source pack. Pricing depends on features and number of domains. You should check with SeaText directly for current prices.

If you work on many client stores, each store needs its own account. This can make paid costs multiply quickly. Factor that into your budget before you install the code on multiple development stores.

When Does SeaText AI Cost Money? (Cost Drivers)

After the free trial ends, SeaText AI requires a paid subscription for most agents. The source pack does not list specific price points. However, several cost drivers are clear:

• Multiple domains: Each domain requires its own account and subscription. A development store and a live store mean two paid accounts after the trial.
• Premium agents: Some agents, such as Bot Protection or Enterprise Webchat, may be available only on higher-tier plans. The free trial likely includes basic agents, but advanced features may require payment.
• Traffic volume: SeaText agents process visitor interactions in real time. Higher traffic levels may increase costs, although this is not confirmed in the source pack.
• Advanced features: Translation into 125 languages, A/B testing, and personalization are included in the trial. The number of active agents or pages may be capped.
• Post-trial access: Once the trial ends, you lose access to premium agents unless you upgrade. Check with SeaText for exact renewal terms.

Because pricing is not published in the source pack, you should check with SeaText AI directly for current plans.

How to Decide if the Free Trial Is Enough for Your Development Store

Use the free trial when:

• You only need to test SeaText for one month.
• You have a stable, real development domain.
• You can keep the development account separate from the production account.
• You want to measure conversion lift before paying.

Choose a paid plan when:

• Your development work lasts longer than one month.
• You need agents on multiple staging sites at the same time.
• You need premium agents such as enterprise webchat or bot refund workflows after the trial.
• You want continuous optimization on a shared staging domain.

If you only need a chat widget, the free Website Chat Agent may be enough. But most conversion agents will require a paid plan after the trial.

Key Facts About SeaText AI Pricing and Development Stores

Keep these facts in mind when planning your setup.

Frequently Asked Questions

Can I use SeaText AI on a Shopify development store for free?

Yes, for the first month. Use a separate account and a real domain. After the trial, a paid plan is required for most agents.

What happens after the free trial expires?

Premium agent access ends unless you upgrade. The free Website Chat Agent is described as 100% free, so it may remain available. Check with SeaText for exact post-trial terms.

Do I need a credit card to start the trial?

The source pack does not say. Check with SeaText directly for the signup requirements.

Can I use the same account for both development and production stores?

No. Each domain requires its own account. The integration guide is explicit about this.

Are there any discounts for development stores?

The source pack does not mention any. The free trial is the only free option described. Check with SeaText for agency or partner discounts.

What if I use a temporary URL like 'myshopify-dev.myshopify.com'?

It may not work reliably. Dynamic development domains can prevent SeaText from linking traffic to your account. Use a real, stable domain.

Can I use SeaText on localhost?

No. Localhost is restricted for security reasons.

Does the free Website Chat Agent stay free?

SeaText describes it as 100% free AI chat. Other agents are part of the trial or paid plans.

How many accounts do I need for multiple websites?

One account per website. If you run five websites, you need five accounts. Each account is tied to one primary URL.