Why this is the first question people ask
Most catalog owners already have a website they do not love but cannot risk. It is tied to an agency retainer, or a platform contract, or one person who is the only one who understands it. "Replatform everything" is not a proposal they can say yes to, no matter how good the resulting catalog would be, and no amount of feature list changes that.
How it actually runs
You point one subdomain of your own domain at the catalog. From that moment it serves your catalog while your main site carries on exactly as before, untouched, on whatever it already runs. The two are independent. Your existing site does not know the catalog exists until you add a link in your navigation, which is a one-line change you make when you are ready.
The other way to do it
If you would rather not point any DNS at someone else's server, take the whole site as ordinary files and host it yourself, wherever you already host things. It is plain pages and assets, with nothing to install and nothing running. That option stays open permanently, not just at the start.
The exit
This is the part worth reading twice. If it does not work out, you delete a DNS record and remove one link. Your existing site was never modified, so there is nothing to unwind, no migration to reverse, and no data trapped anywhere, because you can take your catalog out as files at any time. Every account also starts on a private, login-gated staging address kept out of search results, so you can build the whole thing before anyone else sees it. What you get for that low risk is covered in hvce reason crawl index.
Metrics
| Reason Rank | 6 |
|---|---|
| Proof Weight | 3 |
Descriptors
| Buyer Stage | consideration |
|---|---|
| Primary Audience | manufacturer |
| Evidence Type | deployment-arrangement |
| Demo Dataset | early-humans |
| Claim Scope | Runs on a separate address with no change to your existing site; one DNS record, or self-host the exported files |
| Automation Level | one-time-setup |
Frequently asked questions
Do I have to move my website?
No. Nothing about your current site changes. The catalog runs alongside it on a separate address.
Can I use a subdomain of my own domain?
Yes, that is the normal arrangement. You add one DNS record pointing that subdomain at the server, and it needs to resolve directly rather than through a proxy service.
What if I would rather not point DNS at your server?
Export the site as files and host it yourself. Same pages, your infrastructure, no ongoing dependency.
Will this hurt my main site in search?
Adding a new set of indexable, genuinely useful pages on a subdomain does not remove anything from your existing site. What it cannot do is transfer your main domain’s existing authority.
Can I see it before anyone else does?
Yes. Your workspace starts on a private, login-gated staging address that search engines are told to ignore.