Real estate hosting built around the property feed.
An agency site is downstream of somebody else's database. The feed syncs on a schedule, listings change without warning, and a property shown as available after it sold is a phone call you do not want.
The site is only as current as the sync.
Almost every real estate problem is a freshness problem, and freshness is decided by a scheduled job nobody watches.
Feed syncs that complete
A portal feed can carry thousands of properties with dozens of images each. Sync runs get their own execution and memory limits so an import finishes rather than stopping half way and leaving the site partly updated.
Sold means gone, quickly
Cache lifetimes on listing pages are short enough that a withdrawn or sold property stops being shown soon after the feed says so, rather than lingering because a page was cached for a day.
Property images processed on import
Feeds arrive with large photographs per property. They are resized on the way in, so a hundred new listings do not become a hundred slow pages.
Search that handles the filters buyers use
Price band, bedrooms, area and type are all meta fields, and buyers combine them. Those lookups are indexed so a filtered search stays quick as stock grows.
Enquiries are not lost
A lead form that fails is revenue gone with no trace. Notification chains have room to complete, and submissions are stored on the site as well as emailed.
Nobody complains that the site is slow.
They complain that a property they enquired about had already sold. On an agency site, correctness of stock is the customer experience.
- Sync runs finish rather than timing out
- Listing pages expire from cache quickly
- Withdrawn properties leave search too
- Enquiries stored as well as emailed
Filtered stock, without the wait.
Buyers arrive with a price range and an area and immediately filter. That query is the whole experience, and it runs against a dataset the feed rewrites nightly.
What we change for real estate
This workload is unusual in that the site's content is written by a scheduled import rather than by a person, and everything follows from that.
| Setting | What we do | Why |
|---|---|---|
| Feed import runs | Own execution and memory ceilings | A portal feed rewrites thousands of properties in one run, and a half-finished import leaves the site advertising stock that is not there. |
| Listing cache lifetime | Short, unlike the rest of the site | A property's status can change between syncs, and a day-long cache keeps a sold house on the market. |
| Image processing | Handled during import rather than on request | Feeds deliver many large photographs at once, and resizing them on first view means the first buyer to click waits. |
| Search indexing | Indexed on price, bedrooms, area and type | Buyers filter on those four in combination, which is a multi-condition meta query on every search. |
| Enquiry handling | Stored locally as well as emailed | A lead that only existed as an email is unrecoverable if delivery fails, and nobody finds out until the seller asks. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Can you handle an MLS or portal feed?
How quickly does a sold property disappear?
Why is my property search slow?
What happens if an enquiry email fails?
Show stock that is actually available.
Move the agency site across - migration is free, feed configuration included.