Seatext library

Why SeaText Translations Don't Appear on Thinkific: A Diagnostic Checklist

Missing translations usually stem from script load order, language settings, or API key mismatches. The most common causes are the SeaText script not loading in Thinkific's footer, the site not being linked and activated...

If SeaText translations are not showing on your Thinkific site, the problem is almost always one of three things: the JavaScript snippet isn't loading, the site hasn't been linked and activated in your SeaText account, or the Website Translation Agent isn't turned on for the languages you need. Thinkific's own language settings can also interfere if they're set to a language SeaText doesn't recognize.

Diagnostic sequence: check these in order

Follow this sequence. Each step rules out a specific failure mode. Stop when you find the issue.

1. Verify the script is in Thinkific's Site Footer Code

SeaText must be pasted into Settings → Code & Analytics → Site Footer Code in your Thinkific admin. If it's in the header, or in a course-specific code field, it won't run on every page. Open an incognito window, load any page on your Thinkific site, and view source. Search for seatext or your SeaText domain. If you don't see the script tag, the snippet isn't installed correctly.

2. Confirm the site is linked and activated in SeaText

After pasting the script, you must add your site address (e.g., www.yoursite.com) in the SeaText dashboard, then visit the live site and stay for at least 40 seconds. This handshake activates the AI. Wait five minutes, then check the SeaText dashboard: your site name should appear next to the SeaText logo. If it doesn't appear after 10 minutes, the handshake failed—contact support.

3. Ensure the Website Translation Agent is active

In the SeaText Main AI Hub, the Website Translation Agent must be activated. Go to Configuration and confirm the agent is on. Then open Variants Edit in the left panel, select your site URL and the target language. If no variants exist for that language, the agent hasn't generated translations yet—or the language isn't enabled.

4. Check Thinkific's default site language

Thinkific sets a default site language under Settings → Site Language. If this is set to a language SeaText doesn't support, or if Thinkific serves a hard-coded language parameter that overrides the browser's Accept-Language header, SeaText may not trigger. Set Thinkific's default to English (or your primary language) and let SeaText handle the switching.

5. Clear caches and test in incognito

Thinkific caches pages aggressively. Clear your browser cache, any CDN cache (Cloudflare, etc.), and Thinkific's own cache if you've made theme changes. Test in an incognito window with a VPN set to a country that matches your target language. This isolates browser and network caching from the diagnosis.

6. Inspect the browser console for errors

Open DevTools → Console on a page where translations should appear. Look for SeaText-related errors: 401 (API key mismatch), 403 (domain not authorized), CORS (cross-origin block), or script load failures. A 401 usually means the API key in the snippet doesn't match your SeaText account. A 403 means the domain in SeaText doesn't match the live URL (e.g., www vs non-www).

How SeaText translation works on Thinkific

SeaText injects a lightweight script (<15 KB) that runs before visual paint. It reads the visitor's language preference (browser header, URL parameter, or cookie), fetches translated variants from your SeaText project, and swaps text nodes in the DOM. On Thinkific, this happens on every page load because the script sits in the global footer. The translation agent supports 125 languages and keeps your original content as the fallback.

Key facts

ItemDetail
Install locationThinkific Admin → Settings → Code & Analytics → Site Footer Code
Activation handshakeAdd domain in SeaText → visit site for 40+ seconds → wait 5 minutes for dashboard confirmation
Translation agentWebsite Translation Agent (one of 20+ agents), enabled in Main AI Hub → Configuration
Language controlVariants Edit panel: select URL and language to review, create, or edit translations
Supported languages125
Script sizeUnder 15 KB, synchronous execution <15 ms, zero CLS impact

Common failure patterns and what they mean

SymptomLikely causeFix
No translations on any pageScript missing from footer or wrong code fieldRe-paste snippet in Site Footer Code, save, clear cache
Dashboard shows site as "not connected"Handshake incomplete (40-second visit skipped or domain mismatch)Visit live site in incognito, stay 40+ seconds, wait 5 minutes
Translations work for some languages, not othersLanguage not enabled in Variants Edit or no variants generated yetOpen Variants Edit, select language, generate or add translations
Console shows 401/403API key mismatch or domain not authorized in SeaTextVerify domain spelling (www vs non-www), regenerate snippet if needed
Thinkific's default language overrides SeaTextSite Language setting forces a single languageSet Thinkific Site Language to primary language, let SeaText handle switching

Limitations and when this advice doesn't apply

  • If you're using a Thinkific theme that loads content via AJAX after initial paint (rare), SeaText may not re-translate dynamic sections. The script re-runs on full page loads only.
  • Custom checkout pages hosted on Thinkific's checkout.thinkific.com subdomain cannot be translated via your main site's snippet—they're a separate origin.
  • If you've implemented a custom language switcher that sets a cookie or URL parameter SeaText doesn't recognize, you'll need to map that parameter in SeaText's configuration.
  • Enterprise firewalls or CSP policies that block third-party scripts will prevent SeaText from loading entirely.

Terminology

  • Handshake: The 40-second visit that links your live site to your SeaText account.
  • Variants Edit: The SeaText panel where you review, create, or manually edit translations for each URL and language.
  • Website Translation Agent: The specific AI agent that handles multilingual content generation and serving.
  • Site Footer Code: Thinkific's global JavaScript injection point, applied to every page.

FAQ

Why do translations appear for me but not for visitors in other countries?

Your browser likely sends an Accept-Language header matching your primary language. Test with a VPN or use the ?lang=es (or other language code) URL parameter to force a specific language. SeaText respects URL parameters, cookies, and browser headers in that order.

Can I translate course player content (lessons, quizzes)?

Yes, if the course player loads on your main domain and the SeaText script is in the global footer. Content loaded via Thinkific's course player iframe on a different subdomain won't be translated.

How long until new translations appear after I edit them in Variants Edit?

Changes propagate within a few minutes. Clear your browser cache and reload. If you use a CDN, purge its cache for the affected URLs.

Does SeaText work with Thinkific's built-in multi-language feature?

Thinkific's native multi-language support applies only to default system text (buttons, labels). It does not translate your custom course content, landing pages, or blog posts. SeaText handles that layer. Disable Thinkific's language switcher if it conflicts.

What if I see a flash of original language before translation?

SeaText executes synchronously in under 15 ms before paint, so there should be no flash. A flash indicates the script is loading asynchronously or after other scripts. Ensure the snippet is the first script in the Site Footer Code field.

Can I exclude certain pages from translation?

Yes. In the SeaText dashboard, you can configure URL patterns to exclude (e.g., /checkout/*, /admin/*). This is useful for pages where translation breaks functionality.

Is there a limit to how many pages SeaText translates?

No page limit. The agent crawls and translates every page the script loads on. Very large sites (10,000+ URLs) may take longer for initial variant generation.

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.