What Shopify app detector means for a Shopify store

What you actually get

Shopify app detector lists apps that load on the public storefront and, when it recognizes one, links the App Store listing. Reviews, email, upsells, chat, subscriptions, and loyalty are the usual set, because those are the apps a shopper meets.

A product page is a theme plus the apps embedded in it. The detector makes that stack readable. It is not a list of every app in the admin.

App embeds are turned on per theme, in the theme editor. An app that is installed and never embedded does not load for a shopper, so it will not appear here either.

What it leaves out

Only apps that load on the storefront can be named. An app that never injects a script on the page stays hidden.

The steps for a single pass are in how to run Shopify app detector.

What a Shopify app detector lists

A Shopify app detector looks at the storefront and lists apps that actually load there. The list is about the public shop a buyer downloads in the browser, not about every app installed in admin. If an app never injects anything on the storefront, it stays off the list. That includes many apps that only work in the admin: some reporting, some internal workflows, some edits to orders that never add a script to the product page. Hidden from this check means not present on the storefront. It does not mean uninstalled, and it does not mean unimportant to your operations.

When the detector recognizes an app, it can point you at the App Store listing. The link is a convenience so you know which product the script corresponds to. It is not an endorsement, a security review, or a verdict that the app is configured well. An unrecognized script can still be an app. Recognition is a label, not a complete census of every possible add-on. You still confirm anything important inside the theme editor and the Apps list in admin.

The check is not a speed test. It does not rank apps by milliseconds. It does not tell you which script is the heavy one. It does not bill you, read your app invoices, or see whether a charge is active. A listed app may be on a free plan. A quiet admin app may be the expensive one. Money questions stay in admin billing. You came here to learn what the storefront loads.

Run it from /app-detector/ on the domain you intend. Use your own domain when you are cleaning your shop. Use another domain when you are trying to understand what a buyer loads there. In both cases you get storefront presence, not a tour of their admin. Pair the list with the public theme name from /theme-detector/ so each app note has a theme to sit on. App embeds are per theme. A list without a theme name becomes stale the day you publish a different theme.

Storefront load versus the admin app list

Open the Apps section in Shopify admin and you will see installs. Some of those installs change the storefront. Some change checkout only on eligible plans. Some never touch a page a buyer views before checkout. The detector list and the admin list are supposed to disagree. The disagreement is the information. Anything on the storefront list should be findable as an install or as a script the theme adds. Anything that is only in admin will not show up here, and you should not hunt through the storefront for it.

A theme can also contain code a developer pasted, which is not an app at all. The detector is aimed at apps that load on the storefront. A custom snippet can still affect the page and remain a theme-file conversation. If you see behavior on the product page that no listed app explains, the next place to look is the theme editor, then someone with code access. Do not install a new app to counteract a snippet you have not found.

Staff-only previews can confuse you. If you are logged into the shop, some apps show extra tooling. A buyer is not logged into your admin. When an app appears on the detector result for the public URL, treat it as buyer-visible load. When something appears only while you are inside the theme editor, confirm on a logged-out browser before you add it to the removal list. The public result is the closer match to the buyer.

Duplicate names deserve a second look. Merchants install two review apps, or a page builder plus a separate badge app that does the same job. The detector listing both is a gift. It means both load, not that both are needed. Your admin list might have even more review apps that are installed and dormant. Dormant and not loading is a billing question. Loading twice is a storefront question. Work on the loading ones first.

App Store links when a script is recognized

A recognized app comes with a way to read the listing. Read it for what the app claims to render, where it usually sits, and what it asks to access. You are orienting, not shopping. The listing will not tell you whether this shop uses one feature or ten. It will not tell you the monthly bill. It will tell you the product name so your note matches the words your team already uses in admin.

If there is no listing link, write the name the detector could show and mark it unrecognized. Then search your admin apps for a similar name, and search the theme editor for an app block or embed with similar wording. Unrecognized does not mean dangerous by default, and recognized does not mean safe by default. This tool is not a security review. If you need a security judgment, involve someone whose job is that judgment, with access to the app permissions in admin.

Do not install an app because its listing looked impressive while you were identifying a script. Identification and installation are different afternoons. The first afternoon ends with names on a page. The second afternoon, if it happens, starts from a job the current theme and the current apps cannot do. Mixing them is how a reading session adds a script.

Save the listing path next to your own decision, not instead of it. Example of a useful line: name, listing found, appears on the product template as an app block under the form. Example of a weak line: a row of listing links with no placement. Placement is what you learn in the editor. The link only stops you from arguing about which app you meant.

Embeds and app blocks sit on one theme

Shopify lets apps add app embeds and app blocks. An embed often affects the theme broadly, such as a script that runs across templates. An app block is placed inside a template like any other section, on a specific spot in the order. Both are configured on a theme. If you enable them on Dawn and then publish a duplicate where they are off, the storefront list can change even though admin still shows the apps installed. When you read a detector result, write the theme name beside it. A result captured on Monday does not describe the theme you publish on Thursday.

The product template is where you will see the blocks that sit near the form. The form itself should still hold title, price, variant picker, and buy buttons unless an app replaced it. An app block under the description is a different object from an app that takes over the form. Your note should say which one you are looking at. The detector list alone may show the app in both cases. The editor tells you the role.

Turning off an embed in one theme does not uninstall the app. Turning off an app block on the product template does not stop the same app from loading on the collection template if another block or embed remains. Be precise in the note: where you disabled it. Then reload the URLs that matter. Precision here saves you from believing an app is gone because one template looks clean.

Checkout UI extensions that run on the information, shipping, or payment steps are a Shopify Plus surface. This storefront list is about the shop before that. Do not treat a missing checkout extension as a broken detector, and do not spend this pass auditing checkout. If your question is the product page, stay on the product page. Mention checkout only if someone tries to explain a storefront script by pointing at a Plus checkout feature. Those are different places.

What the list refuses to decide

The list does not say an app is worth the money. Worth depends on whether you use the feature, whether another section already does the job, and what the bill is. You can see the feature on the storefront sometimes. You see the bill in admin. You see the section overlap in the theme editor. Three places, three facts. The detector contributed the first clue: it loads.

The list does not say a competitor is winning because of their apps. You do not know their margin, their traffic, or their operations. You know some scripts their buyers download. That is a thin slice. Copying the slice stacks scripts on your theme without copying anything that might actually matter, such as the product or the offer. Seeing an app on their storefront is not a reason to install it on yours.

The list does not measure how heavily you configured the app. A review app can be present with no reviews displayed, or present with a widget on every template. The detector says it loads. Your eyes on the product template say whether the widget is in the way. Configuration depth is an editor and app-admin question. Leave it there.

Each storefront app is another script the buyer loads and another vendor who can change behavior on you. That is the practical weight of a long list. It is not a moral judgment about apps. Some scripts earn their place by doing a job the theme cannot do. The list gets dangerous when nobody can say the job. Your later notes exist to attach a job to every name, or to mark the name for removal from the theme.

Shopify questions