Off-market property sites that protect discretion

Most off-market agencies do not need fewer pages. They need a site that never exposes an address. The public side sells judgement and access. The private side holds the property itself, behind a link or a login, excluded from search. The enquiry path does the work a listing would normally do.

Why would a discreet agency publish a website at all?

Because the vendor checks you before they call you. A seller who will not allow a portal listing is, by definition, someone worried about what becomes public. The first thing they do is look you up. If what they find is a holding page and a contact form, they have learned nothing about whether you can be trusted with the fact that they are selling.

The site is the credential, not the shop window. It answers three questions a private vendor actually has: who else have you sold for, how do you find buyers without advertising, and what happens to my information once I engage you.

Knight Frank runs this pattern openly through its Private Office pages, which describe a service and a way of working without putting a single private property on the page. That is the shape. The public site argues for the relationship; the property never appears in it.

There is search demand for this, and it is not address demand. People search for private sale, discreet sale, off-market plus a city or a district, and for the agency name plus the service. Those are brand and service queries, and they are winnable with ordinary pages, which is the argument I made in listing pages versus brand pages on agency sites. An off-market agency is simply the extreme case: the brand page is the whole site.

What belongs on the public side?

Your point of view, your people, your process, and proof. No addresses, no interiors that identify a house, no price on a live property.

The point of view is a paragraph, not a manifesto. What kind of property you handle, in which parts of which city, and for whom. Specific beats grand. A sentence naming three districts and one property type tells a vendor more than a page of adjectives.

Your people need real photographs and direct contact details. Discretion is a promise made by a named person, so anonymous team pages work against you. If an agent handles a particular area or language, say so on their page.

Process is where most discreet agencies underperform. Write down what happens after the first call: how you qualify a buyer, what you disclose and when, whether buyers sign an NDA, how viewings are arranged, who else in the office sees the file. A vendor reading that page is deciding whether your handling is disciplined. Give them something to read.

How do you show proof without showing the property?

Describe the transaction, not the house. Typology, district rather than street, price band rather than price, year, and one line on why it was handled privately. A canal-side townhouse in Amsterdam Centrum, sold in 2025 to a buyer from the existing client list, in a price band, without advertising. That is proof, and it identifies nobody.

Photography follows the same rule. A detail shot of a staircase, a window reveal, a garden corner, taken so that no recognisable facade or view appears. If the owner has since moved and has given written consent, you can show more, and you should date the consent in your records. The same production standards apply as anywhere else in this trade, and the resolution and file-size discipline I set out in the piece on photography for design websites applies here without change.

How should the private side be gated?

There are three practical levels, and they differ in how much friction they add and how badly they fail.

An unlisted link is a URL nobody publishes. It is the weakest option. Links leak through forwarded email, browser sync, shared devices and referrer headers. Use it only for material you would tolerate being seen by a stranger, and give it an expiry.

A shared password protecting a small portfolio is the common middle ground. It works if the password rotates on a schedule and per campaign, and if you can revoke it without rebuilding the site.

Per-buyer access is the only version that actually holds. The buyer requests access, you approve, they get a magic link tied to their email address with an expiring token. You can see who opened what and when, and you can switch one person off without affecting anyone else. It costs more to build and it is the right answer for anything above a certain value.

What do search engines see?

Nothing, if you configure it correctly, and the correct configuration surprises people.

A page blocked in robots.txt cannot be crawled, which means Google cannot read the noindex rule on it. Google's own documentation on blocking indexing is explicit that the noindex directive must be crawlable to be obeyed. If someone links to a robots-blocked URL, it can still surface as a bare result. The reliable combination for a gated area is: crawlable, noindex on every private page, no entry in the sitemap, and authentication in front of the content itself.

Then verify it. Log out, open a private window, and request the URL. If you get anything other than a redirect or a challenge, the gate is decoration.

What should never appear in the page source?

An address can escape through a dozen small channels that have nothing to do with the visible text. This is the checklist I run on every private area before it goes live.

Image filenames. A file called herengracht-412-kitchen.jpg is the address, published. Rename on upload to an opaque identifier.

EXIF data. Camera GPS coordinates survive most publishing pipelines. Strip metadata during compression.

Image URLs on a public CDN path. Gating the page does nothing if the photograph sits on an open bucket URL that Google can crawl and anyone can share. Private images must be served through the same authentication as the page.

Open Graph tags and preview images. A private page with an og:image renders a full preview the moment a link is pasted into a chat window.

Structured data. On a public listing I ship RealEstateListing markup with address and price because that is the point. On a private page I ship none of it. The only JSON-LD that belongs there is nothing at all, and the public side carries Organization and Person nodes instead.

Sequential identifiers. If private files live at /p/1, /p/2 and /p/3, one curious visitor sees the whole book. Use random identifiers.

Analytics and CRM exports. A page title containing the address ends up in your analytics interface, your weekly email report and any integration hanging off it. Title private pages by reference code.

How does an enquiry work when nothing is listed?

The enquiry replaces the listing, so it has to qualify before it reveals. In practice that means a short form, then a person, then access.

Keep the form to five fields: budget band, area, timing, whether they are buying with finance or without, and whether an agent already represents them. That is enough to separate a real buyer from a neighbour. Anything longer reads as an interrogation and loses people you want.

Then a human call, and only after that, credentials to the private area. The sequence matters more than the software. Every step should also be visible on the public site, because a vendor reading your process page is reassured by exactly the friction a casual browser finds annoying.

An AI assistant has a real but narrow role here. It can answer questions about the service, areas, timelines and fees, and it can collect and qualify an enquiry at two in the morning. It must not hold private inventory in its context for an unauthenticated visitor, because a model given the file will eventually paraphrase the file. Authenticate first, then let it answer property questions for that buyer only.

What does a site like this take to build?

Four to six weeks for a boutique agency, on the same schedule as any other site in web design for luxury real estate. The gated area adds engineering, not months.

Two rules of thumb I work to. Keep any gallery page under about two megabytes in total transfer, which on a phone abroad keeps you inside two seconds; images at 2000 pixels on the long edge, compressed to WebP, get you there with room to spare. And on the header images for this journal I hold a hard budget of 180 kilobytes each, which is a useful reminder that the constraint is always achievable if you decide it first.

The rest is judgement, and judgement is what the public side is selling. If you want the scoring framework I use when I look at an agency site before rebuilding it, it is written up in how I score a website. For discreet agencies I read the content score hardest. The property is not there to carry the page, so the words have to.