Seatext library

What domains should I add to SeaText for a complete Webflow development workflow?

To run a full Webflow development workflow with SeaText, you must add four domain types: your local development URL (via a public tunnel), the Webflow staging subdomain, each branch deployment URL, and your production...

SeaText ties each account to one primary URL. If you run local development, staging, branch deployments, and production on different URLs, you need a separate SeaText account for each. This isolation keeps AI experiments, translation variants, and bot‑refund tracking from bleeding across environments. Below is the complete domain checklist, why each matters, and how to configure them without errors.

Environment Domain Pattern SeaText Account Needed Key Setup Step
Local Development https://xxxx.ngrok.io or similar tunnel Yes, dedicated account Expose localhost via Ngrok/Cloudflare Tunnel, then add tunnel URL
Staging yoursite.webflow.io Yes, dedicated account Paste account‑specific JS in Webflow Settings → Custom Code
Branch Deployment branch-name-yoursite.webflow.io Yes, one per active branch Create account per branch URL, install script, verify activation
Production yourdomain.com Yes, dedicated account Install script, wait 5‑10 min for dashboard confirmation

Why Domain Isolation Matters

SeaText uses the primary URL to associate traffic, experiments, and AI agents with the correct configuration. When you reuse one account across multiple domains, the system cannot reliably attribute sessions. This leads to mixed A/B test data, broken translation mappings, and inaccurate bot‑refund evidence. The vendor documentation states that each SeaText AI account is linked to a single primary URL and that using one account on multiple domains is not supported.

Separate accounts also let you enable different agent sets per environment. You might run the Translation Agent on staging to verify localized copy, the Bot Refund Agent on production to recover ad spend, and the Google Ads Agent only on the live site. Isolation prevents a staging experiment from overwriting production variants.

Local Development: Getting a Public URL

SeaText blocks bare localhost or 127.0.0.1 addresses for security reasons. The platform requires a valid, public‑facing domain to verify origin and inject scripts. To test locally, expose your dev server through a tunneling service such as Ngrok, Cloudflare Tunnel, or VS Code Port Forwarding.

Typical flow: start Webflow CLI or your local stack on port 3000, run ngrok http 3000, copy the generated https://random.ngrok.io URL, create a new SeaText account for that URL, paste the provided JavaScript into your local layout, then visit the tunnel URL and stay 40 seconds to activate. The tunnel URL changes each session unless you pay for a reserved domain, so you may need to update the SeaText account when the tunnel restarts.

Staging Environment: The .webflow.io Subdomain

Webflow automatically provisions a staging subdomain (e.g., project-name.webflow.io) when you publish to staging. This is the canonical QA target before merging to production. Add this exact subdomain as a new SeaText account.

Installation steps match the vendor guide: copy the account‑specific JavaScript, open Webflow Dashboard → Site Settings → Custom Code (last tab on the right), paste into the Head or Footer field, click Publish. Wait at least five minutes for the site name to appear next to the SeaText logo in your dashboard. If it does not appear after ten minutes, contact support — this often signals a Content Security Policy block or script placement error.

Branch Deployments: One Account Per Branch URL

Webflow branch deployments generate unique URLs such as feature-checkout.project.webflow.io. Each active branch that you want to test with SeaText needs its own account. This granularity lets parallel teams run independent copy tests, translation checks, or personalization rules without collision.

Create the account using the branch URL, install the script in that branch’s Custom Code settings, publish the branch, then verify activation by visiting the branch URL for 40 seconds. When the branch is merged and deleted, you can retire the SeaText account or keep it for historical data.

Production Domain: The Revenue‑Critical Configuration

Your custom domain (e.g., www.yourbrand.com) is where SeaText delivers the most value: bot‑click refunds, real‑time keyword adaptation, conversion‑rate lift, and multilingual traffic. The production account should have the full agent suite enabled — Bot Refund Agent, Conversion Agent, Google Ads Agent, Translation Agent, and AI SEO Agent — depending on your plan.

After pasting the script and publishing, monitor the dashboard. The vendor notes that activation is not instant; the website name must appear in the dashboard header. If it is missing after ten minutes, open a support ticket. Common causes include CSP headers blocking inline scripts, the script placed in the wrong Custom Code field, or the Webflow Site plan being inactive (Custom Code requires an active Site plan).

Step‑by‑Step Implementation Checklist

  1. Inventory every URL: List local tunnel, staging subdomain, each active branch URL, and production domain.
  2. Create SeaText accounts: One per URL. Use a naming convention like brand-local, brand-staging, brand-branch-checkout, brand-prod.
  3. Install scripts: For each account, copy the unique JavaScript. In Webflow, go to Site Settings → Custom Code, paste into Head (recommended) or Footer, then Publish.
  4. Activate each environment: Visit the URL, stay at least 40 seconds. Refresh once. Check the SeaText dashboard — the site name should appear next to the logo within five minutes.
  5. Configure agents per environment: Open the AI Hub for each account. Enable only the agents you need for that stage (e.g., Translation on staging, Bot Refund + Google Ads on production).
  6. Set brand guardrails: In Configuration, define tone, forbidden terms, and variant limits so AI output stays on‑brand across all accounts.
  7. Document and hand off: Record account IDs, URLs, and active agents in a shared sheet for the team.

Common Pitfalls and How to Fix Them

  • Tunnel URL changes on restart: Use a paid Ngrok reserved domain or Cloudflare Tunnel with a stable hostname. Update the SeaText account if the URL must change.
  • Script not loading: Verify Webflow Site plan is active. Check browser console for CSP errors. Move script from Footer to Head if needed.
  • Dashboard shows “Not Connected” after 10 minutes: Contact SeaText support with the account ID and URL. Provide a screenshot of the Custom Code panel.
  • Branch deployment URL not recognized: Ensure the branch is published in Webflow. The URL must be reachable publicly; password‑protected branches block SeaText.
  • Dynamic query parameters in dev URLs: SeaText may struggle to associate traffic if the URL structure changes every session. Prefer stable tunnel hostnames.

Advanced Configuration Options

Once all accounts are active, you can tune each environment for its role:

  • Staging: Enable Translation Agent to preview 125‑language output. Use Variants Edit to manually approve copy before merging.
  • Branch: Turn on AI A/B Testing Agent to test headline variants against a control. Results stay isolated to that branch.
  • Production: Activate Bot Refund Agent to capture forensic evidence for Google/Meta refund claims (vendor reports 87% acceptance rate). Enable Google Ads Agent for real‑time keyword matching (+35% conversion lift claimed). Add Intent Amplifier to push verified buyer signals to Meta CAPI and Google Ads conversions API.
  • All environments: Set up Conversion Relay (CAPI) to forward 100% of real purchases to ad platforms, bypassing ad blockers and ITP.

Limitations and Technical Boundaries

SeaText cannot track highly ephemeral dynamic URLs that change structure on every session. If your Webflow setup uses session‑specific query strings for routing, traffic association will be unreliable. The vendor explicitly warns that dynamic development domains may not function properly.

Custom Code access in Webflow requires an active Site plan. Without it, you cannot paste the SeaText script. Localhost and bare IP addresses are blocked for security; a public tunnel is mandatory. Each account is billed separately, so budget for four or more seats if you run the full workflow.

Frequently Asked Questions

Can I use one SeaText account for staging and production?
No. The platform links one account to one primary URL. Mixing environments corrupts experiment data and bot‑refund evidence.
Do I need a paid Ngrok plan?
Only if you want a stable hostname. The free tier works but generates a new URL each restart, requiring you to update the SeaText account.
What if my branch deployment is password‑protected?
SeaText cannot activate on password‑gated URLs. Remove protection during testing or use a public staging branch.
How long until the AI starts rewriting copy?
After the site name appears in the dashboard (5‑10 minutes post‑install), enable agents in the AI Hub. Rewrites begin on the next visitor session.
Can I share one Translation Agent across accounts?
Each account manages its own translation memory and glossary. For consistent terminology, export/import glossaries manually or use the enterprise sync feature (check with vendor).
Does SeaText work on Webflow’s free staging plan?
Yes, as long as the .webflow.io subdomain is publicly accessible and you have Custom Code access (requires a Site plan on that staging site).

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.

Learn more