Squarespace development within the platform’s rules.

Part one is knowing the rules. Squarespace’s guide to adding custom code sets them: the CSS editor and plain HTML code blocks work on all plans; JavaScript and iframes in code blocks, and code injection, need the Core, Plus, Advanced or some legacy plans; checkout pages don’t support code; and server-side code such as PHP isn’t supported at all. We check your plan and version before writing a line.

Part two is design changes with CSS. The custom CSS editor handles fonts, colors and backgrounds, and Squarespace itself advises keeping CSS to those, because other changes can harm a site. We keep layout changes minimal, write small, commented CSS, test it on phones and desktops, and keep it in one place so it survives template updates as far as possible.

Part three is code injection and code blocks. Site-wide code injection adds scripts to the head or before the closing body tag of every page; page-level injection targets single pages. We use it for analytics, ad pixels, chat, verification tags and structured data, and code blocks for embedded tools such as calculators, booking widgets or listing searches. Each script is documented so nobody adds it twice.

Part four is SEO, speed and tracking. Page titles and descriptions are written for search, renamed pages get redirects in Squarespace’s URL mappings, images are sized before upload, and unneeded embeds are removed. Because checkout pages don’t run custom code, store purchase tracking uses Squarespace’s built-in analytics and pixel integrations rather than scripts copied from tutorials. That connects to our tracking service.

Part five is the honest platform check, and sometimes a move. When a business needs funnels, a CRM with automations, member areas or logic Squarespace can’t run, working around it costs more than moving. We moved one client’s site from Squarespace to GoHighLevel; stores usually move to Shopify and content-led businesses to WordPress. Each move follows Google’s guidance on site moves with URL changes.

For most Squarespace websites, a move isn’t needed. A clear site that brings in enquiries often just needs better page titles, a faster homepage, forms connected to the right inbox, and a couple of well-placed custom features. That is cheaper and less risky than a rebuild, and we say so, even when the rebuild would be the bigger project for us.

Squarespace’s own support team can’t help with custom code, and its help pages say so plainly, recommending the Squarespace forum or a Squarespace Expert instead. That is the gap we fill: custom work written and tested by a developer, documented for the next person, and checked again after Squarespace updates.

Squarespace work often sits next to marketing. New landing pages for campaigns, service pages for local SEO and form tracking for ads are built by the same team that runs them, so pages go live quickly and are measured from the first visit. Our local services marketing page shows how that fits together for service businesses. For any URL change we follow Google’s site move guide, which says to keep redirects in place for generally at least 1 year. Speed is judged against Google’s Core Web Vitals thresholds: main content within 2.5 seconds, a response to input within 200 milliseconds and layout shift of 0.1 or less.