There is a real method behind the answer — the same four checks a developer runs before making an offer: the zone, the minimum lot size, the frontage, and the practical yield once the site plan meets reality. This page walks through all four, then runs them on your address, free.
Takes you to the free screen with your address carried over. No account needed to see the first read.
Ask three neighbours how many units fit on your block and you will get three confident, contradictory answers. Ask a developer and they will not answer at all until they have checked four things — because the honest answer to “how many units can I fit?” is never a single number pulled from the air. It is the output of a short chain of checks, each one capable of cutting the number down. This page explains that chain in plain English, so you can run it on your own block and understand the answer you get.
Zoning decides whether multiple dwellings are even on the menu. Some residential zones are written for single houses and resist anything denser; others actively invite townhouses, group dwellings or small apartment buildings. Until you know the zone and what it permits, every unit count is a guess. Check yours with the zoning lookup.
Most zones set a minimum site area per dwelling — the density control. Divide your land area by that number and you have the theoretical ceiling. An 800 m² block in a zone with a 300 m² minimum divides to 2.67, so the paper ceiling is two dwellings — and possibly three where the code allows a different product type, like group dwellings, to work to a smaller effective area.
Codes typically require a minimum street frontage per dwelling, and every dwelling needs legal and practical access. A wide, regular block can put dwellings side by side; a narrow block forces a battle-axe or shared-driveway layout, and the driveway itself consumes land that no longer counts toward anything sellable. Corner blocks, with two frontages, are the quiet winners here.
The number that survives contact with a site plan: setbacks off every boundary, private open space per dwelling, car parking that actually works, easements, protected trees, slope and stormwater. This is why the practical answer is so often one fewer than the paper ceiling — and why forcing the extra unit can produce the worst dwelling on the site.
Take a generic example — not a real address, because the point is the method. Suppose a roughly 800 m² suburban block, regular in shape, with about 20 m of frontage, in a zone whose policy welcomes infill and whose density controls suggest around 300 m² of site area per dwelling.
| Step | Check | Result on this example |
|---|---|---|
| 1 | Zone permits multiple dwellings? | Yes — infill products are envisaged by the zone |
| 2 | Theoretical ceiling: 800 ÷ 300 | 2.67 → two comfortably; three only if a smaller-lot product type applies |
| 3 | Frontage: 20 m against a per-dwelling minimum | Two street-facing dwellings fit; a third needs a shared drive |
| 4 | Practical yield: setbacks, parking, open space, services | Two generous dwellings, or three tighter ones if access resolves |
Notice what happened: the answer is not “three units”. It is “two comfortably, three if the access and open-space geometry can be made to work — and the three-unit scheme needs its economics checked before anyone falls in love with it.” That sentence is what a genuine yield answer looks like. Anything shorter is marketing.
Four constraints do most of the damage to optimistic unit counts, and none of them appear in a land-area calculation:
A sewer main or drainage easement across the middle of a block can sterilise exactly the land the extra dwelling needed. Easements are on the title and the services plan — check early, because no design fixes geography.
Regulated trees, heritage and character overlays, flood and bushfire overlays — each can shrink the developable envelope or add conditions that make the marginal unit uneconomic.
Every dwelling needs parking that a car can actually swing into. Driveways and manoeuvring areas are land you buy but cannot sell. Shared drives also introduce body-corporate or community-title questions that affect end value.
Fall across a site drives retaining, split levels and drainage design. Overland flow paths can be a hard no for the part of the block you needed most. Flat, dry and regular is worth more than it looks.
This is also why the question “how many units can I fit?” is really the first half of a two-part question. The second half is “…and what is the block worth with that scheme on it?” The residual land value calculator answers the second half; the townhouse-fit checker and the subdivision potential checker help with the first.
GoSiteHunt runs the whole chain from the address alone: the zone and what it permits, the density and lot-size logic, frontage and parcel geometry from the cadastre, local approval precedent, and an indicative yield with the economics attached — what the finished scheme might sell for and what that makes the land worth to a developer. It is a screen, not a design: its job is to tell you whether the block deserves an architect, and to arm you with the right expectations before anyone knocks on your door with an offer.
Check my block freeRun the full site report
Curious how your suburb's numbers stack up first? Browse the suburb, postcode and LGA data pages or the ranked Adelaide, NSW, Victoria and Queensland opportunity indexes — all built from government sale and rental-bond data. And if you are commissioning a report, read what a development potential report should contain first.
Type the address, get the zone, the density logic, an indicative yield and what it means in dollars — free, in about a minute, with no obligation. Then you will know whether the right next call is an agent, an architect, or nobody at all.
Whatever brought you here, the sound path is the same one developers follow: identify the market, test the planning controls, work out what can actually be built, check real end values, estimate the costs — and only then decide what the land is worth. GoSiteHunt runs that whole sequence from a single address, before you commit due-diligence money.
Run an address through GoSiteHunt or start with the residual land value calculator before you commit due diligence spend.
Before relying on any first-pass development signal, confirm the address against the live planning source, the title and easements, survey dimensions, tree and heritage controls, infrastructure capacity, stormwater, access geometry, parking, open-space requirements and any recent or pending planning amendments. Then test the commercial side: realistic end values, selling time, construction rate, demolition, services, consultant fees, authority contributions, contingency, finance, tax treatment, delivery timeframe, holding costs and the margin required for the risk. The value of GoSiteHunt is that it keeps these checks connected. A page may help a site get onto the shortlist, but the address-level report and a professional review decide whether it deserves an offer.
For search users, this extra context matters because development feasibility is never a single-keyword answer. A useful page should explain the decision path, the assumptions and the next action, not just repeat a suburb, zone or tool name. That is why each GoSiteHunt discovery page links the topic back to a practical screening workflow. The goal is not to pad copy; it is to make the page useful enough that a buyer understands what evidence is missing, what a consultant would still need to confirm, and which next action moves the opportunity closer to or further from a genuine offer. Every page should answer a practical buyer question and point to a measurable address-level check.