> ## Documentation Index
> Fetch the complete documentation index at: https://docs.polyembed.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Editorial guidelines

> How to present PolyEmbed widgets next to your journalism without making prohibited claims.

The [Publisher Terms](https://polyembed.io/policies/publisher-terms) and [Prohibited Claims Policy](https://polyembed.io/policies/prohibited-claims) set rules for how you present the widget. These guidelines explain them in practice.

## Don't

Publishers may not present prediction market trades as:

* Guaranteed returns or a way to make money.
* Financial advice.
* Risk-free.
* An official editorial endorsement by PolyEmbed or Polymarket.

| Avoid | Prefer |
| - | - |
| "Bet on this and win big" | "See the market's current odds" |
| "Our pick: buy Yes now" | "Traders on Polymarket give this a 62% chance" |
| "Risk-free way to back your view" | "Prediction markets carry risk. Trades can lose value." |
| "Polymarket's official forecast" | "Odds from Polymarket, a prediction market" |

## Do

* **Label it clearly.** A heading such as "What the market says" or "Live odds" tells readers the widget isn't part of the reporting.
* **Keep reporting and odds separate.** Market prices reflect traders' positions, not facts. Don't quote odds as if they were a poll or a forecast by your newsroom.
* **Keep the widget's disclosures visible.** Don't cover or crop the widget's risk notice.
* **Respect regions.** Don't encourage readers to get around geographic restrictions. The widget shows odds only where trading isn't available.

## Placement on sensitive stories

Matching is automatic, but you decide where the widget can appear. Consider leaving it out of templates for tragedies, obituaries and stories about victims, where a tradable market would be inappropriate.

## Enforcement

PolyEmbed reviews reports of misleading claims. Breaking these rules can lead to suspension of a widget, a domain or your publisher account, and held payouts.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.