Why Is My SeaText Popup Not Appearing? A Diagnostic Guide
Your SeaText popup is most likely not appearing because an ad blocker is blocking the script, your trigger settings are off, or your browser is serving a cached version of the page. Less often,...
Your SeaText popup is most likely not appearing because of one of three things: an ad blocker is blocking the script, your trigger settings are off, or your browser is serving a cached version of the page. Less often, the script wasn't installed correctly or the AI hasn't been activated yet. Let's walk through the causes in order.
Why the Popup Fails: The Mechanism
SeaText works by loading a JavaScript snippet on your site. That snippet stays inert until you activate it. The activation process requires you to visit your site, stay on the page for at least 40 seconds, and then wait a few minutes for the connection to register. If any part of that chain breaks, the popup won't show.
Ad blockers are the most common culprit. They can block the script before it even runs. Browser caching is another frequent issue: your browser might be showing an old version of the page that doesn't include the script. Trigger settings matter too—if you've configured the popup to appear only after a specific action or on certain pages, it won't show elsewhere.
The script loads asynchronously. This means it doesn't block your page from rendering. But it also means the popup appears after the main content loads. If a visitor leaves before the script finishes, they never see it. This design protects page speed but creates a visibility window you must account for.
Diagnostic Sequence: Check These in Order
- Confirm the script is installed. Log into your Squarespace dashboard, go to Settings, then Developer Tools, then Code Injection. Make sure the SeaText JavaScript snippet is pasted in the HEADER area and saved. If it's missing, paste it again and save.
- Check your account and domain. Each SeaText account is linked to a single primary URL. If you're testing on a development domain like localhost, it won't work. Use a real, valid domain.
- Activate the AI. Visit your website several times and stay on the page for at least 40 seconds. This activates the AI and links it to your account. Without this step, the popup won't appear.
- Wait for connection. After activation, wait at least five minutes. You should see your website name next to the SEATEXT logo in your dashboard. If it doesn't appear after 10 minutes, contact support.
- Disable ad blockers temporarily. Turn off any ad blocker or browser extension that might block scripts, then reload the page. If the popup appears, you know the blocker was the issue.
- Clear your browser cache. Hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) or clear your cache completely, then reload the page.
- Review trigger settings. In your SeaText dashboard, check the Configuration panel. Make sure the popup is set to show on the pages you're testing and that the trigger conditions (like time delay or scroll depth) are met.
- Verify template support. SeaText works with any Squarespace template that supports Code Injection. If your template is heavily customized or very old, it might not display the popup.
How SeaText Popups Work
SeaText is a single JavaScript snippet that you paste into your Squarespace site's header. It remains inert until you activate it. The activation process is deliberate: you visit your site, stay for 40 seconds, and then the AI links to your account. This protects your content and ensures the script only runs when you're ready.
Once activated, the AI can display popups, personalize content, and run other agents. But if you haven't completed the activation steps, the popup simply won't exist on your page. That's why the diagnostic sequence starts with installation and activation, not with trigger settings.
The script communicates with SeaText servers to fetch personalized content. This happens in milliseconds. If the network request fails—due to a blocker, firewall, or connectivity issue—the popup has nothing to show. The script fails silently to avoid breaking your page.
Key Facts About SeaText Installation
| Fact | Detail |
|---|---|
| Installation method | Paste JavaScript into Squarespace Code Injection (HEADER area) |
| Activation requirement | Visit/refresh your website several times and stay for at least 40 seconds |
| Connection confirmation | Wait at least 5 minutes; website name appears next to SEATEXT logo |
| Domain restriction | Each account is linked to a single primary URL; development URLs like localhost are restricted |
| Multiple domains | Create a separate account for each domain |
| Support | If website name doesn't appear after 10 minutes, contact support immediately |
Practical Scenarios and Decision Criteria
Scenario 1: Fresh Install on Live Domain
You pasted the script, saved, and published. You visit the site. Nothing appears. First, check the dashboard. Does your site name show next to the logo? If not, you haven't met the 40-second stay requirement. Stay longer. Refresh a few times. Wait five minutes. Check again.
Scenario 2: Popup Works on Homepage But Not Blog
You see the popup on the homepage but not on blog posts. Open the Configuration panel. Look at page targeting. You may have limited the popup to specific URLs. Add the blog URLs or select "All Pages." Save. Clear cache. Test again.
Scenario 3: Works in Incognito But Not Regular Browser
This points to an extension. Disable extensions one by one. Ad blockers, privacy tools, and script blockers are common causes. Once identified, whitelist your domain in that extension.
Scenario 4: Staging Site on Subdomain
You're testing on staging.yoursite.com. The script loads but no popup. SeaText ties accounts to primary URLs. A subdomain counts as a different domain. Create a separate SeaText account for the staging environment.
Decision Criteria: When to Contact Support
- Script is in HEADER, site is live, you've waited 10+ minutes, dashboard shows no connection
- Popup appears in incognito but no extension seems to block it
- Multiple team members confirm the issue across devices and networks
- Console shows SeaText script errors (open DevTools → Console)
Limitations and When This Advice Doesn't Apply
This diagnostic sequence assumes you're using a standard Squarespace site with Code Injection available. If your template doesn't support Code Injection, SeaText won't work at all. Also, if you're using a development domain or a dynamic URL, the script may not associate with your account, so the popup won't appear.
If you have multiple websites, remember that each one needs its own SeaText account. You can't use one account across different domains. And if you're testing on a staging site that isn't publicly accessible, the activation steps won't work.
SeaText relies on first-party cookies and local storage. If your site uses a strict Content Security Policy (CSP) that blocks inline scripts or third-party domains, the script may load but fail to execute. Check your CSP headers if you have a custom setup.
The AI agents (conversion, translation, SEO, etc.) only activate after the initial connection. If the base script doesn't connect, none of the agents will run. This includes the popup agent.
Terminology: What "Trigger Settings" Really Means
Trigger settings control when and where your popup appears. In SeaText, you configure these in the Configuration panel. Common triggers include time delay (e.g., show after 5 seconds), scroll depth (e.g., show after user scrolls 50% of the page), or exit intent (e.g., show when the mouse leaves the window). If you've set a trigger that hasn't been met, the popup won't show.
Also, you can choose which pages the popup appears on. If you're testing on a page that isn't included in your configuration, it won't appear. Double-check that the page you're viewing is in the active set.
Trigger logic uses AND conditions. If you set "time delay 10 seconds" AND "scroll depth 50%", both must be true. The popup waits for the later of the two. This can cause unexpected delays. Simplify triggers while testing.
Advanced Troubleshooting: Browser Console and Network Tab
Open Developer Tools (F12). Go to the Console tab. Look for errors mentioning "seatext" or "SEATEXT". A blocked script shows a network error. A CSP violation shows a security error. Copy the error and share it with support.
Switch to the Network tab. Filter by "seatext". You should see the script load (usually a .js file) and then an API call to fetch popup content. If the script loads but the API call fails, the issue is server-side or network-related. If neither appears, the script is blocked before it runs.
Check the Application tab → Local Storage → your domain. Look for keys starting with "seatext". If they're missing, the script never initialized. If they exist but are empty, the activation didn't complete.
Frequently Asked Questions
Why does my popup show on some pages but not others?
Check your trigger settings. You may have limited the popup to specific pages or conditions. Also, ensure the AI is activated for those pages in the Main AI Hub.
How long does it take for SeaText to activate?
After you visit your site for 40 seconds, wait at least 5 minutes for the connection to appear in your dashboard. If it doesn't show after 10 minutes, contact support.
Does SeaText work with all Squarespace templates?
SeaText works with any template that supports Code Injection. Most modern templates do. Older or heavily customized templates may not display the popup.
What if I have an ad blocker enabled?
Ad blockers can block the SeaText script. Temporarily disable your ad blocker and reload the page to see if that's the issue.
Can I use SeaText on multiple domains?
No. Each SeaText account is linked to a single primary URL. You need a separate account for each domain.
Why is my popup not showing after I cleared the cache?
If clearing the cache doesn't help, check that the script is still in Code Injection and that you've completed the activation steps. Also verify that your trigger settings are correct.
Does SeaText work on password-protected pages?
Yes, if the script is installed on the site and the page loads the header. The popup will appear once triggers are met.
Can I test SeaText on a local development environment?
No. Development URLs like localhost are restricted for security reasons. Use a real domain or a public staging URL.
What happens if I change my domain?
You need to update the primary URL in your SeaText account settings or create a new account for the new domain.
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.