Move your Squarespace site, blog, email list, and custom domain to Aveiro without losing SEO signals — inventory exports, rebuild pages, import subscribers, set redirects, and launch on one connected publishing stack.
Integrating ByteDance Models Directly: What We Learned Building Aveiro
In short
Audit Squarespace URLs and exports first. Recreate site structure in Aveiro, migrate content page by page, import subscribers via CSV, connect your custom domain for 301 redirects from the old host, then publish with fresh SEO metadata and analytics consent before you cut traffic over.
Why teams leave Squarespace for Aveiro
Squarespace is strong at polished templates and fast launches. Many creators outgrow it when email, analytics, and the site live in separate products — or when Squarespace Email Campaigns, forms, and blog SEO need manual glue work to stay aligned.Aveiro is built for connected publishing: one organization dashboard for sites, audience email, and analytics. That matters during migration because you are not just moving pages — you are often moving subscribers, campaign history habits, and measurement at the same time.Common reasons teams switch:
Squarespace pain
What Aveiro changes
Site forms and email lists do not share one workspace
Signup components write directly to Audience lists campaigns use
Blog + landing pages + newsletter need separate tools
Sites, campaigns, and analytics under one org
Limited control over MDX-style content and AI-assisted edits
Visual editor plus AI that edits existing layouts, not blank-page guesses
Analytics lives outside the site builder
Cookieless, banner-free tracking toggled in site settings
Scaling to docs, collections, or multi-site brands
Collections, file tree, and multiple sites per organization
This guide is a practical migration playbook — not a one-click importer. Squarespace does not expose a full site export Aveiro can ingest automatically. The steps below minimize downtime, preserve URLs where possible, and keep SEO signals intact.
Before you start: migration inventory
Spend one session documenting what you are moving. Future-you will thank present-you when DNS cutover day arrives.
Asset
Where to find it in Squarespace
Aveiro destination
Live pages and blog posts
Pages panel + blog collection
Aveiro Pages file tree (MDX pages)
Images and media
Asset library / page blocks
Re-upload or hotlink during rebuild; prefer upload for long-term control
Custom domain
Settings → Domains
Settings → Site → Custom domain
Email subscribers
Email Campaigns → Subscribers (export CSV)
Audience → Overview → Import subscribers
SEO titles and descriptions
Page SEO settings per page
Page settings + Settings → SEO defaults
URL slugs
Page settings → URL slug
Match slugs in Aveiro page paths before go-live
Forms and CTAs
Form blocks, button links
Email Signup components + named analytics events
Export what Squarespace allows
Blog posts: use Squarespace’s export tools or copy content manually into Aveiro pages. Expect to rebuild layout blocks — Aveiro uses MDX components, not Squarespace sections.
Subscribers: export your Email Campaigns list as CSV (email, optional name columns). See Import subscribers.
Commerce: if you run Squarespace Commerce, plan product pages separately — Aveiro integrates merch via Fourthwall rather than a native cart clone.
Keep a spreadsheet of old URL → new URL for every indexed page. Identical slugs on your custom domain make redirects straightforward after DNS moves.
Phase 1 — Create your Aveiro site skeleton
Do not paste every paragraph on day one. Structure first, content second — the same pattern Aveiro docs recommend for large migrations.
Squarespace content will not transfer as a single ZIP. Treat each page as a small rebuild project.
Homepage and marketing pages
Open the Squarespace page and the matching Aveiro page side by side.
Recreate sections using Aveiro catalog components (hero, columns, media, CTAs).
Set title, summary, and cover image in Page settings — these drive SEO and social previews.
Replace Squarespace form blocks with Email Signup components tied to your site list.
Blog posts
Create one MDX page per post inside your Blog collection.
Match the slug to the Squarespace post URL.
Paste body copy; re-add headings, images, and pull quotes with MDX components.
Set publishedAt metadata if your theme or archive pages use it.
Images
Download originals from Squarespace when possible — re-upload into Aveiro for stable URLs and alt text control.
Write descriptive alt text on every hero and inline image (accessibility + image search).
AI-assisted speed-up
Use Aveiro’s AI editor to refine copy or adjust layout on the page you already built — paste a section, ask for tighter headlines, or reorder blocks. Avoid generating entire sites from scratch during migration; you already have proven Squarespace content to migrate.
Search engines care about consistent URLs, metadata, and redirects — not which builder rendered the HTML.
Match URLs on your custom domain
When your custom domain connects to Aveiro, paths like /about and /blog/post-slug should resolve the same as on Squarespace. Slug parity avoids unnecessary 404s on day one.
Set site-wide SEO defaults
In Settings → SEO and social sharing, configure:
Default site title suffix
Fallback social image
Privacy policy page (disclose analytics there — Aveiro tracking is cookieless, so no banner is shown)
Per-page unique titles beat one generic site title on every URL. Reference: SEO and social sharing.
Redirects from Squarespace
While Squarespace still serves traffic:
If Squarespace lets you add URL redirects for changed slugs, configure them before cutover.
After DNS points to Aveiro, your *.aveiro.page preview slug 301-redirects to the custom domain automatically when connected — old Squarespace hostnames stop receiving traffic once DNS propagates.
Analytics baseline
Enable Aveiro analytics after your privacy policy mentions it. Compare post-migration traffic in Analytics → Overview once the domain serves Aveiro — do not expect historical Squarespace stats to import. See Analytics and privacy.
GEO note for AI search
Structure pages with a clear In short summary, descriptive H2 sections, tables, and FAQ blocks (like this post). Answer-first paragraphs help both Google featured snippets and AI assistants cite your migration steps accurately.
