Can I Use SeaText AI on a Shopify Development Store?
Yes, you can install SeaText AI on a Shopify development store, but you must use a valid, stable domain, not localhost or a dynamic dev URL. Create a separate SeaText account for each domain....
Yes, with important restrictions
The short answer is yes. SeaText AI works on Shopify development stores. You must follow a few rules. Use a real, stable domain. Localhost and dynamic development domains are restricted. Each SeaText account is linked to one primary URL. If your dev store and live store use different domains, create a separate account for each.
Here is how a development store compares to a live store.
| Factor | Development store | Live store |
|---|---|---|
| Main purpose | Test theme changes, code, and agent setup before launch | Run the store with real customers and revenue |
| Domain requirement | Real, stable domain such as dev.yourstore.com or yourstore.myshopify.com | Real production domain such as yourstore.com |
| SeaText account | Separate account for the dev domain | Separate account for the production domain |
| Traffic and data | Usually low or no traffic; agents have little data to analyze | Real visitors and ad campaigns give agents usable data |
| Best for | Developers, QA testers, theme designers, staging demos | Store owners and marketing teams who want conversion growth |
A development store fits anyone who needs a safe test environment. A live store fits anyone who wants SeaText to improve real conversion rates. If you only need to test code, use a dev store. If you need revenue results, use a live store.
What the source pack says about development stores
SeaText’s integration page says:
“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.”
That quote is the basis for every rule in this article. SeaText links each account to a primary URL. The script on your site reports back to that account. If the URL is local or changes often, the report has no stable home.
Stable domains are easy to identify. Examples include dev.yourstore.com and yourstore.myshopify.com. Unstable domains include localhost addresses, 127.0.0.1, and temporary URLs from tunnel services or preview deploys. These unstable URLs change. When they change, SeaText cannot connect the traffic to your account.
Key facts about using SeaText on a dev store
| Factor | Details |
|---|---|
| Allowed domain types | Real domain, such as yourstore.myshopify.com or dev.yourstore.com. Localhost and dynamic dev domains are restricted. |
| Account per domain | Each SeaText AI account is linked to one primary URL. You need a separate account for dev and production. |
| Installation method | Add the JavaScript snippet to theme.liquid in your Shopify theme code. Works with any Shopify theme. |
| Feature limitations | Some agents, such as CRO and Google Ads, may have no data to work with in a dev store with no traffic. Agents stay inert until activated. |
| Security | The script is secure and does not affect site content until you activate agents. Installation is safe for dev environments. |
These facts affect how you plan your dev work. If you want to test the script, use a stable domain. If you want to test the agents, you also need real visitor behavior.
How to install SeaText on a Shopify development store
Follow these steps after you have a real domain assigned to your dev store.
- Create a SeaText AI account for the dev domain. If you already have a production account, create a new one for the dev domain.
- In Shopify, go to Online Store > Domains and make sure the dev store has a real domain. Check Shopify’s current documentation for the exact steps.
- In Shopify admin, go to Online Store > Themes.
- Click Actions > Edit Code for your active theme.
- In the Layout folder, open theme.liquid.
- Find the closing
</body>tag. - Paste the SeaText AI JavaScript code just before the closing body tag.
- Click Save.
- Open the dev store in a browser and inspect the page. Use browser developer tools to confirm the snippet loads without errors.
Here is a simplified version of where the code goes:
<!-- theme.liquid -->
<body>
...
<!-- Paste SeaText AI code before the closing body tag -->
<script>
// Your SeaText AI JavaScript code goes here.
</script>
</body>Replace the comment and script placeholder with the exact code from your SeaText account. The code from the dashboard is the version you should use.
If you also use product description tags, open the product template. This file is usually named product.liquid or product-template.liquid. Find the product description output and wrap it with the data attribute from your SeaText dashboard. Then preview a product page and inspect the HTML source to verify the attribute is present.
Important limitations you should know
Development URLs are restricted
Localhost is a loopback address. It points to your own machine, not a public site. SeaText restricts localhost for security reasons. 127.0.0.1 is the same. Even if you can see the page, SeaText cannot treat that URL as a valid storefront.
Do not use http://localhost:3000 or http://127.0.0.1:8080. These addresses only exist on your computer. SeaText cannot verify them, and the script will not work reliably.
Dynamic domains may break
Some development tools create a new URL on every preview. For example, ngrok gives a random subdomain. Vercel and Netlify can create per-deploy URLs. These work for a human, but the domain changes.
SeaText uses the primary URL to associate visits. A changing URL makes that association unreliable. If you need to test on a hosted preview, keep a fixed staging domain.
Examples of unstable domains:
http://localhost:3000https://random-name.ngrok.io- Preview URLs that change after every code push
Examples of stable domains:
https://yourstore.myshopify.comhttps://dev.yourstore.comhttps://staging.yourstore.com
One URL per account
Your SeaText account has one primary URL. Reports, agents, and settings are tied to that URL. If you use the same account on dev and live stores, the wrong URL gets the data.
Create one account per domain. This is not a workaround. It is the intended design. A separate account keeps dev data and production data clean.
No traffic, no results
Most SeaText agents are behavior driven. The CRO optimizer watches reading patterns. The Google Ads agent reacts to paid clicks. The bot protection agent checks paid sessions.
A dev store with no visitors gives these agents nothing to analyze. The script may load, but no changes will appear. Do not expect conversion optimization in an empty store. If you want to see how the script fires, use a stable domain and invite a few human testers. Still, that is not enough data for real optimization.
Common mistakes to avoid
Installing on localhost
Developers often test on localhost because it is fast. But SeaText restricts localhost. The fix is to deploy to a real domain or use a Shopify development store with a stable URL.
Using one account on two domains
One SeaText account is tied to one primary URL. If you reuse a production account on a dev store, you may pollute the live store’s data. Use a separate account for every domain.
Using a temporary tunnel URL
A tunnel URL may work for a browser demo, but it is not stable. When the tunnel stops, the domain dies. Use a real subdomain for testing.
Forgetting to verify the script
Pasting the code is not enough. Open browser developer tools. Look for errors. Confirm the script loads on the dev domain. Check the Network tab or view page source.
Expecting live results from an empty dev store
SeaText agents are inert until activated. Even when activated, they need visitor behavior. An empty dev store produces no optimization data. Understand this before you install.
Frequently asked questions
Can I use the same SeaText account on my dev store and live store?
No. Each SeaText AI account is tied to a single primary URL. Use a separate account for each domain.
What if my dev store is on a subdomain like dev.mystore.com?
That works. Subdomains are real domains. Create a separate SeaText account for that subdomain.
Will SeaText affect my Shopify theme or break my store during development?
No. The script is inert until you activate agents. It only adds a JavaScript tag. It will not change your theme code before activation.
Do I need to pay for a separate account on a dev store?
You need a separate account. You may be able to use the same plan or a free trial. Check the pricing page for current options.
Can I test SeaText agents on a development store with no traffic?
You can install the script and activate agents, but agents need visitor behavior to optimize. Without traffic, you will not see data or changes. Use a small group of real testers if you want to watch the script fire, but do not expect conversion results.
How do I set up a real domain on a Shopify dev store?
In Shopify, go to Online Store > Domains. Connect a domain you already own or buy one through Shopify. For development, use a subdomain such as dev.yourstore.com. Shopify’s exact menu path can change, so check the vendor’s current documentation.
What if I accidentally use a localhost URL?
Remove the SeaText code from the local version. Create a fresh SeaText account for the real domain you plan to use. Do not reuse the localhost account. Then install the code on the real domain and verify it loads.
What if I need to move my dev store to a new domain later?
Create a new SeaText account for the new domain. The old account remains tied to the original dev URL. There is no primary URL change after account creation.
Why this matters and what changes if you ignore it
If you ignore the domain rule, SeaText cannot link the script to your account. If you use localhost, the script will not verify. If you use a dynamic URL, your reporting will be patchy. If you reuse a production account, you may pollute the live store’s data.
These problems are avoidable. Use a stable domain. Make a separate account. Verify that the script loads. Then a development store is a safe place to test SeaText before you launch.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Learn more
Visit the website for more information.