XML Sitemap

What this page shows. A full audit of Nature’s Path’s XML sitemap architecture: the parent index at https://naturespath.com/sitemap.xml, its 24 child sitemaps across 6 locale markets (en-US, en-CA, fr-CA, en-GB, en-MX, es-MX), the 4 content types under each (products, collections, pages, blogs), and 8,773 total URLs.

Sitemap hygiene determines what Google can find and how quickly. A bloated sitemap dilutes crawl budget and trains Google that low-value URLs are publishable content; a clean sitemap focuses crawl attention on the pages that actually earn rankings. For a site the size of NP (8,773 URLs across 6 locales) the bloat cost compounds each crawl cycle until the hygiene work is done.

How to read the findings. Start with URL Inventory to see the locale distribution, then Validation Checks for the XML-level pass/fail list. The 28 Pages to Remove section is the bulk of the remediation work. The final two sections name Shopify platform limits that cannot be fixed in the theme — document them, escalate to Shopify support, and move on.

What the data says about NP today. All 24 child sitemaps parse cleanly and no file approaches the 50,000 URL limit. Major hygiene opportunities: 28 pages flagged for removal across 6 locales (170 total URL instances), no IndexNow enabled, no AI-crawler directives in robots.txt, and a Shopify bug that inserts every locale homepage into the products sitemap. Product <lastmod> values are all identical (Shopify-generated at fetch time), giving Google zero scheduling signal for products.

What this section shows. The breakdown of the 8,773 sitemap URLs by locale and content type, with a totals row at the bottom.

URL distribution is the first signal of locale bloat. When a locale carries the same blog count as the default market but only a handful of translated products, most of those blog URLs are English content under a locale prefix (thin or duplicate at the URL level). The distribution table below makes that pattern visible at a glance.

How to read the table. Compare Products across locales to spot thin markets (en-GB at 7, en-MX / es-MX at 24 each). Blogs and Pages are replicated across all 6 locales regardless of translation, which inflates the total and is the primary target for locale-level suppression.

What this section shows. An 8-point XML-level validation pass against each sitemap file: parse validity, per-file URL limit, deprecated priority / changefreq tags, <lastmod> accuracy for products and blogs, robots.txt declaration, and IndexNow status.

XML validity is a baseline, not a finish line. A sitemap that parses cleanly can still provide zero scheduling signal to Google if its timestamps are generated at fetch time rather than at record modification. The product <lastmod> failure below is the clearest example: valid XML, useless content.

How to read the table. PASS rows are clean; INFO rows flag non-harmful quirks Google ignores; FAIL and MISSING rows are real remediation targets. The MISSING row on IndexNow is a 5-minute Shopify Admin toggle and the highest-leverage single fix on this page.

What this section shows. The 28 URLs that should not be in the sitemap at all, grouped into three buckets (internal / B2B, compliance boilerplate, thin / ghost / expired) plus a Shopify bug that inserts every locale homepage into the products sitemap.

Sitemap bloat is a direct crawl-budget tax. Each of the 28 URLs listed here is replicated across 6 locales, so removing them strips 170 URL instances from Google’s crawl queue. That reclaimed crawl budget redirects to product and collection pages where ranking gains actually compound revenue.

How to read the tables. Each bucket names the URL pattern and the reason for removal. Effort is low: noindex meta tag per template plus sitemap suppression. The Shopify homepage-in-products bug is a platform-level issue; escalate to Shopify support and document, do not try to fix in theme code.

What this section shows. The 11 blog handles that make up the 1,242-URL US blog sitemap, with an article count per handle plus freshness and locale replication observations.

Blog sitemap composition exposes which content silos are active versus legacy. Recipes (561) and posts (545) do the heavy lifting; one-article handles (anitas-tips-and-techniques, anitas-guides) and the internal /blogs/wholesale handle (6 articles, should not be public) are the cleanup targets. Locale replication of English content across fr-ca / es-mx compounds the problem.

How to read the table. High-count handles are active content silos worth investing in. The highlighted /blogs/wholesale row is tagged for removal. The check-list below names freshness, locale replication, and the wholesale removal as the three remediation items.

What this section shows. Two crawler-control gaps: missing AI-crawler directives in robots.txt (GPTBot, ClaudeBot, PerplexityBot, CCBot, Diffbot, Amazonbot), and IndexNow not yet enabled in Shopify Admin.

Crawler-directive clarity is the line between passive and intentional indexing. AI training crawlers are now routinely addressed by name so content licensing stance is explicit; IndexNow pushes product and blog updates to Bing and Yandex within minutes instead of waiting for the next crawl cycle. Both are low-effort additions with durable reputational and freshness payoffs.

How to read the callouts. The warning callout names the AI crawler directives and the recommended block set. The info callout names the IndexNow enable step (5-minute Shopify Admin toggle) and clarifies the Google impact: IndexNow does not reach Google, so Google freshness depends on GSC crawl rate plus sitemap <lastmod> (limited by the product-timestamp issue).

What this section shows. Three Shopify platform behaviors that affect sitemap output and cannot be fixed in theme code: query-string requirements on child sitemap URLs, auto-inserted <changefreq> tags, and dynamic product <lastmod> timestamps.

Platform-level limits need documented expectations. Spending engineering time fighting Shopify defaults is expensive; the right move is to capture each limit, state the workaround, and file a Shopify support ticket if any of the three ever becomes blocking. Future audit cycles then reference this section instead of re-discovering the same issues.

How to read the callouts. The first callout documents the query-string fetch requirement for anyone re-running the sitemap pull. The second names the three items that cannot be fixed without a custom sitemap solution, and is the reference document to cite in conversations with the NP IT team.