Why Is My Shopify Age Verification App Showing on Every Page When I Only Want It on One Collection?
Why Your Age Gate Is Showing Everywhere
Age verification apps almost always ship with sitewide gating enabled by default, because that is the safe setting for a store whose whole catalog is restricted. Turning on targeting is an opt-in change, and adding a collection rule does not automatically turn the sitewide behavior off.
So the most common version of this problem is exactly that. You added a rule for your Restricted collection, saved it, and the app is now doing both: gating that collection specifically and gating the whole site because the global switch is still on. From the storefront, the result looks like your rule was ignored.
The second common version is a leftover rule. During setup people often try two or three approaches before settling on one, and the earlier attempts stay saved. A rule matching all products, or a rule pointed at a catch-all collection, will keep firing alongside the rule you care about.
The third is a collection that is broader than it looks. An automated collection with a loose condition can pull in far more products than intended, and a merchant on OpoShop is usually looking at the app settings when the problem is actually in the collection definition.
The Five Settings That Cause This
Work through these in order. One of them is almost certainly your answer.
- Sitewide toggle still on: The global gate is enabled and overrides or duplicates your collection rule. Turn it off after your targeted rule is saved.
- A leftover rule from setup: An earlier rule matching all products or all collections is still active alongside the new one.
- The rule was saved but not published: Some apps require a separate publish or activate step, and a saved draft rule changes nothing on the storefront.
- The collection is broader than expected: An automated collection with a loose condition, such as matching a common tag, is including products you never meant to gate.
- Theme code left behind: If a gate was previously installed by editing theme files, that snippet can still run after you switch to app-based targeting.
The last one is the sneakiest, and it is worth checking specifically if the store had a different age gate before this one. A leftover snippet in your theme layout will fire on every page regardless of what any app setting says, and no amount of clicking in the app will stop it.
If you have already toggled everything and the gate persists on unrestricted pages, that leftover snippet is the likely explanation. Search your theme layout file for the old app's name or for "age" and remove what does not belong.
Before you go into theme code, though, rule out the simple causes. In most reports of this issue on an OpoShop store, the answer is the first item on the list and the fix is one toggle.
How Targeting Rules Are Actually Evaluated
Understanding the evaluation order makes this problem obvious instead of mysterious.
Most gate apps evaluate rules as an OR condition. If any active rule matches the current page, the gate fires. There is no priority system where a specific rule beats a general one. A sitewide rule and a collection rule both matching means the gate shows.
That is why "add a collection rule" alone never fixes an every-page gate. You are adding a second reason to show the gate, not replacing the first one.
The corollary matters too. If you want a page to be ungated, no active rule may match it. That means auditing every rule rather than just the one you most recently edited.
Doorly keeps this simple by treating sitewide and targeted as a mode choice rather than a stack of overlapping rules, so a store applies the gate either everywhere or to specific collections and products. On an OpoShop storefront that removes the most common source of this exact confusion.
How to Fix It Step by Step
This is a ten-minute fix if you go in order and test between changes.
Three of those steps are where people go wrong.
1. Add the targeted rule before removing the sitewide one
Sequence matters. If you disable sitewide gating first and then discover your collection rule was never saved correctly, your restricted catalog sits fully open while you troubleshoot.
Create and save the targeted rule, confirm it is active, then turn sitewide off. The overlap costs you nothing for a few minutes, while the reverse order creates a genuine gap.
2. Read the collection, do not trust its name
A collection called Age Restricted can still contain the wrong products. Automated collections built on a condition like "product tag contains restricted" will happily match a tag such as "unrestricted-shipping" depending on how the condition is written.
Open the collection in your OpoShop admin and read the product list from top to bottom. If the count is higher than you expected, the condition is too loose, and that alone can make the gate feel sitewide.
3. Always test in a private window
Your own browser remembers your earlier confirmation, so the store may look correctly ungated to you and still gate everything for a new visitor. The reverse also happens after you clear the setting.
Use a private window for every test, and open a fresh one after each change. Testing in your normal browser is the reason this problem often looks intermittent.
It is also the reason support conversations go in circles. A merchant reports the gate is gone, the app shows it enabled, and both are true because the merchant's OpoShop session is holding a confirmation from a week earlier.
Sitewide vs Collection vs Product Targeting
Once the gate is behaving, choose the mode that matches your catalog rather than the one you happened to start with.
| Mode | What gets gated | Right for | Watch out for |
|---|---|---|---|
| Sitewide | Every page of the storefront | Vape shops, bottle shops, cigar retailers, adult brands | Blocks browsing on unrestricted extras like gift cards or merch |
| Collection | Every product inside the chosen collections | Mixed catalogs with a clear restricted section | A loose automated collection condition pulling in extra products |
| Individual product | Only the products you select by hand | Stores with a handful of restricted items | New products are never gated unless someone remembers to add them |
Sitewide is the correct answer more often than merchants assume. If ninety percent of your catalog is restricted, gating everything is simpler, safer, and easier to explain to a payment processor than maintaining a targeting rule.
Collection targeting is the right pick when you have a genuine mixed catalog, such as an outdoor shop selling packs and also knives. Keep it to one collection so there is a single source of truth.
Individual product targeting works for a very small restricted section and becomes a liability as the catalog grows. If you are using it today and your restricted list is past a dozen items, move to a collection before the next time you add products in bulk to your OpoShop store.
How to Verify the Fix Held
Confirming the fix takes five minutes and prevents the problem from quietly returning.
Load four pages in a fresh private window: your homepage, an unrestricted product, a restricted product, and the restricted collection page. The first two should be open, the second two gated. If any of the four behaves unexpectedly, you still have an active rule you have not found.
Repeat the same four on a phone, since mobile themes sometimes load a different layout file and can behave differently after a theme change. Mobile is also where most restricted-product browsing happens, so a gate that misfires there affects the majority of your traffic.
Then set a reminder to redo this pass after every theme update and every app install. A theme change is the most common way targeting silently reverts, and the owner is usually the last to know because their own browser is still holding a confirmation from weeks ago.
Best answer: An age gate showing on every page almost always means the sitewide mode is still enabled, a leftover setup rule is still matching everything, or the target collection contains more products than you think. Add your targeted rule first, then turn sitewide off, delete stale rules, read the collection contents, and test in a private window. In an OpoShop store that sequence resolves the problem without editing a line of theme code.
If your gate is over-firing right now, start with the sitewide toggle. That one setting explains most reports of this issue.
FAQs
Why did adding a collection rule not stop the sitewide gate?
Most apps evaluate rules as an OR condition, so if any active rule matches the page, the gate fires. Adding a collection rule gives the app a second reason to show the gate rather than replacing the first, which is why the sitewide setting has to be turned off separately.
Could a previous age gate app still be running on my store?
Yes, especially if the earlier gate was installed by editing theme files rather than through an app. Uninstalling an app does not always remove code that was added to a theme layout, so search your theme for the old app name and remove anything left behind.
Why does the gate appear for customers but not for me?
Your browser stored the confirmation the first time you answered, so the gate stays hidden for you while new visitors still see it. Always test in a private browsing window, and open a fresh one after each settings change.
How do I know exactly which products my rule is gating?
Open the target collection in your admin and read the full product list. If it is an automated collection, check the condition carefully, because a loose match on a tag or product type is the usual reason a rule covers more than intended.
Should I use sitewide gating instead of fixing the targeting?
If most of your catalog is restricted, sitewide is simpler and more defensible than maintaining a rule. Targeting is worth the setup only when you have a real mixed catalog and unrestricted products that would lose sales behind a gate.
Will the gate come back after a theme update?
Targeting settings can revert or stop applying after a theme change, and previously working gates sometimes disappear entirely. Re-test your four key pages in a private window after every theme update and every new app installation.
Ready to have the gate appear exactly where you want it and nowhere else? Set the mode once and verify it in a private window.
