Which Squarespace Settings Must Be Enabled for SeaText to Work?
SeaText works on Squarespace by inserting a JavaScript snippet into your site's header through the Code Injection feature. You need to access the Developer Tools section in your site settings, paste the code into...
SeaText connects to Squarespace through a JavaScript snippet that you paste into the Header field of the Code Injection area. The only settings you need to enable are access to the Developer Tools section and the Code Injection feature itself. There is no separate API key to generate or developer mode switch to flip. Once the code is saved and the site is published, you visit the page a few times to activate the connection.
What SeaText Needs from Squarespace
SeaText runs on your site by loading a small script in the browser. That script must be present on every page you want optimized. Squarespace provides a built-in way to add code to the header of every page: the Code Injection feature inside Developer Tools. You do not need to enable any API, create a developer account, or turn on a developer mode. The integration works on standard Squarespace plans.
The script stays inert until you activate it from the SeaText dashboard. This means you can install it safely without changing anything on your live site until you are ready.
Step-by-Step Settings Checklist
- Log in to your Squarespace dashboard and open the website panel.
- Click the three-dot icon next to your site name and select Settings.
- Scroll to the bottom of the settings page to find the Developer Tools section.
- Click Code Injection to open the code entry fields.
- Copy the JavaScript snippet from your SeaText account.
- Paste the snippet into the Header field (not the Footer field).
- Click Save.
- Publish your site if it is not already live.
- Visit your site several times and stay on a page for at least 40 seconds.
- Wait up to 10 minutes for your site name to appear next to the SeaText logo in your dashboard.
Developer Tools Section Explained
The Developer Tools section sits at the very end of the Squarespace settings page. It is available on all current Squarespace plans. Inside, you will find Code Injection, which provides two text areas: Header and Footer. Code placed in the Header loads before the page content renders. Code in the Footer loads after. SeaText must go in the Header so it can rewrite content before the visitor sees it.
If you do not see Developer Tools, check that you are on a site-level settings page, not a page-level settings panel. The three-dot menu on the website panel leads to the correct location.
Code Injection Header vs Footer
Paste the SeaText snippet into the Header field. The Header field injects code inside the <head> tag of every page. This ensures the script loads early enough to modify headlines, copy, and layout before the browser paints the page. The Footer field injects code before the closing </body> tag, which is too late for SeaText's real-time rewrites.
Do not add the script to individual page headers through page settings. The site-wide Code Injection header covers every page automatically and is easier to maintain.
Publishing and Activation Requirements
After you save the code injection, you must publish the site. Unpublished or draft sites do not serve the injected script to visitors. Once published, visit your own site several times. Stay on a page for at least 40 seconds per visit. This activity signals the SeaText servers that the script is live and communicating.
After the visits, wait five to ten minutes. In your SeaText dashboard, your site name should appear next to the SeaText logo at the top of the page. If it does not appear after 10 minutes, contact SeaText support. The connection may have been blocked by a content security policy or a caching layer.
Multi-Domain and Development Environment Rules
Each SeaText account connects to one primary domain. If you have a development domain (for example, a staging subdomain) and a production domain, you need two separate SeaText accounts. Localhost addresses and dynamic development URLs are restricted for security reasons. Use a real, publicly resolvable domain for each environment.
To use SeaText on multiple distinct websites, create one account per website. The script from account A will not work on the domain registered to account B.
Common Mistakes and How to Avoid Them
- Pasting into Footer instead of Header: The script loads too late. Always use the Header field.
- Forgetting to publish: Saved but unpublished changes are not served to visitors. Click Publish after saving.
- Using one account for multiple domains: The dashboard will not recognize the second domain. Create a separate account.
- Testing on localhost: The script will not activate. Deploy to a real domain.
- Not waiting for activation: The dashboard shows connection status after a few minutes. Do not assume failure immediately.
- Skipping the 40-second visit: Brief visits may not register. Stay on the page long enough for the handshake.
Key Facts
| Setting | Location | Action Required | Notes |
|---|---|---|---|
| Developer Tools access | Site Settings → bottom of page | Click to expand | Available on all plans |
| Code Injection | Inside Developer Tools | Click to open | Provides Header and Footer fields |
| Header field | Code Injection panel | Paste SeaText JavaScript snippet | Loads in <head> on every page |
| Save button | Code Injection panel | Click after pasting | Commits the snippet |
| Publish site | Top-right of dashboard | Click if not already live | Required for script to serve |
| Activation visits | Your live site | Visit multiple times, stay 40+ seconds | Triggers handshake with SeaText |
| Dashboard confirmation | SeaText dashboard | Wait 5–10 minutes | Site name appears next to logo |
Limitations and When This Doesn't Apply
This checklist applies to standard Squarespace websites using the built-in Code Injection feature. It does not cover Squarespace Commerce sites with custom checkout scripts, headless implementations using the Squarespace API, or sites behind password protection that blocks the SeaText crawler. If your site uses a content security policy (CSP) that blocks inline scripts or external domains, you may need to adjust the CSP headers — a change that requires developer access beyond the standard settings.
SeaText does not work on Squarespace trial sites that are not published to a custom domain. The activation handshake requires a real domain with valid SSL.
FAQ
Do I need to enable Developer Mode in Squarespace?
No. The Developer Tools section in settings is different from the legacy Developer Mode (which allowed Git access to template files). You only need the Code Injection feature inside Developer Tools.
Is there an API key to generate in Squarespace?
No. SeaText uses a JavaScript snippet, not an API key. The snippet authenticates your domain against your SeaText account when the page loads.
Can I add the script through page-level Code Injection instead of site-wide?
You can, but you would have to repeat it for every page. Site-wide Code Injection in Developer Tools applies to all pages automatically and is the recommended method.
What if my site name never appears in the SeaText dashboard?
Wait the full 10 minutes. If it still does not appear, check that the script is actually loading (view page source, search for the SeaText snippet). Common blockers include CSP headers, ad blockers on your browser, or a caching plugin serving an old version of the page. Contact SeaText support with your domain if the issue persists.
Does SeaText work on Squarespace 7.0 and 7.1?
Yes. Both versions include the Developer Tools → Code Injection path described above.
Can I use the same SeaText account for a staging subdomain and my main domain?
No. Each domain requires its own SeaText account. Create a separate account for the staging subdomain.
Will the script slow down my site?
The snippet is small and loads asynchronously. SeaText rewrites content at the edge in under 15 milliseconds. Most sites see no measurable impact on Core Web Vitals.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
How SeaText can help
SeaText installs on Squarespace in under a minute through the native Code Injection field. Once active, it runs 25 autonomous AI agents that rewrite headlines to match ad keywords, translate pages into 125 languages, detect bot clicks to recover ad spend, and publish SEO content that ranks in AI search. You control every agent from a single dashboard — no developer needed after the initial paste.
The script stays inert until you activate agents, so you can install safely and test on your schedule. Each domain needs its own SeaText account, and localhost or password-protected staging environments are not supported.