Sitemap
Every public route on boomerangin.com, listed by section. The sitemap exists for readers who prefer a single index page and for crawlers that want a clean URL list.
This page is the human-readable counterpart to the XML sitemap at /sitemap/sitemap.xml. It is organised by editorial intent, not by URL depth, and every link below resolves to a public Boomerang page. There are no login forms, wallet flows, or APK mirrors on this publication; the only commercial surface is a single first-party redirect to the platform's play page, and that link is labelled as such on the route where it appears.
How the sitemap is organised
Boomerang organises its public routes into four editorial categories. Editorial hubs answer the questions a reader is most likely to ask on a first visit: what is rummy, what are the rules, what does a hand look like, what should a discard decision consider, which platforms observe a usable interface, and where does the safety checklist live. Brand-intent routes answer narrower questions that already carry a brand name: sign-in, app, download, APK, customer care, jurisdiction, wallet and KYC, refer code, bonus code, editorial review, account deletion, and the owner page. Company-and-support routes are the standard governance pages every publication publishes: about, contact, privacy and terms. Crawler files, which include the XML sitemap, the RSS feed, and the robots.txt, are listed at the bottom because they are intended for search-engine indexers rather than for human readers.
Every route in the sitemap is a public Boomerang page with a clear title, a publication date and a canonical URL. A reader who wants to read a route can click the route name; a reader who wants to verify a route can read the route description; a reader who wants to bookmark a route can copy the URL. Boomerang's editorial standard is to keep every route in the sitemap in sync with the actual page; any change to a route is reflected in the sitemap at the next editorial pass.
The sitemap is reviewed at every editorial pass and updated when a route is added, removed or renamed. The change log is the canonical record of every change to the sitemap; a reader who wants to verify a change can subscribe to the Boomerang RSS feed or visit the change-log route directly. Boomerang does not publish deep-link shortcuts inside the sitemap that bypass the editorial framing of a route; the goal of the sitemap is to give a reader a clean map of the publication, not to surface marketing routes ahead of editorial ones.
How a reader should use the sitemap
Readers who arrive at the sitemap from a search engine or a browser bookmark can use the four lists below as a starting point. The editorial hubs are the routes a reader is most likely to want on a first visit; the brand-intent routes answer narrower questions that have a brand-name attached; the company-and-support routes are the standard governance pages every publication publishes; and the crawler files are intended for search-engine indexers rather than for human readers. Each route in the sitemap resolves to a real Boomerang page, and each route description tells the reader what the page covers without forcing them to open it first.
If a route a reader is looking for is missing from this sitemap, the most likely explanation is that Boomerang has not yet published a route for that specific question. The publication does not publish placeholders; instead, the contact route is the right place to ask for a route that has not yet been written, and the change-log route will note any new routes that have been added since the last editorial pass. A reader who writes to the contact mailbox with a clear, well-framed question is providing the most useful kind of input the editorial desk receives.
The sitemap is intentionally comprehensive rather than selective. Boomerang's editorial standard is to list every public route on a single index page, so a reader who arrives from any external source can find every other route on the publication from one place. The downside of that standard is that the list is long; the upside is that a reader who knows what they are looking for does not need to remember a particular URL pattern. The four categories give the reader a way to navigate that long list by intent rather than by alphabetic order.
Sitemap editorial policy
The sitemap is reviewed at every editorial pass and updated when a route is added, removed or renamed. Boomerang does not publish deep-link shortcuts inside the sitemap that bypass the editorial framing of a route; the goal of the sitemap is to give a reader a clean map of the publication, not to surface marketing routes ahead of editorial ones. Commercial surfaces are kept to a single first-party redirect, and that redirect is not listed in the sitemap because it is not a Boomerang page.
The sitemap does not include third-party URLs, partner landing pages, or any route that is not a public Boomerang page. Readers who want to verify a commercial surface should look at the rel attributes on the link itself (sponsored, nofollow, noopener, noreferrer) and at the surrounding copy; the editorial standard is to label every commercial surface clearly so the reader can choose whether to follow it. A reader who wants to know why Boomerang publishes the redirect at all can read the editorial desk's scope statement on the about route.
The sitemap categorisation is stable across editorial passes. The four categories (editorial hubs, brand-intent routes, company-and-support routes, and crawler files) are reviewed when a new route is added, when an existing route is retired, and when a route moves between categories because its editorial scope has shifted. The change log records every such decision so a reader can trace how the publication's taxonomy has evolved over time. The editorial desk treats category moves the same way it treats route renames: the previous URL stays live with a redirect until the change has been in place for at least one editorial cycle.
What the sitemap does not list
The sitemap does not include third-party URLs, partner landing pages, or any route that is not a public Boomerang page. It does not list the platform reached through the first-party redirect, because the platform is not a Boomerang page. Boomerang's editorial standard is to keep the sitemap focused on Boomerang's own routes, and the platform reached through the redirect is documented on the platform's own help page rather than on Boomerang's sitemap. A reader who wants to verify the platform's documentation can follow the redirect and read the platform's help page directly. The sitemap also does not list draft routes, retired routes, or routes that are not yet published. Boomerang's editorial standard is to publish only what is currently true, and the sitemap is a snapshot of that truth at the last editorial pass. A reader who is waiting for a new route can subscribe to the RSS feed to be notified when the route is published; a reader who wants to suggest a new route can use the contact route to write to the editorial desk. The desk treats suggestions as input to the next editorial pass, and a suggestion that includes a clear alternative is the most useful kind of input.
The sitemap is regenerated at every editorial pass and is served as a static HTML page rather than as a dynamically generated list. The static approach means the sitemap reflects the publication's state at the moment of generation rather than at the moment of request; a reader who wants the most current state should consult the XML sitemap or the RSS feed, both of which are updated as routes are added, removed, or renamed. The static HTML sitemap is updated alongside the XML sitemap at the same editorial pass, so the two sources never disagree about which routes are live.
Changes since the last editorial pass
Every change to this sitemap is logged on the change-log route, including route additions, route removals, route renames, and changes to the editorial framing of a route. Readers who want to verify a change can subscribe to the Boomerang RSS feed or visit the change-log route directly. The change log is the canonical source of truth for the publication's editorial state; the sitemap is a snapshot of that state at the last editorial pass.
When a route is renamed, Boomerang keeps the old URL live with a 301 redirect to the new URL for at least one editorial cycle, so external links do not break. The sitemap only lists the current canonical URL; the redirect history is held in the change log. This convention keeps the sitemap compact while preserving the back-compatibility that external readers rely on. The redirect history is also reflected in the XML sitemap for search-engine indexers that follow the canonical URL strictly.
The publication does not publish draft routes, retired routes, or routes that are not yet live. A reader who is waiting for a new route can subscribe to the RSS feed to be notified when the route is published; a reader who wants to suggest a new route can use the contact route to write to the editorial desk. The desk treats suggestions as input to the next editorial pass, and a suggestion that includes a clear alternative is the most useful kind of input. The sitemap is updated when the suggested route is published, not before, so the list always reflects what is actually live.
Editorial hubs
- Home
- Games. Rule catalog and variant index.
- How to play. Beginner turn-by-turn guide.
- Strategy. Discard decisions and sequence limits.
- Reviews. Platform usability notes.
- Safety. Verification and payment review.
- Responsible play. Limits, pauses, and support routes.
- . Documented change log.