CMS / SQUARESPACE
Squarespace is a hosted website-building and content-management platform combining visual design tools, content management, commerce and site infrastructure in one place.
This guide covers Squarespace 7.1, Fluid Engine, sections and blocks accurately, with honest comparisons and no invented plan limits or pricing.
Fluid Engine places blocks on a grid within a section. Blocks are positioned and resized directly, and the mobile arrangement is edited separately from desktop.
THE BASICS
Squarespace is a hosted website-building and content-management platform. Website creation, content, design controls, commerce and the underlying infrastructure all live in one subscription, so there is no server to manage, no software to update and no plugin compatibility to maintain.
Calling it “a WordPress alternative” frames it by what it is not. Squarespace is better understood by what it prioritises: design coherence. Its templates and style controls are built so that a site stays visually consistent even when the person building it is not a designer. Typography, spacing and colour are governed site-wide rather than set page by page.
That priority shapes everything else. You get polished output quickly and you work within the platform’s boundaries — which is the trade, stated plainly.
It suits portfolios, creative businesses, professional services, personal brands, restaurants, small business sites, blogs and smaller online stores. People choose it when they want a good-looking site without becoming a web administrator.
On plans and limits: Squarespace’s pricing, commerce features, template availability and plan-specific capabilities change. Check squarespace.com rather than any article’s figures.
Visual page creation without managing code or servers.
Pages, blogs, portfolios and products managed in one place.
Grid-based block positioning within sections.
Products, cart and checkout integrated into the site.
Layouts adapt, with separate mobile arrangement in Fluid Engine.
Titles, descriptions, URLs, sitemaps and verification.
STRUCTURE
A Squarespace page is built from sections — major horizontal areas stacked down the page. Sections are added, reordered, styled and removed independently, which is what makes pages quick to assemble and rearrange.
Not all sections behave the same way, and this is where confusion usually starts. Fluid Engine sections hold freely positioned blocks. Auto layouts arrange content in predefined patterns that reflow automatically. Collection sections pull in blog posts, portfolio projects or products. Gallery sections handle image collections with their own layout options.
Blocks are the content elements inside a section: text, image, button, form, video, gallery, code, shape, social and various commerce blocks among others.
Fluid Engine is the primary editing experience for block sections on Squarespace 7.1. It works as a grid: blocks are placed on it, resized by dragging, and can sit side by side or overlap. This gives considerably more layout freedom than the older classic editor, where content flowed in a more constrained arrangement.
The most useful thing about Fluid Engine is that the mobile layout is arranged separately. You switch to the mobile view and reposition blocks for small screens without affecting desktop. That is genuinely powerful — and it means mobile is a layout you build rather than one you receive.
The classic editor is not obsolete. Older sites run on it, and some content areas behave differently from Fluid Engine sections. If instructions do not match what you see, the editing experience is usually why.
RESPONSIVE
Squarespace sites adapt to screen size. Content reflows, images scale, navigation collapses and typography adjusts. For most sites this works well without intervention.
What it does not mean is that mobile looks after itself. Fluid Engine’s separate mobile arrangement is an opportunity and an obligation — the platform gives you control over the small-screen layout, which also means the small-screen layout is your responsibility. A section arranged carefully at desktop width can stack into something awkward on a phone until you go and arrange it.
The practical habit: after any significant desktop change, switch to the mobile view and check. Things worth looking at are block order after stacking, section heights that become excessive, text sized for a large viewport, images cropping badly at narrow widths, button and tap-target sizes, and spacing that reads generous on desktop and cramped on mobile.
Not every area offers the same control. Collection sections, galleries and auto layouts follow their own responsive rules, and older classic-editor content behaves differently again. See our responsive design guide.
And as on any platform, rendering varies slightly between browsers and devices. Testing on a real phone catches things no editor preview will.
In Fluid Engine the mobile arrangement is edited separately. Blocks can be repositioned, resized and in supported cases hidden, without changing desktop.
A selection of common block types. Which are available depends on your version, plan and section type.
DESIGN & NAVIGATION
Squarespace’s design model is global first. Site-wide styles govern typography, colour palette, button appearance and spacing, and changing them changes the whole site at once. Section and block level settings then adjust individual areas.
Working with that model rather than against it is the difference between a site that stays coherent and one that drifts. The common failure is styling each element individually until forty one-off decisions exist and nobody can change the brand colour without hunting through pages. Set things globally wherever you can.
Setting names and locations vary between versions and interface updates, so treat any specific menu path as indicative rather than fixed.
Pages hold the content and can be organised hierarchically, with navigation reflecting that structure through dropdowns. Navigation is more than a menu — it communicates site architecture to visitors and search engines alike. Clear labels beat clever ones, and a menu that needs explaining is a menu that needs simplifying.
The footer carries secondary navigation, legal pages and contact details, and is worth treating deliberately rather than as leftover space.
CONTENT & COMMERCE
Blogging in Squarespace covers posts with categories, tags, authors, featured images, scheduling, excerpts and per-post SEO settings. Posts are collection content, displayed through collection sections and their own post pages.
It handles content publishing perfectly adequately. Where WordPress pulls ahead is editorial depth at scale — complex taxonomies, many contributors, custom post structures, extensive editorial workflow. For a business publishing regularly to support its services, Squarespace is entirely sufficient, and the integration with the rest of the site is cleaner.
Portfolios are among the strongest reasons people choose Squarespace. Designers, photographers, studios and artists get project presentation, gallery layouts, case study pages and image-led designs that look considered without design work. The image handling and typography defaults do a lot of quiet work here.
Worth remembering: image-heavy portfolios are where performance discipline matters most. Large galleries of unoptimised files are the usual reason a beautiful portfolio site feels slow.
Commerce covers products with variants, product pages, categories, inventory, cart, checkout, payments, shipping, taxes, discounts and order management — integrated into the same site rather than bolted on.
It suits stores where presentation matters more than catalogue depth: a studio selling prints, a maker with a focused range, a service business with some products alongside. Design-led selling is where it is strongest.
Against Shopify, the honest comparison is scope. Shopify’s catalogue modelling, inventory handling across locations, commerce app ecosystem and international selling tools go considerably deeper. Squarespace gives you a beautiful store with less commerce machinery behind it.
Which is right depends on whether selling is the business or part of it. Commerce features and availability vary by plan, so check current documentation against your requirements.
SEO
Squarespace provides the SEO controls that matter: editable SEO titles and meta descriptions per page, URL control, automatic sitemap generation, search engine verification, redirect management and structured markup for supported content types.
Worth saying directly: “Squarespace is bad for SEO” is outdated, and so is the opposite claim. No platform produces rankings. Content, relevance, architecture and competition do. See our website SEO guides.
One Squarespace-specific point causes more confusion than any other — three different titles, and knowing which does what matters:
What appears in the menu. Keep it short, because menus need to be scannable.
The page's name within Squarespace, often used as the on-page heading.
What appears in the browser tab and search results. This is the one search engines show — and the one most often left unset.
If you set nothing, Squarespace falls back to defaults, which usually means a page named “Services” competing in search results as “Services”. Setting SEO titles deliberately on your important pages is among the highest-value hours available on a Squarespace site.
Other points worth attention: URL slugs can be edited and should be settled before publishing, since changing them later means redirects. Blog and product URLs follow structures worth understanding before you commit to an architecture. And third-party embeds — booking widgets, social feeds, chat tools — add weight that affects performance and therefore experience. See our technical SEO guide.
[ ] SEO title set deliberately, not left as the page title [ ] Meta description written for each important page [ ] URL slugs readable and planned before publishing [ ] One H1 per page with a logical heading structure [ ] Alt text on images, including gallery and product images [ ] Internal links placed within content, not only in navigation [ ] Redirects set for any changed URLs [ ] Search Console and Bing Webmaster Tools verified [ ] Sitemap submitted and indexing monitored [ ] Images compressed before upload [ ] Third-party embeds reviewed for performance cost [ ] Core Web Vitals measured with real-user data
MEDIA, SPEED & INFRASTRUCTURE
Images are handled through image blocks and galleries, with responsive serving, focal points, captions and alt text. Squarespace does real work here, resizing and serving appropriately for the device.
It cannot fix what you give it. Uploading camera originals at full resolution produces pages that are heavy regardless of platform handling. Compress before uploading — it is the single most effective performance habit on a Squarespace site, and the one most often skipped on image-led designs. See our image SEO guide.
On performance generally: Squarespace handles hosting, delivery and infrastructure. Page weight is yours. The usual causes of a slow Squarespace site are oversized images, many third-party embeds, multiple font families, large video backgrounds and very long pages. No platform guarantees a performance score, and Squarespace sites are not automatically fast — they are as fast as what you put on them.
Domains can be registered with Squarespace or connected from an external registrar by pointing DNS. SSL is provided, so sites are served over HTTPS. Follow Squarespace’s current documented DNS instructions rather than records quoted anywhere else.
The hosting model is the structural difference from self-hosted platforms. There is no server to configure, no database to maintain, no software to update, no security patching. That removes a genuine burden — and it removes the control that comes with it. See our hosting and domains guides.
CONTROL & QUALITY
Visual controls cover most needs: site styles, section settings, block options and layout. Custom CSS is supported on appropriate plans, and code blocks allow custom markup. Customisation has boundaries — you work within what the platform exposes, and CSS applied to platform-generated markup can break when that markup changes.
Squarespace offers developer-oriented tooling for deeper template work, with implications worth understanding before enabling anything — some developer modes change what visual editing remains available. There are APIs and integrations for connecting external systems. Squarespace does not run arbitrary server-side application code.
The platform handles infrastructure, HTTPS and software maintenance — a real reduction in risk. What remains yours: account security and multi-factor authentication where available, who has contributor access, which third-party services are connected, and any custom code. No hosted platform eliminates risk entirely.
Squarespace provides alt text fields, heading controls and reasonable defaults. It does not make a site compliant. Heading hierarchy chosen for structure rather than size, real alt text, sufficient contrast, keyboard operability, form labels and visible focus are all implementation decisions. See website accessibility.
COMPARISONS
These describe differences rather than declaring winners. Each platform suits some projects and not others.
The trade is managed polish against ownership and flexibility. Squarespace produces a coherent site quickly with no maintenance; WordPress gives ownership, portability and an enormous ecosystem, along with everything that comes with running it.
Compared on commerce specifically. Shopify is commerce-first — its data model is built around products, variants, inventory and orders, with a hosted checkout, deep catalogue modelling, extensive commerce apps and international selling tools.
Squarespace is website-first with commerce included. Products live within a site built for design, which suits stores where presentation carries the sale and the catalogue is manageable.
A studio selling a focused range of prints is well served by Squarespace, and would find Shopify more machinery than the situation needs. A business with hundreds of SKUs, variant complexity, multi-location inventory or international selling will hit Squarespace’s commerce ceiling and should start with Shopify.
The question is whether selling is the business or part of it.
FIT
Squarespace can be considered when a project’s shape matches what it does well. Fit is the honest question rather than ranking.
Designers, photographers, studios and artists presenting visual work.
Consultants, clinics and practices needing a credible presence.
Where a polished site matters more than platform flexibility.
Speakers, writers and practitioners building a presence.
Visual sites with menus, bookings and location details.
Focused catalogues where presentation carries the sale.
And where another platform may be more appropriate:
Logic and workflows beyond what the platform exposes.
Arbitrary structures with relationships and granular permissions.
Where server-level access or data residency is required.
Where the inability to move the site is unacceptable.
Where a large third-party ecosystem is essential.
Large catalogues, variant complexity, multi-location inventory.
Stated plainly, the real limitations are: less control than self-hosted systems, customisation within platform boundaries, advanced requirements needing workarounds or external services, migration away meaning a rebuild, and commerce that is capable rather than deep.
None of these is a criticism. They are the cost side of a trade where the benefit is a coherent site with no infrastructure to manage. For a great many projects that is exactly the right trade — it is worth making knowingly rather than discovering later.
OPERATIONS
A sensible build order: define goals, plan the sitemap, settle a visual direction, configure site styles, build pages and sections, add content, set navigation, configure SEO, optimise media, check mobile, test forms and commerce, connect the domain, publish, then monitor.
The step most often skipped is the first. Planning the sitemap before building saves restructuring later, and URL structure follows page structure — so page organisation decided early is URL organisation decided early.
Migrating to Squarespace is largely a rebuild. Some content imports from some platforms, but design always needs rebuilding and functionality rarely transfers. Audit the existing site, import what can be imported, map every URL, rebuild the design, recreate content and metadata, configure redirects, check images and internal links, test forms and mobile, connect the domain, then verify indexing.
Redirects are where migrations succeed or fail. URL structures differ between platforms, so most URLs change — and without a redirect for each one you lose accumulated search visibility and break every external link.
Migrating away from Squarespace is worth understanding before you commit. Content export has limits that vary by content type, design must be rebuilt entirely, and URLs must be mapped again. It is a rebuild in both directions.
On maintenance: a hosted platform removes infrastructure work, not website work. Content ages, SEO metadata needs setting on new pages, forms break silently, integrations stop working, and mobile layouts need rechecking after design changes.
These are possible causes rather than diagnoses. The same symptom frequently has several causes.
[ ] Content reviewed and kept current [ ] SEO titles and descriptions set on new pages [ ] Broken links checked [ ] Forms tested end to end [ ] Analytics and Search Console reviewed [ ] Domain and billing current [ ] Third-party integrations confirmed working [ ] Images optimised before upload [ ] Mobile layouts rechecked after design changes [ ] Accessibility rechecked after design changes [ ] Account access and contributors reviewed [ ] Commerce flow tested if selling [ ] Redirects maintained for changed URLs
PRACTICE
Fluid Engine gives you control, which means mobile is yours to arrange.
Camera originals on an image-led site, unoptimised.
Pages competing in search as “Services” and “About”.
Structure sacrificed to appearance.
Links only in navigation, never within content.
URLs changed without mapping, visibility lost.
Each third-party widget adding weight.
One-off decisions accumulating into inconsistency.
Especially on galleries and product images.
Movement that distracts rather than guides.
Menus that need explaining.
A good template is a starting point, not a plan.
Building pages, sections and blocks, with the mobile view for layout checking.
Indexing status, search queries and coverage issues for your verified site.
On-site behaviour, whether Squarespace's own or Google Analytics connected.
Field and lab performance data for individual pages.
Lab auditing for performance, accessibility and best practices.
Inspecting rendered markup, network requests and layout behaviour.
Compressing images before upload — the highest-value habit.
Contrast checkers and keyboard testing beyond the platform's defaults.
FAQ
Short answers to the questions people ask most about Squarespace as a website builder, CMS and hosted platform.
NEXT TOPICS
Compare Squarespace with WordPress, Wix, Webflow, Shopify, Joomla, Drupal and Framer to find the platform that fits your goals.
A self-hosted CMS with a very large plugin ecosystem and full ownership.
An open-source CMS with hierarchical content and granular access control.
An open-source CMS built around arbitrary content modelling.
A hosted platform exposing the layout model for precise design control.
A hosted builder with free-form placement and a large app ecosystem.
A commerce-first platform with deeper catalogue and checkout capability.
Another design-led builder with a visual canvas and publishing.
How SEO principles apply across any platform, including Squarespace.
Compare Squarespace with WordPress, Wix, Webflow, Shopify, Joomla, Drupal and Framer to choose the platform that best fits your website goals.