Why SeaText Shows on the Weebly Dashboard But Not the Live Site
SeaText appears connected in your dashboard because the script was added and the account handshake succeeded, but the live site may still serve a cached version without the script, the script may be blocked...
How the SeaText–Weebly handshake works
SeaText integrates with Weebly by pasting a JavaScript snippet into Settings → SEO → Footer Code and then clicking Save followed by Publish. Once published, the script loads on every page view. The SeaText dashboard then waits for a real visit to the live URL—you must stay on the page for at least 40 seconds—before it registers the site as “connected” and shows the site name next to the SeaText logo. That dashboard confirmation is a separate event from the script actually executing on the live site.
This two-step process matters because the dashboard confirmation only proves that SeaText received a qualifying visit. It does not prove that the script ran correctly on every visitor's browser. Many users assume that seeing their site name in the dashboard means everything is live and working. In reality, the handshake is a necessary condition, not a sufficient one. The script must also be served, unblocked, and visible in the public-facing HTML.
Before installing, you need a SeaText account. The installation process is secure, and the AI remains inert until activation. If you do not have an account yet, you can create one through the SeaText website. After pasting the snippet, always click Save first, then Publish. Saving stores the snippet in Weebly's database. Publishing pushes it to the public CDN. Both steps are required.
Why the dashboard says “connected” while the live site shows nothing
Several distinct problems can create the gap between dashboard status and live output. Understanding each cause helps you pick the right fix instead of guessing randomly.
- Cached live pages. Weebly's CDN and your browser may serve an older HTML snapshot that does not yet contain the Footer Code snippet. After publishing, the CDN can take time to distribute the updated page. If you use a separate CDN like Cloudflare, the cache layer adds another delay.
- Publish step skipped. Saving in the SEO panel stores the snippet locally in Weebly's database. It does not push the change to the public URL. Many users click Save, see a confirmation message, and assume the site is live. Without clicking Publish, the live site never receives the script.
- Theme or Content Security Policy blocks the script. Some Weebly themes restrict inline or external scripts through strict CSP headers. If your theme enforces a restrictive policy, the SeaText snippet may load in the dashboard (which runs on SeaText's own domain) but fail on the live site.
- Activation visit not done on the live domain. The 40-second visit must happen on the exact production domain. Visits to a staging subdomain, a preview URL, or the Weebly editor preview do not count toward the handshake.
- Multiple-domain mismatch. Each SeaText account is tied to a single primary URL. If you added the script to a development domain but check the live domain—or vice versa—the dashboard reflects only the domain that received the qualifying visit. Managing multiple Weebly sites means each needs its own SeaText account and its own snippet installation.
- Ad blockers or privacy extensions. Extensions such as uBlock Origin, Privacy Badger, or browser tracking protection can strip the SeaText script on the live site while the dashboard remains unaffected. The dashboard loads from SeaText's domain, so it bypasses most blockers.
Diagnostic checklist—run these in order
Follow this sequence to isolate the problem quickly. Each step rules out one common cause before moving to the next.
- Open the live site in an incognito or private window. This bypasses most browser caches and extensions. Right-click on the page, select “View Page Source,” and search for the SeaText snippet. If it is missing entirely, the publish step did not propagate to the public URL. Go back and confirm you clicked Publish after Save.
- Hard-refresh the live page. On Windows, press Ctrl+Shift+R. On Mac, press Cmd+Shift+R. This forces the browser to fetch the latest version from the server instead of using a cached copy. If the snippet appears in source but the SeaText UI still does not initialize, open the browser console and look for CSP errors or script-load failures.
- Confirm you clicked Publish after Save. In Weebly's SEO settings, the Save button stores the snippet in the site's configuration. The Publish button deploys it to the public CDN. Both are required. The Weebly editor preview iframe often strips footer scripts, so always test on the published URL rather than the preview.
- Check the domain match. In the SeaText dashboard, verify that the domain shown next to the logo matches the live URL you are testing. If you see a development subdomain or a staging URL, create a separate SeaText account for the production domain. Each account supports one primary URL only.
- Do the 40-second activation visit on the live URL. Stay on any page of the live site for at least 40 seconds. The AI remains inert until this activation step completes. Then wait up to 5 minutes for the dashboard to update and show your site name next to the SeaText logo.
- Disable ad and tracker blockers temporarily. Reload the live site with blockers turned off. If SeaText appears, add an exception for the SeaText script domain in your blocker settings.
Fixes mapped to each cause
Once you identify the cause through the checklist above, apply the corresponding fix. The table below pairs each problem with its solution and a verification step so you can confirm the fix worked.
| Cause | Fix | Verification |
|---|---|---|
| Cached live page | Hard-refresh the page. If using a CDN such as Cloudflare, purge the cache there too. You can also enable Development Mode in Cloudflare while testing. | Snippet visible in incognito page source. |
| Publish step skipped | In Weebly, navigate to Settings → SEO → Footer Code. Paste the snippet, click Save, then click Publish. | Snippet appears in live page source immediately. |
| Theme or CSP blocks script | Switch to a default Weebly theme temporarily. If it works, adjust CSP headers or move the snippet to Header Code instead of Footer Code. | Console shows no CSP errors. SeaText initializes on the live page. |
| Wrong domain activated | Create a new SeaText account for the production domain and repeat the install steps with the correct snippet. | Dashboard shows the production domain name next to the SeaText logo. |
| Activation visit missing | Visit the live site, stay for 40+ seconds, then wait 5 minutes. | Dashboard updates to “connected” with the correct domain. |
| Blocked by extension | Whitelist the SeaText script domain in your blocker or extension settings. | SeaText UI loads with the blocker enabled. |
Practical scenario: You publish a new Weebly site for a client and install the SeaText snippet. The dashboard shows the site as connected after the 40-second visit, but the live page displays no SeaText interface. You open the page in incognito mode, view the source, and find no snippet. You return to Weebly, confirm that you clicked Save but not Publish. After clicking Publish and hard-refreshing, the snippet appears and SeaText initializes. This is one of the most common mistakes new users make.
Limitations and edge cases
Even after following every step, certain situations can prevent a clean connection. Knowing these limitations saves time and prevents unnecessary support tickets.
- Localhost and dynamic dev domains are restricted. SeaText will not reliably associate traffic with your account on localhost, 127.0.0.1, or randomly generated preview URLs. These environments are restricted for security reasons. Use a real domain—even a staging subdomain like staging.example.com—for testing and development.
- One account per primary URL. If you manage multiple Weebly sites, each needs its own SeaText account and its own snippet installation. A single account cannot track more than one primary URL.
- Weebly's editor preview is not the live site. The preview iframe often strips footer scripts and other embedded code. Always test on the published URL with a real domain.
- Dashboard latency. Even after a valid activation visit, the dashboard can take up to 10 minutes to reflect the connection. If it has been longer than 10 minutes, contact SeaText support with the exact live URL and the snippet you installed. This could indicate an issue during installation on your platform that requires assistance.
- AI remains inert until activated. The SeaText AI does not begin functioning until the 40-second activation visit completes. Installing the script alone does not turn on any features. Visit the live site, stay on the page, and wait for the dashboard confirmation before expecting any AI behavior.
Key facts at a glance
| Item | Detail |
|---|---|
| Installation location | Weebly Settings → SEO → Footer Code |
| Required actions after paste | Click Save, then Publish |
| Activation requirement | Visit live URL, stay 40+ seconds |
| Dashboard confirmation delay | Up to 5 minutes (10 minutes max before escalation) |
| Domain policy | One SeaText account per primary URL; separate accounts for dev and prod |
| Restricted environments | localhost, dynamic dev domains, editor preview URLs |
| Pre-installation requirement | Active SeaText AI account required before pasting snippet |
FAQ
Why does the SeaText dashboard show my site name but the live page has no SeaText UI?
The dashboard confirmation only means a qualifying visit occurred on some domain linked to that account. The live page may be cached, unpublished, or blocking the script. Run the diagnostic checklist above to identify the specific cause.
I pasted the code and clicked Save but not Publish. Does that matter?
Yes. Save stores the snippet in Weebly's database. Publish pushes it to the public CDN. Without Publish, the live site never receives the script, and the dashboard will not reflect the correct domain.
Can I test SeaText on a Weebly subdomain like mysite.weebly.com?
Yes, as long as it is a real, publicly accessible URL. Dynamic preview URLs generated by the editor will not work reliably. Use a published URL for testing.
My live site uses Cloudflare. Could that hide the script?
Cloudflare's cache can serve an older HTML version after you publish in Weebly. Purge the Cloudflare cache or enable Development Mode after publishing to ensure the latest version is served.
What if the script loads but SeaText still doesn't activate after 10 minutes?
Open a support ticket from the SeaText dashboard. Provide the exact live URL, the snippet you installed, and a screenshot of the browser console showing the script loaded without errors.
Do I need a separate SeaText account for a staging domain and the production domain?
Yes. Each SeaText account is linked to a single primary URL. Create one account for staging.example.com and another for example.com, then install the respective snippet on each Weebly site.
Will ad blockers on my visitors' browsers stop SeaText from working?
Some aggressive blockers may strip the script. SeaText's script is lightweight, but you cannot control every visitor's extensions. The dashboard connection test uses your own browser, so disable blockers during the activation visit.
Why does the AI remain inert after I install the snippet?
The SeaText AI requires a 40-second activation visit on the live URL before it starts operating. Installing the script is only the first step. Visit your live site, stay on any page for at least 40 seconds, and wait for the dashboard to confirm the connection.
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.