Editorial note: betkwiff is a field guide to Indian rummy, not a paid platform. Read responsible play before considering any money table.
A field guide to Indian rummy

Robots and indexing policy.

Updated · Aug 2026 Filed from Mumbai

The betkwiff editorial publication follows standard search-engine indexing. The full robots policy is published at /robots.txt. The text version is reproduced below for readers who reached this page directly.

Rules

  • Editorial pages are indexed. Long-reads, news pages, and the canonical pages under /games/, /how-to-play/, /strategy/, /reviews/, /safety/, /news/, /responsible-play/, /is-legal/, /customer-care/, /wallet-kyc/, /about/, /owner/, /contact/, /terms/, /privacy/ are indexed by default.
  • Login endpoints are not indexed. The platform login endpoints (under /Login/) are marked noindex, nofollow.
  • Sponsored links are tagged. Sponsored links are tagged with rel="sponsored" and disclose the commercial relationship.
  • Retired pages are pruned. A page that is retired from the editorial set is removed from the XML sitemap after a 90-day grace period. During the grace period the page is annotated with a noindex directive and a one-line editorial note. After the grace period, the page returns a 410 Gone response.

Canonical URL

Every page declares a canonical URL. The editorial desk uses absolute canonicals (e.g., https://betkwiffin.com/customer-care/) across the publication. The absolute canonical is set in the page's <link rel="canonical"> tag and is also reflected in the Open Graph og:url tag and the Schema.org url property. The publication does not use relative canonicals; the editorial position is that absolute canonicals are easier to audit and easier to reason about when a page is migrated.

The publication's policy on URL structure is unchanged: the publication uses a flat URL structure with a single trailing slash for each canonical page. The publication does not use query parameters for canonical content; query parameters are reserved for tracking and are excluded from the canonical URL. The publication does not use URL fragments for canonical content; fragments are reserved for in-page navigation and are excluded from the canonical URL.

Sitemaps

The publication publishes two sitemaps: a human-readable sitemap at /sitemap/ and an XML sitemap at /sitemap.xml. The two sitemaps are kept in sync; the XML sitemap is generated from the human-readable sitemap on a quarterly cadence. The XML sitemap includes last-modified timestamps for each page, which allows a search engine to prioritise recent updates.

The publication's policy on sitemap updates is unchanged: the sitemap is updated whenever a new page is published, whenever a page is corrected, and whenever a page is retired. Readers who want to be notified when a new page is published can subscribe to the RSS feed; the RSS feed is updated at the time of publication and is the publication's primary distribution channel.

Discussion

For corrections or clarifications, write to the editorial desk via the contact page. The desk aims to acknowledge receipt within one working day and to respond substantively within five working days. The publication's editorial position on indexing policy is that the policy should be transparent, machine-readable, and easy to audit; the desk publishes the robots policy at /robots.txt and the text version on this page, and the two should be in sync. If a reader finds a discrepancy between the two, the desk would rather fix the discrepancy than defend it.

Editorial desk photograph for the indexing policy page
Robots and indexing policy · the publication's policy is transparent, machine-readable, and easy to audit
Crawler policy

How the desk handles crawlers, in plain language.

Crawler policy

The publication's crawler policy is straightforward: editorial pages are indexed by default; login endpoints are marked noindex, nofollow; sponsored links are tagged with rel="sponsored"; retired pages are pruned after a 90-day grace period. The publication does not use a paywall, does not run a cookie wall, and does not block search-engine crawlers. The publication's editorial position is that the publication's editorial content should be reachable by readers who arrive at the publication through search engines, and the desk does not want to put a technical barrier between the reader and the publication's long-reads.

The publication's policy on third-party crawlers is unchanged: the publication permits the major search-engine crawlers and explicitly excludes the crawlers that have been flagged by the editorial community as abusive. The publication's allow-list is published at /robots.txt and is updated when the editorial community flags a new crawler as abusive. The publication's editorial position is that the publication's editorial content should be reachable by readers, and the desk does not want to make allowances for crawlers that have been flagged as abusive.

The publication's policy on AI training crawlers is unchanged: the publication does not currently opt out of AI training crawlers through robots.txt. The publication's editorial position is that the publication's editorial content is editorial and is not free for AI training without a written agreement. The publication is opted out of Common Crawl through the robots.txt, and the publication's editorial position is that the desk should be paid for AI training data the same way other publishers are paid for AI training data.

Meta and Open Graph

Meta tags and Open Graph, in plain language.

Meta policy

The publication's meta-tag policy is straightforward: every page declares a title, a description, a canonical, an Open Graph block (og:title, og:description, og:type, og:url, og:image, og:image:alt, og:site_name), and a Twitter card block. The title is the page's masthead plus the publication's name; the description is a 150–160-character summary of the page's editorial scope; the canonical is the absolute URL of the canonical page. The Open Graph image is the publication's default editorial image, with a 1200x630 aspect ratio and a written alt text.

The publication's policy on Open Graph images is unchanged: the default image is rule-diagram-lede.webp, which is a graphic of the rummy card-hand composition on a lilac-paper background. The image is reachable at /assets/img/hero/rule-diagram-lede.webp and is the publication's default image for Open Graph, Twitter, and Schema.org markup. The image is loaded preconnect from the publication's CDN and is not loaded until the page is rendered.

The publication's policy on Twitter card is unchanged: the publication uses summary_large_image for long-reads and summary for short pages. The Twitter card image is the same image as the Open Graph image, and the Twitter card title and description are the same as the Open Graph title and description. The publication's editorial position is that the Twitter card should be a faithful summary of the Open Graph block, and the desk should not differentiate the two for engagement reasons.

Redirects

How the desk handles redirects, in plain language.

Redirects

The publication's policy on redirects is straightforward: the publication uses 301 (permanent) redirects for pages that have moved within the publication, and 410 (Gone) responses for pages that have been retired from the editorial set. The publication does not use 302 (temporary) redirects within the editorial set; the publication's editorial position is that a redirect that is temporary should be temporary, and the desk should be able to defend any permanent redirect against the question of why the redirect is permanent.

The publication's policy on retired pages is unchanged: a page that is retired from the editorial set returns a 410 Gone response after a 90-day grace period. During the grace period, the page is annotated with a noindex directive and a one-line editorial note explaining the retirement. The retirement note is dated and is reproduced in the desk's quarterly corrections log. The publication's editorial position is that retired pages should be retired cleanly, with a visible note and a 410 response, rather than silently redirected.

The publication's policy on canonical URLs after a migration is unchanged: when a page is migrated, the publication updates the page's canonical URL to the new URL and uses a 301 (permanent) redirect from the old URL to the new URL. The publication's editorial position is that the desk should be able to defend any permanent redirect against the question of why the redirect is permanent, and the desk should be able to defend any retirement of a page against the question of why the page is retired.

The publication's policy on HTTPS is unchanged: every page is served over HTTPS, and the publication's canonical URLs use the https:// scheme. The publication does not serve any page over HTTP, and the publication does not include any HTTP URLs in its editorial content. The publication's editorial position is that serving editorial content over HTTP is a security risk for the reader and is a negative signal for the publication's editorial line.

The publication's policy on HSTS is unchanged: the publication enables HSTS (HTTP Strict Transport Security) to ensure that browsers always connect to the publication over HTTPS. The publication's HSTS policy is published at /hsts.txt and is updated whenever the publication's security policy is updated. The publication's editorial position is that HSTS is a basic security measure for editorial content, and the desk should not require a reader to opt in to HTTPS.

The publication's policy on security headers is unchanged: the publication sets a Content-Security-Policy header, a Referrer-Policy header, and an X-Content-Type-Options header. The publication's editorial position is that security headers are a basic security measure for editorial content, and the desk should not require a reader to opt in to security headers. The publication's security headers are published at /security-headers.txt and are updated whenever the publication's security policy is updated.