If your website is still running on Squarespace 7.0, you've probably wondered whether it's time to move to version 7.1.
Squarespace 7.1 offers a more flexible editing experience, newer design features, and improvements to the way websites are built and managed. But upgrading isn't necessarily the right decision for every website.
For businesses with heavily customized Squarespace 7.0 sites, the differences go beyond appearance. Certain features, layouts, and custom development work may need to be recreated.
So, should you upgrade? Here's what you need to know before making the move.
What's the difference between Squarespace 7.0 and 7.1?
Squarespace 7.0 and 7.1 are two different versions of the platform, each with its own approach to website design and customization.
Squarespace 7.0 uses different template families, each with its own styling options and functionality. Some 7.0 websites also use the Squarespace Developer Platform, which gives developers access to template files for deeper customization.
Squarespace 7.1 takes a more unified approach. Instead of choosing between template families with different capabilities, sites share the same underlying design system.
Version 7.1 also introduces features such as Fluid Engine, flexible page sections, auto layouts, and additional design controls.
For most businesses building a new website, version 7.1 is the natural choice. But existing 7.0 websites require a more careful assessment.
Do you have to upgrade from Squarespace 7.0?
No. Squarespace currently allows existing 7.0 websites to remain on that version, and upgrading to 7.1 is optional.
That means there's no reason to rush into an upgrade simply because your website uses an older version.
If your site works well, meets your business needs, and doesn't require functionality exclusive to 7.1, staying on 7.0 may be perfectly reasonable.
The important question isn't whether your website is running the newest version. It's whether the version you're using still supports what you need.
What are the benefits of upgrading to Squarespace 7.1?
For the right website, moving to 7.1 can provide meaningful improvements.
More flexible page layouts
Squarespace 7.1 includes Fluid Engine, a visual editor that offers greater control over how content is positioned on desktop and mobile layouts.
This makes it easier to create customized page designs without relying on additional code for every adjustment.
A more consistent design system
Version 7.0 template families can have very different features and styling controls.
In 7.1, the shared design system makes it easier to apply consistent fonts, colors, spacing, and other visual settings across a website.
Access to newer features
Squarespace continues to develop features around version 7.1, including newer page layouts, animations, commerce capabilities, and content options.
If your existing website is limited by its current template, these features may provide a good reason to upgrade.
What happens to custom code when you upgrade?
This is where things become more complicated.
Squarespace supports custom CSS, JavaScript, and certain code-based integrations in both versions. However, custom code doesn't necessarily behave the same way after an upgrade.
The structure and styling of elements in version 7.1 can differ from those in 7.0.
For example, CSS written to target a particular 7.0 template element may no longer work in 7.1.
Squarespace also notes that custom CSS may be commented out during the update process and may require review before being used again.
Custom JavaScript and third-party integrations should be tested carefully, especially when they depend on particular page elements or template behavior.
The more customized your existing website is, the more important it becomes to review its code before upgrading.
What if your Squarespace 7.0 site uses Developer Mode?
If your website uses the Squarespace Developer Platform, the decision deserves particular attention.
The Developer Platform is available for eligible version 7.0 websites and allows developers to work directly with template markup, stylesheets, scripts, and other template assets.
This functionality isn't available in version 7.1.
To use Squarespace's version update tool, Developer Mode must first be disabled. Doing so removes Developer Platform customizations from the active site.
That means a heavily customized 7.0 website may need substantial redevelopment to achieve a comparable result in 7.1.
This doesn't necessarily mean an upgrade is impossible. It means the project should be approached as a technical migration rather than a simple version switch.
Before disabling Developer Mode, it's essential to preserve the existing code and understand which functionality depends on it.
Will upgrading affect your SEO?
Squarespace's version update tool is designed to retain important site data, including SEO information, domains, URL mappings, and other settings.
However, that doesn't mean every page will remain exactly the same.
Some older page types and structures are handled differently in version 7.1. Certain index-page configurations, for example, can affect page URLs and metadata.
After updating, it's worth checking:
- Important page URLs and redirects
- SEO titles and descriptions
- Heading structure and page content
- Internal links and navigation
- Mobile layouts
- Forms and other important functionality
If you're creating a completely new 7.1 website and moving content manually, the SEO considerations are different. You'll need to plan the migration of URLs, redirects, content, and metadata more carefully.
An upgrade shouldn't be treated as an automatic SEO improvement.
When does it make sense to stay on Squarespace 7.0?
Staying on 7.0 may be the better option if:
- Your website is working well and meets your current needs.
- You rely on custom Developer Platform functionality.
- Your existing design would require significant redevelopment.
- You don't need features exclusive to version 7.1.
- The cost and disruption of upgrading outweigh the benefits.
There's little value in rebuilding a functioning website purely to change its version number.
In some cases, targeted improvements to the existing 7.0 website may be a more sensible investment.
When should you consider upgrading to 7.1?
An upgrade becomes more attractive when:
- You're already planning a significant website redesign.
- Your current template limits the layouts or features you need.
- You want to use newer Squarespace editing tools.
- Your custom functionality can be recreated within 7.1's capabilities.
- The benefits of moving outweigh the migration work.
For a relatively simple website with little custom code, updating may be straightforward.
For a highly customized site, it's worth reviewing the technical implications first.
How to prepare for a Squarespace 7.1 migration
Before starting an upgrade, we recommend taking a few practical steps.
1. Review your existing website. Identify its template, custom code, third-party integrations, and any features that aren't available in 7.1.
2. Preserve your current work. Duplicate the website where supported, and separately save any custom code and important assets. A duplicate isn't a complete backup of every type of site data.
3. Test the 7.1 preview. Squarespace provides an update tool that lets eligible sites preview changes before publishing. Pay particular attention to navigation, mobile layouts, and customized content.
4. Plan for functionality that needs rebuilding. Don't assume every feature or customization will transfer automatically.
5. Review everything before publishing. The update to 7.1 is permanent. Once published, you can't revert the same site to 7.0.
For more details, see Squarespace's official version update guide.
So, should you upgrade?
It depends on what your website needs to do.
For a straightforward Squarespace site, version 7.1 may offer a better editing experience and more room to evolve.
For a heavily customized 7.0 website, staying where you are might be the more practical choice—at least until there's a clear business reason to rebuild.
The best approach is to evaluate your existing website before committing to a migration.