Sitemap and editorial colophon — every published route
The sitemap lists every published route on the newsroom. Editorial-only routes are linked from the masthead; commercial or affiliate routes are disclosed separately and labelled.
Editorial independence
Sources cited · Updated 2026-08-04 · No invented fixtures · No fabricated rosters
Editorial colophon
Sitemap — the full editorial surface
The sitemap lists every published route on the newsroom. Editorial-only routes are linked from the masthead; commercial or affiliate routes are disclosed separately and labelled.
| Route | Intent | Status |
|---|---|---|
| / · Home | Broadcast newsroom | Published |
| /tournaments/ | Tournament calendar ledger | Published |
| /matches/ | Match desk with platform and source tier | Published |
| /teams/ | Team identity dossiers | Published |
| /players/ | Player role atlas | Published |
| /games/ | Five-genre chapter rail | Published |
| /guides/ | Patch workshop, tactical notebook, reading list | Published |
| /news/ | News desk | Published |
| /about/ | About the newsroom | Published |
| /sources/ | Source hierarchy and corrections | Published |
| /contact/ | Editorial contact | Published |
| /responsible-play/ | Editorial standards | Published |
| /sitemap/ | Editorial colophon and route map | Published |
| /login/ | Account access route (disclosed, not editorial) | Published · noindex |
| /app/ | Editorial companion route (read-only) | Published |
| /Login/playnow | First-party affiliate route | 302 redirect · noindex |
Methodology
How the desk builds the sitemap
The sitemap is built from the editorial surface the desk actually publishes. The desk does not include thin pages, placeholder routes, or routes that have not been verified in the current cycle.
The sitemap mirrors the HTML sitemap on this route and the XML sitemap at /sitemap.xml. The XML sitemap carries the same routes with lastmod and changefreq annotations.
Route shape
How the desk builds the route map
The desk builds the route map from the editorial surface the desk actually publishes. The route map does not include thin pages, placeholder routes, or routes that have not been verified in the current cycle. The route map mirrors the HTML sitemap on this route and the XML sitemap at /sitemap.xml.
Where a route is no longer published, the route is removed from the route map and the corresponding XML sitemap entry is removed on the next refresh. The desk does not keep retired routes in the map for SEO value; the desk's case for the clean map is that a retired route has no editorial value.
Update cadence
How often the route map refreshes
The route map refreshes weekly on Monday and on every Tier 1 release. The refresh date is published in the methodology block at the foot of this route. The XML sitemap carries the same routes with lastmod and changefreq annotations.
Where the desk has published a new guide or a new chapter, the route map refreshes on the same day. Where the desk has retired a route, the route map refreshes on the next Monday.
Route shape
How the desk builds the route map
The desk builds the route map from the editorial surface the desk actually publishes. The route map does not include thin pages, placeholder routes, or routes that have not been verified in the current cycle. The route map mirrors the HTML sitemap on this route and the XML sitemap at /sitemap.xml.
Where a route is no longer published, the route is removed from the route map and the corresponding XML sitemap entry is removed on the next refresh. The desk does not keep retired routes in the map for SEO value; the desk's case for the clean map is that a retired route has no editorial value.
Update cadence
How often the route map refreshes
The route map refreshes weekly on Monday and on every Tier 1 release. The refresh date is published in the methodology block at the foot of this route. The XML sitemap carries the same routes with lastmod and changefreq annotations.
Where the desk has published a new guide or a new chapter, the route map refreshes on the same day. Where the desk has retired a route, the route map refreshes on the next Monday.
Route state
What the state tag on a route carries
Every route on the route map carries a state tag. The state tag is the publication state the desk has filed against the route: published means the route is live and the desk has refreshed it within the cycle; draft means the route is in the editorial queue and not yet live; retired means the route is no longer published and has been removed from the XML sitemap.
Where the state tag shifts, the shift is recorded on the change log with the previous tag, the new tag and the date.
XML mirror
How the route map mirrors the XML sitemap
The route map mirrors the XML sitemap at /sitemap.xml. The XML sitemap carries the same routes with lastmod and changefreq annotations. The XML sitemap refreshes weekly on Monday and on every Tier 1 release.
FAQ · sm
Frequently asked questions, in editorial voice
The desk answers the most common reader questions about this surface in editorial voice. The FAQ is editorial — the desk does not invent answers; the answers cite the surface that already carries the answer.
What does the route map carry?
Every published route on the newsroom. Editorial-only routes are linked from the masthead; commercial or affiliate routes are disclosed separately and labelled.
How often does the map refresh?
Weekly on Monday and on every Tier 1 release. The refresh date is published in the methodology block.
What does the state tag tell me?
Published, draft, or retired. Published means the route is live and the desk has refreshed it within the cycle; draft means the route is in the editorial queue; retired means the route is no longer published.
Where do I find the source hierarchy?
The desk's source hierarchy lives on the methodology page. Every dossier, ledger row and match note carries one of four tiers: Tier 1 (League/Official), Tier 2 (Verified org), Tier 3 (Established media), Tier 4 (Community).
What does the source badge tell me?
The source badge tells you what the desk trusts about the row. A Tier 1 source is a league announcement; a Tier 2 source is an org confirmation; a Tier 3 source is a named reporter; a Tier 4 source is a community post the desk has not yet verified.
How does the desk promote a row's tier?
The desk does not promote a row's tier by editorial decision. A Tier 4 row carries a rumor badge and stays Tier 4 until a Tier 1 or Tier 2 source confirms it. The desk's case for the no-promotion rule is that an editorial promotion would conflate the desk's confidence with the source's confirmation.
How often does the surface refresh?
The surface refreshes weekly on Monday and on every Tier 1 release. The refresh date is published in the methodology block at the foot of every route.
How do I subscribe to updates?
The desk's RSS feed at /feed.xml carries every news desk story. The LLMs manifest at /llms.txt carries the editorial surface as a single document.
How do I file a correction?
Corrections are routed through the corrections email at corrections at esportswagerin dot com. The desk verifies the correction against a Tier 1 or Tier 2 source and updates the row within 48 hours.
Extended notes
How the route map handles a new chapter
When the desk publishes a new chapter — for example, a new competitive gaming genre — the desk adds the chapter's chapter page, the chapter's tournament ledger entries, the chapter's match desk entries, and the chapter's team dossier and player atlas entries. The route map refreshes on the same day.
The route map's discipline for new chapters is that the chapter's chapter page carries the same four fields as every other chapter: the chapter number, the chapter title, the chapter count, and the named beat reporter. The chapter card is not a teaser for the chapter's content; the card points at the chapter's surfaces.
Where a chapter's primary surface changes — for example, the calendar ledger is replaced by a calendar widget — the desk updates the chapter card and the surfaces that point at the chapter. The route map mirrors the change on the same day.
Retirement
How the route map handles a retired route
When the desk retires a route — for example, a discontinued chapter or a merged event — the desk removes the route from the route map and the corresponding XML sitemap entry. The retirement is recorded on the change log with the previous route, the new route (if applicable) and the date.
Where the retirement affects a cross-reference — for example, a chapter card that links to the retired route — the desk updates the cross-reference on the same day. The desk's case for the immediate cross-reference update is that a retired route with active cross-references reads as a broken link.