Celso/markdown for agents improvements (cloudflare#28367)

* Markdown for Agents improvements

* Adds changelog entry

* typo

* Apply suggestions from PCX review

* Use AI Crawl Control instead

* Update src/content/changelog/fundamentals/2026-02-16-markdown-for-agents-improvements.mdx

Co-authored-by: Matt Silverlock <msilverlock@cloudflare.com>

---------

Co-authored-by: Pedro Sousa <680496+pedrosousa@users.noreply.github.com>
Co-authored-by: Matt Silverlock <msilverlock@cloudflare.com>

Author: 3 people

src/content/changelog/fundamentals/2026-02-16-markdown-for-agents-improvements.mdx

@@ -0,0 +1,19 @@
+---
+title: Content encoding support for Markdown for Agents and other improvements
+description: Markdown for Agents now supports content encoding and larger responses.
+products:
+  - fundamentals
+date: 2026-02-16
+---
+
+When AI systems request pages from any website that uses Cloudflare and has [Markdown for Agents](/fundamentals/reference/markdown-for-agents/) enabled, they can express the preference for `text/markdown` in the request: our network will automatically and efficiently convert the HTML to markdown, when possible, on the fly.
+
+This release adds the following improvements:
+
+- The origin response limit was raised from 1 MB to 2 MB (2,097,152 bytes).
+- We no longer require the origin to send the `content-length` header.
+- We now support content encoded responses from the origin.
+
+If you haven’t enabled automatic Markdown conversion yet, visit the [AI Crawl Control](https://dash.cloudflare.com/?to=/:account/:zone/ai) section of the Cloudflare dashboard and enable **Markdown for Agents**.
+
+Refer to our [developer documentation](/fundamentals/reference/markdown-for-agents/) for more details.

src/content/docs/fundamentals/reference/markdown-for-agents.mdx

@@ -103,23 +103,12 @@ curl https://blog.cloudflare.com/markdown-for-agents/ \
 
 ## Limitations
 
-:::note
-
-Markdown for Agents will not return a converted Markdown response when:
-
-- The origin response does not include a `content-length` header.
-- The origin response `content-length` exceeds 1 MB (1,048,576 bytes).
-
-In these cases, the original HTML response is returned instead.
-:::
-
 - We only convert from HTML, other types of documents may be included in the future.
-- We don't support compressed responses from the origin.
-- Markdown for Agents is a zone level setting. If you need different settings for different sub-domains of a zone, you need to decouple them to separate zones.
+- The origin response cannot exceed 2 MB (2,097,152 bytes).
 
 ## Other Markdown conversion APIs
 
 If you’re building AI systems that require arbitrary document conversion from outside Cloudflare or Markdown for Agents is not available from the content source, we provide other ways to convert documents to Markdown for your applications:
 
 - Workers AI [AI.toMarkdown()](https://developers.cloudflare.com/workers-ai/features/markdown-conversion/) supports multiple document types and summarization.
-- Browser Rendering [/markdown](https://developers.cloudflare.com/browser-rendering/rest-api/markdown-endpoint/) REST API supports markdown conversion if you need to render a dynamic page or application in a real browser before converting it.
+- Browser Rendering [/markdown](https://developers.cloudflare.com/browser-rendering/rest-api/markdown-endpoint/) REST API supports markdown conversion if you need to render a dynamic page or application in a real browser before converting it.

src/content/partials/fundamentals/markdown-for-agents.mdx

@@ -10,8 +10,8 @@ To enable Markdown for Agents for your zone in the dashboard:
 
 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account (you need a Pro or Business plan).
 2. Select the zone you want to configure.
-3. Look for **Quick Actions**.
-4. Toggle the **Markdown for Agents** button to enable.
+3. Visit the [AI Crawl Control](https://dash.cloudflare.com/?to=/:account/:zone/ai) section.
+4. Enable **Markdown for Agents**.
 
 </TabItem> <TabItem label="API">
 
@@ -83,4 +83,4 @@ curl --request PUT \
 
 This will enable the feature on custom hostnames that have the `content_converter` custom metadata tag set.
 
-</TabItem> </Tabs>
+</TabItem> </Tabs>