· 11 min read
How Many Products Does a Shopify Store Have? Free Check
Shopify publishes a product sitemap anyone can read. Here is how to count a store's catalog, check how fresh it is, and what the number actually tells you.
Before you study a competitor’s marketing, it helps to know one blunt number: how big their catalog actually is. A store with 40 products and a store with 4,000 are playing different games — different ad volume, different margins, different tolerance for a slow month. The number is also easy to get wrong by eye. A homepage showing twelve hero products can hide a four-thousand-SKU catalog one click deep, and a store that looks like a dropshipping warehouse on the surface sometimes curates harder than a boutique.
Shopify makes this number public whether the owner intends it or not. Every Shopify store ships an XML sitemap, and the product section of that sitemap lists every published product URL. You do not need an account, an app, or a paid tool to read it. This guide shows the exact steps, the two ways the count goes wrong, and how to read what a catalog size actually means once you have it.
Why Catalog Size Is Worth Counting
A product count is not a vanity stat. It is the fastest available read on a store’s operating model:
- A small, stable catalog (roughly under 100 products) usually means curation: fewer bets, deeper inventory per product, longer product lifecycles, and a brand story doing the selling.
- A large, fast-changing catalog (roughly 1,000 and up) usually means volume: many small bets, thin margins per item, heavy paid traffic, and products retired as soon as they stop converting.
- A mid-size catalog that keeps growing is often the most interesting signal — it means the operator is actively testing, and the products added most recently are the ones they currently believe in.
The number also disciplines everything else you research. If you are about to analyze a store’s ads or its product pages, knowing whether you are looking at 60 products or 6,000 changes what “they run a lot of ads” means in context.
What it does not tell you matters just as much. A product count says nothing about sales, traffic, or margins. A store with 4,000 products might sell three of them; a 40-product store might be doing exceptional volume on a single hero item. Treat the count as context, never as a verdict.
Step 1: Open the Store’s Sitemap Index
Every standard Shopify store publishes its sitemap at a predictable address:
https://STORE-DOMAIN/sitemap.xmlOpen that URL in a browser. You will get an XML file — a plain index, not a designed page. It contains no products directly. Instead it links to section files, something like:
<sitemapindex>
<sitemap><loc>https://store.com/sitemap_products_1.xml?from=...&to=...</loc></sitemap>
<sitemap><loc>https://store.com/sitemap_pages_1.xml?from=...&to=...</loc></sitemap>
<sitemap><loc>https://store.com/sitemap_collections_1.xml?from=...&to=...</loc></sitemap>
...
</sitemapindex>You only care about the file whose name contains products. The pages and collections files list other things.
Step 2: Open the Product Sitemap File
Click (or paste) the sitemap_products_1.xml URL. You get a second XML file that lists URLs, one per published product:
<url>
<loc>https://store.com/products/some-product-handle</loc>
<lastmod>2026-10-25T14:46:41-07:00</lastmod>
</url>Two practical details:
- Force the full range. Some stores link the product sitemap with
fromandtoparameters that limit the ID range. To be sure you are seeing everything, append?from=1&to=9999999999999to the URL if those parameters exist. We verified this works on live stores: the file then returns the complete published catalog. - The first entry is usually the homepage, not a product. The file can include the root URL alongside the product URLs. This is the most common reason a hand count comes out one too high — or several too high on small stores where the product file is mostly navigation.
Step 3: Count Only the /products/ URLs
Do not count <loc> tags total. Count only the entries whose URL contains /products/. Each published product appears exactly once — Shopify does not list variants or product images as separate URLs — so the /products/ count is the product count.
The fastest way, if you are comfortable with a terminal or a spreadsheet, is to save the file and count matches of the pattern /products/:
# in a browser: Ctrl+F for "/products/" and read the match count
# in a terminal:
curl -s "https://store.com/sitemap_products_1.xml?from=1&to=9999999999999" \
| grep -o "/products/[a-z0-9-]*" | sort -u | wc -lThe sort -u matters: it removes any duplicate handles so a product that appears twice in the file is not counted twice.
Step 4: Big Stores Ship Multiple Files
For larger catalogs, Shopify splits the product sitemap into several files by product ID range: sitemap_products_1.xml, sitemap_products_2.xml, and so on, all linked from the index you opened in Step 1. We verified a live store whose index listed seven product sitemap files — and the files are not equal-sized, because the split follows product IDs, not round counts. One chunk held 51 product URLs and another held 766.
So the rule is: open every sitemap_products_N.xml file in the index and sum the /products/ counts across all of them. If you count only the first file on a large store, you will massively undercount — in our verified example, the first file alone covered under 3% of the real catalog.
Step 5: Read the Freshness, Not Just the Count
Each product URL carries a lastmod timestamp — the last time that product was meaningfully updated. Scanning these dates gives you a second signal for free:
- A catalog where most
lastmoddates are recent is being actively maintained: prices, stock, images, or descriptions are being touched. - A catalog where
lastmoddates cluster months or years back is either dormant or running on evergreen inventory that rarely changes. - A catalog where a small subset of products has very recent
lastmodvalues points at an operator testing a handful of new items right now — those are the products to watch.
A Worked Example (Hypothetical Numbers)
Suppose a store’s index lists three product sitemap files. You fetch each one with the full range parameter and count /products/ URLs:
| File | /products/ URLs |
|---|---|
sitemap_products_1.xml | 214 |
sitemap_products_2.xml | 486 |
sitemap_products_3.xml | 91 |
| Total | 791 |
Now scan the lastmod dates and find that 60 of those 791 products were modified within the last 30 days, and those 60 all sit in one product category. That single read tells you: mid-size volume store, actively testing in one category right now. That is a much sharper picture than “this store has a lot of products,” and it took about ten minutes with no tool beyond a browser.
Three Catalog Archetypes, and What Each Means
Once you have counted a few stores, the numbers fall into recognizable shapes:
The curated boutique (under ~100 products). The store’s value is selection and brand. Competing here means competing on creative and positioning, not on catalog breadth. If you research this store’s ads, expect polished brand creative rather than high-volume testing.
The testing operator (100–800, growing). This store is running a portfolio: launch, measure, keep winners, quietly delist the rest. The lastmod scan from Step 5 is most valuable here — the newest-dated products are the current bets. The product page teardown method pairs well with this: tear down only the products that were modified most recently.
The catalog machine (1,000+, multiple sitemap chunks). Volume play. Expect heavy ad rotation, aggressive pricing experiments, and products that live for weeks, not years. Researching any single product page here tells you less than researching the pattern — this is where store-level tools beat page-level ones.
Where the Free Method Breaks
The sitemap trick is reliable, but it has edges. Know them before you trust a count:
- Password-protected stores hide their sitemap with everything else. You will get a password page instead of XML. There is no legitimate workaround; the store has opted out.
- Headless or heavily customized storefronts sometimes run on Shopify’s backend but serve the front end from elsewhere. Most still keep the Shopify sitemap live, but a few do not. If
/sitemap.xml404s, try/sitemap_index.xml— some builds use that name. - Duplicate handles and non-product URLs inflate sloppy counts. Always filter strictly to
/products/and deduplicate. - The
products.jsonroute is real but unreliable. Shopify exposeshttps://store.com/products.json?limit=250&page=1, which returns catalog data as JSON — useful when it works. But Shopify rate-limits that endpoint aggressively: requests from shared or datacenter IPs often come back with a short error string instead of data. Do not build a counting workflow on it; the sitemap is the stable path. - A count is not a sales number. Unpublished, draft, and out-of-stock-archived products may not appear at all. Two stores with identical counts can be in completely different businesses.
Cross-Check Before You Trust the Number
Two cheap validations keep the count honest:
- Sample ten product URLs from the sitemap and open them. If all ten resolve to real product pages, the file is current. If several 404, the sitemap is stale and the count skews high.
- Compare against a collection page. Open a visible collection and check that its products appear in the sitemap. If visible products are missing from the XML, the store is excluding some products from the sitemap, and your count is a floor, not a ceiling.
Turning Counts Into a Research Habit
One count is a data point. A count tracked weekly is a strategy read: catalog growth rate tells you how hard an operator is pushing, and sudden drops in the count — dozens of products removed in one week — usually mean a purge of losers or a seasonal reset. Both are useful timing signals if you study a niche.
A simple spreadsheet is enough. One row per store, one column per week, plus a column for “products with lastmod in the last 30 days.” Ten minutes a week across five to ten stores gives you a catalog-growth dataset nobody published — you built it yourself from public pages.
When the count is not enough and you need to know which of those products actually moves, that is the point where page-level free data ends. TrendTrack’s free account lets you check individual stores, and the paid tiers are built for exactly the step after counting: tracking many stores over time, with traffic estimates, app stacks, and ad libraries alongside the catalog data.
Verified 2026 · 20% off Starter, Pro and Business for your first 3 months
The TrendTrack promo code is WINNING - 20% off all plans for the first 3 months, so if you decide the tracking step is worth paying for, applying it before checkout simply makes the first quarter cheaper. The per-plan numbers before and after the code are in the TrendTrack pricing breakdown.
FAQ
How do I check how many products a Shopify store has for free?
Open https://STORE-DOMAIN/sitemap.xml, click the sitemap_products_1.xml link, and count the URLs containing /products/. If the index lists several product sitemap files, count each one and add the totals. The method needs no account or app, works in any browser, and reflects exactly what the store currently publishes.
Does the sitemap count include product variants?
No. Shopify lists one URL per product, and variants are attributes of that product rather than separate pages. A T-shirt in five sizes and three colors is one URL and therefore a count of one. If you need variant-level detail, the optional products.json endpoint returns variant data, though it is frequently rate-limited.
Why does my count of the sitemap come out one too high?
Because the product sitemap file often includes the store’s homepage as its first entry before the product URLs begin. Filter strictly to URLs containing /products/ and the homepage drops out. Duplicate handles can also inflate a naive count, which is why deduplicating before counting is worth the extra step.
What if the store’s sitemap.xml returns a 404?
First try /sitemap_index.xml, which some custom builds use instead. If both fail, the store may be password-protected or running a headless front end without a public sitemap. In those cases there is no legitimate free way to count the catalog, and the honest answer is that the store has deliberately opted out of being counted this way.
Can I tell which products a store added most recently?
Partially. The lastmod timestamp on each product URL shows when a product was last meaningfully updated, and a cluster of very recent dates usually indicates new launches or active edits. It is an approximation rather than proof — a lastmod can also reflect a price tweak on an old product — but combined with the count it is a strong read on where the operator is currently focusing.
Is a bigger catalog better for dropshipping research purposes?
Neither bigger nor smaller is inherently better; they are different games. A large catalog signals volume testing with thin margins and heavy ad rotation, while a small catalog signals curation with deeper brand investment. The useful question is what the count and its weekly trend tell you about how that specific operator competes, which is why tracking the number over time beats reading it once.
If you want the same count plus traffic, ads, and app data on every store you track, the free Shopify store analyzer walks through what the free TrendTrack account already covers — and when a catalog count turns into a weekly habit, the tracking tiers do the remembering for you.