<?xml version="1.0" encoding="UTF-8"?>
<!--
  The two hand-written public pages, and only those. Everything under /p/ is
  listed by the generator's own sitemap instead, so neither file can go stale
  describing the other's contents.

  No changefreq and no priority: Google states outright that it ignores both.
  lastmod is the one element it does read, and only "if it's consistently and
  verifiably accurate" — so it is the date these two files were last actually
  edited, never a build clock. Stamping it on every deploy would teach Google
  the field is noise, which is the same mistake as keying a cache on "a job
  ran" rather than "the content changed".
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://fplmodel.com/</loc>
    <lastmod>2026-08-24</lastmod>
  </url>
  <url>
    <loc>https://fplmodel.com/how-it-works.html</loc>
    <lastmod>2026-08-24</lastmod>
  </url>
</urlset>
