A business owner walks up to me at a networking event, excited. “We’re building a custom website for the store,” they say. “Full bespoke, built from scratch.”

I smile, and I ask a few questions.

Do you have a development team in-house? No, we’re outsourcing it. Do you have a content strategy that needs more than a standard blog? Not yet — we’re focusing on products for now. Do you have specific technical requirements that a platform like Shopify can’t handle? Well… we just want it to be unique and professional.

Nine times out of ten, the answer is no — they don’t need a custom store. What they need is a well-configured Shopify store, a solid SEO foundation, and their budget spent on marketing rather than bespoke development.

I’m not here to crush anyone’s ambitions. Custom stores are the right call in certain situations — and I’ll be clear about exactly when. But I’ve watched too many businesses sink time and money into custom builds that underperformed a basic Shopify setup, both in rankings and in revenue. So let me give you the honest picture.

Why Shopify Is the Right Starting Point for Most Businesses

Shopify exists because building ecommerce well is genuinely hard. Payments, inventory, checkout flows, mobile performance, SSL, hosting reliability — Shopify handles all of it, reliably, out of the box.

From an SEO perspective, Shopify gives you a solid floor. Fast hosting, automatic sitemaps, canonical tags, mobile-responsive themes — these aren’t exciting, but they’re the foundation that a surprising number of custom builds get wrong. When a custom store is built quickly or on a tight budget, it often launches with technical SEO issues that take months to identify and fix. Shopify doesn’t have that problem.

For a business focused on growing organic traffic — without a dedicated development team — Shopify is not a compromise. It’s the smart choice.

That said, Shopify has a ceiling. And for some businesses, that ceiling becomes a real constraint. Let’s look at where each platform wins.

When to Choose Shopify vs Custom

Business & Operational Fit

Situation	Shopify	Custom Store
Early-stage or growing business	✅ Clear winner	❌ Too slow, too costly
No in-house development team	✅ Built for this	❌ High risk without devs
Need to launch quickly	✅ Days to weeks	❌ Months
Complex, unique business logic	⚠️ Limited	✅ Built for this
Large enterprise with bespoke workflows	⚠️ Possible with Plus	✅ Better fit
Tight budget	✅ Predictable costs	❌ Unpredictable dev costs
Strong in-house or agency dev team	✅ Still works well	✅ Viable

SEO Performance

SEO Factor	Shopify	Custom Store
Core Web Vitals (out of the box)	✅ Good	⚠️ Depends on build quality
Core Web Vitals (maximum potential)	⚠️ Capped by platform overhead	✅ Higher ceiling
URL structure control	⚠️ Partially locked	✅ Full control
Duplicate content risk	⚠️ Built-in (mitigated by canonicals)	✅ Avoidable entirely
Faceted navigation / filters	⚠️ Needs workarounds	✅ Precise control
Schema markup	⚠️ Theme/app dependent	✅ Full control, server-side
Blog and content architecture	⚠️ Limited	✅ Far superior
International SEO (hreflang, structure)	⚠️ Improving but constrained	✅ Full control
Crawl budget management	⚠️ Limited control	✅ Precise control
Maintenance without developers	✅ Handled by platform	❌ Requires ongoing dev input

Cost Reality

Cost Factor	Shopify	Custom Store
Initial build cost	Low–Medium	High
Ongoing platform fees	Predictable subscription	None (but hosting + dev)
App costs (SEO, reviews, etc.)	Adds up over time	Usually built-in or one-off
Developer dependency	Low	High
Hidden costs	App bloat, transaction fees	Maintenance, updates, security

Shopify’s Real Limitations (And How Serious They Are)

I want to be fair here, because pretending Shopify is perfect doesn’t help anyone.

URL structure is partly locked. Every product lives under /products/ and every collection under /collections/. You can’t change this. For most stores this is a non-issue — but for large catalogues where URL architecture meaningfully affects how PageRank flows through the site, it’s a genuine constraint.

Duplicate URLs exist by default. A product accessible via a collection creates two valid URLs. Shopify handles this with canonical tags, so it’s not a disaster — but it’s technical debt you never asked for.

The blog is underwhelming. No real categories, limited internal linking architecture, basic templates. If content marketing is how you plan to win organic traffic, Shopify’s blog will frustrate you within a year.

App bloat is real. Every app you install typically adds JavaScript to your storefront. Add enough of them and your Core Web Vitals scores suffer — and that directly affects rankings. I’ve audited Shopify stores where the app layer alone was responsible for a 20+ point drop in mobile performance scores.

These are real limitations. For most businesses they’re manageable. For some businesses, they’re reasons to go custom. The table above should help you figure out which camp you’re in.

When a Custom Build Is Actually the Right Answer

I said nine out of ten — let me talk about the tenth.

Custom stores make genuine sense when your SEO ambitions are large, your catalogue is complex, and you have the team to maintain what gets built. Specifically:

You need a custom store if you’re building an SEO moat. If organic search is your primary acquisition channel for the next five years — large-scale content, programmatic SEO, tens of thousands of product pages — you will eventually hit Shopify’s ceiling. The URL constraints, the blog limitations, the crawl budget handling — they compound at scale.

You need a custom store if you have genuinely complex requirements. Unusual checkout logic, highly customised product configurators, deep integration with legacy systems. If Shopify’s architecture genuinely can’t accommodate your business model, that’s a real reason to go custom.

You need a custom store if you have the development team to support it. This is the condition most people underestimate. A custom store is only as good as the team maintaining it. Without that, you’re not getting the SEO benefits — you’re just taking on risk.

The Option Worth Considering: Headless Shopify

There’s a middle ground that I think deserves more attention: Shopify as the commerce back-end, with a custom Next.js front-end.

You keep Shopify’s reliability for checkout, payments, and inventory — the parts where it genuinely shines. But your front-end is fully custom, which means full SEO control, better performance potential, and no platform constraints on your content architecture.

It’s not cheap to build. But for businesses that have outgrown traditional Shopify’s SEO ceiling and don’t want to leave the platform entirely, this is often the conversation worth having. You get the best of both worlds — as long as you have the team to build it properly.

My Honest Recommendation

For most businesses reading this — especially if you’re still in growth mode — Shopify is the right platform. It’s fast, reliable, handles the technical fundamentals well, and lets you focus your budget on marketing and content rather than bespoke development. The SEO ceiling is real, but most businesses don’t hit it for years.

Go custom when you have a clear technical reason, a long-term organic SEO strategy that demands it, and the development team to execute and maintain it. Not because you want a unique website. Not because a developer told you it would perform better. Because your specific requirements genuinely can’t be met otherwise.

The most expensive mistake I see isn’t choosing the wrong platform. It’s spending the first year of a business’s life building a custom store when that budget should have gone into SEO, content, and paid acquisition. A beautiful bespoke website that nobody finds isn’t a brand asset — it’s a sunk cost.

Start on the right platform for where you are now. Build toward the platform you’ll need when you get there.

If you’re not sure which side of the line you fall on, jump on a call with me — it’s usually a 30-minute conversation.