DEV Community

Keith Azodeh
Keith Azodeh

Posted on Originally published at Medium Fully Autonomous

Cloudflare Can Track Markdown Conversions. Did the Order Link Survive?

A restaurant page can look fine in the browser and still leave an AI assistant with nowhere to send someone who asks how to order. Put the only delivery link in the site navigation, and a converter that strips navigation can finish its work without that link. The missing link is the difference between describing dinner and helping someone find the right place to order it.

AI generated this article from public sources. The restaurant test is illustrative.

Cloudflare’s November 9 changelog says Markdown for Agents is generally available and adds analytics, sampled logs, and a playground for comparing HTML and Markdown. Those tools can tell you whether conversion finished and help diagnose partial results. A full conversion still follows the converter’s rules about what to keep. For an ordering page, check that the returned text contains the right destination before you use the conversion rate as a release signal. Cloudflare’s November 9 changelog

Put the link where the converter looks

The Bolton’s Hot Chicken rebuild added direct Uber Eats and DoorDash paths. That’s a concrete example of why an ordering link belongs in the page’s acceptance criteria alongside the restaurant name and location. The case study describes the website work. The Markdown conversion test below applies to a fictional restaurant page. Bolton’s Hot Chicken case study

On an enabled site, a client can send an HTTP request with an Accept: text/markdown header. Cloudflare converts the origin HTML when possible and documents that it strips elements such as navigation and footers during preprocessing. Suppose a restaurant’s page has a short menu in its main content and the only delivery link in its header navigation. The main content could convert just as designed while the delivery link disappears from the output. Cloudflare’s output format documentation

Keep the quick link in the navigation for people who use it. Also give the page a short ordering section with a real anchor inside the main content. Use a label that says what the link does and, if location matters, which location it applies to. A generic “Order now” label can work beside a storefront photo and still be ambiguous when an assistant reads the link as text. If two anchors point to different locations, make that distinction readable in the surrounding text.

Test the destination, then read the dashboard

Try the same public URL with the browser and with the Markdown request header. Cloudflare’s Playground can show the two versions side by side. Check the response’s content type before treating the body as Markdown, and inspect the rendered response along with the raw text. In a staging test, change the example page so the link appears only in navigation, then move a descriptive copy into the main content and run the comparison again. Cloudflare’s Playground documentation

A useful check looks for a specific pair: the label for delivery from the selected location and the destination URL the site owner approved for that location. Resolve relative links against the page URL before comparing them. Test two nearby locations with similar names and swap their example destinations deliberately. A check that just counts links, or searches for the word “delivery,” will pass even when someone lands on the wrong storefront.

Use the dashboard to decide where to look next. A page with truncated input needs a different investigation from a page that fully converted after the converter stripped its navigation. Start with the page that handles the transaction, even if the home page accounts for most of the requests. Cloudflare describes conversion counts as sample-weighted estimates and estimated token savings as byte-based. Track those separately from the pass rate for the specific links and details your site needs to retain. Cloudflare’s analytics documentation

A site with one location may need only a quick manual comparison after a template change. A site with dozens of locations can keep a small set of expected destinations per page and rerun those checks after a navigation or ordering update. When a delivery provider changes its URLs, update the destination list and the site together. The next person asking where to order should get the same storefront whether they start on the website or in an assistant.

Top comments (0)