A reader may reach your site through an agent. Access decisions now have a more specific set of controls.
Cloudflare announced personal-agent analytics and access policies on November 4. Site owners can examine supported agents separately from other automated traffic and set exceptions for individual agents. The release gives publishers a choice tied to whether a page carries advertising.
See which agent is requesting which pages
Security Analytics adds a Personal Assistants category to Bot Analysis. A new widget lists agents and their request counts. Selecting one filters the surrounding traffic views, including requested paths, response codes, and originating networks.
For a publisher, that creates a useful starting point: examine whether an agent reaches articles successfully or repeatedly encounters errors. A request count alone cannot establish that the traffic produced a reader, subscription, or sale.
Choose a policy for supported agents
Cloudflare’s Security Settings now call the section AI Crawler and Agent access policies. Owners can set the overall Agents policy and override it for a supported personal agent. Existing Search and Training policies remain unchanged.
| Setting | Access choice |
|---|---|
| Allow (do not block) | The agent policy does not block that supported agent. |
| Block on pages with ads | Apply the advertising-related restriction to that agent. |
| Block | Block the supported agent through this policy. |
An advertising-funded publication might begin by reviewing its most requested paths, then decide which agent deserves an exception. That decision should reflect the site’s business model and actual traffic. Allowing an agent through this setting also should not be confused with giving it permission to perform every account action.
User identity requires a separate service
Cloudflare also describes account views that associate personal agents with particular users. Those views belong to Account Abuse Protection, which remains in early access. The general analytics announcement does not mean every site can identify the human behind every automated request.
This distinction matters when investigating an unusual login. Recognizing the agent is one piece of evidence; recognizing the account and understanding the authorized action require additional context. Cloudflare itself describes carrying user context through agents as continuing work.
For more reporting on agent infrastructure and practical deployment changes, browse our AI news feed. Which pages would you allow a personal agent to read on your site?
Abdessalam Alaoui
I'm Abdessalam Alaoui, founder of Musthave.AI. I write practical guides to AI models, tools, generative media, and ways real people make money with this stuff. No press-release fluff. 20+ years shipping digital products; you'll also find my work around HowTik, Yumasty, and IncomeHelpful.
