Why do HTMLvault links serve from a separate domain instead of htmlvault.com?

Serving user published content from the application origin would let published pages share cookies, storage, and domain reputation with the app itself. HTMLvault deliberately serves published pages from dedicated delivery domains so sign-in sessions never exist next to user content, link reputation stays separate from the corporate domain, and published pages stay out of search engines. This split is a standard isolation practice for platforms that host user content.

Are pages published with HTMLvault indexed by search engines?

No. Every HTMLvault delivery domain serves a robots policy that blocks crawling of link paths, so published pages are never indexed. Only each delivery domain’s home page is crawlable, which is how search engines can describe the domain without reading any published content.

Domains

Q: What is htmlvault.io?

htmlvault.io is the active, default link delivery domain for HTMLvault. Every new page published with HTMLvault that is not pinned to a branded subdomain or a custom domain goes live at a short htmlvault.io link. It is current infrastructure, not a legacy domain, and nothing has migrated away from it: accounts and dashboards simply live on htmlvault.com while published content serves from htmlvault.io.

Q: What is hvlt.io?

hvlt.io is the parent domain for branded HTMLvault subdomains. Teams on paid plans claim a subdomain such as yourteam.hvlt.io and deliver their published links from it. Like htmlvault.io, it is active HTMLvault infrastructure serving pages published today.

HTMLvault is one product spread across deliberately separated domains: htmlvault.com runs the application, htmlvault.io delivers published links, and hvlt.io hosts branded team subdomains. This page explains what each domain does and why the separation exists.

One product, three domains

Domain	Role
`htmlvault.com`	The application and website. Accounts, dashboards, link analytics, documentation, and billing all live here.
`htmlvault.io`	Default link delivery. Every new published page that is not pinned to a branded subdomain or custom domain serves from a short link here.
`hvlt.io`	Branded subdomains. Teams on paid plans deliver links from a personal subdomain such as yourteam.hvlt.io.
`Your own domain`	White label delivery. Paid plans can serve links from a custom domain such as links.acme.com, with no HTMLvault branding.

What is htmlvault.io?

htmlvault.io is the active, default delivery domain for pages published with HTMLvault. When a user publishes a page and has not pinned it to a branded subdomain or a custom domain, it goes live at htmlvault.io followed by a ten character slug, for example htmlvault.io/a1b2c3d4e5.

htmlvault.io is not a legacy domain, and the product has not moved away from it. It is the current home of every new default link. The two domains split responsibilities on purpose: htmlvault.com runs the application, htmlvault.io serves published content.

What is hvlt.io?

hvlt.io is the parent domain for branded HTMLvault subdomains. Accounts on paid plans can claim a subdomain such as yourteam.hvlt.io and deliver their published links from it, so recipients see the team name in every URL. Each subdomain belongs to a single HTMLvault account.

Like htmlvault.io, hvlt.io is active HTMLvault infrastructure serving pages published today. The apex domain itself hosts nothing but an explainer page; all delivery happens on the subdomains.

Why links serve from a separate domain

Serving user published content from the same origin as the application would let published pages share cookies, browser storage, and domain reputation with the app itself. HTMLvault deliberately serves published pages from dedicated delivery domains instead:

Session isolation. Sign-in sessions for htmlvault.com never exist on the delivery domains, so a published page can render its own scripts without ever executing next to an account session.
Reputation isolation. Reputation for user published content is kept apart from the corporate domain that account security and company email depend on.
Crawl isolation. Published pages are excluded from search engine crawling on the delivery domains, so shared content stays out of search results.

This split is a standard isolation practice for platforms that serve user content on the web, and it is part of the security model described on the security page.

Serving links from your own domain

Paid plans can go a step further than the branded subdomain and serve links from a fully white labeled custom domain, for example links.acme.com, with no HTMLvault branding on the page. Domains are added and verified from the domain settings screen; see pricing for what each tier includes.

Search engines and published pages

Published pages are never crawlable on HTMLvault delivery domains. htmlvault.io, every hvlt.io subdomain, and white label custom domains all serve a robots policy that blocks link paths, so a page you share through HTMLvault does not end up in search results. Only the home page of htmlvault.io and hvlt.io is crawlable, which is how search engines can describe these domains without reading any published content.