Can you block AI crawlers on Kajabi? Not the way you would on WordPress. Kajabi gives you no robots.txt editor, no server access, and no way to upload your own robots.txt file. But that does not mean you have no control. Your paid course content is already protected by Kajabi's login wall, your public pages have SEO settings you can use, and Kajabi's own support team can block AI bots by user agent for you. Here is exactly what you can control, what you cannot, and the Cloudflare workaround for the rest.
The short version: if your main worry is that AI companies will train on your paid course videos and lesson text, relax a little. That content sits behind a login, and crawlers cannot log in. If your worry is your public sales pages and blog posts, you have real options, but they are Kajabi's options, not yours. Read on for the full picture.
The short answer: no robots.txt editor, but real controls exist
Kajabi handles robots.txt and your sitemap automatically. You cannot edit either file, and there is no setting, plugin, or code trick inside Kajabi that lets you upload your own version. That is a deliberate trade-off: Kajabi is a hosted, all-in-one platform, and it keeps the technical plumbing to itself so non-technical creators do not break their sites. Independent reviews of Kajabi's SEO features confirm the same limit: control over robots.txt and sitemaps is not something Kajabi gives you.
What you can control instead: which landing pages appear in search results, the meta titles and descriptions on every page, a noindex tag on your login page if you have a plan with code editor access, and, through Kajabi support, user-agent blocking of AI crawlers at the platform's Cloudflare layer. On a custom domain, you can also put your own Cloudflare account in front of Kajabi and enforce your own rules at the edge. Each of these is weaker than a robots.txt file you own, but together they cover most of what a course creator actually needs.
What Kajabi does for you automatically
Before reaching for workarounds, it helps to know what is already handled. Kajabi creates and maintains your robots.txt file and your sitemap.xml automatically, based on your published pages. You can view your sitemap by adding /sitemap.xml to your domain. Search engines find it on their own, and you can also submit it in Google Search Console to speed things up after big changes.
Kajabi's default robots.txt allows search engines to crawl your public pages, which is what you want for your sales pages and blog. The problem is only that it does not distinguish between Googlebot, which brings you traffic, and GPTBot or ClaudeBot, which take your content for training. You cannot change that distinction yourself. That is the gap every workaround in this article is trying to close.
One more automatic protection worth knowing: Kajabi's built-in pages, like the login page and the member library, are not the kind of public content crawlers index and quote. Your site is not wide open just because you cannot see the robots.txt file.
Your paid course content is already behind a wall
This is the most reassuring fact in this whole article, and it is the one most course creators miss. AI crawlers are anonymous visitors. They do not have accounts, they cannot log in, and they cannot pass a paywall. Your course lessons, videos, downloads, and community posts live behind Kajabi's membership system. A crawler that requests a lesson URL gets a login page, not your content.
That means the training risk for your paid material is low by design, and it stays low as long as you keep the material inside the membership area. A few habits keep it that way. Do not paste full lesson transcripts onto public sales pages to pad them out. Do not upload course PDFs to public file links and share those links in your blog. Do not put the same video on a public YouTube channel and embed it in the course unless you are comfortable with that video being public everywhere. The wall only protects what is actually behind it.
There is one honest caveat. If a student copies your content and posts it somewhere public, no platform setting can stop that. That is a different problem, a piracy and terms-of-use problem, and it is worth a clear line in your own terms telling members not to redistribute course material. But the crawler itself is not getting through the login screen.
Public pages: sales pages and blog posts
Your public pages are a different story. Sales pages, blog posts, and your homepage are visible to every crawler, including AI training bots. This is where Kajabi's built-in controls actually help.
For standalone landing pages, Kajabi has a simple toggle: turn off "Show page in search results" and Kajabi adds a noindex, nofollow meta tag to the page and leaves the page out of your sitemap. That is the right move for pages you never want found in search, like a limited-time offer page, a thank-you page, or a private webinar registration page. Note the limitation: this setting is available for standalone landing pages only, not for standard website pages.
For blog posts and website pages, use the SEO and social sharing section. Every page, blog, and blog post has one. It controls the title, description, and image that search engines and social networks show. Kajabi recommends keeping titles under 60 characters and descriptions under 160. Writing a clear title and description does not block AI crawlers, but it does control how your content appears when it is surfaced, and it is the closest thing Kajabi gives you to per-page SEO control.
Be honest with yourself about what noindex does and does not do. A noindex tag tells search engines not to index a page. It does not physically stop a crawler from fetching the page, and it does not stop an AI company from using content it already fetched. Many AI crawlers do respect noindex, and Google has said its AI features follow it, but it is a request, not a lock. For pages you truly want hidden from AI training, noindex is one layer, not the whole answer.
A practical rule for deciding what to protect: your sales pages are meant to be found, so leave them open. Your blog posts are also meant to be found, but they are the content most likely to be useful as training data, so they deserve a deliberate choice. Your offer pages, upsell pages, and anything with a price or a deadline should be hidden from search when they are not live. Audit your pages once a quarter and ask of each one: do I want this found, or do I want this quiet?
Ask Kajabi support to block AI bots for you
Here is the option most Kajabi users never discover. Kajabi's own help documentation has a section called "Discourage AI bots from scraping your site." It says, plainly, that completely blocking AI bots is tricky, but that Kajabi can help make it harder. Many AI scrapers identify themselves with a user agent string, Kajabi uses Cloudflare to protect its sites, and Kajabi can block scrapers by user agent. The help page tells you to email support and they will help.
This is the closest thing Kajabi offers to a robots.txt rule, and it is worth using. When you write to support, be specific. List the bots you want blocked: GPTBot, OAI-SearchBot if you also want to skip AI citations, ClaudeBot, CCBot, Bytespider, Meta-ExternalAgent, PerplexityBot, and Applebot-Extended. Say whether you want training bots blocked but search bots left alone, because blocking OAI-SearchBot also removes your pages from ChatGPT's answers, and that is a visibility trade-off you should choose deliberately, not accidentally.
A few things to know before you email. First, user-agent blocking only stops bots that identify themselves honestly. A scraper that lies about its user agent will not be caught by this. Second, support will apply the block at Kajabi's Cloudflare layer, which covers your site as hosted by Kajabi, including the default Kajabi subdomain and your custom domain. Third, keep a copy of the email and the reply. If a bot you asked to be blocked shows up in your logs later, that paper trail is useful.
Ask support two follow-up questions while you have them: whether the block also covers the ai.txt and llms.txt signals, and whether there is any way to see which bots have been blocked on your account. The answers will tell you how much of the job this route actually covers.
The Cloudflare workaround for custom domains
If you use a custom domain with Kajabi, there is a stronger option: put your own Cloudflare account in front of your site and enforce your own rules at the edge, before requests ever reach Kajabi. Kajabi's own help pages acknowledge this setup exists, noting that cached content can behave differently when a site runs through its owner's Cloudflare account.
Here is how it works in outline. Your custom domain's DNS lives in your Cloudflare account. The record that points your domain at Kajabi is proxied through Cloudflare, which means every request to your site passes through Cloudflare first. At that layer you can do things Kajabi does not let you do: write WAF rules that block specific AI bot user agents, turn on Cloudflare's AI bot blocking, and even serve a custom robots.txt file from a Cloudflare Worker that answers requests for your domain's robots.txt path before they reach Kajabi.
The Worker approach is the most powerful piece. A small Worker can return a robots.txt file of your choosing whenever anyone requests yourdomain.com/robots.txt, with separate rules for training bots and search bots. That gives you the file Kajabi will not let you edit. It is a documented, legitimate use of Cloudflare Workers, and it works because the request is answered at the edge, not at the origin.
Before you do any of this, understand the risks. This is an advanced setup. A wrong WAF rule can block Googlebot and cost you search traffic, which is exactly the opposite of what you want. Cloudflare's own managed robots.txt feature changed in September 2026, and at some sites it silently replaced existing rules, so whatever you set up, verify it live afterwards by opening your robots.txt in a browser and by testing it with a robots.txt tester. Also, do not run two conflicting systems at once: if you put your own Cloudflare rules in place, tell Kajabi support what you have done, so their user-agent blocks and yours do not fight each other.
For most course creators, the honest recommendation is this: try the support route first, and only add your own Cloudflare layer if you are comfortable with DNS and WAF rules, or if you have someone technical to help you. A misconfigured edge setup can do more damage to your business than any AI crawler.
The Pro plan custom-code option
If your Kajabi plan includes code editor access, such as the Pro plan, there is one more small control. Kajabi's help documentation explains that you can add a noindex meta tag to your site's code to keep your login page out of most search engines. That is a niche fix, and the login page is not your main worry, but it is an example of what code access buys you: the ability to add meta tags to pages that do not have their own SEO settings.
Custom code can also add analytics, embed third-party tools, and change how pages look. What it cannot do is change robots.txt, add server-level blocks, or intercept requests before Kajabi serves them. Do not let anyone sell you a "Kajabi robots.txt plugin" or a code snippet that claims to block bots at the server level. There is no server level you can reach on Kajabi. Anything that claims otherwise is either a meta tag in disguise or a scam.
A practical checklist for course creators
Here is the whole plan, in the order to do it. It takes an afternoon.
First, sort your content. Make a list of what is behind the login wall, what is public and meant to be found, and what is public but should be quiet. This list is the basis for every decision that follows.
Second, hide the quiet pages. For every standalone landing page that should not be found, turn off "Show page in search results" so Kajabi adds the noindex tag and drops the page from your sitemap.
Third, tidy your public SEO. For your sales pages and blog posts, fill in the SEO and social sharing fields: a clear title, a description under 160 characters, and a social image. This is also the moment to check that your best blog posts are the ones you actually want AI tools to cite.
Fourth, email Kajabi support and ask them to block AI training bots by user agent. List the bots by name, say whether you want search bots left alone, and keep the reply.
Fifth, decide about Cloudflare. If you have a custom domain and you are comfortable with DNS, set up your own Cloudflare rules or a Worker-served robots.txt, then verify the live file and test it. If you are not comfortable, skip this step. The support route plus the login wall already covers the most important ground.
Sixth, build your own robots.txt rules somewhere you control, even if you cannot publish them on Kajabi yet. A free robots.txt generator lets you draft the exact rules you want, with training bots blocked and search bots allowed. Keep that file ready: if you ever move your blog or your marketing site off Kajabi, you can publish it on day one. And if you use the Cloudflare Worker route, that drafted file is exactly what the Worker should serve.
Finally, check your work. Open yourdomain.com/robots.txt and yourdomain.com/sitemap.xml in a browser. Search Google for a few of your hidden pages to confirm they are not indexed. Ask a friend to visit a lesson URL while logged out and confirm they hit the login screen. Test any new rules with a robots.txt tester before you call the job done. Re-check every few months, because Kajabi updates its platform and Cloudflare updates its features, and a setting that worked in January may behave differently by June.
What you cannot do, honestly
It is worth stating the limits plainly, because several products and blog posts overpromise here. You cannot edit Kajabi's robots.txt. You cannot install a plugin that blocks bots. You cannot see server logs or write server rules. You cannot stop a scraper that ignores robots.txt, fakes its user agent, or copies content from a student's screen. And you cannot remove content from a model that has already been trained on it.
None of that makes the steps above pointless. The goal is not perfect protection, which does not exist on any platform. The goal is to make the honest bots respect your wishes, keep your paid content behind the wall where it belongs, and leave a clear record that you objected. On Kajabi, that is achievable, and it is mostly a matter of using the settings and the support channel that already exist.
Frequently asked questions
Can I edit robots.txt on Kajabi?
No. Kajabi creates and maintains your robots.txt file automatically, and there is no editor, setting, or code option that lets you change it. The workarounds are Kajabi support's user-agent blocking, hiding individual landing pages from search, and, on a custom domain, putting your own Cloudflare account in front of the site.
Is my Kajabi course content safe from AI crawlers?
Your paid content is protected by Kajabi's login wall: crawlers cannot log in, so they see a login page instead of your lessons. That protection holds as long as the content stays inside the membership area. Do not paste full lesson text or course files onto public pages, or the wall cannot help you.
Will hiding a landing page from search also hide it from AI bots?
Not completely. Turning off "Show page in search results" adds a noindex, nofollow tag and removes the page from your sitemap, which tells search engines and many AI crawlers to leave it alone. But noindex is a request, not a physical barrier. A crawler that ignores it can still fetch the page. For pages that must stay private, keep them behind the login wall instead.
What should I ask Kajabi support to block?
Ask them to block AI training bots by user agent: GPTBot, ClaudeBot, CCBot, Bytespider, and Meta-ExternalAgent are the main ones. Decide separately about search bots like OAI-SearchBot and PerplexityBot, because blocking them also removes your pages from AI search answers. Email support, list the bots by name, and keep the reply.
Does putting Cloudflare in front of Kajabi break anything?
It can, if it is set up wrong. A bad WAF rule can block Googlebot, and caching at the Cloudflare layer can delay your SEO changes showing up. Kajabi's own help pages note that sites running through their owner's Cloudflare account may need a manual cache purge. Set it up carefully, verify your live robots.txt afterwards, and test with a robots.txt tester before you call it done.
Should I move my blog off Kajabi to control robots.txt?
Probably not, unless AI crawler control is your top priority. Moving a blog means moving your SEO authority, your links, and your audience habits, which is a much bigger cost than the crawler issue. Most creators are better off using Kajabi's built-in controls and the support channel, and keeping a drafted robots.txt file ready in case they ever move.
