How to Embed a Widget on Squarespace

1. Prerequisites

Before you start, make sure you have the following:

• An Embeddy widget: Log in to embeddy.ai/dashboard and open your widget. Under the Embed tab, copy your iframe embed code.
• A paid Squarespace plan: Iframes and JavaScript require the Core, Plus, Advanced, Business, or Commerce plan. Free trials do not support code rendering. See the Paid Plan section below for details.
• Editor access: You need to be logged in as the site owner or a contributor with editor permissions.

2. Step-by-Step: Adding a Code Block

Squarespace uses a block-based page editor. You will add a Code block to your page and paste the Embeddy iframe code inside it. The entire process takes about two minutes.

1. 1

   Copy your Embeddy embed code

   In your Embeddy dashboard, open the widget you want to embed. Click the Embed tab and copy the full iframe code. It will look like:

   <iframe
     src="https://embeddy.ai/webhost/WIDGET_ID?widget_props_id=PROPS_ID"
     width="100%"
     height="500"
     frameborder="0"
   ></iframe>

2. 2

   Open the page editor in Squarespace

   In your Squarespace dashboard, go to Pages and click the page where you want to add the widget. Click the Edit button to enter the page editor.

3. 3

   Click the insertion point (+) to add a block

   Hover over the area of the page where you want the widget to appear. A blue (+) insertion point will appear between existing content blocks. Click it to open the block picker.

4. 4

   Select the Code block

   In the block picker, scroll down to the More section or search for "Code". Click the Code block to insert it onto your page.

5. 5

   Open the code editor and paste your embed code

   The Code block will appear on your page. Click the pencil icon (edit) on the block to open its settings. In the code editor that appears:

   • Set the Type dropdown to HTML.
   • Paste your Embeddy iframe code into the text area.
6. 6

   Turn off "Display Source"

   In the code block settings, find the Display Source toggle and make sure it is OFF. When Display Source is ON, Squarespace shows the raw code as text rather than rendering it as HTML.

   Common mistake: If you see your raw iframe code displayed as text on the live page, it almost always means Display Source is turned on. Go back to the block settings and toggle it off.

7. 7

   Apply and save

   Click Apply to close the code editor, then click Save in the top-right corner of the page editor to publish your changes.

8. 8

   Preview in Safe Mode

   The editor preview may look different from your public site when you are logged in. To see the true public view, use Preview in Safe Mode (available from the Pages panel). Safe Mode shows the page exactly as visitors will see it.

3. Paid Plan Requirement

Squarespace restricts iframe and JavaScript execution to paid plans. This is a platform-level limitation, not an Embeddy restriction. Here is what each tier supports:

4. Ajax Loading Issue

Squarespace uses Ajax-based page transitions by default. When a visitor navigates from one page to another, Squarespace loads the new page content without a full browser reload. This can prevent JavaScript and some iframe-based content from initializing correctly when a user arrives via site navigation.

If your Embeddy widget loads correctly when you visit the page directly (hard refresh) but appears blank or fails to load when navigating from another page on the same site, Ajax is likely the cause.

Fix Option 1: Disable Ajax

1. In your Squarespace dashboard, go to Design > Site Styles.
2. Look for Enable Ajax Loading and toggle it off.
3. Save your changes. Pages will now load with a full browser refresh, which ensures all iframe content initializes correctly.

Fix Option 2: Move the page out of an Index

Pages placed inside a Squarespace Index structure (a group of pages displayed as a single scrolling page) may not render Code Block content correctly. If your widget page is inside an Index, try moving it out to a standalone page to see if that resolves the issue.

5. Troubleshooting

6. FAQ