<?xml version="1.0" encoding="UTF-8"?>
<!--
  Kept in sync with the page set by scripts/check-sitemap.mjs, which runs in `npm run check`
  and therefore on CI and both deploy paths. It also asserts that every URL here matches the
  rel=canonical the corresponding page declares, so the two cannot disagree.

  No <priority>: every major search engine ignores it, and carrying it implied a control over
  crawl ordering that does not exist.

  No <lastmod>: it is only useful if it is consistently accurate, and there is no deploy-time
  build step here to stamp it. A hand-maintained date that drifts is worse than no date at all,
  because a crawler that learns to distrust it discounts the whole file.

  404.html is deliberately absent. It is an error page, not a destination.

  /pricing is listed since the pricing cutover (2026-10-17, D-071); it was absent while it
  shipped dark. /payment-history is absent permanently: an account page, noindex.

  THE BLOG IS WITHDRAWN (owner, 2026-09-22): "it should not be seen from the web while we do
  some work on it before a subsequent release." Its nine entries were removed from this file in
  that change, and /blog now answers 404 rather than redirecting - a 301 on a URL that is coming
  back would sit in browser and crawler caches and have to be fought at re-launch.

  WHEN IT RETURNS, the nine lines come back here and so does the paragraph below, which is left
  as a record of how this file and the blog's own sitemap divided the work:

    Blog pages are rendered from the database into their own document root, so the page set
    changes when someone publishes rather than when someone commits, and a hand-maintained list
    here could not keep up: a fourth post would have failed the build until somebody remembered
    to edit this file. The blog publishes its own /blog/sitemap.xml on every render, listing
    exactly the posts and categories that exist at that moment. Both files are named in
    robots.txt, which is the supported way to serve more than one. The state previews (search,
    search-no-results, empty, 404) stay out of it for the same reason 404.html is out of this
    one: a search result page is generated by a query rather than authored, and indexing one is
    how thin near duplicate pages get into an index.

  /help is listed here, and its articles are not, for the same reason (2026-09-15). Articles are
  rendered from the app's help feed by help-renderer/, so they change when someone publishes in
  HelpScout. The renderer writes /help/sitemap.xml with /help and every article, and robots.txt
  names it. /help itself is here because public/help/index.html, the committed placeholder, is a
  page check-sitemap.mjs sees.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url><loc>https://lotjitsu.com/</loc></url>
  <url><loc>https://lotjitsu.com/features</loc></url>
  <url><loc>https://lotjitsu.com/platforms</loc></url>
  <url><loc>https://lotjitsu.com/compatibility</loc></url>
  <url><loc>https://lotjitsu.com/platforms/hibid</loc></url>
  <url><loc>https://lotjitsu.com/platforms/liveauctioneers</loc></url>
  <url><loc>https://lotjitsu.com/platforms/proxibid</loc></url>
  <url><loc>https://lotjitsu.com/platforms/auctionninja</loc></url>
  <url><loc>https://lotjitsu.com/platforms/bidwrangler</loc></url>
  <url><loc>https://lotjitsu.com/platforms/wavebid</loc></url>
  <url><loc>https://lotjitsu.com/pricing</loc></url>
  <url><loc>https://lotjitsu.com/contact</loc></url>
  <url><loc>https://lotjitsu.com/terms</loc></url>
  <url><loc>https://lotjitsu.com/privacy</loc></url>
  <url><loc>https://lotjitsu.com/delete-account</loc></url>
  <url><loc>https://lotjitsu.com/support</loc></url>
</urlset>
