Identifying the technology behind an online store can be surprisingly useful. Competitors may want to understand market trends, developers may need to diagnose integrations, marketers may be researching ecommerce features, and shoppers may simply be curious. One of the most common platforms to look for is Shopify, a hosted ecommerce system used by small boutiques, fast-growing direct-to-consumer brands, and large retail operations alike.
TLDR: You can often detect whether a website uses Shopify by checking its page source, URL patterns, cookies, checkout behavior, and network requests. Common clues include references to cdn.shopify.com, Shopify-specific scripts, cart endpoints, and cookies such as _shopify_y. Browser developer tools and technology lookup services can speed up the process, but no single sign is perfect. The most reliable approach is to combine several indicators before making a conclusion.
Why Shopify Detection Matters
Shopify powers a huge number of ecommerce websites, but many stores use custom themes, headless front ends, or third-party checkout modifications that make the platform less obvious. Detecting Shopify is not just about satisfying curiosity. It can help agencies prepare migration proposals, affiliate teams understand checkout flows, SEO specialists benchmark store architecture, and security researchers identify platform-specific behavior.
That said, platform identification should be done responsibly. The goal is to observe publicly available signals, not to bypass security, scrape private data, or interfere with a site’s operation. Fortunately, most Shopify indicators are visible through normal browsing and basic inspection tools.
1. Check the Page Source for Shopify Clues
The simplest method is to open the website, right-click on the page, and select View Page Source. Then use your browser’s search function and look for terms such as:
- shopify
- cdn.shopify.com
- Shopify.theme
- ShopifyAnalytics
- myshopify.com
If the source contains multiple Shopify references, the site is very likely using Shopify. For example, many stores load theme assets, JavaScript files, and images from cdn.shopify.com. You may also see code related to Shopify analytics, product variants, cart handling, or theme settings.
However, page source alone can be misleading. Some Shopify stores use custom builds that hide or minimize obvious references. Others may include Shopify-related scripts even if only a portion of the experience, such as checkout, is powered by Shopify. Treat source code as a strong clue, not an unquestionable verdict.
2. Look for Shopify Asset URLs
Shopify-hosted stores frequently serve images, theme files, fonts, and JavaScript from Shopify’s content delivery network. In the source code or browser developer tools, look for asset URLs that include:
- cdn.shopify.com/s/files/
- cdn.shopify.com/shopifycloud/
- cdn.shopify.com/extensions/
These URLs are among the most reliable public indicators. Product images hosted on Shopify often follow recognizable CDN paths, and theme assets may include filenames such as theme.css, theme.js, global.js, or app-generated scripts.
In Chrome, Firefox, or Edge, press F12 or open Developer Tools, then go to the Network tab. Refresh the page and filter for “shopify.” If many files load from Shopify domains, you have a strong signal.
3. Inspect Cookies and Local Storage
Shopify stores often set cookies used for analytics, sessions, checkout, and cart behavior. In your browser’s developer tools, open the Application or Storage panel and review cookies for the current domain. Common Shopify-related cookies include:
- _shopify_y
- _shopify_s
- _shopify_sa_t
- _shopify_sa_p
- cart
- cart_currency
- secure_customer_sig
Finding one of these cookies does not always prove the entire site runs on Shopify, but finding several of them, especially alongside Shopify CDN assets, is a strong indicator. Cookies are particularly helpful when a site’s visual design is heavily customized and does not look like a typical Shopify store.
4. Test Shopify URL Patterns
Many Shopify stores use predictable URL structures. You can test these paths by adding them to the domain in your browser:
- /cart
- /collections
- /products
- /checkout
- /admin
- /cart.js
- /products.json
For instance, visiting example.com/cart.js may return JSON data about the current cart if the site is built on Shopify. The /products.json endpoint may also exist, although some stores block or restrict it. Similarly, /admin on a Shopify store often redirects to a Shopify login path.
Be careful not to send repeated automated requests or probe aggressively. Checking a few ordinary public URLs is generally enough. If a site blocks access or returns errors, that does not necessarily mean it is not Shopify; the merchant may have disabled certain endpoints, installed protective apps, or used a custom front end.
5. Observe Checkout Behavior
The checkout experience can reveal a lot. When you add a product to the cart and proceed to checkout, a Shopify store may redirect to a checkout URL that resembles:
- checkout.shopify.com
- shop.app related flows
- yourdomain.com/checkouts/…
Modern Shopify stores may keep checkout on the merchant’s domain, especially with newer checkout configurations. Still, Shopify-specific wording, payment methods, scripts, and request patterns often appear during the process. You do not need to place an order; simply observing the public checkout page is usually enough.
Some brands use Shopify only for checkout while running the rest of their website on another system. This is especially common with headless commerce setups, where the visible storefront may be built with React, Next.js, or another framework while Shopify handles products, carts, and orders behind the scenes.
6. Use Technology Detection Tools
If you want a faster answer, browser extensions and online scanners can detect common web technologies. Tools such as Wappalyzer, BuiltWith, and similar services analyze scripts, headers, cookies, and page structure to identify platforms. These tools often flag Shopify automatically when enough signals are present.
The benefit is speed: you can get a likely result in seconds. The drawback is accuracy. Detection tools can be outdated, blocked by privacy settings, or fooled by headless implementations. A tool may say “Shopify” because it found a single Shopify script, or it may miss Shopify because the storefront hides most platform traces. Use these tools as a starting point, then verify manually.
7. Check DNS and Domain Clues
Some Shopify stores are connected through DNS records that point to Shopify infrastructure. For example, a domain may use a CNAME record associated with shops.myshopify.com. You can inspect DNS using common lookup tools or command-line utilities.
Another clue is the presence of a hidden or historical myshopify.com subdomain. Every Shopify store has one, such as storename.myshopify.com, even when it uses a custom domain. Sometimes this subdomain appears in page code, emails, redirects, asset references, or older indexed pages.
8. Recognize Theme and App Signatures
Shopify themes and apps can leave recognizable fingerprints. You may see theme names, app proxy paths, or scripts from popular Shopify app providers. Common signs include product review widgets, subscription tools, loyalty apps, upsell popups, or shipping calculators that are widely used in the Shopify ecosystem.
Look for URLs containing /apps/, references to theme sections, or JavaScript objects related to product variants and cart updates. A store using Shopify’s Online Store 2.0 architecture may include section IDs, JSON templates, and theme editor structures. These are more technical clues, but they can be helpful when other indicators are subtle.
Common False Positives and Edge Cases
Not every Shopify reference means the whole site runs on Shopify. A blog, landing page, or brand website might be built on a different content management system while the shop area uses Shopify. Conversely, a Shopify Plus brand may run a highly customized storefront that barely exposes obvious Shopify markers.
Headless commerce creates the most ambiguity. In a headless setup, Shopify may act as the backend while the front end is served by another framework and hosting provider. In that case, you might not see traditional Shopify theme assets, but cart APIs, checkout redirects, cookies, or product data patterns can still reveal the connection.
A Practical Detection Checklist
For the most reliable result, combine several methods rather than relying on one clue. A practical workflow looks like this:
- Search the page source for shopify and cdn.shopify.com.
- Open developer tools and inspect Network requests.
- Review cookies for Shopify-specific names.
- Test public paths such as /cart, /cart.js, and /products.json.
- Observe checkout redirects without completing a purchase.
- Confirm with a technology detection tool.
If three or more of these checks point to Shopify, your conclusion is probably safe. If only one signal appears, describe the result more cautiously: the site may use Shopify for part of its ecommerce stack.
Final Thoughts
Detecting Shopify is a mix of observation, technical inspection, and pattern recognition. The clearest signs are Shopify CDN assets, platform cookies, cart endpoints, checkout behavior, and references inside page source code. While modern storefronts can hide or complicate these signals, a careful review usually reveals enough evidence.
The key is to think like an investigator rather than a guesser. One clue is interesting; several independent clues create confidence. With a browser, developer tools, and a short checklist, you can usually determine whether a website uses Shopify in just a few minutes.
