SaaS Website Builder SEO: Wix, Squarespace, Carrd, Framer

A canonical 2026 reference for SEO, AEO, and AIO on the hosted SaaS website builder category. The framework treats the category as one problem space because the platforms share more constraints than…

Wix, Squarespace, GoDaddy Websites, Weebly, Strikingly, Carrd, Notion Sites, Framer, and the broader hosted builder category in 2026

A canonical 2026 reference for SEO, AEO, and AIO on the hosted SaaS website builder category. The framework treats the category as one problem space because the platforms share more constraints than they differ on. Every site on Wix, Squarespace, GoDaddy Websites + Marketing, Weebly, Strikingly, Carrd, Notion Sites, or Framer faces the same family of platform constraints: limited robots.txt control, limited canonical control, limited schema injection surface, limited server side dynamic rendering, no edge function integration, no log analysis. The engineer's job on each platform is the same: use what the platform exposes well, work around what it hides, recommend migration when the ceiling becomes binding.

Cross stack note: for Webflow see framework-webflow.md. For WordPress as migration target see framework-wordpress.md. Schema in framework-schema.md. Multilingual in framework-hreflang.md and framework-international.md. Migration in framework-migration.md. Core Web Vitals in framework-pageexperience.md. Audit overlays in framework-technicalseo.md and framework-mobileseo.md. AI search in framework-aicitations.md and framework-aioverviews.md. Ecommerce in framework-ecommerceseo.md.

1. Document Purpose

1.1 What This Framework Is

Canonical 2026 reference for SEO on hosted SaaS website builders: Wix, Squarespace, GoDaddy Websites + Marketing, Weebly, Strikingly, Carrd, Notion Sites, Framer. Webflow is adjacent but documented separately in framework-webflow.md.

Per W3Techs platform market share survey March 2026 (sample 10M domains crawled) these platforms power roughly 28% of all websites. Wix reports 250M+ cumulative sites in Wix Q3 2025 earnings (around 5% of the active web). Squarespace reports 3.6M+ paid sites in Squarespace Q3 2025 earnings. GoDaddy Websites + Marketing covers 2M+ active sites per GoDaddy 2025 annual report. Weebly under Square covers 1M+ active sites. Strikingly, Carrd, Notion Sites, Framer cover smaller long tail segments.

1.2 The Hosted SaaS Builder Tradeoff

Every platform trades technical control for non technical accessibility. The cost: the SEO engineer cannot reach the levers a self hosted stack exposes. There is no nginx config to tune, no /var/www/sites/[domain]/ to deploy logic into, no log file to grep. There is a limited Custom Code field, limited URL structure, limited robots.txt editor, and a platform generated sitemap that may or may not behave as documented. The engineer operates within constraints, pushes the platform to its ceiling, recommends migration when the ceiling becomes binding.

1.3 When To Recommend SaaS Builder vs WordPress vs Webflow vs Custom

SaaS builder when: under 50 pages, no or basic ecommerce, single language, no custom application logic, no engineering team, content team needs to update without designer involvement.

WordPress when: 100+ pages or growing, content workflow needs Gutenberg, plugin ecosystem solves specific needs (LMS, membership, advanced ecommerce), team can manage updates and security. See framework-wordpress.md.

Webflow when: design is primary value driver, marketing site under 200 pages, content team includes a designer, CMS Collections meet structured content needs. See framework-webflow.md.

Custom (Next.js, Astro, Hugo, static) when: technical team available, performance ceiling matters at the percentile level, deep backend integration required, headless CMS chosen, ecommerce at scale with custom logic, AI features integrated, true SSR personalization needed.

Broader matrix in framework-cross-stack-implementation.md. This framework assumes the SaaS builder decision has been made or inherited.

1.4 The 2026 Positioning of Each Platform

The category has consolidated. Wix and Squarespace dominate general purpose. GoDaddy Websites + Marketing serves "I bought a domain and want a site fast." Weebly under Square is in maintenance mode. Strikingly, Carrd, Notion Sites cover the one page niche. Framer emerged in 2024 and 2025 as a design first builder competing with Webflow on aesthetic with simpler CMS depth.

Each platform's SEO controls have improved since 2020. Schema injection through Custom HTML is standard. Per page meta is universal. Canonical override is available on paid tiers of every major platform. Robots.txt customization is available on Wix, Squarespace, Framer; partial on Weebly; absent on GoDaddy, Strikingly, Carrd, Notion Sites. Sitemap auto generation is universal.

1.5 Required Tools

• Account access on the platform (admin or owner role)
• Google Search Console verified; Bing Webmaster Tools verified
• Rich Results Test and Schema.org Validator
• PageSpeed Insights for Core Web Vitals field data
• Screaming Frog or Sitebulb for crawl auditing rendered output

1.6 Document Scope

Covers platform by platform SEO surface, schema workarounds, internationalization workarounds, performance per platform, migration mechanics, decision criteria for migration. Schema strategy itself in framework-schema.md. Migration playbook beyond SaaS origins in framework-migration.md. General technical SEO in framework-technicalseo.md.

2. Client Variables Intake

# SAAS BUILDER SEO INTAKE
# Stored at /var/www/sites/[domain]/intake/saas-builder.yaml post migration.
# While on hosted builder, store at agency reference copy alongside engagement records.

# Project Identity
project_name: ""
primary_domain: ""
current_platform: ""                 # wix | squarespace | godaddy | weebly | strikingly | carrd | notion | framer
current_plan_tier: ""
plan_cost_monthly: 0
platform_tenure_months: 0

# Migration Posture
migration_consideration: ""          # none | exploring | planned | in_progress
migration_target: ""                 # wordpress | webflow | nextjs | astro | shopify | tbd
migration_blocker: ""                # cost | content_team | timing | platform_lockin

# Content Team Capability
content_team_size: 0
content_team_roles: []               # designer | marketer | writer | generalist
technical_capability: ""             # none | basic | intermediate | advanced
designer_in_team: false
developer_in_team: false

# Technical Team Availability
internal_developer_hours_per_month: 0
external_developer_relationship: ""  # none | retainer | project_based
budget_for_engineering: ""           # none | minimal | moderate | substantial

# Brand Control Requirements
design_control_critical: false
custom_typography_needed: false
template_constraint_acceptable: false

# SEO Baseline State
gsc_property_verified: false
gsc_avg_monthly_clicks: 0
gsc_avg_monthly_impressions: 0
indexed_url_count: 0
sitemap_url_status: ""               # auto | custom | broken | absent
robots_txt_status: ""                # default | customized | unavailable

# Schema State
sitewide_schema_present: false
sitewide_schema_types: []
per_page_schema_present: false
schema_injection_method: ""          # platform_native | custom_html | absent

# Performance Baseline
mobile_lcp_p75_ms: 0
mobile_cls_p75: 0
mobile_inp_p75_ms: 0
lighthouse_mobile_score: 0

# Content Architecture
total_published_pages: 0
total_blog_posts: 0
total_products: 0
total_localized_versions: 0
url_slugs_editable: false

# Integration Inventory
forms_destination: ""                # platform_inbox | webhook | external_crm
analytics_implementation: ""         # platform_native | gtm | direct_ga4 | hybrid
ecommerce_provider: ""               # platform_native | shopify_embed | square | none

# Migration Inventory (if migration planned)
total_legacy_urls: 0
content_export_method: ""            # platform_export | scraping | manual | hybrid
redirect_strategy: ""                # platform_redirect | dns_level | self_hosted_redirect_map

Intake stored alongside the broader engagement intake from framework-clientonboarding.md. When migration is planned, feeds the playbook in framework-migration.md.

3. Wix SEO 2026

3.1 Platform Snapshot

Wix powers approximately 250M cumulative sites per Wix Q3 2025 earnings, around 5% of the active web. The platform invested heavily in SEO tooling since 2018 when its reputation as "bad for SEO" became a public liability.

Wix offers three build experiences: standard Wix Editor (drag and drop), Wix ADI (AI assisted setup), Wix Studio (designer focused responsive grid). Wix Studio is the relevant tier for SEO engineers. The standard Editor is acceptable. Wix ADI should be avoided when SEO matters because AI generated content and structure rarely survive an audit cleanly.

3.2 The Wix SEO Wiz

Wix SEO Wiz is the guided onboarding: site name, business type, target keywords, target location produce a checklist. Useful for first time builders. For an SEO engineer the Wiz is a starting checklist, not the complete setup. Treat as the floor.

3.3 Auto Generated Meta Defaults

Wix auto generates meta tags if SEO settings are blank. The default title is page name plus site name. The default description is a truncation of the first text block. Override manually on every published page in Page Settings > SEO Basics.

3.4 Per Page SEO Settings

Per page SEO on Wix covers:

• Title Tag: up to 70 characters. Best practice 50 to 60.
• Meta Description: up to 160 characters. Best practice 130 to 155.
• URL Slug: editable. Defaults to kebab cased page name.
• Robots Tag: per page index/noindex and follow/nofollow toggles.
• Open Graph: title, description, image. Defaults inherit from meta.
• Structured Data: a JSON-LD field exposed per page.
• Canonical URL: editable per page.

The Structured Data field is the most important Wix specific SEO surface.

3.5 The Schema Editor

The Schema Editor in Page Settings > SEO Basics > Advanced SEO > Structured Data accepts JSON-LD per page, validates basic JSON, renders on publish.

For static pages hand author the JSON-LD. For Wix Dynamic Pages (CMS backed templates) use the {site.field_name} placeholder syntax. Complex traversal is unreliable and often requires Velo developer mode.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "{site.title}",
  "description": "{site.summary}",
  "image": "{site.featured_image}",
  "datePublished": "{site.published_at}",
  "author": {"@type": "Person", "name": "{site.author_name}"},
  "publisher": {"@type": "Organization", "name": "Example Brand"}
}
</script>

3.6 The Wix App Market

Avoid most App Market SEO apps (SEO Wiz, Site Booster, Get Found on Google). The native Page Settings SEO controls and the Structured Data field cover what an engineer needs. Third party apps add platform JavaScript overhead.

Useful App Market categories: form integration (HubSpot Forms, Mailchimp signup) and analytics (GA4 connector) where native integrations are sometimes weaker.

3.7 Wix Studio for Designers

Wix Studio (launched 2023, matured 2025) exposes responsive grid editing, advanced typography, CSS grid primitives, a Components system roughly comparable to Webflow Components. The generated HTML is cleaner than the standard Editor's output.

Wix Studio exposes a Site Code panel for global head and body code injection (the Wix equivalent of Webflow's Project Custom Code). Use for sitewide Organization schema, sitewide tracking pixels, sitewide fonts not hosted by Wix.

3.8 The Velo Developer Mode

Velo is Wix's developer mode: a JavaScript runtime, server side backend/ folder, Wix Data API for CMS access. Occasionally useful for dynamic schema generation, conditional canonical rewriting, custom 301 redirect logic beyond the native redirect manager. Velo code runs on every page load and adds platform JavaScript overhead. Use sparingly.

3.9 URL Structure Constraints

Wix produces URLs as domain.com/page-slug. Static pages at root. CMS Dynamic Pages under a collection prefix like domain.com/blog/post-slug.

Wix does not natively support deep URL hierarchies like domain.com/services/seo/local-seo/. Multi level nesting requires Dynamic Pages with carefully constructed slugs or static pages with manually crafted slugs that simulate hierarchy. The native breadcrumb component breaks on deep trees. For sites needing deep hierarchy Wix is not a good fit.

3.10 Dynamic Pages SEO Handling

Wix Dynamic Pages are template driven pages backed by Wix Collections, the Wix equivalent of WordPress custom post types or Webflow CMS Collections. Every template has its own SEO settings that template across all items.

The SEO engineer should:

1. Author the template SEO with placeholder variables for title, description, structured data.
2. Add explicit SEO Title and SEO Description fields to the Collection.
3. Map the template SEO to those fields rather than to default Name and Description.
4. Author Structured Data with placeholder variables, validating one rendered output before publishing the full collection.

Common gotcha: image URLs in Structured Data that reference wix:image://... internal URIs do not validate. Wix renders these to public CDN URLs on publish but the validator sees the source URI. Validate against a published preview, not the editor preview.

4. Squarespace SEO 2026

4.1 Platform Snapshot

Squarespace powers approximately 3.6M paid sites per Squarespace Q3 2025 earnings. Acuity Scheduling (acquired 2019) and Tock (acquired 2021) are bundled. The platform serves design driven brands, restaurants, hospitality, photographers, creative service businesses.

Squarespace 7.1 is the current version. 7.0 still operates on legacy sites. Where this section says "Squarespace" without qualification it means 7.1. Sites on 7.0 should be migrated to 7.1 before deeper SEO work.

4.2 Squarespace Commerce

Squarespace Commerce is bundled into Business and Commerce plan tiers. Supports up to a few hundred SKUs cleanly. Above 500 SKUs the platform strains on category page performance and faceted navigation. For larger catalogs see framework-ecommerceseo.md.

Squarespace auto generates Product schema for every Product page (name, description, image, price, availability, SKU). Augmentation with AggregateRating, Review, Brand requires Code Injection.

4.3 Per Page SEO

Per page SEO lives in Page Settings > SEO and on blog posts and products in their Settings panels.

• Page Title (SEO Title): editable per page.
• SEO Description: up to 300 characters, truncated around 155.
• URL Slug: editable. Auto generated from title on creation. Editing later requires manual redirect setup.
• Social Image: per page Open Graph image.
• Excluded from Search: per page noindex toggle.

Sitewide SEO defaults in Marketing > SEO Appearance: sitewide title format pattern (e.g. %p | %s) and sitewide default description.

4.4 Schema Injection via Code Blocks

Squarespace does not expose a dedicated structured data field per page. Schema injection happens through one of three mechanisms:

Sitewide Code Injection in Settings > Advanced > Code Injection. Two slots: Header and Footer. Header accepts JSON-LD that renders in <head> on every page. Use for Organization, WebSite schema, sitewide analytics.

Per page Code Injection in Page Settings > Advanced > Page Header Code Injection. Renders in <head> of the specific page only. Use for WebPage, BreadcrumbList, FAQPage, HowTo.

Code Blocks within content for blog posts and product pages. Renders raw HTML inline. Less ideal than head injection.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {"@type": "Organization", "@id": "https://example.com/#organization",
      "name": "Example Brand", "url": "https://example.com/",
      "logo": {"@type": "ImageObject", "url": "https://example.com/logo.png"}},
    {"@type": "WebSite", "@id": "https://example.com/#website",
      "url": "https://example.com/", "name": "Example Brand",
      "publisher": {"@id": "https://example.com/#organization"}}
  ]
}
</script>

4.5 URL Slugs

Squarespace URL slugs follow predictable patterns. Static pages at root: domain.com/page-slug. Blog posts: domain.com/blog/post-slug (the blog prefix is the URL slug of the blog page). Products: domain.com/shop/product-slug. Events: domain.com/events/event-slug.

Collection prefix is determined by the URL slug of the collection page. Multi level taxonomy is not natively supported. Categories and tags become URL parameters like domain.com/blog?category=Topic rather than clean paths.

For category pages with SEO value the workaround is dedicated static pages with manual content that link to blog posts via category filter URLs.

4.6 Canonical Handling

Squarespace generates canonical tags automatically pointing to the rendered URL. Override requires Code Injection per page removing the platform default canonical via JavaScript or accepting two canonical tags. For sites that depend on precise canonical control Squarespace is a difficult platform.

4.7 International Support

Squarespace's native multilingual support is limited. The 7.1 platform supports multiple languages through a workaround: duplicate the site under a different URL slug pattern (e.g. domain.com/es/...) and manually link between versions. Hreflang requires Code Injection.

<link rel="alternate" hreflang="en" href="https://example.com/page-slug">
<link rel="alternate" hreflang="es" href="https://example.com/es/page-slug">
<link rel="alternate" hreflang="x-default" href="https://example.com/page-slug">

For sites where international is a primary growth lever Squarespace is not the platform of choice. See framework-hreflang.md and framework-international.md.

4.8 Sitemap and Robots.txt

Squarespace auto generates sitemap.xml at /sitemap.xml. Includes all indexable pages, blog posts, products.

Robots.txt is auto generated and not directly editable in 7.1 standard editor. Disallows admin paths, allows public site. Workaround: noindex relevant pages individually rather than using robots.txt directives.

4.9 Performance Considerations

Squarespace pages carry platform JavaScript overhead (editor scripts, fluid engine grid runtime, font loading). HTTP Archive April 2026 sample (47,000 Squarespace domains): median LCP p75 3.1s, CLS p75 0.08, INP p75 240ms. Squarespace lands in "needs improvement" for most sites without intervention. Available levers: image compression, font minimization, section count discipline, avoidance of third party widget bloat. Detail in Section 12.

5. GoDaddy Websites + Marketing SEO

5.1 Platform Snapshot

GoDaddy Websites + Marketing is GoDaddy's hosted builder, formerly GoCentral, successor to GoDaddy Website Builder. Powers 2M+ active sites per GoDaddy 2025 annual report. The customer base skews toward small business owners who bought a domain through GoDaddy and chose the bundled site builder.

Strength: speed of launch. A first time builder can publish a serviceable site in an afternoon. Weakness: SEO ceiling. The platform offers the most limited SEO surface of any major hosted builder. For clients with serious SEO ambition migration is usually recommended within the first year.

5.2 The Limited SEO Control Reality

GoDaddy Websites + Marketing exposes per page SEO Title, per page SEO Description, per page URL slug (editable on most plan tiers), sitewide site name and tagline, Google Business Profile connection (manual or auto sync), email marketing integration.

Does not natively expose: robots.txt editing, canonical override per page, per page noindex toggle on lower plan tiers, Custom HTML injection on lower plan tiers, JSON-LD schema editor, per page Open Graph image override on lower plan tiers, hreflang configuration, multilingual site support.

A LocalBusiness with one location, five page site can run on GoDaddy Websites + Marketing acceptably. A multi service business with location pages, service pages, blog content, and ranking ambitions hits the platform ceiling within months.

5.3 Meta Override Mechanics

Per page meta override lives in the Editor under the Settings panel for each page or section. The workflow is fragmented because the platform organizes a site by sections rather than full pages on some templates. Build a meta inventory spreadsheet listing every rendered URL, the section/page that backs it, current title and description, target title and description. Migrate all overrides in one session.

5.4 Basic Schema

GoDaddy Websites + Marketing auto generates basic Organization and LocalBusiness schema on Premium and Commerce tiers when business profile data is filled out.

Augmentation requires the platform's Custom HTML embed block (Premium and above) or Commerce plan's sitewide code injection. The Custom HTML embed is content level injection, not head injection. For LocalBusiness patterns see framework-schema.md.

5.5 GBP Integration

GoDaddy Websites + Marketing offers a tight Google Business Profile integration. The platform can auto sync business hours, contact information, basic posts. For local businesses this is genuinely useful.

Limitation: syncs only basic profile fields, not photos, reviews, posts beyond title and one line of text, product/service details. Treat as a starting point and continue managing GBP directly.

5.6 GoDaddy Studio Asset Library

GoDaddy Studio is a separate Canva style design tool. The Studio asset library can feed images into Websites + Marketing. Ensure images are saved at appropriate dimensions and weights before reaching the live site. Default export sizes are sometimes oversized.

6. Weebly SEO

6.1 Platform Snapshot

Weebly was acquired by Square in 2018 and gradually rebranded as Square Online for the ecommerce variant. The standalone Weebly platform continues for non ecommerce sites but is in maintenance mode. Powers approximately 1M+ active sites globally. For clients on Weebly the question is usually "when do we migrate."

6.2 Per Page SEO

Per page SEO on Weebly lives in Page Settings > SEO Settings. Exposes Page Title (SEO Title), Meta Description (up to 160 characters), Footer Code (per page HTML injection), Header Code (per page HTML injection on Pro and above). Schema injection through Header Code is the recommended pattern.

6.3 The SEO Settings Panel

Sitewide SEO in Settings > SEO. Exposes sitewide meta description, sitewide footer code, sitewide header code on Pro, 301 redirect manager.

The redirect manager works reliably when Weebly is the destination. When Weebly is the origin the redirects do not survive the migration; they need to be reimplemented in the destination's redirect system or at DNS level.

6.4 Square Integration for Ecommerce

Square Online integrates with Square's commerce ecosystem: Reader, Invoices, Appointments, POS. For businesses already on Square's payments stack Square Online is a frictionless ecommerce extension.

The SEO surface matches Weebly's: per page meta, header and footer code injection, basic Product schema generation, sitemap auto generation. Weaknesses: weaker faceted navigation, limited category page customization, limited product catalog structure beyond simple categories.

6.5 Limited Schema Control

Weebly auto generates basic page schema (WebPage, WebSite) but not Article, Product, LocalBusiness, BreadcrumbList. All require manual injection through Header Code (see Section 10.2 for the LocalBusiness template).

7. Strikingly, Carrd, Notion Sites

7.1 The One Page Site Category

Strikingly, Carrd, Notion Sites occupy a distinct niche: one page sites. Use case: landing page for a personal brand, portfolio, product launch, fundraising campaign, small event, digital business card. Small, fast, cheap, quick to build.

The SEO ceiling is correspondingly low. They are designed for sites that have one purpose and exist primarily to be linked to from external traffic sources, not for ranking multiple keywords across multiple pages.

7.2 Strikingly

Strikingly (founded 2012) is the oldest and most full featured. Supports limited multi page sites (up to a few pages on paid plans) and basic ecommerce. SEO surface: per page SEO title and description (paid plans), sitewide footer code injection (paid), custom domain (paid), Google Analytics, sitemap auto generation.

The SEO ceiling sits below Wix and Squarespace. For clients considering serious SEO, migration is almost always the recommendation.

7.3 Carrd

Carrd is intentionally minimal: one page sites built from blocks, $19 per year for Pro, no CMS, no ecommerce beyond Gumroad and Stripe Buy Button embeds. SEO surface: per site title and description, Open Graph image, favicon, custom domain, Google Analytics.

Carrd does not natively expose JSON-LD injection, robots.txt control, or sitemap customization. Pro Plus tier ($49 per year) exposes a Site Settings Custom HTML field for schema injection and tracking pixels.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Person Name",
  "url": "https://example.com",
  "jobTitle": "Job Title",
  "sameAs": ["https://www.linkedin.com/in/example", "https://github.com/example"]
}
</script>

Carrd is acceptable for one page personal brand. For any site that wants to rank for more than the brand name, Carrd is the wrong platform.

7.4 Notion Sites

Notion Sites (launched 2024) lets a Notion workspace publish as a site. Strength: content lives in Notion's editor. SEO surface: per page SEO title, per page meta description, custom domain (paid), sitemap auto generation, basic schema generation (WebPage only).

Notion Sites does not natively expose JSON-LD injection, robots.txt control, canonical override, or hreflang. For documentation use cases reasonable. For ranking ambition the wrong tool.

7.5 Limited SEO Constraints Across the Category

All three share the same ceiling. They work well when the site has one goal, traffic comes from external sources (social, email, paid), the brand has external SEO assets (LinkedIn, GitHub, podcast, YouTube), and the owner does not want to maintain a CMS.

They hit their ceiling when the site needs to rank for multiple keywords, needs more than a few pages, needs internal linking depth, needs schema beyond basic WebPage and Person/Organization, or needs international/multilingual presence.

7.6 Meta Override and Schema Absence

Across Strikingly, Carrd, Notion Sites the schema injection surface is the platform's custom HTML field if available. Inject Person for personal brand sites, Organization for company sites, Article if the site has blog content. Where not available, accept that the site has only the auto generated platform schema.

7.7 The Use Case for Landing Pages

The defensible use case in 2026: a launch landing page for 4 to 12 weeks ahead of a product launch, event, or campaign. Carrd is often the right answer because speed of launch beats every other platform.

For agencies running multiple launch landing pages Carrd's $49 per year Pro Plus tier with 25 sites is unbeatable on cost per landing page. Strikingly serves a similar use case at higher price. Notion Sites is useful when content will feed into broader documentation post launch.

7.8 The Redirect Strategy When Outgrowing

When a one page site outgrows its platform: build the replacement on a more capable platform (WordPress, Webflow, Next.js, Astro), set up a DNS or platform level 301 redirect from the old URL to the new URL. For platforms that do not natively support 301 redirects (Carrd does, Strikingly does on paid tier, Notion Sites does not) implement at DNS or at the new platform. Migration mechanics in framework-migration.md. For one page sites migration is usually trivial because URL inventory is small.

8. Framer SEO

8.1 Framer Platform Snapshot

Framer emerged in 2023 and 2024 as a design first builder competing with Webflow on aesthetic but with a different DX. Where Webflow uses a CSS box model and Style Manager, Framer uses a Figma like canvas. Powers an estimated 200,000+ active sites by Q2 2026 per Framer community telemetry.

8.2 Framer's SEO Settings Surface

Framer exposes per page SEO title and description, per page Open Graph image, per page canonical override, per page noindex toggle, sitewide robots.txt customization, sitemap auto generation, sitewide Custom Code injection in head and body, per page Custom Code injection (paid plan). The Framer SEO surface is comparable to Webflow's in scope. Execution is less mature because the platform is younger but the feature set covers the essentials.

8.3 Meta Override

Per page meta override lives in the page properties panel. Template style meta references CMS field values:

{title} | Example Brand

Framer's CMS templating syntax is simpler than Webflow's {{wf}} syntax but functionally equivalent for the common meta cases.

8.4 Basic Schema Injection

Schema injection happens through sitewide or per page Custom Code. Framer does not have a dedicated structured data field per page the way Wix does.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {"@type": "Organization", "@id": "https://example.com/#organization",
      "name": "Example Brand", "url": "https://example.com/",
      "logo": {"@type": "ImageObject", "url": "https://example.com/logo.png"}},
    {"@type": "WebSite", "@id": "https://example.com/#website",
      "url": "https://example.com/", "name": "Example Brand",
      "publisher": {"@id": "https://example.com/#organization"}}
  ]
}
</script>

Per page schema lives in per page Custom Code (Pro plan and above).

8.5 CMS for Blog Posts

Framer CMS supports Collection style structured content similar to Webflow Collections. Each Collection has a defined field schema, a template page rendering one item per record, automatic sitemap inclusion, referenced fields.

For blog posts: create a Blog Posts Collection (title, slug, summary, body Rich Text, featured image, author reference, published date, SEO title, SEO description), build a Blog Post Template page, configure template SEO to reference Collection fields, inject Article schema in template Custom Code.

8.6 Performance Profile

Framer pages score better than Squarespace and Wix on Core Web Vitals. HTTP Archive April 2026 sample (3,200 Framer domains): median LCP p75 1.9s, CLS p75 0.05, INP p75 180ms. Framer lands in "good" for the majority of sites. The ceiling is limited by the Framer Motion animation runtime that ships on every page using motion components.

8.7 When Framer is the Right Recommendation

Framer is right when the brand is design driven and the designer prefers a Figma like canvas, marketing site under 100 pages, CMS depth fits Framer's feature set, team is comfortable with a younger platform, no headless commerce or deep backend integration required.

Framer is wrong when site exceeds 200 pages of CMS content, multilingual is a primary requirement, ecommerce beyond Gumroad and Stripe embeds is needed.

9. The Universal SaaS Builder Constraints

9.1 Limited Robots.txt Control

SaaS builders abstract /robots.txt. Most platforms generate it automatically based on per page "exclude from search" toggles. A few (Wix, Squarespace 7.1, Framer) expose a robots.txt editor. Most (GoDaddy, Weebly, Strikingly, Carrd, Notion Sites) do not.

Workaround: rely on per page noindex meta tags rather than robots.txt Disallow. The two have different semantics but for most small site needs noindex is sufficient. For sites that need to block crawling of URL patterns at scale the platform is the wrong choice.

9.2 Limited Canonical Control

SaaS builders generate canonical tags automatically pointing to the rendered URL. Some (Wix, Framer) expose per page override. Most require Custom HTML injection with a JavaScript snippet that removes the platform's canonical and inserts a custom one.

Google handles client side canonical rewriting acceptably in 2026 but the platform's server side canonical remains in HTML source. Validators may flag the dual state. For sites that depend on precise canonical control this workaround is brittle.

9.3 Limited Schema Injection Surface

Self hosted stacks let the engineer inject JSON-LD into the head of every page programmatically with full templating. SaaS builders limit injection to platform exposed fields, code injection slots, or content blocks.

Workaround pattern is universal: identify the platform's most powerful schema injection slot (head injection preferred, body acceptable, content block last resort) and use it consistently. Patterns in Section 10.

9.4 Limited Server Side Dynamic Rendering

SaaS builders render statically at publish time or use the platform's runtime which the engineer cannot extend. There is no if (request.country === 'GB') pattern because there is no request handler the engineer can write to. Client side JavaScript layered on top of static HTML can implement dynamic behavior but does not affect what Googlebot sees on rendered HTML.

9.5 No Edge Function Integration

SaaS builders do not expose an edge runtime the engineer can deploy to. This framework explicitly avoids prescribing third party edge or CDN proxies. The right answer when a site needs edge logic is to migrate to a stack that natively supports edge functions on self hosted infrastructure with no third party CDN proxy intermediating.

9.6 No Custom Log Analysis

SaaS builders do not expose raw access logs. Platforms expose some analytics (Wix Analytics, Squarespace Analytics, Framer Analytics) designed for marketing dashboards. Google Search Console Crawl Stats covers some of the gap but does not replace raw log analysis. For sites where log analysis is a primary operations tool the platform is the wrong choice.

9.7 The Workaround Pattern

When facing any constraint:

1. Identify the smallest platform exposed surface that addresses the need.
2. Implement as close to HTML head as the platform allows. Head injection beats body beats content block.
3. Test rendered output against target tool (Rich Results Test, Schema.org Validator, Lighthouse, Search Console URL Inspection).
4. Document the workaround in the project's intake file.
5. Note the workaround as a migration trigger when it becomes fragile or the platform changes behavior.

10. Schema Workarounds

10.1 The Custom HTML Pattern Across Platforms

Every SaaS builder exposes some form of HTML injection slot. Location and capacity differ; the pattern is the same.

For schema strategy beyond injection mechanics see framework-schema.md.

10.2 LocalBusiness Schema Template

For local service businesses LocalBusiness lives in the sitewide head injection slot.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "@id": "https://example.com/#business",
  "name": "Example Local Business",
  "telephone": "+1-555-555-5555",
  "address": {"@type": "PostalAddress",
    "streetAddress": "123 Main St", "addressLocality": "City",
    "addressRegion": "ST", "postalCode": "12345", "addressCountry": "US"},
  "geo": {"@type": "GeoCoordinates", "latitude": 40.0, "longitude": -75.0},
  "url": "https://example.com/", "priceRange": "$$",
  "openingHoursSpecification": [{"@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
    "opens": "08:00", "closes": "17:00"}],
  "sameAs": ["https://www.facebook.com/example", "https://www.linkedin.com/company/example"],
  "areaServed": [{"@type": "City", "name": "Primary City"}]
}
</script>

For service area businesses (no storefront), replace LocalBusiness with the specific subtype (ProfessionalService, Plumber, Electrician) and remove address in favor of areaServed.

10.3 Article Schema Template

For blog posts on any SaaS builder Article schema lives in the CMS template head injection slot or per page head injection.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "{title}",
  "description": "{summary}",
  "image": "{featured_image}",
  "datePublished": "{published_at}",
  "dateModified": "{updated_at}",
  "author": {"@type": "Person", "name": "{author_name}",
    "url": "https://example.com/authors/{author_slug}"},
  "publisher": {"@type": "Organization", "name": "Example Brand",
    "logo": {"@type": "ImageObject", "url": "https://example.com/logo.png"}},
  "mainEntityOfPage": {"@type": "WebPage",
    "@id": "https://example.com/blog/{slug}"}
}
</script>

The {...} placeholders are platform specific. Wix uses {site.field_name}. Framer uses {field_name}. Squarespace requires hand authored values per post because the blog template does not natively support field templating in Code Injection.

10.4 Product Schema Template

For ecommerce on Wix Stores, Squarespace Commerce, Square Online, the platforms typically auto generate Product schema. When auto generated schema is insufficient (missing AggregateRating, Brand, detailed Offer variants), augment via product template head injection.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "{product_name}",
  "image": "{product_image}",
  "description": "{product_description}",
  "sku": "{product_sku}",
  "brand": {"@type": "Brand", "name": "Example Brand"},
  "offers": {"@type": "Offer", "price": "{product_price}",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://example.com/products/{product_slug}"},
  "aggregateRating": {"@type": "AggregateRating",
    "ratingValue": "{aggregate_rating}",
    "reviewCount": "{review_count}"}
}
</script>

When platform auto schema and manual schema both render the page has duplicate Product schema. Google handles duplicates by merging where possible. Removing the platform's auto schema via JavaScript is the cleaner pattern but most platforms make this difficult; accept the duplicate state if removal is brittle.

10.5 Per Page Schema Injection Limitations

Per page injection slot is usually limited in capacity. Squarespace has no character limit. Wix Structured Data field has a soft limit around 8,000 characters. Framer per page Custom Code has plan based limits.

For pages with many schema types (a service page needing Service, FAQPage, BreadcrumbList, WebPage), consolidate into a single @graph block:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {"@type": "WebPage", "@id": "https://example.com/services/seo#webpage",
      "url": "https://example.com/services/seo", "name": "SEO Services",
      "breadcrumb": {"@id": "https://example.com/services/seo#breadcrumb"}},
    {"@type": "BreadcrumbList", "@id": "https://example.com/services/seo#breadcrumb",
      "itemListElement": [
        {"@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com/"},
        {"@type": "ListItem", "position": 2, "name": "Services", "item": "https://example.com/services"},
        {"@type": "ListItem", "position": 3, "name": "SEO"}]},
    {"@type": "Service", "@id": "https://example.com/services/seo#service",
      "name": "SEO Services", "provider": {"@id": "https://example.com/#organization"}},
    {"@type": "FAQPage", "@id": "https://example.com/services/seo#faqpage",
      "mainEntity": [{"@type": "Question", "name": "How long does SEO take?",
        "acceptedAnswer": {"@type": "Answer", "text": "SEO typically takes..."}}]}
  ]
}
</script>

10.6 Schema Validation Workflow

After installing schema, validate.

# Publish and wait for platform cache invalidation (30-90 seconds)
curl -s -A "Mozilla/5.0 SEO-Validation" "https://example.com/target-page" \
  | grep -A 50 'application/ld+json' > /tmp/schema-extract.html
# Inspect or paste into Rich Results Test
# Verify rendered HTML uses platform CDN URLs for images, not internal URIs
# (common Wix gotcha: wix:image://... URIs in editor preview that render to public URLs on publish)

Validate at least one item per template (one blog post per blog template, one product per product template, one location per location template). Template level schema is consistent across items.

11. Internationalization Workarounds

11.1 The Subdomain vs Subdirectory Limitations

SaaS builders constrain the choice between subdomain, subdirectory, ccTLD.

Wix Multilingual and Framer i18n are the cleanest native implementations. Both expose subdirectory locale strategy, automatic hreflang generation, locale specific content overrides, locale specific URL slugs. Both are paid.

The "multi site workaround" pattern: build the second language as a separate site, point at a different subdomain or ccTLD, manually maintain hreflang and cross language linking.

11.2 Hreflang Patterns Where Supported

Wix Multilingual auto generates hreflang for every page with locale variants. Covers standard language and language-region patterns (en, en-US, en-GB, es, es-MX). Framer i18n generates hreflang similarly with narrower locale support.

Squarespace, Weebly, and the one page platforms require manual hreflang injection through Custom Code:

<link rel="alternate" hreflang="en" href="https://example.com/page-slug">
<link rel="alternate" hreflang="es" href="https://example.com/es/page-slug">
<link rel="alternate" hreflang="fr" href="https://example.com/fr/page-slug">
<link rel="alternate" hreflang="x-default" href="https://example.com/page-slug">

Maintaining hreflang manually at scale is operationally expensive. A 50 page site with three languages requires 200 declarations. For serious international ambition the right answer is Wix Multilingual, Framer i18n, or migration to a platform with stronger native multilingual support (WordPress with WPML, Next.js with i18n routing). Full strategy in framework-hreflang.md. Broader international SEO in framework-international.md.

11.3 The Multi Site Workaround Pattern

When native multilingual is unavailable: build the primary language as single language, build a second site for the second language, point the second site at a different URL pattern (subdomain, ccTLD, or different domain), manually inject hreflang on both sites, maintain content parity manually, submit both sites to GSC as separate properties.

The pattern works but is operationally expensive. Every content change on the primary site requires a parallel change on the secondary. For most clients the recommendation is: stay single language until international traffic justifies migration to a platform with native multilingual support, then migrate.

12. Performance Profile Comparison

12.1 Platform Performance Baseline

PageSpeed Insights mobile field data from the HTTP Archive sample April 2026 shows median Core Web Vitals per platform:

Lighter platforms (Carrd, Framer, Notion Sites) ship faster baselines than heavier general purpose platforms (Wix, Squarespace, GoDaddy, Weebly). Squarespace and Wix land in 40 to 65 Lighthouse mobile. Framer lands in 70 to 85. Carrd lands at 90+.

12.2 Why Wix and Squarespace Score 40 to 65

The ceiling is constrained by platform JavaScript runtime that ships on every page (editor scripts, fluid engine grid for Squarespace, Velo bootstrapping for Wix), font loading patterns that block render, image lazy loading that is not aggressive enough on hero images, animation libraries in default templates, third party widgets bundled by default.

Per page optimization can lift scores into 60 to 75 but rarely above. The baseline overhead is a floor engineering effort cannot push below without migrating.

12.3 Why Framer Scores 70 to 85

Framer's ceiling is higher because of a lighter runtime (Framer Motion is opt in per component rather than ambient), more aggressive image optimization on publish, cleaner generated HTML, static publishing with minimal hydration. Sites heavy on motion score lower (60 to 75). Sites minimizing animation can hit 85+.

12.4 Why Carrd Scores 90+

Single page sites with minimal content, no platform runtime beyond a tiny initialization script, no fonts unless added, no images unless added, no third party widgets unless embedded. A default Carrd site ships under 50KB total page weight.

12.5 Platform Side Optimization Options

Wix: Wix Studio for cleaner HTML, disable Velo where not needed, native image lazy loading, minimize App Market installs, system fonts where brand permits, compress images before upload.

Squarespace: 7.1 not 7.0, minimize fluid engine sections per page, disable social link block if unused, WebP where upload permits, prefer Clean and Crisp template families, defer analytics and chat to footer.

GoDaddy Websites + Marketing: limited options beyond image compression discipline; avoid template themes loading custom fonts by default; disable unused homepage sections.

Weebly / Square Online: minimize plugins from Weebly App Center, compress images before upload.

Strikingly: minimalist templates rather than photography heavy, compress hero images.

Carrd: system fonts, compress images, avoid embedded videos (use thumbnails linking to YouTube).

Notion Sites: runtime overhead fixed; optimize images.

Framer: motion components selectively, alt text and srcset on every image, native lazy loading on below fold images, minimize custom fonts.

12.6 The Asset Hosting Limitations

Every platform hosts assets on the platform's infrastructure. The engineer cannot move images to a separate origin without breaking the editor's media management. The platform's image optimization is what the site gets.

For sites where image optimization matters at the percentile level (image heavy ecommerce, photography portfolios, recipe sites) migrate to a platform with a stronger image pipeline (Shopify for ecommerce, Next.js with self hosted image optimization, WordPress with ShortPixel/Imagify) or accept the ceiling.

For Core Web Vitals beyond platform tactics see framework-pageexperience.md. For mobile patterns see framework-mobileseo.md.

13. Migration from SaaS Builders

13.1 Migration Strategy Overview

Migration from a SaaS builder is one of the most common projects an SEO engineer takes on. The pattern: client has been on Wix or Squarespace for three to five years, accumulated 50 to 200 indexed URLs, sees traffic plateau, asks "should we move." The answer is rarely no. Detailed playbook in framework-migration.md.

13.2 Wix to WordPress

Most common SaaS builder migration. Wix RSS feed at domain.com/blog-feed.xml exports blog posts (25 most recent on free). Wix CMS export is not directly available; CMS Collection data requires Wix's Site Migration tool, the Velo wix-data API, or scraping. Static pages: manual content copy. Images: download from Wix Media Manager or scraping.

Pattern: crawl live Wix site with Screaming Frog, export blog posts via RSS, copy static page content to CSV, download images, build new WordPress site on staging with theme and Rank Math, import blog posts via WP All Import, create static pages from CSV, upload images, configure URL mapping (Section 13.6), test, cut DNS, implement 301 redirects.

For 50 to 100 page sites timeline is 60 to 120 hours. Beyond 200 pages grows non linearly.

13.3 Squarespace to WordPress

Supported by Squarespace's WXR export under Settings > Advanced > Import / Export Content. Includes blog posts, pages, embedded images, comments, some metadata. Does not include product data (requires separate Commerce product CSV), form submissions, member accounts, Acuity Scheduling data, custom CSS or Code Injection blocks, block styling.

Pattern: export, crawl live site for URL inventory, build new WordPress site, import WXR via native Importer, re-add Code Injection content as WordPress equivalents, re-add custom CSS as theme customizations, configure URL mapping, test, cut DNS.

For 50 to 100 page sites timeline is 40 to 80 hours. Faster than Wix to WordPress because the export is cleaner.

13.4 GoDaddy to WordPress

GoDaddy Websites + Marketing does not offer a content export. Migration is entirely manual: crawl, copy content to CSV, download images, build new WordPress site, paste content, upload images, configure URL mapping, cut DNS.

For 20 to 50 page sites timeline is 30 to 60 hours. The lack of export tooling makes GoDaddy migration the most labor intensive relative to site size.

13.5 Strikingly, Carrd, Notion Sites to WordPress

For one page sites migration is small: capture rendered HTML, download images, build new target, recreate content, configure DNS. Timeline 10 to 25 hours.

For a one page brand growing into a multi page site WordPress or Webflow is usually correct. For a brand intending to remain one page migration is usually unnecessary; rebuild on the same platform with better SEO discipline.

13.6 The URL Mapping Discipline

Every SaaS builder migration's success depends on URL mapping discipline:

1. Crawl the origin comprehensively. Capture every indexable URL.
2. Export to a spreadsheet: Origin URL, Page Type, Target URL on New Platform, 301 Required, Notes.
3. Build the new site's URL structure deliberately. Preserve origin slugs where possible. Where the platform forces a change (Wix /post/post-slug to WordPress /blog/post-slug), document.
4. For every changed URL configure a 301 redirect in the new platform's redirect system (Rank Math Redirections on WordPress, Webflow Project Settings > Hosting > 301 Redirects on Webflow).
5. Test every redirect with curl before DNS cutover.
6. After cutover monitor Google Search Console for crawl errors. Expect a temporary 404 uptick. Fix by adding missing redirects.

while IFS=',' read -r origin target; do
  status=$(curl -s -o /dev/null -w "%{http_code}" -I "$origin")
  resolved=$(curl -s -L -o /dev/null -w "%{url_effective}" "$origin")
  echo "$origin -> $status -> $resolved (expected: $target)"
done < url-map.csv

URL mapping is the single most important deliverable. SEO equity transfers through the redirect chain. Sloppy mapping leaves traffic on the floor; disciplined mapping preserves rankings. Full playbook in framework-migration.md.

14. When to Recommend Migration

14.1 Decision Criteria

The decision to migrate is a weighted set of triggers. When two or more fire, migration is usually correct.

Traffic growth: organic traffic has grown 3x or more since launch and the platform's SEO ceiling is the binding constraint. Signal: clear keyword opportunities the platform cannot serve.

SEO ceiling hit: GSC shows sustained plateau or decline despite content additions. Audit reveals platform constraints contribute.

Custom feature need: client needs a feature the platform does not offer (membership, custom LMS, advanced ecommerce logic, multi step lead capture, custom calculator, backend integration).

Multi language requirement: client expanding internationally and the platform's i18n is inadequate.

Ecommerce scale: catalog grown beyond what the commerce layer handles cleanly. Squarespace Commerce above 500 SKUs. Wix Stores above 1,000. Square Online above 500. Beyond, Shopify or WooCommerce on WordPress is usually correct.

Design control need: brand has evolved beyond what templates can express. Custom typography, interaction patterns, component library, design system requires flexibility beyond hosted builders.

14.2 The Cost Benefit Framework

Cost components: agency hours for the build (40 to 200+), content recreation (10 to 100+), image migration (5 to 30), testing and QA (10 to 30), post launch monitoring (5 to 20), opportunity cost if traffic dips. For a 50 to 100 page small business site total runs $8,000 to $25,000.

Benefit components: removed SEO ceiling, new feature capability, sometimes lower ongoing hosting cost, better performance (Core Web Vitals improvements can lift conversion 5 to 15% per HTTP Archive correlation studies 2024 sample), better design control. Usually realized over 6 to 18 months post migration. For sites with serious growth ambition migration pays back. For sites intending to remain small often does not.

14.3 The Migration Timeline

Typical small business migration:

• Week 1 to 2: discovery, intake, audit, URL inventory, content audit.
• Week 3 to 4: target platform selection, hosting provisioning, design direction.
• Week 5 to 8: build on staging. Theme/template, content migration, schema, performance baseline.
• Week 9 to 10: URL mapping finalized, redirect configuration, staging QA, GA4 and GSC preparation.
• Week 11: pre-launch review, final QA, redirect testing.
• Week 12: DNS cutover, post-launch monitoring, redirect verification.
• Week 13 to 16: post-launch monitoring, fix 404s, optimize for new platform, baseline new performance.

Under 50 pages compresses to 6 to 8 weeks. Over 200 pages expands to 16 to 24 weeks.

14.4 The "Stay on Platform" Scenarios

Stay on the SaaS builder when site is small (under 20 pages) and growth is not the primary goal; site exists for credibility rather than traffic; content team has limited capability and the editor is the only sustainable workflow; budget cannot support migration and the platform is "good enough"; site is already on the most capable platform in the category; site is part of a portfolio where standardization is more valuable than per site optimization.

For these scenarios invest in platform side optimization. Configure every per page SEO setting precisely. Inject schema through the available surface. Compress every image. Minimize platform JavaScript overhead. Document constraints and revisit the migration question annually.

14.5 The Hybrid Recommendation

A common pattern: move high traffic content to a more capable platform while keeping the marketing site on the original.

1. Origin platform (Squarespace, Wix) serves homepage, about, contact, brand pages
2. A subdomain (blog.example.com) on WordPress serves the blog
3. A separate subdomain or path (shop.example.com) on Shopify or WooCommerce serves ecommerce

Operationally more complex but allows engineering effort where it generates the most return. Works best when high traffic content is logically separable from the brand site.

Risks: cross domain schema and Organization continuity, hreflang complexity if multilingual, brand consistency, operational overhead of two platforms. Mitigate via consistent design tokens, consistent Organization schema declared on both with the same @id URI, consistent NAP and brand mentions.

14.6 The Final Recommendation Framework

For every engagement the final recommendation falls into one of four buckets:

1. Optimize and stay: the platform is the right choice; push it to the ceiling.
2. Optimize now, migrate later: acceptable today; document migration triggers and revisit annually.
3. Migrate now: the platform is the binding constraint; benefit justifies cost.
4. Hybrid: keep the platform for the brand site; move high traffic content elsewhere.

The right recommendation depends on the client's growth ambition, budget, team capability, risk tolerance. The intake in Section 2 surfaces the variables. The criteria in 14.1 surface the triggers. The cost benefit framework in 14.2 quantifies the tradeoff.

Document the recommendation in the engagement's strategic plan. Revisit at every annual review. Conditions change; the right answer at engagement start is not always the right answer eighteen months later.

End of Framework

Cross references:

• framework-cross-stack-implementation.md
• framework-schema.md
• framework-hreflang.md
• framework-international.md
• framework-migration.md
• framework-pageexperience.md
• framework-technicalseo.md
• framework-mobileseo.md
• framework-aicitations.md
• framework-aioverviews.md
• framework-webflow.md
• framework-wordpress.md
• framework-ecommerceseo.md