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 SEATEXTCODEINTEGRATION in the integration guide).

Step 1: Upgrade the Webflow Site plan

1. Open the Webflow Dashboard and select the site you want to migrate.
2. 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.
3. Complete the purchase. Webflow provisions the plan instantly.

Step 2: Add the SeaText snippet to Custom Code

1. In the same Site Settings area, select the Custom Code tab (now visible because the plan is active).
2. 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.
3. 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

1. 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.
2. Refresh the page a few times over the next five minutes.
3. 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

Key facts at a glance

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.

Installing SeaText on Squarespace requires accessing the Code Injection area under Developer Tools in your website settings. This is where you paste the JavaScript snippet that connects your site to the SeaText AI platform. The process takes about five minutes once you know the exact navigation path.

Prerequisites Before You Start

You need an active SeaText AI account before beginning the installation. Each SeaText account links to a single primary URL, so if you manage multiple domains — such as a development and production environment — you must create separate accounts for each. Development URLs like localhost are restricted for security reasons, and dynamic development domains may not function reliably because SeaText needs to associate traffic with your account consistently.

Have your SeaText JavaScript code snippet ready. You can copy it from your SeaText dashboard under the integration section. The script remains inert until activated, so your website content stays unchanged during installation.

Step-by-Step Navigation to Squarespace Settings

1. Log into your Squarespace dashboard and locate the website panel for the site you want to connect.
2. Click the three-dot icon (more options) on that website panel and select "Settings" from the dropdown menu.
3. Scroll to the very bottom of the Settings page to find the Developer Tools section.
4. Click "Code Injection" to open the designated area for inserting custom code snippets.

This path — Settings → Developer Tools → Code Injection — is consistent across all Squarespace plans that support code injection. The Developer Tools section always sits at the end of the Settings page, so scrolling down is the fastest way to find it.

Understanding Code Injection in Squarespace

Code Injection is Squarespace's built-in feature for adding custom scripts, meta tags, or tracking codes without modifying template files. It provides two main fields: Header and Footer. Code placed in the Header loads before the page content renders, which is required for SeaText to initialize properly and begin analyzing visitor behavior from the first millisecond.

The Header injection point ensures the SeaText script loads early enough to rewrite headlines, deploy translation layers, and start reading telemetry before visitors interact with the page. Footer injection would delay activation and reduce the accuracy of reading behavior analysis.

Installing the SeaText JavaScript Snippet

1. In the Code Injection panel, locate the Header field (labeled "Header" or "Header Code Injection").
2. Paste the complete JavaScript snippet from your SeaText account into this field.
3. Click "Save" at the top or bottom of the page to preserve your changes.
4. Ensure your website is published — unpublished or draft sites will not activate the script.

After saving, the script begins loading on every page of your site. The AI remains dormant until you complete the activation steps in your SeaText dashboard.

Verification and Activation Steps

1. Visit your live website and stay on the page for at least 40 seconds. This triggers the initial handshake between your site and SeaText.
2. Refresh the page a few times during this period to ensure the script loads consistently.
3. Return to your SeaText dashboard. Within 5 to 10 minutes, your website name should appear next to the SeaText logo at the top of the page, confirming the connection.
4. If the site name does not appear after 10 minutes, contact SeaText support — this indicates an installation issue that may require assistance.

Once connected, proceed to the Main AI Hub in your SeaText dashboard to activate the specific AI agents you need (translation, conversion optimization, SEO content, etc.) and adjust configuration parameters for each.

Common Issues and Troubleshooting

• Script not loading: Verify you pasted the code into the Header field, not Footer. Check for extra whitespace or missing characters in the snippet.
• Site not appearing in SeaText dashboard: Ensure the site is published, not in trial or private mode. Confirm you waited the full 10 minutes before contacting support.
• Multiple domains: Remember each domain needs its own SeaText account. Using one account across multiple domains will cause connection failures.
• Development environments: Localhost and dynamic staging URLs are blocked. Use a real, publicly accessible domain for testing.

Limitations and Restrictions

SeaText's Squarespace integration has several constraints you should know before starting:

• One account per primary URL: You cannot manage multiple websites from a single SeaText account. Each site requires a separate registration.
• No localhost or dynamic staging domains: Security restrictions prevent activation on localhost, 127.0.0.1, or automatically generated preview URLs.
• Code Injection plan requirement: Only Squarespace Business and Commerce plans (or legacy plans with the feature) support Code Injection. Personal plans do not include this capability.
• Script inertia until activation: The installed script does nothing until you activate AI agents in the SeaText dashboard. This protects your content integrity during setup.

Key Facts

Frequently Asked Questions

Why must I use the Header field instead of Footer?

The Header field loads the script before page content renders. SeaText needs this early load to analyze reading behavior from the first interaction, rewrite headlines in real time, and deploy translation layers without flicker. Footer loading would delay all these functions.

Can I install SeaText on a Squarespace Personal plan?

No. Code Injection — the feature required to paste the JavaScript snippet — is only available on Business and Commerce plans. Personal plans do not include Developer Tools access.

What happens if I paste the code but don't activate agents in the dashboard?

The script loads but remains inert. Your website content and performance are unaffected. No translations, rewrites, or tracking occur until you explicitly activate specific AI agents in the SeaText Main AI Hub.

How do I know the installation worked?

After visiting your live site for 40+ seconds and refreshing a few times, check your SeaText dashboard. Your website name should appear next to the SeaText logo within 5–10 minutes. If it doesn't appear after 10 minutes, contact support.

Can I use one SeaText account for a staging and production domain?

No. Each domain requires its own SeaText account. The system links one account to one primary URL for traffic attribution and security. Create a separate account for each environment.

Why are localhost and dynamic staging URLs blocked?

Security restrictions prevent SeaText from reliably associating traffic with your account on non-public, non-static domains. This protects against misuse and ensures accurate visitor attribution for billing and analytics.

What if I need to update the JavaScript snippet later?

Return to Settings → Developer Tools → Code Injection, replace the Header field content with the new snippet, and click Save. The updated script will load on the next page view. No re-activation is needed unless the account URL changes.

What optimizing product pages with AI agents actually means

When teams say they want to optimize product pages with AI agents, they usually mean handing off the repetitive work of writing, testing, and refining product copy to an autonomous system that learns from real visitor behavior. Instead of manually crafting a single description and hoping it converts, the agent generates multiple variants of product names, descriptions, bullet points, and calls to action, then runs continuous experiments that shift traffic toward the versions that produce more add-to-carts and purchases.

SeaText's Ecommerce Product Copy agent does exactly this: it makes controlled changes to product names and descriptions, compares variants with real visitor behavior, and keeps the wording that improves conversion. The system tracks results by page, keyword, and version so you can see which changes moved the needle.

Prerequisites before you deploy an AI optimization agent

1. Product catalog access. The agent needs a structured feed of your SKUs, current titles, descriptions, images, and prices. Most platforms export this as CSV, XML, or via API.
2. Traffic volume. Multi-armed bandit allocation works best when each product page receives at least a few hundred sessions per month. Very low-traffic SKUs may need to be grouped or tested via split-URL tests instead.
3. Brand guardrails. Define forbidden phrases, required compliance language, tone guidelines, and any legal constraints before the agent starts writing.
4. Conversion event tracking. Ensure add-to-cart, begin-checkout, and purchase events fire reliably in your analytics and ad platforms so the agent can optimize for the right signal.
5. Edge deployment capability. SeaText injects changes at the edge with zero flicker, so you need DNS or CDN control to route traffic through their network.

Step-by-step process to optimize product pages with SeaText's AI agents

1. Connect your catalog. Import your product feed into SeaText. The system maps each SKU to its current page URL and existing copy.
2. Set optimization goals. Choose primary metrics (add-to-cart rate, revenue per visitor, conversion rate) and secondary guardrails (minimum margin, brand compliance score).
3. Configure the Ecommerce Product Copy agent. Enable the agent for specific product categories or the full catalog. Define variant generation rules: how many headline variants, description lengths, CTA styles, and whether to test benefit-led vs feature-led angles.
4. Launch reading-telemetry analysis. Before writing variants, the AI CRO Reading Analysis agent scans session recordings and millisecond-level dwell data to pinpoint friction points — sections where visitors re-read, hesitate, or drop off.
5. Start multi-armed bandit testing. The agent deploys variants and automatically allocates 80%+ of traffic to top-performing copy within hours, not months. Losing variants are retired; winning variants become the new control for the next round.
6. Review and approve high-impact changes. For brand-sensitive pages, set a manual approval gate. For long-tail SKUs, allow full autonomy.
7. Scale winners across similar products. When a copy pattern wins in one category, the agent propagates the structure to related SKUs and re-tests.
8. Monitor the dashboard. Track results by page, keyword, and version. Export winning copy back to your PIM or CMS if you want a permanent record.

Key facts about SeaText's product-page optimization agents

Main options and trade-offs

Choose SeaText if you want continuous, autonomous optimization that learns from how real visitors read and act on your product pages, and you can route traffic through their edge network.

Choose a manual A/B tool if you have ample traffic, prefer to design every hypothesis yourself, and can wait months per test.

Choose a generic AI writer if you only need fresh copy drafts and have no traffic or testing infrastructure.

Invest in schema markup if your priority is visibility to external AI purchasing agents, not on-site conversion.

Practical scenarios

Scenario 1: Large catalog, thin team

An electronics retailer with 12,000 SKUs and one copywriter connects their feed, sets brand guardrails, and lets the agent run. Within two weeks, the agent has tested headline and description variants on the top 500 revenue SKUs, lifting add-to-cart rate by 18% on winning pages. The copywriter reviews only the top 20 strategic products.

Scenario 2: Seasonal product launches

A fashion brand launches a summer collection. They enable the agent two weeks before launch with "launch mode" guardrails (no price mentions, emphasis on newness). The agent tests urgency vs. aspiration angles in real time and locks in the winner before peak traffic hits.

Scenario 3: International expansion

A home-goods brand expands to Germany and Japan. They activate the Translation Agent alongside the Ecommerce Agent. The system translates and locally optimizes product copy in 125 languages, testing cultural nuances (e.g., German specificity vs. Japanese politeness markers) independently per market.

Limitations and when this advice does not apply

• Extremely low traffic. If a product page gets fewer than 200 sessions per month, bandit allocation lacks signal. Consider split-URL tests or grouping similar SKUs.
• Regulated industries with locked copy. Pharma, financial services, or medical devices where every word requires legal sign-off may need full manual approval for every variant, slowing the loop.
• No edge/CDN control. If you cannot route traffic through SeaText's edge network (e.g., locked-down enterprise CMS), zero-flicker injection won't work.
• Goal is external AI visibility, not on-site conversion. If you need your products to be recommended by ChatGPT, Perplexity, or Rufus, focus on structured data, knowledge-base publishing, and the ChatGPT Influence Agent — not on-site copy testing.
• Single-page funnels with no product catalog. Lead-gen pages, webinar registrations, or SaaS pricing pages are better served by the Conversion Agent or AI Personalization Agent.

Terminology quick reference

Multi-armed bandit

An algorithm that dynamically allocates more traffic to better-performing variants while still exploring others, reducing regret compared to fixed 50/50 splits.

Reading telemetry

Millisecond-level behavioral signals — dwell velocity, re-reading, scroll deceleration — that reveal friction before a conversion event occurs.

Edge injection

Rewriting HTML at the CDN layer before it reaches the browser, eliminating layout shift and flicker.

Guardrails

Brand, legal, and business rules that constrain what the AI can write (e.g., no price claims, required disclaimers).

FAQ

How much traffic do I need for the AI agent to work?

Aim for at least a few hundred sessions per month per product page you want to optimize. Lower-traffic SKUs can be grouped into category-level tests or tested via split-URL experiments.

Can I review every change before it goes live?

Yes. You can set an approval gate for any subset of pages — typically hero products, regulated categories, or brand-critical lines. Long-tail SKUs can run fully autonomous.

Does the agent change product images or prices?

No. The Ecommerce Product Copy agent optimizes text only: product names, descriptions, bullet points, and CTAs. Price and image tests require separate workflows.

How does this differ from using ChatGPT to rewrite descriptions?

ChatGPT produces static drafts. SeaText's agent generates variants, deploys them to live traffic, measures reading behavior and conversion, and automatically scales winners — creating a continuous improvement loop.

Will the agent mess up my SEO?

The agent preserves your canonical URLs, structured data, and core product attributes. It rewrites visible copy at the edge. You can exclude specific SEO-critical elements (e.g., schema markup, canonical tags) from rewrites.

What happens if a winning variant violates brand guidelines?

Guardrails prevent forbidden phrases from being generated. If a variant slips through, the approval gate catches it before deployment. You can also retroactively block a variant and the agent learns from the rejection.

Can I export winning copy back to my PIM or CMS?

Yes. The dashboard shows winning variants by SKU with performance data. You can export CSV or push via API to make changes permanent in your source of truth.

Quick Answer: Keep Each Site in Its Own Account

SeaText links each account to a single primary URL. If you manage three Squarespace sites, you need three SeaText accounts. This is the core rule for keeping content organized. Each account tracks traffic separately. This prevents cross-site confusion and activation failures. The reason is simple. SeaText associates each account with one domain. When traffic arrives, the AI matches it to the correct account. Multiple domains on one account breaks that match.

This matters for every Squarespace user managing more than one site. Whether you run a blog, a store, or a portfolio, each site needs its own SeaText account. The account-per-domain rule is not optional. It is the foundation of the entire setup process.

Step-by-Step: Set Up Separate Accounts for Each Site

Step 1: Create a SeaText account for each domain. Go to the SeaText signup page. Create one account per Squarespace site. Do not try to manage multiple domains from one account. Each account needs its own login and dashboard. Write down each account's email and password in a secure place. This saves time later when you need to check each dashboard.

Step 2: Install the SeaText code on each site. Log into each Squarespace dashboard. Click the three dots icon. Select Settings. Navigate to Developer Tools at the bottom of the page. Click Code Injection. Paste the JavaScript snippet from that site's SeaText account into the HEADER area. Save and publish. Repeat this for every site you manage. Make sure you use the correct JavaScript snippet for each account. Mixing up snippets can cause activation failures.

Step 3: Activate each site. Visit or refresh each website several times. Stay on the page for at least 40 seconds. This activates the AI and links it to your account. The 40-second window is important. Shorter visits may not trigger the activation signal. If you are testing on multiple browsers, repeat the visit in each one.

Step 4: Verify the connection. Wait at least five minutes. You should see the website name appear next to the SEATEXT logo at the top of the SeaText dashboard. If you don't see it after 10 minutes, contact support. Do not skip this step. Verification confirms the installation worked. It also confirms that SeaText can read traffic from your domain.

Why Separate Accounts Matter

SeaText accounts are tied to a single primary URL. If you try to use one account for multiple domains, the AI may not reliably associate traffic with your account. This can cause activation issues. It also makes it hard to track which content belongs to which site. Separate accounts solve this problem cleanly. Each site gets its own isolated environment. Data from one site does not bleed into another.

This matters for analytics. It matters for AI training. It matters for troubleshooting. When each site has its own account, you can review performance per site. You can see which site generates more AI interactions. You can isolate problems to a single site without affecting others.

Consider a real-world scenario. You run a blog on site A and a store on site B. Both use SeaText AI. If both sites share one account, the AI may mix signals. Blog visitors might trigger store recommendations. Store traffic might feed blog insights. Separate accounts keep each site's data clean. Each AI instance learns from its own traffic only. This leads to better results on both sites.

Another reason to keep accounts separate is support. When you contact SeaText support, they need to know which account and domain you are referring to. With separate accounts, support can quickly identify the issue. With shared accounts, they may need to investigate multiple domains. This slows down resolution time.

Common Mistakes to Avoid

• Using one account for multiple domains. This is the most common mistake. It can cause activation failures. It also makes content tracking nearly impossible.
• Forgetting to activate each site. After installing the code, you must visit the site and stay for at least 40 seconds. Otherwise, the AI won't link to your account.
• Not verifying the connection. Always check that the website name appears next to the SEATEXT logo. If it doesn't, the installation may have failed.
• Using development domains. URLs like localhost are restricted for security reasons. Use a valid, real domain for each site.
• Assuming dynamic development domains work. Dynamic development domains may not function properly. SeaText might be unable to reliably associate traffic with your account.
• Pasting the wrong JavaScript snippet. Each account has its own unique code. Using the wrong snippet means the site won't connect to the right account.

Verification: How to Know It's Working

After setting up each account, visit the SeaText dashboard. You should see the website name next to the SEATEXT logo at the top of the page. This confirms the site is connected. If you don't see it after 10 minutes, contact support immediately.

The verification step is critical. It confirms that the JavaScript code is firing correctly. It also confirms that SeaText can associate the domain with your account. Without verification, you might think everything works. But the AI could be silent. No data would flow. No insights would generate.

If verification fails, check these common issues. Did you paste the code in the HEADER area? Did you save and publish? Did you visit the site for at least 40 seconds? Did you wait the full 5 minutes? If all steps check out, contact SeaText support. They can check server-side logs to find the problem.

Key Facts at a Glance

Limitations and When This Advice Doesn't Apply

This approach works for standard Squarespace sites. If you use dynamic development domains, they may not function properly. SeaText might be unable to reliably associate traffic with your account. If you have a single domain with multiple subdomains, check with SeaText support about whether separate accounts are required for each subdomain.

The 40-second activation window assumes real user traffic. Automated pinging or scripted visits may not trigger activation. SeaText relies on genuine browser interaction to confirm the domain-account link.

This guide covers the Squarespace integration specifically. Other platforms may have different requirements. Always refer to the relevant SeaText integration guide for your platform. The steps above are specific to Squarespace. Other CMS platforms may use different installation paths.

FAQ

Can I use one SeaText account for multiple Squarespace sites?

No. Each SeaText account is linked to a single primary URL. You must create a separate account for each domain.

How long does it take to activate a site?

After installing the code, visit the site and stay for at least 40 seconds. Then wait at least 5 minutes for the site name to appear in the dashboard.

What if I don't see my site name after 10 minutes?

Contact SeaText support immediately. This could indicate an issue during installation.

Can I use localhost or a development domain?

No. Development URLs like localhost are restricted for security reasons. Use a valid, real domain.

What happens if I ignore the separate account rule?

The AI may not reliably associate traffic with your account. This leads to activation failures and difficulty tracking which content belongs to which site.

The short answer: SeaText does not give you a single dashboard for all your domains. Each domain gets its own account and its own dashboard. So organizing multiple domains really means creating a separate account for each domain and then keeping those accounts clearly labeled and easy to switch between. You can use custom tags or labels for each domain in your own workflow, and filter reports by domain simply by opening the correct account. The core rule from SeaText is one account per website.

Why per-domain accounts matter

SeaText ties every account to a single primary URL. This design keeps data isolated. If you ran two domains under one account, visitor metrics from site A would mix with site B. You could not tell which traffic belonged to which domain. Reports would be meaningless. The one-account-per-domain rule avoids this confusion. Each account sees only its own domain's data. No mixing. No guesswork. This is a deliberate choice by SeaText to ensure accurate reporting. As noted in the SeaText documentation, “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.”

What You Need Before You Start

Before you set up multiple domains, make sure you have:

• A SeaText account for each domain. Each account is linked to a single primary URL.
• A valid, real domain for each site. Localhost and dynamic development URLs are restricted.
• A password manager or a simple naming system to keep your logins separate and findable.

Step 1: Create One SeaText Account per Domain

SeaText's documentation is direct: “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.” Each SeaText account is tied to one primary URL. Without separate accounts, you risk mixing data and confusing which domain the traffic belongs to.

Create a fresh account for each website you manage. Use the domain name when you sign up so the account is easily identifiable later.

Create your domain-to-account inventory

Before you start creating accounts, map out every domain you manage. Include production, staging, and any subdomains you plan to use. For each domain, decide on a clear account name. A good pattern is domain-environment. For example:

• mysite.com → account name: mysite-production
• staging.mysite.com → account name: mysite-staging
• client-acme.com → account name: acme-production
• dev.client-acme.com → account name: acme-dev

Store these accounts in a password manager. Create a folder named “SeaText Accounts” or “Multi-Domain Logins”. Inside that folder, create subfolders for each client or project. For example:

• SeaText Accounts
  ├── My Sites
  │ ├── mysite-production
  │ └── mysite-staging
  └── Client Work
  ├── acme-production
  └── acme-dev

Set each password entry's title to the same account name you used. Add a note with the domain URL. This way you can find the right login in seconds.

Step 2: Name Your Accounts Clearly

Use a consistent naming scheme for your accounts. Add the domain or a short label in the username line or the account profile. For example:

• For mysite.com, use mysite-production or just mysite.com.
• For staging.mysite.com, use mysite-staging.
• For a client site, use client-acme-main and client-acme-staging.

Store these logins in a password manager. Name each entry exactly the way you will search for it later.

Step 3: Use Tags and Labels in Your Own System

Since SeaText's dashboard is per-account, tagging and grouping happen outside the platform. Use your password manager's folders, tags, or notes to group domains by project, client, or environment. Create folders such as “Production Domains” and “Staging Domains”, or add tags like “dev”, “prod”, “clientA”, and “clientB”. This is the custom labeling that keeps your workflow organized.

Step 4: Filter Reports by Domain

Inside each SeaText dashboard, you will see only that account's domain data. Use the reporting tools to set date ranges, look at specific pages, or focus on a campaign. There is no cross-domain report, but each account's data is automatically filtered to its own domain. If you need a particular metric, select the right account first and then apply any additional filters.

Step 5: Isolate Development and Production Domains

SeaText restricts certain development URLs. “Development URLs, such as localhost, are restricted for security reasons.” Dynamic development domains may also fail to function properly because SeaText might not reliably associate traffic with your account. For testing, use a valid, real domain. A subdomain like staging.yourdomain.com works well, but it still needs its own SeaText account. Keep development data separate from production data so you don't accidentally read test traffic as real results.

Step 6: Verify You're in the Correct Account

Before checking reports or making changes, confirm which account you are in. Look at the primary URL shown in the account settings or dashboard header. Also check the website in your browser's address bar. This simple verification prevents you from adjusting the wrong domain's page or misreading another site's metrics.

Common multi-domain mistakes

Many users make the same errors when managing multiple SeaText accounts. Avoid these three pitfalls:

Same-account installs on multiple domains. Some try to install the same SeaText script on two different domains. This breaks the one-account-per-domain rule. Metrics get mixed. You cannot trust the data. Always create a separate account for each domain and install the corresponding script.

Using localhost or dynamic development URLs. SeaText restricts localhost and other non-real domains. Dynamic development URLs may not function properly because SeaText might not reliably associate traffic with your account. Always use a valid, real domain even for staging or testing. A subdomain like staging.example.com works.

Failing to verify the active account before editing reports. When you have multiple accounts open in different tabs, it is easy to edit the wrong one. Always check the primary URL in the account settings before making changes. This prevents accidental edits to the wrong domain's data.

Step 7: Switch Quickly with Browser Profiles

If you manage many domains, use separate browser profiles or a multi-login extension to stay signed in to multiple SeaText accounts at the same time. For example, create a Chrome or Firefox profile for each client or environment. Name the profiles after the domain: “mysite-prod”, “mysite-staging”, “client-acme”. This lets you switch with a click instead of logging in and out repeatedly.

Key Facts: SeaText Multi-Domain Setup

Limitations and Workarounds

SeaText does not offer a single aggregate dashboard for multiple domains. You must log in to each account separately. If you need a unified view, consider using a third-party reporting tool that can pull from each SeaText account, or just keep a bookmarked folder of all your SeaText dashboards.

Another limitation is that localhost and dynamic development domains are not supported. The workaround is to use a real domain, even for staging, and to create a separate account for that staging domain. This keeps development data isolated and ensures the script works reliably.

FAQ

Can I see all my domains in one SeaText dashboard?

No. SeaText ties each account to one primary URL, so there is no combined view. You need to log in to each account separately.

How many SeaText accounts do I need?

One account per domain. If you have three domains, you need three accounts. If you have a production and a staging site, you need at least two.

Can I use a subdomain as a separate domain?

Yes. A subdomain like staging.example.com is a valid real domain and works well for testing, but it still needs its own SeaText account.

Is localhost supported?

No. Localhost and similar development URLs are restricted for security reasons.

What if I accidentally install the same SeaText account on two domains?

SeaText's rule is to create separate accounts for each domain. Sharing one account across domains may lead to data mixing and unreliable traffic association. Create a new account for the second domain and reinstall the script with the correct code.

How do I keep my logins organized?

Use a password manager and save each account under a clear name. Add tags or folders for environment, client, or project. This makes it easy to find the right dashboard in seconds.

Open your website's HTML file, locate the <head> or <body> section, and paste the SeaText snippet. Then save, publish, and visit the page for 40 seconds. This is the direct answer. The rest of this guide explains why the integration matters, how it works, and how to avoid common mistakes.

Why the SeaText integration matters

SeaText is not a simple tracking code. It is the gateway to a set of AI agents that change what visitors see on your site. The snippet links your page to your SeaText account. Once activated, the platform can rewrite content, adapt offers, and respond to visitor behavior.

The source materials describe four major benefits:

• Conversion-rate optimization. The CRO agent rewrites headlines, calls to action, and offers. It tests variations and keeps the ones that sell more. This is a core part of the SeaText system.
• Bot click recovery. The Bot Protection Agent detects suspicious paid traffic. It separates real buyers from bots and creates evidence you can submit to Google, Meta, TikTok, Reddit, or other ad platforms. The source mentions up to 20% back from Google bot clicks.
• 125-language translation. The Website Translation Agent translates pages, headlines, buttons, and offers into up to 125 languages. This lets international visitors read and buy in their own language.
• Keyword-matched landing pages. The Google Ads Agent rewrites your landing page in real time to match the keyword a visitor typed. One page can become a keyword-matched landing page for every paid click.

These benefits are only possible after the integration code is installed. That is why the paste step is the foundation of the system. The source materials say SeaText deploys 20 autonomous AI agents that work in real time.

How the integration works

The snippet is a small JavaScript code block. It sits on your page and remains inert until activation. This means it does nothing by itself. It only starts working after the right conditions are met.

Before installation, you need a SeaText AI account. The source says the installation process is secure. It also says the AI remains inert until activated, protecting your content's integrity.

Each SeaText account is linked to one primary URL. If you plan to use the platform on multiple domains, you must create separate accounts. For example, a development domain and a production domain each need their own account.

Activation is tied to visitor behavior. SeaText instructs you to visit or refresh your website several times and stay on the page for at least 40 seconds. This visit tells SeaText that the script is installed and links it to your account.

After the 40-second visit, wait about five minutes. Then look for the SeaText logo at the top of the page. Your website name should appear next to it. This confirms the connection is live. If the logo does not appear after 10 minutes, the source says to contact support immediately.

The exact snippet identifier is SEATEXTCODEINTEGRATION. Copy it from your SeaText dashboard. Paste it exactly as provided. Do not change, trim, or reformat the code.

Platform-specific instructions

Different platforms have different ways to add custom JavaScript. The underlying requirement is the same: place the snippet in a site-wide HTML area. Below are instructions for common setups.

Raw HTML files

If your site is built from static HTML files, use a text editor. Open the file that contains your page's structure. Find the closing </head> tag or the closing </body> tag.

1. Copy the SeaText snippet from your dashboard.
2. Open the HTML file in a text editor.
3. Paste the snippet just before </head> or just before </body>.
4. Save the file.
5. Upload it to your web host.

For most pages, the <head> section is the safer choice. It loads early. If you want the script to run after the page loads, use the </body> position.

WordPress

WordPress does not let you edit the header or footer files from the default editor. Use a custom code plugin instead. This plugin adds a site-wide code area without editing your theme files.

1. Log in to WordPress admin.
2. Install and activate a custom code plugin.
3. Open the plugin's custom code section.
4. Create a new code snippet.
5. Name it “SeaText Integration.”
6. Paste the SeaText JavaScript into the snippet area.
7. Set it to load on all pages.
8. Publish the snippet.

Do not paste the script only into a single post or page. The integration needs to be present on every page where you want AI agents to run.

WP Engine

WP Engine is a managed WordPress host. According to the SeaText general integration guide, WP Engine users should use the WP Engine plugin that enables custom JavaScript. This plugin lets you add code across all pages.

1. Download the WP Engine custom JavaScript plugin.
2. Install and activate it in WordPress.
3. Open the plugin settings.
4. Add a new JavaScript block.
5. Paste the SeaText snippet.
6. Apply the block across all pages.
7. Save your changes.

The source explicitly mentions this plugin. Use it to avoid conflicts with WP Engine's caching and security setup.

CMS custom-code areas

Many CMS platforms include a field for site-wide custom code. Common names are “Custom Code,” “Code Injection,” “Header Code,” or “Footer Code.” The exact location depends on your CMS.

1. Find the custom-code area in your CMS settings.
2. Choose the header or footer field.
3. Paste the SeaText snippet there.
4. Save the changes.
5. Preview your live site to confirm the page still loads correctly.

If your CMS has no custom-code area, you may need to edit the theme template. Contact your CMS provider or a developer if you are unsure.

Common mistakes to avoid

Many integration failures come from avoidable errors. Here are five specific mistakes and how to prevent them.

1. Pasting into an HTML comment

HTML comments begin with <!-- and end with -->. Text inside comments is hidden from the browser. If you paste the script inside a comment, it will not execute. Always paste the snippet outside of comment tags.

2. Missing the closing script tag

The SeaText snippet is a complete <script>...</script> block. If you accidentally delete </script>, the browser may not run the code. Copy the entire snippet and paste it without edits.

3. Using localhost or dynamic development domains

Development URLs like localhost are restricted for security reasons. Dynamic development domains may also fail because SeaText cannot reliably associate traffic with your account. Use a valid, real domain when installing the integration.

4. Putting the script in the wrong section

The snippet should sit near the end of <head> or before </body>. Do not nest it inside a <div>, <p>, or other content element. This can cause parsing errors.

5. Skipping the 40-second activation visit

The script stays inert until a visitor stays on the page for at least 40 seconds. If you skip this step, the connection may never activate. After publishing the code, visit your live site and remain on it for the full 40 seconds. Then wait the recommended five-minute window.

Verification

After installing the code, verify that SeaText has activated. Use this step-by-step flow:

1. Clear your browser cache.
2. Go to your live website.
3. Stay on the page for at least 40 seconds.
4. Wait 5–10 minutes.
5. Look at the top of the page for the SeaText logo.
6. Check that your website name appears next to the logo.

If the logo appears, the integration is active. You can now move to the SeaText dashboard and choose which AI agents to enable.

If the logo does not appear after 10 minutes, contact SeaText support. The source says this could indicate an installation issue. Support may need to help you identify the problem.

FAQ

Can I use one SeaText account for multiple domains?

No. Each SeaText account is linked to a single primary URL. If you need the integration on a development domain and a production domain, create separate accounts for each.

Is localhost allowed for testing?

No. Development URLs such as localhost are restricted for security reasons. Dynamic development domains may not work because SeaText cannot reliably associate traffic with your account. Use a real domain.

Can I remove the SeaText code later?

Yes. Delete the snippet from your HTML or from your CMS custom-code area. The AI agents will stop running on that page. For account-level changes, check with SeaText support.

Will the code slow down my website?

The snippet is small and inert until activated. It should not slow your page before activation. After activation, the AI agents work in the background. Test your page speed after setup to see the impact on your site.

What does the SeaText logo mean?

The logo at the top of the page, with your website name, confirms that the script is active. It means SeaText has linked the page to your account. From there you can enable AI agents.

What you need before you start

Before you begin, make sure you have:

• A SEATEXT AI account. You can create one on the SEATEXT website.
• Access to your Odoo admin panel with permission to edit the website.
• The JavaScript code snippet from your SEATEXT AI dashboard. This is found in the "SEATEXT CODE INTEGRATION" section of your account.

The installation process is secure, and the AI remains inert until you activate it. That means pasting the snippet alone won't change your site content.

Why SEATEXT AI matters for Odoo websites

SEATEXT AI rewrites your page text in real time to match each visitor's search intent. When someone clicks a Google ad for "red running shoes", the landing page headline and product blocks adapt to that phrase. This relevance lifts conversion rates. SEATEXT also translates pages into 125 languages automatically and detects bot traffic to protect ad spend. The snippet is the bridge that lets these agents run on your Odoo site.

Step-by-step: Paste the SEATEXT code snippet in Odoo

Follow these steps exactly:

1. Log in to your Odoo account and open the Website module from the dashboard.
2. Navigate to the page you want to edit and click the Edit button to open the editing panel.
3. In the editing panel, scroll through the Blocks panel until you reach the Dynamic Content section.
4. Locate the Embed Code module and drag it to the desired location on your page.
5. Once the module is placed, click the Edit button in the right panel.
6. In the pop-up window, paste the SEATEXT code snippet into the designated area.
7. Click Save to apply the changes.
8. In the Visibility section, select Hide on Desktop to keep the block from showing on desktop devices.
9. Click Save again to finalize.

That's it. The snippet is now installed on your Odoo page.

Why the "Hide on Desktop" step matters

The SEATEXT code snippet is a JavaScript snippet that runs in the background. It doesn't need to be visible on the page. If you leave the block visible, it may appear as an empty box or a code block on your website, which looks unprofessional and can confuse visitors.

By selecting Hide on Desktop, you ensure the block is invisible on desktop devices. This is the recommended setting because SEATEXT AI works by rewriting content in real time, not by displaying a widget. The block is just a container for the script.

Common mistakes and how to avoid them

• Pasting the code into the wrong block. Make sure you use the Embed Code module, not a text block or HTML block. The Embed Code module is specifically designed for scripts.
• Forgetting to save after pasting. You need to click Save in the pop-up window, then click Save again after adjusting visibility.
• Skipping the "Hide on Desktop" step. If you don't hide the block, it may show as an empty element on your page.
• Using a development domain like localhost. SEATEXT restricts development URLs for security reasons. Use a real, valid domain.
• Trying to use the same account on multiple domains. Each SEATEXT account is linked to a single primary URL. If you need SEATEXT on multiple domains, create separate accounts.

How to verify the snippet is working

After pasting the snippet, you can verify it's working by:

1. Visiting your Odoo page in a browser.
2. Opening the browser's developer tools (F12) and checking the console for any errors.
3. Looking for the SEATEXT script in the page source (Ctrl+U or right-click > View Page Source). Search for "seatext" or the script URL.

If you see the script and no errors, the snippet is installed correctly. The AI won't activate until you turn it on in your SEATEXT dashboard, so don't expect immediate changes.

What happens after the snippet is installed

Once the snippet loads, SEATEXT AI sits idle. You control activation from the SEATEXT dashboard. There you choose which agents to run: the Google Ads agent rewrites headlines and CTAs per keyword, the Translation agent serves 125 languages, the Bot Protection agent filters invalid clicks, and the SEO agent publishes FAQ pages for AI search. Each agent toggles on independently. No code changes are needed after the initial snippet.

Managing multiple Odoo environments

If you run a staging site and a production site, you need two SEATEXT accounts. Each account binds to one primary URL. Development domains such as localhost or dynamic preview URLs are blocked for security. To test on staging, register a real domain (e.g., staging.yourcompany.com) and create a separate account. Then install the snippet on that Odoo instance. This keeps traffic data clean and prevents cross-contamination between environments.

Limitations and restrictions to know

• Multiple domains: Each SEATEXT account is tied to one primary URL. If you need SEATEXT on a development domain and a production domain, you must create separate accounts for each.
• Localhost and dynamic development domains: These are restricted for security reasons. SEATEXT may not be able to reliably associate traffic with your account on such domains.
• Account requirement: You must have a SEATEXT AI account before you can install the script. The account provides the code snippet and the activation controls.
• AI activation is manual: The snippet installs the engine. You still need to enable agents in the dashboard and select target pages or campaigns.

Key facts about SEATEXT Odoo integration

Frequently asked questions

Do I need coding skills to paste the SEATEXT snippet in Odoo?

No. The process uses Odoo's built-in Embed Code block. You just copy, paste, and save.

Can I use the same SEATEXT account on my staging and production Odoo sites?

No. Each SEATEXT account is linked to a single primary URL. You need separate accounts for different domains.

What if I don't hide the block on desktop?

The block may appear as an empty or code-like element on your page. It's best to hide it to keep your layout clean.

How long does the installation take?

The actual pasting takes under a minute. The rest is account setup and activation.

Will the snippet slow down my Odoo site?

The snippet is lightweight JavaScript. SEATEXT states the installation is secure and the AI remains inert until activated, so there's no performance impact until you turn it on.

Can I paste the snippet on any Odoo page?

Yes, you can add it to any page you can edit. The snippet is typically added to the pages you want SEATEXT to optimize.

Which SEATEXT agents work on Odoo?

All agents work once the snippet is installed: Google Ads intent matching, translation into 125 languages, bot protection with refund reports, SEO FAQ generation, personalization by referral source, and A/B testing of copy variants.

How do I activate the AI after installing the snippet?

Log into your SEATEXT dashboard, choose the agent you want, select the target pages or campaigns, and toggle the agent on. Changes appear in real time.

Why generic AI content kills your SEO (and what to do instead)

Google and AI engines like ChatGPT prefer content that offers something unique: real data, specific examples, and a clear point of view. Generic AI copy—the kind that reads like every other blog post—gets ignored by readers and often flagged as low-quality by search algorithms. The fix is not to abandon AI. It is to feed it better raw material.

The most common mistake is using vague prompts like "write an article about X" without giving the AI any brand-specific context. That guarantees filler. You need to give the AI the same things you would give a freelance writer: your customer data, your product details, your tone guide, and a list of things you will never say.

Step 1: Collect your proprietary data before you open the AI tool

Generic AI content comes from generic inputs. If you ask for "a guide to email marketing," you will get the same list of tips everyone else has. Instead, gather:

• Your own customer survey results
• Sales numbers or usage stats (even anonymized)
• Product specifications or unique features
• Case study numbers (with permission)
• Internal notes on why customers choose you

Feed these into the prompt. For example, instead of "write about our CRM," write: "We have a CRM used by 200 mid-sized agencies. Our churn rate is 0.8% monthly. Our customers say the mobile app is the main reason they stay. Use these facts to explain why we are different."

Step 2: Write a brand style guide and force the AI to follow it

Your brand voice is not a style guide on paper—it is the way you speak to customers. Create a one-page document that lists:

• Words you use (e.g., "we help", not "we leverage")
• Words you never use (e.g., "synergy", "best-in-class")
• Sentence length and structure (short vs. long)
• Your preferred pronoun (we, I, you?)
• Examples of good and bad paragraphs

Then add these examples to your prompt. Say: "Adopt this tone. Here is a sample: ... Now write the article." The AI will imitate the patterns you show it.

Step 3: Use a uniqueness checker before publishing (free or paid)

Uniqueness is not just about plagiarism. A generic article can pass a plagiarism check and still be useless. Use a brand-voice checker or a simple test: ask yourself, "Would this article be useful if it were published on a competitor's site?" If yes, rewrite.

You can also run the draft through a tool like Grammarly's tone detector, but the best check is human: read the article aloud. If it sounds like a robot summarizing Wikipedia, cut it.

Step 4: Add human-only elements that AI cannot invent

AI cannot interview your customer or see your dashboard. You can. Include:

• Real quotes from customer interviews (with permission)
• Behind-the-scenes anecdotes from your team
• Screenshots of your product with real data
• Links to your own internal research

These elements ground the content in your reality. Even if the AI writes a solid draft, your job is to insert the unique proof points before publishing.

Step 5: Edit for rhythm and remove every generic sentence

Generic AI content often has a tell: every paragraph starts with "In today's fast-paced world" or ends with a hollow summary. After the AI writes, do a pass where you:

• Cut any sentence that could be on any other website
• Replace adjectives with specific numbers and examples
• Shorten paragraphs to one or two sentences
• Rewrite the first sentence of each H2 to be actionable

For example, change "It is important to understand SEO" to "SEO rewards specificity."

Step 6: Test your content on a small sample of real readers

Before you publish a full set of AI-generated pages, test one or two. Ask a few customers or industry colleagues: "Does this sound like us?" If they say it sounds like a robot, refine your prompts. If they say it sounds helpful, you have a winning template.

You can also compare engagement metrics (time on page, bounce rate) between AI-generated and manually written pages. If the numbers are close, you are on the right track.

Step 7: Set up a repeatable workflow, not a one-time fix

Generic AI content is not a one-time problem. Every new draft needs the same rigor. Build a process:

1. Collect new data points quarterly
2. Update your style guide when your brand evolves
3. Run every draft through your uniqueness checklist
4. Keep a folder of "good AI examples" for future prompts

Once the process is in place, scaling content without losing uniqueness is possible.

Key facts: How SeaText helps you avoid generic AI content

The integration process involves accessing your Squarespace dashboard. You navigate to Settings, then Developer Tools, and finally Code Injection. The SeaText JavaScript code is pasted into the HEADER field. After saving these changes, the site must be published for the integration to become active. (S1)

Once installed, SeaText requires a period of activation. You need to visit or refresh your website multiple times. Staying on the page for at least 40 seconds helps activate the AI. (S1)

A crucial step is verifying the connection. After installation, you should wait for your website's name to appear next to the SeaText logo within your SeaText account dashboard. This usually takes about five minutes, but can extend to ten. If your website name doesn't appear, it signals a potential installation issue, and contacting SeaText support is recommended. (S1)

SeaText's AI agents work in real-time. They can rewrite landing pages based on search keywords, optimize product copy, and even provide autonomous sales chat. (S2, S3, S5, S6, S7)

Why Remove SeaText from a Trial Site

Removing SeaText from a Squarespace trial site can be beneficial for several reasons. Understanding these reasons helps clarify the importance of the removal process.

Trial Cleanup: During a trial, you might be testing multiple tools. Removing SeaText ensures your trial environment is clean and reflects your site's performance without its influence. This prevents confusion when comparing different services.

Privacy Concerns: While SeaText aims to be secure, some users may prefer to limit third-party script access to their site during testing phases. Removing the script ensures no external data collection or modification occurs.

Performance Testing: SeaText's AI agents can impact site speed and performance. Removing it allows you to accurately measure your Squarespace site's baseline performance. This is crucial for understanding how different integrations affect loading times.

Avoiding Unintended Changes: SeaText's AI features are designed to optimize your site automatically. During a trial, you might not want these automated changes. Removing SeaText prevents any unexpected modifications to your content or user experience.

Cost Management: If you decide not to continue with SeaText after the trial, removing it promptly ensures you won't incur any charges. This is especially important if the trial automatically converts to a paid subscription.

Testing Alternatives: You might be evaluating other AI or CRO tools. Removing SeaText clears the way to test these alternatives without interference. This provides a clearer comparison of features and effectiveness.

Data Integrity: For specific testing scenarios, you might want to ensure that no AI-driven data is influencing your analytics. Removing SeaText guarantees that your site's data reflects organic user behavior.

Simplifying the User Interface: During a trial, the Squarespace interface can become cluttered with various integrations. Removing SeaText simplifies the dashboard, making it easier to manage your site.

Preparing for Launch: If the trial site is intended to become a live website, removing all trial integrations is a standard pre-launch checklist item. This ensures a polished and stable final product.

In essence, removing SeaText from a trial site allows for a more controlled and accurate evaluation of your website's core functionality and performance. It also helps manage expectations and avoid potential future complications.

Prerequisites for Removal

Before you begin the process of removing SeaText from your Squarespace trial site, ensure you have the following prerequisites in place. Meeting these requirements will make the removal process smooth and efficient.

Squarespace Account Access: You must have administrative access to your Squarespace account. This includes the ability to log in to your dashboard and navigate to the site's settings. Without this access, you cannot modify the site's code injection settings.

SeaText JavaScript Snippet: The SeaText JavaScript snippet must be currently installed in your Squarespace site's Code Injection settings. Specifically, it should be located in the HEADER section. If the snippet was never added, or if it was already removed, then no further action is needed for this step.

Ability to Publish: You need the authorization and ability to publish changes to your Squarespace site. After deleting the code, you must save and republish the site for the changes to take effect on the live version. This is a standard Squarespace function.

Understanding of Code Injection: While the process is simple, a basic understanding of where the code injection settings are located within Squarespace is helpful. This guide provides detailed steps, but familiarity with the interface aids in quicker execution.

Browser Access: You will need access to a web browser to log into your Squarespace account and perform the necessary actions. Ensure your browser is up-to-date for optimal performance.

No Dependencies: Confirm that no other critical scripts or functionalities on your site rely on the SeaText JavaScript snippet. Removing the snippet should not break other essential features. If you are unsure, it is best to consult with your web developer or review your site's setup.

Having these prerequisites met ensures that you can follow the removal steps accurately and effectively. If any of these are missing, you may encounter difficulties during the uninstallation process.

Step-by-Step Removal Instructions

Follow these detailed steps to remove the SeaText JavaScript snippet from your Squarespace trial site. This process will disable all SeaText AI features on your website.

Step 1: Log In to Your Squarespace Dashboard

1. Open your preferred web browser.
2. Navigate to the Squarespace login page.
3. Enter your username and password to log in to your account.
4. Once logged in, you will see your website dashboard.

Step 2: Access Site Settings

1. In your Squarespace dashboard, locate the main navigation menu, usually on the left side.
2. Click on the website panel for the site you wish to modify.
3. You will see a three-dot icon (⋮) next to your site's name. Click this icon.
4. From the dropdown menu that appears, select Settings.

Step 3: Navigate to Developer Tools and Code Injection

1. Within the Settings menu, scroll down to the bottom of the page.
2. You will find a section labeled Developer Tools. Click on it.
3. Inside Developer Tools, select Code Injection. This will open a page with fields for HEADER and FOOTER code.

Step 4: Delete the SeaText Snippet

1. Locate the text area labeled HEADER.
2. Carefully examine the code within the HEADER field. Look for the SeaText JavaScript snippet. It typically starts with <script> and contains references to "seatext" or "seatext.com". (S1)
3. Select the entire SeaText JavaScript code block. Ensure you select from the opening <script> tag to the closing </script> tag.
4. Press the Delete or Backspace key on your keyboard to remove the selected code.
5. Double-check that you have removed the complete snippet and not just a portion of it. Also, ensure no other essential code was accidentally deleted.

Step 5: Save Your Changes

1. After deleting the SeaText snippet, look for a Save button, usually located at the top left of the Code Injection page.
2. Click Save to confirm and store the changes you have made.

Step 6: Republish Your Squarespace Site

1. Once the changes are saved, you need to publish them to make them live.
2. Navigate back to your main Squarespace dashboard or site preview.
3. Click the Publish button. This is typically found in the top left corner of the screen.
4. Confirm the publication if prompted. Your site will now be updated with the SeaText code removed.

By following these steps, you will successfully remove SeaText's functionality from your Squarespace trial site.

Verifying the Removal

After completing the removal steps, it's essential to verify that SeaText has been successfully uninstalled from your Squarespace site. This ensures that its features are no longer active and that no residual code remains.

Check the Live Site

1. Open a new browser tab or window.
2. Navigate to your live Squarespace website's URL.
3. Wait a few moments for the page to load completely.
4. Look for any SeaText branding, such as a logo or specific AI-generated text elements. These should no longer be visible.
5. If you previously used SeaText for translation, check if the language options or translated text are gone.
6. If you used SeaText for CRO or personalization, observe if the site behaves as it did before SeaText was installed.

Use Browser Developer Tools

1. On your live website, right-click anywhere on the page and select Inspect or Inspect Element. This will open your browser's developer tools.
2. Navigate to the Console tab. Look for any error messages related to SeaText or seatext.com. If the removal was successful, there should be no SeaText-related errors.
3. Go to the Network tab. Refresh your page. Filter the requests by "seatext" or "seatext.com". If SeaText is removed, you should not see any network requests being made to these domains.

Check SeaText Account (Optional)

1. Log in to your SeaText account dashboard.
2. Check if your website is still listed as connected or active. If the code was removed correctly, your site should no longer appear as connected.
3. Note that the SeaText account itself still exists, but its integration with your Squarespace site is broken.

If you do not see any SeaText elements on your site and no SeaText-related errors or network calls appear in the browser console, the removal process has been successful.

Common Mistakes and Troubleshooting

Even with clear instructions, users can sometimes encounter issues when removing SeaText. Here are common mistakes and how to troubleshoot them.

Mistake 1: Deleting Only Part of the Snippet

Problem: You might accidentally delete only a portion of the SeaText JavaScript code, leaving behind incomplete or broken script tags. This can lead to errors or unexpected behavior.

Solution: Carefully re-examine the HEADER section in Code Injection. Ensure you have selected and deleted the entire block of code, from the opening <script> tag to the closing </script> tag. If unsure, delete everything that looks like it might be SeaText code and then re-add any other essential custom code you might have.

Mistake 2: Forgetting to Save or Publish

Problem: You delete the code but forget to click the 'Save' button or 'Publish' your site. The changes will not appear on the live

To remove the SeaText AI JavaScript, delete the snippet from wherever you installed it. On Shopify, that means going to Online Store → Themes → Edit code, opening Layout/theme.liquid, removing the SEATEXT code, and saving the file. On WordPress, Webflow, or any other site, reverse the same step you used to paste the code in the first place.

If you are not sure you want it gone forever, you can leave the code in place. The installation is secure and “the AI remains inert until activated,” so nothing changes on your site until you turn an agent on. This guide covers both full removal and verification.

What the SeaText AI code does and why removal matters

SeaText installs as a client-side JavaScript snippet. In Shopify, the integration guide tells you to paste it into your active theme's theme.liquid file inside the Layout folder. On other websites, you may have used a theme header/footer field, a code injection area, or a tag manager.

When you remove the snippet, the script no longer loads on your pages. If you do not remove it and you do not activate any agents, the code sits there without changing your content. But it is still a third-party script, so removing it is the right move if you no longer want that connection at all.

Before you start: what you need

• Admin or editor access to the site where the code is installed.
• Editor access to Shopify themes or your CMS's custom code section.
• A saved copy or duplicate of the theme if you work in Shopify.
• A clear idea of where the code lives: theme.liquid, product template, page head, tag manager, or plugin.

You do not need to delete your SeaText account to remove the code. Removing the JavaScript only removes it from your website.

How to remove the SeaText code from Shopify

1. Log in to your Shopify admin.
2. Go to Online Store and open Themes.
3. On your active theme, click the three dots and choose Edit code.
4. In the left file list, open the Layout folder and select theme.liquid.
5. Find the SeaText snippet. Press Ctrl+F on Windows or Cmd+F on Mac and search for SEATEXT or seatext.com.
6. Select the entire script block. A minified snippet often sits on one long line, so select the whole thing, not just the part with the brand name.
7. Delete it.
8. Click Save.
9. Preview a page to make sure the layout still works.

If you also added the product description tag

The SeaText integration guide also describes wrapping product descriptions with a data attribute. That optional markup lives in the product template, not in theme.liquid. If you added it, open the product template and remove that wrapper too.

How to remove SeaText code on WordPress, Webflow, or a tag manager

The process is the reverse of the install. Find the file or field where you pasted the snippet and delete the same snippet.

WordPress

• Check Appearance → Theme File Editor and look in header.php or footer.php.
• If you used a code snippet plugin like “Insert Headers and Footers,” remove it there.
• If you added it through Google Tag Manager, see the tag manager step below.

Webflow

• Go to Site Settings → Custom Code.
• Look in the Head Code and Footer Code boxes.
• Delete the SeaText snippet and save. Publish the site after saving.

Google Tag Manager or another tag manager

• Open the container that holds the SeaText tag.
• Find the tag. SeaText tags usually contain SEATEXT or seatext.com in the tag name or URL field.
• Delete the tag, or unpublish the current container version.
• Submit the new container version and make it live.

On a site builder you are not sure about, do this: open the custom code area, search for “seatext,” and delete exactly what you see. Do not remove a script that belongs to your theme or another tool.

How to verify the code is gone

1. Hard-refresh your webpage to bypass the browser cache.
2. View the page source and search for SEATEXT and seatext.com. If neither appears, the main snippet is gone.
3. Open browser developer tools and go to the Network tab. Reload the page and search for “seatext” in the request list. You should see no requests to a SeaText domain.
4. If you used Google Tag Manager, check the live container version and make sure the SeaText tag is absent.
5. Check any product page where you added the optional data attribute. Remove that markup as well if you want a full cleanup.

One common mistake is checking before the cache clears. Always test in a private browser window after saving your changes.

Key facts from the SeaText integration guide

Use these facts to avoid setup mistakes if you decide to reinstall later.

Common removal mistakes

• Deleting only part of a minified script. The whole script block must go, not just the line with the brand name.
• Editing the wrong theme. Make sure you are editing the active theme in Shopify, not an old duplicate.
• Forgetting the product template wrapper. If you added the optional data attribute markup, remove it from the product template too.
• Checking before the cache clears. Test in a private window or after a hard refresh.
• Assuming removal cancels your account. Removing the code from your site is a separate step from closing or changing your SeaText account.

Limitations and when this advice doesn't apply

This guide assumes you or someone on your team pasted the code manually. If SeaText was installed by an agency, ask them to remove it. If it came from a Shopify app, uninstall the app instead of editing code.

• The steps cover client-side JavaScript, not a server-side integration. If a developer installed it server-side, reverse the server-side changes.
• Removing the snippet does not automatically change your account's domain setup or billing.
• Do not use the same SeaText account on a development domain and a production domain. Each account is linked to one primary URL.
• Localhost and dynamic development URLs are restricted, so you cannot test a fresh install on those domains.

Terminology

• JavaScript snippet: the short block of code you copy and paste into your site.
• theme.liquid: the main layout file in a Shopify theme where SeaText is usually installed.
• Code injection: a CMS field that lets you add head or footer code without editing core theme files.
• Tag manager: a tool like Google Tag Manager that controls when third-party scripts load.
• Data attribute: the data- markup mentioned in the SeaText product description instructions.

Frequently asked questions

What happens if I leave the code in place but don't activate agents?

According to SeaText's integration guide, the AI remains inert until activated. The code can stay without automatically changing your site. If you want no third-party script at all, remove it.

Does removing the code cancel my SeaText account?

No. Removing the code removes the script from your site. Account-level settings stay with SeaText, so closing or changing the account is a separate step in your SeaText account settings.

Can I use one SeaText account on both production and staging?

No. Each SEATEXT AI account is linked to a single primary URL. Use separate accounts for each domain. Development URLs such as localhost are restricted.

I can't find the code. Where should I look?

View the page source and search for “SEATEXT” or “seatext.com.” Check Shopify's theme.liquid, your CMS custom code area, and Google Tag Manager. If the snippet was added through a plugin or app, look in that app's settings.

Do I need to remove the data attribute from product pages too?

If you added the optional product template wrapper from the integration guide, yes. That markup is separate from the main JavaScript snippet, and it also needs to be removed for a full cleanup.

Will removing the code break my theme?

Generally no. The SeaText snippet is an independent script. Deleting it returns the file to its pre-install state. Save a theme backup before editing so you can restore quickly if anything goes wrong.

To reset AI parameters to factory defaults after installation, open the SeaText Main AI Hub, select the page you want to reset, and open Configuration. Use the reset option if your dashboard shows one, or manually restore each parameter to its starting value. Do this only after the SeaText script is installed and the AI is activated and linked to your account.

SeaText’s own integration steps treat activation as a separate stage. The script is secure and the AI remains inert until it is activated. So a reset mostly matters after you have changed something: a headline, a CTA, a translation, a variant, or an agent setting.

What “factory defaults” means here

In SeaText, the parameters you can adjust live in Configuration inside the Main AI Hub. They control how agents rewrite the page, which variants are visible, and which translations are active. “Factory defaults” means the state of those settings before you changed them.

The General Integration guide does not promise a universal one-click reset button. Some dashboards provide one; others expect you to set values back manually. Start by checking Configuration, then use the manual route if you need to. If you skip a reset, edited variants and agent settings can stay active, so the page can keep showing copy you meant to replace.

Before you reset: check these three things

Do not reset while the site is still connecting. A reset on a disconnected account can look successful and then change nothing.

1. The script is installed

You need a SeaText AI account before you can install the script. Copy the JavaScript code provided by SeaText and add it to your pages. On WP Engine, install the WP Engine plugin that lets you add custom JavaScript, then apply it across all your pages.

2. The AI is activated

Visit or refresh your website several times and stay on the page for at least 40 seconds. That activates the AI and links it to your account.

3. The site shows as connected

Wait at least five minutes. You should see your website name next to the SEATEXT logo at the top of the SeaText page. If you do not see it after 10 minutes, contact support before you reset anything.

Step-by-step: reset AI parameters to factory defaults

1. Log in to your SeaText AI account.
2. Go to the Main AI Hub.
3. Select the page whose parameters you want to reset. If you run several pages with agents, repeat the process for each page.
4. Click Configuration.
5. Look for a Reset to Defaults or Restore Defaults option. If it exists, choose it and confirm.
6. If no one-click reset is available, go through each parameter and return it to its initial value. Use Variants Edit in the left panel to review, create, or manually edit the translations and variants that were changed.
7. Save your changes.
8. Refresh or visit the page to confirm the old settings are gone.

Manual reset is slower but just as valid. It also gives you a chance to delete or disable variants you no longer want.

How to verify the reset worked

Start with the connection check. The website name should appear next to the SEATEXT logo at the top of the SeaText dashboard. If the site is not connected, the reset will not hold.

Next, open Configuration again and compare each value with what you expect as the default. Then visit or refresh the page several times and stay for at least 40 seconds. If the old headline, CTA, or translation still appears, check Variants Edit. The reset may restore parameters without removing previously generated variants.

Common mistakes that break a reset

• Resetting before activation. The AI remains inert until activated, so there is nothing to reset yet.
• Using one account on multiple domains. Each SeaText account is linked to a single primary URL. For a development domain and a production domain, create separate accounts.
• Testing on localhost. Development URLs such as localhost are restricted for security reasons. Use a valid real domain.
• Forgetting the connection wait. Give the system at least five minutes to show your website name. If it does not appear after 10 minutes, contact support.
• Assuming reset deletes variants. Configuration controls parameters. Variants Edit is where translations and alternate versions are managed.

Key facts from the SeaText integration guide

Limitations and when a reset is not the right fix

A parameter reset fixes settings, not connection problems. If the website name never appears next to the SEATEXT logo, the issue is installation or activation, not Configuration. Resetting parameters will not make the script connect.

The one-account-per-domain rule also limits what a reset can do. You cannot reset a development domain and a production domain from the same account. And if you have not activated the AI yet, you are already at a default state; no reset is needed.

If your goal is to remove all custom translations and variants, a parameter reset alone may not be enough. You also need to clean up in Variants Edit.

Terms you may see in Configuration

• Main AI Hub: the dashboard where you activate AI on your preferred pages.
• Configuration: the section where you adjust AI parameters.
• Variants: alternate versions of translations and copy that SeaText creates for testing.
• Variants Edit: the left-panel area where you review or manually edit variants.
• Activation: the step that links the installed script to your account.

FAQ

Is there a one-click reset in SeaText?

The official guide points to Configuration to adjust parameters. It does not describe a universal reset button. Open Configuration and look for a reset action. If you do not see one, restore the values manually.

When is the right time to reset after installation?

After the script is installed, after you visit or refresh the page and stay for 40 seconds, and after the website name appears next to the SEATEXT logo. Reset after these checks, not before.

Will a reset delete my translated variants?

Not automatically. Configuration controls parameters; Variants Edit is where translations and variants are reviewed and edited. If you want a completely clean set, remove or edit them there.

Can I reset one page without affecting the rest of the site?

Yes, if you select that page in the Main AI Hub and adjust its Configuration. For multi-domain setups, each domain needs its own account.

What should I do if the website name does not appear after 10 minutes?

Contact SeaText support. The integration guide says this could indicate an installation issue on your platform, and you may need assistance.

Why can’t I use localhost to test the reset?

Development URLs such as localhost are restricted for security reasons. Use a valid real domain because dynamic development domains may not work reliably.