Seatext library

Why SeaText Only Works on One of Your Weebly Sites

SeaText ties each account to a single verified domain. If you have multiple Weebly sites, you must create a separate SeaText account for each one and install the unique JavaScript snippet from that account's...

Understanding the One-to-One Requirement

SeaText associates your website traffic, conversion data, and AI configurations with a specific, verified domain. Each SeaText account links to one primary URL. The system cannot aggregate data or manage AI agents across multiple domains from a single login.

If SeaText works on one site but not another, the most common cause is using the same account and JavaScript snippet across different domains. Each site needs its own dedicated account so the AI can correctly identify and optimize traffic for that specific URL.

Technical Architecture: Domain-Linked Security Model

SeaText uses a domain-linked security model to prevent data cross-contamination. Every account creates an isolated data container bound to a primary domain. When the JavaScript snippet loads, it sends the current hostname to the SeaText server. The server checks that hostname against the account's registered primary URL. If they match, the AI activates. If they differ, the request is rejected.

This design ensures that conversion data, bot detection reports, and AI-generated copy variants stay specific to the correct audience. It prevents "data cross-talk" where traffic from one site might accidentally trigger optimization logic meant for another. The isolation also protects against session hijacking and unauthorized domain spoofing.

Each account stores its own encryption keys, visitor profiles, and agent configurations. No data shares across accounts. This architecture supports compliance with data privacy regulations because each domain's data remains in its own silo.

The Handshake Process: How the Snippet Talks to the Server

The activation handshake is a multi-step exchange between the JavaScript snippet on your page and the SeaText backend. Understanding this process helps diagnose why a second site may stay inactive.

  1. Snippet Load: The browser loads the unique JavaScript file from SeaText's CDN. The snippet contains an account identifier tied to your primary domain.
  2. Environment Check: The script reads window.location.hostname and compares it to the registered domain. It also checks for localhost, IP addresses, or known development patterns.
  3. Beacon Request: If the hostname passes the check, the snippet sends a lightweight beacon (HTTP POST) to the SeaText activation endpoint. The payload includes the account ID, current URL, timestamp, and a browser fingerprint hash.
  4. Server Validation: The server verifies the account ID exists, the domain matches the primary URL, and the fingerprint is not flagged as bot traffic.
  5. Session Token: On success, the server returns a short-lived session token. The snippet stores this token in memory (not localStorage) to authorize subsequent API calls for AI agents.
  6. Heartbeat: Every 30 seconds, the snippet sends a heartbeat with dwell time and scroll depth. This keeps the session alive and feeds reading telemetry to the AI.

If any step fails — domain mismatch, blocked request, or fingerprint anomaly — the handshake aborts and the AI remains inert. No errors show in the browser console by design, to avoid leaking configuration details.

Diagnostic Sequence: Why Your Second Site Isn't Responding

If you believe you have set up multiple sites but only one works, follow this diagnostic sequence to identify the gap:

  1. Check Account Association: Log into your SeaText dashboard. Look at the top of the page next to the SeaText logo. Does it display the name of the site you are currently working on? If it shows the wrong site, you are likely logged into the wrong account.
  2. Verify the Snippet: Ensure you have copied the unique JavaScript snippet from the specific SeaText account created for the second site. Using a snippet from Site A on Site B will cause the AI to fail to associate the traffic correctly.
  3. Confirm Installation: Navigate to your Weebly Settings > SEO > Footer Code for the second site. Verify that the code is present and saved.
  4. Trigger Activation: After pasting the code, visit or refresh your second website several times. Stay on the page for at least 40 seconds. This dwell time is required for the AI to "handshake" with your domain and link it to your account.
  5. Wait for Sync: Allow at least five minutes for the system to process the connection. If the site name does not appear at the top of your SeaText dashboard after 10 minutes, the installation may be incomplete.

Weebly-Specific Troubleshooting Guide

Weebly's platform quirks can break the SeaText handshake even when the snippet is pasted correctly. Check these common issues:

Caching and Publish Delays

Weebly caches published pages aggressively. After pasting the snippet in Footer Code, you must click Save then Publish. Wait 2-3 minutes for the CDN to propagate. Test in an incognito window to bypass browser cache.

Conflicting Scripts

Other analytics or chat widgets in Footer Code may execute before SeaText and throw errors that halt further script execution. Open the browser DevTools Console (F12) on your live site. Look for red errors before the SeaText beacon fires. Temporarily remove other scripts to isolate the conflict.

Theme Footer Code Limitations

Some Weebly themes inject their own footer HTML after the SEO Footer Code block. This can wrap the SeaText snippet in a container that blocks its access to window. Switch to a default Weebly theme temporarily to test. If it works, contact the theme developer or move the snippet to the Header Code block (Settings > SEO > Header Code) as a workaround.

Multiple Sites in One Weebly Account

Weebly allows multiple sites under one login. Each site has its own Settings > SEO panel. Ensure you are editing the correct site's Footer Code. The site selector dropdown in the Weebly editor top-left must match the domain you are activating.

SSL and Mixed Content

If your Weebly site loads over HTTPS but the SeaText snippet URL is HTTP (rare), browsers block the request. The snippet URL from the dashboard always uses HTTPS. Verify the script src starts with https://.

Managing Multiple Accounts for Agencies and Power Users

Agencies managing dozens of client sites need a workflow to handle many SeaText accounts efficiently. SeaText does not yet offer a multi-account dashboard. Use these practices:

  • Password Manager: Store each account's credentials in a password manager with tags like "client-name-seatext". Use the password manager's browser extension for one-click login.
  • Browser Profiles: Create a separate Chrome/Edge/Firefox profile per client. Each profile maintains its own cookies, so you can stay logged into multiple SeaText accounts simultaneously.
  • Spreadsheet Inventory: Maintain a sheet with columns: Client, Primary Domain, SeaText Account Email, Snippet ID, Activation Date, Status. Update after each new site launch.
  • Delegated Access: For client-owned accounts, ask the client to create the SeaText account and share login via a secure password-sharing tool. You install the snippet; they own the data.
  • Automation: Use Weebly's API (if available) or a browser automation tool to paste snippets across many sites, but always verify each activation manually with the 40-second dwell step.

SeaText's roadmap includes an agency dashboard. Until then, treat each account as a separate tenant.

Why Development and Localhost Environments Are Restricted

SeaText blocks localhost, 127.0.0.1, *.local, and dynamic development domains (e.g., ngrok.io, localhost.run) for security and data-integrity reasons.

Security Rationale

Development environments often lack HTTPS, have open ports, and run on shared networks. Allowing them would expose the activation endpoint to spoofing. An attacker could mimic a development domain and harvest account IDs or inject malicious payloads into the AI pipeline.

Data Integrity

The AI models train on live visitor behavior. Development traffic — automated tests, bots, team members clicking through — pollutes the training set. A single QA session can generate thousands of fake events that skew conversion predictions.

Staging Best Practices

To test SeaText before production:

  1. Use a real subdomain on your production domain (e.g., staging.clientdomain.com) with a valid SSL certificate.
  2. Create a dedicated SeaText account for that subdomain.
  3. Install the snippet on the staging site.
  4. Restrict staging access via IP allowlist or basic auth so only your team generates traffic.
  5. Run the 40-second dwell activation. Verify the site name appears in the dashboard.
  6. Test AI agents (translation, CRO, chat) in staging. When satisfied, replicate the setup on the production domain with a new account.

Do not reuse the staging account for production. Each domain needs its own account.

Why the 40-Second Dwell Time Matters for Data Integrity

The 40-second minimum dwell requirement is not arbitrary. It serves as a quality gate for the handshake and for the AI's reading telemetry.

Handshake Confirmation

The server only marks a domain "connected" after receiving heartbeats that prove a real browser stayed on the page. This filters out bots, crawlers, and pre-rendering services that load the page for milliseconds. Without this gate, a single bot visit could activate an account on a domain the owner doesn't control.

Reading Telemetry Baseline

SeaText's CRO agents rely on millisecond-level reading behavior: eye-line dwell velocity, friction points, scroll deceleration. A 40-second session captures enough scroll events, pauses, and re-reads to build a preliminary behavioral fingerprint. Shorter visits provide noise, not signal.

Multi-Armed Bandit Initialization

When the AI starts, it deploys copy variants using a multi-armed bandit algorithm. It needs an initial cohort of genuine visitors to allocate traffic. The 40-second threshold ensures the first visitors counted are engaged humans, not bounces. This prevents the bandit from optimizing for bot patterns.

Practical Tip

During activation, browse naturally: scroll, click a link, read a paragraph. Do not just leave the tab open. The script detects tab visibility and pauses heartbeats when the tab is backgrounded.

Key Facts About SeaText and Weebly

Feature Requirement
Account Structure One account per primary domain.
Installation Method Paste unique JavaScript into Weebly Footer Code.
Activation Time Requires 40+ seconds of active browsing on the site.
Development URLs Localhost/dynamic dev domains are restricted for security.
Sync Latency Up to 10 minutes for dashboard to reflect connection.
Agency Workflow Separate browser profiles or password manager per account.

Common Pitfalls to Avoid

  • Reusing Snippets: Never copy-paste the JavaScript from one site's dashboard to another. Always generate the code from the account associated with that specific domain.
  • Ignoring Development Domains: If you are testing on a "localhost" or temporary development URL, the AI will not activate. Always use a valid, live domain.
  • Insufficient Dwell Time: Simply pasting the code is not enough. You must actively browse the site to "wake up" the AI agent.
  • Skipping Publish: In Weebly, saving Footer Code is not enough. You must click Publish for changes to go live.
  • Wrong Site Context: When managing multiple Weebly sites, verify the site selector in the editor matches the domain you are configuring.

When to Contact Support

If you have followed the steps above — specifically the 40-second dwell time and the 10-minute wait period — and your site still does not appear in your dashboard, there may be a deeper integration issue. Contact the SeaText support team with your domain URL so they can verify if the script is successfully communicating with their servers. Provide the browser console network log (filter for "seatext") if possible.

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.

Learn more