How to manage multiple Thinkific sites with one SeaText account

SeaText lets you connect multiple Thinkific schools to a single account. You add each site through the integrations panel, paste the same JavaScript snippet into each site's footer, link each domain in SeaText, and then switch between them in the dashboard.

How to Implement Language Switching Persistence in Vue with SeaText

Q: SeaText Angular Integration: TypeScript Types and Practical Workarounds

SeaText’s public documentation shows Angular integration through a plain JavaScript snippet. No official TypeScript definitions, interfaces, or Angular‑specific service classes are published. Developers must rely on the snippet, handle zone and SSR concerns themselves, and can create a thin wrapper service for type safety.

How to Implement Language Switching Persistence in Vue with SeaText

Direct Answer: Store the selected language in localStorage or a cookie, restore it when the SeaText plugin initializes, and watch for changes to keep the stored value in sync. This gives users a consistent language experience across sessions without extra server round-trips.

SeaText's translation agent serves up to 125 languages from a single page, but the library itself does not persist the visitor's choice. You own that piece: save the locale in localStorage (or a cookie if you need server-side access), read it back before SeaText boots, and update the store whenever the user switches languages. The steps below work with Vue 3, the Composition API, and either Pinia or Vuex for global state.

Prerequisites

A Vue 3 project (Vite, Nuxt 3, or Vue CLI) with the SeaText snippet already added to index.html per the SPA integration guide.
Access to the browser's localStorage API — SeaText's own script uses it for an internal ID, so the permission is already granted.
A state store (Pinia recommended, Vuex 4 supported) to hold the active locale across components.
Basic familiarity with the Composition API watch and onMounted hooks.

Step 1 — Add the SeaText snippet to your SPA entry point

Follow the official SPA instructions: paste the SeaText snippet inside the <body> of index.html or in your framework's bootstrap file. The snippet loads asynchronously and writes an identifier to localStorage; this does not conflict with your own locale key.

<!-- index.html -->
<body>
  <div id="app"></div>
  <script async src="https://cdn.seatext.com/your-project-id.js"></script>
</body>

After adding the snippet, run npm run dev (or npm run serve) and open DevTools → Console/Network to confirm the script loads without errors.

Step 2 — Create a locale store

Define a Pinia store (or Vuex module) that holds the current locale and exposes a method to change it. The store reads the saved value on initialization.

// stores/locale.ts
import { defineStore } from 'pinia'

export const useLocaleStore = defineStore('locale', {
  state: () => ({
    current: 'en' as string,
    supported: ['en', 'es', 'fr', 'de', 'ja', 'zh']
  }),
  actions: {
    init() {
      const saved = localStorage.getItem('seatext-locale')
      if (saved && this.supported.includes(saved)) {
        this.current = saved
      }
    },
    setLocale(locale: string) {
      if (!this.supported.includes(locale)) return
      this.current = locale
      localStorage.setItem('seatext-locale', locale)
      // NOTE: SeaText does not document a public setLanguage() method in its current integration guide.
      // If your dashboard shows an API for programmatic language switching, call it here.
      // Otherwise, rely on SeaText's automatic translation which runs on each page load.
    }
  }
})

Call useLocaleStore().init() once in main.ts before mounting the app.

Step 3 — Build a language switcher component

A small dropdown or button group that calls setLocale. Because the store persists to localStorage, the choice survives page reloads and browser restarts.

<!-- components/LanguageSwitcher.vue -->
<script setup lang="ts">
import { useLocaleStore } from '@/stores/locale'
const localeStore = useLocaleStore()
</script>

<template>
  <select v-model="localeStore.current" @change="localeStore.setLocale(localeStore.current)">
    <option v-for="lang in localeStore.supported" :key="lang" :value="lang">
      {{ lang.toUpperCase() }}
    </option>
  </select>
</template>

Step 4 — Sync SeaText with the stored locale on navigation

SeaText translates on load. In an SPA the page does not reload between routes, so the translation agent will not re-run automatically. The documented integration does not expose a setLanguage method. Two practical workarounds exist:

Full page reload: call window.location.reload() after changing the locale. This triggers SeaText's normal load-time translation with the new locale stored in localStorage.
Hash-based locale: include the locale in the URL hash (e.g., #lang=es) and read it in a navigation guard to decide whether a reload is needed.

Example using a navigation guard with reload:

// router/index.ts
import { createRouter, createWebHistory } from 'vue-router'
import { useLocaleStore } from '@/stores/locale'

const router = createRouter({ /* ... */ })

router.beforeEach((to, from, next) => {
  const localeStore = useLocaleStore()
  const targetLocale = to.query.lang as string | undefined
  if (targetLocale && localeStore.supported.includes(targetLocale)) {
    localeStore.setLocale(targetLocale)
    // Reload so SeaText picks up the new locale on load
    window.location.href = to.fullPath
    return
  }
  next()
})

export default router

If you prefer a component-based approach without router guards, watch the store and reload when the locale changes:

<script setup lang="ts">
import { watch } from 'vue'
import { useLocaleStore } from '@/stores/locale'
const localeStore = useLocaleStore()
watch(() => localeStore.current, (val, oldVal) => {
  if (val !== oldVal) {
    window.location.reload()
  }
})
</script>

Step 5 — Handle server-side rendering (Nuxt 3) if applicable

In Nuxt, localStorage is unavailable during server render. Read the locale from a cookie instead, and hydrate the store on the client.

// composables/useLocale.ts (Nuxt 3)
import { useCookie } from '#app'
import { useLocaleStore } from '@/stores/locale'

export function useLocaleInit() {
  const cookie = useCookie('seatext-locale', { default: () => 'en' })
  const store = useLocaleStore()
  if (process.client) {
    store.current = cookie.value
  } else {
    // server: seed store from cookie so first paint matches
    store.current = cookie.value
  }
  return store
}

Call useLocaleInit() in a plugin or app.vue onMounted.

Step 6 — Verify persistence across sessions

Open the app, switch to Spanish via the dropdown.
Refresh the page — the UI should stay in Spanish and SeaText should translate content on load.
Close the browser entirely, reopen, and navigate to the app — Spanish remains selected.
Open DevTools → Application → Local Storage and confirm seatext-locale equals es.

How SeaText uses language internally (documented behaviors only)

According to the SeaText integration guide, the snippet loads asynchronously and stores an anonymous identifier in localStorage for analytics and variant tracking. The translation agent supports up to 125 languages. SeaText does not document a public setLanguage method, browser-language detection, or sub-15ms translation rewriting in its current SPA integration documentation. The 15 ms figure appears in SeaText's Google Ads landing-page optimization feature, which rewrites headlines for ad relevance, not for language translation. Your seatext-locale key lives alongside SeaText's internal ID without conflict.

Key facts

Aspect	Detail	Source
Supported languages	Up to 125	S2, S6
Script loading	Async, <15 KB, executes before paint	S1, S4
Local storage usage	SeaText writes an internal ID; your app can write its own keys	S1
SPA integration	Snippet in `index.html` body; works with Vue, React, Angular	S1
Translation trigger	Automatic on load; programmatic switch not documented in integration guide	S1
Cookie alternative	Implementation detail not covered in the source pack	—

Common mistakes

Assuming a setLanguage method exists. The current SeaText SPA documentation does not list this API. Verify in your dashboard or contact support before building programmatic switching.
Using a locale code SeaText doesn't recognize. Stick to ISO 639-1 codes (e.g., en, es, zh) that match your SeaText dashboard languages.
Reading localStorage during SSR. Causes hydration mismatch; use cookies in Nuxt/Next.
Not guarding setLocale against unsupported codes. Leads to blank translations or console errors.

Limitations and when this approach does not apply

If you need the locale on the very first server-rendered HTML (for SEO meta tags), you must use a cookie or edge middleware — localStorage is client-only.
SeaText's programmatic language-switching API is not documented in the public integration guide; verify in your dashboard or contact support if you need it.
This guide assumes you control the Vue codebase. If SeaText is injected via a tag manager you cannot modify, you can still persist the locale but cannot guarantee translation timing.
Without a documented setLanguage method, SPA route changes require a full page reload to trigger SeaText's translation with the new locale.

FAQ

Does SeaText automatically remember the user's language?

No. SeaText detects the browser's navigator.language on first visit, but it does not write a persistent preference. You must store and restore the choice yourself.

Can I use a cookie instead of localStorage?

Yes. Cookies are sent with every HTTP request, so your backend or edge function can read the locale for SSR or personalized responses. Set SameSite=Lax and Secure in production. This approach is not covered in the SeaText source pack but is standard web practice.

What if the user clears browser data?

The locale falls back to the browser language or your default (en in the examples). The next explicit selection will be saved again.

How do I test translations without changing my browser language?

Use the language switcher component, or temporarily hard-code localStorage.setItem('seatext-locale', 'fr') in the console and reload.

Will this work with Nuxt 3's hybrid rendering?

Yes, with the cookie-based composable shown in Step 5. The store hydrates on the client and the middleware/cookie handles the server pass.

Can I persist per-page language overrides?

SeaText translates the whole page at once. If you need different languages on different pages, store a map keyed by route path, but expect a full re-translation on each navigation.

Where do I find my project-specific SeaText snippet?

In the SeaText dashboard under Installation → SPA Integration. The snippet contains your project ID and the async loader.

Is there a documented `setLanguage` API for programmatic switching?

Not in the current public SPA integration guide. Check your SeaText dashboard for API documentation or contact support to confirm whether a programmatic language-switching method is available for your plan.

Verification checklist

[ ] Snippet loads in Network tab with 200 OK
[ ] localStorage.getItem('seatext-locale') returns the chosen code after switch
[ ] Page content updates to the new language after reload (no setLanguage call needed)
[ ] Preference survives browser close/open cycle
[ ] No console errors related to undefined window.seatext.setLanguage

Direct Answer: No TypeScript Types Published in Current Documentation

SeaText does not provide .d.ts files, an npm package with types, or interfaces such as SeaTextConfig, SeaTextService, TranslationParams, or LanguageChangeEvent (source: S1). Integration is achieved by adding the supplied script tag to index.html or the Angular bootstrap file.

How the Documented Integration Works

Step‑by‑Step Angular Setup

Locate the entry point – in a standard Angular CLI project this is src/index.html (source: S1).
Paste the SeaText snippet inside the <body> tag, preferably near the closing </body> so it loads after Angular bootstraps (source: S1).
Run ng serve or ng build. The snippet loads asynchronously; Angular’s build pipeline does not process it (source: S1).
Verify in DevTools – open Console and Network tabs to confirm the script loads without errors and SeaText features appear on the page (source: S1).

What the Snippet Does

Loads asynchronously to avoid blocking page render (source: S1).
Stores a visitor ID in localStorage; ensure your app permits local storage access (source: S1).
Handles cross‑origin scenarios if your Angular app spans multiple domains (source: S1).
Activates SeaText’s AI agents (translation, personalization, A/B testing, bot detection) on the rendered DOM (source: S1).

Implications for TypeScript Projects

No Type Safety from SeaText

Because SeaText provides no .d.ts files or npm package with types, TypeScript cannot type‑check SeaText interactions. Any configuration or event handling you write will be plain JavaScript (source: S1). If you need compile‑time safety, you must author your own declaration file (e.g., seatext.d.ts) that mirrors the snippet’s global object shape.

Angular Zone and Change Detection

The snippet runs outside Angular's zone. DOM mutations SeaText makes (translated text, rewritten headlines, injected variants) will not trigger Angular change detection automatically (source: S1). To react to those changes you must either:

Wrap SeaText callbacks in NgZone.run().
Use ChangeDetectorRef.detectChanges() on affected components.
Observe DOM mutations with a MutationObserver inside a directive.

Server‑Side Rendering (Angular Universal)

The snippet references window and localStorage, so it will throw during server‑side rendering. Guard the snippet with a browser check:

<script>
  if (typeof window !== 'undefined') {
    // SeaText snippet here
  }
</script>

(source: S1).

Comparison: Snippet vs. Hypothetical TypeScript SDK

Criterion	Current Snippet Approach	Hypothetical TypeScript SDK (Not Available)
Installation	Paste script in `index.html`	`npm i @seatext/angular` (Check with the vendor)
Type safety	None (manual `.d.ts` needed)	Full IntelliSense & compile checks (Check with the vendor)
Angular DI integration	No	Injectable `SeaTextService` (Check with the vendor)
Zone awareness	Manual `NgZone` handling	Could emit zone‑safe observables (Check with the vendor)
SSR compatibility	Requires `window` guard	Could provide platform‑agnostic API (Check with the vendor)
Version updates	Automatic via CDN	Controlled via `package.json` (Check with the vendor)

Takeaway: Today you trade type safety and Angular idioms for zero‑install simplicity and automatic updates. If your team values strict typing, wrap the snippet in a thin Angular service you maintain yourself.

Practical Workaround: Minimal Angular Wrapper

Create a small service to encapsulate the global SeaText object and give your components a typed façade:

// seatext.service.ts
import { Injectable, NgZone } from '@angular/core';

export interface SeaTextConfig {
  // Add only the options you actually use
  language?: string;
  autoTranslate?: boolean;
}

@Injectable({ providedIn: 'root' })
export class SeaTextService {
  private get st(): any {
    return (window as any).SeaText;
  }

  constructor(private zone: NgZone) {}

  init(config: SeaTextConfig): void {
    this.zone.runOutsideAngular(() => this.st?.init?.(config));
  }

  onLanguageChange(cb: (lang: string) => void): () => void {
    const handler = (e: any) => this.zone.run(() => cb(e.detail));
    window.addEventListener('seatext:lang', handler);
    return () => window.removeEventListener('seatext:lang', handler);
  }
}

This gives you a single place to maintain types, zone handling, and SSR guards without waiting for an official SDK (source: S1).

Limitations & When This Advice Doesn't Apply

Source limitation: This article reflects only the public documentation pages provided. SeaText may publish TypeScript definitions in a private npm registry, a beta program, or a newer docs version not included here (source: S1).
Enterprise contracts: Custom integrations or dedicated support tiers might include type definitions not shown in public docs. Check with the vendor for details.
Future releases: SeaText's agent architecture (translation, personalization, CRO) could ship an Angular library later. Check the integration guide periodically.

Terminology Quick Reference

SPA snippet: The single <script async src="..."> tag SeaText provides for all client‑side frameworks (source: S1).
AI Agents: Autonomous features (translation, A/B testing, bot protection, personalization) that activate once the snippet loads (source: S2).
localStorage ID: A visitor identifier SeaText stores to maintain session continuity across page views (source: S1).
Zone.js / NgZone: Angular's execution context; code running outside it (like the SeaText script) won't trigger change detection automatically (source: S1).
SSR guard: A typeof window !== 'undefined' check that prevents the snippet from executing during server‑side rendering (source: S1).

FAQ

Does SeaText publish an npm package for Angular?

Not according to the current public documentation. Integration is via a CDN‑hosted script tag only (source: S1).

Can I use SeaText with Angular Universal (SSR)?

Yes, but you must wrap the snippet in a typeof window !== 'undefined' check so it only executes in the browser (source: S1).

Will SeaText's DOM changes break my Angular components?

They won't break components, but Angular won't detect the changes. Use NgZone.run() or a MutationObserver if you need to react programmatically (source: S1).

How do I configure SeaText options in TypeScript?

Pass a plain JavaScript object to the global SeaText.init() function (if exposed) or set data-* attributes on the script tag. Define your own TypeScript interface for autocomplete (source: S1).

Is there a way to get TypeScript types from SeaText support?

Contact SeaText directly. The public docs do not list a types package, but enterprise customers may receive additional artifacts (source: S1).

What's the bundle size impact?

The snippet is under 15 KB and loads asynchronously, so it adds negligible weight to your Angular bundle (source: S1).

Can I run SeaText only on specific routes?

The snippet runs globally once loaded. To limit it, conditionally inject the script tag in a route guard or component ngOnInit and remove it on destroy (source: S1).

Criterion	Visual Editor	Programmatic API
Best fit	Marketing pages, static content, landing pages	Dynamic apps, user‑generated content, automated workflows	Choose visual editor for copy‑heavy pages; choose API for code‑driven translation.
Setup effort	Insert snippet, open editor in dashboard, no code changes	Add API calls in components, handle translation keys, version control	Visual editor needs no developer time; API requires coding effort.
Control / customization	Limited to what the UI exposes (text edits, variant toggles)	Full control over timing, scope, fallback logic, A/B testing	Use API when you need custom logic or complex variant rules.
Maintenance	Updates made in UI propagate instantly; no redeploy needed	Changes require code commits and redeploy	Visual editor speeds up copy tweaks; API ties translation to release cycle.
CI/CD friendliness	Manual step; not suited for automated pipelines	Fits naturally into build scripts, can be triggered on each commit	Choose API for teams that rely on continuous delivery.
Learning curve	Low – point‑and‑click interface	Medium – need to understand API endpoints and data format	Visual editor is accessible to non‑developers; API suits developer teams.

Decision trigger: static vs dynamic content

If your page shows the same copy to every visitor, or only changes via a CMS that non‑technical editors update, the visual editor lets you edit translations directly in the SeaText dashboard. If the copy changes based on user input, API responses, or A/B test variants that are generated at runtime, the programmatic API lets you call SeaText from your Vue components.

Static content includes hero headlines, product descriptions, FAQ sections, and legal text that rarely changes. Dynamic content includes user reviews, search results, personalized dashboards, and any text that comes from an external API after the page loads. The visual editor scans the DOM on initial load. It cannot see strings that appear later unless you trigger a refresh. The API works on demand. You call it whenever a new string appears.

Readiness checklist for the visual editor

Your page contains mostly static marketing copy, product descriptions, or landing‑page sections.
You have a non‑technical team that can log into the SeaText dashboard to make edits.
You can accept that translation updates appear after you publish a variant in the UI, without a code deploy.
Your application already loads the SeaText snippet (see the Key facts table).
You do not need to tie translation changes to a specific Git commit or CI pipeline.
Your Vue app does not heavily rely on client‑side routing that replaces large DOM sections without a full reload.
You are comfortable with the snippet storing an ID in local storage for visitor identification.

Signs to wait before choosing the visual editor

Your Vue app renders content that comes from an external API (e.g., user reviews, search results) and you need those strings translated on the fly.
You run automated tests that expect specific translation keys in the DOM.
Your release process requires every text change to be version‑controlled.
You need to coordinate translation updates with feature flags or A/B experiments that are managed in code.
Your team prefers to keep all translation logic inside the repository for audit trails.
You have strict Content Security Policy rules that block inline scripts or third‑party dashboard connections.

Exception: using both approaches together

Some teams start with the visual editor for landing‑page copy while building the API‑driven flow for user‑generated sections. You can keep the snippet on the page and call the API for dynamic parts, letting the visual editor handle static blocks. This hybrid works when you have a clear split between marketing pages and interactive features.

For example, a SaaS site might use the visual editor for the homepage, pricing page, and help center articles. The same site uses the API inside the dashboard area where users create custom reports, invite teammates, or see real‑time notifications. The snippet stays in index.html. The dashboard components import the API client and call seatext.translate() for each dynamic string.

How the visual editor works

After you add the SeaText snippet to your index.html, the script loads asynchronously. It reads the DOM, collects translatable strings, and sends them to the SeaText dashboard. In the dashboard you can edit each string, create language variants, and preview changes. When you publish a variant, the updated strings are served to visitors without touching your Vue code.

The snippet includes the async attribute, so it does not block page rendering. It stores a unique visitor ID in local storage. This ID lets SeaText serve the correct language variant on repeat visits. The script works with Vue's reactivity system because it mutates text nodes directly after Vue mounts. You do not need to modify your components.

How the programmatic API works

You keep the same snippet for basic page load, but you also import the SeaText API client in your Vue components. The client exposes a function like seatext.translate(key, options) that returns a promise with the translated string. You can call it inside setup() or mounted() hooks, pass variables, and handle loading states. The API respects the same async snippet and local‑storage ID, so you do not need a second script.

Below is a minimal Vue 3 Composition API example. It assumes the global seatext object is available after the snippet loads.

// src/composables/useTranslation.js
import { ref, onMounted } from 'vue'

export function useTranslation(key, params = {}) {
  const translated = ref('')
  const loading = ref(true)
  const error = ref(null)

  async function fetchTranslation() {
    if (typeof window.seatext === 'undefined') {
      // snippet not loaded yet
      await new Promise(r => setTimeout(r, 100))
      return fetchTranslation()
    }
    try {
      const result = await window.seatext.translate(key, { params })
      translated.value = result
    } catch (e) {
      error.value = e
      translated.value = key // fallback to source
    } finally {
      loading.value = false
    }
  }

  onMounted(fetchTranslation)
  return { translated, loading, error }
}

Usage in a component:

<script setup>
import { useTranslation } from '@/composables/useTranslation'
const { translated, loading } = useTranslation('welcome_message', { name: user.name })
</script>

<template>
  <div v-if="loading">Loading…</div>
  <div v-else>{{ translated }}</div>
</template>

This pattern lets you translate strings that come from props, API responses, or computed values. You control when the call fires. You can also batch multiple keys with Promise.all to reduce round trips.

Comparison table for specific use cases

Use case	Recommended approach	Reason
Marketing landing page with fixed copy	Visual editor	Non‑technical editors can update headlines and CTAs without code changes.
Blog or documentation site with static articles	Visual editor	Content changes infrequently; dashboard editing is faster than redeploy.
User dashboard with personalized greetings	Programmatic API	Greeting includes dynamic user name; must translate at runtime.
E‑commerce product listings fed from CMS	Programmatic API	Product titles and descriptions arrive via API; translate on mount.
A/B test variants managed in code	Programmatic API	Variant logic lives in Vue store; API can switch translations per variant.
CI/CD pipeline that validates translation keys	Programmatic API	Tests can assert expected keys exist before deploy.
Multi‑domain SPA with shared snippet	Visual editor + API hybrid	Static header/footer via editor; dynamic app sections via API.

Key facts from SeaText documentation

Fact	Detail
Asynchronous loading	The snippet includes the async attribute for the script tag, ensuring that the SEATEXT AI script loads asynchronously, which helps in maintaining page load performance.
Local storage usage	The script stores an ID in the local storage. Ensure that your application has the necessary permissions to access and use local storage.
Cross‑origin considerations	If your SPA interacts with multiple domains, ensure that the SEATEXT AI script is compatible and does not face cross-origin issues.
SPA integration steps	Integrating the SEATEXT AI JavaScript snippet into your Single Page Application (SPA) involves embedding the provided code into your project. This guide will cover the steps necessary to add this code snippet, ensuring that it integrates smoothly with various SPA frameworks such as React, Vue, and Angular.
Vue.js specific step	Insert the SEATEXT AI snippet within the body tag of your index.html file, or in the equivalent initialization section of your SPA framework. Then build and serve your application using standard commands (npm run serve). Inspect the Console and Network tabs to verify the script loads without errors.
Snippet size	The client script is under 15 KB, executes in under 15 ms before visual paint, and does not cause Cumulative Layout Shift.
Language support	SeaText translates pages into up to 125 languages using the same snippet for both editor and API.

Limitations and when the advice does not apply

The visual editor cannot translate strings that are generated after the initial page load without a full reload or a manual refresh of the variant.
The programmatic API requires developer time to write and maintain translation calls; it does not replace the need for the initial snippet.
Both approaches depend on the browser's local storage being available; if you block or clear local storage, the SeaText ID may be lost and translations may fall back to the source language.
If your SPA is served from multiple subdomains with strict cross‑origin policies, you must verify that the snippet's requests are allowed; otherwise you may see blocked requests in the console.
For server‑side rendered Vue (Nuxt) pages that send HTML to the crawler before hydration, you need to ensure the snippet runs on the client; otherwise search engines see the original language.
The visual editor does not expose granular control over translation timing; you cannot delay translation until a specific user action without custom code.
The programmatic API does not automatically retry failed requests; you must implement your own retry or fallback logic.
Both methods share the same rate limits and quotas defined by your SeaText plan; heavy API usage on high‑traffic pages may hit limits faster than static editor usage.
If you use a strict Content Security Policy that disallows unsafe-inline scripts, the snippet may be blocked unless you add the correct nonce or hash.

FAQ

When should I start with the visual editor?: When your landing pages, marketing copy, or static product descriptions are the primary translation need and you want non‑technical editors to make changes without a code deploy.
Can I switch from the visual editor to the API later?: Yes. Keep the snippet in place, add API calls where you need dynamic translation, and retire the visual editor for those strings once the API covers them.
Does the visual editor affect page load speed?: The snippet loads asynchronously and adds less than 15 KB, so impact on load time is minimal.
What permissions does the API need?: The API uses the same snippet; it only needs network access to the SeaText endpoint and permission to read/write the local‑storage ID that the snippet creates.
Is there a cost difference between the two methods?: Both methods are included in the same SeaText plan; you pay for the number of translated words or page views, not for the choice of editor versus API.
How do I handle translation keys that contain HTML markup?: The API returns plain text. If you need to preserve markup, translate the inner text only and reapply the HTML in your component.
Can I use the API inside a Nuxt 3 server route?: The API runs in the browser. For server‑side translation, call the SeaText REST endpoint directly from your server code using your API key.
What happens if the SeaText service is down?: The snippet and API will fail to fetch translations. Your fallback should be the source language string. Implement a timeout and fallback in your composable.

Symptoms of Hitting Site Limits

If you manage more than one Thinkific site, you might notice that after adding a second site, certain SeaText features don’t work as expected. Common signs include: a new site not appearing in your SeaText account dashboard, AI agents not activating on the additional site, or seeing error messages when trying to configure agents for a site beyond your plan’s limit. Some users also report that bots or translation features only work on the first site they added.

How a Thinkific site is linked to SeaText

Each Thinkific site connects to SeaText through a unique JavaScript snippet. You copy this code from your SeaText account and paste it into the Thinkific site's code area. The integration page (source S1) explains: go to your Thinkific admin dashboard, select Settings, then Code & Analytics, and paste the snippet in the Site Footer Code field. After saving, you must visit the site and stay on the page for at least 40 seconds. This activates the AI and links the site to your account. If the site does not appear after 10 minutes, contact SeaText support.

What counts as a separate site

Each Thinkific domain or subdomain you manage is treated as a separate site. This includes different branded sites under the same Thinkific account. If you use the Thinkific Plus Portal to manage multiple websites, each one needs its own SeaText integration. The same rules apply: each site gets its own snippet, activation, and configuration. There is no way to share a single integration across multiple domains.

Per-site integration and activation

You must install the SeaText code on every Thinkific site individually. The process is the same for each: copy the snippet from SeaText, paste it into the Thinkific site's code section, and then visit the site for at least 40 seconds. Activation is per site. If you skip this step, the site will not appear in your SeaText dashboard. The 40-second visit is critical—it tells SeaText that the site is live and ready. After activation, wait five minutes for the site name to appear at the top of the SeaText page. If it does not, contact support.

How agents and features behave across sites

Most SeaText agents are configured per site. For example, the Google Ads Landing Page Agent, Website Translation Agent, and Bot Protection Agent each need to be set up separately for each domain. This means you may need to duplicate settings, language preferences, and targeting rules. Features like headline rewriting or visitor source matching also apply per site. If you activate an agent on one site, it does not automatically activate on others. Check your plan details to see if all agents are available on all sites.

Choosing or upgrading your plan

Your SeaText plan determines how many sites you can manage. Lower-tier plans may include a limited number of sites. To add more sites, you may need to upgrade. Visit the SeaText pricing page to compare plan options. If you are already on a plan that supports multiple sites, ensure each site is properly integrated. If you exceed your plan's site limit, new sites may not activate, or existing sites may stop receiving updates. The recommended solution is to upgrade to a higher tier that matches your needs.

Corrective Actions to Manage Multiple Sites

If you need to run several Thinkific sites under one SeaText account, start by checking your current plan. Compare SeaText plans and site limits to see which tier fits. If your plan is below the needed site count, upgrade. If your plan supports multiple sites but a site does not appear, verify the integration snippet and activation. Check that the code is pasted correctly and that you visited the site for 40 seconds. If the problem persists, contact SeaText support. They can confirm your plan's site limit and help with activation.

Practical workflow for multiple sites

To manage multiple Thinkific sites efficiently, follow these steps: 1) List all domains you want to connect. 2) For each site, copy the unique JavaScript snippet from SeaText. 3) Paste the snippet into each Thinkific site's Code & Analytics section. 4) Visit each site and stay for at least 40 seconds. 5) Wait five minutes and check the SeaText dashboard for all sites. 6) If any site is missing, double-check the code and activation, then contact support. 7) Configure agents per site as needed. This workflow ensures each site is properly linked and active.

Limitations and Considerations

Beyond plan caps, managing multiple sites means repeating integration and configuration steps for each one. Features like Google Ads intent matching or visitor source rewriting may require separate setup per domain. This increases time and complexity. Performance is generally not affected, but very large numbers of sites (e.g., dozens) might require a custom plan. Each site is independent, so you must manage settings individually. The advice in this article applies to Thinkific sites that are separate domains. If you use subdomains, the same per-site integration rules apply.

Frequently Asked Questions

Why does SeaText limit the number of sites I can manage?

SeaText tiers are designed to match usage scale. A site limit ensures fair resource allocation and support for each customer. Higher plans include more sites and additional features.

How do I add another Thinkific site to my SeaText account?

Install the integration code on the new site: copy the JavaScript snippet from SeaText, paste it into the Thinkific site's code section, and then visit the site for at least 40 seconds to activate it.

What happens if I exceed my plan’s site limit?

You may be unable to activate additional sites, or existing sites beyond the limit might stop receiving SeaText AI updates. Upgrading your plan is the recommended solution.

Can I use the same SeaText account for multiple Thinkific sites under different brands?

Yes, as long as your plan allows multiple sites. Each site is treated independently, so you can manage different brands from one account.

Do I need to install the integration code on each Thinkific site separately?

Yes. Each site requires its own unique JavaScript snippet. You must also activate each site by visiting it after installation.

Will all AI agents work on every site?

Agents are typically configured per site. You may need to enable and set up each agent individually for each domain. Check your plan details to see if all agents are available on all sites.

How can I upgrade my plan to support more sites?

Visit the SeaText pricing page to compare plans. Choose a tier that includes the number of sites you need, then upgrade from your account dashboard.

Quick Answer: Professional and Agency Plans Are the Typical Multi-Site Options

If you manage more than one Thinkific site, Professional or Agency is the expected fit. Starter plans usually support one Thinkific site. This is the typical plan structure, not a documented guarantee. The source pack does not include a SeaText feature matrix with site limits. Confirm current plan limits on SeaText's pricing page or with sales before you commit.

Plan tier	Thinkific site limit	Multi-site management	Best for	Verify with sales
Starter	Usually 1 site	Expected: not designed for multiple sites	One course creator with one school	Check with the vendor
Professional	Expected: multiple sites	Expected: yes	Businesses with 2-5 Thinkific sites	Check with the vendor
Agency	Expected: multiple sites	Expected: yes, with client workspaces	Agencies managing Thinkific sites for clients	Check with the vendor

Conditional recommendation

One Thinkific site: Starter may be enough. Confirm that your plan includes the Thinkific integration.
Two to five Thinkific sites: Professional is the typical starting point. Confirm multi-site support first.
More than five sites or client work: Agency is usually the better fit. Ask about client-separated workspaces.

Why Plan Tiers Matter for Multi-Site Thinkific Management

Every Thinkific site needs its own SeaText JavaScript installation. The integration guide (S1) is written for one site. If your plan only allows one connected domain, a second site cannot activate. That is why site limits are the first thing to check.

Thinkific does not bundle multiple schools into one standard account. You need a valid Thinkific plan for each school. SeaText's plan tier decides how many of those schools you can connect to one SeaText account. The two systems work together.

A wrong plan choice creates a blocked rollout. You might install the code, wait for activation, and find that the second domain is not accepted. Sales can tell you the exact limit before you install anything.

How SeaText's JavaScript Installation Works Per Site

The SeaText Thinkific integration uses a JavaScript snippet. Copy the code from the integration page (S1). In Thinkific, open Admin Dashboard, go to Settings, select Code & Analytics, and paste the code into Site Footer Code. Save the change.

Next, link the site to your SeaText account. Add the website address in the format www.example.com (S1). Then visit the site once and stay on the page for at least 40 seconds. This activates the AI and links it to your account.

Wait at least five minutes. Your website name should appear next to the SEATEXT logo. If it does not appear after 10 minutes, contact support (S1). This is the only installation flow in the source pack.

Repeat this process for each Thinkific site. The guide does not show a bulk installer or a multi-domain connector. Plan for one code installation, one URL submission, and one activation visit per site.

How Variants and Reports Are Separated Across Domains

SeaText creates content variants for testing and translation. The Variants Edit panel lets you select the URL and language you want to edit (S1). That means variants are tied to a specific URL.

Reports track results by page, keyword, and version (S2). If each Thinkific site has its own domain, each domain should have its own set of variants and reports. The source pack does not show a multi-site dashboard, so confirm this separation with sales.

Separation matters when you run two brands. You do not want a French translation from Brand A to appear on Brand B. You also do not want A/B test data pooled across unrelated audiences. Ask: "Are variants and reports isolated per domain?"

Thinkific's Own Per-Site Plan Requirements

Thinkific treats each site as a separate product. Thinkific's help center says that an additional Thinkific site requires a separate paid plan. Multi-environment management is a Thinkific Plus feature. These are platform rules, not SeaText rules.

This changes the cost calculation. Even if SeaText's Professional plan covers all of your sites, you still pay Thinkific for each school. The number of SeaText sites you can connect does not reduce your Thinkific bill.

Check your Thinkific plan before counting sites. A single Thinkific account may not allow you to create a second school unless you upgrade. The external links at the bottom of this article point to Thinkific's support pages.

Cost Trade-Offs for Multi-Site Setups

Multi-site management has two cost layers: SeaText and Thinkific. The SeaText subscription covers the AI agents, variants, reports, and the connection to your sites. The Thinkific subscription covers the course platform for each school.

If Starter only allows one site, a second site forces an upgrade or a second SeaText account. A Professional or Agency plan may consolidate multiple sites under one invoice. This can lower the per-site SeaText cost.

Thinkific's per-site pricing remains the same. You still pay for each school. The main saving is in SeaText's platform fee, not in Thinkific's fees.

Ask sales whether multi-site pricing is per site or per account. Ask whether there is a volume discount for agencies. The source pack does not mention any multi-site discount.

Decision Criteria for Choosing a SeaText Plan

Criterion	What to verify	Why it matters
Number of Thinkific sites	Count every domain you need to connect	Each site needs its own JavaScript install and activation
SeaText plan site limit	Check pricing page or ask sales	Starter may stop at one site
Variant isolation	Confirm variants and translations are per URL	Prevents brand and language crossover
Report separation	Ask if analytics are split by domain	Keeps conversion data clean
Billing structure	Ask if multiple sites share one invoice	Affects finance and client cost tracking
Agency features	Ask about client-separated workspaces	Useful when managing client schools

Practical Setup Workflow for Two or More Thinkific Sites

List every Thinkific domain you need. Include test and production schools.
Confirm your SeaText plan allows that many sites. Use the pricing page or sales.
Install the SeaText JavaScript in each Thinkific site. Use Settings → Code & Analytics → Site Footer Code (S1).
Add each website address to SeaText in the required format, www.example.com (S1).
Visit each site and stay for at least 40 seconds to activate it (S1).
Wait at least five minutes. Check that each site name appears next to the SEATEXT logo (S1).
Open the Main AI Hub and activate the agents you need for each site (S1).
Go to Variants Edit and select the correct URL and language for each school (S1).
Run a test on every domain. Check headlines, translations, and reports.

Do not assume one activation covers all sites. The source pack shows a per-site flow.

Pre-Purchase Verification Checklist

Use these questions before you choose a plan:

Does the Starter plan include the Thinkific integration? Does it limit me to one site?
Does the Professional plan allow multiple Thinkific sites under one SeaText account?
Does the Agency plan include client-separated workspaces and consolidated billing?
Are variants, translations, and reports isolated by domain?
Can I run a trial with a second Thinkific site before upgrading?
What happens if I exceed the site limit on my plan?

SeaText's pricing page is linked from the integration page (S1) and other site pages. You can also use the "Book an Enterprise Demo" form (S7) to ask for exact plan details.

Limitations of This Analysis

The source pack does not document explicit site limits for Starter, Professional, or Agency plans.
The Professional and Agency multi-site answer is the expected and typical plan structure, not a confirmed guarantee.
SeaText's public pages in this source pack do not include a full plan feature matrix.
Thinkific's per-site plan rules are separate from SeaText's licensing.
Pricing and plan limits can change. Always confirm with SeaText before purchasing.

Frequently Asked Follow-Up Questions

Can I use one SeaText account for multiple Thinkific sites today?

The source pack does not show a multi-site dashboard. Professional and Agency plans are the expected options. Confirm with SeaText sales.

Does each Thinkific site need its own SeaText JavaScript snippet?

Yes. The integration guide (S1) is per site. Copy the code, paste it into that site's footer, save, and activate it.

Will SeaText's AI agents share learning across my Thinkific sites?

Not documented. Variants are edited by URL and language. Ask sales whether AI learning is isolated per domain.

What happens if I exceed the site limit on my plan?

Unknown from the source pack. Typical SaaS behavior is to block the next site until you upgrade. Ask sales before you hit the limit.

Is there a volume discount for multiple Thinkific sites?

Not mentioned in the source pack. Ask about multi-site or agency pricing during the demo.

Can I manage Thinkific and non-Thinkific sites under the same SeaText plan?

SeaText's JavaScript can be installed on any website (S1, S2). The plan limit would apply to all connected domains. Confirm the total domain count with sales.

Why Switching Without Logging Out Matters

If you manage more than one Thinkific school, you know how easy it is to mix them up. A student asks a question about Course A, while you are working on Course B. You open the wrong dashboard, change the wrong setting, and only notice later. A site selector reduces that risk by making the active site visible and easy to change.

Logging out and logging back in creates friction. You must remember which email belongs to which SeaText account. You must type your password again. If you use two-factor authentication, you must wait for a code. Every extra step makes it more likely that you will lose focus or open the wrong site.

Switching without logging out also helps you move between tasks quickly. You can compare the AI settings on two schools, copy a headline idea from one to another, or check whether a new school has been linked. The selector keeps you inside one dashboard, so you spend less time on account management and more time on course content.

Expert perspective: The site selector separates account-level login from site-level context. You are logged in to SeaText once. The dashboard then changes which Thinkific school is active. This is useful for anyone who runs multiple schools under one SeaText account.

Switching vs. Logging Out: What Changes

The main difference is simple. Logging out ends your SeaText session. Using the selector keeps it active. That one difference changes how you work.

Action	Log out and log in again	Use the site selector
Re-enter email and password	Yes	No
Wait for a login code	Yes, if two-factor authentication is on	No
Time to switch	Usually 30 seconds or more	A few seconds
Active SeaText session	Ends	Stays active
Dashboard after switch	Opens the default view	Opens the selected school

Use the selector if you switch schools often. Use logout if you share a computer or need to change SeaText accounts. The table matters when you work across several schools every day. A small time saving adds up. More importantly, the selector makes it clear which school you are looking at. You can check the site name in the header before you edit anything.

How the Site Selector Works

The site selector is a dropdown in the SeaText top navigation bar. It appears after you link more than one Thinkific site. It shows the name of each linked school. When you pick a school, the dashboard reloads with that school's data and AI configuration. Your SeaText login remains active, so you do not need to type your password again.

SeaText header site selector dropdown showing linked Thinkific schools — The site selector dropdown in the SeaText header lists every linked Thinkific school.

Each Thinkific school must be linked to SeaText before it can appear in the selector. The linking process is the same for every site. You add the SeaText JavaScript snippet to the school's footer, visit the school once, and wait for the site name to appear next to the SeaText logo.

Before You Can Use the Site Selector

You need three things before the selector is available:

An active SeaText account. You need a registered account to access the dashboard.
At least two linked Thinkific sites. The selector is not needed when only one site is connected.
The Thinkific integration installed on each site. The JavaScript snippet must be in the Site Footer Code field.

To link a site, follow the SeaText Thinkific integration guide. Copy the JavaScript code provided by SeaText. In Thinkific, go to Settings, then Code & Analytics. Paste the code in the Site Footer Code field and save. Then use the SeaText form to add your website address in the format www.example.com.

Next, visit your Thinkific site once and stay on the page for at least 40 seconds. This activates the AI and links the site to your account. Wait at least five minutes. The site name should appear next to the SeaText logo at the top of the page. If you do not see it after 10 minutes, contact SeaText support.

Repeat this process for each additional Thinkific school. Once SeaText recognizes two or more schools, the selector appears in the header.

Step-by-Step: Switch Between Thinkific Schools

Log in to your SeaText account at seatext.com.
Find the site selector dropdown in the top header. It usually shows the current site name.
Click the dropdown to see the list of linked Thinkific schools.
Select the school you want to work with.
Wait a moment for the dashboard to update.
Check the site name in the header to confirm you are on the right school.

That is the full process. There is no separate mode, no extra button, and no need to open a new tab.

Managing Multiple Thinkific Schools with SeaText

The selector is most useful when you manage several schools for yourself or for clients. You might run a course library, a membership site, and a client project. Each school can have different pages, different offers, and different AI agents.

Use the selector as your starting point for any task. Need to check the AI settings on School B? Select School B. Need to review content on School C? Select School C. The dashboard then shows the pages and configuration for that school.

Active AI agents are part of each site's configuration. SeaText's Main AI Hub lets you activate AI on your preferred pages and adjust parameters under Configuration. When you switch to another school, the dashboard shows that school's AI setup. To review or change agents on the previous school, select that school again.

Keep multiple linked sites organized by using clear Thinkific school names. SeaText displays the school name from Thinkific in the selector. If you manage three schools with similar names, update the names in Thinkific so you can tell them apart.

You can also create a simple routine. Before switching, note which school you are leaving. After switching, confirm the name in the header. This habit prevents small mistakes like editing the wrong lesson or activating an AI agent on the wrong site.

Troubleshooting the Site Selector

I do not see the selector. Check that at least two Thinkific sites are linked to your SeaText account. If only one site is linked, the selector may be hidden. Confirm the JavaScript snippet is installed on each site.

A new school is missing from the list. Return to the Thinkific integration steps for that school. Visit the school and stay for at least 40 seconds. Wait five minutes for the site name to appear next to the SeaText logo. If it still does not appear after 10 minutes, contact SeaText support.

The dropdown shows the wrong name. SeaText uses the school name from your Thinkific settings. Update the school name in Thinkific if the selector shows an old or unclear name.

I switched but the dashboard looks the same. Check the site name in the header. If it did not change, refresh the page and try again. If the issue continues, contact SeaText support.

I want to add another school. Repeat the linking process for the new school. Once it is linked, it should appear in the dropdown automatically.

Limitations and When the Selector Doesn't Apply

The selector only works for Thinkific sites that are already linked to your SeaText account. It does not work inside the Thinkific admin panel. It does not link new sites by itself.

The selector also works within one SeaText account. If you have two separate SeaText accounts, the dropdown will not show sites from the other account. Log out of one account and log in to the other to see those sites.

The selector changes which school is active in the SeaText dashboard. It does not change user roles or permissions inside Thinkific. A visitor's experience on your Thinkific site is not affected by the selector.

Frequently Asked Questions

Can I switch between Thinkific sites on the mobile version of SeaText?

Yes, the site selector is part of the SeaText header. On a small screen, you may need to open the main menu first. If the dropdown is hard to use on your phone, use a laptop or desktop for multi-site work.

What if I don't see the site selector?

Make sure you have linked at least two Thinkific sites. Verify that the JavaScript snippet is installed in each site footer. Also confirm that you are logged in to the correct SeaText account.

Does switching sites log me out of Thinkific itself?

No. Switching sites in SeaText does not affect your Thinkific session. You remain logged in to Thinkific separately.

How do I add a new Thinkific site to the selector?

Follow the same integration steps: add the SeaText snippet to the new site, visit the site for 40 seconds, and wait for the site name to appear next to the SeaText logo. The new site should then appear in the dropdown.

Can I rename the sites in the dropdown?

SeaText uses the site name from your Thinkific school. To change the display name, update the school name in your Thinkific settings.

What happens to my active AI agents when I switch?

Each site keeps its own AI configuration. The selector changes which site's configuration is shown. Agents stay with the site where they were activated. Switch back to that site to edit or pause them.

Is there a limit to how many times I can switch?

You can switch as often as needed while your SeaText session is active. The dropdown lists every linked school, and the selector does not add extra login steps.

Next Steps to Connect Your Thinkific Schools

If you have not linked your Thinkific sites yet, start with the Thinkific integration guide. Install the snippet on the first school, visit the school, and wait for the site name to appear. Repeat for each additional school. Once two or more schools are linked, the site selector will appear in the SeaText header.

How SeaText Connects to a Thinkific Site

SeaText connects through a JavaScript snippet. You place that snippet in the Thinkific admin area. The official integration guide gives a clear sequence.

Copy the JavaScript code from your SeaText account.
In Thinkific, open Settings and then Code and Analytics.
Paste the code into the Site Footer Code field.
Click Save.
Add your website address in the linking form so SeaText knows which school should be linked to your account.

After the code is saved, the connection is not live yet. The guide says you must visit the site once and stay for at least 40 seconds. That visit activates the AI and links it to your account. Wait up to ten minutes for the site name to appear next to the SEATEXT logo.

Each Thinkific school is a separate website. That means the same installation cycle must be repeated for every school. If you run three schools, you do the process three times.

What SeaText Records on Each Connected School

Once a school is connected, SeaText tracks visitor behavior on that domain. The platform says it tracks results by page, keyword, and version. It also tracks results by language and market, and by traffic source. That gives you a page-level view of what changed and what converted.

For paid traffic, SeaText checks for signs of bots or invalid clicks. It saves a record of each suspicious session and builds a report you can submit to Google, Meta, TikTok, or Reddit. These bot findings are tied to the paid session that produced them.

Version data is also per URL. In the Variants Edit panel, you select a URL and a language. You can review, create, or edit translations for that specific page. You are not editing a global version library.

Why Analytics Stay Separate Across Thinkific Sites

SeaText is installed per website. The code runs on the school's own domain. The linking form asks for one website address at a time. There is no shared collector that merges Thinkific schools into a single profile.

This separation matters for interpretation. A combined roll-up can hide problems. If School A earns $10,000 and School B loses money, a blended number can make the business look fine. Separate data forces you to see each school's real performance.

Separation also matters for testing. A headline variant that wins on School A won the test on that domain. School B may have different courses, prices, and visitors. You cannot assume the same result will appear there.

Use this decision rule: if you need to improve one school, use that school's reports. If you need to compare schools, use the same metric in each school's report and place them side by side.

How to Verify Each Thinkific School Is Connected

Before you trust the numbers, confirm that the connection is active. Use this diagnostic sequence when a school does not show up in your account.

Open Thinkific and go to Settings, then Code and Analytics.
Confirm the SeaText snippet is still in the Site Footer Code field.
Open the live school page in a normal browser window.
Stay on the page for at least 40 seconds. This activates the link.
Wait five to ten minutes.
Return to SeaText and check the area next to the SEATEXT logo at the top of the page.
If the school name is not there, contact SeaText support. The guide says a missing name may mean an installation issue.

Check the URL format too. The SeaText linking form asks for a website address in the format www.example.com. If you enter one format and Thinkific uses another, the connection may not appear. Use the exact domain you plan to track.

Practical Workflow for Multiple Thinkific Schools

Most people run multiple Thinkific schools for different audiences or product lines. A simple workflow keeps the process manageable.

List every school domain and its owner in a spreadsheet.
Install the SeaText snippet on each school.
Complete the activation visit for each school.
Confirm each site appears in your SeaText account.
Review reports one school at a time.
Make changes per school, not across all schools.

Which approach fits you? If you run one brand with one sales page, single-school reporting is simple. If you run a multi-brand network, you need a clear naming system. Use domain names that match your Thinkific school names so you always know which site you are viewing.

How to Decide If Per-School Reporting Is Right for You

Per-school reporting is not a flaw. It is a choice that supports clean data. The right setup depends on how you make decisions.

Choose per-school reporting when you need to judge each offer, campaign, or market on its own. That is the standard SeaText model.

Ask these questions before you try to combine data:

Do the schools share the same product and price? If not, a blended conversion rate may be misleading.
Do the schools share the same ad budget? If not, you need separate revenue numbers.
Does your leadership team report by brand or by total? If by brand, per-school reports are enough.
Do you need one number for an investor or a board? Then you need an external roll-up.

Combine manually only when the business question is about the whole portfolio.

Limitations and Ways to Get Consolidated Data

SeaText does not offer a standard cross-site roll-up report. You cannot see total conversions across every Thinkific school in one native view. This is by design because each school is a separate installation.

The main limitations are:

No combined dashboard in standard reports. Each connected website appears on its own.
Tests stay on the URL where they run. The Variants Edit panel works by URL and language.
Bot evidence is tied to the session. A refund-ready report describes one suspicious visit on one site.
No shared translation set. You choose languages and edit variants for each school separately.

If you need consolidated numbers, use a workaround. The most reliable path is to design your external reporting first. Use consistent campaign parameters on every school. For example, always tag paid links with the same utm_source, utm_medium, and utm_campaign structure. Then your existing analytics platform can group the data.

You can also collect each school's SeaText metrics manually and combine them in your own spreadsheet. That is more work, but it keeps the source data separate and auditable.

For larger portfolios, talk to SeaText support. Ask whether a custom enterprise view or reporting export is available for your plan. Do not assume a feature exists because a competitor offers it. Check with the vendor for your specific contract.

Key Facts at a Glance

Aspect	Detail
Installation method	JavaScript in Thinkific Site Footer Code
Activation visit	Stay on the page for at least 40 seconds
Dashboard confirmation	Site name appears next to the SEATEXT logo
Tracking scope	Per page, keyword, version, language, market, traffic source
Bot reporting	Refund-ready report for suspicious paid sessions
Cross-site roll-up	Not available in standard reports

Frequently Asked Questions

Can I see one combined dashboard for all of my Thinkific schools in SeaText?

No. The standard dashboard shows connected websites separately. Combine the numbers yourself if you need a blended view.

Does a winning headline variant copy to my other schools?

The source material does not describe a copying feature. Variants are edited by URL and language. You can study a result on one school and manually recreate it on another school.

Do I need a separate SeaText account for each school?

No. One account can link multiple website addresses. Add each school through the linking form after you install the code. Check with the vendor if your plan limits the number of connected sites.

Why does my school not show up after installation?

Check the snippet, visit the live page once for 40 seconds, and wait five to ten minutes. Then look next to the SEATEXT logo. If it still does not appear, contact support.

How do I compare performance between schools?

Pull the same metric from each school and place the reports side by side. For paid campaigns, use consistent UTM parameters so an external analytics platform can group the data.

Does bot protection data combine across schools?

No. Bot evidence is tied to paid sessions on a specific website. There is no standard shared bot-evidence view across schools.

Key Terms

School: A single Thinkific site that uses a subdomain or custom domain.
Site Footer Code: The Thinkific field where you paste the SeaText JavaScript snippet.
Variant: A translated or rewritten version of a page element that SeaText tests.
Refund-ready report: A SeaText document used to claim refunds for invalid paid clicks.
Linking form: The SeaText field where you enter your website address to connect it to your account.

Criterion	Single Agency Account	Separate SeaText Accounts per Client
Setup effort	One login, add each Thinkific site via integration panel	Create and bill separate accounts; client owns their account
Site limit impact	All client sites count toward your plan's cap	Each account has its own limit; no cross‑client pooling
Client data access	You control permissions; can revoke instantly	Client owns data; you need their login or shared access
Billing simplicity	One invoice; you allocate costs internally	Client pays directly; cleaner for resale models
Role‑based control	Granular permissions per site per team member	Limited to each account's own user roles
Best fit	Agencies retaining management responsibility	Agencies handing off ownership; white‑label resellers

How Site Slots Are Consumed

Every Thinkific school you connect uses one site slot on your SeaText plan. The integration guide shows that after you paste the JavaScript snippet into the site's footer code field and visit the site for at least 40 seconds, the site name appears next to the SeaText logo within five to ten minutes. That activation confirms the slot is occupied. If your plan allows ten sites and you manage eight clients, you have two slots left. Adding a ninth client consumes another slot. Exceeding the limit requires upgrading the plan or removing an existing site.

Onboarding a New Client Site

Log into your SeaText agency dashboard.
Open the integrations panel and copy the JavaScript snippet.
Log into the client's Thinkific admin → Settings → Code & Analytics → Site Footer Code.
Paste the snippet and click Save.
Visit the client's live Thinkific site once, stay at least 40 seconds.
Wait up to 10 minutes for the site name to appear next to the SeaText logo in your dashboard.
Configure agents such as translation, personalization, or bot protection for that site.

The same snippet works for every Thinkific site you connect; the domain identifies the site during the activation visit.

Managing Team Permissions

Agency plans provide role‑based access per connected site. You can invite team members and assign them to specific client sites. A copywriter working on Client A's translations cannot see Client B's bot‑protection reports unless you grant that permission. This isolation helps when you handle competing clients or clients with strict confidentiality requirements.

Offboarding and Migration

If a client wants to move to their own SeaText account, remove the site from your agency dashboard. That action frees a site slot immediately. The client then creates a new SeaText account and repeats the integration steps. Historical data such as A/B test results and translation memories remain in the original account unless you export them manually. Plan for this hand‑off early to avoid data loss.

Cost Planning

Because each client site consumes a slot, forecast the number of active clients against your plan's site limit. If you expect growth, choose a plan with enough headroom to avoid frequent upgrades. Remember that billing is a single invoice for the agency; you allocate costs to clients internally. If a client prefers direct billing, the separate‑account model may be simpler.

When This Approach Doesn't Work

If a client requires full ownership of their SeaText account for compliance, future portability, or direct billing, the single‑agency‑account model fails. Agencies managing more sites than their plan allows must upgrade or prune sites. The integration guide advises contacting support if a site does not appear after 10 minutes, which usually means the snippet did not fire — often because Thinkific's footer code field did not save correctly or the activation visit did not register.

Key Facts

Fact	Detail
Integration method	JavaScript snippet in Thinkific Site Footer Code
Activation requirement	Visit site once, stay 40+ seconds
Connection confirmation	Site name appears next to SeaText logo within 5–10 minutes
Agency feature	Role‑based access per connected site
Site counting	Each Thinkific site consumes one site‑slot on your plan
Data isolation	Per‑site: translations, variants, bot reports, personalization rules

FAQ

Can I move a client's Thinkific site to their own SeaText account later?

Yes. Remove the site from your agency dashboard to free a slot, then the client creates their own SeaText account and repeats the integration steps. Historical data stays with the original account unless exported manually.

Does each Thinkific site need a different JavaScript snippet?

No. The same snippet from your agency account works on every Thinkific site you connect. The snippet identifies the site by its domain during the activation visit.

What happens if I hit my site limit mid‑contract?

You cannot add new sites until you upgrade your plan or remove an existing site. Removing a site stops SeaText on that Thinkific school immediately.

Can team members see all client sites by default?

No. Agency plans use role‑based access. You assign each team member to specific sites. A copywriter working on Client A's translations cannot access Client B's bot‑protection reports unless you grant it.

What if the site doesn't appear in my dashboard after 10 minutes?

The integration guide instructs you to contact SeaText support immediately. This usually indicates the snippet didn't fire — often because Thinkific's footer code field didn't save correctly or the activation visit didn't register.

Why Organization Matters for Multiple Thinkific Schools

Each school has its own courses, pricing, and audience. When content from one school mixes with another, analytics become unreliable. Mistakenly showing the wrong headline to a visitor can hurt conversion rates. A clear structure protects data quality and saves time.

Prerequisites: Connect Each Thinkific Site to SeaText

Log in to SeaText and open the Integrations panel.
Select the Thinkific integration.
Copy the JavaScript snippet shown in the panel.
In Thinkific, go to Admin Dashboard → Settings → Code & Analytics → Site Footer Code and paste the snippet.
Save the changes.
Visit the site and stay on the page for at least 40 seconds. This dwell time activates the AI.
Wait five minutes. The site name appears next to the SeaText logo, confirming the link.

These steps are described in SeaText’s integration guide (source S1).

Step 1: Adopt a Naming‑Convention Template

A naming convention gives every variant a predictable identifier. Use a short school code, a content type, and a descriptive suffix.

Template

SCODE_CONTENTTYPE_Description

Where:

SCODE – two‑letter school code (e.g., EN for English Academy, FR for French Academy).
CONTENTTYPE – HEAD for headline, CTA for call‑to‑action, TRANSL for translation, AB for A/B test variant.
Description – brief human‑readable note (e.g., WelcomeBanner).

Examples

EN_HEAD_WelcomeBanner
FR_CTA_EnrollNow
EN_AB_PricingTestA
FR_TRANSL_CourseDesc

All SeaText variants appear in the Variant list. The prefix makes it easy to filter by school using the search box.

Step 2: Keep Translations Separate per School

SeaText’s Translation Agent can generate up to 125 language versions. For each Thinkific school, create translation variants that follow the naming template.

Example for a French‑language course description on the French Academy:

FR_TRANSL_CourseDesc_French

When you open the Variant editor, select the URL that belongs to the French school, then choose the target language. SeaText will auto‑translate and let you edit the result.

Because each translation carries the school code, you never edit the wrong language version.

Step 3: Manage A/B Tests Independently for Each School

SeaText’s AI A/B Testing Agent creates variants, runs traffic splits, and reports winners. To keep tests separate, name each test with the school code and a test identifier.

Example:

EN_AB_PricingTestA

FR_AB_PricingTestA

When you launch the test, select the URL that belongs to the appropriate school. SeaText tracks results by page, keyword, and version (source S2). This ensures that traffic from the English school only influences the English test.

Verification Checklist: Confirm That Organization Works

Open the SeaText Variants page.
Enter the school code (e.g., EN_) in the search field.
Confirm that every listed variant starts with that code.
Run a small A/B test on one variant and watch the Results by version chart. Only the selected school’s traffic should appear.
Check the Translation Agent panel for the school’s language list. Verify that each translation variant includes the school prefix.
If any variant is missing the prefix, rename it using the template.

Weekly Maintenance Routine

Regular upkeep prevents drift.

Monday: Review the Variant list for new entries. Rename any that lack the proper prefix.
Wednesday: Open the A/B Testing dashboard. Pause any test that has run longer than its planned duration.
Friday: Export the translation report. Verify that each language version still matches the source school’s URL.
Document any overrides (e.g., a special promotion) in a shared spreadsheet.

This routine keeps naming, translation, and testing data clean.

Common Pitfalls and How to Avoid Them

Skipping the 40‑second activation: The AI remains unlinked and no data appears. Always wait the full dwell time after installing the snippet.
Using generic names: Variants like “Header Test” cannot be filtered. Apply the naming template consistently.
Editing the wrong URL: SeaText’s Variant editor shows the URL at the top. Double‑check before saving.
Forgetting to verify after changes: Run the verification checklist after any bulk rename.

Limitations and When This Approach May Not Fit

The method relies on SeaText’s ability to filter by text search. If you need a true cross‑school experiment (the same variant shown to all schools), create a master variant without a school prefix and duplicate it for each school. Keep the master copy in a separate document to avoid drift.

SeaText does not impose a hard limit on the number of Thinkific sites (source S1). The practical limit is your capacity to manage prefixes and monitor the weekly routine.

Quick‑Reference Table

Item	Details
Integration snippet	Copy from SeaText Integrations → Thinkific and paste into Thinkific footer.
Activation dwell time	Stay on each site for at least 40 seconds after installing the snippet.
Verification wait	Wait five minutes; the site name appears next to the SeaText logo.
Naming prefix	Two‑letter school code (e.g., EN, FR) placed at the start of every variant.
Translation workflow	Use Translation Agent, follow naming template, edit as needed.
A/B testing workflow	Use AI A/B Testing Agent, name variants with school prefix, select school‑specific URL.

FAQ

How often should I audit my naming convention?

Do a quick audit each week during the maintenance routine. Add a new prefix immediately when a new school launches.

Can I run the same A/B test on two schools at once?

Yes. Create a master variant without a school prefix, then duplicate it for each school and give each copy its own prefix. Run the tests separately.

What if the site name does not appear after five minutes?

Check that the JavaScript snippet is correctly placed in the footer. Ensure the page was loaded for at least 40 seconds. If the problem persists, contact SeaText support.

Do I need separate SeaText accounts for each Thinkific school?

No. One SeaText account can manage any number of schools, as long as each site has its own prefix and follows the routine.

Where can I find the JavaScript code for new schools?

In SeaText, go to Integrations → Thinkific. The code is displayed at the top of the page (source S1).

Why Multi-Site Connections Fail

Running multiple Thinkific sites with SeaText increases the chance of connection problems. Each site needs its own JavaScript snippet. If you reuse a snippet, the connection fails. Activation also requires a 40-second visit per site. Miss that step, and the site never links.

Another common issue is expired API tokens. SeaText uses tokens to talk to Thinkific. If a token expires or gets revoked, the site disconnects. Plan limits can also block new sites. If your SeaText plan allows only a set number of sites, you cannot add more until you upgrade or remove one.

Why does this matter? A disconnected site means no data syncs. Your traffic, conversions, and AI-driven content all stop. For businesses relying on multiple Thinkific sites, a single broken connection can hurt revenue and reporting. Troubleshooting quickly saves time and money.

Before You Start: Prerequisites

Before troubleshooting, gather these items:

Your SeaText login credentials
Thinkific admin access for each site
The list of sites you want to connect
Your SeaText plan details (site allowance)

Make sure each Thinkific site is live and publicly accessible. A site behind a password or maintenance mode will not connect. Also confirm that you have the correct JavaScript snippet for each site. You can copy these from the SeaText Thinkific integration page.

If you are unsure about plan limits, check with SeaText support. They can tell you how many sites your plan supports.

How Each Site Is Linked

SeaText connects to Thinkific through a JavaScript snippet. This snippet is unique per site. You paste it into the Thinkific footer code area. Once saved, you visit the site for at least 40 seconds. This activates the AI and links the site to your SeaText account.

After activation, you wait 5–10 minutes. The site name should appear next to the SeaText logo in the dashboard. This confirms the link is working. If it does not appear, the connection failed.

Each site follows this same process. You cannot skip the 40-second visit. The visit must be from a real browser. A bot or automated script will not work.

Common Causes and Fixes

Here are the most frequent reasons a site fails to connect, with fixes:

Cause	Fix
Wrong or missing JavaScript snippet	Copy a fresh snippet from SeaText for that site. Paste it into the Thinkific footer code area. Save and re-activate.
Activation visit skipped or too short	Visit the site and stay for at least 40 seconds. Use a real browser.
Site not publicly accessible	Remove any password protection or maintenance mode. The site must be live.
Expired API token	Remove the site from SeaText dashboard. Add it again as a new site. This generates a fresh token.
Plan limit reached	Check your SeaText plan. If you are at the limit, upgrade or remove an existing site.
Cache or browser issue	Clear your browser cache. Try a different browser or incognito mode.

If the cause is not obvious, start from the first step and work through the sequence. Often a simple re-authentication resolves the issue.

How to Verify Each Site

After you apply a fix, verify the connection. Go to the SeaText dashboard. Look for the site name next to the SeaText logo at the top of the page. If it is there, the site is connected.

You can also check the integration status. In the SeaText dashboard, navigate to the Thinkific integration page. The site should show as active. If it shows as inactive, the connection is broken.

For a deeper check, visit the Thinkific site and look at the page source. Search for the SeaText script. If it is present and not blocked, the code is installed. But the final confirmation is the dashboard.

Repeat this verification for every site you are troubleshooting. Document which sites are working and which are not.

What to Do When a Site Still Will Not Connect

You have tried the steps above, but a site still will not connect. What next? First, double-check that you used the correct snippet for that site. It is easy to confuse snippets when managing multiple sites.

Second, try a different browser or device for the activation visit. Sometimes browser extensions block the script. Use a clean browser without ad blockers.

Third, remove the site from SeaText completely. Wait a few minutes. Then add it again as a new site. Copy a fresh snippet and paste it into Thinkific. Perform the 40-second visit again. This is a full re-authentication.

If none of this works, contact SeaText support. Provide the site URL, the steps you took, and any error messages. The integration guide says to contact support if the site does not appear within 10 minutes. Support can check for deeper issues like server blocks or account errors.

Preventing Future Disconnections

Once all sites are connected, take steps to prevent future problems. Keep a record of each site's snippet. Store them in a secure place. When you need to reinstall, you can copy the correct snippet quickly.

Set a reminder to check the dashboard weekly. Look for any site that shows as inactive. Early detection saves time.

Also, note when you last re-authenticated each site. If you encounter token issues, you will know which sites are due for a refresh. For plan limits, monitor your SeaText account. If you plan to add a new site, upgrade first.

Finally, use the SeaText Thinkific integration page as your main resource. It contains the latest steps and code. Bookmark it for quick access.

Frequently Asked Questions

Why does my Thinkific site not appear in the SeaText dashboard after installation?

Most often, the JavaScript code is missing or incorrectly placed. Check the footer code area in Thinkific, and ensure you visited the site for 40 seconds after saving. Also, wait at least 5–10 minutes for the site to sync.

Can I use the same JavaScript code for multiple Thinkific sites?

No. Each Thinkific site requires its own unique JavaScript snippet from SeaText. Using the same code for multiple sites will cause connection errors.

How long does it take for a site to connect after activation?

Typically within 5 minutes, but it can take up to 10 minutes. If you do not see the site after 10 minutes, contact support.

What if I get an error message when trying to add a site?

Error messages often indicate a plan limit or invalid API token. Check your SeaText account plan to see if you have reached the maximum number of sites. Also, ensure your Thinkific site is active and publicly accessible. If you are unsure about plan limits, check with SeaText support.

Do I need a higher SeaText plan for multiple Thinkific sites?

SeaText plans have site allowances. If you cannot add another site, you may need to upgrade or remove an existing site. Check your plan details or contact SeaText support to confirm.

How do I re-authenticate a disconnected Thinkific site?

Remove the site from the SeaText dashboard, generate a new JavaScript snippet, paste it into the Thinkific footer, and repeat the activation visit. This refreshes the connection.

What if I lost the JavaScript code for a site?

Log into your SeaText account and go to the Thinkific integration page. You can copy the code again for each site. If the site is already connected, you can also find the code in the integration settings.

Factor	Details	What to do
Plan tier	Each tier sets a maximum number of connected Thinkific schools	Review the pricing page for current allowances
Resource usage	Each site consumes dashboard resources, variant storage, and AI agents	Monitor usage in the integrations panel
Site isolation	Variants, analytics, and AI agents are separate per domain	Plan for one slot per distinct Thinkific school
Limit enforcement	Blocked at "Add site" step with upgrade prompt	Upgrade or disconnect an unused site
Legacy plans	Older plans may have different limits	Contact support to confirm your allowance
Enterprise agreements	Custom limits negotiated per contract	Talk to enterprise sales for high-volume needs

What determines your Thinkific site limit

Your SeaText plan tier sets a ceiling on how many separate Thinkific schools you can link to a single SeaText account. This limit exists because each connected site consumes dashboard resources, stores its own variant library, and runs independent AI agents for translation, testing, and personalization. The limit is enforced at the account level, not per user or per domain.

When you attempt to add a new Thinkific site in the SeaText integrations panel, the system checks your current site count against your plan allowance. If you are at the cap, the "Add site" action is blocked and you see a prompt to upgrade or free a slot. The exact number of sites allowed depends on your specific plan. SeaText does not publish fixed numbers in public documentation; they direct customers to the pricing page or support for current details.

How SeaText plan tiers affect site connections

SeaText offers several plan tiers. Each tier is designed for a different scale of operation. The Starter tier suits a single course creator or small business with one school. The Professional tier accommodates growing educators running a few niche schools or a main school plus test sites. The Agency tier fits agencies managing multiple client schools or large organizations with many divisions. The Enterprise tier removes the fixed ceiling in favor of a custom agreement.

These tiers are shown on the SeaText pricing page. The site allowance for each tier can change as SeaText updates its packaging. Always verify the current limit on the pricing page or by contacting support. Do not rely on third‑party articles or older screenshots for exact numbers.

How to check your current plan limit

Log in to your SeaText dashboard.
Open the account menu in the top‑right corner and select Billing & Plan.
Your current tier and its site allowance are displayed next to the plan name.
In the Integrations section, the Thinkific card shows how many sites are already connected and how many slots remain.

If the dashboard does not show a site counter, you are likely on a legacy plan. Contact support to confirm your exact limit. The pricing page also lists the current allowance for each public tier.

What happens when you reach the limit

SeaText prevents the new connection rather than silently failing. You will see an error message such as "Site limit reached for your current plan" with a link to the upgrade page. No data is lost from existing sites, but the new Thinkific school remains unlinked until you either upgrade your plan or disconnect an existing site.

Disconnecting a site removes its JavaScript snippet from the SeaText dashboard and stops AI processing for that domain. Historical variants and test results for the removed site are archived but not deleted. They can be restored if you reconnect the same domain later.

Managing multiple Thinkific sites in SeaText

Each Thinkific school requires its own SeaText JavaScript snippet installed in the site's Site Footer Code field (Settings → Code & Analytics). After pasting the code, you must visit the live site and stay for at least 40 seconds to activate the connection. The dashboard then shows the site name next to the SeaText logo within five minutes.

Once connected, you switch between schools using the site selector in the dashboard header. Analytics, variant libraries, and AI agents are scoped per site, so changes in one school never leak into another. This isolation is why the limit is counted per connected domain, not per account user.

Key facts

Item	Details
Integration method	JavaScript snippet pasted into Thinkific Site Footer Code
Activation requirement	Visit the live site for 40+ seconds after installation
Dashboard indicator	Site name appears next to SeaText logo within 5 minutes
Site isolation	Separate variants, analytics, and AI agents per domain
Limit enforcement	Blocked at "Add site" step with upgrade prompt
Pricing reference	See SeaText pricing page for current tier allowances

Limitations and when this advice does not apply

Legacy or grandfathered plans may have different limits not shown on the public pricing page.
Custom Enterprise agreements can include higher or unlimited sites, but only if explicitly written into the contract.
Subdomains under the same Thinkific school (e.g., courses.example.com and blog.example.com) count as one site because they share a single JavaScript installation.
Test or staging Thinkific sites count toward the limit if you add them as separate integrations.
The limit applies to active connections; archived or disconnected sites do not consume a slot.
SeaText may adjust plan limits at any time; always confirm current numbers before planning expansions.

Frequently asked questions

Can I connect more Thinkific sites by creating multiple SeaText accounts?

Technically yes, but each account requires its own subscription and billing. Managing separate logins, variant libraries, and billing cycles usually costs more than upgrading to a higher tier on a single account.

Does the site limit include non‑Thinkific websites?

Yes. The limit is total connected websites across all platforms (WordPress, Shopify, custom domains, etc.). A Thinkific school uses one slot just like any other site.

What if I only need extra sites for a short campaign?

Upgrade to the next tier for the campaign duration, then downgrade afterward. SeaText prorates billing, so you pay only for the time on the higher plan.

Are there API or bulk‑import options for adding many sites at once?

No. Each site must be added individually through the integrations panel, the snippet installed, and the 40‑second activation visit completed. This manual step prevents accidental mass connections and ensures each domain is verified.

How do I request a custom Enterprise limit?

Use the "Talk to enterprise sales" link on the pricing page or contact support from your dashboard. Provide the number of Thinkific schools you plan to connect and any compliance or SLA requirements.

Will disconnecting a site delete its translation variants and A/B test history?

No. Data is archived and can be restored if you reconnect the same domain. However, you cannot access that data while the site is disconnected.

Overview

SeaText connects to Thinkific sites by installing a JavaScript snippet. The guide (S1) shows the steps for a single site and explains how to repeat them for additional sites. No public source describes role‑based access controls or plan‑tier permission models.

Installation Steps

Copy the JavaScript code provided by SeaText in the Thinkific integration section. In your Thinkific admin dashboard, go to Settings, then Code & Analytics. Paste the code into the Site Footer Code field and click Save. This installs the snippet on the site.

Activation Process

After pasting the snippet, visit the Thinkific site and stay on the page for at least 40 seconds. This visit activates the AI and links the site to your SeaText account. The guide notes that the activation visit must load the page with the snippet.

Connection Confirmation

Wait at least five minutes after the 40‑second visit. Your site name should appear next to the SeaText logo at the top of the integration page. If the name does not show after ten minutes, contact SeaText support.

Multi‑Site Setup

To connect additional Thinkific schools, repeat the installation and activation steps for each site. Add each site URL separately in the SeaText integrations panel. Each site needs its own snippet and its own 40‑second activation visit.

Permissions Information and Next Steps

The Thinkific integration guide (S1) does not cover how to grant team members access to specific Thinkific sites. It does not mention role‑based access control, plan tiers, or site‑level permission settings. For any questions about user permissions, contact SeaText directly to obtain the latest documentation.

FAQ

How do I install SeaText on a Thinkific site?

Copy the JavaScript snippet from the integration guide, paste it into Thinkific’s Site Footer Code under Settings → Code & Analytics, then save.

How long must I stay on the site to activate the connection?

Stay on the page for at least 40 seconds after the snippet loads.

How do I know the site is connected?

After waiting five minutes, look for the site name next to the SeaText logo at the top of the integration page.

Can I connect more than one Thinkific site to the same SeaText account?

Yes. Repeat the installation and activation steps for each site and add each URL separately in the integrations panel.

What should I do if the site name does not appear after ten minutes?

Contact SeaText support for assistance with the installation or activation process.

What page-level targeting means in SeaText

Page-level targeting is a setting inside SeaText that controls which URLs the installed script is allowed to change. The script itself still loads on your Thinkific site, but it only acts on the pages you list. Think of it as a guest list: the script is at the door, but only the URLs you approve get the rewrite.

SeaText calls this the "Activation" step. The integration page describes it as: "Proceed to the Main AI Hub to activate the necessary AI on your preferred pages. Click on 'Configuration' to adjust the AI parameters." The phrase "preferred pages" is the targeting control.

Prerequisites before you set up page targeting

Before you touch the targeting rules, finish the base install. The Thinkific integration page lists the steps in this order:

Copy the JavaScript code from the SeaText dashboard.
Open your Thinkific Admin Dashboard, choose Settings, then Code & Analytics.
Paste the code into the Site Footer Code field and click Save.
Add your website address in the format www.example.com using the link form on the integration page.
Visit your site once and stay on a page for at least 40 seconds to activate the link.
Wait up to 10 minutes for your site name to appear next to the SeaText logo at the top of the dashboard.

If your site name does not show after 10 minutes, the integration page tells you to contact support, because the script may not have installed correctly.

Step-by-step: limit SeaText to specific Thinkific pages

Open the SeaText dashboard and go to the Main AI Hub. This is the same screen you used to confirm the install.
Click "Configuration" next to the AI agent you want to scope. Each agent has its own targeting list, so you can run the Google Ads Landing Page Agent only on sales pages and the Translation Agent on every public page.
Add the Thinkific URLs you want to include. Use the full path, for example www.yoursite.com/courses or www.yoursite.com/pages/checkout. Match the format you used when you linked the site.
Exclude the URLs you want to leave alone. Lesson players, login pages, and the course player iframe are common exclusions. A learner watching a video does not need a headline rewrite.
Save the configuration. SeaText applies the rules on the next page load.
Verify on a real page. Open one included URL and one excluded URL in a private window. The included page should show the SeaText variant; the excluded page should look unchanged.

Which Thinkific pages usually get included

Most course creators turn SeaText on for the pages that carry the buying decision and leave it off for the pages that carry the learning. A common split looks like this:

Include: course landing pages, pricing pages, the homepage, and any long-form sales letter.
Include for translation only: the blog and resource pages, where international readers arrive from search.
Exclude: the course player, lesson pages, login, signup, and checkout. These pages need stable copy so learners do not lose their place.

Common mistakes when scoping SeaText on Thinkific

Targeting the wrong URL pattern. Thinkific course pages often live under /courses/<slug>. If you only add the root, you miss every individual course.
Forgetting the www prefix. The integration page asks for the format www.example.com. If your dashboard uses example.com without the www, the targeting rules may not match.
Turning every agent on everywhere. The Translation Agent and the Google Ads Landing Page Agent serve different jobs. Scoping them separately keeps lesson pages calm.
Skipping the 40-second visit. Without that first visit, the site is not linked, and targeting rules will not fire.

How to verify the targeting is working

Open two browser tabs side by side: one URL you included, one you excluded. On the included page, look for the SeaText variant copy or translation. On the excluded page, the original Thinkific copy should be unchanged. If both pages look the same, re-check the URL spelling in the Configuration panel and confirm the site name shows next to the SeaText logo in the dashboard.

Key facts

Item	Detail
Where the script is installed	Thinkific Admin → Settings → Code & Analytics → Site Footer Code
Where targeting is controlled	SeaText Main AI Hub → Configuration per AI agent
Site link format	www.example.com
Activation visit	Stay on a page for at least 40 seconds
Time to confirm link	Up to 10 minutes for the site name to appear next to the SeaText logo
Optional editing path	Variants Edit in the left panel, then pick URL and language

Limitations to keep in mind

Page-level targeting works on the URLs you list. It does not let you target by visitor segment, device, or traffic source on its own; those controls live in other SeaText agents. Also, because the script is installed in the site footer, it loads on every page of your Thinkific site. Targeting only decides where the AI is allowed to act, not where the script loads. If you want the script itself to skip a page, you would need to use Thinkific's own Code & Analytics controls to exclude that page.

Frequently asked questions

Do I have to install the script on every Thinkific page?

No. The script goes into the Site Footer Code field once, and Thinkific applies it across your site. You then use SeaText's targeting rules to choose which pages the AI agents actually change.

Can I run different agents on different Thinkific pages?

Yes. Each AI agent has its own Configuration panel. You can run the Google Ads Landing Page Agent only on sales pages and the Translation Agent on every public page, for example.

Will SeaText change my course lesson pages?

Only if you add those URLs to the targeting list. Most course creators exclude the course player and lesson pages so learners see stable copy.

What happens if I add the wrong URL format?

The targeting rule will not match, and the page will look unchanged. Re-check the format against the www.example.com style used during the site link step.

Can I edit the variants after targeting is set?

Yes. The integration page points to Variants Edit in the left panel, where you pick a URL and language and then review, create, or manually edit translations.

How long does it take for new targeting rules to apply?

Rules apply on the next page load after you save. If a page still looks unchanged, clear the cache or open the URL in a private window.

What if my site name never appears next to the SeaText logo?

Wait the full 10 minutes first. If it still does not show, the integration page says to contact SeaText support, because the script may not have installed correctly on Thinkific.

Why Use Page‑Specific Rules?

SeaText rewrites headlines, offers, and calls to action in real time. If the script runs on every page, it may alter checkout text, course player UI, or privacy policies, which can confuse buyers or break compliance. By limiting the AI to chosen URLs you keep critical pages stable, reduce risk, and can run focused experiments on high‑traffic funnels. You also avoid wasting AI credits on pages that do not need optimization.

Prerequisites

An active SeaText account.
Admin access to your Thinkific site.
The SeaText JavaScript code already pasted in your Thinkific site footer code (see the Thinkific integration guide).

Step 1: Link Your Website to SeaText

After installing the code, you must link your website. In the SeaText dashboard, enter your website address in the format www.example.com. Then visit your site and stay on the page for at least 40 seconds. This activates the AI and links it to your account. Wait five minutes until you see your website name next to the SeaText logo at the top of the page.

Step 2: Access the Main AI Hub

Once your site is linked, go to the SeaText Main AI Hub. This is where you manage which AI agents run on which pages.

Step 3: Open Configuration

Click on Configuration to adjust the AI parameters. Here you can set up page‑specific targeting rules.

Step 4: Create a Page‑Specific Rule

In the configuration, you can define URL patterns or path rules. For example, you can target all course pages by using /courses/* or a specific landing page by its full URL. The exact interface may vary; refer to the SeaText documentation for pattern syntax.

Step 5: Activate AI on Selected Pages

After setting the rule, proceed to activate the AI agents you want on those pages. SeaText will then rewrite headlines, offers, or CTAs only on the matched pages.

Step 6: Verify the Rule

Visit the targeted pages and check that the SeaText changes appear. Use the SeaText dashboard to see which URLs are active. If changes do not appear, revisit the configuration and ensure the URL pattern is correct.

Choosing Pages to Target

Start by listing the URLs that drive revenue: sales pages, course landing pages, webinar registration pages, and upsell funnels. Use simple path patterns like /courses/* to capture all course pages, or /landing-page-slug for a single page. Test the pattern on a staging environment or a low‑traffic page first. Once the rule works, expand to the full set. Avoid patterns that match the checkout path (/checkout/*) or the course player (/player/*) unless you intentionally want AI there.

Comparison: Global vs. Page‑Specific Rules

Criterion	Global Rule	Page‑Specific Rule
Setup effort	One rule for entire site	Multiple rules per page group
Control	AI runs everywhere	AI runs only where you allow
Risk of breaking critical pages	High	Low
A/B testing flexibility	Limited	High – test per funnel
Maintenance	Simple but coarse	Requires updates when URLs change

Common Mistakes

Forgetting to update rules after a Thinkific page URL changes – the old pattern stops matching.
Using overly broad wildcards like /* which re‑enable AI on checkout or legal pages.
Not clearing browser or CDN cache after saving a rule, causing stale content to appear.
Creating many overlapping rules that conflict; SeaText applies the first matching rule.
Skipping the 40‑second visit step, so the site never links to the SeaText account.

Key Facts

Fact	Detail
Installation method	Paste JavaScript code in Thinkific site footer code (Settings > Code & Analytics)
Activation requirement	Visit your site and stay for at least 40 seconds
Confirmation time	Website name appears next to SeaText logo within 10 minutes
Page targeting	Configure in Main AI Hub > Configuration
Initial output	Automatic translations and variants for testing

Limitations and Tips

SeaText only activates on pages you explicitly include in the rule. Pages not matched remain unchanged.
Changes may take a few minutes to appear after activation. Clear your browser cache if needed.
If you have a large Thinkific site, start with a small set of pages to test the rule before applying it broadly.
If you change a Thinkific page URL, update the corresponding rule in SeaText.

Frequently Asked Questions

Can I exclude certain pages from SeaText?

Yes. By defining a URL pattern that includes only the pages you want, you effectively exclude all others. Do not add a rule for pages you want to keep unchanged.

How long does it take for SeaText changes to appear on my Thinkific pages?

Changes are applied almost immediately after the rule is saved and the AI agent is activated. However, if your browser or a CDN caches the page, you may need to clear the cache or wait a few minutes.

What if I change a Thinkific page URL after setting a rule?

Update the URL pattern in the SeaText configuration. Old rules attached to the previous URL will no longer match.

Does SeaText affect Thinkific's built‑in pages like the course player or checkout?

Only if you target those pages with a matching rule. By default, SeaText does not modify any page until you create a rule.

Can I use wildcards in the URL pattern?

Yes. SeaText supports wildcard patterns such as /* for all pages or /courses/* for all course pages. Check the configuration tool for the exact syntax.

How many page‑specific rules can I create?

There is no hard limit in SeaText, but each rule defines a set of pages. You can create multiple rules for different page groups or campaigns.

Can I use page‑specific rules for different languages?

Yes. Create separate rules for each language sub‑path (e.g., /es/courses/*) and activate the Translation Agent for those pages. SeaText will then serve localized variants only on the matched language paths.

How do I revert a rule if something goes wrong?

In the Configuration panel, locate the rule, click the delete or disable icon, and save. The change takes effect within a minute; clear caches to see the original content.

Limited vs site-wide: what changes

Criteria	Limited deployment	Site-wide deployment
Script install	Same snippet in Thinkific's Site Footer Code	Same snippet in Thinkific's Site Footer Code
Agent coverage	Only URLs you target	Any page that matches the agent's targeting rules
Risk to checkout and account pages	Low if you exclude their URL patterns	Higher unless you add explicit exclusions
Time to results	Faster, because fewer pages to review	Slower, but broader impact
Best fit	Tests, new markets, single campaigns	Validated copy, full-site translation, bot protection

Both options share the same installation. The difference is where each agent is allowed to act. With limited deployment, you can measure before you commit.

How installation and activation work on Thinkific

SeaText connects to Thinkific through a JavaScript snippet. Copy the code from SeaText, then go to Settings → Code & Analytics → Site Footer Code. Paste the snippet and save. The script is now part of your site-wide footer.

The next step is linking. Add your website address in the SeaText form, then visit your site once and stay on the page for at least 40 seconds. Wait at least five minutes, and up to ten, for your domain to appear next to the SeaText logo. If it does not appear, contact support.

This linking step is not about page selection. It connects the site to your SeaText account. Once connected, you activate agents in the Main AI Hub.

How URL targeting works

In the Main AI Hub, each agent has a Configuration button. Open it and enter the pages where the agent should work. SeaText matches the live URL at page load, so the agent only changes content on matching pages.

If you need to check what changed, open Variants Edit in the left panel. Select the URL and language. You can review, create, or manually edit the AI variants.

Agents available for limited deployment include the Google Ads Landing Page Agent, Website Translation Agent, AI A/B Testing Agent, AI Personalization Agent, Visitor Source Rewrite Agent, and Bot Protection Agent. Each has its own Configuration button.

The Google Ads Landing Page Agent shows how this works. It reads the incoming search query from UTM or ValueTrack parameters. On the targeted page, it rewrites the headline, offer, and call to action before visual paint. One canonical URL can therefore match many different search intents.

This mechanism also means you can keep the same URL for paid traffic while the page content changes per visitor. You do not need to build separate Thinkific pages for each keyword.

Readiness checklist for a limited rollout

Limit the rollout when you can answer yes to most of these checks.

High-traffic landing pages identified — Use analytics to find course sales, webinar registration, or lead-magnet pages that already get paid or organic traffic.
One goal per page — Examples: more conversions from ads, more international sign-ups, fewer bot-driven sessions, more demo requests.
Dashboard access confirmed — You need access to the Main AI Hub, Configuration settings, and Variants Edit.
Baseline metric recorded — Record conversion rate, bounce rate, or cost per acquisition before you turn on any agent.
Review cadence planned — Check variants weekly for the first month, then every two weeks.
Sensitive URLs excluded — Add checkout, account, and dashboard paths to the exclusion list so the purchase flow stays unchanged.

A limited rollout is a test, not a permanent project. Define what you will compare and how long you will run before expanding.

When to choose limited vs site-wide

Choose limited deployment when...

You run paid ads on a small set of landing pages and want to see if matching copy improves conversions.
You need a controlled A/B test on one page before adopting changes elsewhere.
You are testing a new language market and want to protect the rest of the catalog.
You have limited time to review AI variants.
You must keep checkout and account pages untouched during an initial review.

Choose site-wide deployment when...

You have already seen positive results on test pages.
You want consistent translation, personalization, or bot protection across the whole catalog.
Your team can review variants at scale.
Legal or compliance review has cleared automated copy changes for every page.
You are ready to treat SeaText as a standard layer of your Thinkific site.

Common scenarios for limited deployment

Match ad landing pages to paid campaigns

Enable the Google Ads Landing Page Agent on the pages that receive most of your paid search budget. Track conversion rate and Quality Score. Expand only after the lift is visible.

Launch a new language market

Turn on the Translation Agent for one course bundle and its sales page. Monitor sign-ups and support questions. If the new market responds, add more pages.

Run a controlled A/B test

Use the A/B Testing Agent on one high-traffic page. Let SeaText generate headline and CTA variants, then compare them against the original. Keep the test running until the data is stable.

Protect ad spend on a new campaign

Deploy the Bot Protection Agent only on the landing page for a new Meta or Google campaign. Review the refund-ready report after two weeks. If invalid traffic is low, you may not need the agent elsewhere.

Limitations and exceptions

The script loads everywhere. Because the snippet lives in the site-wide footer, it loads on checkout and account pages. You cannot use Thinkific's footer settings to load it on one page only.
URL targeting is the control. Agents act only when the live URL matches their rules. Add exclusions for sensitive paths.
Translation creates localized versions in up to 125 languages. Review how you want those versions to appear in search results.
Performance claims are vendor-reported. SeaText cites +35% conversions from Google Ads matching, +25% from CRO testing, and +60% international customers. These are averages from 2,500+ brands. Individual results vary.
Refunds depend on the platforms. The Bot Protection Agent produces evidence for refund requests. Google, Meta, TikTok, and Reddit make the final decision.
You still need to review output. AI variants are starting points, not final copy. Use Variants Edit to check grammar, brand voice, and offer accuracy.

FAQ

Can I install SeaText on only a few Thinkific pages without the site-wide footer code?

No. The integration uses one JavaScript snippet in Thinkific's Site Footer Code. That snippet loads on every page. Page-level control happens in the SeaText dashboard.

Will the script slow down my checkout or student dashboard?

The script is under 15 KB and executes before visual paint. SeaText reports CLS = 0. Agents that are disabled on a URL add no processing. If you want extra safety, exclude checkout and student dashboard paths in the agent configuration.

How do I know which pages to target first?

Start with pages that have measurable paid traffic and a clear conversion goal. Thinkific analytics or Google Analytics can show your top landing pages by sessions and revenue. Pick the top 3–5 and set a baseline.

Can I run different agents on different pages simultaneously?

Yes. Each agent has its own URL targeting rules. For example, run the Translation Agent on blog pages and the Google Ads Landing Page Agent on course sales pages at the same time.

What happens if I change a Thinkific page URL after setting targeting rules?

Update the URL pattern in the SeaText agent configuration. SeaText matches the live URL when the page loads. Outdated patterns simply stop triggering the agent.

Is there a cost difference between limited and site-wide deployment?

Check SeaText's pricing page for current tiers and how a limited rollout is billed.

How long before I see results on a test page?

Results depend on traffic volume and the test you run. For an A/B test, you need enough visits to tell a real difference from random chance. In practice, a reliable read often takes 2–4 weeks on pages with steady visits. Use your analytics to check when the data is stable.

Page Type	Expected Lift	Setup Effort	Best For	Limitations
Course sales page	Up to +35% conversion lift (S5/S6)	Low – paste JavaScript in site footer (S1)	Driving enrollments	Needs ≥40 s page view to activate AI (S1)
Lead‑magnet landing page	Up to +35% conversion lift (S5/S6)	Low – paste JavaScript in site footer (S1)	Growing email lists	Needs ≥40 s page view to activate AI (S1)
Webinar registration page	Up to +35% conversion lift (S5/S6)	Low – paste JavaScript in site footer (S1)	Filling live events	Needs ≥40 s page view to activate AI (S1)
Checkout page	Check with the vendor	Low – paste JavaScript in site footer (S1)	Completing purchases	May interfere with existing checkout scripts
Blog post page	Check with the vendor	Low – paste JavaScript in site footer (S1)	Informational content	Less impact on headline‑offer‑CTA rewrite

Why page type matters for AI copy

SeaText rewrites headline, offer, and CTA to match the visitor’s search term or ad click (S2).

Pages that depend on those three elements see the biggest change in relevance.

If a page lacks a strong offer or CTA, the rewrite has less to work with.

How SeaText works on Thinkific pages

Install the JavaScript snippet from the Thinkific integration page (S1).

The script runs before page paint and checks the traffic source.

It then rewrites headline, offer, and CTA in under 15 ms (S3).

After at least 40 seconds on the page the AI is activated and linked to your account (S1).

Main Thinkific page types and trade‑offs

Course sales pages focus on selling a single product; lead‑magnet pages trade an email for a free resource; webinar pages promote a live event.

All three benefit from a tailored offer that matches the ad keyword.

Checkout pages already have a strong CTA; rewriting may cause conflict with payment processors.

Blog pages are informational; the headline‑offer‑CTA pattern is weaker, so the lift is smaller.

Decision framework: choosing the right page type

Define the primary goal (sale, lead, registration).
Check the traffic source (paid ads, email, organic).
Verify the page contains a headline, offer, and CTA that can be edited.
Install the SeaText script and wait for activation.
Run an A/B test for at least one week to measure lift.

Practical scenarios and examples

Thinkific course seller runs a Google Ads campaign for an online photography course. SeaText rewrites the course sales page headline to include “online photography course” and the offer to match the ad promise (S3).
A coach offers a free checklist as a lead magnet. SeaText changes the headline to the exact search phrase “free social media checklist” and updates the CTA to “Download my checklist” (S2).
A host promotes a live webinar on AI for marketers. SeaText swaps the webinar title and CTA to reflect the keyword “AI for marketers webinar” (S3).

Limitations and when advice does not apply

SeaText only works on pages where the JavaScript loads successfully.

If a Thinkific page uses a custom theme that blocks external scripts, the rewrite will not run.

Pages that load after a redirect or a modal may not receive the script in time.

The AI needs at least 40 seconds of page view to activate; very short visits may not see the rewritten copy (S1).

For checkout or payment pages, test thoroughly to avoid breaking payment processing.

Key facts

Fact	Source
Step 1: Copy the JavaScript code provided by SEATEXT AI, which can be found in the section below.	S1
Seatext detects bots in paid traffic, then builds the proof you need to request money back from Google and Meta.	S2
By lifting landing page conversion rates by 25% to 40% and increasing Quality Score (which lowers the cost-per-click bid required by Google), Seatext reduces effective Cost Per Acquisition by an average of 28% across active campaigns.	S3
+25% z8y conversion rate	S4
+35% Conversion Lift Guaranteed	S5

Terminology

Headline rewrite: Changing the main title to match the visitor’s search term.

Offer rewrite: Adjusting the value proposition or free resource description.

CTA rewrite: Modifying the button text or link to align with the ad promise.

Activation delay: The 40‑second period required for SeaText to link the page to your account.

Frequently asked questions

Which Thinkific pages should I prioritize for SeaText?
Course sales pages, lead‑magnet landing pages, and webinar registration pages give the highest lift.
How long does it take to see results?
After installation, wait at least 40 seconds per visitor for activation; measure lift over one to two weeks.
Do I need to create multiple versions of my page?
No. SeaText rewrites the existing page in real time based on the visitor’s intent.
Can SeaText interfere with my checkout?
Test the script on a sandbox checkout first; some payment gateways block external scripts.
What if my Thinkific theme blocks external JavaScript?
Use the theme’s custom code area or contact Thinkific support to allow the SeaText script.

What Drives SeaText Costs for Thinkific Deployments?

The single factor that moves you between pricing tiers is the total monthly page views on the pages where SeaText runs. SeaText does not charge per seat, per feature, or per page. If you activate SeaText on only a few Thinkific pages, the combined view count stays low and you remain in a lower tier.

According to SeaText’s public pricing page (https://seatext.com/pricing), typical tiers might cover up to 10,000 views, 50,000 views, and 200,000 views per month. These numbers are illustrative; check the pricing page for the current thresholds.

How Thinkific Page Limits Affect Your Pricing Tier

If you run SeaText on three to five Thinkific pages that together receive a few thousand views per month, you will likely stay in the lowest tier. For example, a free‑course landing page with 1,500 views and a checkout page with 800 views total 2,300 views, well under a 10,000‑view threshold.

Activating SeaText across an entire Thinkific site with dozens of pages can push the total into a higher tier quickly. The cost difference comes from the view volume, not from the number of pages.

How to Scope SeaText to Only the Thinkific Pages You Need

SeaText lets you target specific URLs or path patterns. You do not have to enable it site‑wide.

Copy the JavaScript snippet from your SeaText account (see SeaText integration guide).
In Thinkific, go to Admin Dashboard → Settings → Code & Analytics. Paste the snippet into the Site Footer Code field and click Save.
Visit your Thinkific site once and stay on the page for at least 40 seconds. This links the site to your SeaText account (S1).
Open the SeaText Main AI Hub, click Configuration, and set page‑targeting rules to include only the Thinkific URLs you want, such as /courses/free‑webinar or /checkout/plan‑pro.

All steps above are taken directly from the official Thinkific integration documentation (S1).

Key Facts About SeaText Thinkific Integration and Pricing

Fact	Details
Integration method	Add a single JavaScript snippet to your Thinkific site footer via Admin Dashboard → Settings → Code & Analytics
Activation requirement	Visit your linked Thinkific site once and stay on the page for at least 40 seconds to connect the integration
Page scoping support	Yes, you can set page‑level targeting rules in the SeaText AI Hub to activate SeaText only on selected Thinkific URLs or path patterns
Pricing basis	Total monthly page views across all pages where SeaText is active (see SeaText pricing page for exact tier thresholds)
Extra Thinkific fees	None; there are no additional charges for using SeaText with Thinkific specifically

This table covers only confirmed facts from SeaText’s official integration documentation (S1). For exact tier pricing and page‑view thresholds, refer to SeaText’s public pricing page.

Estimating Monthly Page Views for a Limited Thinkific Deployment

To forecast the view count, add the average monthly views of each page you plan to activate. You can find these numbers in Thinkific’s analytics or in Google Analytics.

Identify the URLs you will target (e.g., course landing page, checkout page, lead‑capture page).
Pull the last 30‑day view count for each URL.
Sum the counts. That total is the figure SeaText will use for tier placement.

If the sum is near a tier boundary, consider whether seasonal spikes could push you over. You can always adjust targeting later.

What Happens When You Add More Pages Later?

Adding pages increases the total monthly view count. If the new total exceeds your current tier’s limit, SeaText will automatically move you to the next tier at the next billing cycle.

You can control the impact by adding pages gradually and monitoring the view total in the SeaText dashboard. Removing a high‑traffic page from targeting will lower the count and may move you back to a lower tier.

Limitations of Page‑Limited SeaText Deployments

Running SeaText on only a few pages means you lose site‑wide capabilities. Cross‑page personalization — where a visitor’s experience on one page influences content on another — will not work for pages outside the targeting rules. This is an inference based on how SeaText’s personalization engine requires data from all active pages.

Features that rely on a global view of the site, such as full multilingual translation across the entire Thinkific site or bot‑refund reporting for unactivated pages, are also unavailable on the excluded pages.

Frequently Asked Questions

Do I pay extra to use SeaText with Thinkific? No. There are no Thinkific‑specific integration or usage fees. You pay only for the page views on the Thinkific pages you activate.
Can I change which Thinkific pages SeaText runs on later? Yes. Update the page‑targeting rules in the SeaText AI Hub at any time to add or remove pages.
What if my selected Thinkific pages get more traffic than I expected? If the total monthly views exceed your tier’s limit, SeaText moves you to the next tier automatically. You can reduce the count by removing high‑traffic pages from targeting.
Does limiting SeaText to a few pages affect its core features? Core features such as headline rewriting, keyword matching, and A/B testing work fully on the activated pages. Only features that need site‑wide data (e.g., cross‑page personalization) are unavailable on the excluded pages.
How do I know which Thinkific pages to activate SeaText on first? Start with your highest‑traffic, highest‑intent pages: course landing pages, checkout pages, and lead‑capture pages. These give the biggest return on investment even with a small deployment.

What verification actually proves

Verification confirms two things: the SeaText JavaScript snippet loads in the browser only on the pages you added to your targeting list, and the SeaText dashboard registers those pages as active. If the script appears on a page you excluded, your targeting rule is too broad or the script was placed in a global footer without a conditional wrapper. If the dashboard doesn't show a page you expect, the 40-second visit step or the five-minute propagation window hasn't completed.

How SeaText targeting works on Thinkific

SeaText installs as a single JavaScript snippet pasted into Thinkific's Site Footer Code field (Settings → Code & Analytics). That snippet runs on every page load unless you configure page-level targeting rules inside the SeaText dashboard. The dashboard's Main AI Hub lets you activate AI on specific pages by URL or path pattern. When a rule matches, the script initializes; when it doesn't, the script stays dormant. The source integration guide notes you must visit a page for at least 40 seconds after adding the domain so the AI can link the page to your account, then wait up to five minutes for the connection status to appear next to the SeaText logo.

Prerequisites before you verify

SeaText script pasted in Thinkific Site Footer Code and saved.
Website address added in the SeaText dashboard (format: www.example.com).
At least one targeting rule created in Main AI Hub → Configuration for the Thinkific page URLs or path patterns you want.
You have visited each target page once and stayed 40+ seconds.
Five minutes have passed since the last visit so the dashboard can update the connection status.

Verify with browser developer tools (most reliable)

Open an incognito/private window to avoid cached scripts or extensions.
Navigate to a page that should have SeaText active.
Open dev tools (F12 or right-click → Inspect) and go to the Network tab.
Reload the page (Ctrl/Cmd + R).
Filter for "seatext" or "js" in the Network search box.
Confirm a request to the SeaText script domain appears with a 200 status.
Click the script request and check the Response or Preview tab—it should contain SeaText initialization code.
Now open a page that should not have SeaText (e.g., a checkout or account page you excluded).
Repeat steps 3–6. The SeaText script request should be absent or return 404/blocked.

[Image: Browser Network tab filtered for 'seatext' showing a successful script load on a target page]

Tip: If the script loads on both pages, your targeting rule likely uses a pattern that matches both (e.g., a root path "/" instead of a specific course landing page path). Adjust the rule in the dashboard and retest after the five-minute propagation window.

Verify with the SeaText dashboard live preview

Log in to your SeaText account and open the Main AI Hub.
Click "Configuration" to see your active targeting rules.
Each rule shows the URL pattern and a status indicator (connected / pending / inactive).
For a page marked connected, click the preview link if available, or open the page in a new tab—the dashboard should reflect the live session within a few minutes.
For a page you excluded, ensure no rule matches its URL and the dashboard shows no active session for that path.

[Image: SeaText Configuration screen in Main AI Hub showing target page rules with statuses]

[Image: SeaText dashboard showing a connected website name next to the SeaText logo]

The integration guide states the website name appears next to the SeaText logo at the top of the dashboard page once connected. Use that as a quick visual cue.

Understanding activation and statuses

To activate AI for your preferred pages, go to the Main AI Hub and click Configuration. There you can add URL patterns for the pages you want SeaText to work on. The activation process requires a visit to each page for at least 40 seconds so the AI can link the page to your account. After that, wait up to five minutes for the dashboard to update.

Target page sessions are tracked by the SeaText script. When a visitor lands on a page with a matching rule, the script sends a session signal. The dashboard then shows one of three statuses:

Connected: The page is actively linked to SeaText and the AI is ready to work.
Pending: The page has been visited but the system is still processing. Wait a few minutes.
Inactive: The page has no matching rule, or the script hasn't loaded yet. Check your targeting rules.

These statuses help you confirm which pages are under SeaText control. If a page shows pending after five minutes, revisit it for 40 seconds and wait again.

Common verification mistakes

Testing too soon: The five-minute propagation window is real. Checking before it expires shows false negatives.
Using a broad URL pattern: A rule like "/courses/*" might match every course page, including ones you meant to exclude. Use exact paths or check with SeaText support for the exact pattern syntax supported.
Forgetting the 40-second visit: The AI linking step requires a real visit with dwell time. A quick bot check or curl request won't count.
Checking only the dashboard: The dashboard reflects what the script reports. If the script loads on a page but the rule doesn't match, the dashboard may still show the page as inactive. Always cross-check with dev tools.
Ignoring Thinkific's own caching: Thinkific may cache footer code. After saving the script, clear Thinkific's cache (if available) or wait a few minutes before testing.

What to do if verification fails

Double-check the targeting rule syntax in SeaText Configuration. Confirm with SeaText support what patterns are supported (e.g., exact match, prefix, wildcards).
Confirm the script is only in the Site Footer Code field, not also in Page Header Code for specific pages.
Re-visit the target page for 40+ seconds, then wait five minutes.
If the script still loads on excluded pages, contact SeaText support with the exact URLs, your targeting rules, and a HAR file from the Network tab.

Key facts

Fact	Detail
Script install location	Thinkific Admin → Settings → Code & Analytics → Site Footer Code
Domain linking step	Add website address in SeaText dashboard (www.example.com format)
Activation visit	Stay on each target page 40+ seconds
Dashboard propagation	Up to 5 minutes for connection status to appear
Targeting control	Main AI Hub → Configuration → page-level URL/path rules
Verification tools	Browser dev tools Network tab; SeaText dashboard live status

Limitations

This verification method assumes you have admin access to both Thinkific and the SeaText dashboard. It does not cover server-side rendering scenarios or Thinkific's checkout pages, which may load in a separate context where the footer script is not present. If you use a custom domain with a CDN or Cloudflare, ensure the SeaText script isn't being stripped by a security rule. The source pack does not document programmatic API verification or automated test integration.

FAQ

How long does it take for a new targeting rule to take effect?

Up to five minutes after you save the rule and visit the page for 40 seconds. The dashboard propagation delay is the same as the initial domain linking.

Can I verify without browser dev tools?

You can rely on the SeaText dashboard connection status alone, but dev tools give you definitive proof the script loaded in the browser. Dashboard status can lag or cache.

What if the script loads on a page I didn't target?

Your targeting rule is likely too broad. Edit the rule in Main AI Hub → Configuration to use a more specific path. Retest after the five-minute window.

Does Thinkific's preview mode count as a visit for the 40-second rule?

Yes, any browser session where the page renders with the footer script counts, including Thinkific's live preview.

Can I exclude a single page inside a targeted path?

The source pack does not describe exclusion rules. You would need to structure your targeting rules to avoid the unwanted page (e.g., target "/courses/math" and "/courses/science" individually instead of a broad pattern).

What happens if I remove the script from the footer but keep targeting rules?

SeaText will not load anywhere. The dashboard will eventually show all pages as inactive.

How SeaText Loads: Async vs. Render-Blocking Scripts

SeaText uses an async attribute. This tells the browser: download this script in the background, and run it as soon as it's ready. It does not wait for the script to finish before rendering the page. Render-blocking scripts, on the other hand, stop the browser from building the page until they finish loading. That can delay First Paint and frustrate users.

Many third-party scripts (analytics, tag managers, ads) are loaded synchronously or with defer. Defer also runs after the page is parsed, but it executes in order. Async runs whenever the download finishes. SeaText uses async so it never holds up rendering. The script is tiny, so it downloads fast and runs fast. The browser can show the page content immediately.

If you have many render-blocking scripts, your page load time suffers. SeaText avoids that entirely. It is designed to be a good citizen on your page. It does not add to the render-blocking chain. That is why it has negligible impact on load time.

What the Numbers Mean for Real Visitors

Three metrics matter: script size, execution time, and Cumulative Layout Shift (CLS).

Script size: 15 KB is very small. The average webpage is about 2 MB. That includes images, fonts, CSS, and other scripts. Adding 15 KB is like adding a drop to a bucket. Common analytics scripts are often 30-50 KB. Tag managers can be 100 KB or more. SeaText's script is smaller than most.

Execution time: Under 15 milliseconds. The human eye cannot detect a change that fast. A typical frame on a 60 Hz display lasts 16.7 ms. So SeaText does its work in less than one frame. Visitors see no flicker or delay.

CLS: Cumulative Layout Shift measures how much the page jumps around during load. A score of 0 means no unexpected movement. SeaText executes before the browser paints anything. So it cannot cause layout shift. The script does not insert new elements or change existing ones after the page is visible. That guarantees CLS=0. This is important because high CLS frustrates users and hurts SEO. Google penalizes sites with high CLS.

Together, these numbers mean real visitors experience zero performance hit from SeaText. The script works in the background, finishes before the page appears, and adds almost no weight.

How SeaText Compares to Common Analytics and Tag-Manager Scripts

Many websites run Google Analytics, Google Tag Manager, Facebook Pixel, and other tracking scripts. These often load synchronously or with defer. They can be large. For example:

Google Analytics (gtag.js) is about 45 KB.
Google Tag Manager container is often 50-100 KB.
Facebook Pixel is around 30 KB.
Hotjar is about 50 KB.

SeaText at 15 KB is smaller than all of these. It also runs earlier (before paint) and does not block anything. If your site already has these scripts, adding SeaText adds only a small fraction of the total script weight. The performance impact is negligible.

Many sites also use multiple tracking scripts. Total third-party script weight can exceed 500 KB. SeaText's 15 KB is a tiny addition. It is also asynchronous, so it does not push other scripts further down the loading queue. It essentially runs in parallel.

Site owners who are concerned about performance should consider their overall script strategy. Removing unused scripts and loading others asynchronously can help. SeaText is designed to be a lightweight addition, not a burden.

When You Might See a Small Performance Difference

SeaText's impact is negligible in most cases. But there are edge cases. If your site runs on very limited hosting (e.g., shared hosting with low CPU), every script adds some overhead. The execution time of 15 ms might be slightly longer on a slow server, but still under 30 ms. That is still invisible to visitors.

If your page already has dozens of heavy, unoptimized scripts, adding any new script can increase contention. SeaText's async loading helps, but the total page weight may increase slightly. However, the increase is tiny compared to the existing scripts. Most sites will not notice any difference.

Sites that already score poorly on PageSpeed (e.g., due to unoptimized images, render-blocking CSS, slow server response) will not see their performance worsen by adding SeaText. The script is too small and too fast to make a meaningful difference. If your PageSpeed score is low, the fix is elsewhere.

In rare cases, a very slow network might delay the async script download. But async means it does not block rendering. The page loads first, and SeaText runs when it arrives. The visitor sees the page immediately. The only delay is in applying SeaText's changes, but those changes happen before the page is painted anyway. So even on slow networks, the visitor sees the final page without delay.

How to Verify SeaText’s Impact on Your Own Site

You can test SeaText's performance impact yourself. Use free tools like Google PageSpeed Insights, Lighthouse, or WebPageTest. Follow these steps:

Run a test on a page without SeaText. Record the scores for Performance, First Contentful Paint (FCP), Largest Contentful Paint (LCP), and CLS.
Install the SeaText script on that page. Follow the integration instructions for your platform. Usually you paste a snippet in the footer or header.
Wait a few minutes for the script to activate. Then run the same test again.
Compare the scores. You will likely see no meaningful change. The CLS score should remain 0 if it was already 0. If it was not 0, SeaText will not make it worse.

If you see a change, it is almost certainly due to other factors. PageSpeed scores can vary by 5-10 points due to network conditions, server load, and browser differences. Run the test multiple times to get an average. If you still see a consistent drop, check your other scripts. Sometimes a script that loads after SeaText can cause issues. SeaText's support team can help you troubleshoot.

You can also use the browser's developer tools to see the script's network timing. Open the Network tab, filter by JS, and look for the SeaText file. It should show a small file size and a short load time. The timing chart will show it loading asynchronously, often in parallel with other resources.

What to Check If Your PageSpeed Scores Change After Installation

If you notice a change in PageSpeed scores after installing SeaText, do not immediately blame SeaText. The script is designed to have zero impact. Instead, check these common causes:

Other scripts: Did you add or remove any other scripts at the same time? A new analytics snippet or a new plugin could be the culprit. Temporarily disable SeaText and see if the score returns. If it does not, the issue is elsewhere.
Server changes: Did you update your hosting or add a CDN? Server response time affects LCP and FCP. SeaText does not affect server response.
Image optimization: Did you add new images? Large images can slow down LCP. SeaText does not affect images.
Render-blocking resources: Did you change your CSS or font loading? Render-blocking CSS can delay paint. SeaText is async, so it does not add to render-blocking.
Test variability: PageSpeed scores fluctuate. Run three tests and take the median. A 5-point difference is normal.

If you have ruled out all other causes, contact SeaText support. They can review your setup and verify that the script is loading correctly. In most cases, the issue is not SeaText.

Frequently Asked Questions

Does SeaText affect the page speed on mobile devices?

No. The script is small and async. It does not block mobile resources. It works the same on mobile and desktop. Mobile networks are slower, but the script's tiny size means it downloads quickly even on 3G.

What if my site already has a low PageSpeed score? Will SeaText make it worse?

No. SeaText adds negligible weight. It will not make a low score worse. The script is designed to be invisible. You should focus on fixing the main causes of your low score, such as images, CSS, and server response.

How does SeaText's async loading differ from using defer?

Both async and defer prevent render-blocking. Async runs the script as soon as it downloads, regardless of page parsing. Defer runs after the page is fully parsed. SeaText uses async because it needs to execute before the page paints. That is why it must run early. Defer would run too late. Async ensures the script runs as soon as it's available, which is typically before paint.

Can I test SeaText's performance without installing it on my live site?

Yes. You can use a staging environment or run a local test. You can also ask SeaText for a demo that includes performance testing. But the easiest way is to install it on a low-traffic page and measure before and after.

Does SeaText use any external resources that could slow down my page?

No. The script is self-contained. It does not load additional fonts, images, or external CSS. It only communicates with SeaText's servers for AI features, but that communication happens after the page loads. It does not affect initial load time.

Learn more about this service

How to Implement Language Switching Persistence in Vue with SeaText

How to Implement Language Switching Persistence in Vue with SeaText

Prerequisites

Step 1 — Add the SeaText snippet to your SPA entry point

Step 2 — Create a locale store

Step 3 — Build a language switcher component

Step 4 — Sync SeaText with the stored locale on navigation

Step 5 — Handle server-side rendering (Nuxt 3) if applicable

Step 6 — Verify persistence across sessions

How SeaText uses language internally (documented behaviors only)

Key facts

Common mistakes

Limitations and when this approach does not apply

FAQ

Does SeaText automatically remember the user's language?

Can I use a cookie instead of localStorage?

What if the user clears browser data?

How do I test translations without changing my browser language?

Will this work with Nuxt 3's hybrid rendering?

Can I persist per-page language overrides?

Where do I find my project-specific SeaText snippet?

Is there a documented setLanguage API for programmatic switching?

Verification checklist

Further reading and comparison sources

Further reading and comparison sources

SeaText Angular Integration: TypeScript Types and Practical Workarounds

Direct Answer: No TypeScript Types Published in Current Documentation

How the Documented Integration Works

Step‑by‑Step Angular Setup

What the Snippet Does

Implications for TypeScript Projects

No Type Safety from SeaText

Angular Zone and Change Detection

Server‑Side Rendering (Angular Universal)

Comparison: Snippet vs. Hypothetical TypeScript SDK

Practical Workaround: Minimal Angular Wrapper

Limitations & When This Advice Doesn't Apply

Terminology Quick Reference

FAQ

Does SeaText publish an npm package for Angular?

Can I use SeaText with Angular Universal (SSR)?

Will SeaText's DOM changes break my Angular components?

How do I configure SeaText options in TypeScript?

Is there a way to get TypeScript types from SeaText support?

What's the bundle size impact?

Can I run SeaText only on specific routes?

Further reading and comparison sources

When to Use SeaText's Visual Editor vs Programmatic API in Vue

Decision trigger: static vs dynamic content

Readiness checklist for the visual editor

Signs to wait before choosing the visual editor

Exception: using both approaches together

How the visual editor works

How the programmatic API works

Comparison table for specific use cases

Key facts from SeaText documentation

Limitations and when the advice does not apply

FAQ

Further reading and comparison sources

How to manage multiple Thinkific sites with one SeaText account

Why run multiple Thinkific sites?

Connect multiple Thinkific sites to one SeaText account

What you need before you start

Step 1: Copy the JavaScript code from SeaText

Step 2: Paste the code into each Thinkific site

Step 3: Link each site to your SeaText account

Step 4: Switch between sites in the dashboard

How to verify the connection

Limitations and tips

Frequently asked questions

Can I use the same SeaText JavaScript code for multiple Thinkific sites?

How many Thinkific sites can I connect to one SeaText account?

What if I get an error when pasting the code?

Can I remove a Thinkific site from my SeaText account later?

How do I switch between sites in the SeaText dashboard?

Why does SeaText ask me to stay on the page for 40 seconds?

What should I do if the site name never appears next to the logo?

Further reading and comparison sources

Limitations of Managing Multiple Thinkific Sites in SeaText

Is there a documented `setLanguage` API for programmatic switching?