Cloudflare Markdown changes: check your client
What publishers should check after the October 9 Markdown for Agents update: size limits, response handling and dependencies in their own clients.
Change and audience
On October 9, 2026, Cloudflare announced streaming Markdown for Agents conversion and a 6 MiB decompressed-HTML limit. This concerns an external tool on enabled sites, not a new AffiliateCore feature. Regional use depends on service and account availability, not website language.
The change matters to publishers whose own fetchers or content workflows consume converted pages. Publishing an article does not itself require conversion. Documentation lists Pro, Business, Enterprise and SSL for SaaS; do not assume every plan qualifies.
Practical check
Our recommendation: identify code that treats response headers as mandatory. Token-count headers are no longer generated; Content-Length is removed. Do not silently replace missing data with zero, which can hide budgeting errors.
On an authorized test page, compare returned text with the original: meaningful headings, important terms and links should survive your workflow. Test a small document and one near the applicable limit without account pages or customer data. Record date, response type, received bytes and completion. Transfer size and decompressed size differ.
Your success criterion is correct completion with explicit handling of unavailable optional information. If text is truncated, stop rollout and investigate response handling. This release does not establish better rankings, conversions or AI accuracy.
Use verified material when preparing your website and source description for AffiliateCore. Do not describe the converter as built-in platform tracking.
Sources: October 9 update, documentation and availability.