<?xml version="1.0" encoding="UTF-8"?>

<!--
  Hand maintained, and it drifted: until now this file listed exactly two URLs,
  the home page and /gallery. /gallery has never been a route in this app, so
  the only non home entry here was a 404 being advertised to Google, while
  /events, /about and /contact existed and were not listed at all.

  Every <loc> below is a real route in src/App.tsx. If you add a Route there,
  add it here. The full set as of the Sept 2026 page split, plus /specials
  which landed with the home page rebuild:
  / , /menu , /visit , /events , /specials , /about , /contact

  Two things deliberately absent:

  - /#room and the other home page anchors. A fragment is not a separate URL to
    a crawler; listing them would be listing the home page five times.
  - The ?lang variants. Language is client state held by i18n.tsx, not a route,
    so there is one URL per page in three languages. That is a real SEO
    limitation and not one a sitemap can fix. The fix is prerendering, which is
    the same fix the per page <title> and canonical tags are waiting on.

  DOMAIN: these say tinytapasnyc.com, which is what index.html's
  canonical and og:url and robots.txt also say. Those four have to move
  together, always: a sitemap on one host listing URLs on another is ignored
  outright, so a half-finished rename is worse than no rename.

  ⚠️ The restaurant's EMAIL is on a different domain — tinytapasandbites.com,
  not tinytapasnyc.com — and that is correct, not a leftover. It is a live
  mailbox. The only place it appears is the JSON-LD block in index.html and
  site.ts. Do not sweep it up in a find and replace on this name.
-->

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://tinytapasnyc.com/</loc>
    <changefreq>monthly</changefreq>
    <priority>1.0</priority>
  </url>

  <!-- Its own page as of the split, and the highest priority after home:
       "tapas inwood menu" is the search this business actually gets. -->
  <url>
    <loc>https://tinytapasnyc.com/menu</loc>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>

  <url>
    <loc>https://tinytapasnyc.com/visit</loc>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>

  <!-- weekly, unlike most of the rest: this is the dated calendar, so it is one
       of the two that goes stale on a real schedule. -->
  <url>
    <loc>https://tinytapasnyc.com/events</loc>
    <changefreq>weekly</changefreq>
    <priority>0.7</priority>
  </url>

  <!-- Ranked ABOVE /events, which is the opposite of what the nav order
       suggests, and deliberately. This is the page carrying happy hour, Taco
       Tuesday, Jueves Carnívoro and Sunday brunch — the searches this business
       actually gets after "menu" — while /events has no dated content in it at
       all yet. Flip them back if the calendar ever fills up. -->
  <url>
    <loc>https://tinytapasnyc.com/specials</loc>
    <changefreq>weekly</changefreq>
    <priority>0.8</priority>
  </url>

  <url>
    <loc>https://tinytapasnyc.com/about</loc>
    <changefreq>monthly</changefreq>
    <priority>0.6</priority>
  </url>

  <url>
    <loc>https://tinytapasnyc.com/contact</loc>
    <changefreq>monthly</changefreq>
    <priority>0.6</priority>
  </url>
</urlset>
