The Problem If you have ever built a site on Sitecore AI, you have probably seen image URLs that look like this: https://edge.sitecorecloud.io/yourcompany1-yourcompanyltd-p49d-fb1a/media/images/HeroBanner.png That works fine while you are prototyping or testing. But when real customers visit your site, a URL that says "sitecorecloud.io" can cause real problems: Your images are not showing up in Google Image search. Sitecore adds an X-Robots-Tag: noindex header to every media request served from the default Edge domain. Search engines see that and skip your assets. It looks unprofessional. Brand teams hate sharing links that point to someone else's domain. Analytics and cookies get messy. Browsers are blocking third-party cookies, and a "shared" domain makes it harder to track your own traffic correctly. You lose domain authority. Search engines don't credit your brand for content hosted on a shared, multi-tenant domain. In this p...
The Problem Let's say your company has one website for the whole world, but inside it there are actually three separate divisions . Each division has its own team, its own products, and its own pages on the same domain. Something like: www.yourcompany.com ├── /clothing/* → the clothing division ├── /sanitation/* → the sanitation division └── /healthcare/* → the healthcare division Now think about how a team would usually build this. One big application for the whole site. Every division team commits into the same codebase, and every small change rebuilds and redeploys the entire site. Fast teams slow down, and the build waits become painful. There is another way to build it, and this tutorial will walk you through it step by step: Vercel Microfrontends , working with a Sitecore AI (headless) setup. Instead of one big app, you build several small apps. Vercel joins them into one website for the visitor. What you will learn How to split one domain into several separ...