Embedding
One iframe, on the listing page you already have.
The plan renders inside your website rather than sending somebody away from it. There is no script to load, nothing to install, and no framework it has to match.
The snippet
Copy it from the sharing panel in the portal, where the plan id is already filled in.
<iframe
src="https://floorplans.quickcasa.ai/embed/YOUR_PLAN_ID"
title="Floorplan"
width="720"
height="560"
style="border:0;max-width:100%"
loading="lazy"
></iframe>The portal offers three sizes: 480 by 420, 720 by 560, and 960 by 720. The max-width rule is what keeps the frame inside a narrow column on a phone, so keep it whichever size you pick.
Why it is an iframe and not a script
It works where a script tag will not
Plenty of listing platforms and website builders allow an iframe and block scripts outright. An embed that needs JavaScript from another domain is an embed half your clients cannot use.
It cannot touch your page
A frame has no access to the page around it. Nothing we ship can read your forms, change your layout or slow down your own JavaScript, and you do not have to take that on trust.
Nothing to keep up to date
There is no version of the embed pinned into your website. Improvements to the viewer arrive in the frame without anybody editing the listing page.
It loads when it is needed
The snippet is marked lazy, so a plan low down a long listing page does not cost anything until somebody scrolls to it.
What is different inside a frame
The embedded view is the same viewer with the page chrome taken off. There is no header and no branding bar, because the page it is sitting in already has yours, and a second one inside the frame reads as a mistake.
The comment box is dropped. A frame on a listing page is somewhere to look at a plan and pass it on, not somewhere to hold a conversation, and a comment form in a box a few hundred pixels wide is a bad form.
The share button stays, and it points at the plan on its own page rather than at the frame. What gets passed on should be something to open, not something to embed again.
There is a link in the corner out to the full page, so anybody who wants the room detail, the area breakdown and the comments can get there in one tap.
Gated plans do not put their gate in your page
A plan behind a passcode or an unlock form will not render that gate inside a frame on somebody else's website. It shows a line saying the plan opens on its own page, and links there.
This is deliberate and it is not a limitation we intend to remove. A form asking for a passcode, inside a frame, on a domain that is not the one the passcode belongs to, is indistinguishable from a phishing widget. Worse, it teaches renters that typing a code into an unfamiliar embedded box is a normal thing to do. On its own page the address bar is visible and the request is honest.
If you want a plan embedded, make it public. If it needs a gate, embed a link to it instead.
Turning embedding off
Embedding is a setting on the plan. With it off, the embed address answers with a short line saying so and a link to the readable page, whoever built the frame and wherever it is.
The check runs on the plan itself rather than on the page that framed it, so switching it off works retroactively against embeds that already exist.
Put a plan in front of your next renter.
Floorplans are part of QuickCasa, so the drawing, the listing and the lead it brings in all live in one place. Book a demo and we will show you what it looks like with your own properties.