How the route index is organised
The route index groups every route on myteam11online.com into five columns. Each column is a different reading angle: Fantasy covers how the game is played, Brand covers the operator routes players search for by name, Trust covers the controls and the legal frame, Library covers the cricket reference material, and Legal covers the policies that govern play.
Start with the column that matches your question. Inside each column, the routes are ordered by topic. Contest formats and captain picks lead the Fantasy column; sign-in and download lead the Brand column; and the responsible-play hub leads the Trust column. The full flat list further down repeats the same routes in alphabetical order so you can jump straight to a slug when you already know it.
A route appears here as soon as the entry is published. A route disappears here when the entry is retired. The flat list below is the same set you see in the XML mirror that search engines read; the two stay in step.
The Fantasy column
The Fantasy column is the heart of the desk. The contests page lines up the four formats you can join (Practice, Head-to-Head, Mega League and the practice-only lobby) and walks through entry bound, leaderboard size and the captain multiplier on each. The captain-picks page is the working ledger we update every match week. It ranks the captain options by role fit, recent form, matchup and boundary share, and it spells out the four reads we apply before any name goes on top of the squad. The scoring page is the public scoring table, with every run, wicket, catch and bonus line, and the points each event pays out.
The leaderboards page shows where the live rank is right now and how the cohorts are split (top 10%, top quartile, median finisher). The how-to-play page is the nine-step path from a fresh sign-up to a locked squad, with screenshots of the actual app screens at each step. The fantasy-tips page is a ten-item checklist you can run through in two minutes before lock. The compare page lays two formats side by side on a single table. The predictions page is the format-by-format prediction desk, written the morning of each fixture. The FAQ page is the routing layer for the questions we hear most often: sign-in trouble, payout timing, contest cancellation and the captain change window. The strategy page is the long-form read on squad building and captain logic, written for a player who already knows the scoring table but wants to think harder about the captain pick.
The Brand column
The Brand column is where players end up when they search the operator by name rather than by topic. The login page is the sign-in entry. The app page is the mobile-app landing. The download page and the apk-download page cover the Android and iOS install paths side by side. The refer-code page and the bonus-code page cover the two sign-up incentives; refer-code-hub is the deeper read on how the referral chain pays out. The review and reviews pages cover independent write-ups and player feedback. The customer-care page is the help-desk entry, with live chat, email and the callback window.
The is-legal page covers the legality of paid fantasy cricket across Indian states. The owner page is the about-the-company read. The official-website page is the canonical-URL explainer. The delete-account page walks through the self-exclusion and account-closure path. The wallet-kyc page covers PAN, Aadhaar and bank-account verification for the wallet.
The Trust column
The Trust column is where the responsible-play, KYC, state and support routes live. The responsible-play page is the main hub, covering deposit caps, time-outs, self-exclusion and the links to the national helpline. The responsible-play-hub page is the dedicated hub that expands each control with the steps to switch it on. The kyc-payments route is the dedicated entry that walks through PAN first, Aadhaar second and bank-account last, in the order the operator checks them.
The state-eligibility page lists the current set of eligible Indian states, with the states where paid entry is restricted called out at the top. The safety page is the operator's safety policies in plain language. The support page is the help-desk index, covering the categories, the response window and the email path for issues that don't fit a category.
The Library column
The Library column is the cricket reference material. The matches page is the fixture calendar with the contest open and close windows next to each game. The news page is the editorial cricket desk, with match previews, captain-pick logic, toss calls and the longer reads that explain a series. Three sub-routes are linked from the news index: india-t20i-captain-pick-logic covers the captain-pick logic for India T20Is, practice-session-bowling-rotations covers how teams rotate their bowlers in the nets, and toss-call-impact-fantasy-pick covers how the toss call reshapes the captain pick on the night.
The players page is the squad-by-squad player index. The teams page is the team index with the squad list, the captain and the home ground. The winners page is the recent-winners leaderboard, with the entry, the rank and the payout next to each name.
The Legal column
The Legal column covers the policies. The cookies page lists the cookie categories and the consent path. The dmca page covers the takedown procedure for copyrighted material. The legal page is the operator disclosure. The terms page is the terms of service. The privacy page is the privacy policy. The cookie-settings button in the footer opens the same consent panel for users who want to revisit their choices later.
How the route set stays current
The route set in the column grid matches the route set in the flat list below and the route set in the app. When a new route goes live on myteam11online.com, the route appears here on the same day, in the column that fits. When a route is retired, the route is removed from this index and from the XML mirror at the same time. Editorial pages carry a date stamp so you can tell at a glance how fresh the read is.
What the route index does not include
The route index lists public routes only. It does not list unpublished drafts, retired entries, or routes that are restricted to signed-in players. The full route set, including the in-app routes, is larger than what appears here.
How to use the route index
Open the column that matches your question. Pick the route that fits. Read the entry it points to. If that entry points to a second entry (for example, responsible-play points to responsible-play-hub for the controls), follow the link and read the deeper entry. When you are ready to act on the answer, sign in to the app and verify. The app is the live system, and this index is the editorial map to it.
Sitemap by column
Every route on myteam11online.com, sorted into five columns. Each column is a different reading angle: Fantasy for the game itself, Brand for the operator routes, Trust for controls and KYC, Library for cricket reference, and Legal for policies. Pick the column that matches your question and follow the link.
Fantasy
Brand
Trust
Full route list and update cadence
The flat list below carries every route on myteam11online.com with the route name, the slug and a rough update cadence. Cadence here is a guide, not a promise. The actual update timing depends on the match calendar and on how often the operator changes the policy. The home page and the news index are the most frequently updated; the dated articles under /news/ change month to month; the editorial hubs hold steady for longer.
The same flat list is published as a separate XML mirror for search engines; the human-readable HTML index you are reading now, and the machine-readable XML mirror, stay in step with each other. When a new route is published, the slug appears here and in the XML on the same day. When a route is retired, both mirrors drop it at the same time.
How to read the cadence column
The cadence column is a guide to how often the entry is refreshed, not a strict schedule. Daily means the entry is updated whenever the live cricket state moves (fixtures, captain announcements, payout timings). Weekly means the entry is reviewed and refreshed at least once a week. Monthly means the entry is reviewed and refreshed at least once a month, usually around the start of a new series or when the policy changes.
Where the guide and the actual entry disagree, the entry is correct. Entries carry a date stamp at the bottom of the article that shows the last refresh, so you can check at a glance how fresh the read is.
How to read the route list
Each entry in the route list carries three pieces: the route name (a human-readable label), the slug (the URL path on myteam11online.com) and the cadence (a guide to how often the entry is refreshed). The list below is alphabetical by route name. If you already know the slug, use Ctrl+F to jump straight to it; if you only know the topic, jump back up to the column grid and pick the route from there.
What the route list does not include
The flat list does not include unpublished drafts, retired entries, or routes that are restricted to signed-in players. The full set of routes, including the in-app screens and the signed-in dashboard, is larger than what appears here. The route index is the editorial map to the public routes; the app is the live system underneath.
- Home
- apk-download
- app
- bonus-code
- captain-picks
- compare
- contests
- cookies
- customer-care
- delete-account
- dmca
- download
- fantasy-tips
- faq
- how-to-play
- is-legal
- kyc-payments
- leaderboards
- legal
- login
- matches
- official-website
- owner
- players
- predictions
- privacy
- refer-code-hub
- refer-code
- responsible-play-hub
- responsible-play
- review
- reviews
- safety
- scoring
- sitemap
- state-eligibility
- strategy
- support
- teams
- terms
- wallet-kyc
- winners
How to use the full route list
Scroll through the flat list until you spot the topic you want, then follow the link. If you are coming back to a specific entry you already know (the captain-picks ledger, the scoring table, the state-eligibility list), use Ctrl+F on the flat list below to jump to the slug. Each entry in the list is a working link that opens the dedicated entry in a new tab.
How this index lines up with the app
The routes you see here mirror the public routes in the app. The operator may also publish screens inside the signed-in app (match centre, wallet, leaderboard, contest join, payout history) that do not have a separate slug on myteam11online.com. Those screens live inside the app and are not listed here.
The index updates when a route is published or retired on the public routes. The in-app screens update on the operator's own schedule, which is usually faster (a live leaderboard updates every ball). Where the public route and the in-app screen disagree on a live value (current rank, payout total, contest status), the app screen is the live system.
What the route list does not include
The flat list does not include unpublished drafts, retired entries, or routes that are restricted to signed-in players. The route index is the editorial map to the public routes; the app is the live system underneath.
How to use the route list
Scroll until you spot the entry you want. Follow the link. Read the dedicated entry. If that entry points to a second entry (for example, responsible-play points to responsible-play-hub for the controls, and kyc-payments lists the verification order), follow the second link too. When you are ready to act on the answer (joining a contest, setting a captain, changing a limit), sign in to the app and verify there.
Reading the route index alongside the FAQ desk and the captain ledger
The route index, the FAQ desk and the captain-picks ledger are three different reads on the same desk. The index answers "which route covers this question?" The FAQ desk answers "what is the right call on this question?" The captain-picks ledger answers "which name goes on top of the squad tonight?" Each read has a job. The three work together when you read them in sequence.
The sequence is straightforward. Start at the route index and find the entry that matches your question. Read the entry. It usually points to a deeper entry on the same topic (responsible-play points to responsible-play-hub, kyc-payments points to the verification order). Once you have the topic pinned down, jump to the FAQ desk and check whether your question is one of the common ones; if it is, the FAQ desk gives you the short answer in two paragraphs. If your question is about tonight's captain pick, jump to the captain-picks ledger and run the four reads (role fit, recent form, matchup, boundary share) on the candidates you have in mind.
How the route index stays in step with the FAQ desk
The route index and the FAQ desk are reviewed at the same time. When a new FAQ answer goes live, the route index points to it the same day; when an old FAQ answer is retired, the index drops the reference. Editorial pages carry a last-refresh date stamp so you can see at a glance how fresh the read is; where the index and the FAQ desk disagree on a topic, the dedicated entry is the deeper read and the FAQ is the short answer.
What the route index does not cover
The route index is the public map of the public routes. It does not cover in-app screens, signed-in dashboards, or unpublished drafts. The FAQ desk and the captain-picks ledger are public reads, so both appear in the index under their slugs.
How to read the three together
Open the route index. Pick the column that fits. Follow the link to the entry. Read the entry. If your question is a common one, check the FAQ desk for the short answer. If your question is about tonight's captain, run the four reads on the captain-picks ledger. When you are ready to act, sign in to the app and verify. The app is the live system, and the three public reads are the editorial map to it.
How the route index helps search engines and humans
The route index is written for two readers. Search engines use the XML mirror to discover new routes; humans use the HTML index you are reading now to navigate. The two views stay in step: a slug that appears in one appears in the other on the same day.
Search engine discovery
Search engines crawl the XML mirror to find routes they have not yet indexed. The XML mirror is published as sitemap.xml at the root of myteam11online.com. When a new route goes live, the slug lands in the XML mirror on the same day, which gives the search engine a faster path to discovery than waiting for a crawl. Where the XML mirror and the search engine's own index disagree on which routes exist, the search engine's index is the source of truth for what is actually indexed.
The XML mirror and the HTML index you are reading now carry the same set of slugs. The XML version is for machines; the HTML version is for humans. Both are updated at the same time.
Human discovery
Humans reach the route index in two ways. The first is the direct path: a player who knows the operator and types "myteam11 sitemap" into a search engine. The second is the indirect path, where a player lands on a deep entry (say, the captain-picks ledger for the India T20I side) and scrolls to the footer to see what else is published. The route index is organised for both paths. The column grid at the top is the entry point for someone who knows the topic; the flat list further down is the entry point for someone who knows the slug.
If you arrived here looking for a specific entry, use Ctrl+F on the flat list below to jump to the slug. If you arrived here looking for a topic, jump back up to the column grid and pick the column that fits.
What the route index does not include
The route index lists public routes only. It does not list in-app screens, signed-in dashboards, or unpublished drafts. Where an entry exists in the app but does not have a separate URL on myteam11online.com, that entry is reachable only from inside the signed-in app.
How to use the route index
Find your topic in the column grid. Follow the link. Read the dedicated entry. When you are ready to act (joining a contest, setting a captain, changing a limit), sign in to the app and verify there.
How to use the route index as a starting point
The route index is the natural starting point for any read on myteam11online.com. Open the column grid, find the column that matches your question, follow the link to the dedicated entry, read the entry. The dedicated entry usually points to a second entry on the same topic; follow the second link and read the deeper read.
The route index is the editorial map. The dedicated pages are the editorial layer. The app is the verification layer. Reading the three layers in sequence (index, dedicated entry, app) is the recommended pattern.
What the route index helps with
The index helps with three things: route discovery (which route covers this topic), route comparison (which routes overlap and which are the deeper reads), and route cadence (how often a route is refreshed). Route discovery is the most common use. Most visitors arrive here looking for a specific topic and need to know which route to open next.
What the route index does not help with
The index does not help with the live cricket state. The live state (current score, live leaderboard, payout total, contest status) lives inside the app. The index does not print a live value because the live value changes during the day. The index prints the route and the cadence; the app prints the live value.
How to read the index against the dedicated entries
Each route in the index points to one dedicated entry. The dedicated entry carries the editorial content; the index carries the route. Reading the index without reading the dedicated entry is reading a label without opening the envelope.
The dedicated entries cover the editorial core: KYC, state eligibility, withdrawal timing, contest formats, captain picks, scoring, leaderboards, responsible play, refer and bonus, account deletion, customer care, and the app path itself. Each one is updated on the cadence listed in the flat list above.
How to read the index against the BCCI / IPL feed
The index and the BCCI / IPL feed carry different information. The index carries the editorial routes; the feed carries the live cricket state, with score, wickets and overs. The two readers should not be confused. The index answers "which route covers this topic?" The feed answers "what is the live cricket state?"
Where the editorial entries and the live feed disagree on a captain call, the live feed is the most up-to-date read. The captain-picks ledger is reviewed against the live feed every match week; if a captain option changes (an injury, a late toss decision), the ledger is updated the same day.
How to read the index against the FAQ desk
The index and the FAQ desk carry different information. The index carries the editorial routes; the FAQ desk carries short answers to the questions we hear most often (sign-in trouble, payout timing, contest cancellation, captain change window). The two readers work together: the index tells you which route covers the topic, the FAQ desk tells you the short answer on the common decision.
Where the index and the FAQ desk disagree on a topic, the dedicated entry is the deeper read and the FAQ is the short answer.
How to read the index against the captain-picks ledger
The index and the captain-picks ledger carry different information. The index carries the editorial routes; the ledger carries the captain-pick criteria (role fit, recent form, matchup, boundary share) applied to the captain options for the next match. The two readers work together: the index points you to the ledger, and the ledger walks you through the four reads.
Where the index and the ledger disagree on a captain name, the ledger is the most up-to-date read. The ledger is reviewed every match week against the live feed.
How to use the route index as a starting point
Open the route index. Pick the column that fits. Follow the link. Read the dedicated entry. If your question is on a common decision, jump to the FAQ desk for the short answer. If your question is on tonight's captain, jump to the captain-picks ledger and run the four reads. When you are ready to act (joining a contest, setting a captain, changing a limit), sign in to the app and verify there.