Why Your SEATEXT Script Isn't Working on One Domain (and How to Fix It)
The most common causes are script placement errors, caching plugins blocking execution, domain verification issues, or conflicting JavaScript on that specific domain. Each domain also needs its own SEATEXT account linked to that exact...
If your SEATEXT script works on most domains but not one, the cause is almost always one of four things: the script isn't actually installed on that domain, a caching plugin is blocking it, the domain isn't verified in your SEATEXT account, or another script is conflicting with it. The most common reason, though, is that each domain needs its own SEATEXT account linked to that exact URL.
The Short Answer: Why One Domain Fails
SEATEXT links each account to a single primary URL. If you're using the same script code on multiple domains without creating a separate account for each, the script won't associate traffic correctly with the second domain. The script may load, but the AI won't activate because it can't match the domain to your account.
Even if you have separate accounts, the script might still fail due to placement errors, caching, or JavaScript conflicts. The diagnostic sequence below walks you through the most likely culprits in order.
Why SEATEXT Requires One Account Per Domain
SEATEXT's architecture ties an AI instance to a single primary URL. This design ensures that traffic data, variant testing, and conversion attribution stay isolated per domain. When you install the script, it sends a domain identifier to SEATEXT's servers. If that identifier doesn't match the account's registered URL, the AI remains inert. This prevents cross-domain data leakage and keeps reporting accurate. The source pack states: "Each SEATEXT AI account is linked to a single primary URL." Therefore, you must create a new account for each domain you want to optimize.
The Most Common Causes
- Script not installed on that domain – The code may be missing from the page's header or footer, or it was pasted into the wrong section.
- Caching plugin blocking execution – Some caching plugins delay or strip JavaScript, preventing the script from running.
- Domain not verified in your SEATEXT account – Each domain needs its own account, and the domain must be confirmed before the AI activates.
- Conflicting JavaScript – Another script on the page might throw an error that stops SEATEXT from loading.
- Development URL restrictions – Localhost or dynamic development domains are restricted for security reasons.
How to Diagnose: A Step-by-Step Sequence
Follow these steps in order. Stop when you find the issue.
- Check if the script is on the page. Open the problematic domain in a browser, right-click and select "View Page Source," then search for "seatext" or the script ID. If it's not there, the script wasn't installed on that domain.
- Verify the domain in your SEATEXT account. Log in to SEATEXT and look for the website name next to the SEATEXT logo at the top of the page. If it's not there, the domain isn't linked to your account.
- Confirm you have a separate account for this domain. Each domain requires its own SEATEXT account. If you're reusing the same account, create a new one for the problematic domain.
- Check for caching plugins. Temporarily disable caching on that domain and refresh the page. If the script starts working, the cache was the problem.
- Look for JavaScript errors. Open the browser's developer console (F12) and check for errors. A conflicting script might be stopping SEATEXT from loading.
- Wait and refresh. After fixing any issues, visit or refresh the page several times and stay for at least 40 seconds. Then wait five minutes and check if the domain appears in your SEATEXT account.
What to Check on the Domain Itself
If the script is present but not working, inspect the placement. SEATEXT provides integration guides for WordPress, WooCommerce, BigCommerce, HubSpot, and Optimizely. Each platform has a specific location for the script:
| Platform | Placement Method | Key Detail |
|---|---|---|
| WordPress / WooCommerce | Use "Insert Headers and Footers" plugin | Paste code into "Scripts In Header" section |
| BigCommerce | Script Manager → Create a Script | Add via Channel Manager → Storefronts |
| HubSpot | Settings → General → Advanced → Footer HTML | Publish changes with orange button |
| Optimizely | Follow step-by-step integration instructions | Copy JavaScript from SEATEXT account |
Make sure the script is on every page you want to optimize, not just the homepage. Also, check that the domain is a real, valid domain—not localhost or a dynamic development URL.
When the Problem Is Your Hosting or Platform
Some hosting providers, like WPEngine, require a special plugin to add custom JavaScript. If you're on WPEngine, install the WP Engine plugin that enables custom JS. Without it, the script may not load.
If you're using a content delivery network (CDN) or a firewall, it might block the script. Temporarily disable these to test. Also, ensure the script is not being minified or altered by a build process. The source pack notes: "If you are using WPEngine please download the WP Engine plugin that enables you to add custom JavaScript code to your pages."
Common Platform-Specific Pitfalls
- WordPress: Forgetting to activate the "Insert Headers and Footers" plugin after installation.
- WooCommerce: Placing the script in the footer instead of the header, which delays loading.
- BigCommerce: Not selecting the correct storefront in Channel Manager before creating the script.
- HubSpot: Pasting the code into the wrong field (e.g., Header HTML instead of Footer HTML).
- Optimizely: Skipping the step-by-step integration guide, leading to missing dependencies.
What to Do If Nothing Works
If you've gone through the diagnostic sequence and the domain still isn't connecting, contact SEATEXT support. The source pack says: "If you do not see it at the top of the page after 10 minutes, please contact our support team immediately." Support can help you verify the installation and check for platform-specific issues.
Key Facts About SEATEXT Multi-Domain Setup
| Fact | Detail |
|---|---|
| Account per domain | Each SEATEXT AI account is linked to a single primary URL. |
| Development URLs | Localhost and dynamic development domains are restricted for security reasons. |
| Activation | Visit or refresh your website several times and stay on the page for at least 40 seconds. |
| Confirmation | Wait at least five minutes for your website name to appear next to the SEATEXT logo. |
| Support | If the name doesn't appear after 10 minutes, contact support immediately. |
Limitations and Exceptions
The advice above assumes you're using a standard, publicly accessible domain. If you're testing on a staging site or a domain with a firewall, the script may not activate. Also, if you have multiple subdomains, each one may need its own account. The source pack specifically mentions that dynamic development domains may not function properly because SEATEXT can't reliably associate traffic with your account.
Another exception: if you're using a single-page application (SPA) like React, the script may need special handling. The source pack mentions "For SPAs (React and etc)" in the FAQ, so check the documentation for SPA-specific instructions.
Frequently Asked Questions
Why does the script work on one domain but not another?
Most likely because each domain needs its own SEATEXT account. If you're using the same account for multiple domains, the script won't associate traffic correctly with the second domain.
How long does it take for the domain to appear in my SEATEXT account?
After installing the script, visit or refresh the page several times and stay for at least 40 seconds. Then wait at least five minutes. If it doesn't appear after 10 minutes, contact support.
Can I use the same script code on multiple domains?
No. Each domain requires a separate SEATEXT account, and each account has its own script code. You must copy the code from each account separately.
What if I'm using a development domain like localhost?
Development URLs are restricted for security reasons. Use a valid, real domain. Dynamic development domains may not work because SEATEXT can't reliably associate traffic with your account.
Does a caching plugin really block the script?
Yes. Some caching plugins delay or strip JavaScript. Temporarily disable caching on the problematic domain to test.
What should I do if I've tried everything and it still doesn't work?
Contact SEATEXT support immediately. They can help you verify the installation and troubleshoot platform-specific issues.
Can I use SEATEXT on a single-page application (React, Vue, etc.)?
Yes, but SPAs require special handling. Check the SEATEXT documentation for "For SPAs (React and etc)" to get the correct integration steps.
What if I have multiple subdomains?
Each subdomain may need its own SEATEXT account. Treat each subdomain as a separate primary URL.
Why does the AI remain inert after installation?
The AI stays inert until activated by real traffic. You must visit the page, stay for 40 seconds, and wait five minutes for the domain to register.
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.