How Long Does SeaText Take to Activate on a Development Domain?

What "working" means for SeaText on a development domain

When the SeaText dashboard shows your development domain name next to the SeaText logo, the script is installed, the account is linked, and the AI is ready to generate variants. Until that moment the AI remains inert — no rewrites, no translations, no testing agents run.

This connection state is the single gate for every SeaText agent. The Google Ads rewrite agent, the translation agent, the CRO testing agent, and the bot refund agent all wait for this link. Nothing happens until the domain appears in the dashboard.

So the real question is not just "how long does it take?" but "how do I make sure the connection completes?" The answer involves a few precise steps and a few common pitfalls.

Step-by-step activation timeline

1. Create a dedicated SeaText account for the development domain. Each account binds to one primary URL. You cannot reuse a production account for staging.
2. Copy the JavaScript snippet from that account's dashboard. The snippet appears in a section labeled "SEATEXTCODEINTEGRATION."
3. Paste the snippet into the HEADER field of Squarespace → Settings → Developer Tools → Code Injection. The Developer Tools section is at the very end of the Settings page.
4. Save and publish the Squarespace site. Saving alone is not enough. The site must be live and publicly accessible.
5. Visit the development domain and stay on the page for at least 40 seconds. This visit activates the AI and links the domain to your account. Refresh the page a few times if you can.
6. Wait 5 minutes, then refresh the SeaText dashboard. The domain name should appear next to the logo at the top of the page.
7. If it does not appear after 10 minutes, contact SeaText support — the installation may have an issue. Include the domain URL and a screenshot of the Code Injection panel.

The 40-second dwell is not a suggestion. It is a hard requirement. The script needs time to load, run, and send a signal back to SeaText's servers. If you bounce after 5 seconds, the activation never fires.

Prerequisites before the timer starts

• A live, publicly accessible development domain (e.g., yoursite.squarespace.com or a custom staging subdomain). Localhost and dynamic preview URLs are blocked for security.
• The Squarespace site must be published; draft or password-protected sites will not trigger activation.
• The JavaScript snippet must be placed in the HEADER injection area, not the footer or page-level code blocks.
• A valid SeaText account created specifically for that domain. One account per domain, always.

Why does SeaText block localhost? Because localhost is not a real domain. The script cannot reliably associate traffic with your account when the URL is 127.0.0.1 or localhost:3000. The same logic applies to dynamic preview subdomains from Netlify or Vercel — those URLs change on every deploy, so SeaText cannot track them.

Common reasons for delays

• Caching: Squarespace or browser cache serves an old version of the page without the script. Clear cache or open an incognito window.
• Wrong injection field: Pasted into Footer or Page Header instead of the global Header. The global Header is the only field that works.
• Unpublished site: Changes saved but not published. The live page still serves the old HTML.
• Dynamic subdomain: Some staging platforms generate a new subdomain on each deploy; SeaText cannot reliably associate traffic.
• Multiple domains on one account: Each domain needs its own SeaText account. If you try to use one account for two domains, only the first one will connect.
• Password protection: SeaText cannot activate behind authentication. The script never loads because the visitor never reaches the page.

Cache is the most common culprit. Squarespace has its own CDN cache, and your browser has its own cache. Both can serve stale HTML. The fix is simple: clear both, or use a private window with cache disabled.

Verification steps

1. Open the development domain in a private browser window. This bypasses your normal browser cache.
2. Stay on the page for 40+ seconds. Do not navigate away.
3. Open the SeaText dashboard in another tab.
4. Wait 5 minutes, then refresh the dashboard.
5. Confirm the domain name appears next to the SeaText logo.
6. If absent after 10 minutes, open a support ticket with the domain URL and a screenshot of the Code Injection panel.

You can also verify the script is present by viewing the page source. Right-click the page, select "View Page Source," and search for "seatext" or the script ID. If the snippet is not in the source, the injection failed.

Limitations for development domains

• Localhost and 127.0.0.1 are permanently restricted.
• Dynamic preview URLs (e.g., Netlify deploy previews, Vercel preview links) often fail because the domain changes on every deploy.
• Each development domain consumes a separate SeaText subscription seat. A second account for staging incurs the same plan cost as the first.
• AI agents (Google Ads rewrite, translation, CRO testing) only start after the domain shows as connected.
• Password-protected staging sites will not work. You must remove the password or use a public staging subdomain.
• If you switch to a new custom domain at launch, you need a new SeaText account and fresh variant generation. The old variants do not carry over.

These limitations are not arbitrary. They exist to protect the integrity of the connection. SeaText needs a stable, public URL to associate traffic with your account. Anything else breaks the link.

Key facts

FAQ

Can I use a single SeaText account for both staging and production?

No. Each SeaText account links to one primary URL. You need two accounts — one for the development domain, one for production.

Does SeaText charge extra for a development domain?

Pricing follows your subscription plan per account. A second account for staging incurs the same plan cost as the first.

What if my staging domain is password-protected?

SeaText cannot activate behind authentication. Temporarily remove password protection or use a public staging subdomain.

Why does the dashboard still show "waiting" after 10 minutes?

Likely causes: script in wrong injection field, site not published, or a caching layer stripping the script. Verify the live page source contains the SeaText snippet.

Can I test SeaText on a Squarespace trial site?

Yes. Trial sites use real .squarespace.com domains, which are supported.

Will my AI-generated variants carry over when I launch the custom domain?

Only if you keep the same domain. Switching to a new custom domain requires a new SeaText account and fresh variant generation.

What happens if I refresh the page too quickly?

The 40-second dwell is required. If you leave before 40 seconds, the activation signal never fires. Stay on the page, then refresh a few times.

Can I use a subdomain like staging.example.com?

Yes, as long as it is publicly accessible and not password-protected. Custom staging subdomains work fine.

Does the script work on a site that is not Squarespace?

Yes, but the installation steps differ. The 40-second dwell and 5-minute wait still apply. The script must be in the head of every page.