Does SeaText Require Separate Installation for Each Squarespace Page?

No, SeaText does not require a separate installation for each Squarespace page when you use the site-wide code injection method. The JavaScript snippet goes into one place—the header code injection field in Squarespace settings—and then loads across your entire published site. After that, you control which pages the AI actually runs on from inside the SeaText AI Hub.

If you want a narrower rollout, you can simply turn the AI off on the pages you do not want to touch. You do not need to paste the script into every page individually.

What “installation” actually means on Squarespace

Installation on Squarespace is the act of pasting a small JavaScript snippet into the Header area of the Code Injection panel. Squarespace then adds the snippet to the HTML of every page on your site automatically. From SeaText’s side, that single paste is the entire technical install. There is no per-page template edit and no plugin to mount on each URL.

The source guide describes the flow as: open Settings, scroll to Developer Tools, open Code Injection, paste the script into the HEADER field, then Save. Publish your site for the change to go live.

Site-wide vs. per-page control

SeaText splits the work into two layers:

• Where the code lives: one place, the site-wide header injection.
• Where the AI acts: chosen page by page inside the AI Hub.

So the install is one-time and global, while the activation is selective. A marketer can ship the script on Friday, then on Monday turn the Conversion Agent on for the product pages only and leave the blog untouched.

Why the distinction matters

Treating installation as a per-page chore leads to real problems:

• Maintenance debt: every new page would need a new paste, and old copies would need cleanup when the script updates.
• Inconsistent behavior: one page quietly running an older script can skew A/B tests and analytics.
• Slower rollout: skipping install on a page means the AI cannot help there, even if you wanted it to.

Using the header injection avoids all three. The script is always the latest version, and your per-page decisions live in one dashboard.

How to install SeaText once on Squarespace

1. Log in to Squarespace and open the website panel.
2. Click the three dots icon and choose Settings.
3. Scroll to the Developer Tools section at the bottom of the settings page.
4. Open Code Injection.
5. Paste the SeaText JavaScript snippet into the HEADER field.
6. Click Save, then publish your site.

After saving, visit your site and stay on a page for at least 40 seconds. This triggers the AI to link to your account. Wait up to 10 minutes for your website name to appear next to the SeaText logo at the top of the dashboard, which confirms the connection.

How to run SeaText only on chosen pages

Once the install is confirmed, go to the Main AI Hub and open Configuration. There you can choose the pages where each AI agent is active. For example, you might enable the Translation Agent site-wide but turn the Conversion Agent on only for checkout, product, and landing pages. The JavaScript stays installed everywhere; the activation flag is what changes.

Limitations and things the source pack actually says

The Squarespace integration notes a few constraints worth knowing before you start:

• One primary URL per account. If you run a staging domain and a production domain, you need a separate SeaText account for each.
• No localhost or dynamic dev URLs. For security, local development addresses are blocked. Use a real registered domain for testing.
• Activation is not instant. Allow up to 10 minutes after the first visit for the dashboard to show your site. If it does not appear, contact support—the install may have failed silently.
• Per-page decision is about agents, not the script. The code lives in one place. What changes page by page is which agents run, not whether the script is present.

Key facts at a glance

Common scenarios and the right setup

Small site, want AI everywhere: paste the script into the header, activate the agents you want in the AI Hub, done.

Large store, want AI only on money pages: paste the script into the header, then disable agents on category and blog pages from Configuration. The script still loads; it just does nothing.

Multiple Squarespace sites: create a separate SeaText account for each site. Each account is tied to one primary URL.

Staging + production: use two accounts, one for each domain. Do not try to point a staging URL at a production account.

Frequently asked questions

Will SeaText slow down my Squarespace site if it loads on every page?

The script sits in the header, but it stays inert until you activate agents in the AI Hub. Inactive agents do no work, so an installed-but-deactivated site behaves like a site without the script for that page. The source guide explicitly states the AI remains inert until activated.

Can I install SeaText on just one Squarespace page?

Not by pasting the script into a single page header. The supported path is to paste once in the site-wide header and then switch the agents off on the pages you do not want. Squarespace does not offer a per-page code injection field for header scripts in the same way.

Do I need to reinstall the script when Squarespace updates its template?

No. Code Injection lives at the site level, so template changes do not remove it. You would only need to touch the script if SeaText issues a new snippet or if you rotate the snippet for security reasons.

How do I know the install worked?

Visit your site and stay at least 40 seconds on a page. Then check the SeaText dashboard. Within about 5 minutes, up to 10 minutes, your website name should appear next to the SeaText logo at the top. If it does not, the source guide says to contact support.

Does each Squarespace page need its own SeaText account?

No. One account covers one primary URL. The page-by-page control happens inside that one account. Multiple accounts are only needed for multiple domains.

Can I run different AI agents on different pages?

Yes. The AI Hub lets you activate agents per page. For example, you could run the Translation Agent across the whole site while running the Conversion Agent only on checkout.

What happens if I uninstall the theme or rebuild the site?

A rebuild or theme switch can clear Code Injection in some cases. After any major change, check the header field and re-paste the script if it is gone, then refresh a page for 40 seconds to re-link the account.