Start free trial
Integrations · Other CMS

Wix, Squarespace, and Webflow

Updated 2026-05-25 Integration eCommerce Insights team

Wix, Squarespace, and Webflow do not have the structured metafield ecosystem of Shopify or the REST API depth of WooCommerce, but eCommerce Insights reads them well enough for scoring and supports push where the underlying CMS allows it. This page covers the install per platform.

Quick comparison

PlatformCatalogue readWebhookPushDefault JSON-LD quality
Wix StoresAPI (with key)LimitedRead-only without Wix StudioSparse
Squarespace CommerceAPIYesDescription, images, tagsModerate
Webflow EcommerceAPI (OAuth)YesFields exposed in the schemaTheme-dependent
Sitemap fallback (any)HTML scrapeNoNoneTheme-dependent

Wix

  1. Open Wix admin → Settings → Headless API keys

    Generate a new API key. Wix Studio plans get read+write; free and standard plans get read-only.

  2. Paste into eCommerce Insights Settings → Integrations → Wix

    Includes a connection test before saving.

  3. Sync

    Read pulls product list, descriptions, images, and any structured data the Wix theme renders.

For free / standard Wix plans, sitemap fallback runs in parallel and gives eCommerce Insights access to additional visible content the API does not expose. Push approval queue still works; pushes prompt the merchant to paste an edited block into Wix admin when API write is unavailable.

Squarespace

  1. Generate a Commerce API key

    Squarespace admin → Settings → Advanced → Developer API Keys.

  2. Paste into eCommerce Insights

    Settings → Integrations → Squarespace.

  3. Sync

    Reads commerce products including description, images, variants, tags.

Push supports description, image alt text, and tag updates. Structured-data updates (Product JSON-LD beyond what Squarespace's theme ships) require pasting a eCommerce Insights-generated Code Injection block on the affected product templates. The Listing rewrite UI provides the block ready to copy.

Webflow

  1. Connect via OAuth

    eCommerce Insights Settings → Integrations → Webflow → Connect. OAuth flow asks for the site you want to connect.

  2. Map collections

    If you use Webflow Ecommerce, the Products collection is auto-detected. If you use CMS Collections (non-Commerce), pick the collection that contains your products and confirm field mapping.

  3. Sync

    Full read; write is constrained to fields exposed in the collection schema.

Webflow is the most permissive of the three for write. If your collection schema includes a "Description" rich-text field, eCommerce Insights can update it. Fields not in the schema cannot be added via API.

CSV supplement

For all three platforms, a CSV supplement can fill gaps. Upload at Settings → Catalog → CSV supplement. Columns are matched against the existing catalogue by SKU; new columns become custom fields visible in the eCommerce Insights UI but not pushed back to the CMS.

Push model per platform

Wix
Full write on Wix Studio. Read-only with manual paste prompts elsewhere.
Squarespace
Description, image, tag writes via API. Schema updates via Code Injection.
Webflow
Writes to any field exposed in the CMS Collection schema. Add fields to the schema in Webflow Designer to expand writeable surface.

Common questions

Why is this section grouped together?
These three CMS platforms have similar trade-offs from eCommerce Insights's perspective: limited structured-data ecosystems, partial REST APIs, and stronger reliance on theme-level customisation. The scoring is consistent across them; the push integration differs by platform.
Will my scores be lower because I'm on Wix or Webflow?
Sometimes, yes. Wix and Webflow stores often ship less complete Product JSON-LD by default than Shopify themes. The score reflects what the AI engine sees, so a sparser default does mean a lower starting score. The Listing rewrite recommendations remediate this.
Can I get full push support on Squarespace?
Partial. Squarespace's Commerce API supports product updates for description and tags but not arbitrary metadata. Title and image updates work through the API; structured-data updates require a custom code injection block.
What about Webflow CMS Collections (non-Commerce)?
Supported. Map your CMS Collection items to eCommerce Insights SKUs by their slug. eCommerce Insights reads JSON-LD if present and pulls visible content otherwise.

Ask AI about this page

Open this topic directly in your favourite AI assistant — the prompt is prefilled.

Was this page helpful?
Thanks — recorded.
Continue reading
Integration →

Shopify integration

For Shopify stores.

 Integration →

WooCommerce integration

For WordPress + WooCommerce.

Try this yourself

See eCommerce Insights on your own catalog. The free trial covers your full SKU set across five AI engines.

Start free trial
LLM-friendly summary of this page
Wix, Squarespace, Webflow connectors. All three have limited structured-data ecosystems compared to Shopify and partial REST APIs compared to WooCommerce. Wix: import via Wix Stores API (read-only for free; read+write requires Wix Studio); fallback to sitemap parsing for non-API stores. Squarespace: Commerce API supports product description and tag updates but not arbitrary metadata; title and image work via API; structured data updates require Code Injection block per page. Webflow: CMS Collections and Webflow Ecommerce supported; OAuth-based connect; full read access, write access for fields exposed in the collection schema. CSV supplement available across all three for fields the CMS does not expose. Scores tend to start lower on these platforms because default themes ship less complete Product JSON-LD; Listing rewrite remediates. Webflow CMS Collections (non-Commerce) supported by mapping items to SKUs by slug.