Key facts
- The store's sitemap index pointed to product, pages and collections sitemaps, and each of those returned an empty list rather than the catalog.
- The home page was the only URL a crawler could reach through the sitemap for a store with 53 products and several collections.
- An empty sitemap does not remove pages from the index, because crawlers also follow links, but it removes the store's own signal about what exists and what changed, and it hides new products until they are linked from somewhere.
- The same store had a home page weighing nearly eleven megabytes and two domains, so a slow, split site also had no map, and each problem masked the others.
- The fix was to restore the platform's generated sitemaps, submit the index in Search Console, and check the count against the catalog rather than trusting the file exists.
The finding
The store's sitemap index was present and well formed. It listed the product sitemap, the pages sitemap and the collections sitemap the platform generates. Requesting each of them returned a valid file with no URLs in it. Only the home page appeared anywhere. For a store with 53 products, that meant the one file whose whole purpose is to tell search engines what the catalog contains told them nothing.
What we looked at
We requested the sitemap index and each child sitemap and counted the URLs in each. We compared the count with the number of products and collections visible in the store's navigation. We checked whether products were marked as unavailable to search engines or hidden from the online store channel, which would remove them from the sitemap by design. We checked the robots file for a sitemap directive and looked at how the store's product pages were linked, since links were the only remaining path for a crawler.
Why it mattered for leads
A sitemap is the store's own statement of what exists and when it changed. Without it, a search engine relies on links alone, which means new products wait until something links to them, deep collections get crawled rarely, and the store cannot see in Search Console how many of its pages are indexed against how many it submitted, because it submitted one. For a manufacturer whose product lines are its sales pages, the catalog was the content, and the content had no map.
False positive checks we ran
We checked whether the products were deliberately hidden from search by a channel or visibility setting, in which case an empty sitemap would be correct; the products were live and visible in the storefront. We checked whether a different sitemap file, added by an app, carried the catalog instead; none was referenced in the index or the robots file. We requested the child sitemaps more than once to rule out a temporary generation error; they were empty each time. We confirmed the product pages themselves returned normally when requested directly.
The fix
The proposal's SEO work started with the sitemap: identify why the platform's generated files were empty, usually a channel, app or theme setting, restore them, confirm the counts match the catalog, submit the index in Search Console, and then read the indexed count against the submitted count every month. The same pass added one marketing page per product line on the proposed site, so the catalog was reachable both by map and by pages written for the searches a brand founder types.
How to check your own site for this
Open your sitemap address, usually the site name followed by sitemap.xml. If it is an index, open each child file it lists. Count the URLs in each and compare them with the number of products, collections and pages you actually have. A file that exists and is empty is easy to miss because it looks healthy at a glance. Then open Search Console's sitemap report and compare submitted with indexed; if submitted is one, you have this finding.
Related questions
Not by itself, because crawlers also follow links. It removes your own signal about what exists and what changed, slows discovery of new products, and leaves you unable to see submitted against indexed counts.
Usually a setting: products hidden from the online store channel, a visibility flag, an app that overrode the sitemap, or a theme change. The fix starts with finding which one, and the check is comparing counts with the catalog.
After any platform, app or theme change, and monthly through the Search Console sitemap report, where the submitted and indexed counts should track your catalog size.
The proposal added one page per product line written for the searches a brand founder types, which the store's product pages did not do. The store's catalog and the marketing pages then linked to each other.
an anonymized finding from a real proposal audit; the business is described by type only; SearchPod sells the services that fix findings like this.
Want your site audited the same way?
Get a free, no-obligation proposal within one business day. We look at your site and your market and tell you plainly what we would do, and what we would not.
Get your free proposal