> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Squarespace

> Prepare Squarespace code-injection scope and published-page checks for a future supported Threetone widget.

Squarespace offers code injection in supported site configurations. First confirm that your current site supports the required mechanism; a plan change or purchase does not establish Threetone widget compatibility.

<Note>
  The production widget snippet and working session path are pending. Keep the site unchanged until a released Threetone installation contract specifies its asset and access requirements.
</Note>

## Choose the scope

Squarespace's [code-injection guide](https://support.squarespace.com/hc/en-us/articles/205815908-Customize-parts-of-your-site-with-code-injection) distinguishes global header and footer injection from page-specific header injection. Global fields affect every page; a page's settings under **Advanced** can restrict supported injection to that page.

Choose a test page before planning a site-wide rollout. Follow the released widget's placement instructions. Do not place visible interface HTML in a header field just because it accepts code.

## Prepare the change

<Steps>
  <Step title="Inventory existing code">
    Save a copy of the current injection and identify scripts already providing chat, consent, or analytics. Decide who will maintain the integration and restore the previous configuration if a test fails.
  </Step>

  <Step title="Review the released installation">
    Verify the script origin, version, loading behavior, allowed origins, and session authorization. Keep workspace API keys out of public page code. Use one installation location to avoid duplicate initialization.
  </Step>

  <Step title="Check the published page">
    Test outside the site editor after a supported installation is available. Visit the page directly, navigate to it from another page, and return using browser history. Check that the interface starts once and releases its resources when it ends.
  </Step>
</Steps>

Review mobile layout, cookie-banner overlap, keyboard focus, error messages, and voice permission denial. Keep a contact link visible even when the widget cannot load. If the integration affects editing, remove the test injection and investigate before expanding its scope.

Continue with [web deployment](/agents-platform/deploy/web/overview) and [widget requirements](/agents-platform/deploy/web/widget).

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Is a Squarespace code-injection option proof that the widget works?" id="squarespace-faq-support">No. It provides a place to insert code. Asset loading, session access, browser behavior, and conversation execution must still be verified.</Accordion>
  <Accordion title="Should I install it globally for the first test?" id="squarespace-faq-scope">Start with the smallest supported scope and a clear rollback. Expand only after the published-page checks pass.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.