Check the storefront source
The fastest signal is usually in the page source: Shopify asset URLs, `Shopify` JavaScript objects, Shopify checkout references or CDN patterns often appear in the HTML.
Look for common Shopify clues
- Search for `cdn.shopify.com` or Shopify-hosted assets.
- Check whether the site uses Shopify checkout patterns.
- Inspect JavaScript globals such as Shopify analytics objects.
- Look for myshopify references in source, redirects or canonical tags.
- Review theme markup and section structures common to Shopify storefronts.
Why this matters before app detection
Shopify app detection only makes sense once the storefront has been identified as Shopify. Otherwise you risk matching generic third-party scripts that also appear on non-Shopify sites.
How Detectify uses this step
Detectify checks for Shopify storefront signals before displaying any app detections. If the site does not look like Shopify, the analysis stops and no app list is rendered.
Common false positives to avoid
Generic third-party scripts such as analytics tags, chat tools or popup libraries can appear on both Shopify and non-Shopify sites. That is why the best filter is not a single script but a combination of Shopify-specific storefront evidence.
- Avoid assuming Shopify from one analytics script alone.
- Give more weight to Shopify asset hosts and checkout references.
- Use myshopify domain clues as supporting evidence, not the only signal.
- Cross-check multiple storefront markers before treating a store as Shopify.
Run the live check
Paste a storefront into the Shopify App Detector to confirm Shopify signals and then surface visible apps, analytics tools and payment methods.
Official Shopify references
Related guides
Key takeaway
Shopify identification is the first filter. Without it, app detection is noisy and much less trustworthy.