Your Shopify store gets traffic but no sales — start with the pages you never scroll to

Published September 8, 2026 by Adot Technologies Inc, the team behind Arvio. The store list was drawn at random from a public source on August 26, 2026. We have read it twice since: field completeness on September 1, 2026, and catalogue depth on September 8, 2026.

Key takeaways

• The advice you have already read — homepage, theme, cart, checkout — is about the pages you look at every day. This piece is about the ones you don't.
• Your catalogue is deeper than that. On the stores we could measure, the biggest collection ran a median of 7 pages and the deepest ran 241.
• How many products fit on a page is set by your theme, not by Shopify. We measured 10–48 products per page across those stores, so "page 3" means a different depth on every store.
• The fix is to sort your catalogue by what is missing and read the end of that list rather than the top.
• What we did not measure: whether fixing those pages moves your conversion rate. We haven't run a controlled test, and nothing below claims a number for it.

You can only fix what you can see

Arvio reads your product data past the first page, shows you where it comes up empty, and drafts the fill for you to approve.

See Arvio on the Shopify App Store →

The quick version

1. Check where your traffic actually lands before you change anything. If it's landing on product pages you can't remember writing, that's the case this article is about — and it is the one most checklists skip, because those pages are also the ones the person writing the checklist never sees.
2. Find those pages by sorting, not by scrolling: the Shopify admin can filter your product list by what is missing, and a CSV export can sort by it.
3. Fix the data on the pages people actually land on first, then work down the list. The order matters more than the volume.

Your catalogue is longer than anything you look at

On the 18 live storefronts where we could count it, the biggest collection ran a median of 7 pages of products, and the deepest ran 241. Advice about a store that is not converting is written for the pages an owner sees — and almost none of that depth is one of them.

(If what you want is the per-page checklist rather than the depth argument, we published one with base rates from live stores: a Shopify product page audit checklist.)

We took live Shopify storefronts from a public list, opened the biggest collection on each one, and counted how many products the theme puts on a single page. Then we divided the size of that collection by that number.

The five deepest of the 18 stores we could count — not a typical store; the median is four rows below:

Products in the biggest collection	Products per page (measured)	Pages
2,883	12	241
1,838	12	154
1,919	16	120
1,489	20	75
403	17	24

Across all 18 stores we could count, the median was 7 pages and 13 of them ran deeper than three pages.

Page size is a theme decision, not a Shopify decision. Shopify's own Liquid paginate documentation describes the tag as taking "The number of array items to include per page, between 1 and 250." (read August 29, 2026) — that is a ceiling, not a default. In our reading, stores landed anywhere between 10 and 48 products per page. So "it's on page 2" is not a fixed amount of scrolling; on one store page 2 starts at product 11, on another at product 49.

If products seem to be missing from a collection entirely rather than just sitting deep in it, that is a different problem with a different cause — we wrote it up separately in why a Shopify collection isn't showing all its products.

Where a product sits in your collection is not where a visitor enters. Someone arriving from search lands on whichever product page matched their query. That page may be one you have read a hundred times, or one you last saw the day you imported it — the collection position that decides whether you ever scroll to it does not decide which page they land on.

How we measured this

Sample. 18 live Shopify storefronts, read on September 8, 2026, taken at random from a public list of stores whose owners had posted their own URL on the Shopify Community's Store Feedback board. Everything here came from endpoints any browser can fetch.

Whether it looks like you. These are stores whose owners posted their own URL asking for feedback, so they skew newer and less established than a random Shopify store. On the September 1 reading of all 39 of them, the median catalogue held 130 products — but the 18 deep enough for us to count pages on ran larger than that, so the depth figures below describe the bigger end of the list, not a typical small store. Stores that had already stopped serving a storefront dropped out when the list was built, so what is left is the ones still trading.

The funnel. 39 storefronts in the public list carried products; we opened the biggest collection on each. 18 let us count page size from the storefront itself and are the basis for every page-depth number below. The other 21 could not be counted — 15 returned overlapping products on both pages, 2 rendered no product links we could read, 2 returned nothing on page two while the collection was larger, 2 ignored the page parameter — and are excluded rather than counted as one page.

The exclusion rule, fixed before we looked at the results. If we could not confirm from the storefront itself how many products a page holds, that store does not get a page count — which happens when the theme ignores the ?page= parameter, when it loads more products by scrolling instead of paging, or when the store rate-limited us.

Method 1: use the admin's filters instead of scrolling

The Shopify admin can narrow your catalogue by the fields it indexes. It filters on values that exist, not on emptiness — so use it to cut the catalogue into slices, then read the end of each slice, which is where the products you forgot about sit.

1. Open Products in the admin.
2. Use the search-and-filter bar to filter by Product type, Vendor, Tagged with, Collection, or Status.
3. Sort the result by Product title A–Z and jump to the last page rather than reading from the top.

What this method is good at: it costs nothing extra, it is immediate, and it works on any plan. What it is not good at: the admin filters on fields that exist. There's no filter for "the description is two sentences long", or for "this description was written for a different product".

Method 2: export a CSV and sort by what is missing

For anything the admin cannot filter on, export and sort.

1. Products → Export, then choose "CSV file for Excel, Numbers, or another spreadsheet program" (exporting products, read September 8, 2026).
2. Open the file and add a column with a formula for the thing you care about — for example the character length of the description column (Description in the current template; older exports call it Body (HTML)).
3. Sort ascending. The rows at the top are the product pages a visitor is most likely to bounce off of.

This is where CSV work usually goes wrong:

• Each variant gets its own row. Shopify's product CSV guide describes it from the writing side: "enter all the fields for the product in the first row along with the URL for the first image. In the following rows, enter the URL handle. Then skip the Title, Description, Vendor, and Tags columns." (read September 8, 2026) So the rows after the first one are blank in exactly the columns you want to measure. Keep only the first row of each Handle before you sort.
• That column holds HTML, so a "200-character" description can be mostly markup. Strip tags before you measure length, or you'll rank a <p><br></p> above a real sentence.
• Re-importing matches on Handle: "when the handle in the import CSV file matches an existing handle in your products list, the values in the CSV file overwrite the values in the matching columns." (product CSV guide, read September 8, 2026.) Shopify also warns that "sorting your CSV file in a spreadsheet program can cause product variants or image URLs to become disassociated" (exporting products, read September 8, 2026) — so sort a working copy for analysis, and never re-import that copy.

Method 3: have something walk the whole catalogue

Both methods above have the same ceiling: you still have to decide what to look at, and you still have to write the fix yourself. For a catalogue that runs 7 pages that is an afternoon; for one that runs 241 it is not something you do once a quarter.

This is the part Arvio does. It reads the catalogue on your live store, flags where product data is missing or thin, and drafts the replacement text for you to approve — product by product. It's an operator you review, not a bulk find-and-replace you run and hope about.

It drafts; you approve. If you want something that rewrites 2,000 products without you reading any of them, this is the wrong shape of tool. And it only sees your product data — it can't tell you your pricing is wrong or that your photography is the problem.

See Arvio on the Shopify App Store →

Five things that quietly go wrong past page one

A separate reading of the same stores on 2026-09-01 — 20,659 products across 39 storefronts — says something more useful than an average. Missing product data is not spread thinly across a catalogue. It is closer to a switch that is either on or off for the whole store.

36% of all those products had no product type, while the median store was missing it on 9% of its catalogue. Both numbers are true, and the gap between them is the finding: three stores accounted for 75% of every missing value, and inside those three the field was empty on 85–99% of the entire catalogue. Counting stores instead of products splits them: of the 39, 15 were missing it on more than half their products and 18 on under 5% — only 6 sat anywhere in between. Catalogue size sorts those two groups the opposite way to the raw count — stores holding 72 products or fewer were missing it on a median of 46% of their catalogue, stores above that on 2%. Thin descriptions follow the same shape rather than being sprinkled evenly.

Before you start reading individual products, check whether a field is empty on everything — that is usually one import that did not carry the column, and it is one fix rather than a thousand.

1. Descriptions that stop after one line. (Product description examples if you want a shape to copy.) Usually the product was added in a hurry, or imported from a supplier feed that had nothing in the description field.
2. No product type. (How to add a product type in Shopify covers the field itself.) An empty Product type keeps the product out of every filter and automated collection rule built on that field — other filters, like Vendor or Status, still find it, but the merchandising that depends on type does not.
3. Images that were never re-checked. A product that has one photo has one chance to answer "is this the thing I searched for".
4. Copy written for a different variant. Very common after a catalogue import: the description describes the parent product, and every size or colour repeats it word for word.
5. Products that are still listed but no longer supplied. They keep their search ranking, take the click, and answer with a page nobody maintains.

None of these are conversion tricks. They are the reason a visitor who arrived with intent leaves without a reason to stay.

Three situations where this really is the problem

You get search traffic to product pages but the homepage numbers look fine. Check the landing pages in your analytics, not the sessions total. If the product pages taking the traffic are ones you can't remember writing, that's this problem.

Your catalogue arrived in bulk. Imported from another platform, a supplier feed or a CSV — we have a longer piece on cleaning up product data after an import. Whatever the source file did not carry, your store does not have — and the gaps are distributed across the whole catalogue, not the front of it.

Sales are concentrated in a handful of products. If most of your revenue comes from the products you personally wrote, that is not proof the rest are bad products. It is what you would expect if the rest were never finished.

Is there public data on how deep Shopify catalogues run?

We are not aware of a published figure, which is why we measured it ourselves. On September 8, 2026 we read 39 live Shopify storefronts taken from a public list and counted page size directly from the storefront on the 18 that let us: the biggest collection ran a median of 7 pages, the deepest ran 241, and themes were putting between 10 and 48 products on a page. The exclusion rule and the full funnel are in the method section above — 21 of the 39 could not be counted and are left out of every depth figure rather than counted as one page.

When this is not your problem

Which of these are you? The fix is different for each.

• Small catalogue. If your whole store fits on one or two pages, you've already read all of it. Your conversion problem is somewhere else — price, shipping, trust, or the traffic itself being the wrong traffic.
• No traffic to product pages at all. If visitors land on the homepage and leave, deeper product pages are not what is stopping them. Work on where the traffic comes from first.
• Traffic that was never going to buy. If the visitors arriving were never in the market, better product pages won't turn them into buyers — check what the traffic is before you rewrite what it lands on.
• You already have complete product data. Some stores do. In that case the catalogue is not where your answer is, and nothing in this article will help.

If you want the catalogue walked for you

Everything above is doable by hand, and for a store of a few dozen products doing it by hand is the right call. The reason to automate it is depth: the further your catalogue runs past what you can read, the less likely it is that you will ever get to the end of the list on your own.

That is the case Arvio is built for: it works down the list you would never reach, and you approve each draft before it goes anywhere.

See Arvio on the Shopify App Store →

FAQ

Why is my Shopify store getting traffic but no sales?

The usual answers — price, trust, shipping cost, checkout friction — are all real. This article is about the one that is hardest to see: visitors landing on product pages the owner has never read, because those pages sit past the first page of a collection. Check which pages your traffic actually lands on before assuming it is the homepage.

How many products does Shopify show on a collection page?

Shopify doesn't set it — your theme does. The Liquid paginate tag takes "The number of array items to include per page, between 1 and 250." (read August 29, 2026) In our September 2026 reading of live storefronts, themes were using between 10 and 48.

How do I find products with missing descriptions in Shopify?

The admin can't filter on description length. Export your products to CSV, strip the HTML from the description column, add a length column and sort ascending. Keep one row per Handle first — each variant gets its own row, and the rows after the first are blank in the description column.

Does thin product copy actually affect conversion?

It affects whether a visitor who landed with intent has a reason to keep reading. We haven't tested that. What we measured is how deep a catalogue runs — 7 pages at the median, on the stores where we could count it.

What else is usually empty down there?

Meta descriptions, most often — they are invisible on the page itself, so nothing prompts you to write them. We measured how many were missing across live stores in Shopify meta descriptions.

Should I rewrite my whole catalogue?

No. Sort by what is missing and start with the products that already take traffic. A product page nobody lands on doesn't get more valuable because it's well written.

Is this a Shopify problem?

No — it is a consequence of pagination, which every catalogue on every platform has. Shopify's admin filters are good at the fields that exist; the gap is that "thin" and "empty" are not the same thing, and only one of them is filterable.

What is the fastest way to see how deep my own catalogue goes?

Open your largest collection, count the products on its first page, and divide the number of products in that collection by that number. That is the number of pages your store has. Most owners have read the first one.