The lab's analytical content
Lab reports cover captain picks, contest strategy, player form, and weekly retrospectives. Every report is freely accessible without signup.
Fantasy Cricket guide
/fantasy-cricket/ — the lab's guide to fantasy cricket formats, scoring, and squad-building principles.
Live matches
/live-matches/ — today's and tomorrow's fixtures with ball-by-ball fantasy point sync.
Predictions
/predictions/ — match projections, captain confidence scores, and differential pick rankings.
Captain picks
/captain-picks/ — the differential-captain matrix, consensus vs differential comparison, and 90-day hit rate.
Test results
/test-results/ — 90-day captain hit rate, ROI by contest tier, and weekly re-test findings.
Methodology
/methodology.html — five-stage report pipeline, data sources, and assumption-risk documentation.
Winners
/winners/ — verified contest winners, payout timelines, and the captain pick that won each mega.
News
/news/ — squad announcements, injury updates, and pre-match team news across IPL and T20 internationals.
Tools
/tools/ — projection calculator, ownership simulator, ROI audit spreadsheet, and captain confidence model.
T20 tips
/t20-tips/ — powerplay read, death-overs strategy, and venue-specific captain picks.
Fantasy tips
/fantasy-tips/ — captain selection math, ownership-aware squad building, and contest tier choice.
Blog
/blog.html — strategy posts, match-up previews, and editorial deep-dives.
App, account, and platform
Brand SERP and account pages cover the app, account management, customer support, and platform-specific questions.
Login
/login.html — sign-in portal, security, 2FA, session management.
Sign up
/signup.html — mobile OTP registration, welcome bonus flow.
App
/app.html — mobile app overview, Android/iOS parity.
Download app
/download.html — direct install, system requirements, storage.
APK download
/apk-download.html — APK signature verification, sideloading checklist.
Refer code
/refer-code.html — share, earn ₹50 per signup, climb the tiered referral ladder.
Bonus code
/bonus-code.html — promo codes, wagering math, validity windows.
Wallet and KYC
/wallet-kyc.html — PAN verification, TDS mechanics, payment rails.
Customer care
/customer-care.html — support email, KYC escalation, withdrawal timelines.
Review
/review.html — captain hit rate, payout speed, lab report cadence.
How to play
/how-to-play.html — 4-step squad selection, credit cap, contest tier choice.
Is it legal
/is-legal.html — skill vs chance, state rules, age requirement.
Owner
/owner.html — parent company, leadership team, regulatory standing.
Delete account
/delete-account.html — 14-day cooling-off, data backup window.
Official website
/official-website.html — verified URL, mirror-site warnings.
Comparisons
/comparisons.html — vs Dream11, MPL, My11Circle, Vision11.
Fantasy cricket app
/fantasy-cricket-app/ — feature list, system requirements, Android/iOS parity.
SG11 fantasy
/sg11-fantasy/ — vs SG11 Fantasy.
Reviews
/reviews/ — verified reader feedback.
Points system
/points-system/ — full T20 scoring grid.
Contests
/contests/ — mega pools, small leagues, head-to-heads.
Disclaimer
/disclaimer.html — no warranty on picks.
FAQ
/faq/ — contest rules, payout timelines, KYC requirements.
The lab's legal pages
Legal and disclosure pages cover the lab's terms, privacy policy, disclosure, and responsible play commitments.
Privacy policy
/privacy-policy.html — data collection, cookies, third-party processors.
Terms and conditions
/terms-conditions.html — eligibility, fair play rules, dispute resolution.
Disclosure
/disclosure.html — TDS policy, regulatory standing, partnerships.
Responsible play
/responsible-play.html — deposit limits, self-exclusion, support.
About
/about.html — mission, editorial principles, lab team.
Contact
/contact.html — support inbox, press line, partnership contact.
Sitemap questions, answered
The most common questions about sitemap on PlayExch, with detailed answers.
How many pages are on the lab?
The lab publishes 35+ pages covering lab reports, brand SERP, account management, and legal disclosure. The full list is on this sitemap page.
How often is the sitemap updated?
The sitemap is updated whenever a new page is published. The sitemap includes the publication date for each page. The lab's XML sitemap is available at /sitemap.xml.
Is there an XML sitemap?
Yes. /sitemap.xml is the lab's XML sitemap, formatted for search-engine crawlers. The XML sitemap updates automatically whenever a new page is published.
Can I suggest a new page?
Yes. Submit suggestions via the feedback inbox at [email protected]. The lab reviews suggestions every Monday and adds new pages when the topic fits the lab's editorial scope.
How do I find a specific lab report?
The blog page lists every published report with publication dates and topic tags. The captain-picks hub has all captain-matrix reports. The methodology page has all methodology posts.
Ready to start with PlayExch?
Read the lab reports, pick a contest tier, run ten squads with the captain reads, and audit your ROI after fifty contests.Within the PlayExch framework, read the lab reports, pick a contest tier, run ten squads with the captain reads, and audit your ROI after fifty contests.
How the lab's information architecture is organized
The sitemap reflects the lab's editorial hub-and-spoke architecture. Lab reports are the hub; brand SERP and account pages are the spokes; legal pages are the foundation.
Hub-and-spoke architecture
Lab reports (captain picks, contest strategy, player form, methodology) are the hub. Every brand SERP page and every account page links back to the hub. The hub-and-spoke architecture ensures every page on the site is reachable from the homepage within three clicks.
Editorial cadence
Lab reports update weekly. Brand SERP pages update as features change. Account pages update as policies evolve. Legal pages update as regulations change. The lab's editorial cadence is published on the about page.
URL conventions
Lab reports use subdirectory URLs (e.g., /captain-picks/). Brand SERP pages use root .html URLs (e.g., /login.html). The conventions are enforced by the build pipeline. The conventions are documented on the methodology page.
Canonical URLs
Every page has a canonical URL. The canonical URL is the preferred URL for indexing. Subdirectory pages have canonical URLs ending in /; brand SERP pages have canonical URLs ending in .html. The canonical URLs are enforced via the rel='canonical' link tag.
The lab's extended perspective
A longer-form walk-through of the underlying dynamics, the data behind the recommendations, and the lab's analytical approach.Within the PlayExch framework, a longer-form walk-through of the underlying dynamics, the data behind the recommendations, and the lab's analytical approach.
Methodology in depth
The lab's methodology is built on a five-stage pipeline. Every published report passes through framing, dataset pull, analysis, assumption-risk documentation, and re-test. The pipeline is published in full on the methodology page. The lab's edge comes from data freshness and analyst expertise, not from a secret formula. Other analysts can re-run the experiments with the published datasets and the published model code. The lab publishes every dataset version and every model version. The lab never quietly updates a dataset after the conclusion lands.Within the PlayExch framework, the lab's methodology is built on a five-stage pipeline. Fantasy readers should note that every published report passes through framing, dataset pull, analysis, assumption-risk documentation, and re-test. The pipeline is published in full on the methodology page This is why the sitemap desk treats it as a baseline. The lab's edge comes from data freshness and analyst expertise, not from a secret formula. On sitemap, other analysts can re-run the experiments with the published datasets and the published model code. For the sitemap desk, the lab publishes every dataset version and every model version. Within the PlayExch framework, the lab never quietly updates a dataset after the conclusion lands.
Data sources in depth
The lab pulls data from four primary sources. Match data comes from official tournament data partners, cross-checked against broadcast records. Ownership data comes from public contest-platform feeds, sampled every 30 seconds during contest open windows. Contest result archives come from publicly published leaderboards. Self-collected squad logs come from volunteer readers who submit their picks at lock time. Each source has a published quality score and a published latency benchmark. The lab's data-quality framework is reviewed quarterly by the statistics team.Within the PlayExch framework, the lab pulls data from four primary sources. Fantasy readers should note that match data comes from official tournament data partners, cross-checked against broadcast records. Ownership data comes from public contest-platform feeds, sampled every 30 seconds during contest open windows This is why the sitemap desk treats it as a baseline. Contest result archives come from publicly published leaderboards. On sitemap, self-collected squad logs come from volunteer readers who submit their picks at lock time. For the sitemap desk, each source has a published quality score and a published latency benchmark. Within the PlayExch framework, the lab's data-quality framework is reviewed quarterly by the statistics team.
Reader-safety commitments
The lab's reader-safety commitments cover deposit limits, self-exclusion, play-time alerts, loss trackers, cool-down reminders, and family-controls integration. The lab publishes the safety commitments on the responsible-play page. The lab refuses to partner with operators that do not enforce responsible-play defaults. The lab's reader-safety framework is reviewed annually by an external auditor.Within the PlayExch framework, the lab's reader-safety commitments cover deposit limits, self-exclusion, play-time alerts, loss trackers, cool-down reminders, and family-controls integration. Fantasy readers should note that the lab publishes the safety commitments on the responsible-play page. The lab refuses to partner with operators that do not enforce responsible-play defaults This is why the sitemap desk treats it as a baseline. The lab's reader-safety framework is reviewed annually by an external auditor.
Editorial principles
The lab operates by five public editorial principles. No sponsored picks — no contest operator, brand, or individual can pay the lab to feature a captain pick. Methodology is public — every model's code is published on the methodology page. Misses are published — every Monday morning the lab publishes the previous week's misses alongside the hits. Reader-funded economics — the lab's long-term economics rely on reader subscriptions and contest-entry referrals, not on advertising. Responsible play by default — every contest lobby on the lab's partner platforms shows a responsible-play banner.Within the PlayExch framework, the lab operates by five public editorial principles. Fantasy readers should note that no sponsored picks — no contest operator, brand, or individual can pay the lab to feature a captain pick. Methodology is public — every model's code is published on the methodology page This is why the sitemap desk treats it as a baseline. Misses are published — every Monday morning the lab publishes the previous week's misses alongside the hits. On sitemap, reader-funded economics — the lab's long-term economics rely on reader subscriptions and contest-entry referrals, not on advertising. For the sitemap desk, responsible play by default — every contest lobby on the lab's partner platforms shows a responsible-play banner.
Quarterly transparency
Every quarter the lab publishes a transparency report covering methodology changes, hit-rate recalibrations, partner-operator relationships, and revenue mix. The report is published on the 15th of the month following quarter end. The most recent report covers Q1 2026 and shows a 61% captain hit rate over the trailing 90 days, a 48/47/5 revenue split between subscriptions, referrals, and other, and four partner operators. The report is available on the disclosure page.Within the PlayExch framework, every quarter the lab publishes a transparency report covering methodology changes, hit-rate recalibrations, partner-operator relationships, and revenue mix. Fantasy readers should note that the report is published on the 15th of the month following quarter end. The most recent report covers Q1 2026 and shows a 61% captain hit rate over the trailing 90 days, a 48/47/5 revenue split between subscriptions, referrals, and other, and four partner operators This is why the sitemap desk treats it as a baseline. The report is available on the disclosure page.
