<?xml version="1.0" encoding="UTF-8"?>
<!--
  Sitemap index for laynergroup.com — the single entry point declared in /robots.txt.

  Children:
    sitemap-pages.xml             static, versioned by hand: the 8 indexable static pages
    blog/sitemap-{lang}.xml       generated: posts, categories, tags and the blog index
    blog/sitemap-landings-{lang}.xml  generated: the programmatic /lp/ sales pages

  Why one document per language instead of one per section:
  Search Console reports coverage per sitemap. A single blog sitemap holding
  ru + en + es + fr answers "N discovered / M indexed" for four languages at
  once, so a language that never gets indexed is invisible inside the total.
  Split this way, each language is its own coverage report and a failing one
  is obvious on the first screen.

  Editorial content and landings stay in separate files as well: the /lp/ pages
  are programmatic country×country sales pages and would otherwise spend the
  crawl budget the posts need.

  The hreflang cluster inside every <url> still lists all four languages — that
  reciprocity is what lets Google pair the translations, and narrowing it to
  the sitemap's own language would break it.

  A <sitemapindex> only accepts <sitemap> children: never add <url> or
  xhtml:link here. Never commit a physical blog/sitemap*.xml: it would shadow
  the dynamic route and freeze at the file's mtime.

  No <lastmod> on the blog children on purpose. They are generated per request,
  so any value written here would be a guess, and Google discards lastmod site
  wide once it catches it being unreliable — worse than omitting it.

  /blog/sitemap.xml and /blog/sitemap-landings.xml (the combined, all-language
  documents) still answer 200 for anything that already points at them, but are
  deliberately NOT listed here: declaring both forms would file every URL twice.
  Remove those two from Search Console after submitting the ones below.
-->
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">

  <sitemap>
    <loc>https://laynergroup.com/sitemap-pages.xml</loc>
    <lastmod>2026-08-11</lastmod>
  </sitemap>

  <sitemap>
    <loc>https://laynergroup.com/blog/sitemap-ru.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://laynergroup.com/blog/sitemap-en.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://laynergroup.com/blog/sitemap-es.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://laynergroup.com/blog/sitemap-fr.xml</loc>
  </sitemap>

  <sitemap>
    <loc>https://laynergroup.com/blog/sitemap-landings-ru.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://laynergroup.com/blog/sitemap-landings-en.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://laynergroup.com/blog/sitemap-landings-es.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://laynergroup.com/blog/sitemap-landings-fr.xml</loc>
  </sitemap>

</sitemapindex>
