<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:image="http://www.google.com/schemas/sitemap-image/1.1">

  <!-- The two <image:image> entries below are the ONLY reason this file carries
       the image namespace, and they are not decoration (2026-08-26).

       Anna's own photo HAS been the Google search-result thumbnail twice. It
       stopped being it because s124 renamed the og:image to bust Google's cache
       (LAWS L57) — the rename was correct and necessary, but a brand-new URL is
       an image Google has never fetched. Google re-crawled the PAGE on
       2026-08-25 10:58 and saw the new address; the IMAGE crawl is a separate,
       slower queue, and until it runs Google has no fetched og:image to draw,
       so the thumbnail slot fell to the only already-indexed photo on the
       page — the hero video's poster, which is a client.

       An image sitemap is the documented way to put a specific image URL in
       that crawl queue instead of waiting on discovery. Both entries are Anna
       from the same studio shoot, so whichever one Google picks, it is her.

       ⛔ When the og:image is re-cut, this <image:loc> must move to the new
       dated filename in the SAME edit as the meta tag (L57 again) — a stale
       entry here re-teaches Google the wrong picture.
       Revert marker: serpsitemap. -->
  <url>
    <loc>https://annalysak.com/</loc>
    <lastmod>2026-09-02</lastmod>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
    <image:image>
      <image:loc>https://annalysak.com/assets/images/social/og-image-2026-08-25.jpg</image:loc>
    </image:image>
    <image:image>
      <image:loc>https://annalysak.com/assets/images/homepage/proof-section/anna-portrait-crossed.webp</image:loc>
    </image:image>
  </url>

  <url>
    <loc>https://annalysak.com/pages/bridal-makeup-madrid.html</loc>
    <lastmod>2026-09-02</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>

  <url>
    <loc>https://annalysak.com/pages/event-makeup-madrid.html</loc>
    <lastmod>2026-09-02</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>

  <url>
    <loc>https://annalysak.com/pages/destination-wedding-makeup-spain.html</loc>
    <lastmod>2026-09-02</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>

  <url>
    <loc>https://annalysak.com/pages/self-makeup-classes-madrid.html</loc>
    <lastmod>2026-09-02</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.7</priority>
  </url>
  <url>
    <loc>https://annalysak.com/pages/professional-makeup-course-madrid.html</loc>
    <lastmod>2026-09-02</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.7</priority>
  </url>
  <url>
    <loc>https://annalysak.com/pages/level-up-training-madrid.html</loc>
    <lastmod>2026-09-02</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.7</priority>
    <!-- s147: the page's og:image was re-cut to a NEW dated filename (L57);
         a brand-new URL is an image Google has never fetched, so it goes in
         the image crawl queue here, same rationale as the homepage entries
         above (L60). Move this loc in the SAME edit as any future og re-cut. -->
    <image:image>
      <image:loc>https://annalysak.com/assets/images/social/og-level-up-training-2026-08-26.jpg</image:loc>
    </image:image>
  </url>



  <url>
    <loc>https://annalysak.com/pages/about.html</loc>
    <lastmod>2026-09-02</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.7</priority>
  </url>

</urlset>
