Blocking AI crawlers on a GoDaddy website depends entirely on which GoDaddy product your site runs on. If your site is on GoDaddy WordPress hosting, you can edit robots.txt directly and the job takes ten minutes. If your site is built with GoDaddy's Website Builder, there is no robots.txt file for you to edit at all — and no setting inside the builder adds one. This guide covers both cases honestly: the WordPress path step by step, the Website Builder workarounds that actually work, and the one option — putting Cloudflare in front of your domain — that fixes the problem no matter which GoDaddy product you use.
First, find out which GoDaddy site you have
GoDaddy sells two very different website products under similar names, and the answer to "can I edit robots.txt?" flips depending on which one you bought.
GoDaddy WordPress hosting (Managed WordPress or WordPress on cPanel). Your site runs real WordPress on a server you can reach. There is a robots.txt file in the site's root folder, and you can edit it with a plugin or by uploading a file. This is the easy case.
GoDaddy Website Builder (formerly GoCentral / Websites + Marketing). Your site runs on GoDaddy's closed builder. There is no file manager for the site, no FTP access to its root, and no robots.txt editor. GoDaddy generates the site's crawl behaviour itself. This is the hard case, and it is the one most people asking this question are stuck on.
If you are not sure which one you have, sign in to your GoDaddy account and open My Products. A Website Builder plan says "Websites + Marketing" or "Website Builder". A WordPress plan says "Managed WordPress" or "WordPress Hosting". If you log in to a WordPress dashboard to edit your site, it is WordPress. If you edit it in GoDaddy's own visual editor with no WordPress dashboard anywhere, it is the builder.
Path 1: GoDaddy WordPress hosting — edit robots.txt directly
On WordPress hosting, the standard approach works exactly as it does anywhere else. GoDaddy's own help documentation describes it: install and activate the Yoast SEO plugin, open Yoast SEO in the left menu, choose Tools, then File editor, and create or edit the robots.txt file there.
Here is a complete AI-crawler blocklist to paste in, covering the training crawlers that matter most. Each stanza names one crawler and closes the whole site to it:
# Block AI training crawlers, keep search crawlers open
User-agent: GPTBot
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: Google-Extended
Disallow: /
User-agent: Applebot-Extended
Disallow: /
User-agent: meta-externalagent
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: Bytespider
Disallow: /
User-agent: Amazonbot
Disallow: /
User-agent: DeepSeekBot
Disallow: /
User-agent: MistralAI-Training
Disallow: /Notice what is deliberately missing from that list: OAI-SearchBot, PerplexityBot, Claude-Web and Googlebot. Those are the crawlers that power AI answers and search results. Blocking GPTBot stops OpenAI training on your content; blocking OAI-SearchBot would also remove your pages from ChatGPT's answers. OpenAI documents the two as independent settings, and they are. If you want the full reasoning, our guide to GPTBot vs OAI-SearchBot walks through the split, and our allowlist strategy shows how to block trainers while keeping answer engines open.
After saving, check the live file at yourdomain.com/robots.txt in a browser. If you see your new rules, the file is live. Google's robots.txt specification covers the syntax if you want to extend the list. Then run it through CrawlGuards' free robots.txt tester and confirm that GPTBot is blocked while Googlebot and OAI-SearchBot are still allowed. If the tester shows something different from what you pasted, a security plugin or a caching layer is serving a stale copy — clear the cache and re-check. If you are building the file from scratch rather than editing an existing one, the robots.txt generator produces the same blocklist with the syntax already correct.
One GoDaddy-specific note: on Managed WordPress plans, GoDaddy sometimes serves a default virtual robots.txt when no physical file exists. Creating the file through Yoast's file editor replaces that virtual file with your real one. If your edits seem to vanish, check whether a caching plugin or GoDaddy's own server cache is serving the old version, and purge it before assuming the edit failed.
Path 2: GoDaddy Website Builder — there is no robots.txt to edit
This is the part most guides skip, and it is the part that matters. GoDaddy Website Builder does not give you a robots.txt file. You cannot upload one, because there is no file manager for the builder's root folder. You cannot edit one in the builder's settings, because no such setting exists. The builder exposes a small set of SEO controls — page titles, descriptions, and a search-engine visibility toggle that adds a site-wide noindex — but nothing that names individual crawlers.
That leaves three real options, in order of how much control they give you.
Option A: Use the builder's own visibility controls (limited, blunt)
Website Builder has a setting that hides the site from search engines. It works by telling all crawlers to stay away, not by naming AI crawlers. That is the wrong tool for this job: it also removes you from Google and Bing. Do not use it to block AI training unless you genuinely want the whole site invisible. There is no per-crawler version of this setting, and no meta-tag editor that lets you add crawler-specific directives page by page on the lower plans. Some higher-tier plans allow adding custom code to the page header, which opens the door to per-page robots meta tags — but a meta tag can only carry page-level instructions, it cannot reproduce a site-wide robots.txt, and it depends on your plan including that feature.
Option B: Put Cloudflare in front of the domain (the real fix)
This is the option that actually solves the problem on a Website Builder site. Your domain's DNS lives at GoDaddy (or wherever your registrar is), and you can point it at Cloudflare's nameservers without moving the site itself. Once Cloudflare sits in front of the domain, its firewall sees every request before GoDaddy's builder does — including requests from AI crawlers — and you can block them there.
The setup is: create a free Cloudflare account, add your domain, and change the nameservers at your registrar to the two Cloudflare nameservers. Cloudflare will import your existing DNS records automatically; check that the record pointing at your Website Builder site is still there before you save. Then, in the Cloudflare dashboard, create a custom WAF rule that matches requests where the user-agent contains one of the AI training crawler tokens — GPTBot, ClaudeBot, Google-Extended, CCBot, Bytespider, DeepSeekBot — and set the action to Block. Cloudflare also offers a managed "Block AI Bots" toggle that covers its own list of known AI crawlers, which is a good baseline on top of your named rules.
Two honest caveats. First, this changes your DNS, so a mistake can take the site offline until it is fixed. Do it when you have half an hour free, not five minutes before a launch. Second, the Website Builder site itself still has no robots.txt naming these crawlers, so a polite crawler that checks robots.txt first will find no instruction and will still arrive at the firewall — where it will be stopped. That is fine. The firewall is the enforcement layer; robots.txt is the request layer. On a builder site you lose the request layer and keep the enforcement layer, and enforcement is the part that actually works.
Our Cloudflare AI-bot blocking guide walks through the WAF rule setup in detail, including which tokens to include and how to verify the rules are firing.
Option C: Move the site to WordPress hosting (the permanent fix)
If AI-crawler control matters to you long-term — and if you are reading this guide, it probably does — the durable answer is to move off the closed builder onto a platform where you own the files. GoDaddy's own Managed WordPress plans are the shortest move, since the domain and billing stay in one place. Moving means rebuilding the site's pages in WordPress, which is real work, but it buys you the full set of controls: robots.txt, llms.txt, security plugins, and every other file-level decision a closed builder hides. For a business site that will live for years, that trade is usually worth it. For a small brochure site, Option B is the proportionate answer.
What about GoDaddy's own AI features?
A wrinkle worth knowing: GoDaddy sells AI features of its own, including AI-assisted site building and marketing tools, and its terms allow it to use customer content to operate and improve those services. That is a separate question from whether GPTBot or ClaudeBot can crawl your site, and blocking AI crawlers in robots.txt does not change what your hosting provider does with content you gave it under its terms of service. If you use GoDaddy's AI tools to generate text or images, that content is processed by GoDaddy's systems by design. The crawler controls in this guide govern outside AI companies' bots, not your host's own features. If the host's own data use concerns you, that is a question for the terms of service and for whether you use those features at all — not something a robots.txt file can answer.
How to verify the block on a GoDaddy site
Verification differs by path, because the two paths enforce the block in different places.
On WordPress hosting: open your live robots.txt and confirm the rules are there, then test with the robots.txt tester. Also check your server logs or your security plugin's logs a few days later for requests carrying the blocked tokens — they should stop appearing, or appear only as blocked attempts.
On Website Builder behind Cloudflare: open the Cloudflare dashboard and look at the WAF events for your custom rule. You should see blocked requests from the AI-crawler user-agents within days. If the rule shows zero events after a week, either the crawlers never visited or the rule is not matching — test it by checking your site's access through a request carrying a blocked user-agent string, or compare against the traffic Cloudflare reports. Also confirm your site is still loading normally for real visitors; a WAF rule that matches too broadly can block legitimate traffic, so check the rule's condition carefully before leaving it in place.
On Website Builder without Cloudflare: there is nothing to verify, because there is nothing to enforce. That is the honest position. If you have not added a front layer and have not moved platforms, the AI crawlers can still read the site. Saying otherwise would be pretending.
Common mistakes on GoDaddy sites
Pasting robots.txt into a header code box. Robots.txt is a file, not a snippet. It belongs at the root of the domain, served at yourdomain.com/robots.txt. Putting its contents into an HTML header or a custom-code box does nothing, and on some builders it throws a validation error because the box expects JavaScript. If a guide tells you to paste robots.txt into a header, it is wrong.
Blocking everything to block AI. A User-agent: * group with Disallow: / blocks Googlebot too. On the Website Builder, the "hide from search engines" toggle does exactly this. It is the nuclear option, not the AI-crawler option.
Forgetting subdomains. Robots.txt is per-host. A rule on yourdomain.com does not cover blog.yourdomain.com or a staging subdomain. If you run content on subdomains, repeat the rules there — or, on the Cloudflare path, write the WAF rule to cover the whole domain including subdomains.
Assuming the job is done after one edit. Crawlers re-read robots.txt on their own schedule, and new AI crawlers appear every month. The complete list of AI crawlers is updated as new ones are identified, and a twice-yearly review of your blocklist keeps it honest.
Frequently asked questions
Can I edit robots.txt on GoDaddy Website Builder?
No. GoDaddy Website Builder does not expose a robots.txt file or an editor for one. You cannot upload a robots.txt file to a Website Builder site. To block AI crawlers on a builder site, put Cloudflare in front of the domain and block the crawlers with a firewall rule, or move the site to WordPress hosting where robots.txt is editable.
Can I edit robots.txt on GoDaddy WordPress hosting?
Yes. Install the Yoast SEO plugin, open Yoast SEO, then Tools, then File editor, and create or edit the robots.txt file. GoDaddy documents this exact path in its own help pages. You can also upload a robots.txt file to the site's root folder with FTP or the hosting file manager.
Does blocking AI crawlers on GoDaddy affect my Google ranking?
No, as long as you block only the AI training crawlers and leave Googlebot, Bingbot and the AI search crawlers alone. Blocking GPTBot or ClaudeBot has no effect on search rankings. Blocking everything — including Googlebot — would remove you from search results, which is why the blocklist in this guide names each training crawler individually.
Will Cloudflare's free plan block AI crawlers on my GoDaddy site?
Yes. The free Cloudflare plan includes custom WAF rules and the managed AI-bot blocking toggle. You point your domain's nameservers at Cloudflare, and its firewall filters requests before they reach GoDaddy's servers. The site itself stays hosted at GoDaddy.
How long does it take for a robots.txt change to take effect?
Well-behaved crawlers pick up robots.txt changes on their next fetch, typically within 24 hours. Firewall rules apply immediately to new requests. If you are in a hurry, the firewall layer is the one that acts now.
Should I block AI crawlers at all on a small GoDaddy site?
For most small sites, yes — if the site's value is its original content. Training crawlers take content and return no traffic. The exception is if you want maximum exposure inside AI answers, in which case you should block only the training crawlers and explicitly allow the search crawlers that power citations. Our pros and cons guide works through that decision in full.
The short version: on GoDaddy WordPress hosting, edit robots.txt with Yoast and you are done in ten minutes. On GoDaddy Website Builder, there is no robots.txt to edit — put Cloudflare in front of the domain and block the crawlers at the firewall. Either way, name the training crawlers individually and leave the search crawlers alone.
