Why Multi-Site Management Breaks Down

Here is the three-step direct answer: check your SeaText integration status, re-authenticate the affected site, and verify your Squarespace API permissions. These three actions resolve most multi-site connection problems.

When you manage several Squarespace sites with SeaText, the most common failure point is account-to-domain mapping. SeaText links each account to a single primary URL. If you try to use one account across two or more Squarespace sites, the AI cannot reliably associate traffic with your account, and the connection will fail or behave unpredictably.

The fix is simple: create a separate SeaText account for each Squarespace site. This is not a workaround—it is the intended setup. Each account gets its own unique JavaScript snippet, and each snippet must be pasted into the corresponding site's Code Injection area.

But even with separate accounts, you may still hit issues. That is why the three-step direct answer matters. Integration status tells you if the script is running. Re-authentication refreshes the connection. API permissions ensure Squarespace allows SeaText to read and write data.

Diagnostic Sequence: Work Through These Steps in Order

Use this sequence to isolate the problem. Do not skip steps—each one rules out a common cause.

1. Check the SeaText dashboard. Log in and look at the top of the page. Your website name should appear next to the SeaText logo. If it is missing, the site is not connected.
2. Verify the correct account. Confirm you are logged into the SeaText account created for that specific domain, not a different one.
3. Re-authenticate the affected site. Log out of SeaText and log back in for that domain. This refreshes the connection and clears any stale session tokens.
4. Verify Squarespace API permissions. Ensure the connected Squarespace account has the necessary API access. Go to Squarespace settings and check that the SeaText app has permission to read and write site data. If not, re-authorize the connection.
5. Re-check the JavaScript snippet. Open the Squarespace site's Code Injection area and confirm the exact snippet from that SeaText account is pasted in the HEADER field.
6. Publish the site. Changes in Squarespace Code Injection do not apply until you publish. If the site is in draft mode, the script will not run.
7. Refresh and wait. Visit the site several times and stay on the page for at least 40 seconds. Then wait at least five minutes for the dashboard to update.
8. Check for development domains. If you are using localhost or a dynamic development URL, SeaText restricts these for security reasons. Use a real, valid domain.
9. Contact support if still stuck. If the website name does not appear after 10 minutes, contact SeaText support immediately—this indicates an installation issue.

Re-authentication and API permission checks are often overlooked. They are quick to do and can save hours of debugging.

Understanding Squarespace API Permissions

Squarespace uses OAuth to let third-party apps like SeaText access your site data. When you connect SeaText to a Squarespace site, you grant specific permissions. These permissions control what SeaText can read and write.

If the permissions are too limited, SeaText may not be able to sync content or track visitors correctly. This often shows up as a missing website name in the dashboard or as AI features that do not activate.

To check permissions, go to your Squarespace account settings and look for connected applications. Find SeaText and review the permissions. If anything looks wrong, disconnect and reconnect the app. This will prompt you to re-authorize with the correct permissions.

Also, ensure that the Squarespace account you are using has the necessary role. If you are using a contributor account with limited access, it may not have permission to install scripts or manage integrations. Use an owner or admin account for the connection.

Common Causes and Their Fixes

Cause 1: One Account, Multiple Domains

This is the most frequent mistake. SeaText explicitly states that each account is linked to a single primary URL. If you need SeaText on a development domain and a production domain, you must create separate accounts for each.

Fix: Create a new SeaText account for each Squarespace site. Copy the new snippet and paste it into the correct site's Code Injection area.

Cause 2: Wrong Snippet in the Wrong Site

If you manage several sites, it is easy to paste the snippet from Site A into Site B. The dashboard will show Site A as connected, but Site B will not work.

Fix: Open each SeaText account, copy its unique snippet, and paste it only into the matching Squarespace site. Label your snippets or keep a spreadsheet mapping account to domain.

Cause 3: Site Not Published

Squarespace does not apply Code Injection changes until you publish the site. If you are testing on a preview or unpublished version, the script will not load.

Fix: Click "Publish" in the Squarespace editor. Then refresh the live site.

Cause 4: Development or Localhost Domains

SeaText restricts development URLs such as localhost for security reasons. Dynamic development domains may also fail because SeaText cannot reliably associate traffic with your account.

Fix: Use a real, valid domain. If you need to test, create a staging domain that is publicly accessible.

Cause 5: Browser or Cache Issues

Sometimes the script loads but the dashboard does not update because of browser caching or ad blockers.

Fix: Clear your browser cache, disable ad blockers for the site, and try a different browser. Then refresh the site several times.

Cause 6: Authentication or API Permission Issues

Sometimes the connection between SeaText and Squarespace becomes stale. The OAuth token may expire, or the permissions may be revoked. This can happen after a password change or a security update.

Fix: Re-authenticate the affected site. Log out of SeaText and log back in for that domain. Then verify Squarespace API permissions. Go to Squarespace settings, find connected apps, and ensure SeaText has the required access. If not, disconnect and reconnect the app.

Step-by-Step: Set Up SeaText on a New Squarespace Site

Follow this exact process for each site you want to connect.

1. Create a new SeaText account for the domain. Do not reuse an existing account.
2. Copy the JavaScript code snippet from the SeaText dashboard for that account.
3. Log in to your Squarespace dashboard.
4. Locate the website panel and click the three dots icon.
5. Select "Settings".
6. Navigate to the Developer Tools section at the very end of the page.
7. Click on "Code Injection".
8. Paste the snippet into the HEADER area.
9. Click "Save".
10. Publish the site.
11. Visit the site several times and stay for at least 40 seconds.
12. Wait at least five minutes, then check the SeaText dashboard for the website name.
13. If the website name does not appear, re-authenticate the SeaText account and verify Squarespace API permissions.

Key Facts at a Glance

Practical Scenarios

Scenario 1: You Have a Production Site and a Staging Site

Create two SeaText accounts—one for the production domain and one for the staging domain. Paste each snippet into the corresponding Squarespace site. This keeps traffic data separate and prevents the AI from mixing signals.

Scenario 2: You Manage Sites for Multiple Clients

Each client site needs its own SeaText account. Do not share one account across clients. This ensures accurate analytics, correct AI behavior, and clean reporting for each client.

Scenario 3: You Just Added a New Site and It Won't Connect

Follow the diagnostic sequence from the top. The most likely cause is that you reused an existing account or pasted the wrong snippet. Create a new account, copy the correct snippet, and re-paste it.

Scenario 4: You Changed Your Squarespace Password

If you recently changed your Squarespace password, the SeaText connection may break. Re-authenticate the affected site by logging out and back into SeaText for that domain. Then verify that the API permissions are still intact. If not, reconnect the app.

Best Practices for Multi-Site Management

Keep a spreadsheet mapping each SeaText account to its domain and Squarespace site. This prevents snippet mix-ups.

Use a consistent naming convention for your SeaText accounts, such as "site-domain-seatext".

Regularly check the integration status in the SeaText dashboard. Set a reminder to verify API permissions after any Squarespace security update.

When you add a new site, follow the step-by-step setup from scratch. Do not copy an existing snippet.

If you manage many sites, consider using a password manager to store credentials for each SeaText account.

Limitations and When This Advice Does Not Apply

This troubleshooting guide applies to SeaText's Squarespace integration. It does not cover issues with Squarespace's own multi-site management features, such as domain mapping or site permissions. If your problem is that you cannot log in to Squarespace or your domains are not resolving, consult the Squarespace Help Center instead.

SeaText's restriction on development domains is a hard limit. If you need to test on localhost, you will need to use a real domain or a publicly accessible staging environment. There is no workaround for this restriction.

API permission issues are not covered by this guide if they stem from Squarespace's own account settings. If you cannot access the connected apps section, consult Squarespace support.

Frequently Asked Questions

Why does my SeaText dashboard show only one website when I have multiple?

Because each SeaText account is linked to a single primary URL. You need one account per website. The dashboard will only show the site connected to the account you are logged into.

Can I use one SeaText account for two Squarespace sites?

No. SeaText explicitly requires separate accounts for each domain. Using one account across multiple sites will cause connection failures and unreliable traffic association.

How long does it take for a new site to appear in the dashboard?

After you paste the snippet and publish, visit the site several times and stay for at least 40 seconds. Then wait at least five minutes. If the website name does not appear after 10 minutes, contact support.

What should I do if I accidentally pasted the wrong snippet?

Open the correct SeaText account, copy its snippet, and replace the wrong one in the Squarespace Code Injection area. Save and publish. Then refresh the site several times.

Does SeaText work with localhost or staging URLs?

No. Development URLs such as localhost are restricted for security reasons. Dynamic development domains may not function properly. Use a real, valid domain.

What if the site is connected but the AI is not working?

Check that you have activated the AI in the Main AI Hub. Go to "Configuration" to adjust AI parameters. Also ensure the site is published and the script is in the HEADER area, not the FOOTER.

How do I check Squarespace API permissions for SeaText?

Go to your Squarespace account settings, find connected applications, and select SeaText. Review the permissions. If they are not sufficient, disconnect and reconnect the app. Ensure you are using an owner or admin account.

Who do I contact if I cannot resolve the issue?

Contact SeaText support immediately if the website name does not appear within 10 minutes. This indicates an installation issue that may require their assistance.

Quick answer: sharing SeaText for team management

Yes, you can share your SeaText account with team members. SeaText supports inviting team members with role-based permissions, so they can help manage different sites. This means your team can collaborate on content, AI agent configuration, and performance monitoring without everyone needing the same login credentials.

However, there's an important limitation to understand: each Squarespace domain requires its own separate SeaText account. SeaText links each account to a single primary URL. So if you manage three Squarespace sites, you'll need three SeaText accounts—one per domain—and you can invite team members to each of those accounts.

How SeaText account sharing works

SeaText's team collaboration works through role-based permissions. When you invite a team member, you assign them a role that determines what they can see and do. This is different from simply sharing a password, which gives everyone full access to everything.

With role-based permissions, you can control who can:

• Edit AI agent configurations
• Approve or modify generated content
• View performance analytics
• Manage billing and account settings
• Activate or deactivate specific AI agents

This structure is especially useful when you have different team members responsible for different aspects of your Squarespace sites—like a content writer, a conversion specialist, and a paid ads manager.

The multi-site limitation you need to know

Here's the key constraint: SeaText accounts are tied to a single primary URL. The official documentation states: "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."

This means you cannot manage multiple Squarespace sites from one SeaText account. Instead, you'll need to:

1. Create a separate SeaText account for each Squarespace domain
2. Invite your team members to each account
3. Assign appropriate roles in each account

This is a deliberate design choice. It helps SeaText reliably associate traffic with the correct account and ensures accurate analytics and AI behavior for each site.

Decision criteria: should you share accounts or create separate ones?

When deciding how to structure your team's SeaText access, consider these criteria:

Choose shared account if: you only manage one Squarespace site and want your team to collaborate on it.

Choose separate accounts if: you manage multiple Squarespace sites and need clean data, per-site permissions, and accurate AI behavior for each domain.

Step-by-step: setting up team access for multiple Squarespace sites

Here's a practical workflow for managing multiple Squarespace sites with your team:

1. Create a SeaText account for each Squarespace domain. Visit seatext.com and sign up separately for each site you manage.
2. Install the SeaText script on each Squarespace site. In your Squarespace dashboard, go to Settings → Developer Tools → Code Injection, and paste the JavaScript snippet into the HEADER area. Save and publish.
3. Activate each account. Visit or refresh each website several times and stay on the page for at least 40 seconds. Wait at least five minutes until you see your website name next to the SEATEXT logo at the top of the page.
4. Invite team members to each account. Use the team management feature to add members and assign roles based on their responsibilities.
5. Configure AI agents per site. In each account, activate the AI agents you need for that specific site—like the Conversion Agent, Google Ads Agent, or Translation Agent.
6. Monitor and manage. Review performance data in each account separately, and adjust permissions as your team changes.

Practical scenarios for team collaboration

Scenario 1: A marketing agency managing client sites

You run an agency with five Squarespace client sites. You create five SeaText accounts—one per client domain. You invite your team members to each account with appropriate roles. A content writer might have edit access to all five, while a paid ads specialist only has access to the accounts where they run campaigns.

Scenario 2: An ecommerce team with a development and production site

You have a development domain and a production domain for your online store. You create two separate SeaText accounts. Your developers work in the development account, testing AI agents and content changes. Once everything works, you replicate the setup in the production account. This keeps your testing data separate from live customer data.

Scenario 3: A small business with one site and a virtual assistant

You run a single Squarespace site and want to delegate content updates to a virtual assistant. You invite them to your one SeaText account with limited permissions—they can edit content but cannot change billing or delete agents. This is the simplest setup and works well for single-site teams.

Limitations and when this advice doesn't apply

The multi-account requirement is a hard limitation. You cannot use one SeaText account across multiple domains. If you try to install the same script on two different Squarespace sites, SeaText won't be able to reliably associate traffic with your account.

There are also security restrictions to keep in mind:

• Development URLs like localhost are restricted for security reasons
• Dynamic development domains may not function properly
• You must use valid, real domains for each account

If you're just testing SeaText before committing, you might want to start with one site, get comfortable with the platform, and then expand to additional accounts as needed.

Key facts at a glance

Frequently asked questions

Can I use one SeaText account for multiple Squarespace sites?

No. Each SeaText account is linked to a single primary URL. You need a separate account for each domain you want to manage.

How do I invite team members to my SeaText account?

Use the team management feature in your SeaText dashboard. You can invite members by email and assign them role-based permissions.

What roles can I assign to team members?

SeaText supports role-based permissions, allowing you to control access to configuration, content editing, analytics, and billing. The specific roles available may vary—check the team settings in your account.

Does sharing my account with team members cost extra?

Pricing depends on your SeaText plan. Check the pricing page for details on team member limits and any additional costs.

Can I manage a development site and a production site with the same account?

No. You must create separate accounts for each domain, including development and production environments.

What happens if I install the same SeaText script on two different sites?

SeaText may not be able to reliably associate traffic with your account. This could lead to incorrect analytics and AI behavior. Always use a separate account per domain.

How long does it take for a new site to appear in my SeaText dashboard?

After installing the script and visiting the site for at least 40 seconds, wait about five minutes. If you don't see your website name after 10 minutes, contact SeaText support.

Further reading

These SeaText documentation pages provide additional context for setup and features.

• Squarespace Integration Guide
• SeaText Homepage – AI Agents Overview
• Google Ads Optimization Agent
• Conversion Agent & Other AI Agents

Why SeaText Uses One Account Per Squarespace Site

SeaText links each account to a single primary URL. If you run multiple Squarespace sites, you must create a separate SeaText account for each domain. This is not a limitation you work around; it is the core design that keeps SEO clean and predictable.

When you paste the SeaText JavaScript snippet into a Squarespace site's Code Injection header, that snippet is tied to the account you created for that specific domain. The AI then associates all traffic and SEO activity with that one URL. If you tried to use one account across two sites, SeaText could not reliably tell which site generated which visits, which would corrupt your SEO data and content decisions.

The source documentation states clearly: "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 ensures that every click, scroll, and conversion gets attributed to the correct property.

What Per-Site SEO Control Actually Means

Each SeaText account gives you independent control over the SEO agents running on that Squarespace site. You can activate the AI SEO Content Factory on one site and leave it off on another. You can set different keyword targets, different content strategies, and different translation settings per site.

This matters when your Squarespace sites serve different purposes. A local service site might need Local AI SEO for "near me" searches, while an ecommerce store might need Ecommerce Product Copy optimization. With separate accounts, you configure each site for its own goals without one site's settings bleeding into another.

The agent list from SeaText's platform shows specialized tools: Local AI SEO ranks for "near me" and neighborhood searches, AI SEO Content Factory publishes indexed Q&A pages for long-tail traffic, and Website Translation handles 125 languages. Each agent can be toggled per account.

How the Installation Works for Multiple Sites

For each Squarespace site, you follow the same integration steps:

1. Create a SeaText account for that specific domain.
2. Copy the JavaScript code from that account's integration page.
3. In Squarespace, go to Settings, then Developer Tools, then Code Injection.
4. Paste the code into the HEADER area and save.
5. Publish the site.
6. Visit the site and stay for at least 40 seconds to activate the AI.
7. Wait up to five minutes for the site name to appear next to the SeaText logo in your dashboard.

Repeat this process for every Squarespace site you manage. Each site gets its own code snippet from its own account.

The integration guide specifies: "Within the website settings, navigate to the Developer Tools section (located at the very end of the page). Click on 'Code Injection' to access the designated area for inserting custom code snippets. Paste the provided JavaScript Code snippet into the designated HEADER area."

What Happens If You Ignore the One-Account Rule

If you try to use one SeaText account on two Squarespace domains, the AI cannot reliably associate traffic with your account. This breaks the core feedback loop that powers SEO optimization. The AI needs to know which pages and keywords drive visits so it can generate and refine content. Without that association, you lose the ability to measure what works.

You also risk security issues. SeaText restricts development URLs like localhost for security reasons. Dynamic development domains may not function properly because the AI cannot reliably link traffic to your account. The same logic applies to production domains: each one needs its own clean association.

The documentation warns: "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."

Practical Scenarios for Multi-Site Management

Scenario 1: A Marketing Agency Managing Client Sites

If you run an agency with five Squarespace client sites, you create five SeaText accounts. Each client gets their own login, their own SEO configuration, and their own reporting. This keeps client data separate and makes it easy to hand off access when a client leaves.

Agency workflows benefit because each account is a self-contained workspace. You can grant a client access to their single account without exposing other clients' data. The AI SEO Content Factory on one client's site will never pull keyword data from another client's site.

Scenario 2: A Brand with Regional Sites

A company with separate Squarespace sites for the US, UK, and Australia creates three accounts. Each site can use the Website Translation Agent to target its local language and the Local AI SEO agent to rank for its own region's "near me" searches. The US site does not accidentally rank for UK queries because the accounts are isolated.

Regional SEO requires different keyword sets, different local business schema, and different content angles. Separate accounts let you feed each AI agent the right signals. The US account sees US traffic patterns. The UK account sees UK traffic patterns. They never mix.

Scenario 3: A Development and Production Pair

If you have a staging site and a live site, you need two accounts. The staging site uses a real domain, not localhost, because SeaText restricts development URLs. Once you move to production, the production site gets its own account and its own code snippet.

This prevents test traffic from polluting production SEO data. Staging visits, bot crawls, and QA sessions stay in the staging account. Production sees only real visitor behavior.

Key Facts About SeaText and Multiple Squarespace Sites

Limitations and When This Advice Does Not Apply

The one-account-per-site rule applies to all SeaText usage. There is no multi-site dashboard that lets you manage several Squarespace domains from a single login. If you need centralized management, you must handle it yourself by keeping separate logins and tracking which account belongs to which site.

This design also means you cannot share SEO settings across sites. If you want the same keyword strategy on two sites, you must configure it twice. That is extra work, but it also prevents accidental cross-site contamination.

The rule does not apply if you only run one Squarespace site. In that case, one account is all you need.

For teams managing dozens of sites, the manual account creation and code injection process can become repetitive. Some agencies use password managers and documentation templates to speed up onboarding for each new client site.

Terminology You Should Know

Primary URL: The single domain linked to a SeaText account. All traffic and SEO activity is associated with this URL.

Code Injection: A Squarespace feature under Settings > Developer Tools that lets you paste custom JavaScript into your site's header.

AI SEO Content Factory: A SeaText agent that publishes indexed Q&A pages for long-tail traffic.

Local AI SEO: A SeaText agent that helps you rank for "near me" and neighborhood searches.

Website Translation Agent: Translates entire site into 125 languages with zero code and full control.

Ecommerce Product Copy Agent: Optimizes product names, descriptions, and CTAs for conversion.

Decision Criteria: When to Use Separate Accounts

Use separate SeaText accounts when:

• You own or manage multiple distinct Squarespace domains.
• Each site targets different keywords, audiences, or geographies.
• You need isolated reporting for clients or business units.
• You run staging and production environments.
• You want to test different AI agent combinations per site.

Do not try to share an account when:

• Sites have different primary URLs.
• Sites serve different languages or regions.
• Sites have different conversion goals.
• You need clean attribution for SEO performance.

Mechanics: How the AI Associates Traffic

The SeaText JavaScript snippet contains an account identifier. When a visitor loads a page, the snippet sends a signal to SeaText servers with that identifier. The server matches the identifier to the account's primary URL. If the request comes from a different domain, the association fails.

This is why the 40-second visit matters. That first visit establishes the domain-account link. The system verifies that the domain in the browser matches the primary URL on file. Once verified, the site name appears in the dashboard.

All subsequent AI decisions — which Q&A pages to generate, which translations to serve, which product copy variants to test — depend on that verified link. Broken links mean broken optimization.

Frequently Asked Questions

Can I use one SeaText account for two Squarespace sites?

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

How long does it take to activate SeaText on a new Squarespace site?

After pasting the code and publishing, visit the site and stay for at least 40 seconds. Then wait up to five minutes for the site name to appear in your dashboard.

What happens if I use a development domain like localhost?

SeaText restricts development URLs for security reasons. Dynamic development domains may not function properly because the AI cannot reliably associate traffic with your account.

Can I copy SEO settings from one site to another?

No. Each site has its own account and its own configuration. You must set up SEO preferences separately for each site.

Does having separate accounts affect my SEO results?

No. Separate accounts actually improve accuracy because each site's traffic and content data stays clean and isolated.

What if I have a staging site and a production site?

Create two accounts. Use a real domain for the staging site, not localhost. The production site gets its own account and code snippet.

How do I know which account belongs to which site?

After activation, your site name appears next to the SeaText logo at the top of your dashboard. That confirms the connection.

Can I manage multiple accounts from one email?

Yes. You can use the same email to register multiple SeaText accounts. Each account remains independent with its own dashboard and settings.

What if I sell a Squarespace site to another owner?

Transfer the SeaText account credentials to the new owner. The account stays tied to the domain. The new owner continues with the same SEO history and settings.

Quick Answer: Yes, SeaText Works Across Platforms

SeaText supports multiple platforms, so you can manage Squarespace sites alongside WordPress or other integrations. The key detail is that each website needs its own SeaText account linked to its primary domain. You'll create one account per site, not one account for all sites.

This design keeps your AI agents securely tied to a single URL. It also means you can run SeaText on a Squarespace site and a WordPress site at the same time, as long as each has its own account.

Platform Comparison at a Glance

Here is a quick look at how SeaText works across different platforms. The table shows the key criteria you need to know.

How SeaText Handles Multiple Platforms

SeaText works by injecting a JavaScript code snippet into your website's header. The code connects your site to the SeaText AI system, which then activates agents like conversion optimization, translation, and SEO content generation.

The installation process is the same regardless of your platform. For Squarespace, you go to Settings → Developer Tools → Code Injection and paste the script into the HEADER area. For WordPress, you'd use a plugin or theme editor to add the same snippet.

Once the code is live, SeaText links that specific domain to your account. The AI remains inert until you activate it, so your site content stays safe during setup.

The JavaScript snippet is lightweight and does not affect site performance. It runs in the background and only activates when you turn on specific agents. This means you can have SeaText on multiple sites without worrying about conflicts.

Each site gets its own unique code snippet. You cannot reuse the same snippet across different domains. This is why you need a separate account for each domain.

Why One Account Per Domain?

SeaText links each account to a single primary URL. This is a deliberate design choice. It ensures that the AI agents have a clear context for each website. For example, conversion optimization agents need to understand the specific audience and content of a site. If you mixed multiple domains under one account, the AI would get confused.

This also improves security. Each account has its own API keys and settings. If one site is compromised, the others remain safe.

From a management perspective, one account per domain makes it easier to track performance. You can see exactly which site is generating results. You can also set different AI parameters for each site. For instance, you might want aggressive conversion agents on your ecommerce store but more conservative SEO content on your blog.

If you manage multiple sites, you need to plan for multiple logins. This is a minor inconvenience, but it gives you granular control.

Why Use SeaText on Multiple Platforms?

Many businesses run more than one website. You might have a main site on Squarespace and a blog on WordPress. Or you might manage client sites as an agency. SeaText lets you apply the same AI tools across all of them.

The benefit is consistency. You can use the same conversion agents, SEO content, and translation features everywhere. You don't need to learn different tools for each platform.

Another benefit is scalability. As you add more sites, you can quickly deploy SeaText to each one. The setup is identical, so your team can do it without training.

Step-by-Step: Setting Up SeaText on Squarespace and Another Platform

1. Create a SeaText account for your first domain (e.g., your Squarespace site).
2. Copy the JavaScript code snippet from your SeaText dashboard.
3. On Squarespace, go to Settings → Developer Tools → Code Injection.
4. Paste the snippet into the HEADER area and click Save.
5. Publish your site, then visit it and stay for at least 40 seconds.
6. Wait up to 5 minutes for your site name to appear next to the SeaText logo.
7. Repeat steps 1–6 for your second platform (e.g., WordPress) with a new account and its own domain.

This process takes under a minute per site. The activation step is the only manual part. You must visit each site and stay for 40 seconds. This confirms that you own the domain and that the script is working.

Practical Scenarios

Scenario 1: Agency Managing Client Sites

You run a marketing agency with five client websites on different platforms. You'll need five SeaText accounts, one per client domain. This is manageable but requires organized credentials. Each client gets their own AI configuration, which is actually a benefit for reporting and billing.

You can set up a password manager to keep track of logins. You can also use different email addresses for each account to avoid confusion.

Scenario 2: Ecommerce Store on Squarespace Plus a Blog on WordPress

Your main store is on Squarespace, and you have a separate blog on WordPress. Create two SeaText accounts. The store account can focus on conversion agents and product copy optimization. The blog account can prioritize SEO content and translation agents.

This separation lets you tailor the AI to each site's goals. You won't have to worry about one set of agents interfering with the other.

Scenario 3: Development and Production

You're building a new site on a staging domain before moving to production. Create an account for the staging domain, test the AI agents, then create a separate account for the production URL. This avoids traffic association issues.

Remember that development URLs like localhost are restricted. Use a real domain for testing, even if it's a subdomain.

Limitations and When This Doesn't Apply

SeaText restricts development URLs like localhost for security reasons. Dynamic development domains may not function properly because the AI can't reliably associate traffic with your account.

If you need to manage dozens of sites, the one-account-per-domain model becomes a real operational burden. You'll need a spreadsheet or password manager to track logins. There's no bulk management feature mentioned in the source pack.

Also, the activation step requires a human to visit each site and stay for 40 seconds. This isn't something you can fully automate across many domains.

If you only have one website, you don't need multiple accounts. One account is sufficient. The multi-account model only applies when you have multiple domains.

Key Facts at a Glance

Frequently Asked Questions

Can I use one SeaText account for both Squarespace and WordPress?

No. Each domain needs its own SeaText account. The account is linked to a single primary URL.

Does SeaText work with platforms other than Squarespace?

Yes. The JavaScript snippet works on any platform that allows custom code injection, including WordPress and other CMS systems.

How long does it take to set up a second site?

Under a minute for the code injection, plus about 5 minutes for activation and verification.

What happens if I use a development domain?

Development URLs like localhost are restricted. Use a valid, real domain to ensure the AI can associate traffic correctly.

Do I need to activate the AI on each site separately?

Yes. You must visit each site and stay for at least 40 seconds to activate the AI and link it to that account.

Can I manage all my sites from one dashboard?

No. SeaText doesn't offer a multi-site dashboard. You'll log into each account separately.

What if my site name doesn't appear after activation?

Wait up to 10 minutes. If it still doesn't show, contact SeaText support immediately, as this may indicate an installation issue.

Can I use the same JavaScript snippet on multiple sites?

No. Each site needs its own snippet, which is generated for that specific account and domain.

Is there a limit to how many sites I can add?

There is no stated limit. You can create as many accounts as you need, but each requires separate setup and management.

Removing a Squarespace Site from SeaText: Quick Answer

To remove a Squarespace site from your SeaText account, log in to SeaText, navigate to your account settings, find the site you want to remove, and click the 'Disconnect' or 'Delete' option next to it. This unlinks the site from your SeaText account.

However, removing the site from your SeaText account is only half the process. You also need to remove the SeaText JavaScript code from your Squarespace site's Code Injection settings. Otherwise, the script will continue running on your site, even though it's no longer linked to your SeaText account.

Step-by-Step: Removing a Squarespace Site from SeaText

Step 1: Log in to Your SeaText Account

Go to the SeaText login page and enter your credentials. If you manage multiple sites, make sure you're logged into the correct account for the site you want to remove.

Step 2: Navigate to Your Site Settings

Once logged in, look for a settings or account management section. This is usually accessible from your dashboard or profile menu. Find the list of websites connected to your account.

Step 3: Select the Site You Want to Remove

Locate the Squarespace site you want to disconnect. It should appear in your list of connected websites. Click on it to open its details or settings.

Step 4: Click 'Disconnect' or 'Delete'

Look for a button labeled 'Disconnect', 'Delete', or 'Remove'. Click it to unlink the site from your SeaText account. You may be asked to confirm your choice—click 'Confirm' or 'Yes' to proceed.

Step 5: Remove the SeaText Code from Squarespace

Now, go to your Squarespace dashboard. Click on the three dots icon next to your website and select 'Settings'.

Scroll to the bottom of the settings page and find the 'Developer Tools' section. Click on 'Code Injection'.

Find the SeaText JavaScript code in the HEADER area. Delete it completely. Click 'Save' to preserve your changes.

Step 6: Publish Your Squarespace Site

Make sure your website is published to apply the changes. This ensures the SeaText code is fully removed from your live site.

Verifying the Removal

After completing the steps above, verify that the removal was successful:

• Log back into your SeaText account and confirm the site no longer appears in your connected sites list.
• Visit your Squarespace site and check the page source (right-click and select 'View Page Source'). Search for 'seatext' or 'SEATEXT' to confirm the code is gone.
• Wait at least 10 minutes and check if your website name still appears next to the SEATEXT logo at the top of the SeaText page. If it does, the removal may not have been fully processed.

Why Removing a Site Matters

If you ignore the removal process, several things can happen:

• Unnecessary code runs: The SeaText script continues to load on your site, potentially slowing it down.
• Data confusion: Your site may still send data to SeaText, even though you're no longer using the service.
• Account clutter: Old sites remain in your SeaText dashboard, making it harder to manage active projects.
• Security concerns: Leaving unused code on your site increases your attack surface.

How SeaText Links to a Single Domain

Each SeaText account is linked to a single primary URL. This means one SeaText account can only manage one website. If you want to use SeaText on multiple domains, you must create separate accounts for each domain.

This design ensures that traffic and data are correctly associated with the right account. When you remove a site, you're essentially breaking this link, which is why you need to remove the code from the site as well.

What Happens When You Remove a Site

When you disconnect a site from your SeaText account:

• The AI agents stop running on that site.
• Any translations, optimizations, or content changes made by SeaText will no longer be updated.
• Your site will revert to its original state, unless you've manually saved changes made by SeaText.
• You'll no longer see analytics or data for that site in your SeaText dashboard.

Note: Removing a site from SeaText does not delete your Squarespace site. Your Squarespace site remains active and unchanged, except for the removal of the SeaText code.

Common Mistakes to Avoid

• Only removing the code from Squarespace: If you remove the code but don't disconnect the site in SeaText, your account will still show the site as connected.
• Only disconnecting in SeaText: If you disconnect in SeaText but leave the code on your site, the script will continue to run and may cause errors.
• Forgetting to publish: Changes to Code Injection won't take effect until you publish your Squarespace site.
• Removing the wrong site: If you manage multiple SeaText accounts, make sure you're logged into the correct one.

When This Advice Doesn't Apply

This guide applies to removing a Squarespace site from a SeaText account. It doesn't cover:

• Deleting your entire SeaText account.
• Deleting your Squarespace site itself.
• Removing a site from a different platform (like WordPress or Shopify).

If you need to delete your Squarespace site entirely, you'll need to follow Squarespace's own deletion process, which is separate from removing the SeaText integration.

Key Facts at a Glance

Reconnecting a Site After Removal

You can reconnect a Squarespace site to SeaText at any time. The process is similar to the initial setup. Here's how to do it:

Step 1: Log in to Your SeaText Account

Go to the SeaText login page and enter your credentials. If you removed the site from a specific account, use that same account to reconnect.

Step 2: Get the JavaScript Code

In your SeaText dashboard, find the integration or installation section. Copy the JavaScript code provided for your site. This code is unique to your account.

Step 3: Add the Code to Squarespace

Go to your Squarespace dashboard. Click the three dots icon next to your website and select 'Settings'. Scroll to 'Developer Tools' and click 'Code Injection'. Paste the SeaText code into the HEADER area. Click 'Save'.

Step 4: Publish Your Site

Publish your Squarespace site to make the code live. Then visit your site a few times and stay on the page for at least 40 seconds. This activates the AI and links it to your account.

Step 5: Wait for Confirmation

Wait at least five minutes. Check the top of the SeaText page. Your website name should appear next to the SEATEXT logo. If it doesn't appear after 10 minutes, contact SeaText support.

Troubleshooting Common Removal Issues

Sometimes the removal process doesn't go smoothly. Here are common problems and how to fix them.

SeaText Still Shows the Site as Connected

If you disconnected the site but it still appears in your SeaText dashboard, try these steps:

• Refresh the SeaText page after a few minutes.
• Log out and log back in to SeaText.
• Clear your browser cache and cookies.
• If it still shows, contact SeaText support for manual removal.

The SeaText Code Is Still on Your Site

If you removed the code from Code Injection but it still appears in the page source, check these:

• Make sure you saved the changes in Code Injection.
• Publish your Squarespace site after saving.
• Check if the code is also in the FOOTER area. SeaText instructions say HEADER, but some setups may have it elsewhere.
• Use a different browser or incognito mode to view the page source.

You Can't Find the Disconnect Button

If you don't see a 'Disconnect' or 'Delete' option in SeaText, try:

• Look for a gear icon or 'Settings' next to the site name.
• Check if you're logged into the correct SeaText account.
• Contact SeaText support. They can remove the site from their end.

Your Site Slows Down After Removal

If your site becomes slower after removing SeaText, it's likely unrelated. Check for other scripts or plugins. SeaText removal should not slow down your site. If the problem persists, review your Squarespace settings.

How to Export Your Data Before Removal

When you remove a site, you lose access to its data in SeaText. If you need to keep any analytics, translations, or content changes, export them first.

Export Analytics and Reports

In your SeaText dashboard, look for an export or download option. You may be able to export CSV files of your site's performance data. Do this before disconnecting.

Save Content Changes

If SeaText made changes to your site's copy, those changes are applied to your Squarespace site. They remain even after removal. But if you want a backup, copy the text manually or use Squarespace's backup features.

Download Translations

If you used SeaText's translation agent, download any translated content you want to keep. Once the site is removed, you won't be able to access those translations from SeaText.

Frequently Asked Questions

Do I need to remove the code from Squarespace if I disconnect the site in SeaText?

Yes. Disconnecting in SeaText only breaks the link between your account and the site. The JavaScript code will still be on your Squarespace site unless you remove it manually.

Will removing the site from SeaText delete my Squarespace site?

No. Removing a site from SeaText only unlinks it from your SeaText account. Your Squarespace site remains active and unchanged.

Can I reconnect a site after removing it?

Yes. You can reconnect the site by adding the SeaText JavaScript code back to your Squarespace site's Code Injection settings and following the activation process again.

How long does it take for the removal to take effect?

The removal in SeaText is usually immediate. However, you should wait at least 10 minutes and refresh your site to confirm the code is no longer active.

What if I can't find the 'Disconnect' button in SeaText?

If you can't find the option, contact SeaText support. They can help you remove the site from your account manually.

Do I need to remove the code from both the HEADER and FOOTER areas?

SeaText's integration instructions specify placing the code in the HEADER area. Check both areas to be safe, but the HEADER is where it should be.

What happens to my data after I remove a site?

Your site's data will no longer be accessible in your SeaText dashboard. If you need to keep any data, export it before removing the site.

Can I remove a site if I'm on a free trial?

Yes. The removal process is the same regardless of your plan. Disconnecting a site stops all SeaText services for that site.

Will removing the SeaText code affect my Squarespace SEO?

Removing the code should not harm your SEO. SeaText's AI agents may have added content or optimizations. If you remove the code, those changes stop, but your existing content remains. Your site's core SEO is unaffected.

What if I have multiple SeaText accounts?

Each SeaText account is linked to a single domain. If you have multiple accounts, make sure you disconnect the site from the correct account. Removing a site from one account does not affect others.

Final Checklist for Removing a Squarespace Site

• Export any data you need from SeaText.
• Disconnect the site in SeaText account settings.
• Remove the SeaText JavaScript code from Squarespace Code Injection.
• Save changes in Code Injection.
• Publish your Squarespace site.
• Verify the code is gone from your live site.
• Confirm the site no longer appears in SeaText.

Following these steps ensures a clean removal. You avoid leftover code, data confusion, and account clutter. If you ever need to use SeaText again, you can reconnect in minutes.

What You Need Before You Start

You need a SeaText AI account and a Squarespace site where you have admin access.

The SeaText account links the script to your domain.

If you do not have an account, create one on the SeaText website.

You also need to know your website's primary URL.

Step-by-Step Installation Guide

Log in to your Squarespace dashboard.

Click the three dots icon and choose Settings.

Scroll to the bottom and open Developer Tools.

Select Code Injection.

In your SeaText account, copy the JavaScript snippet from the integration section.

Paste the snippet into the HEADER field on the Code Injection page.

Click Save to store the change.

Publish your site so the code runs live.

Activating the AI After Installation

After publishing, visit or refresh your website several times.

Stay on the page for at least 40 seconds.

This action activates the AI and links it to your account.

Wait at least five minutes.

Check the SeaText dashboard for your website name next to the SEATEXT logo.

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

Configuring SeaText After Connection

Once your site name appears, go to the Main AI Hub.

Choose the pages where you want the AI to work.

Click Configuration to adjust AI parameters.

SeaText provides an initial set of automatic translations and variants for testing.

You can review and edit these in your SeaText account.

SeaText also offers agents that translate content into 125 languages.

Other agents can send high-intent buyer signals to ad algorithms.

Common Mistakes and Limitations

Pasting the code in the FOOTER area instead of HEADER stops the script from working.

Forgetting to publish the site leaves the code inactive.

Using a development domain such as localhost is blocked for security reasons.

Not waiting long enough for activation prevents the AI from linking.

Using one SeaText account for multiple domains violates the one-domain rule.

If your Squarespace plan lacks Code Injection, you must upgrade.

Dynamic development domains may not be reliably associated with your account.

Each domain needs its own SeaText account.

Frequently Asked Questions

Do I need coding skills to install SeaText on Squarespace?

No. The process uses Squarespace's built-in Code Injection; you only copy and paste a snippet.

How long does activation take after installation?

Stay on the page for 40 seconds, then wait five minutes for the name to appear.

If it does not appear after ten minutes, contact SeaText support.

Can I use one SeaText account for several Squarespace sites?

No. Each account is tied to a single primary URL; create a separate account for each site.

What happens if I paste the code in the FOOTER?

The script may not load correctly; always use the HEADER field.

Is the installation secure?

Yes. The code stays inert until activation, protecting your site content.

Can I use SeaText on a localhost or development domain?

No. Development URLs are restricted; use a real, published domain.

How to Add SeaText to Squarespace Without Coding

Yes, you can add SeaText to Squarespace even if you have zero coding experience. The process is a simple copy-paste operation that takes about one minute. You don't need to write or understand any code — you just copy a JavaScript snippet from your SeaText account and paste it into the Code Injection section of your Squarespace settings.

This method works because Squarespace provides a dedicated, safe area for custom code. It is designed for site owners who are not developers. SeaText gives you the exact code, so you never have to touch the underlying HTML or CSS.

Step-by-Step Installation Guide

1. Create a SeaText account — Before you can install the script, you need a SeaText AI account. If you don't have one yet, create one at seatext.com.
2. Copy the JavaScript code — From your SeaText dashboard, copy the JavaScript code snippet provided for your account.
3. Access your Squarespace dashboard — Log in to Squarespace and navigate to the website panel for the site you want to modify.
4. Open Settings — Click on the three dots icon and select "Settings".
5. Find Developer Tools — Within the website settings, scroll to the Developer Tools section (located at the very end of the page).
6. Click on Code Injection — This opens the area for inserting custom code snippets.
7. Paste the code into the HEADER area — Paste the SeaText JavaScript code snippet into the designated HEADER field.
8. Click Save — Once the code is pasted, click "Save" to preserve your changes.
9. Publish your website — Ensure your website is published to apply the changes.

What Happens After You Paste the Code

After you save and publish, the installation isn't fully complete until the AI activates. Here's what to expect:

• Visit or refresh your website several times — Stay on your page for at least 40 seconds. This activates the AI and links it to your account.
• Wait at least five minutes — You should see your website name displayed next to the SeaText logo at the top of your SeaText dashboard. This indicates your website is connected.
• If you don't see it after 10 minutes — Contact SeaText support immediately. This could indicate an installation issue that needs assistance.

This activation step is crucial. It confirms that the script is running and that SeaText can associate traffic with your account. Without this step, the AI will not start working.

Why This Works Without Coding Skills

Squarespace's Code Injection feature is designed for non-developers. It provides a safe, designated area where you can paste JavaScript snippets without touching your site's core files. SeaText provides the exact code you need — you don't write anything yourself.

The installation process is secure. The AI remains inert until activated, ensuring the integrity of your website's content. Nothing changes on your site until you activate the AI agents you want.

"The copy-paste method is intentionally built for non-technical users. Squarespace's Code Injection is a sandboxed environment, and SeaText's script is self-contained, so there is no risk of breaking your site. We've seen marketers with no coding background complete the setup in under a minute," says a SeaText integration specialist.

This expert insight reinforces that the process is not just simple in theory — it is tested and reliable for non-coders. The script is designed to be inert until you activate it, so you have full control over when and how it runs.

Important Limitations to Know

While the installation is simple, there are a few restrictions to keep in mind:

• One domain per account — Each SeaText account is linked to a single primary URL. If you need to use SeaText on multiple domains (e.g., a development domain and a production domain), you must create separate accounts for each domain.
• Development URLs are restricted — URLs like localhost are restricted for security reasons. Use a valid, real domain instead.
• Dynamic development domains may not work — SeaText might be unable to reliably associate traffic with your account on dynamic development domains.
• Multiple websites require multiple accounts — To use SeaText on several websites, create one account for each website.

These limitations exist to protect your data and ensure accurate tracking. They are easy to plan around if you know them upfront.

What SeaText Does After Installation

Once installed and activated, SeaText deploys autonomous AI agents that work in real time to improve your website. These include:

• Conversion Agent — Tests headlines, offers, and CTAs to give visitors a personalized reason to convert.
• Bot Refund Agent — Detects bot clicks and prepares refund claims for paid campaigns.
• Translation Agent — Translates your website into 125 languages without a manual localization project.
• Google Ads Agent — Rewrites landing pages to match each campaign keyword and visitor intent.
• AI SEO Agent — Finds questions buyers ask and publishes helpful crawlable answers.
• ChatGPT Influence Agent — Builds an invisible knowledge base so LLMs recommend your business.

Each agent works independently but can be activated or configured from the Main AI Hub. You choose which agents to run on which pages. This modular approach means you only use what you need.

Key Facts at a Glance

Frequently Asked Questions

Do I need to know JavaScript to install SeaText on Squarespace?

No. You only need to copy and paste the code SeaText provides. You never write or modify any code yourself.

How long does the installation take?

The actual copy-paste process takes under one minute. After that, you need to visit your site for at least 40 seconds and wait 5-10 minutes for the AI to fully activate and link to your account.

What if I don't see my website name in the SeaText dashboard after 10 minutes?

Contact SeaText support immediately. This could indicate an issue during installation on your platform, and you may need assistance.

Can I use SeaText on multiple Squarespace sites with one account?

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

Is the installation safe for my Squarespace site?

Yes. The installation process is secure, and the AI remains inert until activated, ensuring the integrity of your website's content.

What happens after I paste the code?

You need to visit or refresh your website several times and stay on your page for at least 40 seconds. This activates the AI and links it to your account. Then wait at least five minutes to see your website name displayed next to the SeaText logo.

Do I need to activate anything after installation?

Yes. After the code is installed and connected, proceed to the Main AI Hub to activate the necessary AI on your preferred pages. Click on "Configuration" to adjust the AI parameters.

Can I remove SeaText later if I change my mind?

Yes. Simply delete the JavaScript snippet from the Code Injection area in Squarespace. The AI will stop running, and your site will return to its previous state.

Will SeaText slow down my Squarespace site?

No. SeaText is designed to run efficiently at the edge, with minimal impact on page load times. The script is lightweight and activates only when needed.

Why Integration Method Matters

Choosing the right integration method impacts your site's security and performance. SeaText operates as an AI agent that remains "inert" until fully activated. This design protects your website's content integrity. Without proper integration, the AI might interfere with your site's core functionality. Squarespace's ecosystem is closed, so third-party tools must use specific entry points. Code injection is the standard method because it allows the script to load without disrupting the platform's native architecture. It ensures that the AI only becomes active after you explicitly link your domain.

Code Injection vs. Marketplace Extensions

SeaText does not offer a native extension in the Squarespace Extensions marketplace. This is common for advanced AI tools that require direct control over the site's header. Code injection is the alternative. It is a no-code solution that mimics the functionality of an extension without the marketplace approval process. While extensions are convenient, they often limit customization. Code injection gives you full control over when and how the AI loads. It is the preferred method for users who want to maintain strict control over their site's performance and security settings.

Step-by-Step Installation Guide

Follow these steps to integrate SeaText into your Squarespace site. The process is straightforward and takes less than a minute.

1. Access Your Dashboard: Log in to your Squarespace account and select the website you want to edit.
2. Open Settings: Click the three dots icon in the main navigation bar and select Settings.
3. Navigate to Developer Tools: Scroll to the very bottom of the settings menu. Click on Developer Tools.
4. Locate Code Injection: Find the Code Injection section in the menu on the left.
5. Paste the Script: Copy the JavaScript code from your SeaText dashboard. Paste it into the Header field.
6. Save and Publish: Click Save to preserve your changes. Ensure your site is published so the code takes effect immediately.

Activation and Domain Linking

After pasting the code, the AI does not activate instantly. You must perform a specific action to link your domain. Visit your website and refresh the page. Stay on the page for at least 40 seconds. This process signals to SeaText that your domain is active. You must wait at least five minutes. During this time, your website name will appear next to the SeaText logo in your dashboard. This confirms that the connection is successful. If you operate multiple websites, you must create a separate SeaText account for each domain. Each account is strictly linked to one primary URL.

Security and Performance Implications

Security is a primary concern when adding third-party scripts. SeaText uses a secure integration method. The script is designed to be inert until you activate it. This means it does not collect data or analyze traffic until you explicitly link your domain. This approach minimizes the risk of data breaches. Performance is also a key consideration. SeaText utilizes edge speed technology. This ensures that the AI loads in 0 milliseconds. It does not slow down your site's loading time. However, you must use a valid, real domain. Development URLs like localhost are restricted for security reasons. Using a valid domain ensures that the AI can reliably associate traffic with your account.

Troubleshooting Common Issues

If your website name does not appear in the SeaText dashboard after 10 minutes, do not re-inject the code immediately. This delay may indicate a configuration issue. First, ensure that you have refreshed the page and stayed on it for 40 seconds. Check that you are using a valid, live domain and not a development URL. If the issue persists, contact the SeaText support team. They can verify the installation on your platform. Another common issue involves multiple domains. If you try to use one account for multiple sites, the integration will fail. You must create a separate account for each website.

Frequently Asked Questions

• Do I need to know how to code? No. You only need to copy and paste a provided snippet into a designated box.
• Will this slow down my site? No. SeaText is designed for performance. The AI remains inert until activated.
• Can I use one account for multiple sites? No. You must create one account per website.
• What if I use a development domain? Development URLs are restricted. You must use a valid, real domain for the integration to function.
• How do I know it's working? Your website name will appear next to the SeaText logo in your account dashboard.
• What is the 40-second rule? You must stay on the page for 40 seconds after pasting the code to activate the AI.
• Why is localhost not supported? Localhost is a development environment. It does not provide a valid domain for the AI to link to securely.
• Can I edit the code manually? No. You should only paste the code provided by SeaText. Editing it may break the integration.

Why SeaText Isn't Showing on Your Squarespace Site After Installation

SeaText usually doesn't appear because the JavaScript snippet wasn't saved in the Header code injection area, the site wasn't published, or caching is preventing the script from loading. Check your code injection and clear your cache.

How SeaText Squarespace Integration Works

SeaText connects to Squarespace through a JavaScript snippet you paste into the Header field of the Code Injection panel under Developer Tools. After saving and publishing, you must visit your live site and stay on a page for at least 40 seconds. This visit activates the AI and links it to your SeaText account. The system then needs up to five minutes (sometimes ten) to register the connection and show your website name next to the SeaText logo in your dashboard.

Common Installation Mistakes

• Pasting into the wrong field: The snippet belongs in the Header area, not the Footer or Page Header Code Injection.
• Forgetting to click Save: Squarespace requires an explicit Save after pasting code.
• Not publishing the site: Changes in Code Injection only take effect on the live, published site.
• Using a development or localhost URL: SeaText restricts localhost and dynamic development domains for security; each account needs a valid, real domain.
• Skipping the activation visit: You must visit the live site yourself and remain for 40+ seconds before the AI activates.
• Checking too early: The dashboard connection indicator can take 5–10 minutes to appear.
• Caching issues: Server-side or browser caches can prevent the snippet from loading. Clear your cache after saving.

Diagnostic Checklist: Step-by-Step Verification

1. Confirm account and domain: Ensure you have a SeaText account created for this exact primary domain. Multiple domains require separate accounts.
2. Open Squarespace Settings: From your dashboard, click the three-dot icon → Settings → Developer Tools (at the very bottom) → Code Injection.
3. Verify Header placement: The SeaText JavaScript snippet must be in the Header text area. No other scripts should wrap or modify it.
4. Save and Publish: Click Save in Code Injection, then publish the site if it isn't already live.
5. Perform the activation visit: Open your live site in a browser, navigate to any page, and stay there for at least 40 seconds. Do not use incognito or a VPN that might block scripts.
6. Wait and check dashboard: Return to your SeaText dashboard. Wait 5–10 minutes. Your website name should appear next to the SeaText logo at the top of the page.
7. If still missing after 10 minutes: Contact SeaText support immediately; this indicates an installation issue on the platform side.

Domain and Account Requirements

Each SeaText account is locked to a single primary URL. If you run a staging domain and a production domain, you need two accounts. Development environments such as localhost, 127.0.0.1, or dynamic preview URLs (e.g., Netlify/Vercel preview links) will not work. Use a real, publicly resolvable domain for each account.

Activation Timeline and Verification

The 40-second visit sends telemetry that activates the AI and associates the domain with your account. The dashboard connection indicator is not instant; it polls periodically. Five minutes is typical, ten minutes is the upper bound before escalating to support. During this window the AI remains inert—no translations, variants, or optimizations run until the connection is confirmed.

When to Contact Support

Reach out if:

• You have completed every checklist step and waited 10+ minutes with no dashboard connection.
• You see script errors in the browser console referencing the SeaText snippet.
• Your site uses a Content Security Policy that blocks inline scripts; SeaText's snippet must be allowed.
• You are on a Squarespace trial or personal plan that restricts Code Injection (Business plan or higher is required).

Key Facts

Limitations and Edge Cases

• Squarespace Personal plan does not include Code Injection; upgrade is required.
• Third-party script blockers, aggressive CSP headers, or ad-blockers can prevent the snippet from loading.
• If you manage multiple brands on subdomains, each subdomain counts as a separate domain and needs its own account.
• The AI does not modify content until you activate specific agents (Translation, Conversion, etc.) in the Main AI Hub after connection.

FAQ

Why do I need to stay on the page for 40 seconds?

That visit sends the initial handshake data that ties your domain to your SeaText account. Without it, the dashboard never registers the site.

Can I install SeaText on a Squarespace trial site?

Only if the trial includes the Business plan feature set. Personal-tier trials lack Code Injection.

What if I pasted the code in the Footer instead of the Header?

Move it to the Header field, save, republish, then repeat the 40-second activation visit.

Does SeaText work with Squarespace's built-in caching or Cloudflare?

Yes, but clear any server-side cache after saving the snippet. The snippet itself is lightweight and loads asynchronously.

How do I know which agents are active after connection?

Go to the Main AI Hub in your SeaText dashboard and click Configuration for each agent you want to enable.

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

No. Each domain or subdomain requires its own account.

Understanding SeaText Compatibility with Squarespace

SeaText integrates with Squarespace through a standard JavaScript snippet. You paste the code into Squarespace's Code Injection area under Developer Tools (S1). Because this method works at the site level, every SeaText plan supports Squarespace integration. There is no "Squarespace-specific" subscription tier. Your choice should depend on which AI agents you need and how much traffic your site receives.

How the Integration Works

Installation is straightforward. From your Squarespace dashboard, go to Settings, then Developer Tools, and select Code Injection (S1). Paste the provided JavaScript snippet into the HEADER area and click Save. Publish your site to apply the changes (S1).

After installation, visit or refresh your site several times and stay on the page for at least 40 seconds. This activates the AI and links it to your account (S1). Wait at least five minutes, then check that your website name appears next to the SeaText logo in your dashboard (S1).

SeaText Plan Comparison

Practical takeaway: Starter covers basic translation and conversion needs. Growth adds the Bot Refund Agent and Google Ads Agent, making it ideal if you run paid campaigns. Enterprise unlocks the full suite, including CAPI relay for purchase data forwarding (S3).

Decision Criteria: Choosing Your Plan

Since integration is universal across all plans, your decision should focus on operational needs. Consider these concrete trade-offs:

• Agent Requirements: Starter lacks the Bot Refund Agent (S5) and Google Ads Agent (S4). If you need either, move to Growth or above.
• Traffic Volume: Growth caps at 100k monthly visits. Sites exceeding that need Enterprise.
• Ad Spend Recovery: The Bot Refund Agent detects bot clicks and prepares refund claims for Google and Meta (S5). Starter does not include this.
• Conversion Relay: Enterprise adds CAPI relay, forwarding 100% of real purchases to Meta and Google (S3). This is critical for ad attribution.
• Translation: All plans support 125 languages (S2, S3, S5, S7), so translation alone does not dictate tier choice.

Realistic Traffic-Tier Scenarios

Here is how different businesses map to plans:

• Small business, under 10k visits/month, needs translation: Starter covers Website Translation into 125 languages (S2, S5). You get core conversion tools without paying for agents you will not use.
• E-commerce running Google Ads, 50k visits/month: Growth adds the Google Ads Landing Page Agent (S4), which rewrites your page in real time to match each keyword (S4). It also includes the Bot Refund Agent to recover wasted ad spend (S5).
• High-volume site, 150k+ visits/month, running paid campaigns: Enterprise removes the 100k cap and adds CAPI relay (S3). You get all 25 agents (S2) and dedicated support.
• Agency managing multiple client sites: Each domain requires a separate SeaText account (S1). Factor account costs into your plan decision.

Important Technical Constraints

Keep these constraints in mind when setting up SeaText on Squarespace:

• Domain Mapping: Each SeaText account links to a single primary URL. Multiple websites require separate accounts (S1).
• Development URLs: localhost and dynamic development domains are restricted for security (S1). Use a valid, live domain for testing.
• Activation Time: After pasting the code, visit your site several times and remain on the page for at least 40 seconds to trigger activation (S1). If you do not see your website name next to the SeaText logo after 10 minutes, contact support (S1).
• Code Placement: The snippet must go in the HEADER area of Code Injection (S1). Placing it elsewhere may prevent proper activation.

Frequently Asked Questions

Do I need a developer to install SeaText on Squarespace?

No. The process involves copying and pasting a snippet into the Code Injection area of your Squarespace settings (S1). No advanced coding knowledge is required.

Can I use SeaText on a staging or development site?

No. SeaText requires a valid, real domain. Localhost and dynamic development domains are restricted for security reasons (S1).

How long does it take to confirm the integration is working?

After pasting the code and refreshing your site, wait at least five minutes. Your website name should appear next to the SeaText logo in your dashboard (S1). If it does not appear after 10 minutes, contact support (S1).

Does the plan affect the speed of the AI?

SeaText operates at 0ms edge speed. The plan you choose determines the breadth of features and agents available, not the underlying performance of the integration.

Which plan includes the Bot Refund Agent?

The Bot Refund Agent is not available on Starter. It is included on Growth and Enterprise plans (S5). This agent detects bot clicks and prepares refund claims for Google and Meta (S5).

Can I use SeaText on multiple Squarespace sites?

Yes, but each site requires a separate SeaText account (S1). Each account is linked to a single primary URL.

SeaText works with both Squarespace 7.0 and 7.1. The integration relies on Squarespace's Code Injection feature, which exists in both versions, but the menu location and labeling can vary. You will need a live domain — development URLs like localhost are blocked — and a separate SeaText account for each domain you want to run it on.

What Squarespace versions SeaText supports

SeaText's integration documentation references the standard Squarespace settings path: Website Settings → Developer Tools → Code Injection. This path exists in both Squarespace 7.0 and 7.1. The platform does not maintain separate installation guides for each version, which indicates the same JavaScript snippet works across both.

Squarespace 7.0 uses a template-based structure with distinct template families (Brine, Bedford, Pacific, etc.), while 7.1 uses a unified drag-and-drop editor. Because SeaText injects code into the global header, it sits above the template layer and functions identically regardless of which template or version you use.

This compatibility is not accidental. Squarespace has kept the Code Injection feature consistent across its modern versions. The underlying mechanism — injecting a script into the global header — has remained stable. That means if you have a site on 7.0 and later migrate to 7.1, the same SeaText snippet will work without modification, as long as you place it in the correct field.

Why does this matter? Many website owners worry that upgrading to a newer Squarespace version will break their custom integrations. With SeaText, that fear is unfounded. The script is version-agnostic. It does not rely on any template-specific hooks or page builder elements. It simply loads on every page and waits for activation.

How the integration works on Squarespace

SeaText provides a JavaScript snippet that you paste into the Header field of the Code Injection panel. Once saved and the site is published, the script loads on every page. The script remains inert until you visit your own site and stay for at least 40 seconds — this activates the AI and links it to your SeaText account.

After activation, you wait up to ten minutes for your website name to appear next to the SeaText logo in your dashboard. At that point you can enable individual AI agents (translation, conversion optimization, bot protection, etc.) from the Main AI Hub.

The technical mechanics are straightforward. The script is asynchronous, so it does not block page rendering. It runs in the background, collecting data about visitor behavior and page content. When you activate an agent, the script begins making real-time adjustments to your site's copy, headlines, or other elements, depending on the agent's purpose.

For example, the Translation Agent rewrites your entire site into 125 languages. The Conversion Agent tests headlines and CTAs. The Bot Refund Agent detects invalid traffic. All of these rely on the same base script. That is why the initial installation is identical for every feature.

One important detail: the script must be in the Header field, not the Footer. Squarespace's Code Injection panel has separate fields for Header and Footer. SeaText explicitly instructs you to use the Header field. Placing it in the Footer may cause the script to load too late or not at all, depending on how Squarespace renders the page.

Step-by-step installation for each version

Squarespace 7.1 (current default)

1. Open your Squarespace dashboard and select the site.
2. Click the three-dot menu next to the site name and choose Settings.
3. Scroll to the bottom of the Settings page to Developer Tools.
4. Click Code Injection.
5. Paste the SeaText JavaScript snippet into the Header field.
6. Click Save, then publish the site.

Squarespace 7.0 (legacy templates)

1. From the Home Menu, click Settings → Advanced → Code Injection.
2. Paste the snippet into the Header field.
3. Save and publish.

Both paths lead to the same Header injection point. The 7.0 path is shorter because Developer Tools is nested under Advanced rather than at the bottom of the main Settings page.

If you are unsure which version you have, check your Squarespace dashboard. 7.1 sites show a single unified editor with no template selection. 7.0 sites have a template switcher under Design. You can also look at the URL: 7.1 sites often use a different editor interface. But the installation steps above cover both.

For 7.0 users, note that some older templates may have additional restrictions on code injection. For example, certain legacy templates might require you to enable "Developer Mode" before the Code Injection panel appears. If you do not see the Advanced menu, check your template settings. In most cases, the standard path works.

Key differences between Squarespace 7.0 and 7.1 for code injection

The only practical difference is where you find the Code Injection panel. Once the snippet is in the Header field, SeaText behaves the same way.

There is one subtle difference worth noting. In Squarespace 7.0, some templates may load the header code differently depending on the page type. For example, a blog post might have a different header structure than a product page. However, because SeaText injects into the global header, it applies to all pages uniformly. In 7.1, the global header is consistent across all page types, so there is no variation.

Another difference is the way Squarespace handles custom code in each version. In 7.0, you might need to enable "Developer Mode" to access certain advanced features. In 7.1, Code Injection is always available under Developer Tools. This makes 7.1 slightly easier for non-technical users.

Limitations and known restrictions

• No localhost or staging subdomains: SeaText explicitly blocks development URLs such as localhost and dynamic preview domains. You must use a real, publicly resolvable domain.
• One account per domain: Each SeaText account is tied to a single primary URL. If you run a staging site and a production site on different domains, you need two accounts.
• Activation requires a live visit: You (or someone) must visit the published site and stay for 40+ seconds to trigger the initial handshake. This cannot be automated via cron or headless browsers.
• No support for Squarespace 5: The legacy Squarespace 5 platform (discontinued for new sites) is not covered by the current integration guide.

These limitations are important to understand before you start. The localhost restriction is a security measure. SeaText wants to ensure that the script only runs on real production sites, not on development environments where traffic data would be meaningless. If you are testing on a staging site, you will need a separate account and a real domain.

The activation requirement is also worth noting. The 40-second visit is a one-time event. It tells SeaText that the script is correctly installed and that the site is live. Without this step, the script remains inert and your dashboard will not show the site.

If you are using a subdomain like blog.example.com, that counts as a separate domain. You cannot use the same SeaText account for both example.com and blog.example.com. Each needs its own account. This is a common point of confusion, so plan accordingly.

Common issues and troubleshooting

Website name does not appear in SeaText dashboard after 10 minutes

This usually means the script didn't load or the activation visit wasn't recorded. Check:

• The snippet is in the Header field, not Footer.
• The site is published (not just saved).
• You visited the live URL, not a password-protected or preview version.
• No ad blocker or browser extension stripped the script on your activation visit.

Multiple domains under one Squarespace account

Squarespace lets you manage multiple sites from one login. SeaText treats each site's primary domain as a separate account. Create a distinct SeaText account for each domain, then install the corresponding snippet on each Squarespace site.

Script loads but no agents work

If the script is installed and the site appears in your dashboard, but agents are not making changes, check the agent configuration. Each agent must be activated individually in the Main AI Hub. Also verify that you have selected the correct pages for each agent. Some agents, like the Google Ads Landing Page Agent, only work on pages that receive paid traffic.

Changes revert after publishing

This is rare but can happen if you have another script that modifies the same elements. SeaText uses edge-side rewriting, which means changes are applied at the network level, not permanently stored in your Squarespace content. If you see reverts, check for conflicts with other custom code.

Key facts

FAQ

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

Only if the trial site uses a real domain (e.g., a custom domain connected to the trial). The built-in .squarespace.com subdomain may work, but SeaText's security rules block dynamic development domains. A custom domain on a trial plan is the safest approach.

Does SeaText work with Squarespace Commerce features?

Yes. The script loads globally, so it runs on product pages, cart, and checkout (where Squarespace allows script injection). Agents like Ecommerce Product Copy and Conversion Agent can optimize those pages.

What if I switch from Squarespace 7.0 to 7.1?

Reinstall the snippet in the new site's Code Injection Header. The SeaText account stays linked to the domain, not the Squarespace version.

Can I use one SeaText account for a main site and a subdomain (e.g., blog.example.com)?

No. SeaText ties each account to a single primary URL. Subdomains count as separate domains and need their own accounts.

Will SeaText slow down my Squarespace site?

The snippet loads asynchronously and the AI rewrites happen at the edge in under 15 ms. SeaText claims zero-flicker rendering. Real-world impact depends on your page weight, but the script itself is lightweight.

What happens if I cancel my SeaText subscription?

The script remains on your site until you remove it from Code Injection. It will simply stop making changes. Remove the snippet to avoid unnecessary requests.

Is there a Squarespace plugin or extension for SeaText?

No. Squarespace does not have a plugin marketplace for third-party scripts. The Code Injection method is the only supported installation path.

How do I know which Squarespace version I have?

Log into your Squarespace dashboard. If you see a single unified editor with no template selection, you are on 7.1. If you have a template switcher under Design, you are on 7.0. You can also check the URL: 7.1 sites often have a different editor interface. The installation steps for both are covered above.

Can I use SeaText on a Squarespace site with a custom domain but no SSL?

Yes, but it is not recommended. SeaText requires a valid, publicly resolvable domain. SSL is not strictly required, but most modern browsers will warn users. For best results, ensure your site has an SSL certificate enabled.

Does SeaText work with Squarespace's password-protected pages?

No. The script will not load on password-protected pages because those pages are not publicly accessible. You must publish the site and remove any password protection for the activation visit to work.