It depends which part of “the tour” you mean.
Public room and property information should be findable. A proposal prepared for one buyer, a demo, or anything with private pricing should not. One blanket setting for “the tour” hides that difference.
I’d separate the public explanation from the sales experience first, then decide what search should find.
Make the public version useful
The viewer helps someone explore. Readable text on the page explains the room names, the facts, how spaces connect and what to do next.
Don’t assume an embedded 3D viewer gives Google the same information a well-built text page does. Google’s JavaScript SEO basics cover why.
Keep buyer-specific content on its own path
A proposal for one wedding, with three selected spaces and a note from the sales manager, is a different thing from the public ballroom page. It should behave differently too.
Noindex keeps a page out of search results. It doesn’t make a shareable link private. If something truly needs to be restricted, it needs a login or other access control.
In FOH Visual, Deal Rooms are unlisted, noindexed links you can expire or revoke, and the public discovery pages live separately (see it in the live demo).
Check the real thing, not the toggle
Look at which URLs exist, what each one shows, and what Search Console’s URL Inspection tool says about them. A setting labeled “hidden” isn’t proof of anything.
Keeping public and sales pages separate adds a little admin work. It also stops one generic publishing choice from exposing the wrong information or hiding the useful public facts.
Test both routes
Follow a public path from search, then open a link the way a planner would get it from sales. Each should show what it’s meant to show, with a clear next step, and nothing more.
Don’t ask one tour setting to handle discovery, sharing and privacy all at once. Give each job its own design, then go check that it works.
Related: our guide to the Digital Property model, which explains the shared structure behind the public and sales views.
