<?xml version="1.0" encoding="UTF-8"?>
<!--
  Every route a crawler can reach WITHOUT an account, and nothing else.

  `/new-business` used to be here and was REMOVED on 2026-08-13. It is linked from
  the shell nav and it is a real route, but `App.tsx` wraps it in `<RequireAuth>` — so
  a crawler that followed this entry met a sign-in wall on a URL we had asked it to
  index. Bing's guidelines are explicit that a sitemap should carry only index-worthy
  URLs; advertising a page that answers with a login is how a whole document loses
  credibility, not just the one entry. The link stays in the nav (a person following
  it is signed in or about to be); the advertisement goes.

  Business showcase pages (/businesses/:uid) are deliberately ABSENT. A static file
  cannot enumerate them, and emitting a handful would be worse than emitting none: a
  sitemap is read as the complete set, so a partial one tells Google the rest do not
  exist. Listing them needs a backend route that generates this document from the
  same subscription-gated query the directory uses — worth doing, not done here, and
  every business on the live box today is still a test row.

  `<lastmod>` IS A CLAIM AND IT IS CHECKABLE, which is why each date is the day that
  route's OWN source last changed (measured with `git log -1` over the page component
  and anything whose content it renders), and not the day of the last deploy. A single
  date bumped on every deploy would say all fourteen pages changed whenever any one of
  them did — and both engines discount a lastmod they find unreliable, so a dishonest
  one is worse than none at all. When you change a page's copy, move ITS date. The
  failure direction is safe: a date left behind means a slower recrawl, never a wrong
  page served. `npm run check:seo` fails if any URL lacks one or carries a future date.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://teumon.co.il/</loc>
    <lastmod>2026-08-25</lastmod>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://teumon.co.il/businesses</loc>
    <lastmod>2026-08-12</lastmod>
    <changefreq>daily</changefreq>
    <priority>0.9</priority>
  </url>
  <!-- The price and what it includes. This copy existed from the start and was
       reachable only with an owner session (SubscriptionSection mounts behind
       `pub.isOwner`), so the highest-intent question in this market had no page to
       land on. -->
  <url>
    <loc>https://teumon.co.il/pricing</loc>
    <lastmod>2026-08-25</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>
  <!-- One page per trade. The slugs are `BusinessTypeKey`s — see
       frontend/src/lib/verticals.ts, which is what `VerticalPage` is keyed on — so
       a URL here can never name a category the product does not have. Adding one
       means editing VERTICAL_SLUGS, the VERTICALS record and this file together;
       `npm run check:seo` fails the build on a route the shell links to and this
       document does not advertise. All six share one date because they share one
       component and one copy table. -->
  <url>
    <loc>https://teumon.co.il/for/barber</loc>
    <lastmod>2026-08-12</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
  <url>
    <loc>https://teumon.co.il/for/hairSalon</loc>
    <lastmod>2026-08-12</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
  <url>
    <loc>https://teumon.co.il/for/nailSalon</loc>
    <lastmod>2026-08-12</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
  <url>
    <loc>https://teumon.co.il/for/beautyCenter</loc>
    <lastmod>2026-08-12</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
  <url>
    <loc>https://teumon.co.il/for/medical</loc>
    <lastmod>2026-08-12</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
  <url>
    <loc>https://teumon.co.il/for/fitness</loc>
    <lastmod>2026-08-12</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
  <!-- The deep-link page, at the address that goes on a poster. It was indexable and
       carrying its own canonical from the day it was written, and simply never advertised
       here — so the one URL most likely to be typed from print was the one URL this
       document did not name. With the app installed the OS claims /app and never loads
       the HTML at all; this entry is for the crawler and the desktop visitor. -->
  <url>
    <loc>https://teumon.co.il/app</loc>
    <lastmod>2026-08-25</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.7</priority>
  </url>
  <url>
    <loc>https://teumon.co.il/terms</loc>
    <lastmod>2026-08-25</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
  <!-- /privacy was missing while /terms was here, and the two landed together: both
       are public routes, both are linked from the registration consent boxes, and
       both are read by people who have no session. An omission here is not neutral —
       a sitemap is read as the complete set. -->
  <url>
    <loc>https://teumon.co.il/privacy</loc>
    <lastmod>2026-08-25</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
  <!-- /compliance and /accessibility landed together on 2026-08-25 with the board's
       compliance policy. The accessibility statement is the one of the two that is
       legally REQUIRED to exist and to be findable — regulation 35 of תקנות שוויון
       זכויות לאנשים עם מוגבלות (התאמות נגישות לשירות), תשע"ג-2013 — and the site had
       none at all until that date. -->
  <url>
    <loc>https://teumon.co.il/compliance</loc>
    <lastmod>2026-08-25</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
  <url>
    <loc>https://teumon.co.il/accessibility</loc>
    <lastmod>2026-08-25</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
  <!-- Google Play's Data safety form takes an account-deletion URL and it must be
       reachable with no session, because the reviewer filling that form in has no
       account. Listed here for the same reason /privacy is: a sitemap is read as the
       complete set of public pages, and this is one. -->
  <url>
    <loc>https://teumon.co.il/account-deletion</loc>
    <lastmod>2026-08-12</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
  <!-- Apple requires a support URL on every App Store listing, and it must be a page
       that works with no login — the reviewer opening it has no account here. Listed
       for the same reason as the two above: a sitemap is read as the complete set of
       public pages, and this is one of them. -->
  <url>
    <loc>https://teumon.co.il/support</loc>
    <lastmod>2026-08-13</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.4</priority>
  </url>
</urlset>
