SEO and indexing
Configure search metadata, indexing, sitemap, discovery files and machine-readable versions of your managed OrbitPage page.
Last reviewed 15 October 2026Page controls the public identity and search metadata. Publish manages the sitemap and discovery files. Save changes and inspect the public address; search engines and sharing apps decide when to refresh their cached copies.
Set the public identity and address
Use Page to set the name, browser title, search description, favicon and profile image. The public address comes from your workspace username or an active custom domain. Managed accounts do not configure PUBLIC_SITE_URL or server environment variables.
Check metadata and indexing
Saved public content supplies the HTML title, description, canonical URL, social cards and structured data. Check the public page after saving. Indexing controls request that crawlers include or exclude content; they do not make a public URL private or guarantee search placement.
Keep linked destinations and the selected public address consistent. A changed title or image can remain cached by a search engine or messaging service after the page itself updates.
Generate and inspect the sitemap
Open Publish → Sitemap, review the displayed URL and route list, then generate the sitemap. Open that exact public URL to confirm that the expected destinations are present. Recheck after changing a domain, page slug, policy page or publication state; do not assume the preview proves that a hidden destination is public.
Manage discovery files
Publish → TXT edits robots.txt, llms.txt, humans.txt, security.txt and ai.txt, plus up to 20 supported custom text paths. Save and open the displayed endpoint. Reset restores the generated default for a built-in file. Use public descriptions and contact information, not credentials or private notes.
On the shared orbitpage.net domain, the platform's root robots.txt controls host-level crawler rules. Your workspace's robots file becomes host-root policy on its connected custom domain. Changing a text file does not change permissions or protect a page.
Enable machine-readable access
Page → Online presence includes Machine-readable access. When enabled and published, an explicit Accept: text/markdown request can read supported public page representations; generated AI discovery files are also available. When disabled, those generated representations are unavailable. Normal browsers still receive HTML.
This setting publishes a representation of public content, not access to your private editor or account. It does not call an AI provider. Check the public response after saving and use only information you intend to publish.