Your online shop should be a self-checkout, not a story

Dear eCommerce team,

My SEO expert may hate this one, but I think it is worth saying.

Forget the sprawling eCommerce website for a moment. Forget the mega-menu, the founder story, the blog carousel, the cinematic homepage and the campaign pages piled into the same platform as the checkout.

Imagine the shop is only the transactional bit.

Think of it as a supermarket self-checkout. You know why you came in. You find the thing, pick up an extra or two, pay and leave. Fast, clean and uneventful.

That is a perfectly respectable ambition for an online shop.

The brand can make people care. The shop should make it easy for them to buy.

Separate the jobs

Software companies have worked this way for years. The marketing site explains the product; the application does the work. Each has a different audience, owner and definition of success.

Commerce can be organised the same way:

• www.example.com — the brand, including the story, values and reasons to care
• shop.example.com — the transaction, including products, basket and checkout
• blog.example.com — the content, including education, editorial and search
• get.example.com — the campaigns, with focused landing pages for specific traffic

This does not mean customers should feel as though they are visiting four unrelated businesses. The design, navigation and customer journey still need to feel coherent. It means the machinery underneath no longer has to pretend every job is the same job.

Keep the money bit lean

A brand site may have good reasons to be expressive. Video, motion, campaign tracking and experimental layouts can all earn their place when the objective is attention.

They are less welcome while someone is trying to pay.

The transactional property can be stripped back to what helps the customer:

• Fast product and collection pages
• Useful search and filtering
• Clear availability, delivery and returns information
• A basket that remembers what it is doing
• A short, unsurprising checkout
• Relevant additions without the hard sell

The supermarket does not stop you halfway through payment to play its origin story. It lets you finish.

Use the right tool for each job

An all-in-one platform is convenient until every team is compromising around it.

The content team wants a flexible publishing system. Marketing wants to launch and remove campaign pages without joining a development queue. Commerce needs dependable product data, inventory, promotions and checkout. The brand team wants visual freedom.

Those needs overlap, but they are not identical.

Separating them creates options:

• The shop can use Shopify, Shopify Plus, a headless storefront or another proper commerce engine
• The blog can use WordPress, Ghost, Astro, Sanity or the publishing system the content team can operate well
• The brand site can use a design-led platform without forcing its ideas into a product template
• The landing pages can use a fast, controlled system built for campaigns

The point is not to collect platforms. More moving parts are only useful when they remove more friction than they create. The point is that the checkout should not inherit every compromise made elsewhere.

Make failures smaller

Consider the most irritating version of a monolithic site.

A plugin used by the editorial team breaks after an update. The blog has a problem, which would be annoying enough. But because the blog, storefront and checkout share the same stack, the thing taking money now has a problem too.

Separate properties reduce that blast radius.

If a campaign page fails, the shop can keep trading. If the blog needs emergency maintenance, checkout does not need to know. If engineering changes the basket, the content team can still publish.

The system that makes money is isolated from several of the systems most likely to change.

Keep the secure part small

Payments and customer data deserve a deliberately boring environment.

When the transactional system shares a home with a large CMS and a long list of third-party extensions, there are simply more things to patch, review and reason about. Separating the shop can reduce the attack surface around the sensitive part and make ownership clearer.

It does not remove the need for security, sensible integrations or proper payment architecture. It makes the boundary easier to see.

Give teams clear ground

Combined platforms create combined release queues.

Marketing waits for engineering to publish a landing page. Engineering waits for marketing to approve a checkout change. A harmless content release shares a deployment with revenue-critical code. Everybody becomes responsible for everything, which usually means nobody feels completely responsible for anything.

A separated model can give each team a clearer patch:

• Marketing owns the brand, content and campaign properties
• Engineering owns the transactional experience
• Shared standards protect navigation, brand consistency, analytics and accessibility
• Each property can have a release rhythm appropriate to its risk

That means fewer collisions and fewer Friday afternoons spent discovering that an unrelated change was not unrelated after all.

Yes, there is an SEO argument

The traditional objection is that content on a subdomain may not consolidate authority as neatly as content in a subfolder. There are enough conflicting case studies to keep an SEO meeting occupied indefinitely.

It would be silly to pretend the trade-off does not exist. If organic search is your main acquisition channel, architecture should be agreed with the people responsible for it before anybody starts moving URLs.

But structure is not the only thing search performance depends on. A focused content property can still be fast, coherent, well linked and genuinely useful. A focused shop can give product and category pages more technical attention. A landing-page system can serve campaign intent without turning the main storefront into a cupboard full of old experiments.

The right decision depends on the business. Sometimes the operational and performance benefits justify separate properties. Sometimes the SEO case for keeping content in a subfolder wins. "Separate everything" is no wiser as a rule than "put everything together."

The useful question is: which concerns are currently hurting each other by sharing the same home?

A funnel you can actually read

Separation can also make measurement less muddy.

The brand and blog create awareness. Campaign pages capture a particular intent. The shop closes the sale. Each property has a clearer job and a smaller set of numbers by which it should be judged.

You still need cross-domain measurement to understand the whole journey. But once that is configured properly, the journey becomes easier to describe:

1. Content brought somebody in
2. The brand gave them a reason to care
3. A campaign or product page focused the intent
4. The shop completed the transaction

That is more useful than staring at one enormous traffic total and asking whether the website is "working."

The costs are real

This architecture is not free, and it is not automatically simpler.

You need to handle:

• Cross-domain analytics, so the journey does not become four disconnected reports
• Login, consent and basket behaviour, where state needs to move between properties
• Shared navigation, so customers never feel they have been sent somewhere unexpected
• A design system, so the experience does not drift into four different brands
• Redirects and canonical decisions, especially when existing content is being moved
• More hosting, monitoring and maintenance, because separate systems remain separate things to operate

These are solvable problems. They are still problems, and they belong in the estimate.

Let the shop do the shop's job

We have spent years asking eCommerce sites to be a magazine, a brand film, a corporate brochure, a campaign engine and a shop at the same time.

Sometimes that is the right compromise. Often it is simply the compromise nobody stopped to question.

Let the brand site tell the story. Let the content earn attention. Let campaign pages focus the pitch. Then let the shop help people find what they came for, choose confidently and pay without drama.

Run in. Get the thing. Add an extra. Check out. Done.

If your storefront is carrying several other websites on its back, start with a FREE call. We can work out what should stay together, what should be separated and what is merely in need of a good tidy.