Editorial desk sitemap
The Odds sitemap is the editorial desk's published navigation. The sitemap is built to be accessible to readers aged 18 and over, and to readers using the editorial desk's accessibility layer. The sitemap is built to be transparent, with the editorial verification chain documented in the page footer.
Editorial desks
- Tournaments — tournament brackets, group draws, stage transitions, and grand final schedules.
- Matches — day-of schedule, broadcast partners, and talent rotation.
- Teams — team cards, rosters, and regional qualifying paths.
- Players — player profiles, role notes, and interview logs.
- Games — game profiles, patch notes, and meta reads.
- Guides — editorial guides on reading the broadcast, the meta, and the talent rotation.
- News — editorial notes on tournaments, teams, patches, policy, streaming, and studio.
Brand SERP
- Odds login — account access workflow.
- Odds app — editorial mobile companion.
- Odds download — official app store flow.
- Odds APK — latest version of the Android application package.
- Refer code — operator's invite flow.
- Bonus code — operator's welcome flow.
- Odds review — editorial desk's read on the platform.
- How to play — contest rules, entry requirements, and scoring system.
- Wallet / KYC — wallet and KYC verification flow.
- Is Odds legal — editorial desk's read on regional eligibility.
- Owner — editorial desk's read on the company.
- Delete account — account deletion flow.
- Official website — canonical Odds domain.
Editorial policy
- Customer care — the editorial contact desk.
- About — the editorial desk and the newsroom.
- Editorial policy — editorial standards, content standards, and disclosure standards.
- Privacy — data collection, data sharing, and reader rights.
- Terms — editorial standards, reader rights, and disclosure standards.
- Responsible play — verification, editorial independence, and transparency.
- Sitemap — the editorial desk's published navigation.
What the editorial desk reads on this page
The editorial desk reads three working documents on every page the desk publishes. The published record is the editorial layer the broadcast can't carry — the source, the verification date, the verification result, and the editorial context. The editorial analysis is the editorial timing the broadcast can't carry — the editorial read, the editorial verification chain, the editorial context. The editorial coverage is the editorial follow-up the broadcast can't carry — the editorial window, the editorial cadence, the editorial follow-up.
The editorial read pairs the published record with the editorial analysis and the editorial coverage. The editorial read is the editorial layer the broadcast can't carry, and the editorial verification chain is published with the page footer. The editorial read is built to be accessible to readers aged 18 and over, and to readers using the editorial desk's accessibility layer.
The broadcast studio carries the editorial layer
The broadcast studio is the editorial layer the broadcast can't carry. The studio carries the editorial read, the editorial verification chain, and the editorial context. The editorial read is published with the editorial verification chain, and the editorial verification chain is published with the page footer.
The verification chain is the editorial record
The verification chain is the editorial layer the operator's marketing channel can't carry. The chain documents the source, the verification date, the verification result, and the editorial context. The chain is published with the page footer, and the editorial verification chain is available on request through the contact desk.
How the editorial verification chain is documented
The editorial verification chain is documented across four layers. The source layer identifies the official channel the editorial desk cross-checked against — typically the operator's official documentation, the league's official channel, the team's official social media, or the broadcast partner's official bracket. The verification date layer identifies when the editorial desk cross-checked the source. The verification result layer identifies the editorial desk's conclusion — confirmed, refuted, or unresolved. The editorial context layer identifies the editorial reasoning behind the result.
The editorial verification chain is built to be transparent. The chain is published with the page footer, and the chair is available on request through the contact desk. The chain is built to be accessible to readers aged 18 and over, and to readers using the editorial desk's accessibility layer.
What the page covers in three working documents
First, the published record — the source, the verification date, the verification result, and the editorial context. Second, the editorial analysis — the editorial read, the editorial verification chain, the editorial context. Third, the editorial coverage — the editorial window, the editorial cadence, the editorial follow-up. The three documents are the editorial layer the broadcast can't carry, and the editorial read is published with the editorial verification chain.
The editorial desk's read on the broadcast
The editorial desk reads the broadcast the way the casters read the script. The desk reads the editorial layer, the editorial verification chain, and the editorial context. The editorial read is the editorial layer the broadcast can't carry, and the editorial verification chain is published with the page footer.
What the editorial desk signs up to
The sitemap is published with the editorial verification chain. The editorial verification chain documents the source, the verification date, the verification result, and the editorial context. The verification chain is published with the page footer.
What readers ask the desk most
How is the sitemap organized?
The sitemap is organized by editorial desk, brand SERP, and editorial policy. Each section is published with the page footer.
How often does the sitemap refresh?
The sitemap refreshes whenever the editorial desk publishes a new page. The verification chain is published with the page footer.
How does the sitemap handle the brand SERP?
The brand SERP section covers the operator's account flow, the operator's welcome flow, the operator's invite flow, and the editorial verification chain. The verification chain is published with the page footer.
How does the verification chain work?
The chain documents the source, the verification date, the verification result, and the editorial context. The chain is published with the page footer, and the editorial verification chain is available on request through the contact desk.