orkaCopy the right project’s snippet
Open your Orka dashboard, then Settings → your project → Installation. Under How to embed, click Copy Code. If this is a new website, create its project first so incoming messages have the right context.
← All installation guides
SquarespaceYour website
One inboxEvery project
SQUARESPACE INSTALLATION · SEPTEMBER 2026How to add Orka
How to add Orka
to Squarespace.
Your Squarespace site, with someone to ask.
A small snippet in your site’s head.
A direct line to the humans behind your project.
SquarespaceYour websiteOne inboxEvery project<head> your Orka snippet </head>A quick check before you start.
A plan with Code Injection: Core, Plus, Advanced or an eligible legacy plan, and access to the site’s settings.
WHERE YOU WILL ADD ITCode Injection → Header
ONE PROJECT. ONE SNIPPET.01 02 03 04
Bring your site aboard.
Find Code Injection
Open your site’s Code Injection panel. If your navigation looks different, search settings for Code Injection.
Use the Header field
Paste the entire Orka snippet into Header so it sits inside the head of your site’s pages. Keep the surrounding script tags.
Save and check the published site
Save your changes and open the public website outside the editor. Check a second page as well as the homepage.
THE FIRST HELLO IS YOUR TESTInstalled is good.
Installed is good.
Working is better.
Use a real published page and a test visitor. You are checking the complete journey, from the widget to the right project in your inbox.
- Open it like a customer.Visit the published site on desktop and mobile. Open the widget and check that it does not cover a key control.
- Send a recognizable test message.Use something like “Installation test — Squarespace”. Check it arrives in the project you intended.
- Answer from the shared inbox.Reply once and confirm the answer reaches the visitor. Then visit another site page and check again.
- Set the welcome before inviting people in.Review your colors, availability, reply expectations and help articles. Choose AI behavior separately.
One more project? Same open tab.
Repeat with the next project’s snippet. SaaS, app, shop or publication: the conversations can all come to one inbox.
YOUR BEARINGS, BEFORE YOU DIVE INYour Squarespace
Your Squarespace
installation questions.
Still wondering about something?
Ask a human at Orka ↗
Where do I find my Orka snippet?+
Log in to the Orka dashboard, open Settings, select the project for this website and choose Installation. Click Copy Code in How to embed. Use that project’s full snippet, not the placeholder shown in this guide.
What do I need on Squarespace?+
A plan with Code Injection: Core, Plus, Advanced or an eligible legacy plan, and access to the site’s settings. Code Injection is unavailable on the current Basic plan. Squarespace checkout pages do not support this custom-code route.
Do I add it to every page?+
Use the site-wide header or the shared layout so the script is included wherever you want chat. Add it once, not through both a plugin and a theme. Test the homepage and an inner page.
Does every website need a different project ID?+
Use a separate Orka project for each distinct product or store whose context you want to keep separate. Copy its own snippet. The conversations can still appear together in your shared inbox.
Why is the widget missing?+
Check the published site, confirm the project ID and complete script are present, and look for duplicate installations. Review your platform’s plan restrictions, cache, consent settings and browser extensions. If it still fails, send Orka the public page URL and the error you see.
Does installing the snippet enable AI automatically?+
Installing the widget is separate from choosing your knowledge and AI behavior. Configure the project, review its answers and decide whether you want human replies, AI drafts or automatic replies. AI usage is separate from the team plan.
Checked, with a way to check again.
Valid as of September 2026. Official sources checked 21 September 2026. Platform menus, plans and prices can change. If we have something wrong, email [email protected].