Which Squarespace Pages Can I Add SeaText To? A Complete Placement Guide
SeaText installs globally on Squarespace via Code Injection in the site header, so the script loads on every page. After installation, you choose which pages get active AI agents — such as conversion optimization,...
SeaText adds a single JavaScript snippet to your Squarespace site through the Code Injection field in the header. That snippet loads on every page of your site automatically. Once the script is live, you decide which pages actually run AI agents — conversion optimization, translation, Google Ads keyword matching, bot protection, and more — by activating them in the Main AI Hub. In practice, this means SeaText can run on any Squarespace page type: standard pages, blog posts, product detail pages, collection lists, checkout, and even global header or footer regions. The installation is site-wide; the activation is page-specific.
How SeaText Integration Works on Squarespace
The integration uses Squarespace's built-in Code Injection feature. You paste the SeaText JavaScript snippet into the HEADER injection area, which places the script in the <head> of every page on the site. According to the official integration guide, you access this by opening the Squarespace dashboard, clicking the three-dot menu for your site, selecting Settings, scrolling to Developer Tools at the bottom, and choosing Code Injection. After pasting the code into the header field and saving, the script is present on every page load.
This method differs from adding a code block to individual pages. A code block only affects the single page where you place it. Code Injection applies globally, which is why SeaText recommends it: the AI agents need to be available wherever a visitor might land, whether that's a blog post from organic search, a product page from a paid ad, or the homepage from a direct visit.
Page Types Where SeaText Runs
Because the script loads in the global header, SeaText is technically present on every page type Squarespace serves. The distinction is which AI agents you activate on which pages. Common page types include:
- Standard pages — About, Contact, Services, Landing pages
- Blog posts and blog list pages — Individual articles and index pages
- Product pages — Product detail pages in Squarespace Commerce
- Collection pages — Category pages, tag pages, search results
- Checkout and cart pages — Commerce flow pages
- Header and footer — Global elements that appear on every page
- Password-protected and member-area pages — If the script loads, agents can run
The integration documentation confirms the script loads site-wide once placed in the header injection area. There is no page-type restriction in the installation step. Control happens later, in the SeaText dashboard.
Activation Process: From Installation to Page-Level Control
Installing the snippet is only step one. The integration guide outlines a specific activation sequence:
- Paste the snippet in Code Injection → Header and save.
- Publish the site so the script is live on the public URL.
- Visit your own site several times and stay on a page for at least 40 seconds. This signals the SeaText servers that the domain is active and links it to your account.
- Wait up to five minutes for your site name to appear next to the SeaText logo in the dashboard, confirming the connection.
- Open the Main AI Hub and go to Configuration.
- Activate agents on preferred pages. You can choose which agents run where — for example, the Google Ads Agent on landing pages, the Translation Agent on all pages, the Ecommerce Product Copy Agent only on product detail pages.
This two-phase design (global install, selective activation) lets you test agents on a few pages before rolling out site-wide.
AI Agents and What They Do on Each Page Type
SeaText provides 25 autonomous AI agents. Each agent performs a specific function when activated on a page. The homepage and agent directory list the full set. Here are the most relevant for Squarespace page types:
| Agent | Primary Function | Typical Page Types |
|---|---|---|
| Conversion Agent | Continuously tests headlines, offers, CTAs; personalizes copy per visitor | Landing pages, homepage, product pages |
| Google Ads Agent | Rewrites headline, subhead, proof points to match the searched keyword in <15ms | Paid landing pages, campaign-specific pages |
| Translation Agent | Translates entire page into 125 languages at edge speed | All pages (global activation common) |
| Ecommerce Product Copy Agent | Optimizes product names, descriptions, CTAs | Product detail pages, category pages |
| AI SEO Agent | Publishes indexed Q&A pages for long-tail traffic | Blog, resource center, FAQ sections |
| ChatGPT Influence Agent | Builds invisible knowledge base so LLMs recommend your brand | All pages (site-wide knowledge) |
| Bot Protection Agent | Detects bot clicks, builds refund-ready evidence for Google/Meta | Pages receiving paid traffic |
| Conversion Relay (CAPI) | Forwards 100% of real purchases to Meta & Google CAPI | Checkout, order confirmation |
| AI Personalization Agent | Adapts site copy in real time to visitor context | High-traffic pages, returning visitor paths |
| Visitor Source Rewrites | Matches landing page headlines to referrer campaigns | Email, social, referral landing pages |
You activate each agent per page or page group in the Configuration panel. The system also provides an initial round of automatic translations and variants for testing, which you can edit manually or with AI assistance.
Decision Criteria: Choosing Which Pages to Activate
Not every page needs every agent. Use these criteria to decide:
| Criterion | Question to Ask | Typical Decision |
|---|---|---|
| Traffic source | Does this page receive paid, organic, email, or direct traffic? | Paid landing pages → Google Ads Agent, Bot Protection. Organic blog → AI SEO Agent, Translation. |
| Conversion goal | Is the page designed to sell, capture leads, inform, or navigate? | Sales pages → Conversion Agent, Ecommerce Product Copy. Lead pages → Conversion Agent, Visitor Source Rewrites. |
| Audience language | Do visitors speak languages other than the site default? | If yes → Translation Agent on those pages (or site-wide). |
| Content volatility | Does the page content change frequently (blog) or stay static (About)? | Static pages benefit from set-and-forget agents. Dynamic pages may need more frequent AI retraining. |
| Technical constraints | Does the page use custom code, iframes, or password protection that might block the script? | Test after activation. Password-protected member areas usually work if the script loads. |
| Measurement priority | Which pages need the clearest attribution (CAPI, bot refund evidence)? | Checkout, thank-you pages → Conversion Relay, Bot Protection. |
Start with high-traffic, high-value pages. Activate Translation site-wide if you serve international visitors. Add Google Ads Agent only on pages that receive paid search traffic. Enable Bot Protection on any page with paid campaigns.
Limitations and Exceptions
The source pack identifies several hard limits:
- One account per domain. You cannot use a single SeaText account across multiple domains. A development domain and a production domain each need their own account.
- No localhost or dynamic development URLs. The system restricts
localhostand similar development addresses for security. Dynamic preview URLs (e.g., Squarespace's built-in preview domains) may not reliably associate traffic with your account. - Activation delay. After installation, you must visit the live site and wait up to 10 minutes for the dashboard to show the site as connected. If it doesn't appear, support intervention is required.
- Script dependency. If a page uses a custom template that strips the global header injection, the script won't load. This is rare on standard Squarespace templates but possible with heavy developer customization.
- Agent compatibility. Some agents (e.g., Google Ads Agent) require specific URL parameters (
utm_termor ValueTrack{keyword}) to function. Pages without those parameters won't benefit from that agent.
Practical Scenarios: Common Deployment Patterns
Scenario 1: Ecommerce Store with Google Ads
Install globally. Activate Translation Agent site-wide. Activate Google Ads Agent, Bot Protection, and Conversion Agent on product landing pages used in campaigns. Activate Conversion Relay (CAPI) and Ecommerce Product Copy Agent on product detail and checkout pages. Activate AI SEO Agent on blog and buying-guide pages.
Scenario 2: Service Business with Lead Gen
Install globally. Activate Translation Agent on key service pages. Activate Conversion Agent and Visitor Source Rewrites on contact and quote-request pages. Activate ChatGPT Influence Agent site-wide. Activate Bot Protection on pages receiving paid social or search traffic.
Scenario 3: Content Publisher / Blog
Install globally. Activate Translation Agent site-wide. Activate AI SEO Agent on blog index and article pages. Activate Conversion Agent on newsletter signup pages. Activate ChatGPT Influence Agent site-wide.
Key Facts
| Fact | Detail | Source |
|---|---|---|
| Installation method | Code Injection → Header in Squarespace Settings → Developer Tools | S1 |
| Script scope | Loads on every page site-wide once placed in header injection | S1 |
| Activation requirement | Visit live site, stay 40+ seconds, wait up to 5–10 minutes for dashboard connection | S1 |
| Page-level control | Configured in Main AI Hub → Configuration; activate agents per page | S1 |
| Multi-domain rule | One SeaText account per primary domain; separate accounts for dev and prod | S1 |
| Development URL restriction | localhost and dynamic dev domains blocked or unreliable | S1 |
| Agent count | 25 autonomous AI agents available | S2 |
| Translation coverage | 125 languages, zero-code, edge speed | S2 |
| Google Ads Agent latency | Rewrites headline, subhead, proof points in under 15ms on page load | S4 |
| Bot refund benchmark | Up to 20% of ad spend recoverable; 87% client reports accepted | S6 |
Terminology Quick Reference
- Code Injection — Squarespace feature that inserts code into the
<head>(header) or<body>(footer) of every page. - Main AI Hub — SeaText dashboard where you manage connected sites and configure agents.
- Agent — An autonomous AI module that performs a specific optimization (translation, conversion testing, ad matching, etc.).
- Activation — Turning an agent on for a specific page or page group.
- ValueTrack / utm_term — Google Ads parameters that pass the searched keyword to the landing page; required for Google Ads Agent to rewrite copy.
- CAPI (Conversions API) — Server-side event tracking for Meta and Google that bypasses browser blockers.
FAQ
Can I add SeaText to only one Squarespace page instead of the whole site?
Technically yes — you could use a Code Block on a single page instead of Code Injection. But the official integration guide recommends Code Injection in the header so the script is available everywhere. You then control which agents run where via the dashboard. Using a Code Block limits the script to that page and may break agents that need to track cross-page journeys.
Does SeaText work on Squarespace Commerce checkout pages?
The script loads on checkout pages if they inherit the global header injection. However, Squarespace's checkout is a semi-hosted environment; some custom scripts are restricted. Test by activating Conversion Relay (CAPI) and Bot Protection on the checkout flow and verify events appear in the SeaText dashboard.
What happens if I have a staging domain and a live domain?
You need two separate SeaText accounts — one for each domain. The integration guide explicitly states each account links to a single primary URL. Dynamic staging URLs may not work reliably; use a real domain (e.g., staging.yourdomain.com) for the staging account.
How long before I see AI changes on my pages?
After the site shows as connected in the dashboard (up to 10 minutes post-install), you activate agents. The first round of automatic translations and variants appears shortly after. Conversion tests and personalization accumulate data over days; the system scales winning variants automatically.
Can I exclude specific pages from SeaText?
Yes. In the Main AI Hub Configuration, simply don't activate agents on those pages. The script still loads (it's in the global header), but no AI processing runs. If you need the script completely absent from a page, you would need a developer-level workaround — not supported by the standard integration.
Will SeaText slow down my Squarespace site?
The script is designed for zero-flicker, edge-speed execution. The Google Ads Agent rewrites in under 15ms. Translation happens at the edge. The snippet itself is lightweight. Standard performance monitoring (Lighthouse, Core Web Vitals) after install is recommended.
What if my site name doesn't appear in the SeaText dashboard after 10 minutes?
The integration guide says to contact support immediately. This usually indicates the script didn't load correctly — common causes: forgot to publish the site, pasted code in footer instead of header, or the domain doesn't match the account's registered primary URL.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Learn more
Visit the website for more information.