Salesman Hal

AI agents on Webflow, Wix and Squarespace

Hosted site builders take the server off your hands, which is the point. It also means you can’t change everything AI agents look at. Here’s what Webflow, Wix and Squarespace let you control today, the workarounds for what they don’t, and where the honest limits are.

Updated

At a glance

As of November 2026. Plan names and menus change often, so check your own dashboard.

Webflow Wix Squarespace
Edit robots.txt Yes, Site settings → SEO Yes, Robots.txt Editor Checkboxes only (Crawlers panel)
Site-wide head code Site settings → Custom code; check your plan Settings → Custom Code; needs a connected domain Code Injection, on Core, Plus, Advanced and some legacy plans
Your own file at /.well-known/ Not documented Not documented Not documented
Redirect a path to another domain Not always accepted; test it Yes, URL Redirect Manager Yes, URL mappings
llms.txt Upload your own Generated for you on eligible sites; editable Write your own (version 7.1); off by default
Cloudflare proxy in front Yes, through Cloudflare’s orange-to-orange setup No; DNS-only records Yes, per Cloudflare’s docs, with the verification record DNS-only
Native booking None built in; embed a scheduler Wix Bookings Acuity Scheduling (formerly Squarespace Scheduling)

Letting AI crawlers in

robots.txt is the file AI crawlers and assistants check first to see what they may read. On a builder, you either edit it directly or flip a switch that edits it for you. Our robots.txt guide lists the AI user agents and what each one is for.

  • Webflow: the robots.txt rules live in Site settings → SEO → Indexing, and changes reach the live file only when you publish the site. If you see any bot or AI-crawler toggles there, check they aren’t blocking assistants you want.
  • Wix: in the dashboard, go to SEO & GEO → Tools and settings → Robots.txt Editor → View File, add your rules and save. “Reset to Default” undoes it. Wix calls this an advanced feature and its support team won’t troubleshoot your edits. For page-level control, a page’s Advanced SEO settings offer a nosnippet option, which stops that page’s text being used directly in AI overviews.
  • Squarespace: Settings → Crawlers has a “Block known artificial intelligence crawlers” checkbox, off by default. Ticking it adds rules for a fixed list of 26 bots. Most are training crawlers (GPTBot, ClaudeBot, CCBot, Google-Extended), but the list also includes DuckAssistBot, Amazonbot and Meta-ExternalAgent, so ticking it shuts out more than training. ChatGPT-User isn’t on the list. Squarespace’s help doesn’t describe editing robots.txt line by line, and you can’t block crawlers for only some pages.

Custom head code and plan limits

Most AI-readiness work needs a little code in every page’s <head>: structured data, a <link rel="mcp"> tag pointing to an MCP server, or a script. All three builders have a box for it, but not on every plan.

  • Webflow: site-wide code goes in Site settings → Custom code, with separate head and footer boxes, and per-page code goes in each page’s settings. Publish the site afterwards. Custom code is generally a paid feature, so check your site or workspace plan.
  • Wix: Settings → Custom Code (under Development & integrations). Code can go in the head, the start of the body or the end of the body, on all pages or chosen ones. The site must be published with a connected domain, which on Wix generally means a paid plan. Two gotchas: changing the site’s domain deletes your snippets, and since December 2025 Wix’s frontend security measures may block some third-party snippets until their makers update them.
  • Squarespace: Website Tools → Code Injection, with a Header box (inside <head> on every page) and a Footer box (before </body>). It’s on the Core, Plus and Advanced plans and some legacy ones. Each page also has its own header injection under the page’s gear icon → Advanced. Checkout pages don’t take custom code.

Discovery files: why redirects

AI agents that look for an MCP server check fixed addresses under /.well-known/, such as /.well-known/mcp. (Our MCP discovery guide explains the formats.) On your own server you’d just put the files there. None of these three builders documents a way to host your own file under /.well-known/, so the workaround is a redirect from that path to wherever the file really lives, such as your MCP provider.

  • Wix: SEO & GEO → Tools and settings → URL Redirect Manager. Enter the old path and, for an external destination, the full URL. You can’t redirect the homepage, and the limit is 5,000 redirects.
  • Squarespace: Developer tools → URL mappings, one rule per line, with the destination starting https://. Paths can’t contain ? or #, and image and file URLs can’t be redirected.
  • Webflow: 301 redirects are in the site settings, but whether a full URL on another domain is accepted as the destination has varied. Try it; if it won’t save, skip this step and rely on the head tag.

On Squarespace, the rules look like this (your MCP provider gives you the real addresses):

/.well-known/mcp -> https://ADDRESS-FROM-YOUR-HAL-SETUP-PAGE 301
/.well-known/mcp.json -> https://ADDRESS-FROM-YOUR-HAL-SETUP-PAGE 301
/.well-known/mcp/server-card.json -> https://SERVER-CARD-ADDRESS 301

Two honest caveats. None of the three builders documents redirects for /.well-known/ paths specifically, so open each address in a private window after publishing and check you land on JSON. And not every agent follows a redirect for a discovery file. That’s why the <link rel="mcp"> tag in your head code matters: agents that read the page find the server without the redirect.

Cloudflare in front, or not

Putting Cloudflare’s proxy in front of a site lets you run code at the edge (serve real files at /.well-known/, add tags to pages, log every AI agent request), which gets around most builder limits. Whether you can depends on the platform. Our Cloudflare guide covers the settings.

  • Webflow: Cloudflare documents an “orange-to-orange” setup for Webflow sites, available on any Cloudflare plan: a proxied CNAME to Webflow, after which caching, Rules and Workers can apply to the site’s traffic.
  • Wix: doesn’t support proxied DNS records for domain connections. Cloudflare can handle the domain’s DNS only, with every record set to DNS-only. So no edge code and no edge logs for Wix sites.
  • Squarespace: Cloudflare’s docs say the A records and the www record can be proxied, but the verify.squarespace.com record must stay DNS-only or Squarespace can’t verify the domain. Squarespace treats Cloudflare as outside its support.

Structured data

Structured data (schema.org JSON-LD) states your business’s name, address, phone, hours and services in a form machines read without guessing. Here’s a LocalBusiness example; Plumber is one of schema.org’s many specific business types:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Plumber",
  "name": "Example Plumbing",
  "url": "https://example.com",
  "telephone": "+1-555-555-0100",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "12 Main Street",
    "addressLocality": "Springfield",
    "addressRegion": "IL",
    "postalCode": "62701",
    "addressCountry": "US"
  },
  "areaServed": "Springfield and surrounding towns",
  "openingHoursSpecification": [{
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
    "opens": "08:00",
    "closes": "17:00"
  }]
}
</script>
  • Wix adds some markup itself: LocalBusiness on the homepage once you’ve entered a business name and location, and preset markup on Wix Bookings service pages, Stores products, Blog posts and Events. You can add your own JSON-LD in a page’s SEO settings (Advanced SEO → Structured Data Markup), or for a whole page type in SEO Settings. Each markup must be under 7,000 characters, with up to five per page.
  • Webflow: paste the script into the page’s head code (Page settings), or the site-wide head for business details that apply everywhere.
  • Squarespace: use Code Injection: the site-wide Header for business details, or a page’s own header injection for a service page or FAQ.

Whatever you mark up must match what’s visible on the page, and the facts should agree with your Google Business Profile and directory listings.

Forms and native booking

Builder forms are built for people in browsers. A browser agent can usually fill them in if every field has a clear visible label, required fields are marked and error messages say what’s wrong. Agents that don’t run a browser have a harder time: these forms are typically sent by the platform’s own JavaScript, so there’s no plain address to post to. Keep your phone number and email in plain text on the contact page as a fallback, and keep consent checkboxes for the person to tick.

Booking is where the platforms differ most:

  • Wix Bookings is built in, and its service pages carry preset structured data, which helps agents understand what you offer.
  • Squarespace Scheduling is now Acuity Scheduling. You add it to a page with a Scheduling block; the legacy free Acuity plan doesn’t support embedded schedulers, so you need a paid plan. Because it’s Acuity, any tool that works with Acuity works with it.
  • Webflow has no booking of its own, so most sites embed Calendly, Cal.com or similar. Put a plain link to the scheduling page next to the embed for agents that don’t run scripts.

One thing that isn’t what it sounds like: Squarespace’s “Connect Squarespace to an AI assistant” connector is for owners and staff (domain search and managing store orders from Claude or ChatGPT), not for a visitor’s assistant to contact or book your business.

llms.txt on each platform

llms.txt is a proposed plain-text summary of your site at /llms.txt. No major assistant has said it relies on it; see our llms.txt guide. If you want one:

  • Wix generates and maintains it for you on sites that are upgraded, have a custom domain connected and have search indexing on. Find it at SEO & GEO → Tools and settings → Go to llms.txt. Editing it stops the automatic updates; “Reset to Default” turns them back on; a “Use your llms.txt file” toggle hides it.
  • Squarespace (version 7.1): SEO/AI Visibility → SEO Settings → LLMS.txt tab. It’s off by default and you write the text yourself.
  • Webflow lets you upload an llms.txt file in the site’s SEO settings. Look for it in Site settings, and check Webflow’s help center for the current size limit.

The honest analytics limits

Many AI agents fetch the HTML of a page and nothing else. They don’t run JavaScript, so ordinary analytics never see them. On your own server, logs record every request; on a hosted builder there are no server logs for you to read. So:

  • Script-based analytics (the builder’s own, or Google Analytics) see people and the few browser agents that run scripts, not crawlers or assistants fetching pages.
  • A tracking pixel (a 1×1 image) also counts agents that load images. That’s more, but many AI fetchers request only the HTML.
  • “AI traffic” reports usually mean people who clicked through from ChatGPT or similar, not agent visits. Squarespace’s Traffic Sources shows traffic from AI tools in this sense; its AI Visibility tool checks how often AI tools mention you, using AI credits.
  • Full coverage needs Cloudflare in front, which rules out Wix. On Webflow and Squarespace, Cloudflare’s logs or a Worker see every request.

Our guide to measuring AI agent traffic goes deeper. The short of it: on Wix especially, measure what agents do (inquiries and bookings) rather than how often they visit.

What to do now

  1. Check crawler access: read your robots.txt, and on Squarespace decide whether the AI crawler checkbox blocks more than you want.
  2. Add LocalBusiness structured data and check it matches your Google Business Profile.
  3. Tidy your contact form and booking page: clear labels, a plain booking link, phone and email in text.
  4. Decide on llms.txt, which is a few minutes’ work on all three.
  5. Give agents a way to act without a browser: an MCP server, a head tag pointing to it and redirects for the discovery paths.
  6. Run our free AI-readiness scan to check the lot.

How Salesman Hal handles hosted builders

In the Hal dashboard, add your site as “Any other site” and you get a short head snippet (the <link rel="mcp"> tag and Hal’s WebMCP script), a 1×1 pixel for the end of the body, and the three discovery redirects to paste into Wix’s URL Redirect Manager or Squarespace’s URL mappings. Hal verifies the site by finding the snippet on your homepage, then reads your pages and re-reads them daily. Agents’ inquiries go into HubSpot form embeds or plain HTML forms that post to an address; Webflow’s own forms, forms behind a CAPTCHA and other script-driven builder forms get the inquiry by email instead. Bookings go to Calendly, Cal.com, SavvyCal, Acuity (including former Squarespace Scheduling accounts) or HubSpot Meetings; Wix Bookings isn’t supported yet. Webflow and Squarespace sites behind Cloudflare can install Hal’s Cloudflare Worker instead, which serves the discovery files and logs every AI agent request.

See how Hal works

FAQ

Can I upload files to /.well-known/ on Webflow, Wix or Squarespace?

None of the three documents a way to. Use redirects from those paths to where the files really live, plus a link rel="mcp" tag in your head code, or put Cloudflare in front (Webflow and Squarespace only) and serve them from there.

Does Squarespace’s AI crawler checkbox stop ChatGPT finding me?

It blocks GPTBot and a list of other bots, but ChatGPT-User isn’t on that list. It does include some assistant and search bots, such as DuckAssistBot and Amazonbot, so read the list before ticking it.

Why does Wix matter for Cloudflare?

Wix doesn’t support proxied Cloudflare records, so nothing can run at the edge in front of a Wix site. That rules out edge logging and serving real discovery files; you’re left with head code, redirects and a pixel.

Do I need a paid plan?

For site-wide custom code, generally yes on all three; Wix also needs a connected domain. Check your own plan, as names and limits change.

Will I see AI agent visits in my builder’s analytics?

Mostly not. Builder analytics run in the browser, and many AI agents don’t run JavaScript. AI traffic reports usually count people who clicked through from an AI tool.

Is llms.txt worth it?

It’s cheap on all three platforms, but no major assistant has said it relies on it. Crawler access, accurate structured data and clear pages matter more.

Sources

Further reading

Let AI agents reach you, whatever your site’s built with.

Hal adds an MCP server to Webflow, Wix and Squarespace sites with one snippet. Free during early access.

Or run the free AI-readiness scan first.