Squarespace Sites

Know what arrives, and what happens next.

A website preview, a native Squarespace site, and a source-code package are different deliverables. Check the product page and agreed scope before payment.

1. A visual design preview

The previews on this site run as separate websites. They let you inspect a design direction, desktop and phone layout, and illustrative controls. Business names, reviews, prices, locations, and images are sample content. Demo forms do not send customer inquiries.

A preview cannot be uploaded into Squarespace. It does not establish a working booking system, store, payment integration, map, or project calculator in your eventual site.

2. A native Squarespace 7.1 site

A native site must exist and be checked in the real Squarespace editor. Delivery normally involves a prepared site copy, an invitation, acceptance, and a manual ownership handoff. Native Text, Image, Form, and Button Blocks can be edited visually. Custom code has separate editing and support requirements.

Confirm whether you need a new site or a rebuild of an existing site.
Agree actual pages, features, version, and delivery timing before payment.
Use your own Squarespace account. Never share its password.
Accept the invitation using the agreed account email. Invitation sent, accepted, and ownership transferred are separate steps.
Replace sample content and configure actual forms, subscriptions, domains, and business details.
Check the saved site on desktop and phone, including form delivery, navigation, accessibility, and your domain.

The site's hosting subscription and custom domain are not automatically transferred from another site. A new site's subscription is purchased separately. Duplicating a site also has exclusions, so check the official list before assuming everything carries over.

Check contact-form delivery after handoff

Review the saved notification address on every form after receiving your site. Your inquiries need to reach your own business inbox. Keep a required Email field so form submissions can also be associated with contacts in Squarespace.

Open Contact in Pages, click Edit, select the Form Block, and open its editor.
Set Email Notifications to the inbox you want to receive inquiries. Review Additional Storage and reconnect any service you intend to use. Save the page.
Use the saved site to send a clearly labeled test with an email address you own. Check required-field errors before sending the complete form.
Confirm the success message, stored submission, and delivery to your chosen mailbox separately. Check the submitted field values and reply address, then remove the disposable test from your working contacts.

Form notification emails are normally disabled on trial sites unless the site owner is a Squarespace Circle partner. Trial sites can use another supported storage option. Publishing and live operation require the relevant subscriptions; these are separate from the design purchase. Test your chosen storage again after changing ownership or your plan.

For the Remodeling Studio pilot, Home and Contact are the two native pages. Owned testing confirmed invitation acceptance, ownership transfer, saved visual edits, phone navigation, required-field validation, and a matching estimate submission in Squarespace Contacts. Inbox notification delivery on the receiving trial remains unverified. Your sample content and notification settings still need configuration. Booking, project pricing, payments, and integrations are separate work. We confirm your scope and form delivery before payment.

3. Squarespace 7.0 Developer Mode source

Developer Mode is an optional feature of Squarespace 7.0. It does not run on Squarespace 7.1. A developer package needs a complete template structure, the supported Git connection, and real installation acceptance.

Static .page files are edited in source code rather than through the visual CMS. A homepage fragment is not a complete template. Check the product's actual source and support status. We do not offer an unverified fragment as an instant download.

Disabling Developer Mode can discard custom template changes. Use an owned test site, retain a backup, and follow Squarespace's documented recovery limits.

4. Done-for-you services

Setup, rebuilding an existing site, content migration, and a scheduled build need a person. A Long Drive Group team member owns the delivery task. Your content, account access, and agreed scope must be ready before a build day is booked.

An order receipt confirms payment. It does not confirm that your native site was delivered or accepted. Delivery is complete only when the agreed deliverable and acceptance are recorded.

Common setup problems

I already have a Squarespace 7.1 site.

A separate template cannot simply be switched onto it. Discuss whether to rebuild in place or prepare a new site, and check domain, billing, commerce, and subscription implications first.

I cannot find an invitation.

Check the exact agreed Squarespace account email and your spam folder. Ask support to check whether the invitation was issued. Do not buy again to obtain access.

The mobile version looks different.

Squarespace 7.1 Fluid Engine has a mobile layout to review. Check text, block positions, image cropping, navigation, and form controls after your own content is added.

I want to undo a design change.

Use editor undo before leaving the active editing session where available. Keep a separate site duplicate or documented backup for larger changes. Do not assume deleting or disabling a template restores all content.

Support and account safety

Use the support form or Email support. Include your order or request reference, site URL, version, and the step that failed. Never send passwords, card details, or private customer records.

Official platform references

Explore design details Request a fit check