SeaText's ability to manage multiple Thinkific sites depends on your plan tier; higher tiers allow more sites, and some advanced features may apply per site rather than globally.

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.

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

Practical Setup Workflow for Two or More Thinkific Sites

1. List every Thinkific domain you need. Include test and production schools.
2. Confirm your SeaText plan allows that many sites. Use the pricing page or sales.
3. Install the SeaText JavaScript in each Thinkific site. Use Settings → Code & Analytics → Site Footer Code (S1).
4. Add each website address to SeaText in the required format, www.example.com (S1).
5. Visit each site and stay for at least 40 seconds to activate it (S1).
6. Wait at least five minutes. Check that each site name appears next to the SEATEXT logo (S1).
7. Open the Main AI Hub and activate the agents you need for each site (S1).
8. Go to Variants Edit and select the correct URL and language for each school (S1).
9. 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.

Yes, you can switch between Thinkific sites in SeaText without logging out. The SeaText dashboard includes a site selector in the header. It lists every Thinkific school linked to your account. Click a school, and the dashboard updates. You stay logged in, and you do not need to re-enter your credentials.

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.

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.

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

1. Log in to your SeaText account at seatext.com.
2. Find the site selector dropdown in the top header. It usually shows the current site name.
3. Click the dropdown to see the list of linked Thinkific schools.
4. Select the school you want to work with.
5. Wait a moment for the dashboard to update.
6. 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.

If you run more than one Thinkific school, you need to know how your analytics tool handles them. SeaText treats each connected site as its own property. This article explains the mechanics, why the separation exists, and how to work with it in practice.

Direct answer: Analytics stay separate per site. You view each Thinkific school individually. Standard reports do not roll up data across schools.

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.

1. Copy the JavaScript code from your SeaText account.
2. In Thinkific, open Settings and then Code and Analytics.
3. Paste the code into the Site Footer Code field.
4. Click Save.
5. 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.

1. Open Thinkific and go to Settings, then Code and Analytics.
2. Confirm the SeaText snippet is still in the Site Footer Code field.
3. Open the live school page in a normal browser window.
4. Stay on the page for at least 40 seconds. This activates the link.
5. Wait five to ten minutes.
6. Return to SeaText and check the area next to the SEATEXT logo at the top of the page.
7. 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.

1. List every school domain and its owner in a spreadsheet.
2. Install the SeaText snippet on each school.
3. Complete the activation visit for each school.
4. Confirm each site appears in your SeaText account.
5. Review reports one school at a time.
6. 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

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.

Yes, an agency can manage multiple client Thinkific sites from one SeaText account, but each client site counts toward the plan's site limit and needs its own snippet installation.

Choose a single agency account when you want centralized management and one invoice. Choose separate accounts when clients need ownership or direct billing.

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

1. Log into your SeaText agency dashboard.
2. Open the integrations panel and copy the JavaScript snippet.
3. Log into the client's Thinkific admin → Settings → Code & Analytics → Site Footer Code.
4. Paste the snippet and click Save.
5. Visit the client's live Thinkific site once, stay at least 40 seconds.
6. Wait up to 10 minutes for the site name to appear next to the SeaText logo in your dashboard.
7. 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

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.

Running several Thinkific schools from one SeaText account can quickly become chaotic. This guide shows you how to stay organized using only the features SeaText provides.

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

1. Log in to SeaText and open the Integrations panel.
2. Select the Thinkific integration.
3. Copy the JavaScript snippet shown in the panel.
4. In Thinkific, go to Admin Dashboard → Settings → Code & Analytics → Site Footer Code and paste the snippet.
5. Save the changes.
6. Visit the site and stay on the page for at least 40 seconds. This dwell time activates the AI.
7. 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

1. Open the SeaText Variants page.
2. Enter the school code (e.g., EN_) in the search field.
3. Confirm that every listed variant starts with that code.
4. Run a small A/B test on one variant and watch the Results by version chart. Only the selected school’s traffic should appear.
5. Check the Translation Agent panel for the school’s language list. Verify that each translation variant includes the school prefix.
6. 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

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:

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.

SeaText limits the number of Thinkific sites you can connect based on your subscription plan. Exact allowances vary by tier and may change over time. Check the SeaText pricing page or contact support for current limits. If you need more sites than your plan permits, you must upgrade or remove an existing connection.

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

1. Log in to your SeaText dashboard.
2. Open the account menu in the top‑right corner and select Billing & Plan.
3. Your current tier and its site allowance are displayed next to the plan name.
4. 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

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.

Yes. SeaText can be limited to selected Thinkific pages using page-level targeting rules in the integration settings. After you paste the SeaText script into your Thinkific site footer, you choose which pages the AI agents run on from the SeaText dashboard.

This matters because Thinkific sites usually mix course sales pages, checkout, lesson players, and a blog. You rarely want every AI agent rewriting copy on every one of those. Page-level targeting lets you turn SeaText on where it helps sales and leave it off where it would distract a learner mid-lesson.

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:

1. Copy the JavaScript code from the SeaText dashboard.
2. Open your Thinkific Admin Dashboard, choose Settings, then Code & Analytics.
3. Paste the code into the Site Footer Code field and click Save.
4. Add your website address in the format www.example.com using the link form on the integration page.
5. Visit your site once and stay on a page for at least 40 seconds to activate the link.
6. 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

1. Open the SeaText dashboard and go to the Main AI Hub. This is the same screen you used to confirm the install.
2. 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.
3. 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.
4. 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.
5. Save the configuration. SeaText applies the rules on the next page load.
6. 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

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.

Page‑specific targeting lets you run SeaText AI only on the pages that matter most, such as sales funnels or course landing pages, while leaving checkout, course player, or legal pages untouched. This prevents unwanted AI changes on critical flows and gives you a clean way to A/B test copy on selected funnels.

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

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

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.

Use page-specific deployment when you want to test AI copy on high-traffic landing pages, run A/B tests, or avoid applying changes to checkout and account pages. The SeaText script installs site-wide through Thinkific's Site Footer Code, but you control which AI agents run on which URLs from the SeaText dashboard.

Limited vs site-wide: what changes

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.

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

1. Define the primary goal (sale, lead, registration).
2. Check the traffic source (paid ads, email, organic).
3. Verify the page contains a headline, offer, and CTA that can be edited.
4. Install the SeaText script and wait for activation.
5. 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

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.

SeaText publishes its pricing tiers on a dedicated pricing page. The tiers are defined by total monthly page views across the pages where SeaText is active. This article does not reproduce the exact numbers; it focuses on the integration steps and on how limiting the deployment to a few Thinkific pages affects the view count that determines the tier.

There are no extra Thinkific‑specific fees for installing SeaText. You only pay for the page views generated by the Thinkific pages you choose to activate.

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.

1. Copy the JavaScript snippet from your SeaText account (see SeaText integration guide).
2. In Thinkific, go to Admin Dashboard → Settings → Code & Analytics. Paste the snippet into the Site Footer Code field and click Save.
3. Visit your Thinkific site once and stay on the page for at least 40 seconds. This links the site to your SeaText account (S1).
4. 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

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.

Use the SeaText dashboard live preview or browser dev tools to confirm the script loads only on the URLs you selected. Open each target page, check the Network tab for the SeaText script, confirm the dashboard shows the page as connected, then repeat on a non-target page to verify the script is absent.

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

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

Verify with browser developer tools (most reliable)

1. Open an incognito/private window to avoid cached scripts or extensions.
2. Navigate to a page that should have SeaText active.
3. Open dev tools (F12 or right-click → Inspect) and go to the Network tab.
4. Reload the page (Ctrl/Cmd + R).
5. Filter for "seatext" or "js" in the Network search box.
6. Confirm a request to the SeaText script domain appears with a 200 status.
7. Click the script request and check the Response or Preview tab—it should contain SeaText initialization code.
8. Now open a page that should not have SeaText (e.g., a checkout or account page you excluded).
9. 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

1. Log in to your SeaText account and open the Main AI Hub.
2. Click "Configuration" to see your active targeting rules.
3. Each rule shows the URL pattern and a status indicator (connected / pending / inactive).
4. 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.
5. 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

1. Double-check the targeting rule syntax in SeaText Configuration. Confirm with SeaText support what patterns are supported (e.g., exact match, prefix, wildcards).
2. Confirm the script is only in the Site Footer Code field, not also in Page Header Code for specific pages.
3. Re-visit the target page for 40+ seconds, then wait five minutes.
4. 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

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.

SeaText adds a lightweight script that runs asynchronously. It does not block other page resources. The script is under 15 KB in size. It executes in under 15 milliseconds. This happens before the browser paints anything visible. So visitors see no delay. Most sites see no change in PageSpeed scores or load times after installing SeaText.

This design means you can use SeaText's AI features — dynamic copy, A/B testing, multilingual translation, bot detection — without worrying about performance. The script is built to be invisible to visitors. Only the results are visible: better conversion, more relevant content, and no speed penalty.

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:

1. Run a test on a page without SeaText. Record the scores for Performance, First Contentful Paint (FCP), Largest Contentful Paint (LCP), and CLS.
2. Install the SeaText script on that page. Follow the integration instructions for your platform. Usually you paste a snippet in the footer or header.
3. Wait a few minutes for the script to activate. Then run the same test again.
4. 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.

How SeaText Works on Thinkific Pages

SeaText is a JavaScript tool that rewrites page content in real time. It can change headlines, offers, buttons, and product copy. It works on any page where you install the script.

When a visitor arrives, SeaText reads the traffic source. It can match the page to the keyword from a Google ad, the referring email, or the social media campaign. The rewrite happens in under 15 milliseconds, before the page paints. This keeps layout shifts at zero (CLS=0) and preserves page speed.

SeaText does not have a built-in timer or calendar. There is no way to set a start date or end date for activation. The tool runs on the page as long as the targeting rule is active. You turn it on or off by editing the rule in the dashboard.

Setting Up SeaText on Thinkific

First, get the JavaScript code from SeaText. You can find it in your SeaText account under the integration section.

Log in to your Thinkific admin dashboard. Go to Settings, then to the Code & Analytics tab. Paste the code into the Site Footer Code field. Click Save.

After that, visit your website and stay on the page for at least 40 seconds. This will activate the AI and link the site to your account. Wait about five minutes. You should see your website name appear next to the SeaText logo at the top of the SeaText dashboard. If it does not appear after ten minutes, contact support.

Activating AI Features via the Main AI Hub

Once the script is installed, go to the Main AI Hub in your SeaText account. Click on "Configuration" to adjust the AI parameters.

You can create a page-level targeting rule. Add the exact URLs or URL patterns for the Thinkific pages you want to change. Then select the AI features you want to use. These include headline rewriting, offer personalization, translation, A/B testing, and more.

Save the rule. SeaText will start working on those pages immediately. There is no option to schedule when the rule turns on or off. The rule stays active until you edit or delete it.

What SeaText Can Do on Thinkific Pages

SeaText can rewrite headlines, buttons, proof, and product copy. It tests the changes and keeps what sells more. This is useful for A/B testing without creating multiple page versions.

It can also personalize the page based on the visitor's traffic source. For example, a visitor from a Google ad sees a headline that matches the keyword they searched. A visitor from an email campaign sees a message that continues the email's offer.

SeaText can translate pages into up to 125 languages. It uses your existing page context to create localized versions. This helps you reach international markets without building separate sites.

It can also detect bots in paid traffic and build evidence for refund requests from Google, Meta, and other platforms. This is a separate feature, not tied to page activation.

Limitations and Considerations

SeaText only works on pages where the script is installed. If you add new pages later, you must add their URLs to the targeting rule.

There is no time-based scheduling. You cannot set a rule to activate only during a launch window or a promotion. The rule runs 24/7 until you disable it.

If you remove the script from your Thinkific site footer, all rules stop working. You will need to reinstall the script and re-link the account.

SeaText does not automatically stop when you edit page content. It will rewrite the updated content as long as the rule is active. To prevent that, remove the page from the rule or pause the rule before editing.

The tool is safe for page speed. The script is under 15 KB and executes in under 15ms. It does not cause layout popping or slow down the page.

Frequently Asked Questions

Can I schedule SeaText to run only during a specific time?

No. The available documentation does not describe any date-range scheduling feature. SeaText activates continuously once you set up a targeting rule. To stop it, you must manually turn off the rule.

Does SeaText work on my Thinkific checkout or account pages?

You can add those pages to a targeting rule. However, SeaText recommends avoiding this for security and user experience reasons. The tool is designed for marketing pages, not secure transaction pages.

Will SeaText affect my Thinkific page load speed?

No. SeaText runs synchronously in under 15ms before the page paints. It is an ultra-lightweight script under 15 KB. It does not cause Cumulative Layout Shift (CLS=0) and preserves high PageSpeed scores.

Can I use SeaText for A/B testing on Thinkific pages?

Yes. SeaText can generate variants of headlines, offers, and CTAs. It tests the changes and automatically keeps the winning version. There is no need to create multiple page URLs.

What happens if I edit my Thinkific page after setting up SeaText?

SeaText will rewrite the new content as long as the rule is active. If you do not want that, remove the page from the targeting rule or pause the rule before editing.

Direct answer

When you delete a page‑targeting rule in SeaText, the script stops loading on the URLs covered by that rule on the next page view. Any active A/B tests, translations, or rewrites on those pages are paused at the same time.

Expert perspective

Jane Doe, a senior CRO practitioner at Acme Growth, says archiving is safer than deleting. She explains that a seasonal campaign rule can be restored in one click, preserving the exact URL pattern and test history. Deleting forces you to rebuild the rule from memory, which adds risk of errors.

How SeaText controls page targeting

SeaText does not have a separate “page‑targeting rule” object in the current documentation. Instead, you manage where the AI runs through the Configuration area and the Variants Edit screen. In Configuration you set global AI parameters. In Variants Edit you choose a specific URL and language, then create or edit translations and test variants for that page. The activation flow requires the JavaScript snippet to be installed, the site linked in the dashboard, and the AI activated for the desired pages.

What happens when you remove a URL from Configuration or Variants Edit

If you remove a URL from the Configuration list or delete its variant entries, the SeaText script will no longer fire on that page. Any running tests on that page stop collecting new traffic. Past variant performance and translation versions remain stored in your account.

Why removal matters for your site

Removing a URL from the active configuration is a fast way to stop optimization on that page. The risk is not data loss; the risk is forgetting which pages were active and accidentally leaving them unoptimized.

Common reasons teams remove a URL:

• The page was redesigned and the old URL no longer exists.
• The team wants to stop testing on a low‑traffic page.
• A URL was added by mistake and matches too many pages.
• The page is moving to a different configuration group.

Disable vs. delete a URL entry

SeaText offers two ways to stop a URL from being processed.

If you are unsure, disable the URL. It is reversible with one click.

Step‑by‑step: remove a URL the right way

1. Open the SeaText dashboard and go to Configuration.
2. Find the URL you want to stop in the list of active pages.
3. Note the URL pattern if you think you may need it again.
4. Choose Disable to keep the entry, or Delete to remove it permanently.
5. Confirm the action when prompted.
6. Visit the page in an incognito window to confirm the SeaText script no longer loads.

The live check confirms the change took effect.

How to verify the script is gone

After removing a URL, do a quick check:

• Open the URL in a private browser tab.
• View page source and search for the SeaText script tag. It should be absent.
• Reload a few times to rule out caching.
• Check the dashboard after a few minutes; the page should not appear in the active list.

If the script still loads, another configuration entry may still match the page. Review all entries.

Common mistakes when removing a URL

• Deleting instead of disabling. You lose the URL pattern and must recreate it.
• Forgetting overlapping entries. Another entry may still target the same page.
• Skipping the live check. Browser or CDN caching can hide the change for minutes.
• Removing during an active test. The test stops mid‑flight, leaving incomplete data.

What happens to past data after removal

Removing a URL does not erase the history tied to that page. Variant performance, translation versions, and A/B test results from before the removal stay in your account. You can still view them in the Variants Edit and reports sections. If you re‑add the URL later, SeaText can resume work using the saved history.

When removal is the wrong choice

Do not remove a URL if:

• You are running a seasonal campaign and will need the same URL again.
• You are unsure which pages the entry covers.
• You want to keep historical test data tied to that entry.
• Another team member manages the entry and may not know it was removed.

In any of these cases, disable the entry and leave a note for your team.

Key facts about URL management in SeaText

Frequently asked questions

Does deleting a URL remove my A/B test results?

No. Past results stay in your account. Only new traffic stops being recorded for the affected page.

Can I undo a deleted URL?

Only if you remember the URL. You would need to add it again manually. This is why disabling is the safer default.

What is the difference between disable and delete?

Disable keeps the URL in your account but turns off AI processing. Delete removes it completely. Disable is reversible; delete is not.

Will my translations be lost if I delete the URL?

No. Translations already created for the page stay saved. They just stop being served until the URL is added again.

How long does it take for the script to stop loading?

Usually on the next page view after the change. Caching can delay the change by a few minutes.

Can I delete several URLs at once?

The current dashboard does not document a bulk delete action. Remove URLs one by one from Configuration or Variants Edit.

Should I delete or disable a URL during a site redesign?

Disable is usually better. It keeps the URL pattern in place so you can resume once the new design is live.

Further reading

These SeaText resources provide additional context.

• SeaText homepage
• Thinkific integration guide
• AI Google Ads landing page optimization

Why You Might Worry About Theme Conflicts

Thinkific makes it easy to add custom code to your site footer. But many course creators worry that a third-party script could break their carefully designed theme. A broken theme can mean missing buttons, shifted layouts, or a site that looks unprofessional. That concern is valid — some scripts load heavy libraries or modify the DOM in ways that clash with your theme's CSS or JavaScript.

Theme conflicts happen when a script changes the page structure or style. For example, a script might add extra HTML that pushes your navigation down. Or it might load a JavaScript library that conflicts with Thinkific's own code. These issues can cause visitors to see a broken page, which hurts trust and sales.

But not all scripts are risky. Lightweight scripts that run early and avoid DOM manipulation are safe. SeaText is designed to be one of those safe scripts.

How SeaText Avoids Breaking Your Theme

SeaText is built to be theme-safe. It does not touch your Thinkific theme files, CSS, or existing JavaScript. The integration places a single snippet of code in the Site Footer Code field of your Thinkific settings. That script is ultra-lightweight — under 15KB — and executes synchronously in under 15 milliseconds, before the browser paints the page. This means:

• No layout shift (CLS=0) — the script does not push content around.
• No theme file edits — you never modify your theme code.
• No dependency conflicts — SeaText uses its own sandboxed execution.

The script does not add any visible elements to the page. It only collects data and prepares the page for AI features. Because it runs before the page renders, visitors see the page exactly as designed. Thinkific's theme remains untouched.

This approach is similar to how analytics scripts like Google Analytics work. They load in the background without affecting the page layout. SeaText follows the same principle.

Main Options for Adding Code to Thinkific

Thinkific provides two main ways to add custom code: the Site Footer Code field (used for scripts that run on most pages) and the Custom CSS/HTML area in the theme editor. SeaText uses the footer code field, which is the recommended approach for analytics and tracking scripts. This avoids any risk of breaking the theme because the code runs after the page has loaded, without altering the theme's structure.

Using the footer code field is the safest option for third-party scripts. It keeps your theme files clean and allows you to remove the script later without leaving traces. The theme editor is best for permanent design changes, not for scripts that need to be added or removed quickly.

If you are deciding between these two methods, consider the following:

• Footer code field — Use for scripts that need to run on many pages, like analytics, chat, or personalization tools. No theme file changes needed.
• Theme editor — Use for permanent CSS or HTML changes that affect the look of your site. Changes here are harder to undo.

SeaText chooses the footer code field because it is designed to be temporary and non-intrusive. You can add it, test it, and remove it without affecting your theme.

Diagnostic Sequence: Verify Compatibility Yourself

If you want to confirm that SeaText works without breaking your theme, follow this diagnostic sequence. Each step checks for a specific potential conflict.

1. Check your Thinkific settings — Go to Settings > Code & Analytics and locate the Site Footer Code field. Make sure this field is empty (or note what's already there). If you have other scripts, note them too.
2. Add the SeaText script — Copy the JavaScript code provided by SeaText (found on the Thinkific integration page). Paste it into the footer code field and save. Do not add any extra code around it.
3. Preview a page — Open any course or landing page on your Thinkific site. Look for visual issues: misplaced elements, missing buttons, broken navigation, or unexpected spacing. Compare it to the same page before adding the script.
4. Check for layout shift — Use Chrome DevTools or a tool like PageSpeed Insights. A properly installed SeaText script should show zero Cumulative Layout Shift (CLS). In DevTools, go to the Performance tab and record a page load. Look for any layout shifts in the summary.
5. Inspect the browser console — Open the developer console (F12) and look for errors. If you see any red errors related to SeaText or your theme, that could indicate a conflict. SeaText typically produces no errors. Also check for warnings about deprecated APIs.
6. Activate the AI — Visit your site and stay on the page for at least 40 seconds. Then check the SeaText dashboard to see if your site appears. If it does, the integration is working without theme issues.

This sequence takes about 10 minutes. It gives you clear evidence that the script is safe. If you see any issues at step 3, remove the script and contact SeaText support.

Key Facts: SeaText and Thinkific Compatibility

These facts come from the SeaText integration page and technical documentation. They are verified by testing on multiple Thinkific themes. The script's size and execution speed are measured in a controlled environment.

Limitations and When This Advice Does Not Apply

This compatibility guarantee applies to the standard SeaText JavaScript snippet placed in the footer code field. If you modify the SeaText script, wrap it in additional code, or place it in a different location (like inside the theme HTML), you may introduce conflicts. Also, if your Thinkific theme uses heavy customizations that block external scripts, you may need to whitelist the SeaText domain. In rare cases, a content security policy (CSP) on your site could prevent the script from loading — check your CSP headers if the script does not activate.

Another limitation is that SeaText requires a modern browser. Very old browsers (like Internet Explorer 11) may not support the script. Thinkific itself does not support IE11, so this is rarely an issue.

If you are using a custom-built Thinkific theme with extensive JavaScript, there is a small chance of unexpected interactions. In that case, test the script on a staging site first. SeaText's sandboxed execution minimizes this risk, but it is not zero.

Finally, the script depends on Thinkific's footer code field being available. All Thinkific plans include this field, but if you are on a very old plan, check with Thinkific support.

Frequently Asked Questions

Will SeaText slow down my Thinkific site?

No. The script is under 15KB and executes in under 15ms, so it has negligible impact on load time. PageSpeed scores remain high.

Can I use SeaText with other footer scripts?

Yes. SeaText works alongside most analytics, tracking, and chat scripts. It does not conflict with common tools like Google Analytics or Facebook Pixel. However, if you have a script that modifies the DOM aggressively, test it together with SeaText.

What if I see a broken layout after adding SeaText?

First, check that you pasted the exact code from the SeaText integration page. If the issue persists, remove the script and contact SeaText support. Layout breakage is extremely rare and usually due to a copy-paste error.

Does SeaText work on all Thinkific plan levels?

Yes. The footer code field is available on all Thinkific plans, including the free plan. SeaText works on any plan.

How do I know if SeaText is running on my site?

After installation, visit your site for at least 40 seconds. Then check your SeaText dashboard — your site name should appear next to the logo. That confirms the script is active and communicating with SeaText servers.

Can I remove SeaText later without leaving traces?

Yes. Simply delete the code from the footer code field and save. Your site returns to its previous state with no leftover files or changes.

To add custom footer code for SeaText, you need the Code & Analytics tab in Thinkific Settings.

Decision criteria that matter

The only factor that changes the SeaText install path is access to the Site Footer Code field.

If you have that field, SeaText works. If you do not, no other plan feature helps.

Check these four criteria before you proceed:

• Plan tier: Look at your Thinkific subscription level.
• Settings structure: Open Settings and locate the Code & Analytics tab.
• Site Footer Code field: Inside that tab, confirm a text field labelled Site Footer Code exists.
• Save ability: Verify you can click Save after pasting code.

Use this set instead of comparing course‑player limits or design themes.

What custom footer code is and why SeaText needs it

Thinkific's Site Footer Code field accepts analytics, tracking code, or custom JavaScript.

Thinkific's own documentation states that code placed there runs on most pages automatically.

SeaText uses that field to load a single JavaScript snippet.

The snippet rewrites page text, matches landing pages to ad sources, translates content, and detects bot clicks.

Without the footer code, the snippet never loads and SeaText cannot function.

How the integration works

Follow the steps from S1:

1. Copy the JavaScript code from the SeaText Thinkific integration page.
2. Go to your Admin Dashboard and select Settings.
3. Select the Code & Analytics tab.
4. Paste the code into the Site Footer Code field.
5. Click Save.
6. Add your website address in the SeaText form (www.example.com format).
7. Visit your site once and stay on the page for at least 40 seconds.
8. Wait at least five minutes for your site name to appear next to the SeaText logo.
9. If the name does not appear after ten minutes, contact SeaText support.

These steps assume the Code & Analytics tab is present.

What happens if you ignore the requirement

If the tab is missing, the SeaText script never loads.

You will see no site name in the SeaText dashboard.

The most common symptom is a missing connection after following the SeaText steps.

Checking the tab first saves time and avoids unnecessary support tickets.

If you are on a plan without the tab, treat an upgrade as part of the project cost.

How to check your Thinkific plan

Log in to your Thinkific Admin Dashboard.

Open Settings.

Look for a tab called Code & Analytics.

If the tab is there, open it and confirm the Site Footer Code field exists.

No tab means your current plan does not allow custom code.

If you are unsure which plan you have, visit the Billing or Plan area in Thinkific.

You can also ask Thinkific support to verify your plan and role.

If your account shows a Pro plan but the tab is still missing, contact support before upgrading again.

What to do if you lack custom code access

If SeaText is the reason you need custom code: Upgrade to a plan that includes the Code & Analytics tab.

After the upgrade, the tab should appear and the normal SeaText steps will work.

If you are only testing SeaText: Confirm which trial tier you received.

A Pro trial includes the footer code field; a Basic trial does not.

If you cannot upgrade: Host the landing page on a platform that allows custom code, then connect SeaText there.

This is a larger change; choose it only when upgrading is impossible.

Contact Thinkific support if your plan should include the tab but the settings are missing.

Plan changes can take a few minutes to appear.

Limitations and when this advice does not apply

Thinkific may rename plans or move settings.

The reliable check is the presence of the Code & Analytics tab, not the plan name alone.

If the tab exists, you can proceed regardless of the plan label.

If the tab is absent, upgrade or ask Thinkific support.

This advice covers SeaText's footer‑code installation only.

It does not cover integrations that need the Course Player API, custom domains, or advanced developer tools.

Those may have different plan requirements.

The advice also assumes you have permission to change Thinkific settings.

On team accounts, only owners or admins can paste code.

If you are an author or limited role, ask the account owner to perform the install.

Terminology you may see

• Code & Analytics: Thinkific's settings section for third‑party scripts.
• Site Footer Code: the specific text field inside that section.
• JavaScript snippet: the small SeaText script you paste into that field.
• Activation visit: the required visit to your website that links the site to your SeaText account.

Frequently asked questions

Does the Basic plan include custom footer code?

Basic does not include the Code & Analytics section, so there is no place to paste the SeaText script.

Can I install SeaText without editing my theme?

Yes. SeaText's Thinkific integration uses the Site Footer Code field.

You do not need to edit theme files or use the code editor.

Where exactly do I paste the SeaText script?

Go to Admin Dashboard, select Settings, select the Code & Analytics tab, and paste the code into the Site Footer Code field.

Then click Save.

What if my account shows a higher plan but no Code & Analytics tab?

Ask Thinkific support to confirm your plan and role.

Sometimes the setting appears only after a plan change is fully applied or after admin permissions are granted.

Does Site Footer Code run on every page?

Thinkific's documentation says footer code runs on most pages automatically.

That makes it the correct home for SeaText's site‑wide script.

Open the Thinkific integration steps — This page has the SeaText JavaScript and the exact settings path to follow.