BridgeToAgent
Get the kit — $49
All posts
Explainer8 min read

The 2026 agent-ready Squarespace and Wix checklist — both platforms, same install gate, same fix

Squarespace and Wix share the same agent-readiness shape — native Schema on most templates, no native file-layer for agents, and an install path that depends on which plan tier you're on. The good news is both platforms have the same workaround (Cloudflare Worker in front of either one) and the same four-surface checklist works on both. Here's the combined walkthrough.

BridgeToAgentEditorial team

The 2026 agent-ready Squarespace and Wix checklist — both platforms, same install gate, same fix

Squarespace and Wix sit in a similar spot in the agent-readiness landscape — both are template-driven platforms aimed at non-technical builders, both ship native Schema on most modern themes, and both lock the install paths an agent-readiness kit needs behind paid plan tiers. The buyer who runs Lighthouse Agentic Browsing on a Squarespace or Wix site usually hits the same three findings: Schema present (good), llms.txt + agents.json + agent-instructions.md missing (the gap), and the install needs a workaround because the platform doesn't let you upload arbitrary root-served files.

This is the combined four-surface checklist. Both platforms appear in one post because the platforms share the same agent-readiness shape — the failures are the same, the fix paths are the same, and the only thing that meaningfully differs between them is the click-path inside each editor.

The 30-second version

Surface 1 — Schema markup. Both platforms ship Schema on modern templates. Verify with Google's Rich Results Test on three pages. Plan-tier matters for advanced overrides on both.

Surface 2 — The three kit files. Cloudflare Worker in front of your site is the recommended path on both — works on every plan, takes about 15 minutes once. Alternatively, on Wix Premium / Squarespace Business+, Code Injection + external file hosting gets the discovery snippet shipped without DNS changes (but not true root URLs). The Wix install guide and Squarespace install guide cover both paths.

Surface 3 — Structured content cleanliness. Both platforms have less structured-content depth than Webflow, but the parts they have (Wix Stores / Squarespace Commerce products, Blog posts) emit Schema directly from the data. Audit for missing product fields, draft items that ended up published, and unused tags inflating the taxonomy.

Surface 4 — WebMCP readiness. Not actionable yet for either platform in 2026. Track the spec, don't sink hours.

The work is genuinely under an hour for either platform once the Cloudflare DNS step is done. The 4-surface walkthrough below covers what to verify and where the platform-specific gotchas live.

Why these two platforms in one post

The agent-readiness conversation usually treats Squarespace and Wix as different problems. They have different editors, different pricing, different design conventions, different e-commerce modules. From an agent's perspective, though, the surfaces look almost identical:

  • Both ship modern Schema on default themes (similar coverage to mid-tier Shopify themes)
  • Neither lets you upload arbitrary files at /agents.json style root paths
  • Both have a paid-plan tier that unlocks the Code Injection / Custom Code feature you need to ship the discovery snippet
  • Both work cleanly behind Cloudflare with a single Worker that serves the three files — the same Worker code works on either platform

That's the angle this post takes: not "Squarespace vs Wix" but "the agent-readiness pattern for either of these template-driven platforms, and the install path that works on both."

Surface 1 — Schema markup

What both platforms ship natively.

  • Squarespace. Modern Squarespace 7.1 templates emit Article Schema on blog posts, Product Schema on Commerce products (with Offers, Price, Currency, Availability), Organization Schema sitewide, and BreadcrumbList on navigation hierarchy. Older Squarespace 7.0 templates ship less — verify before assuming.
  • Wix. Modern Wix Editor and Wix Studio templates emit similar coverage — Article Schema on blog posts, Product Schema on Wix Stores products, Organization Schema sitewide. Coverage is slightly less consistent than Squarespace because Wix has multiple editor generations active at once (Wix ADI, Wix Editor, Wix Studio, EditorX legacy).

Where the native Schema isn't enough on either platform.

  • FAQ Schema. Neither platform ships a native FAQ block that emits FAQPage JSON-LD. If you have FAQ content, ship the Schema manually via Code Injection (Squarespace) or Custom Code (Wix).
  • HowTo Schema. Same gap on both — manual JSON-LD via header code if you have tutorial content.
  • Per-page Schema overrides. Both platforms gate granular Schema control behind upper-tier plans (Squarespace Commerce Advanced / Wix Premium VIP or Business Unlimited).

Checklist for Surface 1:

  1. Test three URLs against Google's Rich Results Test. Pick your homepage, one blog post (if you have one), and one product page (if you have Commerce / Stores).
  2. Verify the homepage shows Organization schema. Both platforms emit it sitewide.
  3. Verify blog posts show Article and product pages show Product with offers populated.
  4. For any FAQ-style pages, add FAQPage Schema manually via the platform's code injection feature. The Schema.org reference has a copy-paste template.

Time required: 10 minutes to verify, longer if you need to backfill Schema on legacy themes.

Heads-up. Wix and Squarespace both occasionally ship sample Schema with placeholder values (e.g. description: "Lorem ipsum...") on freshly-installed templates. Check your homepage Schema output isn't shipping the template's default text — if it is, fill in your real Organization details in the site settings.

Surface 2 — The three kit files

This is the surface neither platform ships and the surface most directly determined by which plan tier you're on. Both platforms have the same two install paths.

Path 1 (recommended on both) — Cloudflare Worker in front.

This works on every Wix and every Squarespace plan, including the free / personal tiers. The setup is a one-time DNS move to Cloudflare plus a single Worker that serves the three files at the root paths your domain resolves through. The trade-off is that you need to move your DNS to Cloudflare (free plan is fine for this) and accept Cloudflare sitting in the request path — which is fine for the vast majority of small sites and often improves performance via Cloudflare's edge caching.

Full step-by-step: Wix install guide Option A or Squarespace install guide Option A. The Worker code is identical between the two — same JavaScript, same Triggers → Routes configuration, only the domain differs.

Path 2 — Platform Code Injection (paid tier required).

If you can't move DNS, the alternative is Code Injection (Squarespace, Business plan and above) or Custom Code (Wix, Premium plans and above). This gets the <link rel="alternate"> discovery tags into your <head> so well-behaved AI agents can find the files at the URLs you point them at — typically GitHub Gists, Netlify Drop, S3, or Cloudflare R2.

The trade-off: the URLs aren't true root paths (/agents.json etc.), so some less-sophisticated AI crawlers that hard-code root-path probing might miss them. Most agents follow the discovery <link> tags fine.

Checklist for Surface 2:

  1. Generate the three files. The BridgeToAgent kit does this in two minutes from a real crawl of your site ($49 one-time). The kit's audit reads your existing Schema and structured content to populate the files with real data.
  2. Pick your path. If you're on the free or personal tier of either platform, Cloudflare Worker is your only option for true root-served files. If you're on a paid tier, both options work — Cloudflare is still cleaner long-term but Code Injection is faster to ship.
  3. Follow the platform-specific install: Wix guide or Squarespace guide.
  4. Verify each URL serves the file content (Cloudflare path) or that the <link rel="alternate"> tags appear in View Page Source (Code Injection path).

Time required: 15-30 minutes for the Cloudflare path including DNS setup, 10 minutes for the Code Injection path.

Heads-up. The Cloudflare Worker has a slightly tedious initial step (pasting the file contents into the Worker code). If your kit regenerates frequently, write a small build script that auto-updates the Worker via Cloudflare's API. For most sites the kit is generated once and updated quarterly at most — the manual paste is fine for that cadence.

Surface 3 — Structured content cleanliness

Both platforms have less structured-content depth than Webflow or WordPress — Wix Stores / Squarespace Commerce are simpler than WooCommerce or Shopify, and the blog modules are less customizable than WordPress's. That's a feature for the non-technical builder, but it means the structured data both platforms emit is only as good as the content you put in.

Checklist for Surface 3:

  1. Audit Commerce/Stores product fields. On Wix Stores: Product Catalog → check every product has Description, Image, Price, SKU, Categorization filled. On Squarespace Commerce: Commerce → Products → same check. Empty fields ship as empty Schema, which gives agents an incomplete picture.
  2. Audit blog post Categories and Tags. Both platforms make it easy to create new tags inline while writing a post, which leads to taxonomy sprawl over time ("AI", "AI agents", "ai", "Artificial Intelligence" all meaning the same thing). Consolidate variations.
  3. Unpublish or delete sample content. Squarespace ships templates with sample posts ("Sample Blog Post 1", "Sample Product"); Wix ADI does the same. These sometimes survive into production. Delete them — agents read them as honest data and surface them, which makes your site look unfinished.
  4. For Squarespace specifically: Check that your Site Title and Site Tagline (Settings → Site Identity) are filled in with real values, not template defaults. These propagate into Organization Schema.
  5. For Wix specifically: Check the Business Info section (Settings → Business Info) — Wix uses this for Organization Schema. If it's blank or partially filled, the Schema ships with gaps.

Time required: 15-30 minutes for a typical SMB site, longer if you have a large product catalog that's accumulated content debt.

Heads-up. Both platforms have "draft" states for blog posts and products that are easy to misread. A draft saved months ago can ship to production accidentally if the page template is published and the item state defaults to live on save. Check the actual published state of each item, not just the page status.

Surface 4 — WebMCP readiness (the forward-looking one)

Same story as for every other major platform in 2026. WebMCP is the emerging spec for per-element agent-callable annotations. Chrome 146 ships the browser-level API; Edge 147 follows.

Neither Squarespace nor Wix ships WebMCP-aware blocks in their editors. The Lighthouse webmcp-annotations audit fails on virtually every site on either platform, including the ones doing everything else right. The audit is low-weighted because the spec is still moving.

What to do for Squarespace or Wix today: track the spec, don't manually annotate the platform-rendered HTML (you usually can't reach it cleanly anyway). The BridgeToAgent kit plans WebMCP-annotated output as a version 1.3 add-on once annotation conventions stabilize.

How to verify the full picture

After working through the three actionable surfaces:

  1. Run the free BridgeToAgent audit on your site. Five-second readiness check, no email needed. Detects native Schema output and reports which kit files are present.
  2. Run Chrome Lighthouse Agentic Browsing on your homepage and one inner page. Chrome DevTools → Lighthouse → enable "Agentic Browsing" → Analyze. With the kit files installed and Schema clean, expect to pass six or seven of nine audits. The remaining failures (webmcp-annotations always; possibly sitemap-discoverable on Wix free-tier sites that have a thin sitemap) are platform-shaped.
  3. Run Cloudflare's isitagentready.com as a cross-check.

Common platform-shaped mistakes

  • Squarespace: trying to upload files via "Files" in the editor. Squarespace's Files area renders content as HTML, which corrupts the JSON in agents.json. The install requires Cloudflare Worker (true root) or Code Injection (discovery via header <link> tags). There's no native uploads-to-root option.
  • Wix: assuming Velo development is required. Velo (Wix's developer environment) can serve files dynamically but the install is much faster via Cloudflare Worker for the non-technical builder. Velo is overkill for this use case.
  • Both: forgetting that the install path locks behind a paid plan tier. Code Injection on Squarespace requires Business plan; Custom Code on Wix requires Premium. Free and personal tiers on both platforms only have the Cloudflare-front-of-site option (and the prereq DNS move).
  • Both: Cloudflare DNS migration breaking unrelated email or routing. If your domain handles email or third-party integrations through DNS records, double-check Cloudflare imported them correctly before changing nameservers. The most common failure mode here is MX records not migrating cleanly.

What to do this week

  1. Identify your plan tier. Squarespace Business+ or Wix Premium = both install paths available. Below those tiers = Cloudflare Worker is the only path to true root-served files.
  2. Run the free BridgeToAgent audit on your site. No email needed.
  3. Pick the install path that matches your plan and infrastructure preferences.
  4. Ship the three kit files via the Wix install guide or Squarespace install guide.
  5. Verify Surface 1 with Google's Rich Results Test on three pages.
  6. Audit your structured content (Commerce products, blog tags, sample content) for the failure modes above.
  7. Re-run Lighthouse Agentic Browsing in 14 days to confirm audits flipped.

Both platforms reward the small amount of one-time setup with a full agent-readiness layer that compounds for as long as the site lives. The Cloudflare-front-of-site approach also gives you edge caching and DDoS protection as side benefits — bigger wins than the kit install alone.

Related

Keep reading

All posts →