How to publish policies as text, not images

A policy set in a designed graphic is not a policy as far as an agent is concerned. Asked whether you offer free returns, it will answer that you do not say. That is a different answer from no, and a worse one.

This is the fix for policy in image.

Why "does not say" loses to "no"

A store with a restrictive but stated returns policy can be compared. A shopper who does not care about returns will accept it. A store whose policy cannot be read is a risk with an unquantified size, and an agent working on somebody’s behalf resolves unquantified risk by choosing the alternative.

The stores that lose most here are the ones with genuinely good policies, because they had something worth saying and set it in a banner.

What to convert, in order

1. Returns. The window, and who pays return postage. These two decide purchases in most categories.
2. Shipping. Cost, threshold and delivery expectation. See how to publish shipping costs machine readably.
3. Warranty, where your category is chosen on it.
4. Everything else, eventually and without urgency.

You do not have to lose the design

This is the objection that stalls the work, and it is answerable. Keep the graphic. Add the same facts as text in the same page. Nothing about the visual result has to change, and the fix is normally one template rather than a project.

The same applies to policies that live in an accordion or a modal: those are fine as long as the content is in the served markup rather than fetched when the accordion opens.

Give each policy one canonical home

Stores accumulate several partial answers: a footer link, an FAQ entry, a line on the product page, a help article. When they disagree, and they will, an agent has no way to know which one you meant.

Pick one authoritative page per policy, make the others link to it rather than restate it, and point at it from your llms.txt.