Publishing, domains and search visibility
Understand hosted slugs, custom domains, metadata, sitemap tools and static public delivery.
Last reviewed 24 July 2026Publishing turns the current workspace into the version visitors receive. OrbitPage separates editing from public delivery so the page stays fast and the dashboard remains private.
Managed pages are published as static snapshots.
After a successful save, OrbitPage renders the page state into HTML and public assets. The active snapshot is stored in Cloudflare R2 and served through the OrbitPage edge worker and cache.
This design keeps ordinary page views away from the editor, Vercel functions and Firestore. Updates replace the active snapshot; they do not install a separate application for every user.
Start with a hosted slug; connect a domain when continuity matters.
Managed pages use orbitpage.net followed by the workspace slug. Supported Pro workspaces can connect a domain they control through DNS validation and Cloudflare custom hostnames.
The owner of an external domain must create the requested DNS records. OrbitPage cannot bypass that verification, even when the page content is already published.
The browser title and description should describe the actual page.
Use a specific browser title, a concise description and a square favicon. Search engines decide how and whether to display metadata, but clear fields reduce ambiguity.
OrbitPage can generate a page sitemap and exposes editable robots.txt and llms.txt content. These files help discovery; they do not guarantee ranking.
Useful content and stable references matter more than a settings checklist.
A one-page site can rank for a name, venue or focused service when it contains identifiable, useful information and earns relevant references. It is not a substitute for a large editorial website with many search intents.
Keep the public page current, use meaningful labels and connect the domain from other verified profiles. Avoid repeating keywords that do not help visitors.
