Before embedding a tour, confirm the platform allows embedding and the intended sharing settings are active. Plan layout, loading and a fallback link, then test the visitor journey on the actual website.
Use a public viewer link
Ask for the approved viewer URL and the platform’s embedding instructions. Administrative URLs, editing links and preview tokens should not become public embeds. Open the share link while signed out to check the intended scene, then confirm any password, domain or embedding restrictions required by the project.
Give the viewer a stable frame
An iframe embeds another page and consumes additional browser resources. A single main viewer with a project selector can avoid loading many large tours together. Reserve a stable viewing area, give it a meaningful title and show a cover or instruction before loading so visitors understand what will appear.
Source:MDN — iframe ↗
Test the interaction boundary
On phones, a finger may need to scroll the page or rotate the scene. Make entry into the viewer clear, and test portrait and landscape use, returning to the page, zooming and any supported fullscreen action. Check that the site’s own navigation does not cover essential controls inside the tour.
Provide a fallback route
Keep the project name, description and a link to open the original viewer available if the embed fails. A blank frame should not be the only content. Coordinate required browser permissions and embedding policies with the platform instead of broadly disabling website protections to resolve one compatibility issue.
Document ownership and maintenance
Record the viewer URL, embedding pages, responsible contacts and hosting term. Assign someone to check these entry points when a scene is replaced, disabled or moved to another subscription. Measuring actions inside an external viewer requires supported interfaces; clicking an open button alone does not prove that the scene loaded successfully.
A quick commissioning checklist
- Can a signed-out visitor open the intended public scene?
- Can phone users interact and return to the website?
- Is there a useful original-viewer link if embedding fails?