<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://learnwithcoffee.example.com/</loc>
    <changefreq>daily</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://learnwithcoffee.example.com/index.html#/courses</loc>
    <changefreq>daily</changefreq>
    <priority>0.9</priority>
  </url>
  <url>
    <loc>https://learnwithcoffee.example.com/index.html#/faq</loc>
    <changefreq>monthly</changefreq>
    <priority>0.5</priority>
  </url>
  <url>
    <loc>https://learnwithcoffee.example.com/index.html#/verify</loc>
    <changefreq>monthly</changefreq>
    <priority>0.4</priority>
  </url>
</urlset>
<!--
  NOTE: Individual course landing views (index.html#/course/:id) are rendered
  client-side from live Google Sheets data and cannot be enumerated at build
  time. To keep this file accurate as courses are published, regenerate it
  from code.gs's `getCourses` action (e.g. on a nightly Apps Script trigger
  that writes a fresh sitemap.xml to Drive, or via a small server that calls
  the deployed Web App's ?action=getCourses endpoint and emits one <url> per
  published, non-hash-fragment course route once server-side rendering is
  introduced). Hash-fragment URLs are not reliably indexed by search engines,
  so full SEO coverage of individual courses requires either prerendering or
  moving course detail pages to real paths (e.g. /course/course-slug).
-->
