SeaText requires a separate account for each Squarespace domain you want to optimize. Each account is tied to a single primary URL, so you cannot use one SeaText login to manage multiple domains.

If you try to use the same account on another domain, the AI will not activate and you may see connection errors.

Symptoms of the Limitation

When you paste the same SeaText JavaScript snippet on a second Squarespace site, the dashboard does not show the site name next to the SeaText logo. The AI remains inactive, and you may receive a prompt to create a new account.

How to Diagnose the Issue

1. Log in to your SeaText account and check the top‑right corner for the website name.
2. If the name shown does not match the domain you are viewing, the account is not linked to that domain.
3. Visit the Squarespace site and wait at least five minutes; if the name never appears, the limitation is in effect.

Likely Causes

• SeaText ties each account to a single primary URL for security and billing.
• The activation process requires a unique domain‑specific handshake that cannot be reused.
• Development URLs such as localhost are blocked, reinforcing the one‑account‑per‑domain rule.

Corrective Actions

1. Create a new SeaText account for each additional Squarespace domain.
2. In the SeaText dashboard, copy the JavaScript snippet provided for that account.
3. In Squarespace, go to Settings → Developer Tools → Code Injection and paste the snippet into the Header field.
4. Save, publish, then visit the site and wait 40 seconds for activation.
5. Confirm the site name appears next to the SeaText logo; if not, wait five minutes or contact support.

Best Practices for Managing Multiple Accounts

• Use a password manager to keep track of login credentials for each SeaText account.
• Label each account clearly (e.g., "SeaText – example‑com prod" and "SeaText – example‑com dev").
• Set up a calendar reminder to re‑verify activation after any major Squarespace template change.

When the Advice Does Not Apply

If you are using subdomains that point to the same Squarespace site (e.g., blog.example.com and shop.example.com) and they share the same primary URL setting in Squarespace, a single SeaText account may work because the domain is considered one site. However, if each subdomain is treated as a separate site in Squarespace, you still need separate accounts.

Business Impact of Multi‑Domain Limitations

Each extra domain forces a new SeaText account. That adds administrative overhead for teams that run many sites. Marketers must repeat the installation steps for every domain. Reporting becomes fragmented because each account has its own dashboard. Consolidated performance views are not available without manual data export.

Agencies that manage dozens of client sites see a linear increase in setup time. The time spent copying snippets, verifying activation, and tracking credentials grows with each new domain. This can delay campaign launches and reduce overall efficiency.

Cost Implications for Multiple Accounts

SeaText bills each account separately. If you run ten domains, you pay for ten subscriptions. The total cost scales directly with the number of domains. There is no volume discount mentioned in the public documentation. Budget planning must account for this linear cost model.

For businesses on tight margins, the per‑domain fee may limit the number of sites that can be optimized. Decision makers should compare the expected conversion lift against the cumulative subscription expense.

Strategic Alternatives to Separate Accounts

One alternative is to consolidate multiple Squarespace sites under a single domain using subdirectories or subdomains that share the same primary URL. This works only if Squarespace treats them as one site. Another option is to evaluate competing AI optimization tools that allow multi‑site management from a single dashboard. A third approach is to prioritize high‑traffic domains for SeaText and use manual SEO tactics for lower‑traffic sites.

Each alternative has trade‑offs. Consolidation may affect branding and URL structure. Switching tools requires migration effort and learning curve. Prioritization leaves some sites without AI‑driven optimization.

Why This Matters for Agencies and Multi‑Site Businesses

Agencies often handle many client accounts simultaneously. The one‑account‑per‑domain rule creates workflow friction. Team members must log in and out of multiple SeaText dashboards. Credential sharing becomes a security concern. Billing complexity rises because each client may need a separate invoice.

For businesses that own several brands, the same friction applies. Finance teams must track multiple line items. Project managers lose a single source of truth for optimization performance. The cumulative effect can slow decision making and increase operational risk.

Key Facts

FAQ

Can I use the same SeaText account for a domain and its subdomain?

Only if Squarespace treats the subdomain as part of the same site; otherwise you need a separate account.

What happens if I try to activate SeaText on a second domain without a new account?

The AI will not activate; the dashboard will not display the site name and you may see an error prompting you to create a new account.

Are there any workarounds to avoid multiple accounts?

No official workaround exists; the limitation is built into the SeaText security model.

How long does activation take for each new domain?

After pasting the snippet, wait at least 40 seconds for activation and up to five minutes for the site name to appear next to the SeaText logo.

Do I need to pay for each SeaText account?

Yes, each account is billed separately according to the plan you choose.

To use SeaText on multiple Squarespace websites, you must create one individual SeaText account for each website. SeaText does not support managing multiple domains from a single dashboard or account login.

Each account is tied to a specific primary URL. This architecture ensures that the AI agents, such as the Google Ads Optimization Agent or the Conversion Relay, can accurately associate traffic, reading telemetry, and conversion data with the correct domain.

Understanding the One-Account-Per-Domain Rule

SeaText requires a unique connection between your website's code and your account. When you install the SeaText JavaScript snippet into the Code Injection header of your Squarespace site, the AI must be able to verify the domain to function correctly. Because the system links your account to a single primary URL, attempting to use one account across multiple sites will cause data conflicts and prevent the AI from activating properly.

This rule is not a limitation you can bypass. It is a core design decision. Every SeaText account is a container for one domain's data, settings, and AI agents. The system uses the domain as the primary key to associate all telemetry and conversions. If you try to reuse a snippet on another domain, the AI will not recognize the domain as valid, and the handshake will fail.

For example, if you have a development domain and a production domain, you must create two separate SeaText accounts. The development domain might be a staging site or a local test environment. SeaText explicitly restricts development URLs like localhost for security reasons. Even if you use a real domain for staging, it must have its own account.

Why Separate Accounts Are Required

The technical reason for separate accounts is data integrity. SeaText AI agents rely on precise, domain-scoped data to make real-time decisions. Consider the Google Ads Landing Page AI. It reads incoming search query parameters, such as utm_term or Google Ads ValueTrack tags, and rewrites your landing page copy in under 15 milliseconds to match the visitor's intent. If multiple domains shared one account, the AI would not know which domain's data to use for which visitor. It would mix conversion signals, reading telemetry, and copy variants across brands, leading to incorrect rewrites and broken tracking.

Similarly, the Conversion Relay (CAPI) forwards purchase events to Meta and Google. Each domain has its own pixel and CAPI setup. If you merged domains into one account, the relay would send events to the wrong ad accounts or mix them, corrupting your ad optimization. The same applies to the AI CRO Reading Analysis agent, which tracks millisecond-level reading behavior to identify friction points. That data is only meaningful when tied to a single domain's visitor sessions.

In short, the one-account-per-domain rule is a safeguard for accuracy. It prevents cross-domain contamination and ensures that every AI agent operates on clean, isolated data.

Decision Criteria for Multi-Domain Management

If you manage a portfolio of websites, use this framework to organize your SeaText setup:

• Account Separation: Create a distinct account for every production domain.
• Development Domains: Do not attempt to use SeaText on development URLs like localhost or temporary staging links. These are restricted for security reasons.
• Verification: After installing the snippet on each site, visit the page and stay active for at least 40 seconds. This triggers the initial handshake between your site and the SeaText AI.
• Monitoring: Wait at least five minutes after installation. You should see your specific website name displayed next to the SeaText logo at the top of your dashboard.

When deciding whether to add a new domain, ask yourself: Is this a separate brand or business? Does it have its own ad campaigns, analytics, or conversion goals? If yes, it needs its own SeaText account. Even if two domains are closely related, such as a main site and a subdomain, SeaText treats them as separate primary URLs. You must verify with support if you have complex subdomain requirements, but the default is one account per URL.

Practical Steps for Managing Multiple Domains

Here is a step-by-step workflow to set up SeaText on multiple Squarespace sites without confusion:

1. Create a SeaText account for each domain. Use a unique email or a naming convention that clearly identifies the domain, such as domain1@yourcompany.com and domain2@yourcompany.com.
2. Copy the JavaScript snippet from each account. Do not mix them. Each snippet contains a unique identifier tied to its account.
3. Install the snippet on the corresponding Squarespace site. Go to Settings → Developer Tools → Code Injection and paste the snippet into the Header area. Save and publish the site.
4. Activate each site. Visit the live URL, refresh it a few times, and stay on the page for at least 40 seconds. This triggers the AI handshake.
5. Verify the connection. After five minutes, check the SeaText dashboard. The website name should appear next to the SeaText logo. If it does not appear after 10 minutes, contact support.
6. Repeat for each domain. Keep a spreadsheet to track which account belongs to which domain, along with installation dates and verification status.

This process is straightforward but requires discipline. Do not try to shortcut it by reusing snippets. The AI will not activate, and you will waste time troubleshooting.

Trade-offs and Limitations

The one-account-per-domain rule has trade-offs. The most obvious is cost. Each account may require a separate subscription, depending on your plan. SeaText pricing is not explicitly detailed in the source, but you should check with the vendor for current plans. If you have many domains, the total cost can add up.

Another limitation is management overhead. You must log into multiple dashboards to monitor AI agents, review performance, and adjust settings. There is no central view for all domains. This can be cumbersome for agencies or businesses with a large portfolio.

However, the benefits outweigh the drawbacks for most users. Isolated data means more accurate AI decisions. You can tailor each domain's AI agents to its specific audience and goals. For example, a B2B site might use the Google Ads Agent heavily, while a B2C ecommerce site might prioritize the Ecommerce Product Copy agent. With separate accounts, you can configure each independently without interference.

Another limitation is that development domains are not supported. If you need to test SeaText on a staging site, you must use a real, publicly accessible domain. This might be inconvenient, but it is a security measure to prevent abuse and ensure reliable traffic association.

Common Setup Mistakes

Avoid these common pitfalls to ensure your AI agents deploy successfully:

• Sharing Snippets: Never copy the JavaScript snippet from one account and paste it into a different website's header.
• Ignoring Dynamic Domains: If your development environment uses dynamic URLs, the AI will fail to associate traffic reliably. Always use a stable, valid domain.
• Premature Testing: If you do not see your website name in the SeaText dashboard after 10 minutes, do not assume it is working. Contact support immediately to verify the installation.
• Forgetting to Publish: In Squarespace, you must save and publish your site after adding the code injection. If you only save without publishing, the snippet will not be live.
• Using the Same Account for Multiple Sites: This is the most common mistake. It will cause data corruption and the AI will not activate. Always create a new account for each domain.

Frequently Asked Questions

Can I use one SeaText subscription for a development and production domain?

No. You must create separate accounts for each. Development domains are restricted for security, and production domains require their own unique account link.

What happens if I use the same code on two different sites?

The AI will be unable to reliably associate traffic with your account, and your conversion data will become corrupted or fail to track entirely.

How do I know if my domain is successfully connected?

Your website name will appear next to the SeaText logo at the top of your dashboard after you have visited the site and waited at least five minutes.

Does this limit apply to subdomains?

SeaText is linked to a primary URL. If you have complex subdomain requirements, contact support to ensure your specific configuration is supported.

Can I manage multiple domains from one login?

No. Each domain requires its own account and login. You can use the same email address for multiple accounts, but each account is separate.

What if I have a multi-tenant setup or a network of sites?

You will need one account per site. For large portfolios, consider using a dedicated email alias for each domain to keep things organized. Check with the vendor if you need a bulk pricing option.

How long does activation take?

After installing the snippet, you must visit the site and stay for at least 40 seconds. Then wait five minutes for the dashboard to update. If it does not appear after 10 minutes, contact support.

Can I use SeaText on a domain that is not on Squarespace?

Yes, SeaText works on any website where you can inject JavaScript. The integration instructions are specific to Squarespace, but the same account-per-domain rule applies.

What are the benefits of separate accounts for my AI agents?

Separate accounts ensure that each domain's AI agents learn from clean, isolated data. This leads to more accurate copy rewrites, better conversion tracking, and more reliable ad optimization.

Is there a way to test SeaText without a real domain?

No. Development URLs like localhost are restricted. You must use a valid, real domain. You can use a subdomain of an existing domain, but it will still require its own account.

Understanding Account Architecture

SeaText ties one account to a single primary URL. Each account can only be linked to one domain at a time. This design prevents data mixing between sites.

If you operate multiple Squarespace domains—such as a live store, a development site, or separate brand sites—you must create a distinct SeaText account for every domain.

Why Separate Accounts Are Required

Separate accounts keep AI agents, conversion tracking, and translation settings isolated. Mixing domains in one account can cause data cross‑contamination.

Example 1: A/B test pollution. If two sites share an account, the AI may attribute a variant’s performance from Site A to Site B, skewing results and leading to wrong optimization decisions.

Example 2: Conversion attribution errors. A purchase on Site 1 could be logged as a conversion for Site 2, inflating or deflating ROI reports and breaking the Google Ads Optimization Agent’s feedback loop.

Example 3: AI agent confusion. The Personalization Agent relies on visitor context tied to a specific domain; blended data may cause it to show irrelevant copy, reducing conversion lift.

These risks justify the one‑account‑per‑domain rule.

Steps to Connect a New Domain

1. Create a new SeaText account using a unique email address for the target domain.
2. In Squarespace, open Settings → Developer Tools → Code Injection.
3. Paste the JavaScript snippet from your SeaText account into the Header field.
4. Save the changes and ensure the Squarespace site is published.
5. Visit the live site and refresh several times. Stay on the page for at least 40 seconds to trigger AI initialization.
6. Wait up to ten minutes. Your domain name should appear next to the SeaText logo in the dashboard, confirming a successful link.

Troubleshooting Common Installation Errors

• Snippet not firing: Verify that the code was placed in the Header injection area and that the site is published. Open the page source and look for the SeaText script tag.
• Content Security Policy (CSP) blocks: If your Squarespace plan allows CSP editing, add the SeaText domain to the allowlist. Otherwise, check with the vendor for CSP options.
• Squarespace AJAX navigation: Ensure the snippet is present on every page load. For AJAX‑driven sites, check with Squarespace documentation on how to include global scripts.
• Development URLs: SeaText does not support localhost or temporary preview URLs. Use a live, publicly accessible domain for verification.
• Missing dashboard confirmation: If the domain name does not appear after ten minutes, repeat the activation steps or contact SeaText support.

Best Practices for Managing Multiple SeaText Accounts

• Use a clear naming convention, such as "Brand‑Prod" or "Brand‑Dev", to identify each account instantly.
• Store login credentials in a secure password manager that supports sharing with team members while maintaining audit logs.
• Grant team access only to the accounts they need. Use SeaText’s role‑based permissions if available, otherwise share login details securely.
• Regularly review account activity dashboards to spot unexpected traffic or configuration drift.
• Document each account’s purpose, associated domain, and any custom AI agent settings in an internal wiki.

Staging vs. Production Domain Handling

Treat staging and production as separate domains because SeaText cannot differentiate them within a single account.

Create a dedicated SeaText account for the staging subdomain (e.g., staging.example.com). Use the same installation steps as for the live site.

When you push changes from staging to production, repeat the snippet installation on the production domain. Do not copy the staging account’s credentials to production.

Keep the staging account active only during testing periods. Pause or delete it when not needed to avoid unnecessary costs.

Activation and Verification Mechanics

After installing the snippet, SeaText’s AI remains inert until it receives sufficient engagement signals.

You must stay on the page for at least 40 seconds. This dwell time allows the AI to load, initialize its agents, and begin reading visitor behavior.

Following activation, the system requires up to ten minutes to verify the connection. During this window, the dashboard checks for a heartbeat from the snippet and displays your domain name next to the SeaText logo.

If the name does not appear after ten minutes, the installation likely failed. Re‑check the snippet placement, ensure the site is published, and contact support if needed.

Comparison: SeaText Single‑Domain Architecture vs. Multi‑Domain Competitors

Frequently Asked Questions

Can I migrate a domain from one SeaText account to another?

Yes. To move a domain, install the snippet from the target account on the Squarespace site and remove the old snippet. Verify the new account after the 40‑second activation and ten‑minute verification windows.

Does SeaText support subdomains?

Each subdomain is treated as a separate primary URL. You must create a distinct SeaText account for every subdomain you wish to optimize.

Are SSL certificates required for SeaText to work?

SeaText functions on both HTTP and HTTPS sites, but HTTPS is strongly recommended for security and to avoid mixed‑content warnings in browsers.

How should agencies manage SeaText accounts for multiple clients?

Agencies can use a password manager to store each client’s account credentials. Assign a unique naming convention that includes the client name and domain purpose (e.g., "ClientA‑Prod"). Provide clients with read‑only access if they only need to view reports, and reserve admin access for the agency’s optimization team.

What happens if I exceed the ten‑minute verification window without seeing my domain name?

Double‑check that the snippet is in the Header injection area, that the site is published, and that there are no CSP or ad‑blocker interferences. If the issue persists, contact SeaText support for further troubleshooting.

Overview

When you add a new Squarespace domain to SeaText you must create a separate SeaText account for that domain. Each account is tied to one primary URL, so the new domain cannot be managed from an existing login.

This guide shows the exact steps, explains why each step is required, and describes what you should see after the process finishes.

Why each domain needs its own SeaText account

SeaText links every account to a single primary URL. The integration documentation states: 'Each SEATEXT AI account is linked to a single primary URL' and 'To use SEATEXT AI on several websites, create one account for each website.' This means a new Squarespace domain — whether it is a production site, a staging environment, or a regional variant — must have its own SeaText account. You cannot add the domain to an existing account or manage multiple domains from one dashboard.

Because the account‑to‑domain ratio is fixed at 1:1, billing, usage limits, and agent activation are calculated per account. If you try to use one login for two domains the second domain will not activate and you will see no AI features.

Having a dedicated account also keeps data isolated. Translation variants, A/B test results, and personalization rules stay bound to the single URL that the account was created for.

Step‑by‑step process for adding a new domain

1. Create a new SeaText account for the new domain. Use the domain's full URL (for example https://newsite.squarespace.com or https://www.yournewdomain.com) as the primary URL during signup. This tells SeaText which URL the account will be linked to.
2. Copy the JavaScript snippet from the new account's integration page. The snippet is a block of code that loads the SeaText AI library and prepares it to run on your site.
3. Open the Squarespace dashboard for the new site. Click the three‑dot icon, choose Settings, scroll to Developer Tools at the bottom, and select Code Injection. This is the place where Squarespace allows you to insert custom HTML or JavaScript.
4. Paste the snippet into the HEADER area and click Save. Placing the code in the HEADER ensures it loads before the page content, which is required for the AI to modify the page as it renders.
5. Publish the site if it is not already live. The script will not activate on unpublished or password‑protected sites because SeaText needs to detect real visitor traffic.
6. Visit the live site several times and stay on the page for at least 40 seconds each visit. This triggers the AI activation and links the domain to the account. The 40‑second threshold gives the AI enough time to collect signals and start its processes.
7. Wait five to ten minutes, then check the SeaText dashboard. The new site's name should appear next to the SeaText logo at the top of the page. This visual cue confirms that the account is connected to the domain.

Activation timeline and verification

After installation the AI remains inert until activated. The documentation says: 'Visit or refresh your website several times and stay on your page for at least 40 seconds — this will activate the AI and link it to your account.' During these visits the AI begins to collect usage data and prepares its features.

Then: 'Wait at least five minutes until you see your website name displayed next to the SEATEXT logo at the top of this page. This indicates that your website is connected and ready to proceed.' The name appears once the backend has registered the activation signal from your visits.

If the name does not appear after ten minutes, contact support — this usually signals an installation issue on the Squarespace side. Common causes are missing code, code placed in the wrong section, or the site still being in draft mode.

Development vs. production domains

SeaText restricts development URLs such as localhost for security reasons. The documentation warns: 'Dynamic development domains may not function properly, as SEATEXT AI might be unable to reliably associate traffic with your account.' This restriction prevents accidental use of non‑public addresses that could lead to inaccurate reporting.

If you need a staging environment, use a real, publicly accessible domain (for example staging.yourdomain.com) and create a separate SeaText account for it. Each account still follows the one‑domain rule, so you will have two accounts: one for the live site and one for the staging site.

Using a real subdomain also ensures that the AI can track genuine visitor behavior, which is required for features like personalization and A/B testing.

Common issues and troubleshooting

• Site name not appearing after 10 minutes — usually means the JavaScript snippet was not saved in the HEADER area, the site is not published, or the visits did not meet the 40‑second threshold. Check the Squarespace Code Injection panel to confirm the code is present and saved.
• Script not loading — verify the snippet is exactly as provided, with no extra characters, line breaks, or missing symbols. Even a single altered character can prevent the library from initializing.
• Multiple domains under one login — not supported. You must log in to each SeaText account separately because the authentication token is bound to the account‑specific URL.
• Password‑protected or trial Squarespace sites — may block the activation visits. Temporarily disable password protection during setup, then re‑enable it after the AI shows as connected.
• Visits too short — if you leave the page before 40 seconds the AI does not consider the visit valid. Keep the tab open and interact with the page (scroll, click) to reach the required time.

Limitations and restrictions

• One SeaText account per primary URL — no exceptions. This rule applies to all domain types, including subdomains and alternate protocols.
• No localhost or dynamic development domains. Attempting to use these addresses will result in the AI staying inactive.
• Each account requires its own installation, activation visits, and configuration. You cannot reuse a snippet from another account.
• AI features are scoped to the single domain in that account. Translation variants, personalization rules, and test results do not copy to other domains.
• Billing, usage limits, and agent activation are per account. Changing the plan or adding agents affects only the domain linked to that account.
• The AI remains inert until it receives the activation signal from real visits. No amount of code installation alone will start the features.

Key facts

Frequently asked questions

Can I use one SeaText account for a main domain and its subdomains?

No. Each subdomain (for example blog.yoursite.com or shop.yoursite.com) counts as a separate primary URL and requires its own SeaText account. The AI treats each subdomain as an independent site because the account‑to‑domain link is strict.

What if I migrate a Squarespace site to a new domain?

Create a new SeaText account for the new domain and repeat the full installation and activation process. The old account remains tied to the old URL and will continue to work for that address unless you delete it.

Does SeaText charge per domain?

Yes. Since each domain needs a separate account, billing is per account. Check the pricing page for current plans to see the cost per active account.

Can I install SeaText on a Squarespace trial site before launching?

Only if the trial site is published and publicly accessible. Password‑protected trial sites will not activate the AI because the AI cannot record the required visits.

What happens if I add the script but never visit the site?

The AI stays inert. Activation requires real visits that meet the 40‑second threshold. No visits means no activation and no AI features running, so you will not see any translation, personalization, or testing effects.

Is there a bulk‑install option for agencies managing many Squarespace sites?

No. Each site requires its own account creation, script copy‑paste, and activation visits. There is no multi‑site dashboard or bulk deployment tool, so the process must be repeated for every domain.

How SeaText Installs on Squarespace

SeaText runs on Squarespace through a JavaScript snippet you paste into the Code Injection header. Once installed, the AI stays inert until activated, so it does not affect site performance before you complete setup.

To install, open your Squarespace dashboard, go to Settings, then Developer Tools, and select Code Injection. Paste the provided JavaScript code into the HEADER area and save. Publish your site for the changes to take effect.

If your Squarespace plan provides Code Injection, you can install SeaText directly; otherwise you must upgrade to a plan that includes Code Injection before proceeding.

Decision Criteria: Which Plan Works for SeaText

Use this simple rule: if your Squarespace plan includes Code Injection, you can install SeaText. If it does not, upgrade before you start.

Each SeaText account is linked to a single primary URL. If you run multiple Squarespace domains, you need one SeaText account per domain. A single login cannot manage multiple domains.

Choose a plan that includes Code Injection. Choose a higher tier if you also need ecommerce features SeaText can optimize, such as product copy and checkout personalization.

Setup Steps for Squarespace

1. Create a SeaText account for the domain you want to optimize.
2. Copy the JavaScript code from your SeaText dashboard.
3. In Squarespace, go to Settings, then Developer Tools, then Code Injection.
4. Paste the code into the HEADER area and save.
5. Publish your site.
6. Visit or refresh your site and stay on the page for at least 40 seconds to activate the AI.
7. Wait at least five minutes for your website name to appear next to the SeaText logo. If it does not appear after 10 minutes, contact SeaText support.

Multi‑Domain Account Management

Each domain requires its own SeaText account. Create the first account, install the script, and verify activation. Repeat the process for every additional domain. Use a spreadsheet to track domain, SeaText account email, and activation status. This prevents accidental reuse of a single account across multiple sites.

Troubleshooting Common Code Injection Errors

• Script placed in FOOTER instead of HEADER – SeaText only loads from the header.
• Changes not published – the script only runs on the live, published site.
• Cache or CDN serving old HTML – clear Squarespace cache or wait for CDN propagation.
• JavaScript syntax error – ensure the copied snippet is complete and unmodified.
• Domain not using HTTPS – SeaText requires a secure connection for activation.

Real‑World Scenario: Two Domains on Different Plans

Domain A runs on a Squarespace plan that includes Code Injection. The owner creates a SeaText account, pastes the script into the header, publishes, and sees the AI activate within minutes.

Domain B runs on a plan without Code Injection. The owner cannot paste the script. They upgrade to a plan that includes Code Injection, then repeat the same installation steps. After upgrade, activation succeeds.

Both domains now have independent SeaText accounts, each tracking its own traffic and optimizations.

Limitations and Edge Cases

Development URLs such as localhost are restricted for security reasons. Dynamic development domains may not function properly because SeaText might be unable to reliably associate traffic with your account.

Each SeaText account is linked to one primary URL. You cannot manage multiple Squarespace domains from a single SeaText account. If you need SeaText on a development domain and a production domain, create separate accounts for each.

SeaText does not offer a single dashboard for multiple Squarespace sites. Every domain requires its own account and its own Code Injection setup.

FAQ

Do I need a different SeaText account for each Squarespace domain?
Yes. Each SeaText account is linked to a single primary URL. Multiple domains require separate accounts.

Will SeaText work on a Squarespace plan without Code Injection?
Not unless you upgrade. Plans that lack Code Injection cannot load the SeaText script.

How long does setup take per domain?
The actual installation takes under five minutes. Activation can take up to 10 minutes after you publish.

Can I use SeaText on a staging or development Squarespace domain?
Development URLs like localhost are restricted. Dynamic development domains may not work reliably. Use a valid, real domain for SeaText.

Does SeaText cost more for higher Squarespace plans?
SeaText pricing is separate from Squarespace pricing. Check with SeaText for current pricing details.

What if my website name does not appear after 10 minutes?
Contact SeaText support immediately. This could indicate an installation issue on your platform.

To remove a Squarespace domain from SeaText, you need to take two actions: remove the SeaText JavaScript snippet from your Squarespace site's Code Injection header, and then delete or deactivate the SeaText account associated with that domain. Because each SeaText account is linked to exactly one primary URL, this two-step process fully disconnects the domain from the platform.

How SeaText Domain Association Works

SeaText uses a one-account-per-domain model. When you install SeaText on a Squarespace site, you paste a JavaScript snippet into the Header area of the Code Injection panel. That snippet ties the live site to a specific SeaText account. The account dashboard then shows the connected domain name next to the SeaText logo once the connection is verified.

According to the integration documentation, "Each SEATEXT AI account is linked to a single primary URL" and "To use SEATEXT AI on several websites, create one account for each website." This architecture means there is no multi-domain dashboard; removal is simply the reverse of installation for that specific account.

This design matters for several reasons. First, it keeps each site's data isolated. If you run SeaText on three different domains, each has its own set of reading telemetry, A/B test results, and translation layers. Second, it prevents accidental cross-contamination where changes meant for one site affect another. Third, it makes billing and reporting straightforward: each account corresponds to one site's usage.

When you remove the snippet, the connection breaks immediately. The JavaScript no longer loads on your pages. However, the SeaText account still exists in your records. Until you delete the account, it remains in the dashboard and continues to consume your allocated usage. To fully remove SeaText from a domain, you must complete both steps.

Prerequisites Before Removal

Before you start, verify that you have the necessary access. Without the right permissions, you will not be able to complete one or both steps.

• Administrator access to the Squarespace site: You need permission to edit Code Injection settings. Only site owners and full administrators can access Developer Tools. If you are a contributor or limited editor, you cannot modify the snippet.
• Login credentials for the SeaText account: You need the email and password for the specific SeaText account tied to this domain. If you forgot the password, use the password reset function before starting.
• A published version of the site: Changes to Code Injection only take effect after you publish the site. If your site is in draft mode, publish it first.
• Confirmation of the correct domain: Double-check which domain you want to remove. If you manage multiple Squarespace sites, make sure you are editing the right one.

If you lack Squarespace admin access, contact the site owner. If you cannot access the SeaText account, contact SeaText support before attempting removal through other means.

Step-by-Step Removal Process

Follow these steps in order. Complete the Squarespace steps first, then move to the SeaText account deletion.

1. Log in to Squarespace and open the site you want to remove from SeaText.
2. Navigate to Settings. Click the three-dot menu next to the site name in the Squarespace dashboard. Select "Settings" from the dropdown menu.
3. Open Developer Tools. Scroll to the bottom of the Settings page. Click "Developer Tools" to expand the section.
4. Click Code Injection. This opens the panel where you previously pasted the SeaText snippet.
5. Find the Header field. Locate the text area labeled "Header." This is where the SeaText JavaScript snippet was inserted during installation.
6. Delete the SeaText snippet. Select the entire snippet. It typically starts with <script and contains a reference to a SeaText domain. Delete all of it. Do not leave partial code or comments behind.
7. Save the changes. Click the "Save" button in the Code Injection panel.
8. Publish the site. If the site is not already live, click "Publish" to push the changes to your visitors. The SeaText script will stop loading immediately after publication.
9. Log in to SeaText. Open a new browser tab and go to the SeaText login page. Enter the credentials for the account associated with this domain.
10. Navigate to account settings. Look for a settings, profile, or account section in the SeaText dashboard.
11. Delete or deactivate the account. Find the option to "Delete Account" or "Deactivate." Read any warnings about data loss. Confirm the action.

After confirming account deletion, SeaText immediately removes the domain from its records. Any queued processing for that domain stops. The account and all associated data are deleted permanently.

Verifying the Domain Is Disconnected

After completing the steps above, confirm the disconnection in two places to ensure the removal is complete.

Check Squarespace: Return to the Code Injection panel. Open the Header field. It should be empty or contain only unrelated code. If you see any text referencing SeaText, delete it and save again.

Check SeaText: The domain name should no longer appear next to the SeaText logo at the top of the SeaText dashboard. The integration guide notes that after installation, "Wait at least five minutes until you see your website name displayed next to the SEATEXT logo at the top of this page." The reverse is true for removal: once the account is deleted, the name disappears.

If the domain still appears after deletion, wait five minutes and refresh. If it persists, contact SeaText support. This could indicate a synchronization delay or an issue with the account deletion.

You can also test by visiting your Squarespace site in an incognito window. The page should load without the SeaText behavior you previously observed, such as dynamic content rewriting or personalization.

What Happens After Removal

Removing SeaText has concrete effects on your site and your data. Understanding these outcomes helps you decide if removal is the right step.

Content changes stop. SeaText stops rewriting, translating, or personalizing content on that domain. Your pages revert to their base state, as they appeared before SeaText was installed. Any dynamic headlines, personalized copy, or translation layers disappear.

Data is deleted. Any accumulated reading telemetry, A/B test variants, or translation layers for that domain are removed with the account. This data cannot be recovered after deletion. If you need historical reports, export them before deleting the account.

Billing stops for that domain. If you are on a per-domain pricing plan, removing the account should stop future charges for that domain. Check your billing statements to confirm.

Reinstallation requires a new account. If you later want to use SeaText on the same domain again, you must create a new SeaText account and reinstall the snippet. The old account and its history cannot be restored or linked to the new installation.

Common Mistakes to Avoid

Several errors frequently occur during the removal process. Avoiding them saves time and prevents incomplete disconnection.

• Leaving the snippet in place: If you only delete the SeaText account but keep the script on the site, the script will load but have no backend to connect to. This adds unnecessary page weight and may cause console errors. Always remove the snippet first.
• Deleting the wrong account: Since each domain has its own account, verify the domain name in the SeaText dashboard before deleting. Check that the account shows the correct URL. Deleting the wrong account does not remove SeaText from your intended domain.
• Forgetting to publish: Changes to Code Injection only take effect after you publish the Squarespace site. If you save the snippet removal but do not publish, the script continues to run.
• Not exporting data first: Account deletion is permanent. If you want to keep historical reports, export them before deleting. Once the account is gone, the data is unrecoverable.
• Skipping the verification step: After removal, confirm the disconnection in both Squarespace and SeaText. Assuming the removal worked without checking can lead to unexpected behavior later.

Limitations and Edge Cases

Some situations require special consideration or may limit what you can accomplish during removal.

Development URLs: The documentation states "Development URLs, such as localhost, are restricted for security reasons." If you were using a staging domain, the same removal steps apply, but you cannot reuse a localhost address for a new account. You must use a valid, public domain for SeaText activation.

Dynamic development domains: "Dynamic development domains may not function properly, as SEATEXT AI might be unable to reliably associate traffic with your account." Removal from such domains follows the same process but may have already been unreliable. The account deletion still works, but the underlying setup was not supported.

No bulk removal: Because each domain requires its own account, you must repeat the process for every domain you want to disconnect. There is no central "remove all" button. For agencies managing multiple clients, this means logging into each account individually.

Multiple domains on one Squarespace site: If a single Squarespace site hosts multiple domains (for example, different TLDs pointing to the same content), each domain may require its own SeaText account. In that case, repeat the removal steps for each domain's Code Injection panel and each corresponding SeaText account.

Temporary disconnection vs. permanent removal: If you want to stop SeaText temporarily without losing data, remove the snippet but keep the account active. The account remains in your dashboard without a connected domain. To resume, paste the snippet again and wait for re-verification.

Key Facts

Frequently Asked Questions

Can I keep the SeaText account but stop the script from running?

Yes. You can leave the account active and only remove the snippet from Squarespace. The account will remain in your SeaText dashboard but will show no connected domain. This is useful if you plan to reinstall on the same domain soon or want to preserve your data while taking a break.

Does removing the snippet affect my Squarespace site's performance?

Removing the snippet eliminates the external JavaScript request, which slightly reduces page weight. There is no negative impact on Squarespace functionality. Your site continues to work exactly as it did before SeaText was installed.

What if I have multiple domains under one Squarespace account?

Each domain still needs its own SeaText account. You must repeat the removal steps for each domain's specific SeaText account and each domain's Code Injection panel. There is no way to remove SeaText from multiple domains in one action.

How long does it take for SeaText to stop processing after account deletion?

Account deletion is immediate. Any queued processing for that domain stops as soon as the account is removed. The snippet on your site will no longer connect to a backend, but removing the snippet and publishing is still recommended to eliminate the unused code.

Can I transfer a SeaText account to a different domain?

No. The documentation is explicit: "Each SEATEXT AI account is linked to a single primary URL." You cannot reassign an existing account to a new domain. You must create a new account for the new domain.

Will I lose my translation history and A/B test data?

Yes. Deleting the SeaText account removes all associated data, including translations, test variants, and reading telemetry. Export any needed reports before deletion. There is no recovery option after the account is removed.

Is there a way to pause instead of delete?

The platform does not document a pause feature. The practical pause is removing the snippet while keeping the account. The script stops loading on your site, but your data remains intact. Reactivation requires repasting the snippet and waiting for re-verification.

What happens if I delete the Squarespace site but keep the SeaText account?

The SeaText account will remain active but show no connected domain. You can either delete the account manually or reuse it by installing the snippet on a new site. If the original domain is no longer available, create a new account for the new site.

Can I remove SeaText from a subdomain?

SeaText supports primary domains and subdomains, provided the domain is valid and publicly accessible. Removal follows the same steps: delete the snippet from the subdomain's Code Injection panel and delete the corresponding SeaText account.

SeaText does not support managing multiple Squarespace domains from one account. Each domain you want to optimize needs its own SeaText account, and each account is tied to one primary URL. Development URLs such as localhost are blocked for security reasons, and dynamic development domains may not work reliably. You must install the SeaText JavaScript snippet in the Code Injection header of each Squarespace site separately.

Yes, you can use SeaText on Squarespace domains that are not on the same Squarespace account. The only requirement is that each domain gets its own SeaText account, since every SeaText account is tied to one primary URL. Whether the domains live under one Squarespace login or several makes no difference to SeaText.

Why Domain‑Level Accounts Matter

SeaText treats each domain as a separate property. This design keeps data isolated. Experiments, translations, and conversion optimizations stay specific to each site. Agencies and multi‑site owners avoid cross‑contamination of analytics. Each account has its own dashboard and billing.

The one‑account‑per‑domain rule also simplifies security. The JavaScript snippet contains an identifier that binds traffic to that exact SeaText account. If you reuse a snippet on a second domain, the activation check fails because the domain does not match the registered primary URL.

How SeaText Binds to a Primary URL

When you sign up for SeaText, you provide the domain (for example, example.com) that will run the script. The SeaText dashboard then generates a unique JavaScript snippet. That snippet includes an account token tied to the primary URL you entered.

During activation, SeaText verifies that the snippet is loading on the exact domain registered. The documentation states: "Each SEATEXT AI account is linked to a single primary URL" and "To use SEATEXT AI on several websites, create one account for each website." This binding is strict. Subdomains like www.example.com count as separate primary URLs and need their own accounts.

Squarespace Account Structure vs. SeaText Account Structure

Squarespace lets you manage multiple domains under one Squarespace account or spread domains across several Squarespace accounts. SeaText does not read or enforce Squarespace‑account boundaries. It only cares that the domain where the snippet runs matches the primary URL registered in the SeaText account.

Practical implication: if you manage three client sites on three different Squarespace accounts, you create three SeaText accounts — one per domain — and install each snippet in the respective Squarespace site's Code Injection area. If you later move a domain to a different Squarespace account, the SeaText account stays valid because the domain itself has not changed.

Step‑by‑Step: Connecting a Domain From Another Squarespace Account

1. Create a new SeaText account for the target domain. During signup, enter the exact domain (e.g., client-site.com) as the primary URL.
2. Copy the JavaScript snippet from the new SeaText account's dashboard.
3. Log in to the Squarespace account that owns client-site.com.
4. Open the site's settings: click the three‑dots icon → Settings → Developer Tools → Code Injection.
5. Paste the snippet into the Header field and click Save.
6. Publish the site if it is not already live.
7. Visit the domain and stay on the page for at least 40 seconds. This triggers the activation handshake.
8. Wait up to 10 minutes for the SeaText dashboard to show the domain name next to the logo, confirming the connection.

Repeat these steps for every additional domain, regardless of which Squarespace account hosts it.

Key Restrictions and Technical Limits

• One primary URL per SeaText account. You cannot add alias domains or subdomains to the same account; each needs its own account.
• Development URLs (localhost, dynamic preview URLs) are blocked. The documentation notes: "Development URLs, such as localhost, are restricted for security reasons. Ensure you use a valid, real domain for these cases. Dynamic development domains may not function properly."
• Activation requires a live, accessible page. The 40‑second visit and 5‑10 minute propagation window are mandatory before the AI becomes active.
• Code Injection must be available. Some legacy Squarespace plans restrict Code Injection; verify the plan supports it before purchasing SeaText for that domain.
• Password‑protected sites block activation. Temporarily disable password protection during the 40‑second activation window, then re‑enable.

Practical Scenarios for Multi‑Account Setups

Agency managing client sites across multiple Squarespace accounts

Create a SeaText account for each client domain. Store each account's credentials in your password manager. Installation is identical per site; the only variable is which Squarespace login you use to reach Code Injection.

Single owner with domains split across personal and business Squarespace accounts

Same process: one SeaText account per domain. The fact that you log into different Squarespace dashboards does not change the SeaText side.

Moving a domain between Squarespace accounts

No SeaText changes needed. The domain stays the same, so the existing SeaText account continues to work after the domain transfer completes.

Running a staging subdomain

Each subdomain (e.g., staging.example.com) counts as a distinct primary URL. You must create a separate SeaText account for it. Development URLs are not supported, so the staging subdomain must be a real, publicly accessible domain.

Limitations and Workarounds

• No central dashboard. SeaText does not provide a multi‑domain dashboard; each account has its own dashboard. Agencies must log in separately for each client.
• Separate billing per account. Each SeaText account is a separate subscription. Consolidated billing is not mentioned in the source material. Check with the vendor for volume discounts.
• Primary URL is immutable. The documentation does not describe a domain‑change workflow. Assume you cannot change the primary URL after creation; create a new account for a new domain.
• Code Injection plan requirement. If a Squarespace plan disables Code Injection (some older Personal plans), you must upgrade the Squarespace plan or use a different platform.

What SeaText Actually Does for Each Domain

SeaText deploys 25 autonomous AI agents that rewrite landing‑page copy in real time, translate content into 125 languages, recover wasted ad spend from bot clicks, and feed high‑intent signals to Google and Meta bidding algorithms. Each agent runs from the same JavaScript snippet you install via Code Injection.

The one‑account‑per‑domain model keeps data isolated per site. Experiments, translations, and conversion‑rate optimizations stay specific to each property. This isolation matters when you run different campaigns, languages, or product lines on different domains.

Limitation: you must manage separate logins and billing for each domain. There is no central agency dashboard in the current product.

Frequently Asked Questions

Can I use one SeaText account for a main domain and its www subdomain?

No. The primary URL is an exact match. example.com and www.example.com are treated as separate primary URLs, so each needs its own SeaText account.

Does SeaText charge per account or per domain?

Pricing is per SeaText account, which maps 1:1 to a domain. Check the current pricing page for volume discounts if you manage many domains.

What happens if I paste the wrong domain's snippet into a site?

The activation check will fail. The SeaText dashboard will not show the domain as connected after 10 minutes, and the AI will remain inert.

Can I transfer a SeaText account to a different domain later?

The documentation does not describe a domain‑change workflow. Assume the primary URL is immutable; create a new account for the new domain.

Do I need separate billing for each SeaText account?

Yes. Each account is a separate subscription. Consolidated billing is not mentioned in the source material.

Will SeaText work if the Squarespace site is password‑protected?

Password protection blocks the activation visit. Temporarily disable it during the 40‑second activation window, then re‑enable.

Decision Checklist Before You Begin

• List every domain that will run SeaText.
• Confirm each domain is on a Squarespace plan with Code Injection access.
• Create a SeaText account for each domain using the exact live URL.
• Install each snippet in the correct Squarespace site's Header injection.
• Run the activation visit for each domain and verify the dashboard shows "connected."

The One-Account-Per-Domain Requirement

SeaText is designed to associate its AI agents with a specific, verified primary URL. Because of this, you cannot use a single SeaText account to manage multiple Squarespace domains. If you operate several websites, you must create and maintain a unique SeaText account for every individual domain you wish to optimize. This rule applies whether the domains are completely different brands, sub-brands, or a development domain paired with a production domain. The SeaText integration page states clearly: "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 AI account is linked to a single primary URL." [S1]

Why the One-Account-Per-Domain Rule Exists

The requirement exists for technical and security reasons. SeaText AI agents rely on visitor telemetry, conversion tracking, and keyword intent matching that are tied to a single domain's traffic profile. If one account served multiple domains, the AI would mix visitor behavior data from different sites. This cross-contamination would cause the AI to optimize content for Site A using patterns learned from Site B, leading to irrelevant translations, mismatched personalization, and inaccurate A/B test results. The platform also uses the primary URL as a security boundary to prevent unauthorized domains from injecting scripts into an account. By enforcing a one-to-one link, SeaText ensures that each AI agent only sees traffic, conversions, and search intent from its own verified domain. [S1]

Step-by-Step Setup Process for Each Domain

Repeat the following steps for every domain you want to connect. You must have a SeaText account ready before you start; the integration page notes you need an account before you can install the script. [S1]

1. Create a Unique Account: Visit the SeaText registration page and create a new account specifically for the domain you are currently setting up. Use an email alias or naming convention that identifies the domain (e.g., seatext-example-com@yourcompany.com).
2. Access Squarespace Settings: Log in to your Squarespace dashboard for the target site. Click the three dots icon and select Settings. [S1]
3. Navigate to Developer Tools: Scroll to the bottom of the settings menu and select Developer Tools. This section is located at the very end of the page. [S1]
4. Open Code Injection: Click on Code Injection to open the area where you can add custom scripts. [S1]
5. Install the Snippet: Copy the JavaScript code provided in your specific SeaText account dashboard and paste it into the Header section. Click Save. The integration page instructs: "Paste the provided JavaScript Code snippet into the designated HEADER area. Once the code has been successfully pasted, click on 'Save' to preserve your changes." [S1]
6. Publish Your Site: Ensure your website is published so the changes take effect. The integration page reminds: "Ensure that your website is published to apply the changes made." [S1]

Note: If the Code Injection option is missing, verify that your Squarespace plan includes Developer Tools. Some lower-tier plans restrict code injection. Upgrade or contact Squarespace support if needed.

Verification and Activation

Once the code is installed, you must trigger the initial handshake between your site and the SeaText platform. The integration page provides exact steps: [S1]

• Visit or refresh your live website several times.
• Stay on the page for at least 40 seconds to allow the AI to activate and link to your account.
• Wait at least five minutes. Check your SeaText dashboard; you should see your website name displayed next to the SeaText logo at the top of the page.

If you do not see your website name after 10 minutes, contact the SeaText support team for assistance. The integration page warns: "If you do not see it at the top of the page after 10 minutes, please contact our support team immediately. This could indicate an issue during the installation on your platform, and you may need our assistance." [S1]

Important Security and Domain Restrictions

SeaText requires a valid, real domain for all installations. Development URLs, such as localhost, are restricted for security reasons. Dynamic or temporary development domains may fail to function because the AI cannot reliably associate the traffic with your account. The integration page states: "Development URLs, such as localhost, are restricted for security reasons. Ensure you use a valid, real domain for these cases. Dynamic development domains may not function properly, as SEATEXT AI might be unable to reliably associate traffic with your account." [S1] Always use your production-ready domain for the integration. If you need a staging environment, use a real subdomain (e.g., staging.example.com) that resolves publicly and create a separate SeaText account for it.

Best Practices for Multi-Domain Setup

Managing many accounts requires organization. Follow these practices:

• Naming convention: Include the domain name in the account email or account nickname (e.g., seatext-shop-example-com).
• Central credential store: Use a password manager with tags for each domain. Store the SeaText dashboard URL, API keys, and the Squarespace site URL together.
• Separate dev and prod: Create distinct accounts for staging.example.com and example.com. Never share a snippet between them.
• Document the snippet: Save a copy of each domain's JavaScript snippet in your internal wiki. Snippets are unique per account; copying the wrong one will break activation.
• Schedule activations: Activate domains one at a time. Verify each in the dashboard before moving to the next to avoid confusion.

Cost and Billing Implications of Multiple Accounts

Each SeaText account carries its own subscription. The source pack does not publish multi-account pricing or volume discounts. You should check with the vendor for any available multi-site plans or enterprise agreements. Budget for one subscription per domain. If you manage ten domains, you will have ten separate billing cycles unless a custom contract is negotiated. Keep receipts and renewal dates in your central credential store to avoid accidental lapses.

Managing Multiple SeaText Accounts Efficiently

Log in to each account individually; there is no unified dashboard. To reduce context switching:

• Use browser profiles or containers (e.g., Firefox Multi-Account Containers) to stay logged into several accounts simultaneously.
• Bookmark each account's dashboard with a clear label.
• Set up email forwarding from each account's notification address to a single inbox, then filter by domain.
• Assign a team member as owner for each domain to distribute monitoring workload.

Common Installation Issues and Fixes

• Snippet not appearing in page source: Confirm you pasted into the Header field, not Footer. Ensure you clicked Save and then Published the site in Squarespace.
• Dashboard shows no website name after 10 minutes: Clear browser cache, revisit the live site, stay 40 seconds, wait another 5 minutes. If still missing, contact support with the domain and account email. [S1]
• Code Injection missing in Squarespace: Your plan may not include Developer Tools. Upgrade to a Business or Commerce plan, or use a third-party injection method if allowed.
• Mixed content warnings: Ensure your site uses HTTPS. SeaText snippet loads over HTTPS; HTTP sites may block it.
• Wrong domain activated: You may have pasted a snippet from Account A into Domain B. Verify the snippet matches the account you are checking.

How to Switch or Remove a Domain from SeaText

To move a domain to a different SeaText account, delete the snippet from the old domain's Code Injection, then follow the setup steps with the new account. To retire a domain entirely, remove the snippet from Squarespace and cancel the associated SeaText subscription. Deleting the SeaText account will erase all historical data, translations, and A/B test results for that domain. Export any reports you need before cancellation.

Frequently Asked Questions

Can I use one login for multiple sites?

No. Each SeaText account is tied to one primary URL. You must create a separate account for every domain. [S1]

What happens if I use a development domain?

Development domains like localhost are restricted. The AI will not function correctly, and you may face issues with traffic association. Use a real, publicly resolvable domain instead. [S1]

How long does activation take?

After installing the code and visiting your site, it typically takes about five minutes for the connection to appear in your dashboard. Wait up to 10 minutes before contacting support. [S1]

Does this affect my Squarespace plan?

You must ensure your Squarespace plan allows for Code Injection. This is required to place the SeaText JavaScript snippet in the header. [S1]

What if my site doesn't appear in the dashboard?

If you have waited more than 10 minutes after the initial activation steps, reach out to the SeaText support team to investigate potential installation issues. [S1]

Can I transfer an account to a different domain?

No. The account is permanently bound to its primary URL. To use SeaText on a new domain, create a new account and install its snippet on the new domain.

What happens if I delete an account?

Deleting an account removes all data, translations, test history, and settings for that domain. The action is irreversible. Export reports first.

Are there any discounts for multiple accounts?

The public pricing page does not list multi-account discounts. Check with the vendor for enterprise or volume pricing options.

Can I use the same email for multiple accounts?

SeaText's registration system may allow the same email with different aliases (e.g., user+site1@example.com, user+site2@example.com). Check the sign-up form for alias support.

Do I need to re-verify after a domain migration?

Yes. If you change the primary domain (e.g., from old.com to new.com), you must create a new SeaText account for the new domain and install its snippet. The old account remains bound to the old URL.

Managing SeaText across multiple Squarespace sites requires a per-domain account strategy. Because each SeaText instance binds to a specific origin for security, you must maintain separate accounts for each URL. This guide covers the technical architecture, installation, and management workflows for scaling your SEO and CRO efforts.

Why Centralize Your SEO Strategy with SeaText?

Managing multiple Squarespace sites often leads to fragmented SEO efforts.

Using SeaText across domains adds a consistent automated layer that works in the background of every site.

Whether you run e‑commerce stores or content‑heavy blogs, SeaText provides the same optimization tools.

These tools include real‑time landing page rewrites and bot traffic detection.

The primary benefit is the ability to scale conversion rate optimization and SEO without manual intervention.

Because SeaText agents operate autonomously, every visitor receives a personalized experience that matches their search intent.

How SeaText Handles Multiple Domains

SeaText is designed to associate its AI intelligence with specific web traffic.

To maintain the integrity of this data, each SeaText account is strictly linked to a single primary URL.

This architecture ensures that AI agents such as the Google Ads Landing Page Agent or the Bot Refund Agent can accurately track, analyze, and optimize traffic for that domain.

If you manage multiple domains, you must create a separate SeaText account for each one.

This separation prevents data cross‑contamination and ensures that AI parameters configured for one site do not affect another.

Key Considerations for Multi‑Site Management

Technical Architecture of SeaText

SeaText consists of a cloud‑based AI engine and a lightweight JavaScript snippet.

The snippet is loaded in the page header and remains inert until activation.

When a visitor loads the page, the snippet reads URL parameters and initiates a secure WebSocket to the SeaText backend.

The backend selects the appropriate autonomous agent based on the visitor’s source, keyword, or behavior.

Agents execute in isolated containers, ensuring no cross‑talk between accounts.

Each container maintains its own state, models, and logs tied to the primary URL of its account.

This design guarantees that data from one domain never leaks into another’s processing pipeline.

Benefits of Multi‑Account Management for Data Integrity

Separate accounts enforce a one‑to‑one mapping between a domain and its AI model.

Traffic metrics, conversion events, and bot detection results are stored per account.

Isolating data prevents aggregation errors that could skew performance reports.

When you adjust parameters for one site, the change applies only to that account’s agents.

This reduces the risk of unintended side effects across your portfolio.

Administrators can audit each account independently, simplifying compliance and troubleshooting.

Deep Dive into Autonomous Agents Across Domains

SeaText deploys up to 25 autonomous AI agents that operate in real time.

Agents include the Google Ads Landing Page AI, Bot Refund Agent, Conversion Relay (CAPI), and Intent Amplifier.

Each agent receives input from the JavaScript snippet: URL, referrer, UTM tags, and on‑page behavior.

Based on this input, the agent rewrites copy, adjusts bids, or flags invalid clicks within milliseconds.

Because agents run per account, the Google Ads Landing Page AI for site A uses only site A’s keyword data.

Site B’s agent works with its own keyword set, preventing cross‑contamination of intent signals.

This isolation improves relevance and leads to higher quality scores and lower bounce rates.

How It Works: JavaScript Snippet, Squarespace Code Injection, AI Activation

First, copy the unique SeaText JavaScript snippet from your account dashboard.

In Squarespace, go to Settings → Developer Tools → Code Injection.

Paste the snippet into the Header field and save.

Publish the site to make the snippet live on all pages.

Visit the site several times and stay on a page for at least 40 seconds.

This dwell time triggers the AI activation handshake with the SeaText backend.

After activation, the backend returns a token that links the snippet to your account.

You should see your website name appear next to the SeaText logo within five to ten minutes.

If the name does not appear after ten minutes, contact SeaText support for assistance.

Strategic Advantages of Isolating SEO Data per Domain vs Risks of Data Cross‑Contamination

Isolating SEO data per domain ensures that each site’s performance metrics reflect its true audience.

Search intent, keyword performance, and conversion funnels remain distinct.

This clarity enables precise budget allocation and targeted optimizations.

Conversely, pooling data from multiple domains risks cross‑contamination.

Bot traffic from one site could inflate conversion rates for another, masking real issues.

Keyword signals may bleed, causing agents to apply irrelevant rewrites.

Such bleed can degrade user experience and waste ad spend.

Maintaining separate accounts eliminates these risks and preserves data fidelity.

The Importance of Proper Installation

For SeaText to function across your Squarespace domains, you must follow the installation process for each site individually.

Navigate to your Squarespace dashboard, go to Settings, then Developer Tools, and finally Code Injection.

Paste your unique SeaText JavaScript snippet into the HEADER area and save your changes.

After installation, visit your website several times and remain on the page for at least 40 seconds.

This triggers the AI to activate and link to your account.

You should see your website name appear next to the SeaText logo within five to ten minutes, confirming the connection is live.

Why Ignoring Multi‑Site Optimization Matters

If you optimize only one of your Squarespace domains, you leave your other properties vulnerable to the same issues you are solving elsewhere.

High bounce rates, bot‑driven ad spend waste, and generic landing pages that fail to convert persist on untouched sites.

By applying SeaText to all your domains, you ensure that your entire digital footprint benefits from automated SEO and conversion agents.

This holistic approach maximizes your return on ad spend across the board.

Limitations and Best Practices

SeaText is not a one‑size‑fits‑all dashboard for multiple sites; you cannot manage multiple domains from a single login.

Avoid using dynamic or local development domains like localhost for your SeaText integration.

The AI requires a stable, real‑world domain to reliably associate traffic and provide accurate optimization.

If you attempt to use a non‑standard domain, the AI may fail to link, resulting in inactive agents.

Troubleshooting steps:

• Verify that the JavaScript snippet is placed in the Header, not the Footer.
• Check that the site is published; unpublished preview pages block the activation handshake.
• Confirm that you have visited the site and stayed for at least 40 seconds after each load.
• Open the browser console and look for errors related to the SeaText script; a 404 or CORS issue indicates a copy‑paste mistake.
• If the website name does not appear after ten minutes, deactivate the snippet, clear browser cache, reinstall, and repeat the activation wait.
• Should the problem persist, contact SeaText support with your account ID, domain, and a screenshot of the console.

Best practices include:

• Maintain a spreadsheet linking each Squarespace domain to its SeaText account ID and subscription status.
• Schedule a monthly review of agent logs to detect any unexpected behavior.
• Use the same naming convention for accounts (e.g., client‑name‑domain) to simplify administration.
• Never share snippet code between accounts; each snippet contains a unique token tied to its primary URL.
• Keep your Squarespace plan active; expired sites prevent the snippet from loading.

Frequently Asked Questions

Can I manage all my Squarespace sites from one SeaText dashboard?

No. Each SeaText account is linked to a single primary URL. You must maintain separate accounts for each domain you wish to optimize.

What happens if I use a development domain?

Development URLs like localhost are restricted for security reasons. SeaText requires a valid, real domain to function correctly.

How do I know if my site is connected?

After installing the snippet and visiting your site, wait about five to ten minutes. If your website name appears next to the SeaText logo at the top of your account page, it is successfully connected.

Does each account require a separate subscription?

Yes, because each domain requires its own SeaText account to ensure accurate traffic tracking and AI performance, you should plan for individual account management for each site.

What should I do if the AI fails to link after the 10‑minute window?

Follow the troubleshooting steps: verify snippet placement, confirm site publication, ensure 40‑second dwell, check console for errors, clear cache, reinstall, and if still unsuccessful, contact SeaText support with your account details.