Blog/Plain-English Guide
PLAIN-ENGLISH GUIDE

Does Your Website Builder Hurt Your AI Visibility? The One Setting That Can

A broad open-frame desktop 3D printer in matte near-black with thin amber rims seen straight on in a deep blue void, its print head above one small blank cube glowing warm amber on the build plate

Key Takeaways

  • Stop blaming the builder. Squarespace, Wix and WordPress can all produce a site an assistant reads. The name of the tool is rarely what keeps a business out of an answer.
  • Check one setting today. Each builder has a switch that asks crawlers to stay away. It takes two minutes to find, and it is the only builder problem that can hide a whole site.
  • Read your own page source. Search it for one sentence from your services page. If the sentence is there, an assistant can read it. If not, something you added is in the way.
  • Look hardest at what you bolted on. Booking widgets, review carousels and text set inside images are where builder sites lose words. The builder did not put them there.
  • Do not move sites to fix this. A rebuild costs weeks and changes nothing an assistant cares about unless the words change too. Fix the words where they are.

Somebody told you that your site is the problem. A designer said Squarespace sites "don't work for AI". A forum said Wix is invisible. A developer offered to rebuild the whole thing on WordPress for a few thousand dollars.

Does your website builder hurt your AI visibility? Almost never, and not in the way those people mean. The builder decides very little of what an assistant reads. You decide most of it, including one switch that is worth two minutes of your day.

Below is the short answer, what the builder controls and what you control, the one setting to check on each of the three big builders, where builder sites really do lose words, and whether moving is ever worth it.

Does your website builder hurt your AI visibility?

Rarely. Squarespace, Wix and WordPress all produce pages an assistant can read. A website builder hurts your AI visibility in three specific cases: a setting is asking crawlers to stay away, your words only exist inside images or add-ons, or the pages never state the facts a buyer asks about. Only the first is the builder's doing.

An assistant does not know or care what built your page. It gets a page of text, the same way it gets one from any other site. If the text is there and nothing has asked it to leave, the builder has done its job.

That is why two coaches on the same builder, with the same template, can get opposite results. One is named and the other is not. The tool is identical. The words are different. The broader version of that argument is in whether a great website means AI will recommend you.

What the builder decides, and what you decide

The builder decides how your page is put together and offers you a few switches. You decide what the page says, what you add to it, and where those switches sit. Nearly everything that affects an AI answer is on your side of that line.

On the builder's side: how fast the page loads, whether it works on a phone, and whether it gives you a way to edit the page title and description. All three big builders handle these well enough that they are not the reason you are missing from an answer.

On your side:

  • The switch. Whether crawlers are asked to stay out. Covered in the next section.
  • The words. Whether a page says who you work with, where, what it costs and what you are qualified in.
  • The format of the words. Typed text, or a picture of text, or text inside a widget from another company.
  • Everything off the site. Directories, profiles and reviews that an assistant reads alongside your pages.

Squarespace's own help page on AI-powered search engines makes the same split. When we read it on October 9, 2026, its first piece of advice was to confirm you have not limited AI crawlers. Most of the rest was about content: clear language, short paragraphs, lists, tables and questions with answers. Those are things you type, on any builder.

The one setting to check on each builder

Each builder has one place where a site can ask crawlers to stay away, and it should be off. On Squarespace it is a checkbox. On Wix it is lines in a file. On WordPress it is a checkbox aimed at search engines. The figure shows where each one lives.

ONE SWITCH PER BUILDERSOURCE: EACH BUILDER'S HELP PAGES, READ OCT 9, 2026
  1. Squarespace

    Where it lives

    Settings, then Crawlers

    What it is called

    Block known artificial intelligence crawlers

    Leave it unchecked

    If it is checked, the site asks every crawler on Squarespace's list to stay out.

  2. Wix

    Where it lives

    SEO settings, then Robots.txt Editor

    What it is called

    Disallow lines that name an AI crawler

    Leave them out

    If they are there, each crawler named is asked to skip the whole site.

  3. WordPress

    Where it lives

    Settings, then Reading

    What it is called

    Discourage search engines from indexing this site

    Leave it unchecked

    If it is checked, every page carries a tag asking search engines not to list it.

Three builders, one switch each, and the same resting position on all three: off.

answerhalo.com
One switch per builder, from each builder's own help pages as read on October 9, 2026. Squarespace: under Settings, then Crawlers, the checkbox is called "Block known artificial intelligence crawlers". Leave it unchecked. If it is checked, the site asks every crawler on Squarespace's list to stay out. Wix: under SEO settings, then Robots.txt Editor, look for Disallow lines that name an AI crawler. Leave them out. If they are there, each crawler named is asked to skip the whole site. WordPress: under Settings, then Reading, the checkbox is called "Discourage search engines from indexing this site". Leave it unchecked. If it is checked, every page carries a tag asking search engines not to list it. Three builders, one switch each, and the same resting position on all three: off.
The setting that can ask crawlers to stay away, on Squarespace, Wix and WordPress, from each builder's help pages as read on October 9, 2026
Builder Where it lives What it is called How it ships What to do
Squarespace Settings, then Crawlers "Block known artificial intelligence crawlers" Unchecked by default, per its help page Leave it unchecked
Wix SEO settings, then Robots.txt Editor Disallow lines naming an AI crawler Described as something the owner adds. The help page does not state a default Leave them out, or remove the ones naming crawlers you want
WordPress Settings, then Reading "Discourage search engines from indexing this site" A checkbox you or a developer sets. Often checked while a site is being built Leave it unchecked once the site is live

The details matter, so here they are with their sources. Squarespace's help page on asking AI models to exclude your site says the box is unchecked by default, and gives the reason: checking it could cost a site traffic by keeping it out of chat answers. The list of crawlers on that page ran to 26 names when we read it, including GPTBot and ClaudeBot.

Wix's help page on blocking AI crawlers walks an owner through adding the lines by hand. The menu was labeled "SEO & GEO" when we read it. Its example list includes ChatGPT-User, which OpenAI describes as the visitor that fetches a page when a person asks ChatGPT about it. Copying that example in full blocks more than training.

That is the trap in all three. "Block AI" sounds like one decision and it is several. OpenAI's page on its crawlers lists them separately: GPTBot collects pages that may be used for training, and OAI-SearchBot is the one that decides whether a site is shown in ChatGPT search answers. It says a site opted out of OAI-SearchBot will not be shown in those answers. Blocking the first is a choice about training. Blocking the second removes you from the answer. More on the difference is in what GPTBot is.

WordPress is the odd one out. Its Reading settings page says the checkbox adds a tag to every page asking search engines not to index the site. Developers check it while building, and sometimes nobody unchecks it. It is aimed at search engines, not assistants, but Google's guide to AI features says a page must be indexed to appear in AI Overviews, so the effect carries over.

Where builder sites really lose words

Builder sites lose words in the things owners add, not in the builder. The three usual places are text set inside an image, content that loads from another company's widget, and sections that only appear after a visitor clicks. A crawler that does not run scripts or read pictures gets none of them.

The evidence for the script part is a study of AI crawler traffic published by Vercel, with the consultancy MERJ, on December 17, 2024. Watching requests across Vercel's own network, it reported that none of the major AI crawlers it tracked ran JavaScript, which is the code that makes a page fill in after it loads. That is one company's traffic, and it is nearly two years old. Treat it as a reason to check, not a law.

Here is the check. Open your services page, right-click, and choose "View page source". Search that text for one full sentence from the page. Do it three times:

  1. A sentence from your main description. If it is missing, the page itself has a problem and your builder's support team should hear about it.
  2. A price or a package name. These often live in a pricing widget or a designed image, and go missing.
  3. One line from a testimonial. Review carousels are the most common add-on that leaves nothing in the source.

Whatever is missing, type it onto the page as ordinary text as well. You do not have to remove the widget or the image. The full version of this, with six checks and a clock, is in how to audit your own website in 30 minutes for AI readability, and the reasons behind it are in why a beautiful website can still be invisible to AI.

One honest limit. We have not tested every template on every builder, and builders change how they deliver pages. That is why the advice is to look at your own source and not to trust a general claim, including this one.

Should you switch builders?

No, not for this. Moving from one builder to another changes how the page is made and leaves what it says untouched. If the words were thin on Squarespace they will be thin on WordPress, and you will have spent weeks and broken some links to get there.

There are real reasons to move. None of them is "AI cannot read it":

  • You cannot edit a page's title or description on the plan you have.
  • You need to see and edit the robots.txt file directly and your builder only offers a checkbox.
  • Your whole site is one long page and the builder makes separate pages hard.
  • The site is on a small or abandoned platform that gives you no page source to inspect at all.

If someone quotes you a rebuild as the cure for missing AI answers, ask them one thing: which sentence on the new site will be different from the old one? If the answer is none, the rebuild is a design project. It may be a good one. It is not this.

And if you would sooner see the result than argue about the cause, look at the answers. The free check asks ChatGPT 25 real buyer questions from your niche at $0 and emails a plain-English readout with your score, who got named in your place, and the one fix to start with. It runs as soon as you ask for it, and the report lands within the hour between 7am and 5pm Central, or by 10am the next morning outside those hours.

What the free check does not do: it covers ChatGPT only, and it does not open your builder or change a setting. Check the switch yourself first. It is free and it takes two minutes.

Questions we hear the most

Does your website builder hurt your AI visibility?

Rarely. The mainstream builders all produce pages an assistant can read. What hurts is a setting that asks crawlers to stay away, words that only appear inside images or add-ons, and pages that never state the plain facts a buyer asks about.

Is Squarespace bad for AI visibility?

No. Squarespace has a checkbox that blocks known AI crawlers, and its help page says the box is unchecked by default. If you or a designer checked it, uncheck it under Settings, then Crawlers. The rest depends on what your pages say.

Is Wix bad for AI visibility?

No. Wix lets you block AI crawlers by adding lines to a file called robots.txt, and its help page describes that as something the owner adds. Open the Robots.txt Editor and check that nobody has added lines naming AI crawlers you want to be read by.

Is WordPress better than Squarespace or Wix for AI answers?

Not on its own. WordPress gives you more control, which also means more ways to get it wrong, including a checkbox that asks search engines not to list the site at all. A plain page says the same thing on any of the three.

How do I check whether my builder is blocking AI crawlers?

Type your web address followed by /robots.txt into a browser and read the file. Look for a line reading Disallow: / under the name of a crawler, such as OAI-SearchBot or GPTBot. Then check the setting in your builder that writes that file.

Does the AnswerHalo free check tell me if my builder is the problem?

Not directly. The free check asks ChatGPT 25 real buyer questions from your niche at $0 and emails your score, who got named in your place and the one fix to start with. It reads the answers, not your builder settings.

What does the $500 audit include that the free check does not?

The audit runs 125 checks across ChatGPT, Claude, Gemini, Perplexity and Google AI Overviews, keeps every answer so you can read it, and lands by this time tomorrow. The free check covers ChatGPT only, with 25 questions.

SEE WHERE YOU STAND

Your buyers are already asking. Find out what AI tells them.

The free check asks ChatGPT 25 real buyer questions about your niche and sends you the report within the hour, at $0. If it shows you are already getting named everywhere, we will say so in plain words.

Get my free check →