Your CRM is the source of truth, your website is the shop window
Every agency we work with keeps its listings in a CRM. That's where the property manager updates the rent, where the sales agent marks a property under offer, where the photographer's images get uploaded and where open times are set. The website is supposed to show all of that to buyers and renters, ideally within minutes of it changing.
In practice there's often a gap. Listings that sold a fortnight ago are still marked available. A price change made on Monday shows up on Thursday. The agent profile page lists someone who left last year. None of this is a disaster on its own, but buyers notice, and they draw conclusions about how organised the agency is.
How well your website keeps up with your CRM comes down to how the two are connected. It's worth understanding the basics, because the choice gets made once, usually at build time, and then everyone lives with it for years.
How a listing feed actually works
There are two broad ways a website gets listings out of a CRM.
The first is an API. The website asks the CRM for the current listings, or for anything that has changed since it last asked, and gets back structured data: address, price, bedrooms, description, image links, inspection times, the listing agent and so on. The website then stores that data and builds its own pages from it. Most modern CRMs offer some form of API, though what's in it, how fresh it is and how easy it is to work with varies a lot.
The second is a feed. The CRM publishes or pushes a file of listings on a schedule, often in a format that was designed for the big property portals. The website picks it up, reads it and updates its own records. Feeds are older technology but still common, and they work fine when they're set up properly.
Either way, the important part is what happens on the website side. A well-built site keeps its own copy of the listings, checks for changes regularly, and rebuilds or updates the affected pages straight away. Sync frequency is a real decision here. Checking every few minutes means an under offer status appears almost immediately. Checking once a night means a buyer can enquire about a property that went under contract twelve hours earlier, which wastes their time and your agent's.
Images need their own handling. CRMs store full-size photos, often much bigger than a web page needs. The website should resize and compress them when they arrive, rather than sending a buyer's phone a set of camera originals. And status changes need care. When a property sells or leases, the website has to decide whether to remove the page, keep it as a sold result, or redirect it. Each of those choices affects search rankings and the agency's sold history.
Why embedded listing plugins cost you
Some agency sites don't build listing pages at all. They drop in a widget or iframe supplied by the CRM or a third party, and the listings appear inside a box on the page. It's quick to set up and it looks fine at a glance.
The problem is that the listings don't really live on your website. Search engines often can't see the content inside an iframe as belonging to your domain, so your property pages don't rank, and the traffic from someone searching for a street address goes to the portals instead. The widget also loads its own scripts and styles, which slows the page down, particularly on mobile. Your design control stops at the edge of the box. And your analytics usually can't see what people do inside it, so you can't tell which listings are getting attention or where enquiries come from.
We covered the broader picture in building real estate websites that convert. The short version is that listing pages are usually the most visited pages on an agency site, so they're worth building properly.
What a good listing page needs
When the data comes through cleanly, the listing page can do its job. In our experience, these are the things that make the difference.
- A clean, permanent URL. Something readable that includes the suburb and street, and that doesn't change when the price or status changes.
- Fast, well-sized photos. Responsive images in modern formats, with the first photo loading quickly and the rest loading as the buyer scrolls.
- Accurate status and price. Available, under offer, sold or leased, shown clearly and updated from the CRM without anyone touching the website.
- Inspection times that can be saved. Open times shown in plain language, with the option to add them to a calendar.
- The right agent, with a direct way to reach them. Photo, name, phone and an enquiry form that lands in the CRM against that listing, not in a general inbox.
- Structured data for search. Markup that helps search engines understand the address, price and property type.
- Sensible handling once it's gone. A sold or leased result page that still shows the outcome, or a redirect to similar listings, rather than a dead link.
Agent profiles deserve the same treatment. If the CRM holds the agent's details, the website should pull them from there, along with each agent's current and recent listings. That way a new hire appears when they're added in the CRM, and someone who leaves disappears without a support ticket.
Where syncs usually break
Most listing problems we're asked to fix fall into a few patterns.
The sync stops and nobody notices. An API key expires, a password changes, or the CRM updates its feed format, and the website quietly keeps showing the last listings it received. The fix is monitoring: the site should alert someone when it hasn't heard from the CRM in a while, and it should be obvious in the admin when the last successful sync happened.
Deletions don't come through. The website learns about new listings and changes, but when a listing is withdrawn it never gets told, so the page stays live. A good integration regularly compares the full list on both sides, not just the changes.
Images get out of step. The photographer replaces the hero shot in the CRM, but the website still shows the old one because it only downloads images when a listing is first created.
Duplicates appear. The same property gets relisted under a new ID, or moves from rental to sale, and the website ends up with two pages for one address. This needs a rule for how the site matches properties, decided early.
And data entry flows straight through. If an agent types the price into the description field, or leaves the suburb blank, the website shows exactly that. Sometimes the best fix is a short guide for the team on which fields the website relies on.
How to judge a CRM's integration support
We build websites for agencies on a range of CRMs, including Rex, PropertyMe, AgentBox, VaultRE and Box+Dice. The details differ from one to the next and change over time, so rather than rank them, here are the questions worth asking when you're choosing a CRM or planning a new website around the one you have.
Is there a documented API, and does your plan include access to it? Some CRMs treat API access as an add-on, and some limit how often you can call it. Ask whether there's a way to get only the changes since the last check, which makes frequent syncing practical. Ask how withdrawn and sold listings are represented, and how images are delivered. Ask whether enquiries from your website can be sent back into the CRM against the right listing and agent, because that closes the loop for your team. And ask who to contact when something breaks, and how quickly they respond.
If the answers are vague, that's useful information too. It usually means the integration will need more defensive work on the website side, which affects both the build and the ongoing support.
Doing it once, properly
A listing integration is not glamorous work, but it's the part of an agency website that touches every buyer and every renter. Done well, nobody thinks about it: listings appear when they're entered, change when they change, and leave when they should. Done badly, it becomes a weekly chore for someone in the office and a slow leak of trust with the people you're trying to reach.
If you're planning a new site, or your current one has started showing sold properties as available, it's worth getting someone to look at how the sync is built before anything else. You can see how we approach agency websites on our real estate websites page. If you'd like us to look at your current setup and tell you plainly what's working and what isn't, get in touch.
