What a visitor can read
Human terms, robots/content-signal text, intended-use language, licensing CTA, page type, source URL and observed date.
Do not let the dashboard, public terms and licensing route drift apart.
A fictional nine-row migration ledger for a specialist publisher: content surface × Search / Agent / Training decision × public policy × private control-plane unknown × draft action × effective-date evidence.
Fictional/composite sample: “Atlas Parts Archive” is invented for workflow demonstration. No real publisher, domain, dashboard setting, crawler result, legal right, traffic effect, licensing result or customer demand is claimed. Every private control-plane state remains unknown and every target action remains an unapplied draft.
1. Record the provider event without turning it into a customer claim
Bounded source context: Cloudflare's official article describes Search, Agent and Training crawler controls and says that from 15 September 2026, new domains onboarding to Cloudflare will default to blocking Training and Agent on pages displaying ads while allowing Search. That statement does not establish an existing domain's settings, a fictional publisher's provider, or crawler behavior. Open the dated source snapshot.
Before any authorized setting change, an owner should re-check current provider documentation and the scope of the effective-date rule.
2. Three layers, not one “AI bot” switch
What the public web cannot prove
Dashboard classification, provider account state, rule precedence, page matching and whether an owner applied a draft. Keep this unknown until owner-verified.
What turns policy into a product
A buyer-readable dataset/catalog, intended-use matrix, bounded enquiry route and human decision owner—not a crawler-control promise.
3. Fictional 3 × 3 migration ledger
Three content surfaces are split across Search, Agent and Training. The table shows only a concise view; the downloadable fixture preserves the full terms-alignment, route and effective-date fields.
| Surface | Model | Class | Current public policy | Control plane | Draft target action |
|---|---|---|---|---|---|
| /editorial-guides | Ad-supported editorial | Search | Refer to human terms | Unknown / not publicly observable | Draft allow, owner review required |
| /editorial-guides | Ad-supported editorial | Agent | Request required | Unknown / not publicly observable | Draft block + enquiry route |
| /editorial-guides | Ad-supported editorial | Training | Not pre-authorized | Unknown / not publicly observable | Draft block pending written decision |
| /reference-notes | Subscription reference | Search | Refer to human terms | Unknown / not publicly observable | Draft allow, owner review required |
| /reference-notes | Subscription reference | Agent | Request required | Unknown / not publicly observable | Draft review + enquiry route |
| /reference-notes | Subscription reference | Training | Not pre-authorized | Unknown / not publicly observable | Draft block pending written decision |
| /data-catalog | Licensable data catalog | Search | Refer to human terms | Unknown / not publicly observable | Draft catalog discovery only |
| /data-catalog | Licensable data catalog | Agent | Request required | Unknown / not publicly observable | Draft catalog discovery; data use to enquiry |
| /data-catalog | Licensable data catalog | Training | Not pre-authorized | Unknown / not publicly observable | Draft block pending written decision |
4. Owner checklist before and after 15 September
01 · Inventory
List page groups, ad presence, content model, public policy URL, licensing route and owner. Do not infer page-level scope from a domain-wide label.
02 · Decide
Choose Search, Agent and Training intent separately for each content model. Record who approved the decision and what remains unknown.
03 · Align
Compare the draft control with approved human terms, robots/content-signal text and the data-product enquiry path. Route rights questions to owner/counsel.
04 · Implement only when authorized
Re-check current provider documentation, account scope and rule precedence. This sample does not log in or change settings.
05 · Capture evidence
Record timestamp, source/document version, authorized operator, relevant screenshot/reference and effective date without exposing credentials.
06 · Regress
Re-check public policy alignment and expected page matching. Do not treat a dashboard save as proof that crawlers complied or traffic improved.
5. Founder-readable five-bullet review
1
Separate source event from site state
A provider announcement creates a review trigger; it does not reveal the current settings of an existing or fictional domain.
2
Model by surface and use case
Ad-supported editorial, subscription reference and licensable catalogs can require different Search, Agent and Training decisions.
3
Keep private settings unknown until owner-verified
Public robots or terms evidence cannot prove a dashboard toggle, rule precedence, account configuration or crawler outcome.
4
Align controls with a human commercial route
If the publisher owns licensable data, pair policy language with a clear field catalog, intended-use request and decision owner.
5
Version the migration
Record draft, authorization, implementation and post-change evidence separately so an effective date does not silently become a claimed result.
6. The bounded paid scope
A$149–299 AI Traffic Policy Migration Readiness Review
One public/redacted publisher surface, returned in 48–72 hours with a page/content-model inventory, Search/Agent/Training decision matrix, public-policy/terms/licensing-route alignment check, dated change ledger, owner-approved implementation brief and post-change evidence checklist.
One public/redacted publisher surface, returned in 48–72 hours with a page/content-model inventory, Search/Agent/Training decision matrix, public-policy/terms/licensing-route alignment check, dated change ledger, owner-approved implementation brief and post-change evidence checklist.
Promote gate
Three qualified publishers request a custom migration pack, or one pays for a setup after approved distribution.
Kill gate
Free controls solve the full buyer problem, publishers have no licensable asset, status cannot be verified with owner cooperation, or ten approved touches produce no commercial conversation.
Boundary: workflow and product readiness only. No customer dashboard login or setting change without separate explicit authorization; no legal opinion, security audit, crawler firewall, rights determination, traffic guarantee, revenue guarantee or crawler-compliance guarantee. Not affiliated with Cloudflare.