<?xml version="1.0" encoding="UTF-8"?>
<!--
  Public, linked, indexable pages only.

  THE DASHES BELOW ARE LITERAL EM DASH CHARACTERS ON PURPOSE. XML forbids a
  double hyphen anywhere inside a comment (XML 1.0, section 2.5), and this
  file used the repo's usual ASCII double hyphen as an em dash, so it did not
  parse at all: every conforming parser rejected it at the first occurrence,
  which means Search Console would have reported the whole sitemap as
  unreadable rather than indexing any of the URLs in it. Do not "tidy" these
  back into ASCII.

  Previously this listed /apply, /onboard and /login and nothing else: three
  pages a visitor cannot reach (the Apply entry point was removed from the
  footer 2026-08-18, and /onboard and /login are account plumbing) while
  omitting every page the site actually links to. That is backwards on both
  sides — it pointed crawlers at dead ends and hid the real content.

  Deliberately NOT listed:
    /apply, /login, /onboard, /reset-password, /auth/callback,
    /account/delete, /unsubscribe — account plumbing, no content to index
    /view/:token, /founder-update/:token — tokenised private documents
    everything behind auth (/dashboard, /vault, /ops, ...)
  robots.txt disallows these too; the two files must agree.

  /writing is deliberately absent (2026-08-20). The route exists and renders,
  but every row in news_articles is kind="press", so the page has nothing on
  it, and advertising an empty page marks the site as thin content while
  spending crawl budget that should go to the pages that do have something.
  Add it back the moment the first post is published: the route, the footer
  link and robots.txt all already allow it, so this entry is the only thing
  to restore.

  Detail pages (/companies/:id, /team/:slug, /sectors/:slug) are dynamic and
  driven by Supabase, so they are not enumerated here by hand — that list
  would go stale the moment a GP publishes or unpublishes anything. The index
  pages below link to all of them, which is how a crawler reaches them.
  Generating those entries at build time from the published rows is the
  proper fix and is worth doing separately.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://samarthya.vc/</loc>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://samarthya.vc/press</loc>
    <changefreq>weekly</changefreq>
    <priority>0.8</priority>
  </url>
  <url>
    <loc>https://samarthya.vc/privacy</loc>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
</urlset>
