<?xml version="1.0" encoding="UTF-8"?>
<!--
  2026-06-25 — Manual sitemap. Lists only PUBLIC, anonymously-accessible
  routes. Routes that are gated behind GatedPage / requireAuth in
  pages/_app.js's PUBLIC_PATHS check are excluded because a crawler
  would land on the welcome / sign-in surface, not on the page content
  itself, and would waste crawl budget on a duplicate copy of `/`.

  Per-wallet `/people?wallet=<addr>` pages are PUBLIC (the page-level
  guard at pages/people.tsx L82-107 admits anonymous viewers and the
  backend route is @public_endpoint), so they're indexable in
  principle. They are intentionally NOT enumerated here for two
  reasons:

    1. The leaderboard wallet set is large (thousands of addresses)
       and the list is dynamic. Enumerating them statically would
       drift out of date and force a build-time data fetch for every
       sitemap rebuild.

    2. Google's recommended pattern for large dynamic surfaces is to
       link them from a high-priority indexed page and let the
       crawler discover the long tail naturally. `/compare` IS that
       hub page; it serves the full leaderboard table as semantic
       HTML with `<a href="/people?wallet=...">` rows for each entry,
       so Googlebot will walk from /compare to every wallet profile
       without needing them listed here.

  If wallet pages later need explicit sitemap presence — say AI
  crawlers need a structured list of "what wallets exist" rather than
  recursive crawl — convert this file to a sitemap-index.xml that
  references both this static set AND a dynamic
  /api/sitemap-people.xml route. The dynamic route would pull the top
  N wallets by activity from the leaderboard endpoint and emit them
  at request time. Leaving as a single static sitemap until that
  bottleneck materialises.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://boosted.trading/</loc>
<changefreq>weekly</changefreq>
<priority>1.0</priority>
</url>
<url>
<!-- Trader leaderboard. Public; anonymous viewers see the same table
     a signed-in user would. Linked from the homepage's Explore
     section, which is the topical anchor a crawler needs to rank
     this URL for "Polymarket leaderboard / top traders" queries. -->
<loc>https://boosted.trading/compare</loc>
<changefreq>daily</changefreq>
<priority>0.9</priority>
</url>
<url>
<!-- Help center. Public documentation. -->
<loc>https://boosted.trading/help</loc>
<changefreq>weekly</changefreq>
<priority>0.6</priority>
</url>
<url>
<!-- Polymarket-wedge variant of the welcome page. Same launch flow
     as / but the marketing copy targets prediction-market traders
     specifically. Indexed separately so a Google search for
     "Polymarket trading platform" can land directly here. -->
<loc>https://boosted.trading/landing/polymarket</loc>
<changefreq>monthly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://boosted.trading/terms</loc>
<changefreq>monthly</changefreq>
<priority>0.3</priority>
</url>
<url>
<loc>https://boosted.trading/privacy</loc>
<changefreq>monthly</changefreq>
<priority>0.3</priority>
</url>
<url>
<loc>https://boosted.trading/legal/cookies</loc>
<changefreq>monthly</changefreq>
<priority>0.3</priority>
</url>
<url>
<loc>https://boosted.trading/legal/seller-terms</loc>
<changefreq>monthly</changefreq>
<priority>0.3</priority>
</url>
</urlset>
