By platform
Shopify products not showing on website
The product is in your admin, and the shop page shows a gap where it should be. Mimiq sends simulated visitors to the shop and shows the step where the product drops out.
Why are my Shopify products not showing on my website?
A Shopify product appears on the storefront only when it is Active, available on the Online Store sales channel, and listed in a collection the shop page displays. Check those three in the admin before you blame the theme. Then open the store in a private window to see what a shopper sees. A simulated visitor shows the step where the product drops out of the shop.
What this looks like in a report
“The apron should be in this grid, but I have looked twice and it is not here. Maybe they stopped making it, so I will look somewhere else.”
The fix. Set the apron to Active, turn on Online Store under its sales channels, and check that the collection the shop page shows lists it. Then open the shop in a private window and confirm the apron appears in the grid.
An illustration. Run a test to see your own.See a real sample report
A product can exist in your admin and still be invisible to every shopper
A Shopify product reaches the storefront only when several settings agree. The product has to be Active, not Draft or Archived. It has to be available on the Online Store sales channel. Then a collection the shop page displays has to include it, either because someone added it by hand or because the collection's rule matches its tags, type or vendor. When one of those fails, the product still sits in your admin, so the owner sees it and assumes the shop is broken. A shopper only sees the gap.
- In the admin, check the product status. Draft and Archived products do not appear on the storefront.
- Open the product's sales channel list and confirm that Online Store is turned on for it.
- Open each collection the shop page shows and check whether the product is listed in it.
- For a collection built from rules, compare the product's tags, type and vendor with the rule text.
- Open the store in a private window and check whether a password page appears before the shop.
The shop page, the search box and the direct link fail in different ways
A shopper meets a missing product in three places, and each one reports it differently. On the shop page the product is absent from the grid. In the search box the same name returns nothing. A direct link usually shows a page not found, which tells the shopper the link is dead. Those symptoms come from different settings, so start with the direct link, which tests the product alone, then move to the grid, which also depends on collections.
Draft, channel and collection rules all look the same from the grid
A draft product and an archived product both disappear from the storefront, and both still appear in your admin. Check the status label on each row, because a draft or archived product looks almost the same as an active one in a quick scan. A product can also be Active but left off the Online Store sales channel, which keeps it off the storefront. Open the product and check its status and its sales channel list before you look anywhere else.
Collections decide what the shop page lists. A manual collection shows only the products someone added to it, so a new product stays missing until it is added. A collection built from rules shows products whose tags, type or vendor match the rule, so one tag with a typo hides the item from that collection. Compare the tag on the product with the rule text letter by letter, because the mismatch is rarely the one you expect.
Password pages and market settings hide the store from some visitors only
A store protected by a storefront password shows a password page before any product, so nothing appears to a visitor who has not entered it. Market settings can also keep a product out of one country's view, while the same product shows to a visitor from a country the market includes. Check the market list in your settings, then open the shop in a private window from the country where the product should show.
What the grid screenshot and the recorded errors show
A simulated visitor opens the shop page, searches by the product name, and opens the product when the task asks. The run records each step, a screenshot of the grid at that step, and any failed request or script error on the page. If the product is missing, the report shows the grid with the gap and the step where the visitor gave up. That tells you whether the shop page failed or the product page did.
The run does not read your admin, so it cannot say which setting is off. Open the product status, the sales channel list and the collection rule yourself, in that order, and fix the one that does not match. Then send the same visitor again and see whether the product now appears on the grid. Once it appears, check the direct link too, since a grid and a product page can fail separately.
Mimiq is independent and not affiliated with the platforms it names. Names belong to their owners.
What you get with Mimiq
- 01
Run it by hand, or on every pull request
Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.
- 02
Bugs and usability problems in one report
The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.
- 03
Visitors that behave like your audience
Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.
- 04
A prompt to fix each problem
Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.
- 05
Follow every visitor
See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.
The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.
A new collection rule or theme update can hide the next product
A new product can vanish the same way. A collection rule that worked for last season's tags will skip a product tagged differently, and a theme update can change which collections the shop page displays. After each change, send the same visitor to search for the new product by name and reach the grid. Run it again before the next campaign points traffic at a product, so you see the gap before shoppers do.
Starter
Try it on one launch
About 4 tests of 5 visitors
- Visitors on your landing page, signup and checkout
- Where they left and why, with a fix to copy for each problem
- Run it in the app or on every pull request
- Ask any visitor a question, included
- Test accounts and protected previews
Builder
Test every build
About 20 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Pro
Test every release, as a team
About 60 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Scale
Test at scale, every day
About 240 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Priority support
- Cancel anytime
Questions
Why does the product show in my admin but not on my store?
The admin lists every product, including drafts, archived items and products that are not on the Online Store channel. The storefront shows only products that pass all three checks: Active status, the Online Store channel and a collection the shop page displays. Any single failing check removes the product from the storefront.
Will the product show up on its own after a while?
Not when the cause is a draft status, an unticked channel or a collection rule that does not match it. Those settings stay the same until someone changes them, so waiting changes nothing. Fix the setting, then reload the shop page in a private window.
Does a password page mean my products are broken?
No. A password page stops every visitor before the shop, and it is often switched on while a store is still being built. Products still exist and still work from the admin. Remove the password when you are ready for shoppers, then send the visitor again from a private window.
Can the simulated visitor tell me which product setting is wrong?
No. The run shows the grid, the search result and the step where the visitor stopped, with a screenshot and any errors recorded on that step. It does not open your admin. It also does not tell you how many shoppers would buy the product once they found it.
Keep reading
Send visitors and see what breaks first.
Your first test is free: sign in with Google and it starts right away. Last checked 2026-11-02.