How to Verify SeaText Tracking Code Installation on Your Website
To verify SeaText's tracking code is working, visit your site and stay on a page for at least 40 seconds, then wait 5 minutes and check your SeaText dashboard — your website name should...
You can confirm SeaText's tracking code is installed correctly by triggering a session on your own site and then checking the SeaText dashboard for a connection signal. The process takes about 5–10 minutes and requires no technical tools beyond your browser and the SeaText account page.
Quick verification checklist
Before you start, make sure you have:
- A live SeaText account
- The JavaScript snippet pasted into your site's header or footer (depending on platform)
- The site published and publicly accessible (not localhost or a password-protected staging domain)
- Access to your SeaText dashboard in a separate browser tab
Step-by-step verification
- Open your website in a new browser tab. Use a normal browsing session — incognito works fine.
- Stay on any page for at least 40 seconds. Scroll, click, or just wait. This dwell time lets the script initialize and send a heartbeat to SeaText.
- Refresh the page once or twice. Each reload reinforces the connection.
- Switch to your SeaText dashboard tab. Wait 5 minutes from the first visit.
- Look at the top of the dashboard. Your website name should appear next to the SeaText logo. That text is the confirmation that the domain is linked and the script is firing.
- If nothing appears after 10 minutes, re-check the installation. Common issues: the snippet is in the wrong place, a CMS cache hasn't cleared, or a security header blocks the script.
How the verification signal works
SeaText's snippet is a small JavaScript file that loads asynchronously. When a visitor (including you) lands on a page with the snippet, the script:
- Collects basic session data
- Sends a ping to SeaText's servers with the account ID embedded in the snippet
- Registers the domain against your account
The dashboard polls for that registration. Once the server sees a valid ping from your domain, it updates the UI to show the site name next to the logo. This usually happens within 5 minutes but can take up to 10 if the network is slow or the script loads late.
Common installation mistakes that break verification
| Mistake | Why it fails | Fix |
|---|---|---|
Snippet placed in <body> instead of <head> or footer | Some platforms only execute header/footer code reliably | Follow platform-specific instructions (e.g., Weebly uses Footer Code in Settings → SEO) |
| Using a development URL (localhost, ngrok, preview domains) | SeaText restricts dynamic or local domains for security | Use a real, public domain; create separate accounts for each domain |
| Caching layer serves old HTML without the snippet | CDN or server cache hasn't purged | Clear cache, redeploy, or wait for TTL expiry |
| Content Security Policy blocks external scripts | CSP header lacks script-src allowance for SeaText's domain | Add SeaText's domain to your CSP script-src directive |
| Multiple domains on one account | Each SeaText account supports only one primary URL | Create a new account for each additional domain |
Platform-specific verification notes
Weebly
Paste the snippet in Settings → SEO → Footer Code, then Save and Publish. The verification steps above apply unchanged.
WordPress
Use a header/footer plugin (e.g., WPCode, Insert Headers and Footers) to paste the snippet in the <head> section. Clear any caching plugin (WP Rocket, W3 Total Cache) after saving.
Shopify
Add the snippet in Online Store → Themes → Edit Code → theme.liquid just before </head>. Save and verify.
Custom HTML / static sites
Place the snippet immediately before </head> on every page template. Deploy and verify.
What to do if verification fails after 10 minutes
- View page source (Ctrl+U / Cmd+Option+U) and search for
seatextor your account ID. If it's missing, the snippet didn't publish. - Open DevTools → Network tab, filter for JS, reload. Look for a request to SeaText's domain. A 200 response means the script loaded; a 404 or blocked status means CSP or network issues.
- Check the Console tab for JavaScript errors referencing SeaText.
- Confirm the domain in your SeaText account matches the live URL exactly (including
wwwvs non-www). - Contact SeaText support with your account email and the URL. They can see server-side whether pings arrived.
Key facts
| Item | Detail |
|---|---|
| Minimum dwell time to trigger registration | 40 seconds on any page |
| Typical dashboard update latency | 5 minutes |
| Maximum wait before escalating | 10 minutes |
| Supported domains per account | One primary URL only |
| Restricted environments | localhost, dynamic preview URLs, password-protected staging |
| Verification signal | Website name appears next to SeaText logo at top of dashboard |
| Snippet placement (Weebly) | Settings → SEO → Footer Code |
| Snippet placement (generic) | Just before </head> or in platform header/footer field |
Limitations and when this advice doesn't apply
- If your site uses a strict CSP without SeaText's domain allowlisted, the script will load but fail to send data — verification will never succeed until CSP is updated.
- Single-page applications (SPAs) that navigate without full reloads may need the snippet re-initialized on route change; the basic verification still works for the initial load.
- Sites behind authentication (intranets, member areas) can verify only if you're logged in during the test; the script must load on the authenticated page.
- This verification confirms the snippet fires and registers the domain. It does not confirm that AI agents (translation, CRO, chat, etc.) are configured or active — those are separate steps in the dashboard.
Terminology
- Snippet — The JavaScript code block provided in your SeaText account, unique to your account ID.
- Heartbeat / ping — The lightweight network request the snippet sends to SeaText servers to announce a live session.
- Dashboard — The web UI at
seatext.comwhere you manage sites, agents, and settings. - Primary URL — The single domain an account is bound to; additional domains require separate accounts.
FAQ
Can I verify installation without waiting 5 minutes?
No. The 5-minute window is built into SeaText's backend polling. You can confirm the script loads instantly via DevTools, but the dashboard connection signal requires the server-side registration cycle.
Does the verification work on a staging subdomain?
Only if the subdomain is a real, public DNS record (e.g., staging.example.com). Dynamic preview URLs from Netlify, Vercel, or similar platforms are restricted and will not register.
What if I have multiple languages or subdirectories?
The snippet registers the root domain. All paths and subdirectories under that domain are covered automatically once the root is verified.
Can I use the same snippet on two different domains?
No. Each SeaText account is tied to one primary URL. Using the same snippet on a second domain will either fail to register or attribute traffic to the wrong account. Create a second account.
Why does the dashboard show my site name but the AI agents don't run?
Verification only proves the tracking code is installed. Agents (Translation, CRO, Chat, etc.) must be activated individually in the Main AI Hub → Configuration. Check each agent's status toggle.
What if I'm using a tag manager (GTM, Tealium)?
Paste the snippet into a Custom HTML tag set to fire on All Pages (Page View). Publish the container, then run the same 40-second / 5-minute verification.
How do I know the snippet is the current version?
The snippet in your SeaText account is always the latest. If you copied it months ago, re-copy from the account page to ensure you have any updates.
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.