<?xml version="1.0" encoding="UTF-8"?>
<!--
  The search page is the only URL this file can honestly state.

  The pages worth ranking are the property details, and their set is
  the portfolio: it changes whenever a listing is added or retired, so
  it cannot be committed here without going stale the first time it
  does. Enumerating them at build time was the other option and is
  worse — it would put a live API call on the critical path of every
  build and every PR preview, and a build that fails offline is a
  build that fails for a reason unrelated to what it was building.

  Property URLs join this file when they can be generated from the
  portfolio at request time (a Worker route backed by the public
  properties endpoint), which is the same edge seam per-page social
  cards need. Until then a crawler reaches them by following the links
  on the search page.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://rial.estate/</loc>
  </url>
</urlset>
