Migrating SeaText AI from Webflow Free Plan to Paid Site Plan: Complete Step-by-Step Guide
To migrate SeaText AI from a Webflow free plan to a paid Site plan, upgrade your Webflow site to unlock the Custom Code section, paste your SeaText JavaScript snippet, publish the site, then verify...
Moving SeaText AI from a Webflow free Starter plan to a paid Site plan is straightforward once you understand the single hard requirement: the free plan does not expose the Custom Code section in Site Settings, and SeaText's JavaScript snippet must live there. Upgrade the Site plan, add the snippet, publish, and confirm the connection in SeaText. The steps below walk through the entire migration, including the verification checks that prevent silent failures.
Why the free plan blocks SeaText
Webflow's Starter Site plan intentionally hides the Custom Code tab. SeaText AI works by injecting a small JavaScript file into every page so it can rewrite headlines, test variants, translate content, and track reading behavior. Without the Custom Code tab, there is nowhere to paste that snippet, so the AI remains inert. The SeaText integration documentation states this explicitly: "Accessing custom code in your Webflow site requires an active Site plan."
Prerequisites before you start
- A SeaText AI account with at least one project created.
- Admin access to the Webflow Dashboard for the target site.
- A credit card or billing method on file in Webflow to purchase the Site plan.
- The SeaText JavaScript snippet copied from your SeaText dashboard (labeled
SEATEXTCODEINTEGRATIONin the integration guide).
Step 1: Upgrade the Webflow Site plan
- Open the Webflow Dashboard and select the site you want to migrate.
- Click the three-dot menu → Settings → Plans. li>Choose a paid Site plan (Basic, CMS, Business, or Enterprise) that matches your traffic and CMS needs. The plan tier does not affect SeaText functionality; any active Site plan unlocks Custom Code.
- Complete the purchase. Webflow provisions the plan instantly.
Step 2: Add the SeaText snippet to Custom Code
- In the same Site Settings area, select the Custom Code tab (now visible because the plan is active).
- Paste the SeaText JavaScript snippet into the Head Code field. The integration guide shows the exact copy-paste flow: copy from SeaText, paste here, then publish.
- Click Save Changes.
Step 3: Publish the site
Click the blue Publish button at the top right of the Designer or the Publish button in the Custom Code modal. The snippet is now live on every page of the published domain.
Step 4: Activate the connection in SeaText
- Visit your live site in a browser. Stay on the page for at least 40 seconds. This triggers the initial handshake between the snippet and SeaText's edge network.
- Refresh the page a few times over the next five minutes.
- Open your SeaText dashboard. You should see your website name appear next to the SeaText logo at the top of the page. The integration guide notes this typically appears within five minutes; if it's missing after ten minutes, contact SeaText support.
Step 5: Enable AI agents and configure behavior
Once the site shows as connected, go to the Main AI Hub in SeaText. Activate the agents you need — Conversion Agent, Google Ads Agent, Translation Agent, Bot Refund Agent, etc. Then open Configuration to set parameters such as target languages, test intensity, and bot-detection sensitivity. The integration guide mentions an optional Variants Edit panel where you can review and tweak the first batch of automatic translations and copy variants before they go live.
Step 6: Verify auto-publish and tracking
- Auto-publish check: Make a small text change in SeaText's Variants Edit panel, save, then visit the live page. The change should appear without a Webflow re-publish.
- Reading telemetry check: Open the SeaText dashboard's analytics view. Scroll a test page for 30+ seconds. You should see dwell-time and scroll-depth events appear in real time.
- Bot-refund check (if enabled): Trigger a paid click from a test Google Ads campaign. Within the SeaText Bot Refund Agent, confirm the visit is logged and flagged correctly.
Common migration mistakes
| Mistake | Symptom | Fix |
|---|---|---|
| Pasting snippet into Project Settings instead of Site Settings | Snippet loads on staging but not production | Use the site-level Custom Code tab, not the workspace-level one. |
| Forgetting to publish after saving Custom Code | SeaText dashboard never shows "connected" | Always click the blue Publish button after saving. |
| Using a development domain (localhost, *.webflow.io) for the primary SeaText account | Connection times out or shows "invalid domain" | SeaText restricts localhost and dynamic dev domains. Use a real custom domain or a stable staging subdomain. |
| Creating one SeaText account for multiple domains | Only the first domain tracks correctly | Create a separate SeaText account per domain, as each account links to a single primary URL. |
Key facts at a glance
| Item | Detail | Source |
|---|---|---|
| Custom Code access | Requires active paid Site plan | S1 |
| Snippet placement | Head Code field in Site Settings → Custom Code | S1 |
| Activation trigger | Visit live site, stay 40+ seconds | S1 |
| Connection confirmation | Site name appears next to SeaText logo within 5–10 min | S1 |
| Multi-domain rule | One SeaText account per primary URL | S1 |
| Development domain restriction | localhost and dynamic dev domains blocked | S1 |
| AI activation location | Main AI Hub → Configuration | S1 |
| Variant editing | Variants Edit panel in SeaText dashboard | S1 |
Limitations and when this guide does not apply
- Workspace plan vs. Site plan: Upgrading the Workspace plan (Starter, Core, Growth) does not unlock Custom Code. You must upgrade the individual Site plan.
- Ecommerce sites: The same steps apply, but ensure you choose an Ecommerce Site plan if you need cart/checkout features.
- Client handoff: If you are an agency transferring the site to a client's Workspace, the Site plan transfers with the site, but the SeaText account stays with you unless you hand over credentials.
- Reverse proxy or Cloudflare Workers: If you rewrite HTML at the edge before it reaches the browser, the SeaText snippet may be stripped. Test in a clean browser session first.
Terminology quick reference
- Site plan: The per-site billing tier in Webflow (Starter, Basic, CMS, Business, Enterprise). Controls features like Custom Code, CMS items, form submissions, and bandwidth.
- Workspace plan: The team-level billing tier (Starter, Core, Growth, Enterprise). Controls number of sites, team seats, and code export.
- Custom Code tab: The section in Site Settings where global head/body scripts are injected into every published page.
- SeaText snippet: A small JavaScript file (served from SeaText's CDN) that bootstraps all AI agents on the page.
- Main AI Hub: The central control panel in SeaText where you toggle agents on/off and adjust global settings.
- Variants Edit: The SeaText UI for reviewing and manually overriding auto-generated copy variants and translations.
Frequently asked follow-up questions
Do I need to re-create my SeaText account after upgrading?
No. The same SeaText account works before and after the upgrade. The snippet is already tied to your account; it simply starts executing once the Custom Code tab is available and the snippet is published.
Can I test on a Webflow staging domain (*.webflow.io) before connecting a custom domain?
SeaText's documentation flags dynamic development domains as unreliable. A static *.webflow.io staging domain may work, but the safest path is to connect a real custom domain (even a subdomain like staging.yourdomain.com) before pasting the snippet.
What happens if I downgrade back to the free Starter plan later?
The Custom Code tab disappears again, so the SeaText snippet stops loading. Your SeaText account and historical data remain intact, but the AI goes inert until you upgrade again.
How long does the full migration take?
Plan upgrade: instant. Snippet paste + publish: 2 minutes. Connection handshake: up to 10 minutes. Agent configuration: 10–30 minutes depending on how many agents you enable. Budget 30–45 minutes end-to-end.
Will my existing A/B test data survive the migration?
Yes. SeaText stores test results and reading telemetry in its own database keyed to your account, not to the Webflow plan. The migration only changes where the snippet loads.
Can I run SeaText on a password-protected Webflow site?
Yes, as long as the snippet loads in the browser. Password protection happens at the Webflow CDN level before the page renders, so the snippet is still included. However, search bots and ad-platform validators cannot see the page, which limits SEO and Google Ads agents.
What if I manage multiple client sites in one Webflow Workspace?
Each site needs its own paid Site plan and its own SeaText account. The Workspace plan does not affect Custom Code access. Budget for one Site plan per site and one SeaText account per domain.
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 AI runs entirely from the JavaScript snippet you paste into Webflow's Custom Code tab. Once the paid Site plan unlocks that tab, the snippet activates a suite of autonomous agents — Conversion Agent for headline and CTA testing, Google Ads Agent for keyword-matched landing pages, Translation Agent for 125-language localization, Bot Refund Agent for recovering invalid-click spend, and more — without any further Webflow configuration. The dashboard gives you real-time reading telemetry, variant editing, and per-agent controls so you can tune behavior or pause individual agents without touching code again.