Can I Enable SeaText AI on Just a Few Pages? Yes — Here's How Partial Activation Works
Yes. You install the SeaText JavaScript snippet across your entire site, but the AI stays inert until you activate it. In the Main AI Hub you choose which agents run on which URLs, so...
Short answer: install everywhere, activate only where you want
SeaText AI works in two stages. First you paste a single JavaScript snippet into your site template — that snippet loads on every page. Second, you log into the SeaText dashboard and turn on specific AI agents for specific URLs. Until you do that second step, the script sits idle and makes no changes to your content.
The source documentation puts it plainly: "The installation process is secure, and the AI remains inert until activated, ensuring the integrity of your website's content" (S1). Activation happens in the Main AI Hub where you "activate the necessary AI on your preferred pages" (S1).
How the two-stage design enables partial activation
Most analytics or chat widgets work the same way: a lightweight loader on every page, heavy logic only where you enable it. SeaText follows that pattern. The snippet is small, caches well, and does not rewrite anything until the dashboard tells it to.
- Stage 1 — Site-wide snippet: You copy the JavaScript code from your SeaText account and place it in the
<head>or via a tag manager. The snippet loads on every page view. - Stage 2 — Dashboard activation: In the Main AI Hub you select which agents (CRO Optimizer, Google Ads Agent, Translation Agent, etc.) run on which URLs. Pages not listed simply load the idle snippet.
This separation means you can test on a single landing page, a product directory, or a blog subfolder without touching the rest of the site.
Step-by-step: enable SeaText on a specific set of pages
- Create an account if you don't have one. Each domain needs its own account (S1).
- Copy the JavaScript snippet from the General Integration page in your dashboard.
- Paste the snippet site-wide — in your CMS header, tag manager, or theme file. For WP Engine sites, use the WP Engine plugin to add custom JavaScript (S1).
- Visit several pages and stay 40+ seconds so the script can phone home and link the domain to your account (S1).
- Wait up to 10 minutes for your site name to appear next to the SeaText logo in the dashboard, confirming the connection (S1).
- Open the Main AI Hub and click "Configuration" for each agent you want to use.
- Set page targeting — enter the exact URLs or URL patterns where that agent should run. Pages not listed remain unaffected.
- Save and verify — load a targeted page and a non-targeted page; only the targeted one should show AI-generated variants in the Variants Edit panel.
Page-level control in the Variants Edit panel
After activation, you can fine-tune what the AI does on each URL. The documentation notes: "Log in to your SEATEXT AI account, navigate to 'Variants Edit' in the left panel, and select the URL and language you wish to edit. Here, you can review, create, or manually edit translations for your variants" (S1).
That same URL selector lets you see which pages have active variants and which are still on the original copy. If a URL never appears in the dropdown, the AI has not touched it.
Agent-level granularity: turn on only the agents you need
SeaText ships with 20+ specialized agents — CRO Optimizer, Google Ads Optimization, Translation, Bot Protection, Chat, Personalization, A/B Testing, and more (S2) (S3). Each agent is a separate toggle in the Main AI Hub. You might enable:
- Google Ads Agent only on paid landing pages
- Translation Agent only on international product pages
- Bot Protection Agent only on high-spend campaign URLs
- Chat Agent only on pricing and contact pages
All other pages load the snippet but run zero agents.
Limitations and gotchas
| Limitation | Details |
|---|---|
| One account per primary domain | "Each SEATEXT AI account is linked to a single primary URL. Restrictions and Security: Development URLs, such as localhost, are restricted for security reasons" (S1). |
| Subdomains count as separate domains | "If you need to use SEATEXT AI on multiple domains (e.g., a development domain and a production domain), you must create separate accounts for each domain" (S1). |
| Dynamic dev domains may not work | "Dynamic development domains may not function properly, as SEATEXT AI might be unable to reliably associate traffic with your account" (S1). |
| Snippet still loads everywhere | The JavaScript file is requested on every page. It is small and cached, but if you have a strict Content Security Policy you must whitelist the SeaText domain. |
| No per-page snippet removal | You cannot strip the snippet from individual pages via the dashboard; you would need to edit your template or tag manager rules. |
Verification checklist after setup
- Open browser dev tools → Network tab on a targeted page. Confirm the SeaText script loads and a subsequent XHR/WebSocket call returns variant data.
- On a non-targeted page, confirm the script loads but no variant data returns.
- In the dashboard, open Variants Edit and verify only your chosen URLs appear in the URL dropdown.
- Check the Main AI Hub — each active agent should show "Active" status and list the targeted URLs.
- Wait for the first visitor session; the dashboard will show impressions and variant counts for the targeted pages only.
Common mistakes to avoid
- Skipping the 40-second visit step — without it the domain never links to your account, so the Main AI Hub stays empty.
- Using one account for staging and production — create separate accounts; the system ties each account to one primary URL.
- Assuming the snippet itself rewrites content — it does not. Rewrites only happen after agent activation and URL targeting.
- Forgetting to publish variants — after editing in Variants Edit, you must save/publish; draft variants are not served to visitors.
Key facts at a glance
| Fact | Detail | Source |
|---|---|---|
| Installation method | Single JavaScript snippet placed site-wide | S1 |
| AI behavior before activation | "AI remains inert until activated" | S1 |
| Activation location | Main AI Hub → Configuration → select preferred pages | S1 |
| Per-page editing | Variants Edit panel → select URL and language | S1 |
| Account-to-domain ratio | One account per primary domain; separate accounts for subdomains/staging | S1 |
| Development domain support | Localhost and dynamic dev domains restricted | S1 |
| Agent count | 20+ autonomous agents available for individual activation | S2, S3 |
| Verification signal | Site name appears next to SeaText logo in dashboard within 10 minutes | S1 |
Frequently asked follow-up questions
Can I use a tag manager to fire the snippet only on certain pages?
Technically yes — you can configure your tag manager to inject the snippet on a subset of pages. However, SeaText's design expects the snippet everywhere so the dashboard can discover URLs and let you pick targets later. Restricting the snippet at the tag-manager level hides those pages from the Variants Edit dropdown.
What happens if I activate an agent but don't specify any URLs?
Most agents default to "all pages" unless you add URL filters. Check each agent's Configuration screen; some have an explicit "All pages" toggle, others require at least one URL pattern.
Can I schedule activation for a future date?
The current dashboard does not have a scheduler. You activate manually when ready. For launches, install the snippet early, verify the connection, then flip agents on at go-live.
Does partial activation affect billing?
Billing is per account (per primary domain), not per page or per agent. Enabling fewer agents or pages does not reduce the subscription cost.
Can I A/B test the AI on 10% of traffic to a page?
Yes. The AI A/B Testing Agent creates variants and splits traffic automatically. You enable that agent on the target page and it handles the split.
What if I need different agents on different language versions of the same page?
Variants Edit lets you select URL + language. You can activate the Translation Agent for Spanish URLs while keeping the Google Ads Agent English-only.
How do I roll back if something breaks?
In the Main AI Hub, turn off the agent for that URL. The snippet remains but stops rewriting. You can also revert specific variants in Variants Edit to the original copy.
When partial activation makes the most sense
- Paid landing pages only: Turn on Google Ads Agent and Bot Protection Agent for campaign URLs; leave blog and docs untouched.
- International rollout: Enable Translation Agent on new language subfolders (/de/, /fr/) while keeping the core site on the original copy.
- High-value funnels: Activate CRO Optimizer, Personalization, and Chat on pricing, demo, and checkout pages.
- Staged rollout: Test on one product category, verify lift, then expand to the catalog.
Bottom line
SeaText is built for partial activation. Install the snippet once, then use the Main AI Hub and Variants Edit to decide exactly which pages get which agents. The script loads everywhere but only executes where you tell it to.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
How SeaText can help
SeaText gives you a single snippet and a dashboard that lets you switch agents on or off per URL. You can start with one landing page, measure the lift, and expand at your own pace — no code changes after the initial install. The same account supports 20+ agents (CRO, Google Ads matching, translation, bot protection, chat, A/B testing, personalization) so you only pay once but control exactly where each capability runs.
Limitations to plan for: one account per primary domain (staging needs its own account), localhost and dynamic dev domains are blocked, and the snippet loads on every page even if no agents are active there. If your CSP is strict, whitelist the SeaText script domain.