Sitemap

The publication's full route index. The list below mirrors the canonical sitemap.xml; the canonical file at /sitemap.xml is the index the search engines read.

An open rummy table session with a brass pencil and a thin route ledger laid flat on the felt

How this index is organised

Four clusters the publication routes its reader to

Editorial hubs: the format-reading pages. The route list is games, how-to-play, strategy, reviews, safety and responsible-play.
Brand SERP routes: the reader's decision-shape pages. The route list is login, app, download, apk-download, refer-code, bonus-code, customer-care, is-legal, owner, wallet-kyc, delete-account and official-website.
Company routes: about, contact, privacy, terms, responsible-play and sitemap.
News notes: short-format updates. The route list is format-update, rule-clarification and product-note.

The contact widget at /contact/ is noindex; it does not appear in this index. The two reading-room routes that contain only editorial content are /customer-care/ and /is-legal/.

Reading the index

How to use the sitemap as a reader

Pick the cluster that matches the question the reader is actually making. The four clusters are formats, money, jurisdiction or company.
Follow the editorial hub first; the publication reads the operator's help-centre article before the reader sees the page.
Use the Brand SERP route when the reader is making a decision, not asking a contextual question.
Use the canonical sitemap.xml when the reader wants a machine-readable list of every URL.

The contact widget at /contact/ is noindex; it does not appear in this index. The two reading-room routes that contain only editorial content are /customer-care/ and /is-legal/.