<?xml version="1.0" encoding="UTF-8"?>
<!--
  Served at https://www.drroitman.co.il/sitemap.xml and pointed at from
  robots.txt.

  WHY ONLY ONE URL
  ----------------
  "/" is the patient portal, and it is the only page here that should be
  promoted in search.

  /index.html is deliberately NOT listed. It is the pre-port patient page. It
  still answers 200 -- Program.cs names it in DefaultFileNames and it can be
  requested directly -- but as of 2026-09-06 nothing links to it any more, and
  its booking flow runs through js/clinic.js, which calls
  /clinic/api/Login/Login/{id}/{birthYear}. The national ID travels in the URL
  path there and is written into the App Service access log, where it sits for
  the full 30-day retention. Listing that page in the sitemap would actively
  push patients arriving from search into the flow that leaks their ID instead
  of the portal's.

  WHY "/" AND NOT "/patient-portal.html"
  --------------------------------------
  Program.cs sets DefaultFileNames to ["patient-portal.html", "index.html"], so
  a request for "/" is answered by patient-portal.html. Listing both would
  offer one page under two URLs and split its ranking between them.

  /patient-portal.html still answers 200 directly, and crawlers have already
  found it that way. Resolving that properly needs a <link rel="canonical"> in
  the page itself -- a change to a live patient page, deliberately not bundled
  in here.

  NO changefreq OR priority
  -------------------------
  Google ignores both outright, and priority is defined as relative to the
  other URLs in the same sitemap, which is meaningless when there is one.

  lastmod is the date the page's content last changed in git, not the date this
  file was written.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">

  <!-- The patient portal: appointments, requests, opening hours. -->
  <url>
    <loc>https://www.drroitman.co.il/</loc>
    <lastmod>2026-09-01</lastmod>
  </url>

</urlset>
