Squarespace, past its defaults.

Squarespace is where a lot of good businesses start: fast to launch, easy to edit, and the templates are handsome. It is also the platform where I most often see a site that looks finished and is invisible: no structured data, no crawler policy, nothing an AI assistant can cite. Squarespace allows more than its defaults ship, and that gap is the work.

How I work on Squarespace

• Layer onto your Squarespace site. Structured data, metadata, and crawler policy through Squarespace’s code-injection surfaces, with your design untouched.
• Audit first. A clear, written read on what your current plan tier allows, what your site is missing, and what each fix is worth. No work sold before the picture is honest.
• Rebuild when it pays. If your goals exceed the platform’s ceiling, I say so with specifics, then migrate with every URL preserved.

The machine layer on Squarespace

• JSON-LD ships through code injection, site-wide and, on plans that support it, per page. Hand-authored for your business, validated on the live pages.
• Squarespace generates sitemaps and basic SEO fields automatically. The defaults are fine; the structured layer on top is what’s missing.
• Root-file limits apply. Like most hosted builders, arbitrary root text files (llms.txt) need a lightweight proxy in front, and I set that up.
• The ceiling is real. Deep robots.txt control and server-level work aren’t available. Most businesses never hit that ceiling; if yours will, you’ll hear it from me first.

Platform capabilities move. Before any engagement starts, I re-verify every constraint on this page against the platform’s current documentation and your actual plan tier. You get what is true at kickoff, not what was true when this page was written.