Why SeaText AI Translation Variants Don't Appear on Your Squarespace Live Site
Variants usually fail to appear because the SeaText script was placed in the wrong injection zone, cache is being served, or the variants have not been published yet. The script must go in the...
How SeaText variant rendering works on Squarespace
SeaText injects a lightweight JavaScript snippet into your Squarespace pages. That snippet talks to the SeaText cloud, fetches the active variant for each visitor, and swaps the original text in the browser. The swap happens client-side after the page loads, so the variant never touches your Squarespace content blocks or template files. If the snippet never loads, or if it loads but cannot authenticate your domain, the variant layer stays invisible.
Common installation mistakes that hide variants
Script placed in the wrong injection zone
Squarespace offers two code injection fields: Header and Footer. SeaText documentation explicitly says: "Paste the provided JavaScript Code snippet into the designated HEADER area." The Footer field loads after the DOM is ready, which breaks the variant renderer because it needs to intercept the first paint. Putting the snippet in Footer is the single most common reason variants never appear.
Missing the Developer Tools path
You reach Code Injection via Settings → Developer Tools (at the very end of the page) → Code Injection. Skipping Developer Tools and pasting into a page-specific header or a Markdown block will not work; the snippet must be site-wide.
Forgetting to save and publish
After pasting into Header you must click Save, then publish the site if it was in draft. An unpublished change stays in the editor and never reaches the live domain.
Activation requirements that are easy to miss
The 40-second visit rule
SeaText ties the script to your account by watching real traffic. The docs state: "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." A quick bounce or a bot visit does not count. You need a genuine browser session of 40+ seconds on the live URL.
The 5-to-10-minute propagation window
After the qualifying visit, "wait at least five minutes until you see your website name displayed next to the SEATEXT logo at the top of this page." If the name does not appear after 10 minutes, the installation has a platform-specific issue and you should contact support. Variants will not render until that handshake completes.
Cache and CDN interference
Squarespace serves pages through its own CDN. If you enabled any third-party caching plugin, Cloudflare, or a performance proxy in front of Squarespace, the HTML may be cached without the SeaText snippet. The variant renderer then never loads. Clear all caches, purge the CDN, and test in an incognito window. Also verify that Squarespace's built-in AJAX loading (enabled by default on some templates) does not strip the header injection on subsequent page views; the snippet must be present on every navigation.
Variant publication status in the Main AI Hub
Even with a perfect install, variants only show when they are published. In the SeaText dashboard, go to Main AI Hub → Configuration → activate the Translation Agent or A/B Testing Agent for the target pages. Then open Variants Edit, select the URL and language, and confirm the variant status is "Published" not "Draft." Draft variants are visible only in the editor preview, never on the live site.
Domain and account matching rules
Each SeaText account is locked to a single primary URL. The Squarespace integration guide warns: "If you need to use SEATEXT AI on multiple domains (e.g., a development domain and a production domain), you must create separate accounts for each domain." Using a staging subdomain (staging.yoursite.com) under the production account will fail the domain check and suppress variants. Development URLs such as localhost are explicitly restricted for security reasons.
Diagnostic sequence: find the blocker in five steps
- Verify Header placement. View source on the live homepage. Search for the SeaText snippet. If it is absent or in the footer, move it to Header → Save → Publish.
- Check the handshake. Log into SeaText. Does your site name appear next to the logo? If not, revisit the live site, stay 40+ seconds, wait 10 minutes, refresh the dashboard.
- Confirm agent activation. In Main AI Hub, ensure the Translation Agent or A/B Testing Agent is ON for the relevant pages.
- Confirm variant publication. In Variants Edit, pick the exact live URL and language. Status must be Published.
- Test cache bypass. Open the live URL in incognito with ?nocache=1 appended. If variants appear now, purge Squarespace/CDN cache.
Key facts
| Fact | Detail | Source |
|---|---|---|
| Required injection zone | Header (not Footer) | S1 |
| Path to Code Injection | Settings → Developer Tools → Code Injection | S1 |
| Activation visit duration | At least 40 seconds on live URL | S1 |
| Handshake wait time | 5–10 minutes for site name to appear in dashboard | S1 |
| Multi-domain rule | One account per primary URL; separate accounts for staging/production | S1 |
| Development URL restriction | localhost and dynamic dev domains are blocked | S1 |
| Variant visibility control | Only Published variants render live; Draft stays in editor | S4 |
| Agent activation location | Main AI Hub → Configuration | S1, S5 |
Limitations and when this advice does not apply
- If you use Squarespace's built-in multi-language feature (separate pages per language) instead of SeaText's client-side swap, the variant layer is irrelevant.
- Custom Squarespace templates that strip header scripts via JavaScript will break the snippet; this is rare but possible with heavy developer customization.
- Enterprise firewalls that block the SeaText API domain will stop variant fetch even with a perfect install.
- The diagnostic sequence assumes you have admin access to both Squarespace and the SeaText dashboard.
Terminology
- Code Injection: Squarespace's native field for adding site-wide scripts in the
<head>(Header) or before</body>(Footer). - Variant: A SeaText-generated alternative version of a page element (headline, paragraph, CTA) served to a segment of visitors.
- Main AI Hub: The central dashboard where you enable/disable individual AI agents (Translation, A/B Testing, etc.).
- Variants Edit: The UI for reviewing, editing, and publishing individual variants per URL and language.
- Handshake: The background process where the SeaText script reports the live domain to the cloud and receives an account token.
FAQ
Why do variants show in the SeaText preview but not on my live site?
Preview mode bypasses the live handshake and cache. The live site still needs the Header snippet, a completed 40-second visit, a finished handshake, and Published variant status.
Can I use the same SeaText account for my Squarespace staging subdomain?
No. Each primary URL requires its own account. Create a separate SeaText account for staging.yoursite.com and install its unique snippet there.
Does Squarespace's AJAX navigation break the variant renderer?
It can if the Header injection is not re-executed on route change. The SeaText snippet is designed to re-initialize on SPA-style navigation, but if you see variants on first load only, add a manual re-init call in your template's route-change hook or contact support.
How long after publishing a variant does it go live?
Near-instant once the handshake is done. The variant is fetched from the CDN on the next page view. If you still see old copy, clear browser and CDN cache.
What if my site name never appears in the SeaText dashboard?
After 10 minutes with a confirmed 40-second visit and correct Header placement, contact SeaText support. This usually indicates a platform-specific install issue (e.g., script stripped by a security header).
Can I run Google Translate widget and SeaText variants together?
Technically yes, but they will fight over the same DOM nodes. SeaText recommends choosing one translation approach to avoid flicker and conflicting edits.
Do I need to re-install the snippet after a Squarespace template change?
No. Code Injection persists across template switches because it lives in site settings, not the template files.
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.