<?xml version="1.0" encoding="UTF-8"?>
<!-- Three real pages. The in-app views (#rental, #aic, #resources, and every
     route inside /rent/) are URL fragments, which Google does not index
     as separate pages, so listing them here would be noise. Splitting those
     into real paths is the next step if long-tail search traffic matters.

     /rent/ carries the content — every building, its City inspection
     record and what is within a walk — and is where the portal's PBR button
     now goes, so it is the page with something to rank for anything other
     than the brand name. -->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://torontopolis.ca/</loc>
    <lastmod>2026-10-15</lastmod>
    <changefreq>daily</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://torontopolis.ca/rent/</loc>
    <lastmod>2026-10-15</lastmod>
    <changefreq>daily</changefreq>
    <priority>0.9</priority>
  </url>
  <!-- Every building's own page, and the /rentals/ directory, are in
       sitemap-rentals.xml (generated, 3,600+ URLs), listed in robots.txt. -->
  <url>
    <loc>https://torontopolis.ca/plan/</loc>
    <lastmod>2026-10-18</lastmod>
    <changefreq>daily</changefreq>
    <priority>0.8</priority>
  </url>
  <!-- The human sitemap, linked from every footer. It is also the page that
       links /rentals/, /plan/ and the in-app views a crawler would otherwise
       never reach, since those are URL fragments. -->
  <url>
    <loc>https://torontopolis.ca/sitemap</loc>
    <lastmod>2026-10-18</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.3</priority>
  </url>
  <url>
    <loc>https://torontopolis.ca/privacy</loc>
    <lastmod>2026-10-15</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.2</priority>
  </url>
</urlset>
