How to Test If SeaText AI Is Connected to Your Website
SeaText AI connects after you install its JavaScript snippet, stay on a page for at least 40 seconds, and wait up to five minutes for your site name to appear next to the SeaText...
Quick answer
Install the SeaText JavaScript code on every page, then open your site in a browser and stay on any page for at least 40 seconds. Return to the SeaText dashboard and watch the header next to the SeaText logo. Your website name should appear within five minutes. If it does not appear after ten minutes, the connection has not been established and you need to troubleshoot the installation or contact support.
| Criteria | SeaText | Generic baseline |
|---|---|---|
| Installation ease | Copy‑paste a single SEATEXTCODEINTEGRATION snippet or use the WP Engine plugin. | Often requires custom build steps or multiple files. |
| Connection verification speed | Dashboard shows site name within 5 min after a 40‑second dwell. | May need manual API calls or longer propagation. |
| Support availability | Live chat and ticket support; response within hours. | Varies widely; some providers only email. |
Prerequisites before you test
- An active SeaText AI account. Each account is linked to a single primary URL.
- The JavaScript snippet copied from your SeaText dashboard (labeled SEATEXTCODEINTEGRATION).
- Access to your site's
<head>or a tag manager so you can paste the snippet on every page you want tracked. - If you host on WP Engine, install the WP Engine plugin that enables custom JavaScript injection before adding the snippet.
Development URLs such as localhost and dynamic preview domains are restricted for security reasons. Use a real, publicly resolvable domain for testing. If you need SeaText on a staging domain and a production domain, create a separate account for each, as the source text states: "Multiple Domains ... each SEATEXT AI account is linked to a single primary URL" (S1).
Step 1: Verify the script loads in the browser
- Open your website in a new incognito window.
- Open the browser developer tools (F12 or right‑click → Inspect) and switch to the Console tab.
- Reload the page. Look for a network request to
seatext.comor a console log that mentions SeaText initialization. - If the request is blocked by a Content Security Policy, ad blocker, or script deferral, adjust the policy or tag‑manager settings so the SeaText script executes before the page finishes loading.
Why this matters: the script is the only way the browser can contact SeaText’s backend. A blocked request means the AI never receives the visitor’s session data, so the dashboard will never show your site name.
Step 2: Satisfy the 40‑second dwell requirement
SeaText activates the AI only after it detects a genuine visit. Stay on any page of your site for at least 40 seconds. Do not close the tab, navigate away, or throttle the tab in the background. This dwell time lets the script perform a handshake with SeaText’s servers, create a session ID, and register the visit. The source text emphasizes this: "Important: Visit or refresh your website several times and stay on your page for at least 40 seconds—this will activate the AI and link it to your account" (S1).
Technical detail: the script sets a timer on page load. After 40 seconds it sends a POST request containing the page URL, a unique visitor token, and the account’s primary domain. The backend validates the domain against the account record and, if it matches, marks the site as "connected".
Step 3: Check the dashboard for the site name
- Log in to your SeaText account.
- Look at the top header next to the SeaText logo.
- Wait up to five minutes. Your website name should appear there, confirming the connection.
If the name appears, the integration is live. You can now proceed to the Main AI Hub to activate agents, configure parameters, or edit variants. The dashboard header is a lightweight health check; it confirms that at least one successful handshake occurred.
Step 4: Trigger a test AI response (optional)
Once the site name shows in the dashboard, go to Main AI Hub → Configuration and enable an agent such as the CRO Optimizer. Visit a page where the agent runs and verify that the page content changes (headline, CTA, or translation) according to the agent's rules. This confirms the AI is not only connected but actively rewriting.
Running a test response also helps you verify that the script fires early enough. If you use a tag manager, set the SeaText tag to fire on Page View – DOM Ready or earlier; otherwise the agent may miss the initial request.
Common reasons the connection fails
- Script not on every page: SeaText must load on each page you want tracked. A single‑page installation will only connect that page. Ensure the snippet is placed in a global header or via a tag manager that fires on all URLs.
- CSP or ad‑blocker blocking the request: Check the Console for
blocked:cspornet::ERR_BLOCKED_BY_CLIENTerrors. Adjust yourContent‑Security‑Policyheader to allowscript-src https://seatext.comand whitelist the domain in ad‑blocker whitelists. - Tag manager firing too late: If the tag fires after
window.onload, the 40‑second timer may start too late, causing the handshake to miss the required window. Set the tag to fire onDOM Readyor use a custom HTML tag placed before other scripts. - Wrong domain in account: Each account accepts only its registered primary URL. A mismatch prevents the handshake. Verify the domain listed in your SeaText dashboard matches the URL you are testing.
- Using a restricted development URL:
localhost,127.0.0.1, or dynamic preview domains will not connect. The source text notes these are "restricted for security reasons" (S1). - Server‑side rendering stripping the script: Some SSR frameworks inject scripts only on the client side. If the script never reaches the browser, the connection fails. Use a client‑side injection method or disable SSR for the snippet.
- Edge caching serving a stale version: CDNs may cache an older HTML file without the snippet. Purge the cache after adding the script.
Best‑practice recommendations: always test on a clean incognito window, disable any ad‑blockers, and verify the network request in the DevTools Network tab.
Verification checklist
| Check | Expected result | Where to look |
|---|---|---|
| Script loads | Network request to seatext.com returns 200 | DevTools → Network |
| No console errors | No CSP or blocker messages referencing SeaText | DevTools → Console |
| 40‑second dwell completed | Session recorded in backend | Dashboard header (after 5 min) |
| Site name appears in header | Your domain shows next to SeaText logo | SeaText dashboard top bar |
| Agent activates | Page content changes per agent rules | Live page after enabling agent |
When to contact support
If the site name does not appear next to the SeaText logo within ten minutes after you have satisfied the 40‑second dwell on a valid domain with the script loading cleanly, contact SeaText support. The delay usually indicates a platform‑specific installation issue (e.g., server‑side rendering stripping the script, edge caching, or a CSP header you cannot modify). Provide the support team with console logs, network request details, and the exact URL you tested.
Limitations of the connection test
- The dashboard header only confirms that the script has phoned home once. It does not guarantee every page variant or agent is functioning correctly.
- Multiple domains require separate accounts; a single dashboard will not show multiple sites. This is stated in the source: "Each SEATEXT AI account is linked to a single primary URL" (S1).
- Dynamic development domains (e.g., Vercel preview URLs) may never connect reliably because SeaText cannot stably associate traffic with your account.
- The test does not verify translation agents, bot‑protection agents, or other specialized modules. Those require their own functional checks.
- Connection status may be delayed by network latency or CDN propagation, especially on globally distributed sites.
Frequently asked questions
Can I test on localhost?
No. Development URLs such as localhost are restricted for security reasons. Use a real domain or a public staging domain.
Do I need to reinstall the script after changing the primary URL in my account?
Yes. Each account is linked to a single primary URL. If you change the domain, you must update the script source or create a new account for the new domain.
How long does the initial connection take?
Up to five minutes after a 40‑second dwell. If it takes longer than ten minutes, treat it as a failure and troubleshoot.
Will the connection persist across subdomains?
Only if the same script is installed on each subdomain and the primary URL in the account matches the root domain. Subdomains on different accounts need separate installations.
Can I use a tag manager instead of editing the theme?
Yes, provided the tag fires early (DOM Ready) and is not blocked by CSP. Verify in the Console that the script loads without errors.
What if I use WP Engine?
Install the WP Engine plugin that enables custom JavaScript injection, then add the SeaText snippet through that plugin so it loads on every page.
Does the test confirm translations are working?
No. The connection test only proves the script talks to the backend. Enable the Website Translation Agent and visit a page in a target language to verify translations.
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.