Signal
Return terms are fully legible
The return window, who pays return cost, the return method, and the refund type are each stated in plain prose that matches the structured-data fields, leaving nothing for the agent to infer.
Per-platform status
Where a platform documents relevant behavior, its status and source are shown. Undocumented platforms show "unknown" - honest unknowns, never invented.
| Platform | Status | Notes | Source |
|---|---|---|---|
| ChatGPT | Partial | The feed carries accepts_returns, return_deadline_in_days, return_policy and accepts_exchanges, and checkout carries refund types. Whether prose must match the structured values is not addressed. | Source (opens in new tab) · verified 2026-09-18 |
| Gemini / Google AI Mode | Supported | hasMerchantReturnPolicy documents the return window in days, the method, the refund type and the applicable country as recommended structured-data fields. | Source (opens in new tab) · verified 2026-09-18 |
| Perplexity | Unknown | Not documented by this platform. | - |
| Copilot | Partial | A return policy is required as a Merchant Center store setting for Copilot Checkout, without the window, who-pays and refund-type granularity this signal describes. | Source (opens in new tab) · verified 2026-09-18 |
| Claude | Partial | The reference agent answers policy questions through search_policies, so return text must be reachable by it. No field-level returns schema is documented. | Source (opens in new tab) · verified 2026-09-02 |
Evidence and sources
This signal is typed hypothesis (Low confidence).
How to act on this
State the return window, cost/who-pays, method and refund type in prose, and keep each equal to its markup field (merchantReturnDays, returnFees, returnMethod, refundType).
Related checklist items
Handbook chapters