What to Do When SeaText Won't Connect to Your Domain

Prerequisites Before You Start Troubleshooting

SeaText ties each account to a single primary URL. You cannot use one account across multiple domains — not even a staging and a production version of the same site. Each domain needs its own SeaText account. Development URLs such as localhost or dynamic preview domains (for example, *.vercel.app or *.netlify.app) are blocked for security reasons and will never connect. Make sure you are working with a real, publicly resolvable domain before you begin.

You also need the JavaScript snippet from your SeaText account page. If you haven't created an account yet, do that first — the script is unique to your account and cannot be reused.

Step-by-Step Diagnostic Sequence

1. Confirm the domain in SeaText matches your live site exactly. Open your SeaText dashboard and check the primary URL listed for the account. It must match the domain visitors use (including www vs. non-www and http vs. https).
2. Paste the snippet in the correct location. On Weebly, go to Website → Edit Site → Settings → SEO → Footer Code and insert the script there. On other platforms, place it just before the closing </body> tag or in the equivalent global footer/code-injection field.
3. Save and publish. The script does nothing until the page is live. A draft or preview mode will not trigger the connection.
4. Visit the published page yourself. Load the URL in a browser, stay on the page for at least 40 seconds, and refresh once or twice. This activity signals SeaText that the domain is active and links the traffic to your account.
5. Wait five to ten minutes. SeaText polls for the connection. Your site name should appear next to the SeaText logo at the top of the dashboard within five minutes. If it's not there after ten minutes, something is blocking the handshake.

Common Connection Failure Points

• Wrong domain in the account. You registered example.com but the site lives at www.example.com (or vice versa). SeaText treats these as different primary URLs.
• Script placed in the wrong spot. Putting the snippet in the header, inside a page-specific block, or inside a CMS widget that only loads on certain pages prevents the global handshake.
• Caching or optimization plugins stripping the script. Some performance plugins defer, minify, or remove third-party scripts. Check the rendered page source (View → Source) and confirm the SeaText snippet appears intact.
• Content Security Policy (CSP) blocking the script. If your server sends a CSP header without script-src allowing SeaText's domain, the browser will refuse to execute it. Check the browser console for CSP errors.
• Using a restricted development URL. As noted above, localhost, 127.0.0.1, and dynamic preview domains are explicitly blocked. You must use a real domain with valid DNS.

Domain Configuration Requirements

SeaText requires a standard, publicly accessible domain with proper DNS resolution. The domain must:

• Resolve to an IP address that serves your website (A or CNAME record).
• Serve content over HTTPS (valid TLS certificate).
• Allow outbound connections from the browser to SeaText's endpoints (no firewall rules blocking the script's network calls).
• Not be behind a password-protected staging area, VPN, or IP allowlist that prevents SeaText's automated checks from reaching the page.

If you manage multiple websites, create a separate SeaText account for each one. The system does not support multi-site accounts.

Verification Steps

After completing the diagnostic sequence, verify the connection in three ways:

1. Dashboard indicator. Your site name appears next to the SeaText logo at the top of the account page.
2. Browser console. Open DevTools → Console on your live page. You should see a SeaText initialization log (no errors).
3. Network tab. Filter for "seatext" or the script's domain. A successful 200 response for the script and subsequent ping/beacon requests confirms the handshake.

If all three check out, the domain is connected. You can now proceed to the Main AI Hub to activate agents.

When to Contact Support

Contact SeaText support if:

• The site name does not appear in the dashboard after 10 minutes of confirmed live traffic.
• The browser console shows script errors you cannot resolve (CSP, CORS, 403/404 on SeaText endpoints).
• You need to change the primary URL for an existing account — this requires support assistance.
• You are migrating a site to a new domain and need the account re-associated.

Include your account email, the exact primary URL configured in SeaText, the live site URL, and a screenshot of the browser console/network tab when you open a ticket.

Limitations and Edge Cases

• One account, one domain. You cannot point a single SeaText account at multiple domains, subdomains, or environments. Each requires its own account and script.
• No localhost or preview domains. This is a hard security restriction. For local development, use a real domain pointed to a local IP via /etc/hosts or a tunneling service that provides a stable public hostname (e.g., ngrok with a reserved domain), but note that dynamic tunnels may still be unreliable.
• DNS propagation. If you just pointed a new domain to your site, wait for full DNS propagation (up to 48 hours globally) before expecting SeaText to connect.
• Script updates. SeaText may update the snippet. If you've had an account for a long time, re-copy the script from the dashboard to ensure you have the current version.

Key Facts

FAQ

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

No. Each domain — including subdomains like staging.example.com and example.com — needs its own SeaText account with its own script.

Why does SeaText block localhost and preview domains?

Security. SeaText associates traffic with your account by observing real visitor sessions on a public domain. Local or ephemeral URLs cannot be reliably verified, so they are excluded.

I pasted the script but the dashboard still shows no connection after 15 minutes. What now?

Check the browser console for errors (CSP, CORS, 404). Verify the script is in the global footer, not a page-specific block. Confirm the live URL exactly matches the primary URL in your SeaText account. If all looks correct, open a support ticket with console/network screenshots.

Does the script work if placed in the <head> instead of the footer?

It may load, but SeaText's integration guide specifies the footer (or just before </body>) to avoid render-blocking and ensure the DOM is ready. Follow the documented placement.

Can I change the primary URL on an existing account?

Not directly in the dashboard. Contact support with the old and new URLs; they can re-associate the account.

What if my site is behind a password or VPN during setup?

SeaText's automated checks cannot reach a protected site. Temporarily remove password protection or IP restrictions while establishing the connection, then re-enable them.

How do I know the script is the current version?

Log into your SeaText account and copy the snippet from the integration page. Older saved copies may be outdated.