Beyond keywords: data, permissions and actionability for agent-ready websites

Discovery, understanding and task completion are different jobs

Finding a page and completing a booking are different jobs. The first needs crawlable, indexable and useful information. The second also needs clear fields, feedback and accountability. Google says AI Overviews and AI Mode use existing SEO foundations, without additional specialised technical requirements. Important information should be available as text, and structured data should match visible content.[G1]

CLEARCRAFT groups the preparation into the four layers below. This is our delivery framework, not an AI platform's ranking standard.

Layer one: complete the service facts

Give the business name, audience, market, delivery method, confirmed prices or enquiry route, terms and contact details a stable home. FAQs should answer real customer questions and identify sources, an owner and a substantive review date.

For example, a Hong Kong advisor offering Zoom and in-person meetings should explain the duration, audience, preparation and confirmation process. This is an illustration, not a client result.

Layer two: make the same information readable

Start with normal HTML, headings, internal links, canonical URLs, language versions and schema that matches the body. Then assess optional formats. Cloudflare Markdown for Agents is one conversion option: when enabled on an eligible site, a client can request Markdown with Accept: text/markdown. The documentation describes metadata extraction and preservation of source JSON-LD.[C2]

Cloudflare's 9 October 2026 update introduced streaming conversion at the edge and raised the decompressed HTML limit from 2 MiB to 6 MiB. Converted responses no longer generate x-markdown-tokens, x-original-tokens or Content-Length. Teams relying on those headers need to update their checks.[C1]

Markdown conversion changes the representation. The documentation does not establish that a particular AI platform will request it, cite the page or improve its ranking.

Layer three: make the next step workable

Choose a specific task, such as enquiring about a service or preparing a quote request. Can someone find the entry point? Are fields clearly named and required fields identified? What happens after a button is pressed? How can the person recover from failure?

Complete the same flow manually before testing an agent in an authorised environment. Record steps, time, errors and the work that still needs a person. A visible tool entry point does not establish compatibility with every agent.

Layer four: define data and action permissions

Public service facts, internal files and customers' personal information need different access arrangements. Sending messages, submitting orders, payments and other consequential steps need explicit confirmation and an action record.

Assess content-use signals when considering Cloudflare conversion. The documentation says an existing origin content-signal header is preserved. When none exists, the converted response adds the default ai-train=yes, search=yes, ai-input=yes. The site owner should understand and confirm the intended policy before enabling the feature.[C2]

A practical first step for a Hong Kong SME

Start with one public service page and one enquiry task. Verify the facts, inspect readable text and links, try the form and confirm its result, then list the steps that need a customer or employee to approve them.

A useful deliverable can be small: a one-page gap list, a workflow diagram and a prioritised correction table. Repeat the same task after improvements. This article does not measure a client's rankings, citations or commercial results.