Squarespace

Squarespace, and the faults that are not yours

Squarespace does a lot correctly, which means an audit of a Squarespace site is mostly about the things the platform cannot do for you. Here is where the line falls.

Resizing a window is not mobile testing

Squarespace, like Wix and several page builders, serves a different document to a phone than to a desktop browser. A tool that opens the desktop page and drags the window narrow is measuring a layout no phone ever receives, and it will report horizontal scrolling that no visitor has ever seen.

This engine loads the page with a mobile user agent to measure a phone. The difference is not academic: on a comparable site, resizing produced three separate overflow warnings and a real phone produced none.

Its CDN files are not your build

Squarespace serves its platform assets from squarespace-cdn.com, and those files publish source maps. A check that does not ask whose file it is reports “source maps exposed” on every Squarespace site there is. You cannot turn it off, it is not your code, and it is not a finding about your business.

The cookie banner you did not write

Squarespace ships standard consent copy. When a page’s text is read for a language check, that boilerplate arrives mixed in with your own writing — and a grammar finding about words the platform inserted is a finding about Squarespace, not about you. It is excluded before the copy is read.

Your buttons are called something specific

Squarespace button blocks carry sqs-block-button-element. An audit looking only for Bootstrap’s .btn will not see them, and will tell a site covered in call-to-action buttons that it has none. That spelling is handled, along with Divi, Elementor and WordPress blocks.

What is left, and it is the part that matters

Strip out everything the platform owns and a Squarespace audit is about your words, your evidence and your reachability: whether a first-time visitor can tell what you do, whether anyone has ever said you were good at it, whether your contact route works, and whether your domain’s email records exist. Those are the findings worth paying for, and they are all things you can change this afternoon without leaving the editor.

Questions people ask

Squarespace says it handles SEO. Do I still need an audit?

It handles the mechanics competently — titles, sitemaps, clean URLs — and the report will say so where it is true. What no platform can do is write the page, collect the reviews, publish the opening hours, or set up email authentication on your domain. Those are where the findings on Squarespace sites tend to land.

Will the report be full of things I cannot change?

It should not be, and where a fault belongs to the platform the report says so rather than billing it to you. Findings you cannot act on are not useful, and a report padded with them is longer rather than better.

Do you check pages behind a members area?

No. Everything is read from outside, as any visitor would see it, with no login. Pages that require an account are not read, and the report says they were not read rather than treating them as passing.