Cloudflare Just Changed What AI Can See on Your Portfolio Site. What Designers Need to Know

On September 15, 2026, Cloudflare flipped a switch that reshaped how AI companies interact with creative work across the internet. Most designers don't even know it happened.

The default behavior for AI crawlers on every new Cloudflare-provisioned domain changed overnight. Bots classified as "Training" or "Agent" are now blocked by default on any page that displays ads. Bots classified as "Search" are still allowed.

That distinction matters more than it sounds, because Cloudflare sits in front of a massive share of the web. Design portfolios, agency sites, creative platforms. If your portfolio runs through Cloudflare (and if you're on Squarespace, Webflow, Framer, or most modern hosting providers, it probably does), the rules for who gets to scrape your work just changed.

Image: Cloudflare Blog, official announcement graphic, used for editorial commentary

Read the official Cloudflare announcement here.

What actually changed

Cloudflare now splits AI traffic into three buckets: Search, Training, and Agent.

Search covers crawlers that index content for retrieval or citation in AI-generated answers. Think of these as the new search engine spiders. These stay allowed by default.

Training covers bots that pull content into a model's training pipeline. This is the bucket most creators and designers want blocked. These are now blocked by default on ad-supported pages.

Agent covers bots acting on behalf of a live user. When someone asks an AI assistant to "check my website" or "summarize this page," the agent fetches the content in real time. This gets blocked by default on ad-supported pages too.

For the first time, a website owner can allow search discovery while blocking AI training, without an all-or-nothing choice. Cloudflare also introduced Bot Preference Sync, which automatically writes your preferences into robots.txt so crawlers outside Cloudflare's network see the same instructions.

The design angle most coverage missed

Most of the coverage treated this as a media publishing story. Newspapers, big content sites, the usual players. But designers have been on the front lines of the AI scraping debate for a different reason.

Your portfolio isn't an article. It's your livelihood, your proof of capability, and in many cases, your creative fingerprint. Designers have been vocal about AI tools being trained on their work without consent, without attribution, and without compensation. Dribbble added NoAI tags. ArtStation enabled NoAI protection by default for all artists in September 2026. But those were platform-level changes with limited reach.

Cloudflare's move is infrastructure-level. It doesn't ask designers to opt in. It protects by default and asks AI companies to negotiate access. That's a fundamental shift in who holds the leverage.

Brandon's take: the default should always have been "protect first"

Let's be honest. The previous default was never "let everyone train on your work." It was neglect. Nobody configuring a design portfolio in 2022 thought, "I hope my pixel-perfect case studies get scraped to train a model that might automate parts of my job." It just happened because the infrastructure didn't distinguish between a search engine and a training pipeline.

Now it does. And the default starts from a position that protects creators.

That's the right starting point. If an AI company wants to learn from your work, they should have to ask, or at minimum, clearly identify their crawler and respect a documented preference. Cloudflare's Accountable Crawler standard and the Pay Per Crawl model point toward something designers have wanted for years: a way to get compensated when AI uses their work, instead of getting scraped into oblivion.

But there's a real tension here, and ignoring it would be dishonest. AI-mediated discovery is becoming a thing. People are starting to find designers through AI assistants instead of Google. If your site blocks all AI traffic accidentally, you might be invisible to the next generation of discovery tools. The distinction between "Search" (allowed) and "Training" (blocked) is the feature that makes this workable, but only if site owners understand it.

What designers should do right now

1. Check if your portfolio is on Cloudflare. Most modern hosting providers route through it. If you're on Squarespace, Webflow, Framer, or many others, Cloudflare may already be handling your edge.

2. Verify your crawler settings. If you're on a domain that was set up before September 15, your existing settings weren't automatically changed. New defaults apply only to new domains. If you want the new protection, review and update your bot policies in your Cloudflare dashboard.

3. Allow Search, block Training. This is the smart combo. It keeps you findable through AI-assisted search results while preventing your work from being used to train competing models. Cloudflare's dashboard makes this a toggle, not a engineering project.

4. Check your robots.txt. Cloudflare's Bot Preference Sync writes your preferences into robots.txt automatically. If you previously had custom rules, confirm they still align with what you want.

5. Decide whether you WANT to be in training data. Some designers argue that being included in AI training increases your influence and future opportunities. If that's you, the opt-in path is clear. The point isn't that one choice is right. It's that now you actually have a choice.

The bigger picture

Cloudflare's Pay Per Crawl model and the Cloudflare Wallets product point toward a future where AI companies pay to access content. For designers, that could mean a revenue stream from portfolio work that previously had zero monetization beyond client acquisition.

We're in the early days of this economic model. It might not work. The payments might be too small to matter. But for the first time, the infrastructure is being built to make it possible at all.

The question that matters for designers isn't whether AI should train on your work. It's who gets to decide. Cloudflare just moved that decision from "happens to you by default" to "you make the call." That's a win for creative work, regardless of which option you choose.

If you're building your portfolio site and want tools that respect your creative work from the start, Base44 lets you spin up a designer-grade web app with built-in protections and zero infrastructure headaches.