| 1
Teardowns

Shopify Competitor Analysis: Everything You Can See From Outside

You can see a competitor's app stack, theme, offers and page speed from outside their store, in about twenty minutes, for nothing. The trap is copying what you find.

Gabriel RuimyCofounder, Qosmic ·
An app stack read from page source, with the "what it tells you / what it doesn't" split

Almost everything about a competitor's Shopify store is public. Their app stack, their theme, their product catalog, their prices, their offers, their page speed, roughly what they rank for. None of it requires anything clever, and most of it takes about twenty minutes.

The hard part isn't gathering it. It's not drawing stupid conclusions from it.

Their app stack

Every Shopify app that touches the storefront leaves evidence in the page source. Scripts, class names, injected divs.

You can read this by hand. View source, then search for apps.shopify, cdn.shopify.com/extensions, or the names of apps you already recognize. Or use one of the free app-detector tools that does it for you. Several exist and they all work roughly the same way.

What it's actually good for: seeing which problems a competitor decided were worth paying to solve. If three stores in your category all run the same reviews app and the same bundle app, that's a signal about what matters in your category. If a competitor you respect runs no upsell app at all, that's also a signal.

What it isn't good for: a shopping list. An app stack tells you what somebody bought, not whether it worked. Plenty of stores are carrying four apps they installed in 2023 and forgot about, which is the exact problem the app bloat post is about. You're as likely to be copying somebody's mistake as their strategy.

Worth checking the count too. A competitor running fifteen storefront apps is carrying the same weight problem everyone else is, and that's an opportunity rather than a thing to match.

Your product page measured against a competitor's on the same bars

Their theme and structure

The theme name is usually in the page source. More useful than the name is the structure.

Their product page layout. Where does the price sit? Is there a sticky add-to-cart? How far down is the buying block? These are measurable, and we measured four well-known stores to show what that looks like. Do the same to a competitor and you have a direct comparison on the page that decides the sale.

Their navigation depth. How many taps from home to a product? What did they choose to put in the top-level menu, and what did they bury?

Their collection page structure. Filters, sort options, whether there's real copy on the page or just a grid.

Their cart. Drawer or page, express wallets, whether shipping cost appears before checkout.

This is the highest-value part of the exercise and the part almost nobody does, because it requires opening the site on a phone and paying attention rather than running a tool.

[@portabletext/react] Unknown block type "ctaBox", specify a component for it in the `components.types` prop

Their prices and offers

Shopify exposes a store's catalog as JSON at /products.json on most stores. That gives you product titles, variants, prices and publication dates without touching anything private. Add ?limit=250 and you have their whole catalog in one request.

That tells you their price ladder, how many SKUs they run, what they've launched recently, and what they've quietly stopped selling.

Their free shipping threshold is visible in the cart. Their discount strategy is visible in the announcement bar and the popup that fires at you. Their subscription offer, if any, is on the product page.

Their launch cadence is worth more than any single price. A competitor shipping two products a month is running a different business from one shipping two a year, and that shapes what you should be worried about.

Their traffic and keywords

This is the part that needs a paid tool, and it's the part where the numbers are estimates rather than facts.

Ahrefs, Semrush or similar will show you roughly which terms a competitor ranks for, which pages earn their organic traffic, and who links to them. Treat the traffic numbers as directional. Treat the keyword list as the useful output, because that's a list of things people search for in your category that somebody has already validated.

The single most useful view is their top pages by organic traffic. It tells you what content actually works in your market, as opposed to what content agencies say works.

Copy the constraint, not the tactic

What to do with all of it

Here's where competitor analysis usually goes wrong.

Don't copy the tactic. Copy the constraint they solved. If a competitor added a size guide to every product page, the insight isn't "add a size guide." It's "sizing is a blocking question in this category," which might be better solved on your store a different way.

Benchmark against your segment, not the leader. The biggest store in your category has brand demand you don't have. Their 4% conversion rate is not a target you can reach by copying their layout, and their average order value reflects a customer base that already trusts them.

Use it to find your gap, not their playbook. The most valuable finding is usually something they all do that you don't, or something none of them do that a buyer clearly wants.

Re-check quarterly. Store fronts drift. An app stack from six months ago is fiction.

This is a job that suits software better than a person, which is where we come in, so weigh it accordingly. Qosmic benchmarks your storefront against competitors in your segment as part of its checks, so a gap on your product pages shows up as a ranked finding with what it's costing you rather than as a browser tab you meant to get back to. You can do all of the above by hand with a free app detector, /products.json and an hour. Plenty of good operators do. The difference is whether it happens again next quarter.

[@portabletext/react] Unknown block type "ctaBox", specify a component for it in the `components.types` prop

The short version

A competitor's apps, theme, structure, catalog, prices and offers are all public. Twenty minutes and no budget.

The app stack tells you what they paid to fix, not what worked. Don't treat it as a shopping list.

/products.json gives you their entire catalog and price ladder in one request.

Their organic keyword list is worth more than their traffic estimate, because it's a validated list of what your market searches for.

And benchmark against your segment rather than the category leader, whose numbers reflect brand demand you can't copy.

Grow your store with one click.