Orbit builds app pages on the server, so a search crawler can read the page content rather than an empty shell.
The server supplies the page content
Server rendering means the server prepares the page's HTML before the browser displays it. A crawler can read that content without first performing the actions of a person in the app.
Orbit's product overview describes this as a crawler reading the real page. Server rendering helps expose the content you put on a public page. It does not write that content for you.
For example, a repair business can have a public page that describes its services and service area. Those details answer a visitor's question before the visitor submits a request. The business name and service area are example content, not built-in fields.
A readable page does not guarantee search placement
Server rendering and search placement are different results. A crawler's ability to read the page does not guarantee that a search engine indexes it or ranks it for a particular question.
For the repair business, a page that says only “Welcome” does not explain which repairs the business offers. Put the service details on the page itself. Do not rely on the visitor to open a form to learn what the business does.
Public content and private records have different jobs
The repair business's service page is public information. A customer's repair request can contain private contact details.
Server rendering describes how Orbit produces a page. It is not a rule that grants or restricts access to customer records. Decide who can read each private page and record, then test those rules separately.
Authentication explains why sign-in and permission to read a record are different checks.
Check the page that visitors receive
Open the public page without an account. Confirm that the service details appear and that the links lead to the intended pages.
Then test the customer request flow with separate accounts. Public service content must not depend on access to private customer records.
Use Review an app before launch for the main task, saved data, and access checks. These tests check the reader's experience, not whether a search engine has indexed the page.