
Why Is There No Direct Upgrade from 7.0 to 7.1?
Squarespace 7.0 and 7.1 use fundamentally different architectures. Version 7.0 uses distinct template families - each with its own features, layout options, and CSS class structure. Version 7.1 uses a unified template system where every site has access to the same features regardless of the starting template.
This architectural difference means content and design cannot be automatically converted between versions. Your 7.0 template, with its specific CSS classes, layout structures, and template-specific features, has no direct equivalent in 7.1. Squarespace chose not to build an automated migration tool because the conversion would produce inconsistent results. For a look at the advanced customization and features on Squarespace, 7.1 significantly expands what is possible without code.
Step-by-Step: How to Switch from 7.0 to 7.1
Step 1: Create a New 7.1 Trial Site
Start a free 14-day trial on Squarespace. Choose any 7.1 template - on 7.1, all templates have access to the same features, so the starting point matters less than on 7.0. The trial gives you full editing access to build your new site.
Step 2: Recreate Your Design
Configure Site Styles - fonts, colors, button styles, and spacing. Set up your header and footer layout. Build your page structure using 7.1's section-based editor. Take advantage of new features: section themes for color variety, the Fluid Engine for flexible layouts, and built-in member areas if needed.
Step 3: Transfer Your Content
Blog posts: Export your 7.0 blog as an XML file (Settings > Advanced > Import/Export > Export). Import this file on your 7.1 site. Blog content, categories, tags, and metadata transfer this way.
Pages: No automated transfer. Copy text content from each 7.0 page, paste it into the corresponding 7.1 page, and reformat using 7.1's editor. Re-upload images or drag them from your 7.0 site's file manager.
Products: Export products as CSV from your 7.0 Commerce settings. Import the CSV into your 7.1 site. Product images may need to be re-uploaded.
Step 4: Rebuild Custom Code
Custom CSS from 7.0 will not work directly on 7.1 - class names and element structures are different. Rewrite your CSS using 7.1's class structure. Code Injection contents (header and footer scripts) should transfer directly - copy them from 7.0 and paste into 7.1. For CSS migration, our guide to Squarespace custom CSS covers 7.1's class structure.
Step 5: Set Up URL Redirects
If any page URLs changed during the rebuild, set up URL mappings (301 redirects) on your 7.1 site to redirect old URLs to new ones. This preserves SEO value from backlinks pointing to old URLs and prevents visitors from hitting broken links. Keep the same URL slugs wherever possible to minimize the need for redirects.
Step 6: Transfer Your Domain
When your 7.1 site is ready, disconnect your custom domain from your 7.0 site (Settings > Domains). Connect it to your 7.1 site. Subscribe to a paid plan on the 7.1 site. Cancel your 7.0 subscription after confirming everything works on 7.1.

How Does Switching Affect SEO?
The SEO impact depends entirely on how you handle the migration.
Same Domain, Same URLs = Minimal Impact
If you transfer your domain and keep all page URLs identical, the SEO impact is minimal. Google sees the same content at the same URLs - just with a new design. You may see minor ranking fluctuations for 2-4 weeks as Google recrawls, but no lasting damage. Complete your SEO checklist before and after migration.
Changed URLs Without Redirects = Significant Damage
If URLs change and you do not set up 301 redirects, Google treats the old URLs as 404 errors. Backlinks pointing to old URLs lose their value. Rankings drop. Traffic decreases. This is the single biggest SEO risk in the migration - and it is entirely preventable with proper URL mapping.
New Domain = Full SEO Reset
If you switch to a new domain during the migration, expect a significant ranking drop lasting 3-6 months. Set up 301 redirects from every old URL to the corresponding new URL. Even with redirects, some link equity is lost. Avoid changing domains during the migration unless absolutely necessary. For monitoring, use Squarespace's SEO tools and Google Search Console to track recovery.

Is the Switch Worth It?
Switch to 7.1 When
You want section themes and the Fluid Engine for modern layouts. Your 7.0 template feels outdated and limits your design options. You are already planning a site redesign. You need features only available on 7.1 (member areas, improved social media integration). Your site is small enough that the content transfer is manageable.
Stay on 7.0 When
Your site works well and you have no design complaints. You have extensive custom code that would need complete rewriting. You have hundreds of pages that would take significant time to migrate. You rely on 7.0-specific features (like certain index page types) not available on 7.1. The effort and potential SEO disruption outweigh the benefits.
Migration Timeline
Small site (under 20 pages): 1-3 days for design, content transfer, and testing.
Medium site (20-50 pages): 3-7 days including design, content, and custom code migration.
Large site (50+ pages or e-commerce): 1-3 weeks including product migration, extensive testing, and redirect setup.
Keep both sites running in parallel until you have fully tested the 7.1 site. Confirm mobile responsiveness, test all forms, verify checkout (if applicable), and check every internal and external link before transferring the domain.
Frequently Asked Questions
Can I upgrade from Squarespace 7.0 to 7.1 directly?
How long does it take to switch from 7.0 to 7.1?
Will switching to 7.1 hurt my SEO?
Can I transfer my blog posts from 7.0 to 7.1?
Will my Custom CSS work on 7.1?
Should I cancel my 7.0 site before building on 7.1?
How do I check if I am on 7.0 or 7.1?
Plan the Migration, Execute Carefully
Switching from 7.0 to 7.1 is a full site rebuild, not a simple upgrade. Create your 7.1 trial, recreate your design, transfer content, set up URL redirects, and test thoroughly before moving your domain. Keep both sites running in parallel until you are confident the 7.1 site is complete and fully functional.
* Read the rest of the post and open up an offer