Minimum lot size
Many zones set a floor on the area needed per dwelling or per subdivided lot. A block that is just under the threshold yields one dwelling; two combined can clear the bar with room for three or four.
Single lots miss the minimum-lot, frontage and density thresholds. Combined ones clear them — and win a land premium. GoSiteHunt reads the cadastre around any address and finds the adjoining-lot groups worth assembling, in seconds.
Run a free amalgamation scanOpen the Amalgamations toolThe best development site on a street often is not for sale, and often is not one site at all. It is two or three ordinary blocks that, on their own, each fall just short — too narrow for a driveway, too small for the density the zone allows, one frontage short of what the code demands. Put them together and the maths changes: the combined parcel clears the thresholds, carries more dwellings, and commands a land premium neither owner could get alone. That is site amalgamation, also called land assembly — and finding those combinations first is a real edge.
The hard part is spotting them. You cannot eyeball a suburb and know which runs of adjoining lots quietly unlock extra yield when combined; you would have to read the cadastre parcel by parcel and re-run the yield test for every plausible grouping. This page explains what amalgamation is, how to spot assembly opportunities, exactly how GoSiteHunt's Amalgamations engine finds adjoining-lot groups and quantifies the upside, the owner-agreement and planning realities you cannot skip, and how residential assembly differs from retail and mixed-use.
Site amalgamation is combining two or more adjoining lots into one larger development site so the whole outperforms the sum of the parts. It is a planning and acquisition play, not a construction one. The value is created the moment the parcels are consolidated — because a bigger, wider, more regular site can support a scheme the individual blocks legally or physically cannot.
Three constraints drive almost every assembly opportunity, and they are the reason single blocks so often miss out:
Many zones set a floor on the area needed per dwelling or per subdivided lot. A block that is just under the threshold yields one dwelling; two combined can clear the bar with room for three or four.
Density controls, setbacks and access rules reward width and regularity. Two narrow lots side by side give the combined frontage that makes a driveway, a common access, or an efficient built form possible.
Above a certain site area, apartment and townhouse controls open up. Assembly is often the only way to reach the footprint where the higher-yield product the zone permits actually becomes buildable.
Because a combined site does what the singles cannot, it draws stronger developer interest and a premium over the sum of the individual land values. That premium is the whole economic reason assembly exists — and the reason an owner will sometimes accept a deal only if their neighbour is in it too.
Manually, land assemblers look for a pattern: a cluster of modest, similar-vintage blocks in a zone that permits more than they hold, where no single lot is big or wide enough to justify redevelopment but a run of two-to-four adjoining ones would be. Corner holdings, deep back gardens and older lots in an up-zoned corridor are classic tells. The skill is reading the cadastre and the controls together and asking, for every plausible grouping, "does combining these cross a threshold that unlocks yield?"
Doing that by hand across a suburb is slow and easy to get wrong — exactly the work worth automating. The signal is not "this block is big"; it is "these specific neighbours, combined, screen at more than they do apart" — a comparison across every adjoining grouping, re-run on zone-typical yield numbers. That is what the Amalgamations engine computes at scale.
Inside GoSiteHunt the Amalgamations tool lives on the /sites screen behind the "🧩 Amalgamations" button, and a run costs 5 credits. You give it an address; it reads the cadastre around that address and finds groups of neighbouring or adjoining lots that, combined, support a bigger scheme — more dwellings, or more subdivision lots — than each block does separately. This is the classic land-assembly play, computed for you instead of eyeballed.
For every candidate lot-group it returns a compact, decision-ready result:
A suburb of individual blocks becomes a ranked set of combinations — the runs of adjoining lots where consolidation crosses a threshold and adds yield, sorted by the uplift they create. You are no longer guessing which neighbours belong together; the engine has tested the groupings and shown you the ones that matter.
Be clear about what this is: a screening signal computed on zone-typical numbers. It tells you where to look and how combinations rank, not what will be approved or what anyone will sell for. It is not a guarantee, and the developer-side tool does not contact owners — it reads public cadastre and maps the opportunity. Owner outreach, offers and negotiation are your job.
The table below sets out what you feed a run against what comes back per candidate lot-group, and why each output earns its place in the decision. The figures an engine produces are indicative screening, not a valuation.
| You provide | The engine returns per lot-group | Why it matters |
|---|---|---|
| An address to scan around | Groups of adjoining / neighbouring lots | Surfaces the combinations you would otherwise have to find parcel by parcel |
| (automatic, from cadastre) | The specific lots in each group | Tells you exactly whose land the play depends on |
| (automatic) | Combined site area in m² | The consolidated footprint the yield is tested against |
| (automatic) | Units or subdivision lots the combined site screens at | The scale of the opportunity, not just that one exists |
| (automatic) | Uplift vs developing separately (e.g. "+6") | Ranks groups by how much assembly actually adds |
| (automatic) | Each lot-group mapped as a polygon | Lets you read shape, frontage and context before any outreach |
The point is easiest to see with an illustrative example — figures chosen to show the mechanic, not to appraise any real block. Take three lots of roughly 560, 580 and 600 m². Alone, each sits under the density threshold and screens at one dwelling. Combined into a single ~1,740 m² parcel they clear that threshold and can screen at around nine dwellings — an uplift of about +6 versus developing separately. Change the zone, the threshold or the grouping and the number moves; that sensitivity is exactly what a screening tool is built to run so you chase the combinations that actually pay.
Screening tells you a combination is worth pursuing. It does not make it happen. Three realities sit between a promising lot-group and a real site, and none of them can be skipped:
On the owner side, GoSiteHunt runs a matching service so those conversations can even start. Through /sell-together, an owner checks their address, sees the combined-site upside with their immediate neighbours screened, and registers interest. When another owner in the same run of street registers, GoSiteHunt emails both to introduce them — and that is the whole service. From there owners may list the combined opportunity on the off-market marketplace for a flat advertising fee, never a commission. GoSiteHunt never values property, never negotiates, never relays offers and never handles money. It is an advertising and introduction platform, not an agent.
Assembly logic changes with what you are trying to build, and the engine handles both cases.
Residential assembly is usually about thresholds. You are combining modest blocks to cross the minimum lot size, frontage or density trigger that turns single-dwelling sites into a townhouse or apartment site — the A+B+C pattern above. The prize is dwelling yield and the land premium that comes with clearing the bar.
Retail and mixed-use (centre) assembly is about footprint and catchment. For centre and corridor zones the engine assembles neighbouring lots into a larger centre site — the kind that can carry a retail podium with apartments above — and catchment-tests it. Here the constraint is not just density but reaching the contiguous footprint and frontage a viable retail or mixed-use scheme needs, in a location whose catchment can support it. A single shopfront lot rarely gets there; an assembled run of them can.
In both cases the output is the same shape — the lots, the combined area, what it screens at, the uplift, and a polygon on the map — so you can compare a housing assembly and a centre assembly on the same screen and back the one with the stronger upside.
Amalgamation is one move inside GoSiteHunt's full development stack — find the parcel, run the feasibility, pin the maximum land price, reach the GO / NO-GO — available for any address across dozens of countries and free to start.
Run the Amalgamations tool on the /sites screen to surface adjoining-lot groups, combined area, yield and uplift. Or scan for single parcels first with the development site finder.
Check what a combined site can carry with the subdivision calculator, then model the whole deal in the feasibility software.
Own a block in a promising run? See the combined upside and get matched with neighbours via sell together, or check what your site is worth first.
List or find consolidated opportunities on the off-market marketplace, see the full workflow in how it works, or read more on the FAQ.
The fastest way to understand amalgamation screening is to point it at a street you already read well. GoSiteHunt is free to start with 50 trial credits — a single-address site report costs 1 credit and an Amalgamations run costs 5, so the free tier covers several assembly scans plus a batch of individual reports before you pay anything. Run the tool on your target area, open the top-ranked lot-groups, and read their combined area, screened yield and uplift. Then do the human work: research the owners, confirm the controls, and pressure-test the numbers.
Run a free amalgamation scanSee the feasibility software
Screening outputs are indicative only and are not valuation, planning, financial or legal advice. Amalgamation needs every owner to agree; confirm planning controls, market evidence, title and costs before committing to a site.
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.