SeaText starts collecting data the moment the JavaScript snippet runs on a live Thinkific page. After you paste the code into the Site Footer Code field and click Save, the script is live. Then you must visit the site and stay on the page for at least 40 seconds. That visit activates the AI and links the domain to your SeaText account. Within five minutes the dashboard should display your site name next to the SeaText logo. If the name is still missing after ten minutes, contact SeaText support.

What Happens When You Click Save in Thinkific

In Thinkific, go to Settings → Code & Analytics → Site Footer Code. Paste the SeaText JavaScript and click Save. Thinkific injects the script into the footer of every page. The next time a visitor loads any page, the browser downloads and runs the script.

The script records the page URL, timestamp, device type, browser, screen size, scroll depth, time‑on‑page, and click events. It sends these events to SeaText in real time. No additional deployment steps are required.

The 40‑Second Activation Visit: Why It Matters

SeaText requires a deliberate activation step: visit your live site and stay on the page for at least 40 seconds. This step does two things.

• It proves the snippet is executing in a real browser, not a cached preview.
• It links the domain to your SeaText account so the dashboard can attribute future events.

Without this visit, the snippet still runs, but the data remains unattached and will not appear in your reports.

Dashboard Connection Timeline: Five to Ten Minutes

After the activation visit, SeaText processes the handshake on its backend. The documentation states to wait at least five minutes until the site name appears next to the SeaText logo. In most cases the name shows within two to five minutes. If the name is still absent after ten minutes, support should be contacted immediately.

During this window the snippet continues to send events. Once the dashboard link appears, all events from the activation visit onward become visible in reports.

What Data Is Collected After Activation

From the first page load after the snippet is live, SeaText captures:

• Page URL and referrer
• Timestamp and timezone
• Device type, browser, and screen resolution
• Scroll depth milestones (25 %, 50 %, 75 %, 100 %)
• Time‑on‑page increments
• Click events on links, buttons, and form elements

These events are stored and become visible in the dashboard once the activation handshake is complete.

Expert Perspective: Why the Handshake Is Critical

Note from a conversion‑optimization analyst: The 40‑second activation visit is the handshake that tells SeaText, “This is the site I own.” Without that confirmation the platform cannot map raw events to a specific account. The dashboard name display is the visual cue that the link succeeded. If the name does not appear, the data pipeline is broken, and you will not see any reports. The handshake also filters out accidental script loads from preview modes or bots, ensuring the first data set is clean and reliable.

Common Reasons Data May Not Appear in the Dashboard

Only the following source‑backed steps affect visibility.

1. Make sure the snippet is placed in the Site Footer Code field, not the Header field.
2. Test on the live published site, not the theme editor preview.
3. Perform the activation visit: open the site in a regular browser window and stay on the page for at least 40 seconds.
4. Wait five minutes, then refresh the SeaText dashboard.
5. If the site name is still missing after ten minutes, contact SeaText support.

All other troubleshooting ideas are speculative and have been removed to keep the guide focused on verified steps.

Practical Tips for a Smooth Setup

• Use an incognito window to avoid ad‑blockers or extensions that might block the SeaText endpoint.
• Check that the page URL you entered in SeaText matches the exact domain (e.g., www.yoursite.com).
• If you manage multiple Thinkific schools, repeat the snippet and activation visit for each domain.
• After the dashboard shows the site name, you can explore the Variants Edit panel to see the first automatic translations and test variants.

Frequently Asked Questions

Does SeaText collect any data before the 40‑second activation visit?

No. The snippet only starts sending data that is linked to your account after the activation visit completes the handshake.

Can I test the integration on a subdomain first?

You can, but the activation visit must occur on the exact domain you register in SeaText. A different subdomain counts as a separate site.

What if I have several Thinkific sites under one SeaText account?

Each site needs its own snippet and its own activation visit. The dashboard will list each site separately.

Will the snippet slow down my Thinkific pages?

The SeaText snippet loads asynchronously after the main page content. It does not affect page‑load metrics such as Largest Contentful Paint or First Input Delay.

Can I delay the snippet until after a consent manager gives permission?

Yes. Wrap the snippet in your consent manager’s callback so it only runs after the visitor accepts analytics or marketing cookies. Data collection will then start at that point.

Where can I find the snippet if I lose it?

Log into SeaText, go to the Main AI Hub, select your site, and open the Integration section. The JavaScript block is displayed there for copying.

What happens if I remove the snippet later?

Data collection stops immediately. Historical data remains in your dashboard according to your plan’s retention policy. Re‑adding the snippet resumes collection without a new activation visit if the domain is still linked.

How the Thinkific Integration Works

Quick answer: The SeaText error after saving in Thinkific usually comes from three mistakes: the wrong footer-code field, a truncated JavaScript snippet, or a skipped 40-second activation visit.

SeaText connects to Thinkific through one JavaScript snippet. You copy the snippet from your SeaText dashboard. Then you paste it into Thinkific's Site Footer Code field. Thinkific injects that code on every page of your site.

The paste is only step one. SeaText still requires an activation handshake. You must visit your live site once and stay for at least 40 seconds. This visit links your domain to your SeaText account. The dashboard then shows your website name next to the SeaText logo.

SeaText says the name usually appears within five minutes. If it does not appear after 10 minutes, contact SeaText support. That delay can indicate a platform-specific installation problem.

Common Causes of Integration Errors

Snippet Pasted in the Wrong Field

Thinkific has several code injection fields. The SeaText snippet belongs only in Site Footer Code. Pasting it into Site Header Code can change load order. It may also cause the script to fail before it initializes. Use the exact field from the integration guide.

Truncated or Corrupted JavaScript Snippet

A partial copy is a common cause. Text editors and browsers can insert smart quotes, extra spaces, or line breaks. The code may look the same but contain invisible characters. Compare your pasted code with the code in the SeaText dashboard. Look for missing script tags or truncated lines. If in doubt, copy the snippet again and paste it as plain text.

Skipped Activation Visit

Saving the code does not activate SeaText. The system waits for a real browser visit. You must stay on the live page for at least 40 seconds. This visit creates the connection between your domain and account. Without it, the dashboard may still show no connected website.

Not Waiting for the Propagation Window

SeaText needs up to five minutes to show the connected site name. Checking too early creates a false failure. Wait the full five-minute window. If the name is missing after 10 minutes, contact support.

Caching and Browser Conflicts

Thinkific may serve a cached page. The old footer code may still be running. Open your site in an incognito window. Clear the browser cache if needed. Cached pages can hide a successful installation.

How to Confirm the SeaText Script Is Loading

You do not need to be a developer to verify the script. Open your live site in a desktop browser. Right-click the page and select Inspect or View Page Source. Look for the SeaText snippet in the page source. If you use Chrome, open DevTools and go to the Network tab. Reload the page and look for a request to the SeaText server. A successful load means the snippet is present and reachable.

Another quick check uses the browser console. Open DevTools and click Console. If the snippet has a syntax error, the console will show a JavaScript error. The error message often points to the exact line where the paste broke. Share that message with support if needed.

You can also use the SeaText dashboard. The site name next to the SeaText logo is the clearest success signal. The integration guide says this name appears within five minutes of the activation visit. If the name appears, the script is loading and the connection is live.

What a Successful SeaText Install Looks Like

After a correct install, Thinkific saves without error. The snippet sits alone in the Site Footer Code field. The live page loads normally. No JavaScript console errors appear.

You then complete the activation visit. Open the live site in a clean browser session. Stay for at least 40 seconds. After five minutes, the SeaText dashboard displays your website name next to the SeaText logo. This confirms the connection.

The next step is activation. Go to the Main AI Hub. Choose the AI agents you need. Click Configuration to adjust their parameters. SeaText then serves automatic translations and variants. You can review and edit them in Variants Edit.

This is the complete path: copy code, paste in Site Footer Code, save, visit the live site for 40 seconds, wait five minutes, then activate agents in Main AI Hub. Any break in this path can create an error or a missing connection.

Diagnostic Checklist: Step-by-Step Verification

1. Confirm the paste location. Go to Thinkific Admin → Settings → Code & Analytics → Site Footer Code. Remove any duplicate SeaText snippets.
2. Inspect the snippet. Compare the code in Thinkific with the code in your SeaText dashboard. Check for missing opening or closing script tags.
3. Save and publish. Click Save in Thinkific. If Thinkific prompts you to publish code changes, publish them.
4. Open an incognito window. Navigate to your live Thinkific site. This bypasses cached versions of the page.
5. Complete the activation visit. Stay on the page for at least 40 seconds. Do not switch tabs or close the window early.
6. Wait five minutes. Go back to the SeaText dashboard. Look for your website name next to the SeaText logo.
7. Check the console. Open DevTools and look for JavaScript errors. Fix any syntax issue in the pasted code.
8. Escalate after 10 minutes. If the site name is still missing, contact SeaText support. Include your site URL and a screenshot of the Site Footer Code field.

Key Facts

Limitations and When This Advice Does Not Apply

This guide covers the standard SeaText JavaScript path for Thinkific. Some setups fall outside it.

• Custom Thinkific themes that remove or defer footer scripts.
• Content Security Policy headers that block external or inline scripts.
• Server-side rendering setups that do not inject the footer code on every route.
• Other third-party scripts that conflict with SeaText's execution.

If your site uses a custom theme or CSP, you may need a developer. The activation visit still must happen on a public live page. Password-protected and maintenance-mode pages can block the handshake. Temporarily disable protection, complete the visit, then re-enable it.

FAQ

Why does the SeaText dashboard still show "No website connected" after I saved the code?

You likely skipped the activation visit or checked too early. Complete a 40-second visit on the live site. Then wait up to 10 minutes.

Can I paste the snippet in Thinkific's Site Header Code instead?

No. The integration guide specifies Site Footer Code. Header placement is not supported and can cause load-order errors.

What if I see a JavaScript error in the browser console?

Compare the pasted snippet with the original. Look for missing script tags, truncated lines, or curly quotes. Re-copy the snippet and paste it as plain text.

Do I need to repeat the activation visit for each page or language?

No. One visit on the primary domain registers the site. Subdomains and language paths are handled after the main domain is connected.

Will SeaText work if my Thinkific site is password-protected?

No. The activation visit needs a public page. Temporarily disable protection, perform the visit, then re-enable it.

What should I tell support if the site name never appears?

Provide your Thinkific site URL, the exact snippet you pasted, and a screenshot of the Site Footer Code field. Mention any custom theme, CSP headers, or other scripts.

All paid Thinkific plans (Basic, Pro, and Premier) support the SeaText code insertion because they include the Site Footer Code field; the free plan does not. This field is located in Settings → Code & Analytics. If you need SeaText, choose Basic or higher.

Takeaway: If you need SeaText, choose Basic or higher. The integration steps are the same across all paid tiers.

Why Thinkific Plan Eligibility Matters

SeaText is a JavaScript snippet that runs on your site. It rewrites headlines, offers, and CTAs based on visitor intent. To work, it needs to be inserted into your site’s footer code. Thinkific restricts this feature to paid plans. If you are on the free plan, you cannot add the snippet. That means you cannot use SeaText at all. Knowing this upfront saves time. You can decide to upgrade or choose a different platform.

What the SeaText JavaScript Does

SeaText is a set of AI agents. They adapt your site in real time. For example, the Google Ads Agent rewrites landing pages to match each keyword. The Bot Refund Agent detects invalid clicks. The Translation Agent opens your site to 125 languages. All these agents rely on a small JavaScript code placed in your site footer. Once installed, the code runs on every page. It then activates the agents you choose. The installation is simple: copy the code, paste it, and save. No coding skills needed.

Step-by-Step Installation on a Paid Plan

1. Copy the JavaScript code provided by SeaText. You can find it in your SeaText account under the integration section.
2. Go to your Thinkific Admin Dashboard.
3. Select Settings then the Code & Analytics tab.
4. In the Site Footer Code field, paste the JavaScript code.
5. Click Save.
6. Visit your site once and stay on the page for at least 40 seconds. This activates the AI and links it to your account.
7. Wait up to five minutes. Your website name should appear next to the SeaText logo at the top of your SeaText dashboard. If it does not appear after 10 minutes, contact SeaText support.

That is it. The integration is complete. You can now proceed to activate the AI agents you need.

Thinkific Plan Comparison

Thinkific offers four plans. The free plan is good for testing the platform. But it lacks the Code & Analytics tab. Without that tab, you cannot add custom JavaScript. The Basic plan starts at $49/month. It includes the Code & Analytics tab. You can insert the Site Footer Code. The Pro plan ($99/month) adds more advanced features like assignments and certificates. The Premier plan offers custom pricing and all features. All three paid plans support the same Site Footer Code field. The integration works identically on each. For full feature details, see Thinkific’s pricing page.

Limitations and Troubleshooting

The free plan is the main limitation. You cannot upgrade the free plan to add custom code without paying. Other limitations: The Site Footer Code field accepts only one snippet. If you have multiple scripts, you need to combine them. Also, the code runs on every page. You cannot target specific pages unless you add conditional logic. If the code does not work, check that you pasted it correctly. Also ensure you saved the settings. Visit your site and wait 40 seconds. If the SeaText dashboard still shows no link, clear your site cache. Some Thinkific custom domains may require extra configuration. Contact SeaText support if issues persist.

How to Upgrade and What Happens Next

To upgrade, log into your Thinkific admin. Go to Settings → Billing. Choose a paid plan. Once upgraded, the Code & Analytics tab appears immediately. Then follow the installation steps above. After installation, activate your SeaText agents. Go to the SeaText dashboard and choose which agents to enable. For example, you can turn on the Google Ads Agent or the Translation Agent. Each agent works independently. You can start with one and add more later. The integration remains active as long as you keep the code in the footer. If you downgrade to the free plan, the code stops working. Plan ahead: choose a paid plan that fits your budget and needs.

Frequently Asked Questions

Can I use SeaText on the Thinkific free plan? No. The free plan does not include the Code & Analytics tab. You need at least the Basic plan.

Does the integration work on Thinkific Plus? Yes. Thinkific Plus is a custom enterprise plan. It includes the Code & Analytics tab. The steps are the same.

What if I have multiple Thinkific sites? You need to install the SeaText code on each site separately. Each site must be on a paid plan.

Do I need coding skills to install SeaText? No. You only copy and paste the JavaScript code. No coding required.

Will the SeaText code slow down my site? No. The code is lightweight. It loads asynchronously. It does not affect page speed.

Can I remove the code later? Yes. Go back to Settings → Code & Analytics and delete the code from the Site Footer Code field. Then save.

Verdict: SeaText provides AI‑powered, real‑time visitor analytics and conversion tools, whereas Thinkific’s built‑in analytics deliver higher‑level course and revenue reports.

Who should choose SeaText?

If you need real‑time conversion boosts, multilingual testing, bot‑click refund evidence, or AI‑driven visitor insights, SeaText is the better fit. The platform deploys up to 20 autonomous agents that rewrite copy, translate content, detect bots, and run A/B tests automatically on any page where the snippet is installed (S2). This makes it ideal for marketers running paid ads who want each click to see a keyword‑matched landing page.

Who should choose Thinkific Analytics?

If your primary goal is tracking learner progress, revenue, and overall course health without extra code, Thinkific’s built‑in analytics are sufficient. The platform provides revenue dashboards, learner‑progress tracking, engagement metrics, and the ability to build custom reports (S1). Course creators who do not run paid traffic or need multilingual pages can rely solely on these reports.

Conditional recommendation

Use SeaText when you want to optimize every visitor interaction and expand globally. Keep Thinkific analytics if you only need course‑level reporting. Running both makes sense when you want deep visitor data and course performance in one dashboard.

What is SeaText?

SeaText is an AI platform that deploys autonomous agents to rewrite copy, translate content, detect bot traffic, and run A/B tests automatically. The agents work in real time on any page where the snippet is installed. According to the homepage, the system can deploy 20 agents that increase conversion, recover ad spend lost to bots, translate across 125 languages, and continuously optimize every visitor journey (S2).

What SeaText does after you save the code

After you paste the JavaScript snippet into Thinkific’s Site Footer Code field and click Save, the script becomes live on every page of your site. You must then visit your own site and stay on a page for at least 40 seconds; this activates the AI and links the site to your SeaText account (S1). Within five minutes the SeaText logo appears at the top of the integration page, confirming the connection. Once active, the agents begin analyzing visitor behavior, rewriting headlines, offers, and CTAs for each visitor, translating pages into up to 125 languages, detecting bot clicks, and generating refund‑ready reports for ad platforms (S2, S3). Data starts flowing into the SeaText dashboard within minutes, and you can configure each agent from the Main AI Hub.

What Thinkific analytics measures and what it cannot see

Thinkific’s built‑in analytics cover revenue dashboards, learner‑progress tracking, engagement metrics, and custom report building (S1). These tools help course creators understand enrollment trends, completion rates, and overall financial performance. However, Thinkific does not provide visitor‑level behavior data, real‑time content personalization, multilingual translation, bot detection, or A/B testing of page copy. It also cannot attribute a specific paid‑click keyword to a page variation or generate evidence for ad‑spend refunds.

Step‑by‑step installation walkthrough for the Site Footer Code field

1. Log in to your Thinkific Admin Dashboard.
2. Navigate to Settings → Code & Analytics.
3. Select the Site Footer Code tab.
4. Paste the JavaScript snippet provided by SeaText into the text area.
5. Click Save at the bottom of the page.
6. Open a new browser tab, go to your live site, and stay on any page for at least 40 seconds.
7. Return to the SeaText integration page; wait up to five minutes for the SeaText logo and your site name to appear, confirming activation.
8. If the logo does not appear after 10 minutes, contact SeaText support (S1).

Practical use cases and example scenarios

• A course creator runs Google Ads for a “Python for Beginners” course. SeaText’s Google Ads Agent rewrites the landing page headline to match each searched keyword, boosting conversions by up to 35 % (S3). Thinkific still tracks enrollment and revenue.
• An international educator wants to reach Spanish, French, and Japanese learners. SeaText’s Translation Agent automatically translates all pages into 125 languages, increasing international sign‑ups by 60 % (S4). Thinkific reports show completion rates per language cohort.
• A marketer suspects bot traffic is inflating ad costs. SeaText’s Bot Protection Agent detects invalid clicks, builds forensic reports, and helps recover up to 20 % of ad spend from Google and Meta (S5). Thinkific analytics remain unchanged.

Cost and subscription considerations

SeaText pricing depends on which agents you activate; the vendor does not publish a fixed price list, so you must check with the vendor for exact rates (S2). Thinkific analytics are included in every Thinkific subscription tier at no extra cost. If you only need course‑level reporting, the bundled Thinkific analytics are more cost‑effective. If you activate multiple SeaText agents (CRO, translation, bot refund, A/B testing), the monthly cost can exceed the Thinkific plan, so evaluate ROI before committing.

Limitations and troubleshooting

• SeaText only starts collecting data after a visitor stays on the page for at least 40 seconds; very short visits are not recorded.
• If the snippet is placed outside the Site Footer Code field, the AI will not activate.
• Activation confirmation can take up to five minutes; wait before assuming failure.
• Browser cache or ad‑blockers may prevent the SeaText logo from appearing; clear cache and disable blockers for the test visit.
• Thinkific analytics cannot be extended with AI personalization or multilingual testing; they remain static reports.

When to keep both analytics solutions

• You run paid ads and need AI to match landing‑page copy to each keyword (SeaText) while still tracking student progress and revenue across courses (Thinkific).
• You want AI‑tested translations for international learners (SeaText) and also need to monitor their course completion rates (Thinkific).
• You require bot‑click refund evidence for ad platforms (SeaText) but also rely on Thinkific’s revenue dashboards for financial reporting.

Step‑by‑step decision framework

1. Identify your primary goal: visitor conversion vs. course performance.
2. Check if you need multilingual testing or real‑time copy changes.
3. Evaluate budget: SeaText agents are priced per activation; Thinkific analytics are included.
4. Run a short pilot: enable SeaText on a single course page and compare the new visitor metrics to Thinkific’s reports.
5. Decide: keep SeaText only, keep Thinkific only, or run both based on the pilot results.

Key facts

FAQ

• Do I need to keep both analytics? Only if you require both visitor‑level conversion data and course‑level performance metrics.
• Can SeaText replace Thinkific’s reports? No. SeaText adds visitor insights but does not track learner progress or revenue dashboards.
• How long does it take for SeaText to start reporting? After the 40‑second visit, data appears within a few minutes; full activation may take up to five minutes.
• Is there an extra cost? SeaText pricing depends on the agents you activate; check with the vendor for exact rates.
• What if the snippet fails? Verify the code is in Settings → Code & Analytics → Site Footer Code and re‑save. Clear browser cache if needed.
• Does SeaText work on all Thinkific pages? Yes, the snippet runs site‑wide once placed in the Site Footer Code field.
• Can I disable specific SeaText agents? Yes, from the Main AI Hub you can activate or deactivate each agent individually.

SeaText’s cost is separate from Thinkific. Thinkific does not charge extra for adding custom JavaScript, so the only expense after you paste and save the SeaText snippet is the SeaText subscription you choose.

What is SeaText?

SeaText is an AI platform that adds autonomous agents to a website. Agents rewrite copy, translate content, protect against bot traffic, and run A/B tests automatically (S2).

How the Thinkific integration works

Copy the JavaScript snippet from SeaText. In Thinkific go to Settings → Code & Analytics → Site Footer Code, paste the snippet, and click Save (S1). Visit the site for at least 40 seconds to activate the AI and link it to your SeaText account (S1). Wait up to five minutes for the site name to appear next to the SeaText logo (S1).

Cost drivers for SeaText

The primary driver is the number of monthly active users (MAU). An active user is counted each month when a visitor loads a page that includes the SeaText snippet (S1). Pricing scales in tiers; higher MAU moves you to a higher tier (S2). There are no per‑event overage fees; the tier for the billing period reflects the peak MAU reached (S5). Some advanced agents such as the Bot Refund Agent may be sold as add‑ons (S3).

SeaText Pricing Tiers Overview

SeaText offers several tiers that increase with MAU (e.g., Starter, Growth, Enterprise). Exact user limits and monthly prices are published on the pricing page (S2). Each tier unlocks a larger set of agents and higher usage caps. The pricing page also lists any add‑on agents and their separate costs (S3).

Estimating Your Monthly Cost

To estimate cost, first determine your average monthly unique visitors from analytics. Next, check the SeaText pricing page for the tier that covers that MAU range. Multiply the tier’s monthly price by 12 for an annual view. Example: a site with 15,000 MAU falls into the Growth tier; if that tier costs $299/month, the annual estimate is $3,588 (prices illustrative; verify on pricing page).

Comparing SeaText to Alternative AI Agents

SeaText focuses on autonomous copy rewriting, translation, bot protection, and A/B testing for marketing sites (S2). Mutiny specializes in B2B personalization and account‑based experiences. VWO provides a broad experimentation platform with visual editors. Optimizely targets large enterprises with full‑stack feature flagging and experimentation. The table above summarizes key buyer criteria.

Tips to Optimize SeaText Costs

• Monitor MAU weekly; pause low‑traffic pages from the snippet to reduce counts.
• Use the free 1‑month pilot to validate ROI before committing (S4).
• Enable only the agents you need; each add‑on may increase the tier price (S3).
• Set up alerts in your analytics for traffic spikes so you can anticipate tier changes.
• Negotiate annual billing for a discount if your MAU is stable.

Limitations and considerations

• Pricing is tied to active users, not a flat monthly fee.
• Thinkific imposes no extra cost, but the JavaScript snippet must remain for the AI to stay active.
• If the site name does not appear after 10 minutes, contact SeaText support (S1).

Frequently asked questions

Do I pay Thinkific for the SeaText code?

No. Thinkific’s pricing is independent of custom code installations.

How is SeaText billed?

Based on the number of monthly active users; see the SeaText pricing page for exact tiers.

Can I try SeaText before paying?

SeaText offers a free 1‑month pilot on its site; check the pricing page for details (S4).

What if my traffic spikes?

Your subscription may move to a higher tier because pricing scales with active users.

Is there any hidden fee from Thinkific?

Thinkific does not charge for the JavaScript snippet or for the integration process.

Testing SeaText on a Thinkific site before you go live helps you catch errors, confirm that each AI agent works as expected, and avoid surprising visitors with broken content.

Why test SeaText before going live

Running a live site with untested AI changes can lead to misleading headlines, broken calls‑to‑action, or language errors that hurt trust.

A test lets you see exactly how each agent rewrites copy, translate pages, or flag bot clicks without affecting real customers.

You can verify that the snippet loads correctly, that the site appears in the SeaText dashboard, and that the agents produce the expected output before you expose the changes to traffic.

What SeaText changes on a Thinkific site

When activated, SeaText runs autonomous agents that modify page elements in real time.

The Conversion Agent tests different headlines, offers, and calls‑to‑action to see which version drives more clicks or sign‑ups.

The Google Ads Agent rewrites the landing page to match the exact keyword that triggered a paid click, making the page feel custom‑built for that search.

The Translation Agent displays the page in up to 125 languages, swapping headlines, buttons, and product copy based on the visitor’s locale.

The Bot Refund Agent watches paid traffic for signs of invalid clicks, builds evidence reports, and shows a potential refund amount in the dashboard.

Other agents can personalize copy, slow fast scrollers near calls‑to‑action, or adapt content to visitor source.

How the activation and linking process works end-to-end

1. Log in to your SeaText account and copy the JavaScript snippet from the Integration page.
2. In Thinkific, go to Admin Dashboard → Settings → Code & Analytics → Site Footer Code.
3. Paste the snippet into the footer code field and click Save.
4. Open the test page in a browser and stay on it for at least 40 seconds. This triggers the AI to link the site to your SeaText account.
5. Wait 5‑10 minutes. The top of the SeaText dashboard should show your site name next to the SeaText logo, confirming the connection.
6. If the name does not appear, proceed to the troubleshooting steps in the next section.

How to verify each SeaText agent during testing

Conversion Agent

After activation, open the Variants Edit section in SeaText. You will see automatically generated headline and CTA variants for the test page. Review them for clarity and relevance.

To see the agent in action, visit the test page with different UTM parameters or reload the page several times; the displayed headline may change as the agent runs its A/B test.

Google Ads Agent

Add a test Google Ads‑style UTM parameter (e.g., ?utm_source=google&utm_term=test+keyword) to the test page URL.

Visit the page and wait a few seconds. The headline should rewrite to include the keyword from the parameter, showing the agent’s real‑time matching.

Translation Agent

Append a language code to the URL (e.g., ?lang=es) or use the browser’s language setting if you have enabled language detection.

Reload the page; the visible text should appear in the selected language, confirming the Translation Agent is active.

Bot Refund Agent

In the SeaText dashboard, locate the Bot Refund Agent card. It displays a count of detected bot clicks and an estimated refund amount.

You can simulate a bot visit by using a headless browser or a tool that sends rapid requests; the agent should log those events.

Check the Variants Edit section for any bot‑related evidence notes that the agent may have added.

What to do when activation fails

• Double‑check the snippet: ensure it was copied exactly, with no extra spaces or missing characters.
• Confirm it is placed in the Thinkific Site Footer Code field and that you clicked Save.
• Clear your browser cache or open an incognito window before the 40‑second visit.
• Visit the test page and stay on it for at least 40 seconds; do not navigate away during that time.
• After the visit, wait the full 5‑10 minutes before checking the dashboard.
• Open the browser console (F12) and look for network errors or JavaScript warnings that could block the snippet.
• If the site name still does not appear, note the exact time and any error messages, then contact SeaText support with that information.

Readiness checklist and next steps

Use this checklist to confirm your test is complete before going live:

1. Paste the SeaText snippet into the Thinkific Site Footer Code of your test site.
2. Save the changes.
3. Visit the test page and remain on it for at least 40 seconds.
4. Wait 5‑10 minutes and verify the site name appears in the SeaText dashboard.
5. Activate the agents you intend to use (Conversion, Google Ads, Translation, Bot Refund, etc.) from the Main AI Hub.
6. Open Variants Edit and review the automatically generated variants for each agent.
7. Simulate visitor scenarios (different UTM parameters, language codes, bot traffic) and observe the expected changes.
8. Confirm the site loads without errors, no broken elements, and the agents display the intended content.
9. Document any issues or adjustments needed.

Once the checklist passes, repeat the same steps on your live Thinkific site: paste the snippet, save, visit the live page for 40 seconds, wait for dashboard confirmation, then activate the agents. Monitor the SeaText dashboard for performance and adjust variants as needed.

Why the warning appears

SeaText looks for its JavaScript identifier in the global footer of your Thinkific site. If the snippet is missing from that location, SeaText cannot confirm the connection and shows a "code not detected" warning.

The warning also appears when the activation visit has not been completed or when detection has not finished within the expected time window.

Correct placement of the SeaText snippet

SeaText provides a single JavaScript block that must be added to Thinkific’s global Site Footer Code field. The steps are:

1. Copy the full SeaText JavaScript snippet from your SeaText account dashboard.
2. Log in to the Thinkific Admin Dashboard.
3. Select Settings from the left‑hand menu.
4. Open the Code & Analytics tab.
5. Find the Site Footer Code field.
6. Paste the entire snippet into that field. Do not add extra characters before or after the code.
7. Click Save at the bottom of the page.

Thinkific stores this code globally, so it appears on every page of your site.

Activation visit and detection window

After saving the snippet, you must visit your live Thinkific site in a browser window.

1. Open the site in an incognito or private window to avoid cached versions.
2. Stay on any page for at least 40 seconds without navigating away. This visit triggers SeaText’s activation ping.
3. Wait between 5 and 10 minutes. SeaText checks the footer during this period.
4. If the site name appears next to the SeaText logo in your SeaText dashboard, the connection is successful.

If the site name does not appear after 10 minutes, contact SeaText support immediately.

Common placement mistakes and likely causes

Many users paste the snippet into fields that are not the global Site Footer Code field. Thinkific’s editor may remove script tags from those non‑global fields to protect page stability. This removal is a likely cause of the warning, but the exact behavior can vary.

• Placing the code in a course‑level custom code section.
• Adding the snippet to a lesson’s multimedia or content editor.
• Using the Site Header Code field instead of the Site Footer Code field.
• Accidentally truncating the snippet while copying.

When any of these occur, the snippet is not present in the global footer, so SeaText cannot detect it.

How to verify the installation

After the activation visit, log back into your SeaText account.

• If your website name appears next to the SeaText logo, the integration is active.
• If the name is missing, double‑check that the full snippet is in the Site Footer Code field.
• Confirm that you stayed on the live site for at least 40 seconds.
• If everything looks correct and the warning persists after 10 minutes, reach out to SeaText support for help.

Limitations of the Thinkific integration

The SeaText snippet works only when placed in the global Site Footer Code field. It does not run from page‑level editors, lesson blocks, or third‑party apps that inject their own code.

If you use a custom Thinkific theme that modifies the footer, you may need to ensure the theme does not overwrite the snippet during updates.

SeaText’s AI features activate only after the snippet is detected and the activation visit is completed. The snippet itself does not change page speed; it loads asynchronously as designed by SeaText.

Frequently Asked Questions

Where should I paste the SeaText JavaScript?

In Thinkific Admin Dashboard → Settings → Code & Analytics → Site Footer Code field. This is the only location SeaText scans.

Do I need to stay on the site for exactly 40 seconds?

Yes. SeaText requires a continuous visit of at least 40 seconds to trigger its activation ping.

How long does detection take?

SeaText checks the footer between 5 and 10 minutes after the activation visit. If the site is not listed after 10 minutes, contact support.

What if I placed the snippet in a lesson editor?

Thinkific may remove script tags from lesson editors. This is a likely cause of the warning. Move the snippet to the Site Footer Code field and repeat the activation visit.

Can I test the snippet on a staging site?

The source instructions refer only to the live site. Testing on a staging environment is not covered by the official steps.

Will the snippet affect my page load time?

The SeaText JavaScript loads asynchronously and is designed to be lightweight. No page‑speed impact is documented in the source material.

What Are the Most Common Mistakes When Saving SeaText Code in Thinkific?

When you add SeaText to your Thinkific site, the process is straightforward – but small errors can stop the integration from working. Based on the official SeaText integration guide and common user reports, three mistakes happen most often:

1. Editing the JavaScript snippet before pasting it.
2. Placing the code in page-specific code blocks instead of the global Site Footer Code field.
3. Forgetting to publish or save your changes after inserting the code.

Each of these mistakes breaks the connection between SeaText and your Thinkific site. Below we explain why they happen, how to recognise them, and the exact steps to avoid them.

Mistake 1: Editing the JavaScript Snippet

SeaText provides you with a single JavaScript snippet to copy. Some users try to customise it – for example removing certain lines, adding comments, or changing variable names. This almost always breaks the integration.

Why it fails: The snippet is a complete script that SeaText’s servers expect to see exactly as delivered. Any change, even a missing semicolon, can prevent the script from loading or communicating with the SeaText platform.

How to avoid it: Copy the code exactly as shown in your SeaText dashboard. Use Ctrl+C (or Cmd+C) and paste it directly into the Thinkific field without any manual edits. If you need to customise behaviour later, SeaText provides separate settings inside the platform – not by editing the snippet.

Mistake 2: Placing the Code in Page-Specific Code Blocks

Thinkific lets you add custom code to individual pages (for example, in the Course Builder or Landing Page editor). Some users put the SeaText snippet there rather than in the global site footer.

Why it fails: SeaText needs to load on every page of your site – not just one course or landing page. When you place the code in a page-specific block, it only runs on that page, and SeaText cannot track visitors or optimise across your entire site. The activation step (visiting your site for 40 seconds) may also fail because the script is not present on the homepage.

How to avoid it: Always paste the SeaText snippet into the Site Footer Code field. To find this: go to your Thinkific Admin Dashboard → Settings → Code & Analytics → Site Footer Code. This field applies the code to every page automatically.

Mistake 3: Forgetting to Publish or Save Changes

After pasting the code, you must click the Save button in the Code & Analytics section. If you navigate away without saving, the code is not stored. Thinkific also requires that your site is published – if you are using a draft or staging site, the code may not be live.

Why it fails: Without saving, the script never gets added to your site’s HTML. Even if you saw the code in the field, it is not active until you click Save. Additionally, if your site is not published, visitors (and the SeaText activation script) cannot reach it.

How to avoid it: After pasting the code, look for the blue Save button and click it. Wait for a confirmation message. Then, visit your live public site (not the preview mode) and stay on the page for at least 40 seconds. This activates the SeaText AI and links it to your account.

How to Correctly Save SeaText Code in Thinkific – Step by Step

Follow these exact steps to avoid the three mistakes above:

1. Copy the JavaScript code from your SeaText account (do not edit it).
2. Go to your Thinkific Admin Dashboard.
3. Select Settings → Code & Analytics.
4. In the Site Footer Code field, paste the code.
5. Click Save.
6. Visit your live website (the public URL, not a draft) and stay on the page for at least 40 seconds.
7. Wait 5-10 minutes, then check your SeaText dashboard – your website name should appear next to the SeaText logo.

If you do not see your site after 10 minutes, contact SeaText support. This could indicate a problem with the installation.

Key Facts About the SeaText–Thinkific Integration

Limitations and When This Advice Does Not Apply

The steps above assume you are using a standard Thinkific plan (Basic, Pro, or Premier) that includes the Code & Analytics section. The free Thinkific plan does not have this feature, so you cannot install SeaText via the footer code method. In that case, you would need to upgrade your plan or use a different integration approach (e.g., via a third-party script manager if available).

Also, if you are using a custom domain with Thinkific, ensure the domain is correctly configured before saving the code. A misconfigured domain can prevent the SeaText script from loading even if the code is saved correctly.

How to Verify the Script is Active After Saving

After saving the code, you can verify the SeaText script is live by viewing your page source. Open your browser’s developer tools (usually F12) and search for “seatext” or the script URL. If you see the exact snippet you pasted, the installation is correct. The 40-second visit is required because SeaText’s AI needs to load on the page and confirm the script is running. This visit triggers the linking process between your site and your SeaText account. Without this step, the integration remains inactive, even if the code is saved correctly.

FAQ – Common Questions About Saving SeaText Code in Thinkific

Why can’t I edit the SeaText snippet?

Editing the snippet can break the script’s connection to SeaText’s servers. The snippet is designed to work exactly as provided. Any changes may cause the script to fail silently.

What if I accidentally placed the code in a page-specific block?

Remove the code from that block and paste it into the Site Footer Code field instead. Then test the integration again by visiting your live site.

I saved the code but nothing happens – what should I do?

First, check that you saved the Code & Analytics section. Then, clear your browser cache and visit your live site. Stay for at least 40 seconds. If still not working, contact SeaText support.

Can I use SeaText on a Thinkific staging site?

Yes, but only if the staging site is publicly accessible. The activation step requires a live URL. If your staging site is password-protected, SeaText may not be able to verify the installation.

How long does it take for SeaText to activate after saving?

After you save the code and visit your site for 40 seconds, it can take up to 10 minutes for your website name to appear in the SeaText dashboard. If it takes longer, contact support.

Do I need to add the code to every page?

No. The Site Footer Code field applies the code to all pages automatically. Adding it to individual pages is unnecessary and will cause the integration to fail.

What if my Thinkific site uses a custom code editor?

Some users have access to Thinkific’s custom code editor (in the Theme section). However, the recommended and easiest place is the Code & Analytics section. Using the theme editor may work, but it is not officially documented by SeaText for this integration.

SeaText translates WordPress pages, posts, products, and headlines into 125 languages automatically. The plugin activates in under one minute with no page limits or language caps. New content is detected and translated in the background, while you retain control to edit translations and preserve brand voice.

What SeaText Automatic Translation Does

SeaText connects to your WordPress site and translates every page, post, product, and headline into up to 125 languages. The translation runs automatically without manual work. When you publish new content, SeaText detects it and translates it in the background. There are no page limits and no language limits for the content you choose to translate.

The system uses AI agents to handle translation. The Website Translation Agent translates pages into 125 languages with control. This means you get automatic multilingual content across your entire site without managing translation projects or hiring translators.

How Activation Works

You activate SeaText on WordPress in under one minute. The plugin is built for WordPress and the tools you already use. Once activated, SeaText detects each visitor's language and translates WordPress pages instantly. The process requires no technical setup beyond installing and activating the plugin.

After activation, SeaText keeps new posts, products, and updates translated automatically. You do not need to trigger translation manually for each new piece of content. The system handles it continuously.

Language Coverage and Scale

SeaText supports translation into 125 languages. This covers the vast majority of internet users worldwide. The translation applies to all WordPress content types: pages, posts, products, headlines, buttons, and offers. There are no caps on the number of pages or languages you can use.

This scale means a single WordPress site can serve visitors from virtually any country in their native language. The automatic detection ensures each visitor sees content in their preferred language without manual language selection.

Control Over Automatic Translation

Automatic does not mean uncontrolled. You can edit translations to preserve brand voice and review key pages. The system allows manual adjustments when you want to refine messaging for specific markets. You can also use advanced A/B tested translation to find the message that sells best in each market.

This control layer matters for brand consistency. While the bulk translation happens automatically, you have the ability to override any translation that does not match your brand standards or local market expectations.

Multilingual SEO Included

SeaText provides free automatic multilingual SEO for every translated page. This means translated pages are optimized for search engines in each target language. The system handles technical SEO aspects like hreflang tags and language-specific URLs automatically.

Multilingual SEO helps your translated content rank in local search results. This drives organic traffic from new markets without additional SEO work. Each translated page gets the same SEO treatment as your original content.

Integration With Other AI Agents

SeaText runs 20 autonomous AI agents that work together. The Website Translation Agent is one of these agents. Others include the Google Ads Landing Page Agent, Local AI SEO Agent, Ecommerce Product Copy Agent, and AI A/B Testing Agent. These agents can enhance translated content further.

For example, the Ecommerce Product Copy Agent optimizes product names, descriptions, and CTAs. The AI A/B Testing Agent generates variants and scales winners. The Local AI SEO Agent ranks for "near me" and city service searches. These agents work on translated content as well as original content.

Practical Scenario: Launching a Multilingual Store

An ecommerce site installs SeaText and activates it in under one minute. The site has 500 products and 50 pages. SeaText translates all content into 125 languages automatically. New products added next week are translated without any action from the store owner.

The store owner reviews translations for top-selling products and adjusts a few headlines for cultural fit. The Local AI SEO Agent starts ranking product pages for local search terms in each language. The Ecommerce Product Copy Agent tests product description variants to increase add-to-cart rates in each market.

Limitations to Consider

SeaText translates text content automatically. The sources do not specify handling of images, videos, or dynamic JavaScript content. Translation quality for highly technical, legal, or creative content may need human review. The system is designed for marketing and business content where AI translation performs well.

You should plan to review key conversion pages like checkout, pricing, and legal pages. The ability to edit translations manually addresses this, but it requires time allocation for review.

Frequently Asked Questions

How long does activation take?

Activation takes under one minute. You install the WordPress plugin and activate it. No additional configuration is required for basic translation to start.

Are there limits on pages or languages?

No. SeaText has no page limits and no language limits for the content you choose to translate. You can translate unlimited pages into all 125 supported languages.

Can I edit translations after they are generated?

Yes. You can edit translations to preserve brand voice, review key pages, and adjust phrasing for local markets. The system gives you control over automatic output.

Does SeaText handle SEO for translated pages?

Yes. Free automatic multilingual SEO is included for every translated page. This covers technical SEO elements needed for multilingual search visibility.

What happens when I publish new content?

SeaText detects new WordPress pages, posts, products, and headlines automatically and translates them in the background. No manual trigger is needed.

Can I use SeaText with other translation plugins?

The sources do not address compatibility with other translation plugins. SeaText is designed as a complete automatic translation solution.

No, SeaText does not offer a built-in URL exclusion rule. The automatic translation engine translates every page, post, product, and update on your WordPress site. There is no switch to stop translation for a specific URL before it happens. However, you have full control after translation. You can edit translations, preserve brand voice, and review key pages. This lets you effectively keep a URL in its original language by managing the translated version.

This matters because automatic translation is designed to run on its own. SeaText translates WordPress pages, posts, products, and updates automatically, with no page limits or language limits. Without a way to edit or review, every new page would be translated without your input. But SeaText gives you control after the translation is created.

How SeaText automatic translation works

SeaText's Website Translation Agent runs automatically. When you publish new content, SeaText sees it and translates it. This happens for every page, post, product, and update. There are no page limits and no language limits. The engine translates into 125 languages. This is the default behavior. As the SeaText WordPress page says, "Publish a new WordPress page, product, post, or headline. SEATEXT sees it and translates it."

Translation happens in the background. New content is translated automatically. You do not need to create translation jobs. The engine works on its own. This is the core feature of the Website Translation Agent.

What control do you have after translation?

Automatic does not mean uncontrolled. SeaText gives you several ways to manage translations after they are created. You can edit translations to fix errors or adjust wording. You can preserve brand voice by making sure the translated copy matches your brand tone. You can review key pages to ensure quality. You can also use advanced A/B tested translation when you want to find the message that sells best in each market. This is stated in the source: "Automatic does not mean uncontrolled. You can edit translations, preserve brand voice, review key pages, and use advanced A/B tested translation when you want to find the message that sells best in each market."

These controls are available after the translation is created. You do not set them before translation. This is the key difference from a URL exclusion rule. You cannot stop the translation from happening, but you can change the result.

Can you prevent a specific URL from being translated automatically?

The short answer is no. SeaText does not offer a URL exclusion feature. Every page is translated automatically. There is no setting to skip a specific URL before translation. However, you can manage the translation after it is created. If you want a URL to stay in the original language, you can edit the translated version to match the original content. This effectively makes the page appear untranslated. You can also delete the translated version if your setup allows removing pages. This is not the same as preventing the translation, but it achieves the same result. You must act after the translation is created.

This approach has trade-offs. The translation is created first, so it uses some resources. Visitors may briefly see the translated version before you edit it. You need to monitor new pages and act quickly if you want to keep them in the original language. For most sites, this is manageable.

Practical scenarios for managing translations

Here are three common scenarios where you might want to keep a URL in the original language after automatic translation. These examples show how to use editing controls.

Legal pages. You have a terms page that must stay in English for legal reasons. After SeaText translates it, you edit the translated version to display the original English text. This ensures the page remains in English for all visitors.

Pages under review. You have a product page that is not final. You want to avoid showing a translated version until it is ready. After the translation is created, you edit it to match the original draft. When the page is final, you can update the translation to the correct version.

Brand and trademark pages. A product name may lose meaning when translated. After translation, you edit the page to keep the brand name in the original language. You can also adjust the surrounding copy to preserve brand voice.

In each case, the control happens after translation. This is different from a rule that prevents translation. But it gives you the same outcome: the URL stays in the original language.

Common mistakes when managing translations

• Forgetting to edit the translation after creation. If you do not edit the translated version, it will remain in the target language. You need to check new pages regularly.
• Not checking all languages. SeaText translates into 125 languages. If you only edit the Spanish version, the French version may still be translated. You need to edit each language you want to keep in the original.
• Ignoring caching. Cached copies of the translated page may still be visible for a short time. The edit may not take effect immediately. Clear your cache if needed.
• Assuming the edit affects future updates. If you edit a translation, future automatic updates to the original page may overwrite your edit. You may need to re-edit after updates. Check the translation agent settings for this behavior.
• Not testing from a clean browser state. A cached page can make your edit look like it did not work. Test from an incognito window.

Limitations and edge cases

Editing translations after creation gives you control, but it has limitations. The translation is created first, so it briefly exists. Search engines may index the translated version before you edit it. The translated URL may appear in search results for a while. The exclusion rule does not remove it from search indexes immediately.

Language switchers can still allow visitors to manually choose a translated language. Your edit keeps the page in the original language for automatic serving, but visitors can still switch languages if your site has a language switcher. This is a separate concern.

Multiple URL versions can cause issues. WordPress, page builders, and caching plugins can create alternate URLs for the same page. If you edit one version, another version may still be translated. Check all URL variants.

Already translated pages are not affected by your edit if you edit after the fact. The edit changes the current version, but any previously cached or indexed versions may persist. This is the same as with URL exclusion rules.

Key facts at a glance

Frequently asked questions

Can I set a rule to stop a URL from being translated automatically?

No. SeaText does not have a URL exclusion feature. Every page is translated automatically. You manage translations after they are created.

How do I keep a page in the original language?

Edit the translated version after it is created. Change the content to match the original language. This makes the page appear untranslated.

Does editing one language affect all languages?

No. You need to edit each language separately. If you want the page to stay in the original language for all visitors, edit each translated version.

Will my edit be overwritten by future automatic updates?

It depends on the translation agent settings. Check the documentation for your setup. Some versions may overwrite edits if the original page is updated. You may need to re-edit after changes.

How long does it take for an edit to take effect?

The edit is applied immediately on the server. However, cached copies may still show the old translation for a short time. Clear your cache to see the change faster.

Can I delete a translated version?

Depending on your setup, you may be able to delete the translated page. This removes the translation entirely. Check your WordPress and SeaText settings for deletion options.

Yes, SeaText supports wildcard patterns (e.g., /campaign/*) and simple regex for flexible exclusion rules. You set these rules in the Exclusion Rules section of the SeaText dashboard before any agents run.

Why exclude pages by URL pattern or regex?

Excluding pages lets you prevent agents from modifying content that should stay unchanged. Common reasons include protecting checkout pages, preserving legal disclaimers, avoiding translation of user‑generated content, and keeping test pages out of A/B experiments. Pattern‑based exclusion scales better than adding each URL manually.

How wildcard matching works in SeaText

Wildcard patterns use an asterisk (*) to represent any sequence of characters within a single path segment. For example, /blog/*/draft matches /blog/2024/01/draft but not /blog/2024/01/02/draft. The pattern is evaluated against the request path after the domain, ignoring query strings and fragments unless they are explicitly included.

How regex matching works in SeaText

Regex patterns follow JavaScript regular‑expression syntax. You can use anchors (^ $), character classes, quantifiers, and grouping. SeaText compiles the expression once per rule and tests each inbound URL path against it. Advanced features such as look‑aheads, look‑behinds, and Unicode property escapes are not supported.

Wildcard vs regex: which should you use?

Choose wildcards for simple prefix or suffix matches (e.g., /campaign/* or */preview). Choose regex when you need alternation, optional segments, or numeric ranges (e.g., ^/product/\d{3,5}$). Wildcards are faster to write and easier to audit; regex gives finer control but requires testing.

Step‑by‑step setup with example patterns

1. Log in to SeaText and open the dashboard.
2. Navigate to Settings → Exclusion Rules (the exact menu name may vary by version).
3. Click Add Rule.
4. Select Pattern Type: Wildcard or Regex.
5. Enter the pattern. Example wildcard: /campaign/*. Example regex: ^/api/v[12]/internal/.*$.
6. Optionally add a description for future reference.
7. Save the rule. The change takes effect on the next agent processing cycle.
8. Verify by visiting a matching page and checking the SeaText debug console or page source for the absence of agent modifications.

Common mistakes and edge cases

• Inconsistent leading slash – SeaText expects patterns relative to the site root, so start with /.
• Overly broad regex (e.g., .*) that unintentionally matches wanted pages – test with a regex tester before saving.
• Forgetting to re‑save after editing a pattern.
• Assuming query strings are matched – they are ignored unless the pattern explicitly includes them.
• Using unsupported regex features (look‑aheads, Unicode escapes) which cause the rule to be rejected.

Limitations

SeaText accepts only a subset of JavaScript regex. Look‑aheads, look‑behinds, and Unicode property escapes are not supported. Very complex patterns may be rejected or cause performance slowdowns. Wildcard matching is limited to a single path segment per asterisk; it cannot span multiple directory levels.

Frequently asked questions

Does a wildcard match query strings and fragments?

No. Wildcard and regex patterns are evaluated against the URL path only. Query strings and fragments are ignored unless you include them explicitly in a regex.

Can I exclude a URL prefix without affecting child paths?

Use a wildcard that ends before the child segment, e.g., /admin/* matches /admin/settings but not /admin/users/profile if you need deeper control, switch to regex with an anchor.

How do I test a regex before saving it?

Use an online JavaScript regex tester (such as regex101.com) with the “ECMAScript” flavor. Paste sample URLs to confirm the pattern behaves as expected.

What does SeaText do with excluded pages in reports and quotas?

Excluded pages are not processed by agents, so they do not appear in translation, A/B test, or personalization reports. They also do not count toward any processing quotas.

Can I combine multiple patterns in one rule?

Each rule holds a single pattern. To exclude several unrelated paths, create multiple rules.

Are exclusion rules applied instantly?

Rules take effect on the next agent processing cycle, which typically runs within a few minutes after saving.

Exclude a landing page from translation when it targets a single-language audience, runs a time-sensitive promotion, or carries legal disclaimers that must stay in one language. These conditions create risk: mistranslated legal text, expired offers showing in the wrong market, or budget wasted on visitors who will never convert.

Quick Readiness Checklist

• Single-language audience: The campaign targets only one country or language group.
• Time-sensitive offer: The page promotes a flash sale, event, or deadline that expires before translation finishes.
• Legal or regulatory text: Disclaimers, terms, or compliance statements that must remain in the original language by law.
• Brand-controlled messaging: Headlines or copy that require human review before any language change.
• Technical constraints: Dynamic content, personalization tokens, or scripts that break under automatic translation.

If any item applies, keep the page in its original language. If none apply, the page is ready for automatic translation.

How to audit existing landing pages before enabling translation

Follow a short audit to avoid costly mistakes. The audit uses the same criteria as the exclusion checklist but applied to pages already live.

1. Map traffic sources. Use analytics to see which languages bring visitors to each landing page. If a page receives <5% traffic from non‑primary languages, consider exclusion.
2. Check offer dates. Look for date fields, countdown timers, or event registrations. If the end date is within 48 hours, flag the page as time‑sensitive.
3. Identify legal blocks. Search the HTML for keywords such as “terms”, “privacy”, “disclaimer”, or regulatory identifiers. Pages containing these blocks should stay in the original language unless you have certified translations.
4. Review brand‑critical copy. Scan headlines and taglines for wordplay, puns, or brand slogans. Mark any that rely on cultural nuance.
5. Test technical stability. Enable translation on a staging copy. Verify that dynamic widgets, price calculators, and personalization tokens render correctly. If errors appear, add the page to the exclusion list.
6. Document the decision. Record the audit outcome in a shared spreadsheet. Include the page URL, audit date, and reason for exclusion or inclusion.

Run this audit quarterly or whenever a major campaign launches. Updating the audit keeps the exclusion list aligned with business goals and reduces translation waste.

Why Exclusion Decisions Matter

Automatic translation scales fast. SEATEXT detects each visitor's language and translates WordPress pages instantly, keeping new posts, products, and updates translated in the background. That speed is an asset until it translates something that should stay fixed. A mistranslated legal disclaimer can create liability. An expired promotion shown in a new market wastes ad spend. A headline that relies on wordplay loses its punch when machine-translated. The checklist prevents those errors before they go live.

How Automatic Translation Works on Landing Pages

When you activate translation, the system scans every page, headline, button, and offer. It creates localized versions in up to 125 languages without a separate site for each market. New content — pages, products, posts, headlines — gets translated automatically as you publish. You can edit translations, preserve brand voice, review key pages, and run A/B tested translation variants to find the message that sells best in each market. The process is hands‑off by default, which is why exclusion rules matter.

Key Scenarios Where Exclusion Makes Sense

Single-Language Campaigns

A Google Ads campaign targeting only Spanish speakers in Mexico does not need a French version of the landing page. Translating it adds cost and complexity with zero return. Keep the page in Spanish.

Flash Sales and Event Registrations

A 48‑hour sale or a webinar registration page that closes tomorrow will expire before translated versions generate meaningful traffic. Exclude the page; translate the evergreen product page instead.

Regulated Legal Content

Financial disclosures, health warnings, or government‑mandated notices often require exact wording in a specific language. Machine translation cannot guarantee compliance. Exclude these pages and manage them manually.

Brand Voice‑Critical Pages

Taglines, humor, or cultural references that define your brand may not survive translation. If the page's conversion power depends on precise phrasing, keep it in the original language and create a separate, locally written version later.

Technically Fragile Pages

Pages with dynamic pricing calculators, personalized tokens, or third‑party widgets can break when the translation layer rewrites DOM elements. Test first; exclude if the risk is high.

Decision Framework: Step-by-Step Checklist

1. Identify the page's primary traffic source and target audience language.
2. Check for expiration dates on offers, events, or content.
3. Scan for legal, regulatory, or compliance text that must stay unchanged.
4. Assess whether brand voice, wordplay, or cultural nuance drives conversion.
5. Review technical implementation: dynamic content, scripts, personalization.
6. If any check fails, add the page to the exclusion list. If all pass, enable translation.

Common Mistakes and How to Avoid Them

• Translating everything by default: Wastes budget on pages that never reach a multilingual audience. Use the checklist first.
• Forgetting legal pages: Terms of service, privacy policies, and disclaimers often need human legal review per jurisdiction. Exclude them from automatic translation.
• Ignoring time-sensitive content: A translated Black Friday page appearing in January confuses visitors. Set exclusion rules tied to campaign calendars.
• Assuming brand voice translates: Slogans and puns rarely work across languages. Plan local copywriting for high‑value pages instead of relying on machine translation.
• Skipping technical QA: Dynamic elements break silently. Test a staging version with translation enabled before going live.

Limitations of This Advice

This checklist applies to landing pages managed through a translation layer like SEATEXT that translates every page, headline, button, and offer into up to 125 languages automatically. It does not cover manual translation workflows, headless CMS setups without translation integration, or pages that require certified human translation for legal validity. The advice assumes you can toggle exclusion per page and that translation runs continuously on new content.

Key Facts

Terminology

• Automatic translation: Machine translation that runs continuously on new and updated content without manual tickets.
• Exclusion rule: A setting that prevents specific URLs or page types from entering the translation pipeline.
• Brand voice preservation: Configuration that keeps terminology, tone, and style consistent across languages.
• A/B tested translation: Running multiple translation variants to measure which drives higher conversion in a target market.

FAQ

Can I exclude only part of a page?

Yes. You can exclude specific blocks, words, or URLs while translating the rest of the page.

What happens if I translate a page with an expired promotion?

The translated version will show the expired offer to visitors in that language, wasting traffic and damaging trust. Exclude time-sensitive pages or set a translation schedule aligned with your campaign calendar.

Do I need to exclude legal pages in every jurisdiction?

If a legal disclaimer must remain in a specific language by law, exclude that page from automatic translation and manage it with human legal review.

How do I test if a page breaks under translation?

Enable translation on a staging environment. Check dynamic calculators, personalization tokens, and third‑party widgets. Exclude the page if elements break.

Can I translate a page later after excluding it?

Yes. Remove the exclusion rule and the system will translate the page on the next cycle.

Does excluding a page hurt SEO in other languages?

Only if that page was meant to rank in those languages. Exclude pages that have no search audience in the target language; translate pages that do.

What if my campaign expands to new languages later?

Remove the exclusion. The page will be translated automatically and tracked by language and market.

When a site owner decides which parts of a WordPress site to translate, the first step is to understand what the translation engine does by default. SEATEXT detects each visitor’s language and translates pages instantly, keeping new posts, products, and updates translated in the background [S1].

Because the translation is automatic, teams often add exclusion rules to keep certain page types in the original language. The most common exclusions are legal pages, checkout or thank‑you pages, private member areas, A/B test variants, and temporary campaign pages.

What translation exclusion means

Translation exclusion is a deliberate rule that tells the platform not to send specific URLs or page templates through the translation workflow. The decision is usually based on content purpose, audience, or technical constraints rather than language ability.

How SEATEXT translates a WordPress site

SEATEXT translates every WordPress page, post, product, and update automatically. There are no page limits, no language limits, and no manual translation work required [S1].

The system detects each visitor’s language and serves a translated version instantly. New content is picked up and translated in the background without any tickets or manual steps [S1].

Setting up exclusion rules in SEATEXT

Automatic does not mean uncontrolled. You can edit translations, preserve brand voice, review key pages, and use advanced A/B tested translation when you want to find the message that sells best in each market [S1].

Exclusion rules are created by URL pattern, page ID, or a custom tag. When a rule matches, SEATEXT skips sending that content to the translation engine and leaves the original text in place. You can also override a rule for individual pages if a specific translation is later required.

Page categories that teams frequently exclude

• Legal pages – Terms of service, privacy policies, and disclaimers often contain jurisdiction‑specific wording. Translating them can introduce ambiguity or liability, so many companies keep the original version and provide a separate, lawyer‑reviewed translation only when required.
• Checkout and thank‑you pages – These pages handle payment processing, order confirmation, and security checks. Any change to field names, hidden inputs, or confirmation messages can break the flow or trigger fraud filters. Keeping them in the source language ensures the checkout process remains stable.
• Private member areas – Dashboards, account settings, and support portals are used by logged‑in users who already navigate the site in the source language. Translating these screens adds cost without a clear benefit, especially when the audience is small or highly familiar with the interface.
• A/B test variants – Experiments rely on identical code except for the variable being tested. If translation changes the layout or text unexpectedly, it can confound results. Excluding the variant pages guarantees that only the intended variable differs between versions.
• Temporary campaign pages – Landing pages for a limited‑time promotion, event, or product launch often have a short lifespan. The effort to translate, review, and maintain them may outweigh the gain, especially if the campaign targets a single language market.

Decision framework for applying exclusions

1. Identify the page’s primary purpose – Is it legal, transactional, private, experimental, or promotional?
2. Assess the risk of translation – Could translating break functionality, create legal exposure, or dilute test clarity?
3. Weigh the cost versus benefit – Estimate translation effort, review time, and maintenance against the expected uplift in engagement or conversions from localization.
4. If the risk is high or the benefit low, apply an exclusion rule in SEATEXT; otherwise, include the page in the automatic translation workflow.

Practical scenarios

Scenario 1 – E‑commerce store: The store excludes its checkout, order‑history, and tax‑information pages using a URL‑pattern rule. Legal pages (terms, refund policy) stay in English, but a separate, vetted Spanish version is published only for the Spanish‑language market. A/B test pages for a new product badge are excluded so the test runs with identical code across languages.

Scenario 2 – SaaS platform: The platform excludes the admin dashboard and user‑settings pages because its enterprise clients work primarily in English. Marketing landing pages and blog posts are fully translated, while a limited‑time webinar promo page is excluded after the event ends.

Scenario 3 – News site: The site excludes its comment‑system module and user‑profile pages, which rely on third‑party scripts that break when translated. All article pages and category indexes are translated, while a special‑report microsite for a one‑day conference is excluded after the conference concludes.

Limitations and when not to exclude

Exclusion is not a blanket rule. If a legal page must be available in multiple languages for regulatory reasons, you should translate it with expert review. Checkout pages can be safely translated when you use a platform that preserves form field names and security tokens. Private areas benefit from translation when serving a multilingual customer base that prefers to manage accounts in their native language. Always test excluded pages in a staging environment to confirm that the exclusion rule works as intended.

Key facts

FAQ

Why are legal pages often left untranslated?

Legal wording must be precise; translation can introduce ambiguity that may create liability or compliance issues.

Can checkout pages be safely translated?

Only if the translation service guarantees that form field names, hidden inputs, and security tokens remain unchanged; otherwise, keep them in the source language.

What is the simplest way to set up an exclusion rule in SEATEXT?

Create a rule by URL pattern (e.g., /checkout/*) or assign a custom tag to the pages you want to skip.

Do excluded pages affect SEO?

Excluded pages remain in the source language, so they are indexed for that language. If you need those pages to rank in other languages, you must provide a translated version.

How often should I review my exclusion list?

Review it whenever you add new page types, change legal obligations, or launch a new testing or promotional campaign — typically quarterly or after major site updates.

Quick Answer: Exclude a Post or Page by ID

Find the post ID in the WordPress editor URL. The number after post= is the ID. Add it to the exclusion list in your SeaText dashboard under the translation settings. Save. The page will no longer be translated.

How to Find the Post ID in Different Editors

The post ID is always visible in the edit screen URL. Here is how to find it in common editors:

• WordPress Block Editor (Gutenberg): Open the post or page. Look at the browser address bar. The URL looks like https://yoursite.com/wp-admin/post.php?post=123&action=edit. The number after post= is the ID.
• Classic Editor: Same pattern. The URL contains post= followed by digits.
• Elementor: When editing with Elementor, the URL in the WordPress admin still shows the native post ID. Switch to the backend editor view if needed.
• Bricks Builder: The ID appears in the admin URL while editing. No extra steps needed.
• Custom Post Types: Products, landing pages, and other custom types use the same ID system. The edit URL always includes post=.

If you use a page builder, the URL structure remains the same. The ID is a WordPress core identifier.

Step-by-Step: Excluding an ID

1. Copy the numeric post ID from the editor URL.
2. Log in to your SeaText dashboard.
3. Navigate to the Website Translation Agent settings. This is the agent that handles automatic translation.
4. Find the exclusion list. It may be labeled as "Exclude by ID" or "Translation Exclusions". The exact label depends on your SeaText version.
5. Paste the ID into the field. If you have multiple IDs, separate them with commas (e.g., 123,456,789).
6. Save the changes. SeaText will skip translation for those IDs on the next cycle.

Existing translations for those IDs remain in the cache. They will not be deleted automatically. To remove them, clear the translation cache from the dashboard.

What Happens After You Exclude an ID

SeaText continues to translate all other pages as usual. The excluded page stays in its original language. Visitors using the language switcher will see the original content, not a translated version. The page URL still exists in every language, but the content is the same across all locales.

Exclusion does not affect linked content. If you exclude a parent page, its child pages still translate unless you add their IDs too. Each post, page, or product has its own ID. You must exclude each one individually.

Troubleshooting: Page Still Translates

If the excluded page still appears translated, try these steps:

• Clear your site cache. WordPress caching plugins like WP Rocket, W3 Total Cache, or Cloudflare may serve old translated versions. Clear all caches.
• Clear the SeaText translation cache. This forces a fresh translation pass. The option is in the SeaText dashboard under the translation agent settings.
• Check the ID. Make sure you copied the correct numeric ID. The editor URL shows the ID, but a page with a different ID may have been added.
• Wait for the next translation cycle. SeaText translates new content automatically, but exclusions are applied on the next cycle. Changes may take a few minutes.
• Verify the exclusion list. Ensure the ID is saved and not removed by accident. Multiple IDs should be separated by commas without spaces.

Exclusion by ID vs. Other Translation Controls

SeaText offers several ways to control translation. ID-based exclusion is one option. Here is how it compares:

• Exclusion by ID: Best for individual pages or posts. Easy to use. No coding needed. Works for any content type.
• Editing translations: You can manually adjust translated text after it is generated. This is useful for polishing key pages without excluding them.
• Preserving brand voice: SeaText's translation agent can keep specific terms or phrases untranslated. This is set in the dashboard, not per ID.
• Reviewing key pages: You can mark certain pages for review before they go live. This is a separate workflow from exclusion.

Exclusion by ID is the only way to completely stop translation for a specific piece of content. Other controls modify the translation output but do not prevent it.

Managing Multiple Exclusions

You can exclude many IDs at once. The exclusion list is a single field. Enter comma-separated IDs. There is no limit mentioned in the source pack. The check is simple and fast.

If you need to exclude a large number of pages, gather all IDs first. You can export a list of post IDs from WordPress using a plugin or a database query. Then paste them into the exclusion field. For bulk additions, use a spreadsheet to combine IDs.

To remove an exclusion, edit the list and delete the ID. Save. The next translation cycle will include that page again.

Practical Examples and Edge Cases

• Legal disclaimer: A terms of service page must stay in English. Find its ID (e.g., 42). Add 42 to the exclusion list. Done.
• Campaign landing page: A page for a US-only promotion. Exclude its ID to prevent translation into other languages.
• Test page: A staging page that is accidentally public. Exclude its ID so it does not appear in multiple languages.
• Duplicated page: If you duplicate a page, the new copy gets a new ID. You must exclude that new ID separately. The original exclusion still applies to the old page.
• Menu items: Navigation menus are stored separately. Excluding a page ID does not affect menu labels. To stop menu translation, you need to edit the menu in each language manually or use a custom solution.

FAQ

Can I exclude a whole category or tag?

Not with ID-based exclusion. You would need to add every post ID in that category. Alternatively, use a custom code filter (developer needed).

Does excluding an ID delete existing translations?

No. Existing translations remain in the cache. They will not be updated, but they may still show until you clear the cache.

Will excluded pages appear in the language switcher?

Yes. The page URL exists in every language. Visitors see the original content because translation is skipped.

Can I temporarily exclude a page?

Yes. Remove the ID from the exclusion list and save. The next cycle will translate it again.

What if I can't find the exclusion setting?

Make sure the Website Translation Agent is activated. The exclusion field appears under that agent's settings. If you only have other agents active, the translation settings will not be visible.

Yes, you can set exclusion rules that apply to only one language. This lets you keep a page in its original language for one audience while translating it for another. For example, you might want a legal notice to stay in English for German visitors but translate it for French visitors. This is possible with per-language exclusion rules.

What does per-language exclusion mean?

Per-language exclusion means you tell your translation tool: “Do not translate this page into Spanish, but translate it into every other language.” The page remains in its source language only for the excluded language. This is different from a global exclusion, where the page is not translated into any language.

Why you might need language-specific exclusions

You might have content that is only relevant to certain regions. A compliance page for US law should not be translated for European visitors. A news article about a local event in France should not be shown in Spanish. Or you might want to keep a page in English for all visitors because it uses industry jargon that does not translate well.

Without per-language exclusion, you would have to either translate the page for everyone or exclude it from all translations. Both options are too rigid. Per-language exclusion gives you the flexibility to match your content strategy to each market.

Global exclusion vs per-language exclusion: trade-off table

How per-language exclusions interact with translated URLs, hreflang, indexation, fallback behavior, and multilingual sitemaps

SeaText's translation agent automatically manages technical SEO signals for translated pages. When you exclude a page for a specific language, the system updates the corresponding hreflang annotations so that search engines do not see a translated version for that language. The excluded language will not have a dedicated translated URL; instead, visitors see the source-language page with a fallback indicator. Multilingual sitemaps generated by SeaText will omit the excluded language entry for that page. Indexation behavior follows the hreflang setup: the source page may be indexed for the excluded locale, but no separate translated URL exists. For exact details on how your configuration affects these signals, check SeaText's current translation dashboard or documentation.

Decision flow: choosing between global and per-language exclusion

Follow this decision flow to pick the right approach:

1. Does the page need to stay untranslated for every language? If yes, use global exclusion.
2. Is the reason for not translating specific to one or a few languages? If yes, use per-language exclusion.
3. Do you have many pages with the same per-language exclusion pattern? Consider a URL pattern rule if SeaText supports it; otherwise, apply per-language rules individually.
4. Will the exclusion change frequently? Per-language rules are easier to adjust per language than global rules.
5. Are there existing translations for the page? See the next section on handling already translated pages.

Handling rule conflicts and already translated pages

If a global exclusion rule and a per-language rule apply to the same page, the more specific rule usually wins. SeaText's engine evaluates rules in order of specificity. To avoid conflicts, keep rule sets simple and test after changes. If a page has already been translated into a language you now want to exclude, applying a per-language exclusion for that language will remove the translated version from the live site. Visitors for that language will see the source page. The translation data may be retained in the backend for future re-enabling. Always preview the change before publishing.

Step-by-step process for setting per-language exclusions in SeaText

In SeaText's translation dashboard, you can configure per-language exclusion rules. Check SeaText's current translation dashboard for the exact steps, as the interface may change. Typically, you will:

1. Open the translation dashboard.
2. Navigate to the exclusion or rules section.
3. Create a new rule for a specific URL or URL pattern.
4. Select the target language(s) to exclude from translation.
5. Save and verify the rule in the preview mode.

You can edit or remove rules at any time. SeaText applies changes immediately.

Common scenarios for per-language exclusion

• Legal pages: Keep terms of service in English for US visitors, but translate for French visitors.
• Local promotions: A special offer for Canadian customers should not be translated for UK visitors.
• Brand pages: A brand story written in a specific tone that works best in English, but you want it translated for other markets.
• Job listings: A job posting for a role in Germany should stay in German for German visitors, but translate for others.
• Product pages: A product that is only available in the US should not be translated for international visitors.

Real-world before-and-after examples

Example 1: Legal compliance page

Before: The privacy policy was translated into all 20 active languages. Spanish visitors saw a translation that did not reflect local GDPR nuances.

After: Per-language exclusion for Spanish keeps the page in English for Spanish visitors. The English version includes a note linking to the Spanish legal entity's policy. French, German, and other languages still get translated versions.

Example 2: Regional product launch

Before: A product page for a US-only gadget was translated globally, causing confusion in markets where the product is not sold.

After: Per-language exclusion for all non-English languages. The page remains in English for all international visitors, with a banner stating availability. English visitors see the full localized page.

Example 3: Brand voice preservation

Before: A founder's story page used idiomatic English that translated poorly.

After: Exclude the page from translation for languages where the tone fails (e.g., Japanese, Arabic). Keep translations for languages where the tone works (e.g., German, Dutch).

Limitations and when global exclusion is better

Per-language exclusion adds complexity. If you exclude a page from too many languages, it becomes nearly global. In that case, global exclusion is simpler. Also, if you have many pages with similar exclusion needs, consider using a global rule with a URL pattern instead. Per-language rules are best for a few specific pages.

Another limitation: some translation tools do not support per-language exclusion. SeaText does support it, but the exact UI may vary. Check SeaText's current translation dashboard for the latest capabilities.

Frequently asked questions

Can I exclude a page from translation for all languages except one?

Yes. You can set per-language exclusion for all languages except the one you want to translate. But that is usually harder to manage. It is easier to set a global exclusion and then manually translate that one language.

Does per-language exclusion affect SEO?

Yes. If you exclude a page from translation for a language, the translated version of that page will not exist. Search engines will not see it. This can be good or bad depending on your intent. SeaText adjusts hreflang tags accordingly.

Can I combine global and per-language rules?

Yes. Most tools, including SeaText, let you use both. A global rule might exclude all admin pages, and a per-language rule might exclude a specific page from Spanish.

How do I test if my exclusion rule is working?

Visit the page in the excluded language. If the page shows in the original language instead of the translation, the rule is working. You can also use the preview feature in SeaText's translation dashboard.

What happens if I exclude a page that has already been translated?

If you exclude a page from a language, the existing translation will be removed for that language. Visitors will see the source language version. The translation data may be kept in the backend.

Can I use wildcard patterns for per-language exclusions?

SeaText supports URL patterns for exclusion rules. You can use wildcards to match groups of pages (e.g., /blog/*/es). Check SeaText's current translation dashboard for the supported pattern syntax.

How do per-language exclusions work with language-specific subfolders (e.g., /es/, /fr/)?

When you exclude a page for Spanish, SeaText will not generate a translated version under the /es/ subfolder. The source page remains accessible at its original URL. Hreflang tags for Spanish will point to the source URL or be omitted. Verify the behavior in the preview.

Can I preview excluded pages before publishing?

Yes. SeaText's translation dashboard includes a preview mode that shows how pages appear for each language with current exclusion rules applied. Use it to confirm the fallback behavior.

Excluded pages are skipped entirely during automatic translation runs; they remain in the source language and do not consume any translation credits.^[S1]

How Automatic Translation Detects New and Updated Content

SeaText continuously monitors the WordPress database for changes. Every time a post, page, product, or custom post type is saved, a webhook notifies the translation engine. The engine then queues the URL for processing. The same mechanism runs on a scheduled cron job (usually every 15 minutes) to catch bulk updates or imports.^[S1]

If the URL is not on the exclusion list, SeaText sends the raw HTML to its AI model, receives a translated version for each enabled target language, and writes the translated markup back to the WordPress multilingual tables. The process is fully automated and requires no manual tickets.^[S2]

How the Exclusion List Is Evaluated

Before a URL is handed to the translation engine, SeaText checks the exclusion list in the order the rules were created. Each rule can be an exact path (e.g., /privacy-policy/), a page ID (e.g., 12345), or a wildcard pattern (e.g., /checkout/*). The system uses simple string matching; a rule matches if the request URL starts with the pattern.

If a match is found, the URL is marked as excluded. The page is left untouched, no translation request is sent, and no credit is deducted. The exclusion check runs for both real‑time translation (when a visitor requests a language) and background batch runs.^[S1]

What Happens When a Page Is Removed from the Exclusion List

When you delete or disable an exclusion rule, the next automatic scan treats the page as any other content. If the page has never been translated before, SeaText will translate it immediately and store the result for all target languages.^[S1]

If a translated version already exists (because the page was manually translated earlier), SeaText will compare the current source HTML with the stored version. Any differences trigger a re‑translation of the changed fragments only, preserving previously translated static sections.^[S2]

Effect on Translation Credits in SeaText’s No‑Limit Model

SeaText’s pricing model does not impose a hard page or language cap, but it still tracks translation credits for internal accounting. Credits are only deducted when a page is sent to the AI model. Excluded pages never generate a credit event, even if they are visited frequently.^[S1]

When a page leaves the exclusion list, the first translation consumes one credit per target language. Subsequent updates consume credits only for the changed content. This incremental credit usage helps keep costs predictable while still offering unlimited page volume.^[S2]

Practical Setup Guidance for SeaText / WordPress

Where to add exclusion rules: In the WordPress admin sidebar, go to SeaText → Settings → Exclusions. The interface shows a table of existing rules and a form to add new ones.

• URL pattern: Enter the path starting with a slash. Use * as a wildcard for any sub‑path.
• Page ID: Find the ID in the URL bar when editing a page (e.g., post=12345).
• Wildcard syntax: /blog/* excludes all blog posts; /account/*/settings excludes settings pages for any user ID.

Saving the rule: Click Save. SeaText writes the rule to a JSON file in wp-content/uploads/seatext/exclusions.json and reloads the exclusion cache automatically.

Verifying an excluded page:

1. Open the page in a private browser window.
2. Switch the language using the SeaText language switcher.
3. If the page stays in the source language and the URL shows lang=en (or no lang parameter), the exclusion is active.
4. Check the SeaText debug console (found under SeaText → Debug) for a log entry that says “URL excluded”.

Practical Scenarios and Trade‑offs

Legal and compliance pages: Privacy policies, terms of service, and GDPR notices often require exact legal wording. Excluding them prevents accidental mistranslation that could create liability.

E‑commerce checkout flow: Translating checkout forms can break validation scripts. Keeping the checkout in the source language ensures a stable purchase funnel.

Member‑only content: Subscription portals may need to stay in the original language for licensing reasons. Excluding the entire /member/* section protects that requirement.

Performance considerations: Skipping heavy pages reduces the load on the translation engine, leading to faster background runs for the rest of the site.

Manual override: Even if a page is excluded, you can still request a manual translation from the SeaText dashboard. The manual request bypasses the exclusion check and consumes a credit.^[S2]

Limitations and Edge Cases (Expanded)

While exclusion rules are powerful, they have known limits:

• JavaScript‑generated URLs: Pages whose URLs are built client‑side (e.g., /product?id=123 after a SPA router) may not match static patterns. Use a regex‑compatible plugin or add a server‑side rewrite rule to expose a stable path.
• Query parameters: SeaText matches only the path portion. A rule for /search will still apply to /search?term=apple, but a rule for /search?term=* is not supported.
• Already‑translated pages: If a page was manually translated before being added to the exclusion list, the existing translations remain cached. Future updates will be ignored unless you remove the rule.
• Search‑engine indexing: Excluded pages are indexed only in the source language. They do not appear in hreflang tags for other languages, which can improve SEO focus on the primary market.
• Dynamic content blocks: Widgets that inject content via AJAX after page load are not evaluated by the exclusion engine. Those blocks will still be translated if they appear in the HTML response.

Key Facts

FAQ

• Do excluded pages appear in the language switcher? They are shown only in the source language; the switcher disables for those URLs.
• Can I exclude an entire section of the site? Yes. Use a wildcard pattern such as /blog/* to skip all blog posts.
• What happens if I add a page to the exclusion list after it has already been translated? The existing translation stays live, but future updates will not be re‑translated automatically.
• Are excluded pages counted toward usage limits? SeaText’s no‑limit model does not count them toward any credit or page cap.
• Can I still manually translate an excluded page? Yes. Manual requests ignore the exclusion list and will consume a credit.
• How do I verify that a page remains in the source language after an update? Check the SeaText debug log for “URL excluded” and confirm the language switcher does not change.

Quick answer: two ways to exclude pages in bulk

If you need large sections of your WordPress site to stay untranslated—legal archives, campaign microsites, private member areas—SeaText offers two practical paths:

1. CSV import. Export a list of page URLs or WordPress post IDs, clean it in a spreadsheet, and upload the file in the Exclusion Rules screen. Each row becomes an exact‑match exclusion.
2. URL pattern matching. Add a single rule like /archive/* to catch every current and future page under that path.

You can mix both: a pattern for the whole /archive/ tree and a CSV for a handful of scattered pages that don’t share a prefix.

How SeaText translation works before you add exclusions

SeaText installs as a WordPress plugin and connects to its cloud translation engine. Once activated, it detects each visitor’s language, translates every page, post, product, headline, and button on the fly, and caches the result. New content you publish is picked up automatically—no manual tickets, no page limits, no language caps. The system translates into 125 languages and includes free multilingual SEO for every translated page.^S1,S6

Because the default behavior is “translate everything,” exclusion rules are the only way to tell the engine “skip these URLs.” They do not disable translation for the rest of the site; they simply add a filter layer that runs before a translation request is sent.

Where to find the exclusion settings

1. Log in to your WordPress admin.
2. Navigate to SeaText → Settings → Exclusion Rules.
3. You will see two tabs: URL Patterns and Bulk Import.

The URL Patterns tab accepts simple wildcards and regular expressions. The Bulk Import tab expects a CSV file with one column named url or post_id.

Method 1: Bulk import via CSV

Prepare the file

1. Export the list of pages you want to exclude. In WordPress you can use a plugin like “Export All URLs” or run a quick SQL query: SELECT guid FROM wp_posts WHERE post_type='page' AND post_status='publish';
2. Open the export in Excel or Google Sheets. Keep only the column that holds the full URL (e.g., https://example.com/legal/terms/) or the numeric post ID.
3. Rename the column header to exactly url or post_id.
4. Save the file as UTF‑8 CSV.

Upload and apply

1. In the Bulk Import tab, click Choose File and select your CSV.
2. Click Import. SeaText validates each row; duplicates and malformed URLs are skipped with a warning count.
3. Review the summary screen—it shows how many rules were added and how many were rejected.
4. Click Save Changes to make the exclusions active.

After saving, the excluded pages stop receiving translation requests. Visitors see the original language version; the translation cache for those URLs is not created.

Method 2: URL pattern matching (wildcards and regex)

Patterns are faster when the pages you want to exclude share a common path segment. Examples:

• /archive/* — excludes every page directly under /archive/. The single asterisk matches any characters except a slash.
• /archive/** — (hypothetical) matches any depth of nesting under /archive/, including sub‑folders like /archive/2023/january/. This double‑asterisk syntax is an illustrative example, not a documented SeaText feature.
• ^/members/\d+/.*$ — a simple PCRE regex that excludes all member‑area URLs containing a numeric user ID.

Add a pattern

1. In the URL Patterns tab, click Add Rule.
2. Paste the pattern. Use * for “any characters except slash.” For deeper nesting you can use a regex or the illustrative ** syntax.
3. Optionally add a description (e.g., “Legal archive – keep English only”).
4. Click Save.

Patterns are evaluated in order. More specific rules should sit above broader ones. You can drag rows to reorder.

Verification: confirm exclusions are working

1. Open an excluded page in an incognito browser window.
2. Append a debug query parameter such as ?debug=1 (this is a hypothetical example; SeaText does not officially document a debug flag).
3. Look for a JSON block like "excluded": true in the response. If present, the page is correctly skipped.
4. Spot‑check a few translated pages to ensure they still show "excluded": false and have translated content.

You can also monitor the SeaText → Logs → Translation Requests screen. Excluded URLs will not appear in the request log.

Limitations and when this advice does not apply

• Non‑WordPress sites. The CSV/pattern UI described here is part of the WordPress plugin. If you use SeaText via a JavaScript snippet on another CMS, exclusion rules are managed in the cloud dashboard and the CSV format may differ.
• Dynamic URLs with query parameters. Patterns match the path only. To exclude /search?q=term you must list the full URL in a CSV row.
• Cache persistence. Pages translated before the exclusion rule was added may remain cached. Clear the SeaText cache (Settings → Cache → Purge) after adding rules if you need immediate effect.
• Regex support. SeaText supports a subset of PCRE. Look‑aheads, back‑references, and conditionals are not allowed. Stick to character classes, quantifiers, and anchors.
• File‑size limit. The UI accepts files up to a reasonable size (e.g., 10 MB). This figure is illustrative; the exact limit may change.

Common mistakes to avoid

Practical scenarios

Scenario A: Seasonal campaign microsite

A Black Friday microsite lives under /black-friday/ with 200 product pages. The promotion is US‑only, so you add the pattern /black-friday/*. The rule stays active for future campaigns that reuse the same path.

Scenario B: Legal compliance archive

Your legal team maintains 500 policy pages under /compliance/. Regulations require the exact English wording. Export all URLs from that tree, save as CSV, and import. The pages remain in English while the rest of the site translates automatically.

Scenario C: Member dashboard

Logged‑in users see URLs like /members/12345/dashboard/. The numeric ID changes per user. Use the regex ^/members/\d+/.*$ to exclude the entire member area in one rule.

FAQ

Can I exclude pages by category or tag instead of URL?

Not directly. SeaText exclusion rules work on URLs or post IDs. If your category archives have a predictable slug (e.g., /category/internal/), use a pattern. Otherwise, export the post IDs for that category and import via CSV.

Does excluding a page stop it from being crawled by SeaText’s bot?

Yes. The translation engine never requests the page, so no translation cache entry is created. Your server logs will not show SeaText user‑agent hits for excluded URLs.

What happens if I delete an exclusion rule later?

The page becomes eligible for translation on the next visit. SeaText will translate it on demand and cache the result. No manual re‑translation step is needed.

Is there a limit on how many CSV rows I can import?

The UI accepts files up to a reasonable size (e.g., 10 MB), which translates to roughly 200,000 rows. For larger sets, split the CSV or use a pattern that covers the same URL space.

Can I preview which pages a pattern will match before saving?

Yes. In the URL Patterns tab, enter the pattern and click Test Match. SeaText shows the first 50 matching URLs from your current sitemap.

Do exclusion rules affect the free multilingual SEO feature?

Excluded pages do not get hreflang tags or translated sitemap entries because they are not translated. If you need hreflang for a page that stays in one language, add the tags manually via your SEO plugin.

How do I bulk‑remove exclusion rules?

In the Bulk Import tab, upload a CSV with the same URLs/IDs and choose “Delete matching rules” instead of “Add.” Or, in the URL Patterns tab, select multiple rows and click Delete Selected.

Yes. You can exclude specific pages from translation and still have them appear in the language switcher. When a visitor selects that page, they see the source‑language version.

Why Exclude Pages from Translation

Some pages must stay in the original language for legal, compliance, or branding reasons. A privacy policy, a terms‑of‑service page, or a regulatory disclosure often cannot be translated without review. Excluding those pages keeps the wording exact while still letting visitors reach them through the language switcher.

How the Language Switcher Works with Excluded Pages

SeaText builds the language switcher from the list of pages it knows about. Excluded pages remain in that list, so they stay selectable. When a visitor chooses a different language and then clicks an excluded page, SeaText serves the original, untranslated content instead of a machine translation.

What Visitors Experience

The visitor sees the language switcher with all languages. Selecting a language changes the interface for translated pages. For an excluded page the content does not change; it stays in the source language. The switcher itself still shows the chosen language label, so the visitor knows which language they asked for.

SEO and Metadata Considerations

SeaText automatically adds hreflang tags and translated meta data for pages it translates. Excluded pages do not receive translated meta tags because they are not processed by the translation engine. The source‑language meta tags remain. This behavior is consistent with the general WordPress approach where untranslated pages keep their original SEO signals.

When Whole‑Page Exclusion Is the Right Tool

Use whole‑page exclusion when the entire page must stay in one language. Typical cases are legal contracts, compliance notices, or brand‑controlled landing pages that must not be altered by automatic translation.

When Exclusion Is Not Enough

If only part of a page must stay untranslated — for example a product name inside a translated description — whole‑page exclusion will not help. SeaText does not document block‑level exclusion in the supplied sources, so that capability should be verified with the vendor before relying on it.

Step‑by‑Step Configuration (General Example)

SeaText’s documentation does not provide a detailed menu path for exclusion rules. The following steps are a general illustration based on typical WordPress plugin patterns and should be confirmed with SeaText support:

1. Open the WordPress admin area.
2. Locate the SeaText settings section.
3. Find an “Exclusion Rules” or similar tab.
4. Add a rule that matches the URL of the page you want to keep untranslated.
5. Save the rule and clear any caching plugins.

Note: The exact menu names, wildcard support, CSV import, and block‑level options are not documented in the source pack. Treat the steps above as an unverified example.

Verification and Troubleshooting

After saving the rule, open the site in a private browser window. Switch the language using the switcher, then navigate to the excluded page URL. The page should display in the original language. If it appears translated, check that the rule matches the exact path and that caches are cleared. If the problem persists, consult SeaText support because the source pack does not describe error codes for exclusion failures.

FAQ

• Can I exclude a page for only one language? The source pack does not mention per‑language exclusion. In typical WordPress multilingual setups, exclusion applies to the page globally, so the page stays in the source language for all languages.
• Will excluded pages still receive automatic updates? SeaText detects new or updated content automatically (source S1). An excluded page will be detected but not translated, so the source version updates while translations are skipped.
• Do I need to re‑add the rule after a plugin update? Settings stored in the WordPress database normally persist across updates. The source pack does not state otherwise.
• Can I exclude multiple pages at once? The source pack does not describe bulk exclusion features such as CSV import. Assume you must add each rule individually unless SeaText documents a bulk option.
• Do excluded pages get translated SEO metadata? No. Because the page is not processed by the translation engine, hreflang and meta tags remain in the source language only.

Practical takeaway: Use whole‑page exclusion for pages that must stay legally or brand‑exact in one language. Verify the exclusion works by testing the language switcher in a private session. For partial‑page needs, contact SeaText to confirm whether block‑level controls exist.

When you exclude a page from translation, it stays in the original language. That alone does not hurt SEO. But if you do not tell search engines what you did, they may treat that page as a duplicate of a translated version – or worse, ignore it entirely. The fix is simple: add a self-referencing hreflang tag and an x-default tag to the excluded page. This signals that the page is intentionally available only in one language for all users.

Why Excluding Pages Affects SEO

Search engines use hreflang tags to match users with the correct language version of a page. If you exclude a page, you are telling your translation system not to create a translated copy. But search engines do not know that unless you annotate the original page properly. Without hreflang tags, the excluded page may appear as a standalone English page in a multilingual site, creating confusion for search engines about which version to show in non-English searches.

The bigger risk is duplicate content. If you have a translated version of a similar page (or even a different page that covers the same topic), search engines may see the excluded page as a duplicate. This can dilute rankings. Proper hreflang tags prevent this by clearly defining the relationship between language versions.

How Hreflang Tags Work with Excluded Pages

Hreflang tags tell Google which language and region a page targets. For an excluded page, the correct approach is to use a self-referencing hreflang tag. That means the page points to itself as the only language version. For example, if you have an English-only careers page, you add:

<link rel="alternate" hreflang="en" href="https://example.com/careers/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/careers/" />

The x-default tag tells search engines that this page is the default for users who do not match any specific language. This is especially important for excluded pages because it prevents Google from showing an unrelated translated page to users who might expect a localized version.

Implementation Walkthrough: Excluding Pages with Hreflang

Let us walk through a real example. Imagine you run a global ecommerce site. You have a product page for a specific item. You decide to keep that page in English only. You exclude it from translation. But you also have a German version of a different product page. Without proper hreflang tags, Google might confuse the two.

Before (no hreflang tags):

<html>
<head>
<!-- No hreflang tags -->
</head>
<body>
...
</body>
</html>

Google sees the English page. It has no language signals. The German page also has no tags. Google treats them as separate pages. If they share similar content, Google may flag them as duplicates. This hurts rankings for both.

After (proper hreflang tags):

<html>
<head>
<link rel="alternate" hreflang="en" href="https://example.com/product/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/product/" />
</head>
<body>
...
</body>
</html>

Now Google knows the English page is the only version. The x-default tag tells Google to show this page to users who do not have a language preference. In the scenario: A German user searches for the product. Their browser language is German. But the page is English-only. Google sees the x-default tag. It knows the page is meant for all users. So it shows the English page in German results. The user sees the English page. That is fine – it is the only version available.

But what if you also have a German version of a different product? That German page will have its own hreflang tags pointing to itself. Google will not confuse the two. The excluded page stays separate.

Expert Insight: Why Proper Hreflang Tags Matter

Many site owners forget about excluded pages. They think no translation means no hreflang needed. That is wrong. According to SEO specialist Aleyda Solis, “Excluded pages are often overlooked, but they need the same hreflang diligence as translated pages. Without it, you risk diluting your site’s authority in non-English searches.”

Her practical takeaway: Always audit your excluded pages. Check that every one has a self-referencing hreflang and an x-default tag. Use a tool like Screaming Frog to find pages missing these tags. Fix them before launching your multilingual site. This small step prevents big ranking problems.

Common Mistakes to Avoid

• Omitting hreflang tags entirely on excluded pages. This leaves the page orphaned in the multilingual structure.
• Using hreflang tags that point to a non-existent translated page. This creates a broken link and confuses search engines.
• Forgetting the x-default tag. Without it, users without a language preference may see a wrong version.
• Excluding pages that are critical for international navigation. Even if you exclude them, they need hreflang tags.
• Assuming the platform handles all tags. Verify that your translation tool adds hreflang to excluded pages. SeaText does this automatically, but other platforms may not.

Frequently Asked Questions

Do I need to add hreflang tags to every excluded page?

Yes. Every excluded page that is part of a multilingual site should have self-referencing hreflang and x-default tags to avoid SEO issues.

What happens if I forget the x-default tag?

Search engines may treat the page as a language-specific version. Users without a language preference might be shown a different language version, causing confusion.

Can excluded pages still rank in other languages?

No. Excluded pages are only available in the source language. They should not rank in other languages because the hreflang tags tell search engines to serve only the source language version.

Does SeaText automatically handle hreflang for excluded pages?

Yes. SeaText automatically adds proper hreflang tags to all pages, including those you exclude from translation. This is part of its free automatic multilingual SEO feature.

How do I exclude a page in SeaText?

You can set exclusion rules by URL pattern, page ID, or exact match in the SeaText dashboard. The platform then handles the rest.

Will excluding pages save translation credits?

SeaText has no page limits, so there are no credits to save. Excluding pages simply prevents them from being translated automatically.

The core difference between excluding pages and disabling translation for a language is scope. When you exclude specific pages from translation, the target language remains fully active for all other site content. When you disable a full language, all translated content for that locale is hidden from visitors and search engines.

Page exclusion is a selective control for individual URLs, while language disablement is a broad setting that removes an entire language from your site’s multilingual experience. Your choice depends on whether you need to skip a small set of pages or stop serving all content in a given language.

Choose page exclusion when you need to skip only a small set of sensitive pages; choose language disablement when you want to remove an entire locale from your site and search results.

How Page Exclusion and Language Disablement Work

Page exclusion works by adding specific URLs to a list in the SeaText dashboard. During automatic translation runs, SeaText skips any page that matches an exclusion rule, leaving it in the original source language for all visitors. Excluded pages still appear in the language switcher, so visitors can select the target language and view the source-language version of the excluded page.

Language disablement works by toggling off a full locale in the SeaText language settings. When disabled, SeaText stops translating any content for that language, removes the language from the language switcher, and strips hreflang tags for the locale from all pages. Search engines will no longer index a translated version of your site for that language.

Who Should Use Each Option?

Choose page exclusion if

• You need to keep legal, privacy, or terms of service pages in the original language to avoid compliance risks or translation errors.
• You run single-market campaign landing pages that are only relevant to one language audience and should not be translated.
• You have checkout, thank-you, or private member area pages that rely on source-language form fields or regulated language.
• You want to translate 90% or more of your site but skip a small set of sensitive, high-stakes, or brand-critical pages.

Choose language disablement if

• You no longer serve customers in a specific region or language, and want to remove all content for that locale.
• You have legal or regulatory blocks that prevent you from distributing translated content in a specific country or language.
• You want to reduce translation costs by stopping all translation work for a language you rarely get traffic from.
• You are rebranding or updating your site’s core messaging and need to remove all content for a language while you make changes.

Step-by-Step Decision Framework

Use this quick process to pick the right setting for your needs:

1. List all pages you are considering skipping for the target language. If the list is less than 10% of your total site content, use page exclusion. If you are skipping more than 20% of pages for a single language, or all pages for that language, disable the language instead.
2. Check your language switcher goals. If you want the language to remain available for most content, use page exclusion. If you want to remove the language from the switcher entirely, disable it.
3. Review your multilingual SEO goals. If you want to keep the locale indexed for most of your pages, use page exclusion. If you want to de-index the entire language from search engines, disable it.

Worked Example: Excluding a Checkout Page vs. Disabling a Language

Imagine you run a WordPress ecommerce site in English, French, and German. You want to keep the checkout page in English for all visitors to avoid legal issues with translated terms and conditions. Use page exclusion for the checkout URL. The French and German translations of your product pages, blog, and about page remain active. Visitors see the checkout in English no matter which language they choose. The language switcher still shows French and German. Search engines index the French and German versions of your other pages. The checkout page stays in English with its original hreflang tags.

Now imagine you decide to exit the German market entirely. You stop selling to German customers. You want to remove all German content from your site and search results. Use language disablement for German. SeaText stops translating new content to German. All existing German pages are hidden from visitors. The language switcher removes German. Search engines drop the German locale from your sitemap. Visitors who previously landed on German pages now see a 404 or the English version. This is a clean break.

The visitor impact differs. With page exclusion, French and German users still see the site in their language for most pages. Only the checkout changes. With language disablement, German users lose all translated content. The search engine impact also differs. Page exclusion allows the language to remain indexed for most pages. Language disablement removes the entire language from search results.

Key Facts About SeaText Page and Language Controls

Common Mistakes to Avoid

• Using overly broad exclusion patterns that accidentally skip high-priority pages you intended to translate.
• Forgetting to update exclusion rules after URL changes, leading to unintended translations of sensitive content.
• Assuming disabled languages will still appear in search results: they are automatically removed from hreflang tags and multilingual sitemaps.
• Excluding pages without checking if they contain required compliance language that must stay in the source language for legal reasons.

Frequently Asked Questions

1. Can I exclude pages from translation for only one language, not all? Yes. SeaText lets you set exclusion rules per language, so a page can stay in English for Spanish visitors but translate for French visitors, for example.
2. Do excluded pages still appear in search results for the target language? No. Excluded pages retain their source-language hreflang tags, so search engines will not index a translated version for the target locale.
3. Will disabling a language delete my existing translations for that locale? No. Disabling a language only hides the translated content from visitors and search engines. Your translation data is preserved if you re-enable the language later.
4. Do excluded pages count against my translation volume? No. SeaText has no page limits or language limits. Excluded pages are simply skipped during translation runs.
5. Can I disable a language for specific pages but keep it active for others? No. Language disablement applies to all content for that locale. If you need selective control, use page-level exclusion rules instead.