<?xml version="1.0" encoding="UTF-8"?>
<!--
  Added when the site grew past one page, which is the condition robots.txt
  named. Five URLs, all with the trailing slash that each page's
  <link rel="canonical"> uses — a sitemap that disagrees with the canonical
  tag is worse than no sitemap.

  No <lastmod>: it would be a hand-maintained date that goes stale the first
  time someone forgets it, and a wrong lastmod is a signal worth less than an
  absent one. No <priority> or <changefreq> either; Google ignores both.

  WHY www AND NOT THE APEX. These were written as https://theflir.com/ and moved
  to https://www.theflir.com/ because the apex did not serve. On 2026-08-08 the
  Amplify domain association still had the apex subdomain at verified: false, so
  CloudFront refused theflir.com as one of its own names even though Route 53
  held a correct ALIAS A record to the distribution.

  THAT IS NO LONGER TRUE. Re-checked 2026-08-09: https://theflir.com/ returns
  200 and serves byte-identical content to www, down to the same ETag on
  site.css. The apex was verified in Amplify some time after the note above was
  written.

  So www is a choice now rather than a constraint, and it stays a choice. A
  canonical host should not move without a reason, every canonical tag and
  og:url on the site already says www, and the original warning still holds:
  switch only if someone actually wants the bare domain indexed.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url><loc>https://www.theflir.com/</loc></url>
  <url><loc>https://www.theflir.com/music/</loc></url>
  <url><loc>https://www.theflir.com/band/</loc></url>
  <url><loc>https://www.theflir.com/live/</loc></url>
  <url><loc>https://www.theflir.com/contact/</loc></url>
  <url><loc>https://www.theflir.com/shop/</loc></url>
</urlset>
