<?xml version="1.0" encoding="UTF-8"?>
<!--
  Sitemap for the public marketing site.

  THE DOMAIN IS REAL NOW — 22 August 2026. This file carried `example.com` from
  the day it was written, with a comment saying to replace it before launch. The
  site launched on 22 August and the replacement was missed, so for the first
  hours on the live domain the sitemap pointed at an IANA-reserved placeholder.
  `www.` is not decoration: the apex 308-redirects to it, so `www` is the
  canonical host, measured rather than assumed.

  WHAT IS LISTED, AND WHY IT IS NOT EVERY BLOG POST. The public routes are `/`,
  `/blog`, `/blog/archive` and `/blog/:slug`. The first three are STABLE — they
  exist whatever is in the database — and each post is reachable by a link from
  the two index pages, which is how a crawler is meant to find them.

  A HAND-WRITTEN LIST OF POSTS WOULD GO STALE THE FIRST TIME ONE IS PUBLISHED,
  and posts are written in the portal without a deploy. So they are deliberately
  absent rather than enumerated-and-forgotten. **Production holds 0 published
  posts today**, so nothing is missing from this file that exists.

  WHEN THAT STOPS BEING GOOD ENOUGH: the site is CLIENT-RENDERED, so discovering
  a post by crawling `/blog` needs Google to execute JavaScript. It does, but
  less reliably than following a link in served HTML. Once there are posts worth
  ranking, this file should be GENERATED from `blog_posts` rather than hand
  written — see the queue.

  The in-page sections (#courses, #results, #contact) are fragments of one
  document, not separate URLs. A sitemap of fragments is duplicate content.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://www.accountsbynisha.com/</loc>
    <changefreq>monthly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://www.accountsbynisha.com/blog</loc>
    <changefreq>weekly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>https://www.accountsbynisha.com/blog/archive</loc>
    <changefreq>weekly</changefreq>
    <priority>0.4</priority>
  </url>
</urlset>
