# Publication and version selection

> Promote a reviewed artifact to the managed site address and distinguish publication from preview, GitHub delivery, and data migration.

[Canonical page](https://rogueon.ai/docs/publishing)

## A public address points to a selected version

Completing a site build produces a versioned preview. Publish selects that version for the conversation's managed public address. A subsequent build does not ordinarily replace the live artifact until you publish again. Record the tested version before promotion so a later preview is not mistaken for the release candidate.

This operation changes which artifact the address serves. It is not a database migration, a transfer of provider accounts, or a GitHub push. Those states need their own verification when a release changes more than frontend files.

## Publish a reviewed version

1. **Select the ready artifact**

   Open the original site conversation with owner access. Confirm that generation is complete and that the displayed preview is the version you tested.

2. **Execute Publish**

   Use Publish and wait for the success state and returned address. A disabled control or error is not a completed deployment.

3. **Verify the destination**

   Copy the public link, open it separately, and check the critical flow, assets, authentication, and service calls that apply to this project.

## Coordinate revisions and repository delivery

Keep a distinction between the latest preview, the selected public version, and the latest GitHub commit. The GitHub integration can create commits for subsequent completed changes after the conversation is linked; that does not publish those changes at the site address.

If the site appears unchanged, check the public address and selected version before starting another build. If you use Undo, read its confirmation: reverting an artifact can affect the public version, but does not reverse database mutations or external side effects.

## Sharing a link and appearing in search

Rogue-managed site addresses currently return the HTTP header X-Robots-Tag: noindex. They are intended for reviewing and sharing the selected web artifact, not for search indexing. A title, description, or social card does not override that header. Anyone with the public link can still open the site: noindex is not access control.

If search discovery is a project requirement, export the code and configure a separate hosting destination you control. Review the files for private information, establish required runtime services, and verify indexable responses at that destination before submitting its sitemap. Export does not guarantee indexing or transfer backend services automatically.

- [Export and configure the destination](https://rogueon.ai/docs/exporting#search-ready-hosting)

## Deployment boundaries

Managed publication includes hosting for the web artifact. Custom domains are not supported through this product workflow yet. Sites output runs in a browser; this is not an .apk or .ipa build or an App Store/Play Store submission workflow. Slides use a separate delivery path.

Publication requires owner context. If the app asks for the original browser or conversation, restore that context rather than clearing browser storage. For network or temporary service errors, retry publication after checking the status; avoid regenerating a correct artifact solely to retry delivery.

## Related guides

- [Preview and runtime validation](https://rogueon.ai/docs/preview-and-testing)
- [Export and external development](https://rogueon.ai/docs/exporting)
- [Runtime diagnostics](https://rogueon.ai/docs/troubleshooting)