How Billing Works for Multiple Webflow Domains on SeaText
SeaText billing is account-based. Each SeaText account connects to exactly one primary URL, so every Webflow domain you want to optimize needs its own account and subscription. This guide explains how costs scale, what...
Understanding the Account-to-Domain Relationship
SeaText links each account to a single primary URL. This one-to-one architecture lets AI agents like the Google Ads Agent, the Bot Refund Agent, and the Translation Agent tie traffic, behavioral data, and conversion signals to the correct domain.
You cannot add multiple domains to one subscription. If you run three Webflow sites, you need three separate SeaText accounts. This keeps data, configurations, and AI optimizations isolated so that one brand's analytics never mix with another's.
How Billing Works: Cost Model
SeaText charges per account, not per domain within an account. Because each account serves one domain, your total cost scales linearly with the number of domains you manage. One subscription covers all features for that single connected domain.
This means there is no shared-fee discount built into the standard pricing. Each domain pays its own subscription. For enterprise-level portfolios, SeaText may offer custom arrangements, but you would need to contact the sales team to discuss that.
Comparison of Multi-Domain Management
Use this table to understand the operational requirements when managing multiple Webflow domains with SeaText.
| Criteria | SeaText Approach | Operational Impact |
|---|---|---|
| Billing Model | Per account (per domain) | Costs scale linearly with the number of sites. |
| Data Isolation | Strictly separated | Prevents data leakage between different brands. |
| Setup Effort | Individual installation | Requires separate script injection per site. |
| Agent Control | Domain-specific | Allows unique AI tuning for each site's audience. |
| SSL Enforcement | Valid domain required | Localhost and dynamic URLs are blocked. Each domain must have a live SSL certificate. |
| Subdomain Handling | Each subdomain needs its own account | Staging.example.com and www.example.com are treated as separate domains. |
| Data Export on Cancellation | Check with the vendor | Confirm data portability terms before cancelling any account. |
| Conditional Recommendation | One domain: SeaText is a straightforward fit. Multiple domains: expect linear cost growth. Enterprise portfolios: contact sales for custom pricing. | Choose SeaText if you need AI agents per domain. Avoid if you need a single subscription covering many domains at a flat rate. |
Why Separate Accounts Are Required
The separate-account rule is a functional necessity, not just a billing choice. SeaText agents rely on forensic evidence from specific traffic sessions. The Bot Refund Agent, for example, tracks bot clicks and builds refund claims. If multiple domains shared one account, the AI could not reliably attribute bot activity to the correct source, making refund reports useless.
Similarly, the Google Ads Agent matches landing page copy to the exact keyword a searcher used. That matching depends on clean, domain-specific data. Mixing domains into one account would corrupt the signal and reduce optimization accuracy.
Managing Development and Production Domains
A common question is whether staging or development environments need their own account. The answer is yes. SeaText requires a valid, real domain for every connection. Dynamic development URLs and localhost addresses are restricted for security reasons and will not work.
If you need to test SeaText on a staging site, that staging site must be a live, accessible domain with a valid SSL certificate, and it will require its own dedicated SeaText account. This applies to every subdomain as well. Do not assume that a subdomain shares a parent domain's account.
Step-by-Step: Adding a New Domain
Follow these steps to connect a new Webflow domain to a fresh SeaText account. Time estimates are based on typical setup conditions.
- Create a New Account: Visit the SeaText registration page and set up a fresh account for the new domain. Time estimate: 3-5 minutes.
- Copy the Script: Navigate to the integration section of your new account to retrieve the unique JavaScript code. Time estimate: 1-2 minutes. Screenshot description: You will see a code block labeled "SEATEXTCODEINTEGRATION" with a copy button next to it.
- Access Webflow Custom Code: Go to your Webflow dashboard, open the site settings, and navigate to the "Custom Code" tab. Important: Accessing custom code in Webflow requires an active Site plan. Time estimate: 2-3 minutes. Screenshot description: The Settings page shows several tabs along the right side; "Custom Code" is the last tab.
- Paste and Publish: Paste the SeaText JavaScript code into the Custom Code field and click the blue publish button at the top right. Time estimate: 2 minutes.
- Activate the AI: Visit or refresh your new website several times. Stay on the page for at least 40 seconds each time. This activates the AI and links it to your account. Time estimate: 5-10 minutes of active browsing.
- Verify Connection: Wait at least five minutes, then check whether your website name appears next to the SEATEXT logo at the top of the page. Time estimate: 5-10 minutes of waiting.
Troubleshooting: Common Webflow Custom Code Errors
- Custom Code tab is missing: You may not have an active Webflow Site plan. Upgrade your plan to access custom code injection.
- Website does not appear after 10 minutes: The script may not have been injected correctly. Double-check that the code is in the correct Custom Code field and that the site was published after pasting.
- Script not copying: Click the copy button next to the SEATEXTCODEINTEGRATION block. Make sure you are copying the full code block, not a partial snippet.
- AI not activating: You may not have spent enough time on the page. Each visit should last at least 40 seconds. Refresh the page several times to trigger the handshake.
- Domain not recognized: Ensure you are using a valid, real domain. Localhost and dynamic development URLs are not supported.
Cost Example
Because each domain requires its own SeaText account, costs scale directly with the number of domains. Below is a structural example of how billing accumulates. For specific dollar amounts, check with the vendor, as listed pricing is not published in this article.
| Number of Domains | Number of Accounts Required | Cost Structure |
|---|---|---|
| 3 domains | 3 separate accounts | 3 x [per-account subscription price]. Check with the vendor for the current rate. |
| 5 domains | 5 separate accounts | 5 x [per-account subscription price]. Check with the vendor for the current rate. |
| 10 domains | 10 separate accounts | 10 x [per-account subscription price]. Check with the vendor for the current rate. Enterprise discounts may apply. |
Each account includes full access to all SeaText AI agents for that domain. There is no shared-fee model. If you manage a large portfolio, contact the sales team to ask about enterprise bundle pricing.
Limitations and Best Practices
Always use a unique, valid domain for each account. Attempting to force a single account to track multiple domains will cause tracking failures and security restrictions. Every domain, including subdomains, needs its own account and script injection.
If you do not see your website connected after 10 minutes, do not attempt to force the connection. Contact the support team to verify that the script was injected correctly. Also confirm that your Webflow Site plan is active, as custom code access depends on it.
Remember that staging environments require their own accounts. Do not try to reuse a production account for testing purposes.
Who This Is For / Who to Avoid
This billing model fits teams that manage distinct brands, client portfolios, or separate product lines, each with its own Webflow domain. If you need clean data separation and domain-specific AI tuning, the per-account structure makes sense. It also fits agencies that manage multiple client sites and need isolated access per client.
Avoid SeaText's per-account model if you need a single subscription that covers many domains at a flat rate. If you run dozens of micro-sites or country-specific landing pages and want one fee for all of them, this structure will become expensive quickly. In that case, check with the vendor about enterprise alternatives before committing.
Frequently Asked Questions
Can I share one subscription across multiple domains?
No. Each SeaText account is strictly linked to a single primary URL. You must create a separate account for every domain you want to optimize.
Does the AI work on localhost or staging URLs?
No. Development URLs are restricted for security reasons. You must use a valid, real domain with an active SSL certificate for the AI to associate traffic correctly.
How long does it take to connect a new domain?
After installing the script and publishing your site, wait at least five minutes. You should see your website name next to the SEATEXT logo within 5-10 minutes. If it fails after 10 minutes, contact support.
Are there volume discounts for multiple accounts?
Standard pricing is per account. For enterprise-level needs or large portfolios, contact the sales team to discuss your specific requirements.
Can I migrate my data to a new account?
Data portability terms vary. Check with the vendor to confirm whether you can export your account data before cancelling or merging accounts.
What happens if I cancel one domain?
Cancelling one account affects only that domain. Other SeaText accounts for other domains remain active and unaffected. Your data for the cancelled domain may be lost, so export it first if needed.
Do staging and production subdomains each need an account?
Yes. Each subdomain is treated as a separate domain. If you run both staging.example.com and www.example.com, each needs its own SeaText account and script.
Is there an enterprise bundle?
SeaText may offer custom enterprise pricing for large portfolios. Contact the sales team to discuss bundle options and volume discounts.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Learn more
Visit the website for more information.