Sitemap

Sitemap.

A complete index of every public route on the dreamcatcher editorial desk. The list is grouped by editorial purpose for ease of scanning; the live XML sitemap at /sitemap.xml reflects the canonical order.

Updated: 11 Aug 2026 Total routes: 28 Last verified: against sitemap.xml
A sitemap reference still life with a printed newsroom ticker sheet laid out as an editorial index, a slim pen and a folded rulesheet on a pale linen desk
All routes

All public routes

By purpose

Routes grouped by editorial purpose.

The sitemap below groups every public route by the desk's editorial purpose. Editorial hubs are the read-first routes the desk refreshes quarterly. Trust and safety routes are the read-with-care routes the desk keeps up to date as regulation changes. Brand SERP cluster routes are the reference answers the desk publishes for common branded queries about platforms offering rummy in India.

XML sitemap

The XML sitemap at /sitemap.xml.

The live XML sitemap at /sitemap.xml lists every public route with the same canonical URLs you see on this page. Search engines consume the XML version; readers see the grouped HTML version. The two files are kept in sync by the desk's quarterly review: any route added to the XML sitemap is added to the grouped HTML sitemap in the same revision.

Why two sitemaps

The XML sitemap is the format search engines consume. The HTML sitemap is the format human readers scan. Both list the same routes with the same canonical URLs, but the HTML version groups by editorial purpose so a reader can find a related route without leaving the page they are on.

What the XML sitemap contains

Each entry in the XML sitemap carries the canonical URL, the date the route was last revised and the relative priority the desk assigns to the route in its editorial calendar. Priority is a desk-side signal, not a ranking signal; the desk uses it to plan quarterly review work.

How the sitemap is kept in sync

The sitemap is regenerated whenever a route is added or revised. The desk does not allow the XML and HTML versions to drift; if you spot a route listed on this page that is not in the XML version, or a route in the XML version that is not on this page, the contact page lists the email to send the desk.

Route priority

How the desk prioritises route revisions.

Every route on this sitemap carries a relative priority in the desk's quarterly revision calendar. Priority reflects how often the editorial content changes against real-world events — rules updates, KYC policy changes, regulatory consultation windows — not against marketing or seasonal considerations.

Tier 1 routes: revised every revision cycle

The rules ledger, the strategy boundaries, the format gallery, the how-to-play guide and the platform reviews sit in the top tier. These routes change whenever an underlying source changes — a rulebook amendment, a regulatory draft, a published platform withdrawal window update. The desk refreshes the tier 1 routes inside every quarterly revision cycle.

Tier 2 routes: revised when the source changes

The safety explainer, the responsible-play framework, the state-by-state eligibility page, the legal reference and the wallet and KYC explainer sit in the second tier. These routes are revised when a named source changes — for example, when MeitY publishes a draft amendment or when the Promotion and Regulation of Online Gaming Act, 2025 reaches a new consultation milestone.

Tier 3 routes: revised on demand

The brand SERP cluster routes — customer-care, owner, login, download, app, apk-download, refer-code, bonus-code, review, delete-account, official-website — sit in the third tier. These routes are revised on demand: when a reader emails a correction, when a platform changes its published name, or when a new branded search query reaches the desk.

Tier 4 routes: revised only when policy changes

The terms of use, privacy policy, about the desk and contact pages sit in the fourth tier. These routes are revised only when the underlying editorial policy changes — for example, when the desk expands its verification standards or revises its data-retention window. The fourth tier is the most stable part of the sitemap.

Editorial calendar

The desk runs a quarterly editorial calendar. Each quarter, the desk refreshes the tier 1 routes, runs a read-through of the tier 2 routes, picks up reader corrections on the tier 3 routes and revises any tier 4 route whose underlying policy has changed. The calendar is the desk's commitment to the reader; the desk publishes the last-revision date on every route.

Reader-triggered revisions

A reader correction or a regulatory tip sent to the editorial email can trigger an out-of-cycle revision. The desk treats reader-triggered revisions with the same rigour as quarterly revisions: the desk verifies the correction against the underlying source, revises the affected route and updates the dateline.

How priority is assigned

Priority is assigned at route creation and reviewed at every quarterly revision. The desk does not lower the priority of an existing route without a reason; the desk raises the priority when an underlying source has shifted (for example, when a regulator publishes a new draft amendment).

Crawl instructions

What the desk tells crawlers in robots.txt.

The robots.txt file at /robots.txt tells well-behaved crawlers which routes to crawl, which routes to skip, and where the XML sitemap sits. The desk publishes the robots.txt file in plain English so a reader or a search-engine operator can see the desk's crawl policy.

What the desk allows

The desk allows well-behaved crawlers from the major consumer search engines. The desk publishes the list of allowed crawler user agents on the robots.txt file. The desk does not require a robots.txt token to crawl the publication.

What the desk blocks

The desk blocks crawlers that scrape content for republishing, crawlers that ignore the robots.txt instructions and crawlers that place excessive load on the desk's hosting account. The desk publishes the list of blocked crawler user agents on the robots.txt file.

Where the sitemap sits

The XML sitemap sits at /sitemap.xml. The robots.txt file points crawlers to the XML sitemap. The HTML sitemap on this page is the human-readable version of the same list of routes.

How the desk handles a crawler complaint

Where a reader or a platform reports a crawler that is ignoring the robots.txt file, the desk reads the report sent to the editorial email. The desk does not host the offending crawler; the desk directs the reader to the search engine's own abuse-reporting channel.

How the desk handles a sitemap submission

Search engines can submit the XML sitemap directly from their own consoles. The desk does not require a sitemap submission; the search engines discover the XML sitemap from the robots.txt file. The desk publishes the XML sitemap at the canonical root so the search engines can index it without a manual submission.

How the desk handles a broken route

Where a route returns a 404, the desk removes the route from the XML sitemap and either restores the route or redirects it to a surviving route with a 301. The 404 page on this desk points readers to the sitemap so they can find a working route.

Extended reference

How to read this sitemap.

The sitemap on this page is the read-first map of the desk: the grouped list shows you which route covers which editorial purpose, the XML link shows you the canonical version search engines consume, and the robots file shows you the desk's crawl instructions. Read the sitemap before you cite a desk route.

How the desk counts a route as public

A route is counted as public when it returns a 200 response, includes a complete footer, lists a real canonical URL and has a title that names the editorial purpose. Routes that fail any of these checks are not added to the sitemap and are not indexed.

How the desk handles duplicates

The desk does not publish near-duplicate routes. Where two routes cover overlapping editorial territory — for example, customer-care and contact — the sitemap names both and the body copy distinguishes them: contact is the desk's editorial inbox, customer-care is the desk's reference answer for platform support queries.

How the desk handles redirects

Routes that the desk has consolidated are redirected to the surviving route with a 301. The sitemap lists only the surviving route; the redirect is a server-side instruction that search engines honour without an explicit sitemap entry.

How the desk handles new routes

A new route is added to the sitemap after it has been written, reviewed against the editorial standards on the about page, and verified to resolve with a 200 response. New routes are added in batch during the quarterly revision, not ad hoc.

How the desk handles broken routes

If a route returns a 404, the desk removes it from the sitemap and either restores the route or redirects it to a surviving route. The 404 page on this desk points readers to the sitemap so they can find a working route.

How the desk handles regional variants

The desk does not publish state-specific sitemaps. State-specific editorial guidance is consolidated into the is-legal page, which lists each state's eligibility status with a link back to the relevant primary source.