Squarespace

Founded by Anthony Casalena in 2004; HQ New York City. Previously public (NYSE: SQSP, 2021-2024), taken private by Permira in October 2024.

Founded January 2004 by Anthony Casalena.

Fully managed, proprietary hosted website builder; no self-hosting path.

Proprietary, closed-source SaaS platform.

No source-available or open license; access is subscription-based.

Reflects Squarespace's own site-category taxonomy (Creative Services, Professional Services, Beauty, Home Services, Events, Nonprofits, etc.) plus product lines (Portfolios, Online Stores, Blogs, Digital Products).

No permanent free plan; every site starts on a 14-day free trial and must convert to a paid plan to stay live.

Not applicable; no free plan exists.

Basic plan, monthly-equivalent price on annual billing ($228/yr). Monthly billing (no annual commitment) is $25/mo instead. Verified directly from Squarespace's own JSON-LD structured pricing data (US/USD offers) embedded on the live pricing page.

Core plan, monthly-equivalent on annual billing ($348/yr; $39/mo if billed monthly). Squarespace's support docs position Core as the plan for "most service-based entrepreneurs and small businesses," i.e. the popular/mainstream tier.

Basic plan supports selling unlimited products starting at the entry tier (2% Squarespace commerce transaction fee applies; fee drops to 0% on Core and above).

Could not find an official statement of a branding badge on any current paid tier; treat as effectively no forced branding on any plan since there's no free tier to begin with.

Annual-billing monthly-equivalent price is the ongoing rate, not a discounted intro rate that jumps at renewal (unlike many hosts). The main price differential is annual vs. monthly billing cadence, not year-1-vs-renewal.

Full refund automatically available for annual website subscriptions canceled within 14 days of purchase. Monthly-billed plans and renewal payments are not refundable; domain purchases have a separate ~5-day refund window.

Fluid Engine (default in 7.1) is a drag-and-drop, grid-based section editor; freer than classic template sections but still organized into page sections/blocks, not an unconstrained freeform canvas.

Fluid Engine allows pixel-level drag-and-drop placement of blocks within sections.

Text and image blocks are click-to-edit directly on the page.

Squarespace explicitly states there is no autosave or revision-history feature; undo/redo only works within an active, unsaved-or-still-open editing session and is permanently lost once you click Exit. Deleted pages/posts can be restored, but only within 30 days.

No autosave; changes are only persisted when the user manually clicks Save, and content can be permanently lost if the browser/session closes before saving.

Official Squarespace app (iOS and Android, not tablet-optimized on Android) supports editing 7.0 and 7.1 sites; all contributor permission levels can use it.

Squarespace's own help center states plainly: "You can't switch templates in version 7.1." Design changes must be made via style/theme settings or by rebuilding sections; only legacy 7.0 sites supported true template switching with content preserved.

Editorial judgment: Fluid Engine's drag-and-drop, no-code section model and Blueprint AI onboarding make first-site setup fast; the ceiling is lower than code-first platforms but the floor is very approachable for non-technical users.

Squarespace's own template gallery page does not publish an exact count. Third-party trackers cite roughly 195-200 templates for 7.1 as of mid-2026, but this could not be confirmed against an official Squarespace figure, so left null per sourcing rules.

Direct custom font upload (OTF/TTF/WOFF/WOFF2) shipped in late 2025 via Design > Site Styles > Fonts, in addition to ~600 bundled Google Fonts and Adobe Fonts (Typekit) integration on 7.0. Exact plan-tier gating for the new upload feature was not confirmed in official docs.

Fluid Engine lets editors adjust layout per breakpoint (desktop/tablet/mobile) directly in the editor rather than fully automatic reflow or full CSS-level control.

Code injection (custom CSS/JS panel) is excluded on Basic and available starting on Core and above, confirmed directly from the plan comparison table's feature matrix on the official pricing page.

Same Code Injection gate as custom CSS: unavailable on Basic, available on Core, Plus, and Advanced.

Fluid Engine includes native scroll and entrance animation controls per block/section without requiring custom code.

Site Styles panel provides global color palettes, typography scales, and "Themes" (preset style packs like Professional, Bold, Playful) applied site-wide.

Editorial judgment: Fluid Engine's pixel-level block placement goes beyond rigid template-bound builders, but everything still renders inside Squarespace's own section/block model and CSS framework; real customization ceiling requires Core+ code injection, and even then there's no full template/theme replacement path like WordPress.

Fully managed hosting is bundled into every plan; there is no unmanaged/self-hosted tier.

No option to run Squarespace software on your own infrastructure; it is SaaS-only.

Fully managed SaaS; Squarespace patches, updates, and maintains all underlying platform software, servers, and security with no site-owner action required or possible, consistent with hosting.managed_included and hosting.self_host_option = false elsewhere in this file.

Squarespace serves all sites through its own CDN as part of managed hosting (implied by "unlimited bandwidth" claims and global asset delivery); no separate CDN configuration is exposed or required.

"All domains correctly added to your Squarespace site are automatically protected with free SSL certificates."

No formal, contractual uptime SLA (with guaranteed percentage and service credits) is published. Squarespace maintains a public status page (status.squarespace.com) showing real-time and historical incident status, and third-party trackers commonly cite ~99.9% observed uptime, but that figure is not an official contractual guarantee, so left null per sourcing rules.

Squarespace's own export tool only produces a partial WordPress-oriented XML file (posts/pages/images), not a static HTML/CSS/JS site bundle. Full "static export" is only achievable via unofficial third-party page-scraping tools, not a native Squarespace feature.

May 2026 CrUX data via HTTP Archive CWV Technology Report API: 70.4% of 171,945 origins with good CWV (desktop 70.6%, mobile 70.2%). Report technology name: 'Squarespace'.

Every uploaded image is automatically compressed and converted to WebP (AVIF upload support also exists) through Squarespace's image CDN; no manual optimization plugin required, and this can be disabled per-image in Image Settings if needed.

Squarespace auto-generates up to 7 responsive width variants (100 to 2500px) per uploaded image and serves the appropriate one via srcset based on the visitor's screen, plus automatic WebP conversion on upload. No official documentation confirms a blur-up/LQIP placeholder technique specifically; lazy-loading of below-fold images is separately covered under performance.lazy_loading.

Native lazy-loading of images/media below the fold is built into the platform's rendering, not a toggle the user configures.

Site owners cannot configure cache headers, CDN cache rules, or edge caching behavior; caching is entirely managed by Squarespace's infrastructure with no exposed controls.

Squarespace Analytics is a built-in dashboard covering Traffic, Sales, Purchase Funnel, Form and Button Conversions, Traffic Sources, and more. Scope varies by plan: Basic/Personal get Traffic, Geography, Site Content, and Search Keywords panels but not Sales or Conversion tracking; Core, Plus, Advanced, and Commerce plans unlock the full panel set including Sales and Purchase Funnel. Historical data becomes visible retroactively upon upgrading.

Squarespace Analytics uses first-party cookies (ss_cid, ss_cpvisit, ss_cvisit, etc.) that collect visitor data considered personal under GDPR; Squarespace's own docs state these are non-essential cookies and recommend site owners enable a cookie consent banner in regions requiring it, so it is not positioned as cookieless or consent-exempt by default.

No native session-replay feature in Squarespace Analytics. Third-party tools (e.g. Lucky Orange, Mouseflow) can be added via the Code Injection panel (Core plan and up), but session replay is not a listed category in Squarespace's own Extensions marketplace; it's a self-installed script, not a vetted one-click app.

No native heatmap feature. Third-party heatmap tools connect via the same Code Injection mechanism as session replay; the official Squarespace Extensions marketplace has no dedicated analytics/heatmap category and does not list Lucky Orange, Hotjar, or Mouseflow as vetted extensions.

Per-page SEO tab exposes an SEO Title field (100-character limit) and SEO Description field (400-character limit).

URL slugs are editable per page/post via page settings.

Native URL Mappings panel supports 301 and 302 redirects site-wide, syntax `/old-url -> /new-url 301`, capped at 400KB (~2,500 redirect lines). Requires the original page to be deleted/disabled to take effect. Available on all current plans.

Squarespace automatically sets a canonical URL per page, but there is no built-in settings field to edit it; changing it requires a code-injection workaround (Core plan and above), so direct owner control is not available out of the box.

robots.txt cannot be directly edited or overridden; it's a system-generated route. Site owners can only toggle broad crawler-access switches in Settings > Crawlers, not edit raw robots.txt syntax or add per-path rules.

"Squarespace automatically generates and links a proper sitemap.xml, which lists every URL and image metadata on your site." Pages marked "hide from search results" are automatically excluded.

Automatically generates JSON-LD for Blog post, Event, Local business, Organization, Product, and Website schema types. This auto-generated markup cannot be edited or removed; additional/custom schema types (FAQ, Review, Recipe, etc.) require manual JSON-LD via code injection.

No native hreflang support for a single-language site model; hreflang tags are only generated automatically when using the third-party Weglot integration for multilingual sites (or added manually via code injection).

Per-page and site-wide social sharing image/description fields (Open Graph/Twitter Card meta) are editable in SEO/social settings.

Per-page "Hide this page from search results" toggle in SEO settings applies a noindex directive and removes the URL from the sitemap. Applying it to a collection page also excludes all items within that collection.

Alt text fields are exposed on image blocks, gallery images, auto-layout section images, and product images; an SEO report tool flags images missing alt text.

Native Blog Page collection type with posts, tags/categories, comments, and RSS built in.

Custom post types/content fields require the code-level Developer Platform.(template.conf configuration, HTML/JSON-T, Git), which is itself only available on 7.0 sites on Core-and-above plans; not a no-code feature for typical site owners.

Categories and tags are natively supported on blog posts and other collection items.

Blog posts (and podcast episodes) can be scheduled to auto-publish at a specific future date/time.

No content revision/version history system exists; only session-scoped undo (lost on exit) and a 30-day window to restore an entirely deleted page/post; not a rollback-to-prior-version feature.

"Basic authors" can be attached to posts for byline attribution without needing a full contributor login, and don't count against plan contributor limits; full Contributor accounts can also be credited as post authors. There isn't a way to credit multiple distinct authors on a single post, though (workaround: combine names in one author's Display Name).

Built-in RSS feeds auto-generate for blog, calendar, store, gallery, and album collection pages; feed includes the 20 most recent items.

Any page can be queried as JSON (content-as-API) for use by the Developer Platform's templating layer; this is a read path into the CMS content model, not a documented general read-write content API for external apps (separate Commerce APIs exist specifically for order/inventory data, with webhooks for notifications).

Form Block is a native block type addable to any page on any current plan; submissions require connecting a storage destination (email, Google Sheets, Mailchimp, etc.) since submissions aren't stored in the block itself. Official docs specify a recommended 30-field cap per form for usability/Mailchimp compatibility but do not document a submission-count limit that varies by plan.

Member Sites (formerly Member Areas) is a native, built-in gating system: pages added to a member site sit behind a paywall/login, with Free, Fixed-amount, and Subscription pricing-plan structures and support for gated video libraries and course pages. It's free to build on any plan; a paid website plan is required to actually sell memberships, with transaction fees on member payments tiered by plan (7% Basic down to 0% Advanced, matching ecommerce.platform_transaction_fee's digital-content figures).

Commerce is built into the core platform on all four current plans (Basic through Advanced), not a bolt-on app.

Native Digital Products (files, courses, memberships) selling is included on Basic through Advanced with no separate add-on subscription required (legacy plans needed a standalone Digital Products add-on).

Subscription/recurring product sales are included starting on the Basic plan per the official plan comparison table.

A Squarespace store can only sell in one currency at a time natively; multi-currency checkout requires a third-party extension (e.g. TinyCurrency from Squarespace Extensions), and some of these extensions themselves require Core plan or higher.

Squarespace Point of Sale connects a Square account/reader for in-person Tap to Pay, card, and cash payments with automatic inventory sync; available via the iOS app, US only.

Abandoned cart recovery is checked (included) across all four current plans in the official pricing comparison table; not gated to a higher tier.

One blog page (with all its posts, up to 1,000 comments/post) plus basic layout pages export to WordPress-compatible XML. Explicitly excluded: album/cover/index/info/calendar/portfolio/store pages, page-specific headers/footers/sidebars, additional blogs, drafts, and several block types (audio, product, video, dropdown).

Style settings and custom CSS are explicitly excluded from the export; there is no native way to take the visual design/template elsewhere. (Unofficial third-party HTML-scraping tools can capture a rendered static copy, but that is not a Squarespace feature.)

Domains registered through Squarespace (or connected third-party domains) can be transferred/pointed elsewhere; standard domain-transfer rules apply.

The live, functioning site cannot run off Squarespace's infrastructure; there is no self-hosting or headless deployment option; only the partial content export can be migrated elsewhere and rebuilt.

The Developer Platform's page-as-JSON access is scoped to templating/rendering and Commerce APIs cover orders/inventory/webhooks; there is no documented general-purpose API for pulling the complete content model (all page types, settings, design) out of a site.

Editorial judgment: no self-hosting, no static/full-site export, design and most page types excluded from the one export path available, and 7.1 removed template switching; migrating off Squarespace typically means manually rebuilding the site elsewhere rather than exporting and re-platforming it.

Commerce APIs (orders, inventory, transactions) and a Webhook Subscriptions API are publicly documented at developers.squarespace.com; scope is centered on commerce/orders rather than full CMS content.

Native Webhook Subscriptions API lets external endpoints subscribe to events like order.create, order.update, and extension.uninstall.

Code Injection (site-wide and per-page custom HTML/CSS/JS) is unavailable on Basic and included from Core upward, per the official pricing comparison table.

Local development workflow with Git-based deployment is documented as part of the Developer Platform toolchain.

Zapier integration is available (commonly used to connect Squarespace forms/commerce events to other apps); referenced among Core-plan-and-up premium integrations.

Blueprint AI Builder generates a full starter site (copy, images, layout, structure) from a short questionnaire; free to use for building, requires a paid plan to publish. Also offers Blueprint AI Templates and a ChatGPT-integration path (Squarespace GPT).

AI writing assistant available in text blocks, blog posts, product descriptions, email campaigns, and course excerpts; supports prompt-based generation and rewriting (simplify/shorten/lengthen), plus a "Brand Identity" setting for consistent tone.

AI-generated image/pattern/gradient/video options are selectable when adding background media to page sections.

The SEO/AI Visibility panel scans the site to flag missing alt text and page descriptions and generates keyword-optimized suggestions.

Squarespace 7.1 with Fluid Engine renders largely server-side (not a heavy client-side JS SPA), which helps AI crawlers extract page content, and structured data (JSON-LD for Blog post, Event, Local business, Organization, Product, Website) is generated automatically per seo.structured_data. But two gaps cap it below "strong": seo.canonical_control is false (no native canonical override without code injection, raising duplicate-content risk on crawled variants) and seo.robots_txt_editable is false, with only a single blanket "block known AI crawlers" switch and no per-bot or per-path allow/deny rules, so site owners can't selectively invite AEO-relevant crawlers while blocking others. Editorial judgment weighing these existing file findings together.

No native way to serve a file at a custom root path with a custom content type, so llms.txt cannot be generated or hosted directly through Squarespace's own tools. Community workarounds exist (URL Mappings 301 redirect to a CDN-hosted text asset, or a third-party edge worker in front of the site), but there is no official Squarespace feature or announcement supporting llms.txt.

Settings > Crawlers offers a single "Block known artificial intelligence crawlers" checkbox that toggles a whole bundled list at once (GPTBot, ClaudeBot, Google-Extended, CCBot, Amazonbot, and roughly two dozen others), not per-bot switches; Squarespace's own doc states it's "currently not possible to request that AI crawlers only scan specific pages." Consistent with the existing seo.robots_txt_editable = false finding: no raw robots.txt editing or per-path/per-bot rules are exposed.

No official MCP server from Squarespace. Searches of developers.squarespace.com and Squarespace's own blog/changelog turned up no announcement; every MCP implementation found (e.g. community GitHub projects, Zapier's Squarespace Forms MCP, third-party bundle servers) is an unofficial, third-party wrapper around Squarespace's public Commerce/Forms APIs, not something Squarespace publishes or maintains.

Distinct roles beyond a simple admin/editor split: Owner, Administrator, Billing, Website Editor, Store Manager, Email Campaigns Editor, Comment Moderator, Analytics, Viewer, plus separate Enterprise/Acuity role tiers; permissions are individually toggleable per contributor.

One account can log into and manage multiple separate sites, but each live site requires its own separate paid subscription; Squarespace's own words: "Each website you create is paid for separately. We don't offer multi-site plans." A subscription also can't be moved from one site to another without canceling and starting a new one, so a single subscription does not run multiple separate sites.

Squarespace's own docs warn that content "edited in multiple places at the same time" can be lost/can't be restored; implying no real-time multi-user concurrent editing/conflict resolution like a Google-Docs-style co-editor.

No native editorial approval/review-and-publish workflow was found in official documentation; permission levels gate what a contributor can touch, but there's no submit-for-review or content-approval pipeline built in.

Editors can preview unpublished/unsaved changes before publishing, and unpublished pages can be kept in draft, but there's no separate staging environment/URL distinct from the live site's own draft state.

Negative claim cited to the closest official page: Squarespace's contributor/collaboration docs cover inviting contributors and permission levels but list no in-editor commenting/annotation feature for internal collaboration (blog post comments are a public-facing content feature, not an editorial commenting tool).

Negative claim cited to the closest official page: the account Activity History panel logs only account-level events (logins, contributor permission changes, domain/website creation, account settings) for 90 days; there is no audit log of content/site edits (who changed which page and when); only legacy Squarespace 5 had a site change log.

Live chat is restricted to weekday business-hours windows (e.g. English Mon-Fri 4am-8pm ET); only email intake is available around the clock, and there's no phone support at all, so real-time human support is not a 24/7 offering.

Editorial judgment: Help Center articles are detailed, current, and cover most features with step-by-step instructions, but several important nuances (exact export exclusions, no-revision-history, no-template-switch-in-7.1) are easy to miss unless you read the specific article; not quite "excellent" reference-grade developer docs, but well above a thin/sparse knowledge base.

No automatic full-site backup/restore-to-point-in-time system for site owners; recovery is limited to a 30-day window to restore an individual deleted page/post, not a full-site snapshot restore.

No native multilingual/multi-locale site system. Official path is the Weglot third-party integration (free tier: 1 language, 2,000 words; paid beyond that); alternatively a fully manual, labor-intensive duplicate-pages approach with no localized URL structure.

No native in-editor translation management workflow; Weglot (third-party) provides its own translation dashboard outside Squarespace, or content must be manually duplicated and translated page by page.

Per-locale URLs and hreflang tags are only generated automatically through the third-party Weglot integration, not natively; the manual multilingual approach explicitly cannot use separate domains/subdomains per language.

Could not find an official Squarespace statement confirming or denying native right-to-left language/layout support; left null rather than guess.