What Does the Integration Actually Cost?

The SeaText–Weebly integration itself costs nothing extra. You paste a JavaScript snippet into your Weebly site's footer code, and that's it. The only cost is your SeaText subscription, which starts at a monthly fee for access to SEO features.

Think of it like installing an app on your phone: the app is free, but you pay for the service it provides. SeaText provides the AI agents, and Weebly provides the hosting. Neither charges you for the connection between them.

This means the total cost of using SeaText on Weebly is exactly the price of your SeaText plan. There are no hidden fees, no per-installation charges, and no Weebly markup. The pricing page on SeaText's website shows current rates for each tier.

What Drives the Total Cost?

Your total cost depends on three factors: the SeaText plan you choose, the number of websites you connect, and any optional add-ons or agents you activate.

1. SeaText Subscription Plan

SeaText offers tiered pricing. The exact monthly fee depends on which plan fits your needs — from basic SEO features to enterprise-level AI agents. Check the pricing page for current rates.

Higher tiers unlock more of the 26+ autonomous AI agents. Basic plans may include core SEO tools. Enterprise plans include everything plus dedicated support and custom configurations.

2. Number of Websites

Each SeaText account is linked to a single primary URL. If you want SeaText on multiple Weebly sites, you need a separate account for each domain. That means multiple subscriptions, not one.

This is a key cost driver. A business with three Weebly sites pays three SeaText subscriptions. There is no multi-site discount mentioned in the source materials. Plan your budget accordingly.

3. Optional Agents and Features

SeaText offers 26+ autonomous AI agents, including the AI SEO Agent, Conversion Agent, Translation Agent, and Bot Refund Agent. Some may be included in your plan; others may require a higher tier or add-on purchase.

For example, the Google Ads Landing Page Agent rewrites your page for every ad keyword. The Website Translation Agent localizes your site into 125 languages. The Bot Refund Agent recovers up to 20% of ad spend lost to bot clicks. Each of these may be bundled or sold separately depending on your plan.

Trade-Offs: What You Get for Your Money

Choose a basic plan if you only need core SEO features on one Weebly site.
Choose a higher tier if you want multiple agents, translation, bot refunds, or enterprise-level support.

The trade-off is simple: you pay more for more automation. A basic plan gives you the essentials. A higher tier gives you the full suite of AI agents that can rewrite pages, translate content, recover ad spend, and influence what ChatGPT says about your brand.

Step-by-Step: What the Integration Involves

1. Create a SeaText account. You need one before you can install the script.
2. Copy the JavaScript code from your SeaText account page.
3. Log into Weebly and go to Website > Edit Site.
4. Select your project and click Edit.
5. Click Settings, then SEO.
6. Paste the JavaScript snippet into the Footer Code section.
7. Click Save, then Publish.
8. Visit your site several times and stay for at least 40 seconds to activate the AI.
9. Wait up to 5 minutes for your website name to appear next to the SeaText logo. If it doesn't show after 10 minutes, contact support.

That's the whole process. No developer needed, no extra fees.

The installation is secure. The AI remains inert until you activate it. This means your website content stays intact until you choose to turn on the agents.

What Changes If You Ignore the Integration?

If you skip the integration, you simply don't get SeaText's AI features on your Weebly site. Your site stays as-is. There's no penalty, no broken code, and no hidden charge.

But you also miss out on the potential benefits: AI-driven SEO content, real-time page rewrites for Google Ads keywords, translation into 125 languages, and bot click refunds. Those are the reasons people pay for SeaText in the first place.

Consider what you lose. Without the Google Ads Agent, every paid click lands on the same generic page. Without the Translation Agent, you only reach English-speaking visitors. Without the Bot Refund Agent, you pay for bot clicks that never convert. These are real revenue impacts, not just nice-to-have features.

Limitations and When This Advice Doesn't Apply

This cost breakdown applies to standard SeaText subscriptions. Enterprise deals may have custom pricing, volume discounts, or annual contracts that change the math.

Also, the integration only works on one domain per account. Development domains like localhost are restricted for security reasons. If you need a staging site, you'll need a separate account for it.

Dynamic development domains may not function properly. SeaText might be unable to reliably associate traffic with your account. Use a real, valid domain for testing.

If you're on a Weebly free plan, you can still integrate SeaText — but remember that Weebly's free tier includes Square branding and a 3% platform fee on sales. That's a Weebly cost, not a SeaText cost.

Your Weebly plan cost stays the same regardless of SeaText. Weebly doesn't charge extra for footer code. The only variable is your SeaText subscription.

Key Facts at a Glance

These facts cover the core cost structure. The integration is free. The subscription is the only recurring expense. The setup is simple enough for anyone to do.

Frequently Asked Questions

Is there a free trial for SeaText?

SeaText offers a free trial option. Check the pricing page for current trial terms.

Some pages mention a free 1-month pilot trial for the Google Ads Agent. This may vary by agent and plan. Always verify on the official pricing page.

Can I use SeaText on my Weebly site without paying?

No. You need a SeaText account, which requires a subscription. The integration itself is free, but the service isn't.

Do I need to pay Weebly extra for the integration?

No. Weebly doesn't charge for adding footer code. Your Weebly plan cost stays the same.

What if I have multiple Weebly sites?

You'll need a separate SeaText account for each domain. Each account is linked to one primary URL.

How long does it take for SeaText to start working?

After you publish the code, visit your site several times and stay for at least 40 seconds. Your website name should appear next to the SeaText logo within 5 minutes.

Can I integrate SeaText with a Weebly staging site?

Development URLs like localhost are restricted. Use a real, valid domain for testing.

What if the integration doesn't work?

Contact SeaText support immediately if your website name doesn't appear within 10 minutes. They can help troubleshoot the installation.

Which SeaText plan should I choose?

Start with the plan that covers your core needs. If you run Google Ads, the Ads Agent may pay for itself. If you sell internationally, the Translation Agent opens new markets. If bots waste your ad budget, the Bot Refund Agent recovers that spend.

Check with the vendor for current plan details and pricing.

What integration actually looks like today

SeaText’s public materials describe two integration paths: a website snippet that loads the agent runtime on any page, and an MCP endpoint that turns the site into a tool server for large-language-model clients. Neither path is documented as a plugin for GitBook, Confluence, Notion, or a generic CMS. There is also no public mention of CI/CD pipelines, GitHub Actions, or GitLab CI steps.

Immediate integration paths (snippet and MCP)

To start using SeaText, you add a small JavaScript code to your site header. This code loads the agent runtime and enables real-time text changes on your live site without touching your source files. The process takes under a minute and requires no server changes.

1. Create a SeaText account and log in.
2. Open the dashboard and copy the provided JavaScript tag.
3. Paste the tag into the <head> of every page you want the agents to optimize (or use your tag manager).
4. Save and publish. The dashboard reports “Active” once the snippet fires.

For AI tool access, SeaText provides an MCP endpoint. This turns your website into a tool server that Claude, ChatGPT, or custom agents can call. The endpoint returns live site data and allows agents to trigger SeaText actions.

1. In the dashboard, locate “AI Agent Actions (WebMCP)” or “Turn your website into an MCP server for Claude & ChatGPT.”
2. Enable the MCP endpoint. SeaText will expose a URL that MCP-compatible clients can call.
3. Configure your Claude, ChatGPT, or custom agent to use that endpoint. The agent can then read page content, trigger SeaText actions, and retrieve optimization data.

MCP is an open protocol; any client that speaks MCP can connect without a SeaText-specific plugin.

Platform-specific challenges for GitBook/Confluence/Notion/custom CMS

SeaText does not document native plugins for GitBook, Confluence, Notion, or custom CMS platforms. The snippet works on any rendered HTML, so if your CMS outputs public HTML pages, agents will optimize them. However, there is no documented way to push agent-generated changes back into your source documentation.

For GitBook: You can add the snippet to your published site, but there is no webhook or API to sync SeaText’s optimized headlines back into your GitBook space. Changes remain in SeaText’s edge layer.

For Confluence: The snippet can be added to Confluence-hosted pages if HTML embedding is allowed, but there is no plugin to read or write Confluence pages via SeaText. MCP exposes rendered HTML, not Confluence storage format.

For Notion: The snippet works on Notion’s public site if you enable public sharing, but there is no integration with Notion’s API or internal blocks. SeaText cannot read or write to private Notion databases.

For custom CMS: If your CMS renders HTML, the snippet will function. To integrate with your CMS’s data layer (e.g., to update source Markdown or JSON), you would need to build a custom middleware that calls SeaText’s undocumented API or uses webhooks — neither of which are publicly documented.

CI/CD and version control limitations and workarounds

SeaText does not provide public examples of CI/CD pipelines for agent configuration. Agent rules, translation glossaries, and A/B test variants are managed exclusively in the SeaText dashboard. There is no documented way to version-control these settings via GitHub, GitLab, or Bitbucket.

Workaround: Teams can export agent settings manually from the dashboard (if export functionality exists) and store them in a repository. However, SeaText’s public materials do not confirm an export feature or API for programmatic access to agent configurations.

To achieve version control, you would need to request the API reference from SeaText sales. Without it, you cannot automate agent configuration deployment through CI/CD pipelines.

Staging deployments: You can test agents on a staging subdomain by adding the snippet there. Activate agents, verify behavior, then promote the snippet to production. This is the only documented method for testing changes before live deployment.

MCP use cases for AI agents beyond basic reading

MCP enables AI agents to do more than read your site. They can trigger SeaText actions based on user queries. For example:

• An agent can ask SeaText to show the top-converting headline for a specific keyword and receive live optimization data.
• An agent can trigger a translation variant test for a specific language and locale.
• An agent can initiate a bot refund analysis for a recent ad campaign and return evidence to the user.

These actions require the agent to send structured requests to the MCP endpoint. Public docs do not specify the exact API payloads, but they imply that MCP supports both read and write operations on SeaText’s agent system.

Example hypothetical payload for triggering a headline test: {"action": "run_ab_test", "agent": "Google Ads Landing Page Agent", "variant": "keyword_match_v2", "duration_hours": 24}

This is illustrative only. To confirm actual payload structure and authentication, you must contact SeaText for the API reference.

Data flow limitations and edge-layer architecture implications

SeaText’s edge layer rewrites text on your live site in real time. This means changes happen between your origin server and the visitor’s browser. Your source documentation remains untouched.

Gain: Instant site optimization without deployments or code changes. Visitors see personalized content immediately.

Loss: No round-trip to your source docs. You cannot audit agent-driven changes in your GitBook, Confluence, or Notion workspace. There is no documented way to export optimized content back to your documentation system.

When to accept: For public-facing marketing sites where real-time personalization drives conversions and source control is less critical.

When to seek API access: For regulated documentation (e.g., medical, legal) where every change must be tracked, versioned, and approved in your source system.

Edge-layer implication: Since MCP exposes rendered HTML, not source files, AI agents interacting via MCP see only the final optimized output. They cannot access your original Markdown, Confluence storage format, or Notion blocks through SeaText.

Practical verification and testing procedures

To verify your SeaText integration is working correctly, follow these steps:

1. Open a page with the snippet and check the browser console for SeaText initialization logs. Look for messages like "SeaText agent runtime loaded" or "MCP endpoint active".
2. In the dashboard, confirm each activated agent shows “Active” and displays recent activity (keyword matches, bot detections, translations served, etc.).
3. For MCP, run a test query from your AI client (e.g., "Summarize the pricing page") and verify the response includes live site data.
4. To test agent behavior: Use the dashboard’s preview mode (if available) or add the snippet to a staging subdomain. Activate agents, then visit the staging page to observe real-time changes.
5. To audit changes: Since there is no documented export, you must manually copy optimized text from the live page and compare it to your source. For compliance, log these comparisons externally.
6. To roll back: Disable the agent in the dashboard. Changes stop immediately on new page loads. Previously served variants may persist in browser caches until they expire.

If you need to test agent-driven actions via MCP (e.g., triggering a translation test), you must construct a valid MCP request. Public docs do not provide sample payloads or authentication details. Contact SeaText sales for the API reference to confirm supported actions, required headers, and rate limits.

Trade-offs: instant optimization vs. source control

SeaText’s strength is speed: you get real-time personalization without touching your codebase. The trade-off is limited auditability and no native sync with documentation platforms.

Gain: Instant site optimization. Changes take effect in under a minute after snippet deployment. No development effort required.

Loss: No version control for agent rules. No round-trip to source docs. Limited auditability of AI-driven changes.

Accept these trade-offs when: Running public marketing campaigns where conversion speed outweighs the need for source-tracked edits. Using SeaText for temporary promotions or A/B tests where source sync is not required.

Seek API access when: Your documentation must comply with internal audit trails (e.g., ISO 27001, SOC 2). You need to version-control translation glossaries or agent configurations. Your team requires rollback capabilities tied to your Git repository.

Without public API or webhook documentation, you cannot confirm whether SeaText supports programmatic control. Always verify capabilities with sales before assuming API access exists.

Likely follow-up questions

How do I audit changes made by SeaText?

There is no documented audit log or export feature. To audit changes, you must manually compare live page content to your source documentation. For compliance, consider logging these comparisons in an external system.

Can I roll back an agent-driven change?

Yes. Disable the agent in the dashboard. New page loads will stop serving the agent’s output. Existing browser caches may retain the change until they expire.

What happens if I update my documentation source — will SeaText overwrite it?

No. SeaText only affects the rendered site via its edge layer. Your source documentation (GitBook, Confluence, Notion, etc.) remains unchanged unless you manually copy optimized text back into it.

Is there a sandbox to test agent behavior?

Yes. Add the snippet to a staging subdomain, activate agents, and verify behavior there before moving to production. This is the only documented testing method.

How do I verify MCP authentication?

Public docs do not specify the authentication method for the MCP endpoint. Assume it uses an API key or bearer token. To confirm, request the integration guide from SeaText sales.

What MCP actions are available beyond reading page content?

Public docs imply that MCP supports triggering SeaText actions (e.g., starting A/B tests, running translation variants), but they do not list exact actions or payloads. Contact sales for the API reference to confirm supported operations.

If you are translating a website to capture international revenue, the first question is not "which language" but "which words." Research and live testing consistently show that five component groups — headlines and value propositions, call-to-action copy, trust signals, checkout microcopy, and product-level CTAs — produce the overwhelming share of conversion gains. Everything else is maintenance.

The reason is simple: conversion happens at moments of commitment. A visitor decides to stay, click, trust, or buy based on a handful of high-stakes text blocks. If those blocks read like a machine translation, the visitor leaves. If they read like a local business wrote them, the visitor converts. The rest of the page — navigation labels, footer links, blog archives, legal disclaimers — supports the experience but does not trigger the decision.

Why translation impact is not evenly distributed

Most localization projects treat every word as equal. They export the entire site, run it through a translation memory, and re-import. The result is a site that is technically multilingual but commercially flat. Conversion-sensitive elements differ from informational elements in three ways:

• Decision proximity: They appear within seconds of a conversion action.
• Persuasion density: They pack value claims, risk reversal, and urgency into few words.
• Cultural nuance sensitivity: A phrase that sells in Texas may confuse or offend in Tokyo.

When you translate a privacy policy, accuracy is the only metric. When you translate a headline that carries 40% of a page's conversion weight, nuance, tone, and local idiom become revenue variables.

High-impact tier: headlines and value propositions

The headline is the first text a visitor reads. In eye-tracking studies it captures attention before images. A translated headline must do three things simultaneously: match the search intent that brought the visitor, communicate the core benefit in the local market's vocabulary, and fit the layout without breaking design.

Value propositions — the sub-headline or bullet cluster that explains "why us" — are equally sensitive. They often contain comparative claims ("faster than X," "half the price of Y") that require local market knowledge to land correctly. A literal translation of "twice as fast" may imply "rushed and low quality" in some cultures.

Test first: Run A/B tests on headline variants in the target language before translating the rest of the page. SeaText's AI CRO Reading Analysis measures millisecond-level reading behavior to identify which headline phrasing reduces friction and increases dwell time on the value proposition.

High-impact tier: CTA copy and microcopy

Call-to-action buttons — "Start free trial," "Get my quote," "Buy now" — are the closest text to revenue. Microcopy around the CTA ("No credit card required," "Cancel anytime," "Setup takes 2 minutes") reduces perceived risk. Both are short, high-leverage, and culturally coded.

In German, "Kostenlos testen" (test for free) outperforms "Jetzt starten" (start now) for SaaS trials. In Japanese, "詳細を見る" (see details) often beats "購入する" (purchase) for high-consideration products because it lowers commitment pressure. The only way to know is to test.

SeaText's Visitor Source Rewrites automatically match landing page headlines and CTAs to the referring campaign, so a visitor from a Google Ads search for "precio software contable" sees a Spanish CTA that mirrors that intent.

High-impact tier: trust signals and social proof

Trust badges, security seals, review snippets, client logos, and compliance notices (GDPR, SOC 2, local certifications) function as risk-reduction devices. Their conversion power comes from recognition, not translation. A translated "Trusted by 10,000+ companies" means nothing if the logos are all US brands unknown in the target market.

Localization here means substitution: replace US client logos with regional ones, swap Trustpilot for a local review platform, display the local data-protection badge. The text change is minimal; the credibility shift is massive.

High-impact tier: checkout and form microcopy

Error messages, field labels, progress indicators, and confirmation copy in the checkout flow are conversion-critical because they appear when purchase intent is highest and friction is most costly. A confusing "Postal code invalid" message in a format the user doesn't recognize causes immediate abandonment.

Form field order, required-field markers, and inline help text must follow local conventions. In Brazil, CPF/CNPJ fields replace SSN/EIN. In China, phone-number format and WeChat login options change the entire flow. These are not translation tasks — they are localization engineering tasks.

Medium-impact tier: product descriptions and feature lists

Product pages convert when specifications, benefits, and use cases answer the buyer's questions. Translation quality matters, but the conversion lift from polishing a feature list is smaller than from fixing a headline or CTA. Prioritize the top 20% of SKUs that drive 80% of revenue.

SeaText's Ecommerce Product Copy Agent optimizes product names, descriptions, and CTAs by generating variants and testing them against live traffic, so you invest translation effort where it pays back.

Lower-impact tier: navigation, footer, legal, and support content

Global navigation labels ("Products," "Pricing," "Resources") need to be clear but rarely decide a conversion. Footer links, privacy policies, terms of service, and help-center articles are necessary for compliance and completeness but have near-zero direct conversion impact. Translate them last, using cost-efficient machine translation with human review only for legal accuracy.

Decision framework: effort vs. conversion sensitivity matrix

Use the matrix below to sequence your translation work. Score each page component on two axes: translation effort (word count, technical complexity, cultural adaptation needed) and conversion sensitivity (how directly the text influences a conversion decision). Plot components and tackle high-sensitivity, low-effort items first.

Decision rule: If a component scores high on conversion sensitivity, invest in human transcreation and testing regardless of effort. If it scores low, use the cheapest accurate method. Never let volume dictate priority.

Key facts

Limitations and when this prioritization does not apply

• Regulated industries: In finance, healthcare, or government, legal and compliance pages may carry conversion weight because trust hinges on visible compliance. Treat them as high-sensitivity.
• Brand-first markets: Luxury or heritage brands may find that navigation tone and footer craftsmanship signal quality. Do not automate these.
• Single-page funnels: If your entire conversion happens on one long page, the distinction between tiers blurs — every section is close to the CTA.
• Right-to-left languages: Layout shifts for Arabic, Hebrew, or Persian can turn low-effort components into engineering projects. Factor layout cost into effort scores.

Terminology

• Transcreation: Rewriting copy in the target language to preserve emotional impact and persuasive function, not just meaning.
• Reading telemetry: Millisecond-level measurement of how visitors scan, dwell, re-read, and scroll — used to detect copy friction before a conversion event occurs.
• Multi-armed bandit optimization: A testing method that continuously shifts traffic toward winning variants instead of waiting for statistical significance on a fixed split.
• Visitor source rewrite: Dynamic adjustment of headlines and CTAs based on the referring campaign, channel, or keyword.

FAQ

How do I know which headlines are high-sensitivity without testing all of them?

Start with pages that receive paid traffic. The landing pages for your top campaigns are by definition high-sensitivity. Use reading telemetry (scroll depth, dwell time, re-reads) to identify which text blocks visitors engage with before converting or bouncing.

Can I use machine translation for CTAs if I add a human review step?

Only as a starting point. CTAs are too short for context to disambiguate. A human reviewer needs the full page context, the target market's buying vocabulary, and ideally a test variant to validate. Treat CTA translation as copywriting, not translation.

What if my CMS doesn't support per-component translation workflows?

Export the high-sensitivity components manually, translate and test them outside the CMS, then deploy winners via a JavaScript overlay or edge worker. SeaText's Translation Agent works with zero code changes and full control, so you can prioritize components without a CMS migration.

How many language variants should I test per high-sensitivity element?

Three to five. One control (current translation), one literal translation, one localized variant, one benefit-led variant, and one risk-reversal variant. Run until the bandit algorithm converges — typically weeks, not months.

Does SEO translation (hreflang, metadata, URLs) affect conversions directly?

Indirectly. SEO translation brings the right visitors. On-page translation converts them. Prioritize SEO elements for traffic acquisition, then apply this matrix for conversion optimization.

When should I translate the full site instead of prioritizing?

When you have brand-compliance requirements, legal mandates, or a market-entry commitment that demands a complete local experience. Even then, sequence the launch: high-sensitivity components go live first; the rest follows.

How do I measure whether a translated element actually lifted conversions?

Use split-URL or client-side A/B testing with conversion events tied to revenue, not just clicks. SeaText's AI Split URL Testing runs 0ms zero-flicker tests with dynamic traffic routing, so you measure real revenue impact per variant.

SeaText AI is a website optimization platform. You add its JavaScript code to a site, then it runs autonomous AI agents that rewrite copy, translate content, test variations, and watch for bot traffic. For multiple websites, the model is not one account that controls everything. SeaText links each account to a single primary URL, so you create one account for each website you want to use. Each site then runs independently, has its own installation, and has its own AI settings.

Practical answer: SeaText AI does for multiple websites what it does for one website — optimize conversions and content — but you repeat the setup per domain rather than managing them from one dashboard. That is the single most useful fact to know before you start.

What SeaText AI actually does

SeaText AI installs on a website through a JavaScript code snippet. After installation, the AI stays inert until you activate it. Once active, you use the Main AI Hub to turn on the agents and configure them. The platform's own materials describe 20 autonomous agents that work in real time, including CRO optimization, Google Ads landing page matching, website translation into 125 languages, product copy, AI SEO, A/B testing, personalization, website chat, and bot protection. The exact mix you use depends on the site's goals. For example, a local service site might use Local AI SEO, while an ecommerce brand might use product copy and translation agents.

How SeaText AI handles multiple websites

SeaText's integration guide is explicit: if you need to use SeaText on multiple domains, create separate accounts for each domain. The reason is that each account is linked to a single primary URL. That means:

• One website = one account.
• Two websites = two accounts.
• Development and production domains = two separate accounts as well.

The installation flow is the same per domain:

1. Create a SeaText account (or use an existing one for the first site).
2. Copy the JavaScript code from the General Integration page.
3. Add the code to every page of the site. The guide notes that WPEngine users should use the WP Engine plugin to add custom JavaScript.
4. Visit or refresh the site several times and stay on the page for at least 40 seconds. That activates the AI.
5. Wait at least five minutes until the website name appears next to the SeaText logo. If it doesn't appear after ten minutes, contact support.
6. Go to the Main AI Hub and activate the agents you need.
7. Fine-tune content in Variants Edit to review or edit translations and variants.

Key facts at a glance

Limitations and what they mean for you

• One primary URL per account. You cannot point one SeaText account at two different domains. If you try, only one URL is the recognized primary, and traffic from the other may not be associated with your account.
• Development URLs are restricted. localhost is blocked for security. Use a valid, real domain. Dynamic development domains may not work because SeaText may not reliably associate traffic.
• Activation isn't instant. You need to visit or refresh the page and stay for 40 seconds. Then wait for the site name to appear. If it doesn't after 10 minutes, you may need support.
• Separate accounts means separate reporting and configuration. There is no master switch for all sites in one view. You check each account independently.

Ignoring the account-per-domain rule is the most common setup mistake. It can look like the script is installed, but the account won't link to the second domain, and you lose time debugging.

Terms you'll meet in the SeaText setup

• Primary URL: the single website domain that a SeaText account is linked to.
• Agent: a specialized AI automation within SeaText, such as the CRO Optimizer or Google Ads Landing Page Agent.
• Main AI Hub: the area where you activate agents and configure their parameters.
• Variants: AI-generated versions of your page copy and translations. You can edit or review them in Variants Edit.
• CRO: conversion rate optimization, or improving how many visitors take a desired action.

A practical setup sequence for site two, three, and beyond

Once the first site is connected, adding another site is the same routine with a new account.

1. Create the second account and confirm its primary URL.
2. Get the JavaScript code from that account's General Integration page. The code is the same, but it must sit in the account tied to that domain.
3. Add the code to the second site and repeat the activation visit: refresh several times and stay for 40 seconds.
4. Wait for the domain name to appear in the dashboard, then activate the agents for that site.
5. Track and edit each site separately. Reports show results by page, keyword, and version within that account.

When separate accounts are the right choice

If you run multiple brands, client sites, or campaign-specific landing pages on different domains, use one SeaText account per domain. That is SeaText's intended structure. It gives each site its own AI settings, variant history, and connection status. If you only have one production domain, you need just one account. If you add a staging domain, create a second account for it, or keep the staging site outside SeaText unless you have a specific reason.

Frequently asked questions

Can I manage two websites from one SeaText account?

No. SeaText says each account is linked to a single primary URL. To use the tool on several websites, create one account for each website.

Do I need separate accounts for production and development?

Yes. The integration guide calls this out explicitly. Development and production are different domains, so they need separate accounts.

How do I activate the AI after adding the JavaScript?

Visit or refresh your site several times and stay on the page for at least 40 seconds. Then wait at least five minutes for the site name to appear next to the SeaText logo.

Why doesn't SeaText work on localhost?

Development URLs like localhost are restricted for security. SeaText also warns that dynamic development domains may not work because it may not be able to associate traffic with your account. Use a valid real domain.

Can I edit the AI versions SeaText creates?

Yes. Go to Variants Edit in the left panel, select the URL and language, then review, create, or edit translations and variants.

What should I do if the site name never appears?

Wait up to 10 minutes. If it still doesn't appear, contact SeaText support. The guide says this could indicate an installation issue on your platform.