Identifying whether a website is built on Shopify is often useful for ecommerce research, technical audits, competitive analysis, migration planning, and fraud prevention reviews. The most reliable detection methods combine visible HTML clues with deeper inspection of theme files, scripts, assets, and platform-specific URL patterns. A serious approach should avoid guessing from appearance alone and should instead rely on repeatable evidence found in the page source and related files.
TLDR: The best way to detect a Shopify ecommerce site is to inspect the HTML source for Shopify-specific scripts, asset URLs, meta tags, and checkout patterns. Theme files and asset paths often reveal references to Shopify’s CDN, Liquid-generated variables, and storefront features. No single clue is perfect, so trustworthy detection should combine several indicators before reaching a conclusion. Manual inspection is effective, but automated scanners can improve consistency when used carefully.
Why Shopify Detection Matters
Shopify is one of the most widely used ecommerce platforms, so identifying it accurately can support a variety of practical tasks. Developers may need to determine whether a client’s existing store can be migrated or integrated with third-party tools. Analysts may want to understand ecommerce technology adoption across competitors. Security professionals may need to assess platform-specific exposure without performing intrusive testing.
However, detection should be handled responsibly. A website’s platform is not an invitation to probe private systems, bypass protections, or scrape restricted information. The methods discussed here rely on publicly accessible HTML, JavaScript, CSS, and theme-related assets that are ordinarily delivered to any visitor’s browser.
Start With the Page Source
The simplest and most dependable first step is to inspect the page source. In most browsers, this can be done by right-clicking on the page and selecting View Page Source, or by using developer tools. Once inside the HTML, search for terms commonly associated with Shopify.
Useful search terms include:
- shopify
- cdn.shopify.com
- Shopify.theme
- ShopifyAnalytics
- myshopify.com
- cart.js
- routes.root_url
If multiple terms appear in the source, there is a strong chance the store is running on Shopify. For example, Shopify storefronts commonly load assets from cdn.shopify.com, including theme JavaScript files, CSS files, images, fonts, and product media. A single CDN reference may not be conclusive because external apps or embedded widgets can also use Shopify resources, but repeated references across theme assets are meaningful.
Look for Shopify CDN Asset URLs
One of the strongest indicators is the presence of Shopify-hosted asset URLs. Shopify themes often reference files such as CSS, JavaScript, and images through URLs that include cdn.shopify.com. These URLs may contain paths like:
- /s/files/
- /t/ followed by theme-related asset paths
- assets/theme.css
- assets/theme.js
- products/ or collections/ media paths
This is valuable because most Shopify stores use Shopify’s CDN to deliver theme files and product images. Even when a store has a custom domain and a heavily customized design, the asset delivery layer often reveals the platform underneath.
To verify the finding, inspect several pages, not just the homepage. Product pages, collection pages, search pages, and cart pages may expose additional Shopify-specific asset references. A homepage can be highly customized, but deeper commerce pages are more likely to include standard Shopify structures.
Inspect JavaScript Objects and Variables
Shopify storefronts frequently expose platform-related JavaScript objects in the page source or browser console. These may include analytics, theme configuration, localization data, and cart behavior. Common examples include Shopify, ShopifyAnalytics, and Shopify.theme.
When reviewing scripts, look for code patterns such as:
- window.Shopify or var Shopify
- Shopify.shop
- Shopify.currency
- Shopify.locale
- Shopify.theme =
- ShopifyAnalytics.meta
These variables are not always visible on every store, and some may be minimized, removed, or altered by performance tools. Nevertheless, their presence is a strong signal. For a serious detection workflow, treat JavaScript objects as supporting evidence rather than the only proof.
Check Common Shopify URL Patterns
Shopify uses recognizable URL patterns for common ecommerce functions. These often remain available even when the theme design is customized. Try reviewing public paths such as:
- /cart
- /cart.js
- /products/product-name
- /collections/collection-name
- /collections/all
- /search
- /pages/page-name
The /cart.js endpoint is especially useful because Shopify stores commonly expose cart data in JSON format through this public route. If visiting the path returns a JSON response with cart fields such as token, item count, total price, or items, that is a significant platform indicator.
Still, URL patterns should be interpreted carefully. Some non-Shopify websites imitate Shopify-like structures for SEO or migration reasons. Also, headless Shopify implementations may use custom frontend routing while still relying on Shopify in the background. In those cases, HTML and API evidence may be less obvious.
Review Theme File Names and Asset Structure
Theme files are among the best sources for reliable detection. Shopify themes are built with Liquid templates and usually generate predictable asset references. While you cannot access private theme source files directly, publicly loaded compiled assets often retain informative filenames and paths.
Look for theme-related files such as:
- theme.css
- theme.js
- base.css
- global.js
- product-form.js
- cart-notification.js
- predictive-search.js
- section-main-product.css
Modern Shopify themes, particularly those based on Online Store 2.0 structures, often include files associated with sections, blocks, product forms, cart drawers, and predictive search. A filename alone is not proof, but filenames combined with Shopify CDN paths and JavaScript variables create a strong conclusion.
Search for Liquid-Generated Clues
Shopify themes use Liquid, a template language that renders dynamic store content into static HTML for the visitor. The Liquid code itself is generally not visible after rendering, but the output often includes recognizable patterns.
Examples of Liquid-generated clues may include:
- Structured product data inserted into scripts
- Theme settings rendered into JSON objects
- Section identifiers and data attributes
- Variant IDs embedded in product forms
- Localization and currency configuration
You may see elements with attributes such as data-section-id, data-section-type, data-product-id, or data-variant-id. These attributes can appear on other platforms as well, but Shopify themes often use them in combination with product forms, cart scripts, and section-based JavaScript.
Analyze Product Forms
Product pages are particularly revealing. Shopify product forms usually submit to /cart/add and include hidden inputs for variant IDs. Inspect the HTML around the add-to-cart button and product options. You may find a form similar in structure to:
- A form action pointing to /cart/add
- A hidden input named id containing a variant ID
- Quantity inputs named quantity
- Product option selectors linked to variant data
This pattern is one of the most practical detection methods because it reflects how Shopify handles products and variants. Even if the store’s visual design is unique, the commerce workflow may still show Shopify’s underlying form behavior.
Inspect Checkout and Payment Indicators
Checkout behavior can also reveal Shopify, but it should be examined cautiously and without interfering with transactions. Many Shopify stores move checkout to a Shopify-controlled environment, often involving URLs or redirects associated with checkout infrastructure. Historical patterns may include references to myshopify.com or Shopify checkout scripts.
Because checkout pages can involve sensitive customer data and payment processes, avoid testing beyond normal public browsing. Do not submit personal information, automate checkout attempts, or attempt to bypass protections. For platform detection, publicly visible redirect patterns and source references are usually sufficient.
Use Browser Developer Tools
Browser developer tools provide a structured way to confirm findings. The Network tab is especially useful because it shows every asset, script, image, and API request loaded by the page. Filter the requests for terms such as shopify, cdn.shopify.com, cart, and products.
Developer tools can help you answer important questions:
- Are CSS and JavaScript files loaded from Shopify’s CDN?
- Does the site call /cart.js or related cart endpoints?
- Are product images served through Shopify file paths?
- Are Shopify analytics scripts present?
- Do theme assets include recognizable Shopify theme filenames?
This method is more dependable than looking at the visible design because themes can be customized extensively. The network layer often reveals details that the user interface hides.
Consider Headless Shopify Stores
Not every Shopify-powered store uses a traditional Shopify theme. Some brands use headless commerce, where Shopify manages products, inventory, and checkout while a separate frontend framework handles the website. These stores may not show common theme files or obvious Liquid output.
For headless implementations, detection may rely on different signs, such as references to Shopify Storefront API, product data structures, checkout creation calls, or Shopify-hosted media. You might see GraphQL requests, storefront access patterns, or product images delivered from Shopify’s CDN. Headless stores can be harder to confirm, so it is important to avoid overconfidence when only limited clues are available.
A Reliable Detection Checklist
For trustworthy results, use a checklist rather than a single indicator. A site is very likely using Shopify if several of the following are present:
- Multiple assets loaded from cdn.shopify.com.
- Shopify JavaScript objects such as ShopifyAnalytics or Shopify.theme.
- Cart endpoints such as /cart, /cart.js, or /cart/add.
- Product page forms using Shopify-style variant IDs.
- Theme asset names commonly associated with Shopify themes.
- Product images hosted through Shopify CDN paths.
- Checkout behavior consistent with Shopify infrastructure.
If only one signal is present, label the result as possible. If three or more independent signals are present, the result can usually be considered high confidence. This distinction is important for professional reporting.
Common Mistakes to Avoid
A serious detection process must account for false positives and false negatives. A website may include Shopify scripts because it embeds a Shopify buy button, while the main store runs on another platform. Conversely, a Shopify Plus or headless implementation may hide many ordinary Shopify clues.
Avoid these mistakes:
- Assuming a site is Shopify only because it looks like a typical ecommerce theme.
- Relying on one script, one image URL, or one suspicious keyword.
- Ignoring subdomains, because the storefront and checkout may use different hosts.
- Failing to inspect product and cart pages, which often reveal more than the homepage.
- Confusing third-party app assets with the core ecommerce platform.
Manual Detection Versus Automated Tools
Automated technology profilers can identify Shopify quickly, especially when analyzing many websites. However, they are not perfect. They may rely on cached signatures, outdated patterns, or incomplete page loads. Manual review remains valuable when accuracy matters, particularly for audits, research reports, or migration planning.
The best approach is often a hybrid one: use automated tools for initial screening, then validate important findings manually through HTML inspection, network analysis, and theme asset review. This produces more defensible conclusions and reduces the risk of misclassification.
Conclusion
The best Shopify ecommerce platform detection methods are grounded in observable technical evidence. HTML source code, Shopify CDN asset paths, JavaScript variables, cart endpoints, product forms, and theme file structures all provide meaningful clues. None of these signals should be treated as absolute proof in isolation, but together they can establish a highly reliable conclusion.
For professional use, document the specific evidence found and assign a confidence level based on the number and quality of indicators. Shopify detection is most trustworthy when it is careful, repeatable, and respectful of public boundaries. By combining HTML inspection with theme file analysis, you can identify Shopify stores with accuracy while maintaining a serious and responsible methodology.
