What If SeaText Connects But Doesn't Display Data on Squarespace?

Understanding the Connection vs Data Display Gap

SeaText shows a green connection status when the JavaScript snippet loads on your Squarespace site and the domain registers in your SeaText account. That confirmation only proves the script is present. It does not guarantee that AI agents are running, that content has been processed, or that visitors will see rewritten copy. The connection handshake and the AI execution layer are separate steps.

Think of it like plugging in a router: the lights turn on (connection), but you still need to configure the Wi-Fi network and connect devices (activation) before data flows. On Squarespace, the script injects via Code Injection in the header. Once saved and published, SeaText waits for real visitor sessions to begin its analysis and rewriting work.

Diagnostic Sequence: Step-by-Step Check

1. Verify the connection timestamp. In your SeaText dashboard, look at the top of the page. Your site name should appear next to the SeaText logo within five minutes of publishing. If it took longer than ten minutes, the initial handshake was delayed.
2. Confirm AI activation in the Main AI Hub. After the site name appears, you must go to the Main AI Hub and activate the specific agents you want — translation, CRO, personalization, etc. The source pack states: "Proceed to the Main AI Hub to activate the necessary AI on your preferred pages." Without this step, the script sits idle.
3. Check the Configuration settings. Click "Configuration" to adjust AI parameters. If no parameters are set, agents may run with defaults that produce no visible changes on your current pages.
4. Visit the live site as a real visitor. The source pack emphasizes: "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." Incognito mode or a different browser helps rule out local cache.
5. Clear Squarespace and browser caches. Squarespace caches pages aggressively. Use the Squarespace cache clear option (Settings → Advanced → Clear Cache) and hard-refresh (Cmd+Shift+R / Ctrl+Shift+R).
6. Inspect the network tab. Open DevTools → Network, filter for "seatext", and reload. You should see the script load (200 OK) and subsequent API calls to SeaText endpoints. If the script loads but no API calls fire, the AI may not be activated for that page path.

Common Causes When Connection Shows But Data Doesn't

1. AI Agents Not Activated

This is the most frequent cause. The connection handshake succeeds, but no agents are turned on in the Main AI Hub. SeaText ships with 26 autonomous agents (CRO, translation, bot protection, etc.), but each must be enabled per site or per page. The source pack notes: "SEATEXT AI provides your initial round of automatic translations and variants for testing" — but only after activation.

2. Insufficient Visitor Traffic

SeaText's reading telemetry and multi-armed bandit optimization need real sessions to generate variants. If your site gets fewer than a few dozen visits a day, the AI may not have enough data to produce visible rewrites. The CRO agent, for example, "reads full session recordings and telemetry to pinpoint exactly where buyers lose interest" — it needs sessions to read.

3. Caching Serving Stale HTML

Squarespace's edge cache, your browser cache, or a CDN (Cloudflare, etc.) can serve a page version without the SeaText script or with an old script version. The script injects via Code Injection → Header, but cached pages bypass that injection until the cache expires or is purged.

4. Script Placement Error

The source pack specifies: "Paste the provided JavaScript Code snippet into the designated HEADER area." If the snippet was pasted into the Footer or Page Header instead of the global Header, it may load on some pages but not others, or load after the DOM is ready, missing the activation window.

5. Domain Mismatch or Multiple Domains

Each SeaText account links to a single primary URL. If you're testing on a staging domain (e.g., yoursite.squarespace.com) but the account is registered to the production domain, the connection may show but data won't process. The source pack warns: "If you need to use SEATEXT AI on multiple domains … you must create separate accounts for each domain." Development URLs like localhost are restricted.

6. Page-Level Exclusions or Rules

In Configuration, you can restrict agents to specific page paths. If the current page doesn't match the rules, the AI won't run there. Check the "Configuration" panel for path filters.

Corrective Actions for Each Cause

Key Facts About SeaText Squarespace Integration

Limitations and When This Advice Doesn't Apply

This diagnostic covers the standard SeaText-on-Squarespace path: script injection via Code Injection, activation via dashboard, and AI execution on live visitor sessions. It does not cover:

• Custom Squarespace implementations using developer mode or GitHub sync — the Code Injection path may differ.
• Squarespace Personal plans that lack Code Injection access (Business and Commerce plans typically include it).
• Server-side rendering or static export setups where the SeaText script cannot execute in a browser context.
• Issues originating from SeaText's backend (API outages, model errors) — those require support escalation.
• Third-party script conflicts that block SeaText's execution; use the Network tab to diagnose script load order and errors.

Terminology Quick Reference

Code Injection

Squarespace's built-in feature (Settings → Developer Tools → Code Injection) for adding custom scripts to the <head> or <body> of every page.

Main AI Hub

The SeaText dashboard section where you enable/disable specific AI agents for your connected site.

Configuration

The panel within SeaText where you set agent parameters, page-path rules, and behavior options.

Activation (SeaText sense)

The moment a real visitor session triggers the AI to start analyzing behavior and generating variants; requires ≥40 seconds on page.

Connection (SeaText sense)

The handshake where your domain registers in the SeaText account; confirmed by site name appearing next to the logo.

Multi-armed bandit

An algorithm that dynamically allocates more traffic to better-performing copy variants instead of a fixed 50/50 split.

Reading telemetry

Millisecond-level tracking of scroll depth, dwell time, re-reading, and friction points to inform copy optimization.

FAQ

How long after activation should I see data?

For translation agents, variants can appear within the first few activated sessions. For CRO and personalization agents that rely on reading telemetry, expect 50–200 sessions before statistically confident rewrites surface. Low-traffic sites may take days.

Can I force a refresh without waiting for cache expiry?

Yes. In Squarespace, go to Settings → Advanced → Clear Cache. If you use Cloudflare or another CDN, purge there too. Then hard-refresh (Cmd+Shift+R / Ctrl+Shift+R) in an incognito window.

Why does the SeaText dashboard show zero sessions but my analytics show traffic?

SeaText only counts sessions where the script loaded, the visitor stayed ≥40 seconds, and the AI handshake completed. Ad blockers, script blockers, or rapid bounces (<3 seconds) won't register. Check the Network tab for seatext API calls on a test visit.

Do I need to republish Squarespace after changing SeaText Configuration?

No. Configuration changes in the SeaText dashboard take effect immediately for new sessions. The Squarespace script only needs to be published once during initial install.

What if I have a Squarespace Personal plan?

Personal plans may not include Code Injection (Developer Tools). Upgrade to Business or Commerce, or contact Squarespace support to confirm your plan's capabilities.

Can I test SeaText on a password-protected Squarespace site?

Yes, but the SeaText script must load on the page. Password protection happens at the Squarespace level before the page renders, so the script still injects. However, search crawlers and some bots won't access it, limiting SEO-related agents.

When should I contact SeaText support?

If the site name doesn't appear next to the SeaText logo after 10 minutes, or if the script loads (200 OK in Network tab) but zero API calls fire across multiple test sessions on different browsers/devices after agents are activated and caches cleared.