<?xml version="1.0" encoding="UTF-8"?>
<!--
  Cold-start sitemap TEMPLATE.

  (No "- -" sequences anywhere below: XML forbids them inside a comment, which
  is why this block is punctuated the way it is.)

  The real sitemap is generated offline into ./ephemeral/sitemap (gitignored),
  so a fresh checkout, a rebuilt host or a restored droplet has nothing to serve
  until the first timer run completes. sitemap.php falls back to this file in
  that window.

  WHY EVERY <loc> SAYS sitemap.invalid, AND WHY THAT IS THE POINT
    This file used to be a finished document carrying twelve
    https://www.shaleexperts.com/ URLs, and nginx served it verbatim off disk.
    Measured on staging (www.shaleexpertz.com, whose generated tree had not been
    built yet): GET /sitemap.php answered 200 with X-SE-Sitemap: fallback and
    twelve <loc> values, every one of them naming PRODUCTION. Staging was
    advertising a property it does not own, and so would every other host that
    ever served this file: a review app, a restored droplet, a developer
    replica.

    A sitemap is a list of ABSOLUTE URLs, so the host cannot be left out. It has
    to be filled in by whoever is answering. sitemap.php does that at serve time
    (se_sitemap_render_fallback), substituting the origin it derives the same
    way scripts/sitemap/generate-sitemap.php derives its own: first
    SE_SITEMAP_CANONICAL_HOST, then WEB_PUBLIC_BASE_URL, then NGINX_HOST, and
    only then the Host of the request itself.

    `.invalid` is reserved by RFC 2606 and can never resolve, so if this file is
    ever served raw by something that does not do the substitution, the result
    is a document that advertises NOTHING rather than one that confidently
    advertises somebody else's site. Do not "fix" these back to a real hostname.

  Three rules for editing it:
    * It is a <urlset>, never a <sitemapindex>. An index would reference child
      files that, by definition, do not exist yet in the situation this file
      exists for.
    * Every <loc> must begin with the placeholder origin exactly as the <loc>
      values below spell it (https, then sitemap.invalid, no port, no trailing
      slash). That string, and only that string, is what sitemap.php replaces;
      it is SE_SITEMAP_FALLBACK_ORIGIN there. A <loc> spelt any other way is
      published unchanged, to whatever host it names. It is deliberately not
      written out again in this comment, because the substitution is a plain
      str_replace over the whole file and would rewrite this sentence too.
    * Only URLs verified to return 200 for an anonymous visitor, and only ones
      that will still be true in a year. Everything here is a section root;
      nothing here is data driven, because these paths have to hold on every
      host this file can be served from, not just production.

  There is deliberately no <lastmod>. A date committed to git is stale the
  moment it is written, and an inaccurate lastmod is worse than none: Google
  checks the claim against the page and stops trusting the signal site wide when
  it does not hold.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
	<loc>https://www.shaleexperts.com/</loc>
</url>
<url>
	<loc>https://www.shaleexperts.com/epnews</loc>
</url>
<url>
	<loc>https://www.shaleexperts.com/news</loc>
</url>
<url>
	<loc>https://www.shaleexperts.com/category</loc>
</url>
<url>
	<loc>https://www.shaleexperts.com/company</loc>
</url>
<url>
	<loc>https://www.shaleexperts.com/plays</loc>
</url>
<url>
	<loc>https://www.shaleexperts.com/videos</loc>
</url>
<url>
	<loc>https://www.shaleexperts.com/capital-markets</loc>
</url>
<url>
	<loc>https://www.shaleexperts.com/gathering-processing</loc>
</url>
<url>
	<loc>https://www.shaleexperts.com/capital-budgets</loc>
</url>
<url>
	<loc>https://www.shaleexperts.com/plays/eagle-ford-shale/county</loc>
</url>
<url>
	<loc>https://www.shaleexperts.com/plays/permian-basin/county</loc>
</url>
</urlset>
