Cloudflare Fundamentals - Origin Content Signals for Markdown for Agents

<p><a href="https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/">Markdown for Agents</a> now preserves security- and cache-relevant response headers from your origin when converting HTML to Markdown:</p> <ul> <li>Markdown for Agents preserves security headers such as <code>Strict-Transport-Security</code> (HSTS), <code>Content-Security-Policy</code> (CSP), <code>X-Frame-Options</code>, <code>Set-Cookie</code>, and CORS headers (for example, <code>Access-Control-Allow-Origin</code>) on the converted response.</li> <li>Caching headers (<code>Cache-Control</code>, <code>Expires</code>, <code>Age</code>) continue to pass through.</li> </ul> <p>Your origin's <a href="https://contentsignals.org/" target="_blank" rel="noopener">Content Signals<span class="external-link"> ↗︎</span></a> policy is now authoritative. If your origin sets a <code>content-signal</code> header, Markdown for Agents preserves it. When the origin does not send one, Cloudflare adds the default <code>Content-Signal: ai-train=yes, search=yes, ai-input=yes</code>.</p> <p>This release also fixes relative link resolution for directory-style base URLs (those ending in a trailing slash). Previously, relative links such as <code>../page/</code> could resolve one path segment too high and return a <code>404</code>. Links are now resolved correctly per <a href="https://www.rfc-editor.org/rfc/rfc3986#section-5.2.3" target="_blank" rel="noopener">RFC 3986<span class="external-link"> ↗︎</span></a>.</p> <p>Refer to our <a href="https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/">developer documentation</a> for more details.</p>