Property developers, NZ and AU

Websites for property developers selling something that doesn't exist yet

A property developer's website has a different job to a builder's. You are selling a building that doesn't exist, to two audiences: buyers who need proof you finish things, and landowners or capital partners who need proof you can fund them. It needs a pipeline that stays accurate week to week, a delivered-projects register, and disclosure a buyer's lawyer can read.

Stock, by stage

  1. Releasing6 lots
  2. Selling11 lots
  3. Under construction24 lots
  4. Sold out0 lots
  5. Completed3 lots

A buyer asks one question first: is there any left. Answer it above the fold or they email to find out.

Why doesn't a builder's website work for a property developer?

Because a builder sells finished work and you sell a drawing. A builder's site is a photo gallery with a contact form. Yours has to carry stock that changes weekly, stages that release on dates, disclosure a solicitor will read, and a delivered-projects record that proves you finish what you start. Different content, different structure, different job.

The gap is not cosmetic. A builder's visitor is looking at a kitchen that exists and deciding whether they like it. Your visitor is looking at a render and deciding whether to believe you. Everything downstream changes: the photo gallery becomes a delivered register, the services list becomes a stage pipeline, the single contact form becomes two, and a whole layer of per-project disclosure appears that a trade site has no equivalent of.

If you build one-off custom homes as well as multi-unit or land developments, the pipeline structure on this page is what carries the development side of the business, and the two do not have to fight each other on one site.

What actually goes on a property developer's website?

Six things, and only one of them appears on a trade website: a stage-split project pipeline, a page per development with its own consent status and completion window, a delivered-projects register, per-project disclosure, body corporate detail with an indicative levy, and two separate enquiry paths rather than one.

A stage-split project pipeline

Developers work project to project, not location to location. Each development has its own price bracket, title type and completion date, so each page is genuinely different content, not the same page with a suburb swapped.

A page per development, with consent status and a completion window

This is the first thing a buyer's solicitor looks for, and the field most likely to be out of date on a static site.

A delivered-projects register

Name, suburb, unit or lot count, completion date. The dominant pre-contact question is whether you've actually finished things, on time, and a render can't answer it.

Per-project disclosure, dated

Unit title disclosure in New Zealand and off-the-plan disclosure in each Australian state are per-project obligations, not a page in the footer.

Body corporate structure with an indicative levy

Unique to multi-unit and unit-title stock. A single-dwelling builder's site has no such field, which is exactly why a builder template can't be reused here.

Two enquiry paths, not one

A buyer and a landowner or capital partner are asking for different things, and a single form reads the higher-value enquiry like the lower-value one.

How should the project pipeline be structured?

As five states, not one portfolio page: releasing soon, selling now, under construction, sold out, completed. Each development moves between them on its own page, and none of them get deleted. A sold-out project isn't dead content, it's the proof the next buyer needs, and deleting it throws away the page's search history too.

  1. 1

    Releasing soon

    A waitlist and an expression-of-interest form, not a buy button. This is the stage that justifies a page live inside a week rather than a rebuild.

  2. 2

    Selling now

    Price bracket, remaining count, floor plans, consent status, completion window, disclosure pack, enquiry form. The page that has to be right every day.

  3. 3

    Under construction

    Progress updates with dates. Off-the-plan and subdivision sales run months to years from launch to settlement, and a site that can't be updated weekly can't carry a nurture cycle that long.

  4. 4

    Sold out

    The page stays. State changes, content stays, the URL stays, and it keeps working as proof for the next release.

  5. 5

    Completed

    As-built photographs replace renders, the completion date goes on, and the project joins the delivered register. The same URL now works as proof for the next launch.

What does an off-the-plan buyer check before they enquire?

The projected completion date and what happens if it slips, the disclosure statement, whether a LIM has been obtained in New Zealand, consent status, who is actually building it, and the body corporate levy. If your site answers none of these, the first call is spent answering all of them.

Completion date and sunset terms

In New South Wales a disclosure statement must be attached to the contract with the sunset date stated, and a developer needs the buyer's agreement or a NSW Supreme Court order to rescind under a sunset clause. In Queensland, since the reforms of 22 November 2023, sunset-clause termination needs the buyer's written consent or a court order, and settlement is capped at 18 months.

The disclosure statement itself

Whether the plan has changed since marketing began is exactly what a buyer's lawyer checks first, and in Queensland a change that materially prejudices the buyer gives a 30-day exit right.

A LIM, in New Zealand

A Land Information Memorandum is the standard council due-diligence document, covering consents, zoning, hazards and rates. Stating on the project page that a LIM has been obtained removes a question before it's asked.

Consent status

Named plainly, not implied by a render that looks finished.

Who builds it, and what warranty applies

A buyer who can't find the contractor's name on the site assumes it isn't settled.

An indicative body corporate levy

Published as a figure, stated plainly as indicative.

Do New Zealand, NSW and Queensland need different pages?

Yes, if you sell in more than one of them. Off-the-plan disclosure is set at state level in Australia and has diverged, and New Zealand's unit title regime is different again. One national compliance page will be wrong somewhere. The site's job is not to give legal advice, it's to publish what your solicitor confirms, per project, with a visible date on it.

What a property developer's website needs to surface per project, by market, and the government source for each.
MarketWhat the site has to surfaceGovernment source
New Zealand (unit title)Pre-purchase disclosure for off-the-plan units under the Unit Titles Act 2010 as amended, whose final provisions commenced 9 May 2024; body corporate structure; confirmation a LIM has been obtained.Ministry of Housing and Urban Development, and Unit Titles Services (MBIE)
New South WalesA disclosure statement attached to the contract with the sunset date stated, a 10 business day cooling-off period, the deposit held in trust, and rescission under a sunset clause only with the buyer's agreement or a NSW Supreme Court order.NSW Government, buying property off the plan
QueenslandSeller disclosure of the proposed lot number and area; sunset-clause termination only with the buyer's written consent or a court order since 22 November 2023; an 18-month settlement limit under the Land Sales Act 1984; a 30-day exit right where a change materially prejudices the buyer.Queensland Government, buying off the plan

Want to know what this looks like for your business? Fifteen minutes is usually enough to tell you.

Book a 15-minute callSend us a message instead

How do you keep landowner enquiries separate from buyer enquiries?

Two doors, two forms. A buyer wants a price bracket, a floor plan and a completion date. A landowner or capital partner wants site area, zoning, your delivery record and who to call. Put both through one contact form and the higher-value enquiry arrives with none of the information you need, and gets read like a buyer enquiry.

Door one

Buyers and investors

Asks bedrooms or lot size, budget bracket, timing, finance status, owner-occupier or investor. Suited to the sales agent's queue.

Door two

Landowners, joint-venture and capital partners

Asks site address, land area, current zoning, title type, and what they're proposing. This is the door most developer sites don't have. Land is brokered through relationships with owners, agents and planning consultants long before a development is public, and the person arriving with a site to offer isn't going to fill in a form asking how many bedrooms they want.

Why does a developer's website go stale faster than any other?

Because your stock changes and a trade's doesn't. An accountant's services page is true for years. Your availability is wrong the week after a release. Stage two prices, remaining lots, the completion window, a render that no longer matches consent: all of it moves. A site you have to email someone to change is publicly wrong most of the time.

This is the part of the product that matters most to this sector. You change it by asking. 'Mark stage two sold out.' Done, on the pipeline, the project page, the enquiry form and the homepage counter. 'Move Kingsland completion to Q3 2027.' Changed everywhere it appears, including the disclosure line and the progress page. 'Add the as-built photos to Northcote and move it to completed.' Done, and the project joins the delivered register.

No ticket, and no waiting on a web developer.

Figure 1

What the page still says

RELEASE ONE, TWELVE LOTSWhat has actually soldWhat the website says7 lots shown as available that are goneAbout 11 enquiries so far about lots nobody can buy.
The page did not get worse, it just stopped moving while the release sold. Every dashed lot is somebody being told they can buy something that is gone.

Should each development get its own website?

Usually not, for organic search. Every project microsite starts its authority at zero, and when the development sells out the domain is abandoned along with everything it earned. Put the project pages on your corporate domain so each release compounds the last. The exception is a paid campaign landing page, built deliberately noindex so it never competes with your own site.

The pattern is familiar: a project launches, someone registers a name, a microsite goes up, it sells out, and eighteen months later it's either dead or quietly still live and outranking the company that built it. Meanwhile the corporate site sat untouched between projects and never accumulated anything.

One domain, many project pages, is the version that gets better every release. Project five inherits the standing that projects one to four earned. The sold-out pages keep working as proof. The delivered register grows on its own.

Paid is the honest exception. A landing page for a paid campaign has one job, converting traffic you paid for, and it's set noindex on purpose so it never competes with your main site in organic search. Nobody can promise a ranking, and anyone who does is either uninformed or selling. What we commit to is doing everything known to influence ranking and citation, and none of the things known to hurt it.

What proves you can deliver when there's nothing to photograph yet?

A delivered register, not a render wall. Project name, suburb, unit or lot count, consent date, completion date, and photographs taken after handover rather than before. Renders are what every developer has, so they prove nothing on their own. A list of things you actually finished, with dates a buyer can check, is what survives a sceptical reading.

Buyers have been trained to distrust renders. The public record of delayed completions and sunset-clause disputes did that, and no amount of image quality undoes it. The asset that still works is dull and checkable: what you finished, where, how many, and when.

So the register is structured, not a gallery. Each completed project carries the same fields, which also makes it the page a financier, an agent or a council officer can read in thirty seconds.

The second trust layer is third-party: consent references, industry body membership, the contractor's name, the warranty that applies. Property Council New Zealand and UDIA are the two peer bodies that carry weight on each side of the Tasman, and both are linked below.

Where do buyers and partners actually come from, and what is the site's job?

Mostly not from Google. Off-the-plan sales come through agents and property portals, land comes through relationships, and capital comes through referral. The website is rarely the first touch. It's the verification step everyone takes afterwards: the page a buyer's partner opens, the page a financier checks, the page a council officer reads before the meeting.

Naming the channels, because pretending the website is the whole funnel would be dishonest and this sector knows it. Pre-sales run through property portals and through paid campaigns pointed at a project page. Land and public-sector work runs through relationships and through tender platforms: the Government Electronic Tenders Service in New Zealand, AusTender at federal level in Australia plus each state's own portal. Referral runs through architects, planners and financiers who need a developer with a delivery record they can point at. Peer visibility runs through Property Council New Zealand and UDIA, which matters for reputation with financiers and councils rather than with consumers.

The site sits underneath all four. Every one of those channels ends with someone opening your website to check whether you're real, and that's a job worth building for even though it isn't lead generation on its own.

If you have a stage release dated for the next quarter, book a 15-minute call and we'll work out what has to be live before the campaign points at it.

Which build does a property developer actually need?

Three shapes, and which one you need is a question about your release cycle, not your website. One launch page, when a stage has a date and a campaign pointed at it. A full corporate site, when the pipeline lives in five places and none of them agree. Custom, when portal feeds, CRM routing or investor logins are in scope. Bring your next release to a 15-minute call and you'll leave knowing which row your job sits in and what it comes to.

The three shapes a developer's build takes, how long each runs, and what each one suits.
What you're buildingBuild timeWhen it's the right fit
A single project launch page5 daysA stage release with a date on it, where a page needs to be live before the campaign starts and a rebuild isn't on the table
A corporate site with the full stage pipeline, delivered register and two enquiry paths7 daysThe corporate site has gone stale between projects, or the pipeline lives in five places and none of them agree
CustomScoped on the call before a date is setPortal feeds, CRM routing, investor logins, or something that doesn't fit the two rows above

Where the rules actually come from

These facts come from governments and industry bodies, not from us. New Zealand's unit title disclosure sits with the Ministry of Housing and Urban Development and MBIE. LIM turnaround sits with your council. Off-the-plan rules in Australia sit with each state separately. Property Council New Zealand and UDIA are where the sector's own standards and peer visibility live. Every link below was checked on 2026-09-19 and resolves.

Draft quote. Nobody said this. Replace before publishing.

Agents were ringing to ask what was left. Now the site says, and it is right, because nobody has to remember to update it.
Sales manager, property developer (draft)

Questions, answered.

Usually not. A project microsite starts from zero in search and gets abandoned at sell-out, so every release throws away what the last one earned. Keep project pages on your corporate domain and each release compounds the one before it. The exception is a paid ad landing page, which we build noindex on purpose so it converts paid traffic without competing with your own site in organic search.

Book 15 minutes, not a pitch deck 15 minutes

No commitment. No pitch deck. Just 15 minutes to see a project page update itself: mark a stage sold out, move a completion date, and watch it change everywhere it appears at once.

Book a 15-minute demo

No commitment. No pitch deck. Just 15 minutes.

Published . Last reviewed . We review these pages every six months.