<?xml version="1.0" encoding="UTF-8"?>
<!--
  BintaCura sitemap.

  ── WHY THE LIST IS SHORT ──────────────────────────────────────────────────

  The application is a Flutter single-page app using HASH routing, so every
  in-app screen lives behind a fragment:

      https://bintacura.org/#/public/doctors
      https://bintacura.org/#/info/privacy
      https://bintacura.org/#/academy/catalog

  A URL fragment is never sent to the server and is not a separately indexable
  URL. Listing fragments here would advertise coverage that does not exist,
  which is worse than omitting them. They are not listed, and must not be.

  The application shell at "/" is listed because it is genuinely reachable and
  genuinely canonical. Be aware of what it contains: Flutter renders into a
  WebGL canvas, so the rendered DOM holds no headings, no body text and no
  links — measured on the live site, the whole rendered DOM contains 30
  characters of text, all of it Flutter's hidden "typography measurement" node.
  "/" is therefore an entry point, not a content page.

  The four paths under it are the real content: plain HTML files served by
  nginx next to the SPA, each with its own copy, canonical, metadata and
  structured data. They are the reason this sitemap has more than one entry.

  ── WHAT IS DELIBERATELY ABSENT ────────────────────────────────────────────

  * No <lastmod>. These pages are hand-edited static files; a lastmod that is
    maintained by hand drifts, and a lastmod Google learns to distrust is worse
    than no lastmod at all. Git already records the true modification time.
  * No <changefreq> and no <priority>. Google ignores both. They would imply a
    level of control over crawling that this site does not have.
  * No /404.html, no /under_construction.html — neither is a destination.
  * Nothing that enumerates patients, staff, providers by name, insurance
    memberships, queue or waiting-room displays, or any other protected
    surface. A sitemap is a publication decision, and those are not public.

  Before this file existed, /sitemap.xml was answered by nginx's SPA fallback
  (try_files $uri $uri/ /index.html), returning HTTP 200 with Content-Type
  text/html. Search engines were told a valid sitemap existed and were handed
  the application shell instead.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://bintacura.org/</loc>
  </url>
  <url>
    <loc>https://bintacura.org/decouvrir/</loc>
  </url>
  <url>
    <loc>https://bintacura.org/patients/</loc>
  </url>
  <url>
    <loc>https://bintacura.org/professionnels/</loc>
  </url>
  <url>
    <loc>https://bintacura.org/confiance/</loc>
  </url>
</urlset>
