SeaText Real-Time Connection Detection Across Website Platforms
Yes, SeaText supports real-time connection detection for all website platforms. Most platforms connect within minutes, but Weebly sites typically experience 5-10 minute delays due to Weebly's server-side caching behavior.
SeaText's connection detection works in real time across every supported platform. After you paste the JavaScript snippet and publish, the system watches for the first verified visit. On WordPress, Shopify, Webflow, Wix, Squarespace, and custom HTML sites, the dashboard usually shows "Connected" within one to three minutes. Weebly is the exception: its aggressive footer-code caching means the snippet often isn't served to visitors until Weebly's cache expires, so the dashboard can take five to ten minutes to register the connection.
How SeaText Connection Detection Works
When you add the SeaText JavaScript snippet to your site, the script loads asynchronously on every page view. On the first visit after installation, the script sends a lightweight ping to SeaText's edge network containing your account ID and the current URL. That ping is the "connection event." SeaText's dashboard polls for this event and flips the status badge from "Pending" to "Connected" as soon as the ping arrives. No background jobs, no scheduled cron runs — the moment a real browser executes the snippet, the status updates.
The only variable is how quickly your platform serves the updated footer code to a live visitor. Platforms that invalidate cache on publish (WordPress, Shopify, Webflow, Wix, Squarespace) make the new snippet available immediately. Platforms that cache footer code at the CDN layer (Weebly) introduce a delay between your "Publish" click and the snippet actually reaching a browser.
Platform Compatibility Overview
SeaText officially supports installation on any site where you can inject JavaScript into the global footer or <head>. The integration guide provides step-by-step instructions for WordPress, Shopify, Webflow, Wix, Squarespace, Weebly, and raw HTML. Each guide follows the same pattern: copy the snippet from your SeaText account, paste it into the platform's footer-code field, save, and publish. The detection mechanism is identical; only the platform's cache behavior changes the time-to-first-ping.
If you manage multiple domains — for example, a staging subdomain and a production domain — you need a separate SeaText account for each primary URL. Development URLs such as localhost or dynamic preview domains are blocked for security reasons, so connection detection will never fire on those environments.
Trade-off Table: Detection Speed by Platform
h>Cache Behavior| Platform | Typical Detection Time | Action If Delayed | |
|---|---|---|---|
| WordPress | 1–3 minutes | Cache invalidated on publish | Clear any plugin cache (WP Rocket, W3 Total Cache) and re-publish |
| Shopify | 1–2 minutes | CDN purges on theme save | Check theme.liquid placement; hard-refresh browser |
| Webflow | 1–3 minutes | Instant publish to global CDN | Verify snippet in Project Settings → Footer Code |
| Wix | 1–3 minutes | Cache cleared on publish | Use Custom Code panel in Settings → Advanced |
| Squarespace | 2–4 minutes | Cache cleared on save | Paste into Settings → Advanced → Code Injection → Footer |
| Weebly | 5–10 minutes | Footer code cached at CDN layer | Wait 10 minutes, then contact support if still pending |
| Custom HTML / Static Hosting | Immediate to 2 minutes | Depends on your CDN / host | Purge your CDN cache (Cloudflare, Netlify, Vercel, etc.) |
Takeaway: Every platform reaches "Connected" without manual intervention. Weebly is the only one where the platform's own caching adds a predictable 5–10 minute window. Plan your install-and-test workflow accordingly.
Why Weebly Has Longer Delays
Weebly stores the footer-code field in a database but serves the rendered site through a CDN that caches full HTML pages. When you click "Save" then "Publish," the database updates instantly, but the CDN edge nodes continue serving the old cached HTML until their TTL expires or a manual purge runs. Weebly does not expose a "purge cache" button to users. The SeaText integration guide explicitly notes: "Wait at least five minutes until you see your website name displayed next to the SEATEXT logo at the top of this page. This indicates that your website is connected and ready to proceed to the next step. If you do not see it at the top of the page after 10 minutes, please contact our support team immediately."
This is not a SeaText limitation — it is a Weebly architecture choice. The same snippet on the same domain hosted on Netlify or Vercel would connect in seconds because those platforms invalidate cache on every deploy.
Troubleshooting Connection Issues
- Verify the snippet is actually in the published HTML. Open your live site in an incognito window, view source, and search for
seatext. If it's missing, the platform didn't save or publish correctly. - Stay on the page for 40 seconds. The integration guide advises: "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." The 40-second dwell ensures the async script loads, executes, and sends the ping.
- Check browser console for errors. Content Security Policy (CSP) headers, ad blockers, or syntax errors in surrounding code can block the script. Look for
net::ERR_BLOCKED_BY_CLIENTor CSP violation messages. - Confirm you're on a valid, public domain. Localhost,
*.ngrok.io, and dynamic preview URLs are rejected by SeaText's security policy. The dashboard will never show "Connected" for those. - If Weebly: wait the full 10 minutes. Do not re-paste the snippet repeatedly; each publish resets the cache timer.
- Contact support with your account email and domain. Support can see server-side ping logs and tell you whether the snippet ever reached their edge.
Key Facts
| Fact | Detail |
|---|---|
| Detection mechanism | Client-side JavaScript ping on first verified visit |
| Real-time dashboard update | Yes — status flips the moment the ping arrives |
| Platforms with instant cache invalidation | WordPress, Shopify, Webflow, Wix, Squarespace, custom HTML |
| Platform with CDN-level footer caching | Weebly |
| Weebly typical delay | 5–10 minutes after publish |
| Weebly escalation threshold | Contact support if not connected after 10 minutes |
| Multi-domain rule | One SeaText account per primary URL |
| Blocked environments | localhost, dynamic preview domains, any non-public URL |
| Minimum dwell for activation | 40 seconds on a live page |
Limitations and Exceptions
- No server-side detection. SeaText cannot detect connection via webhook, API call, or DNS record. A real browser must load the page.
- Ad blockers and privacy extensions. uBlock Origin, Brave Shields, and similar tools may block the SeaText script, preventing the ping. The dashboard will stay "Pending" until an unblocked visit occurs.
- CSP headers. If your site sends a restrictive
Content-Security-Policywithoutscript-srcallowance for SeaText's domain, the browser will refuse to execute the snippet. - Staging and preview URLs. Dynamic preview domains (Netlify deploy previews, Vercel preview deployments, Shopify theme previews) are treated as development URLs and will not connect. Use a stable custom domain for testing.
- Multiple accounts per domain not supported. You cannot connect two SeaText accounts to the same primary URL. The second account will never receive pings.
FAQ
Does SeaText work on platforms not listed in the integration guides?
Yes. Any platform that lets you paste JavaScript into a global footer or <head> field will work. The detection logic is platform-agnostic.
Can I speed up Weebly detection?
Not from SeaText's side. The delay is entirely inside Weebly's CDN. The only reliable workaround is to wait the full 10 minutes, then contact support if the status hasn't changed.
What if my site is behind a login wall or VPN?
The detection ping requires a browser that can reach SeaText's edge network. If your site is IP-restricted, behind a corporate VPN, or requires authentication before the footer loads, the script won't execute and the dashboard will stay "Pending." Temporarily allow public access to the homepage for the initial connection.
Does the "Refresh Status" button in the dashboard force a re-check?
The dashboard has a "Refresh Status" button that re-polls the connection state, but it cannot create a connection that hasn't happened. It only updates the UI if a ping has already arrived.
Can I use one SeaText account for a main site and a subdomain?
No. Each primary URL (including subdomains you treat as separate sites) needs its own SeaText account. The account-to-URL mapping is 1:1.
What happens if I move my site to a new platform?
Create a new SeaText account for the new domain, install the snippet, and go through the connection flow again. Historical data does not transfer between accounts.
Is there a way to test the snippet before pointing DNS?
Not on a temporary domain. SeaText blocks dynamic development domains. You must install on the final public domain to verify connection.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
How SeaText can help
SeaText's connection detection is automatic and real-time on every platform that serves updated JavaScript immediately after publish. The dashboard shows "Connected" the moment a live visitor loads your page with the snippet. For Weebly sites, the only extra step is patience: wait up to 10 minutes for Weebly's CDN to flush its cached footer code. If the status doesn't flip, support can see exactly whether a ping arrived and help you troubleshoot CSP, ad-blocker, or placement issues.