Web · Commerce · Platforms · Automation Senior delivery · clear communication No black-box builds Available for selected projects - 2026

◦ Real estate websites · Australia

We speak REAXML.

Most agencies do not need a website. They need their listings to arrive on one — correctly, on schedule, with the sold ones handled and the images already resized. That is a data problem wearing a design brief, and it is the part generic agencies get wrong. WordPress sites for Australian agents, with the feed built properly underneath.

REAXML ingestion from any CRM that publishes it
Incremental sync on modTime — not a nightly wipe and rebuild
Sold and withdrawn listings retired properly, with their rankings kept
Suburb pages and listing schema built in, not bolted on

Get a feed audit

Tell us your CRM and your current site. We will tell you how your listings are reaching the site now, what is going wrong, and what we would change.

Full name

Agency name

Current website

Which CRM do you use?

Roughly how many active listings?

No spam. One technical read of your setup, written by the person who would fix it.

◦ From experience

Listing syncs break in the same four places.

If your listings go missing, arrive late, or your site slows to a crawl every afternoon, it is almost always one of these.

The nightly wipe

The importer deletes every listing and rebuilds from scratch each run. Post IDs change, permalinks change, and every listing page you had ranking starts again from zero. Worse, it is slow enough that a large agency’s feed times out halfway through.

Images re-downloaded every sync

The feed references image filenames, not checksums. A naive importer re-fetches and re-attaches every photo on every run, so the media library grows by thousands of duplicates a month and the sync gets slower until it stops finishing.

Status ignored

REAXML carries a status on every listing — current, sold, leased, withdrawn, offmarket. Miss it and sold properties sit on the site advertising themselves, or get deleted outright, which throws away pages that took months to rank and leaves 404s where the links used to point.

No incremental sync

Every listing has a modTime. Read it and a 900-property feed touches only the three that changed. Ignore it and you reprocess the whole catalogue every fifteen minutes, for nothing.

◦ What we build

The parts that matter

REAXML feed ingestion

The realestate.com.au listing format, read properly: unique IDs respected, modTime honoured, images hashed so they are fetched once, and the whole thing queued so a big feed never blocks the site.

CRM and portal connections

SFTP drops, scheduled pulls, HTTP endpoints and vendor APIs. If your CRM publishes REAXML or exposes an API, we can read it — the format is standardised, so the work does not change with the vendor.

A custom listings plugin

Your listings become real WordPress content — a proper post type with taxonomies for suburb, type and status — so they are searchable, indexable and yours, rather than trapped inside a third-party widget.

Search, filters and map view

Price, beds, baths, land size, suburb and property type, filtered fast because the data is local. Map view where it helps buyers, not because it looks impressive in a pitch.

Listing SEO and structured data

Schema on every property, suburb landing pages that actually rank, clean permalinks, and correct canonical handling so your listings do not compete with the portals for their own content.

Sold and withdrawn lifecycle

Sold listings become proof rather than clutter — kept, relabelled, and redirected where appropriate. Deleting them is the most common way agencies quietly destroy their own search rankings.

◦ The ecosystem

Where your listings come from.

REAXML is a published standard, so the shape of the work does not change with your vendor. If your CRM writes REAXML or exposes an API, we can read it.

Portals and formats

REAXML
realestate.com.au
Domain
Homely
allhomes
Custom XML / JSON

Agency CRMs

VaultRE
Rex
LockedOn
Agentbox
Console Cloud
MyDesktop
Box+Dice
Zenu

How the data arrives

SFTP / FTP drop
Scheduled pull
REST API
Webhook push
Zipped XML + images

◦ Named here as the systems that publish these feeds. Ask us about a specific vendor and we will tell you straight whether we have connected to it before.

◦ How it runs

Six weeks, on staging, against your real feed

01 · Days 1–3

The blueprint

We read your actual feed before quoting — how many listings, which fields your CRM populates, and what the current site is doing with them.

02 · Weeks 2–4

The build

Built on staging against a live copy of your feed, so the sync is proven on real data rather than three sample properties.

03 · Week 5

Feed and speed testing

Full catalogue imported, sold and withdrawn states exercised, Core Web Vitals measured on real listing pages rather than the homepage.

04 · Week 6

Handover and launch

Redirects mapped from the old URLs, sync scheduled, monitoring in place so a failed run tells us rather than you.

◦ The packages

Priced before we start, not after.

Independent Agent

From $6,500

Best for a single-office agency

Custom responsive WordPress build
Suburb and area guide pages
Appraisal and enquiry capture
Core Web Vitals optimisation
30 days post-launch support

Most chosen

Growth Agency

From $15,000

Best for agencies with a live feed

Everything in Independent Agent
REAXML or CRM feed integration
Custom listings plugin, built for you
Advanced search and map view
Suburb market insight pages

Premium Developer

Custom quote

Best for project marketing

Everything in Growth Agency
Headless or multi-site architecture
Interactive multi-unit masterplans
Digital brochure generation
Per-development landing pages

◦ Prices are in AUD and exclude GST. What moves the number: how many listings, how many offices, whether the feed needs custom field mapping, and whether an existing site is being migrated with its rankings intact. You get the full figure in writing before anything starts.

◦ Before you ask

The questions principals actually ask.

Which CRMs can you connect to?

Any that publish REAXML or expose an API. Because the format is a published standard, the work is broadly the same whether the feed comes from VaultRE, Rex, LockedOn or Agentbox — what varies is which optional fields your vendor actually populates, which is why we read your real feed before quoting.

How often do listings update?

As often as your feed publishes — typically every 15 to 30 minutes. Because the sync is incremental, checking frequently costs almost nothing: only listings whose modTime has changed are touched.

What happens to sold and leased listings?

They stay, relabelled, and become proof of what you have shifted in each suburb. Where a listing genuinely has to go, its URL is redirected rather than left to 404. Deleting sold listings is the most common way agencies destroy search rankings they paid for.

Do you build a custom plugin or use an off-the-shelf one?

Whichever is honestly better. For a straightforward feed, an established plugin configured properly is cheaper and we will say so. Custom earns its cost when the field mapping is unusual, when multiple offices or feeds combine, or when the existing plugin is the thing making the site slow.

Will all those listings slow the site down?

No, because nothing is fetched live from a portal when someone loads a page. Listings live in your own database as ordinary WordPress content, so a property page is no slower than a blog post.

Can you migrate from our current listing plugin?

Yes, including the URL structure, so existing rankings and any links pointing at your listings survive the move. That mapping is planned before launch, not patched afterwards.

◦ Start with the feed

Stop losing premium listings to a slow template.

Send us your CRM and your current site. We will look at how your listings reach the page today, tell you what is breaking, and what we would do about it.

Useful whether or not you hire us.