Publishing Properties to Your Website (RDELS)
Check a box, add some web copy, and a unit you manage in REDA appears on your website's property search — with a map pin, pricing, a photo, and a tour form that drops the enquiry straight back into REDA. That's what the REDA listing service (RDELS) does: it publishes your REDA properties as public web pages. This article is for the marketing or leasing administrator running that service. After reading it, you'll know how to publish a unit, which property data the public pages show, the configuration records an implementation has to set once, and how the listing pages sit inside your marketing website. A note on scope: the pages themselves are hosted by REDA and embedded into your site by your web team — this article covers the REDA side, the part you control from the property record.
Access you'll need. Editing a property requires one of the operational permission sets (Sales, Acquisition, Property Management, or Lending; the Leasing set can view). Administering the listing service — the configuration records below — uses the listing service's own administrator permission set. The public pages run as a guest visitor, with no login.
How the listing service works
The listing service publishes two public web pages — a property search and a unit-detail page — that REDA hosts and your web team embeds into (or links from) your marketing website. Guest visitors browse them with no login, and they only ever see published properties: anything you haven't published stays off the site. When a visitor finds a unit and asks about it, the enquiry flows straight back into REDA as an inquiry (covered under The inquiry loop below).
The three publishing levels
Before a single unit reaches the site, publishing is governed at three levels, each with its own Publish to Web flag. A unit only shows when the whole chain above it is published too — this is the single most common reason a correctly-flagged unit stays invisible.
| Level | What it controls | Where you set it |
|---|---|---|
| Region | Whether a whole region (and its map area, currency and search defaults) is offered on the site at all | The Regions tab — the region record's web fields |
| Property Type | Whether a category of property (e.g. a residential apartment type) can appear, and under which portfolio and actions | The Property Types tab — the type record's web fields |
| Property (the unit) | Whether the individual unit is listed | The property record itself (covered next) |
Region and Property Type carry required web settings that REDA enforces the moment you tick their publish flag — set the flag without the settings and REDA blocks the save with a plain message telling you exactly which field is missing. The two callouts below list those requirements so an administrator can enable a region or type cleanly the first time.
Publishing a unit
With the region and property type published, getting an individual unit onto the site takes two things: the publish flag, and at least one web-content record to describe it.
What each content record holds
Each listing-content record is the web copy for one language. Create one per language you publish in; the site picks the record that matches the visitor's language.
| Content field | Where it shows on the site |
|---|---|
| Web Label | The listing title |
| Description Summary / Detailed | The search card / the detail page |
| Highlights | Bullet points on the detail page |
| Video URL | Media on the detail page |
| Language Code | Selects this record for a visitor's language |
| Region / Property Type / Amenity Code / Web Beds | Filter and display metadata |
| Pricing Disclaimer / Number Format | How the price is presented |
| Publish to Web | Visibility of this content |
What the website shows from the property
Beyond the content record's copy, the public pages read a set of fields directly from the property. Some are core property data; others are web-specific fields you set for the listing:
| Property web field | What it does on the site |
|---|---|
| Publish to Web | The visibility flag |
| Featured (web) | Featured placement in the search |
| Sale Price Negotiable | A display flag on the buy path |
| Geo Latitude / Longitude | The map pin |
| Map Group By Parent | Clusters units under the building's pin |
| Web Phone | The contact number shown |
| Web Portfolio | Residential vs. Commercial segmentation |
| URL Identifier (+ Override) | The listing's URL slug |
The pages also pull standard property data for display: rent for a new lease, sale price, gross area, beds, property type, region, the parent property, the thumbnail image URL, and amenities.
Multi-language and regional content
To publish a unit in more than one language, add a separate content record for each — one carrying English copy, another Spanish, and so on — each with its own language code. The site serves the record that matches the visitor's language, so the same unit reads naturally to every audience while the underlying property stays single.
The inquiry loop back
The detail page carries a contact form and a "schedule a tour" form. When a visitor submits either, REDA creates an inquiry — with the unit, the source marked Web, and any campaign attribution the visitor arrived with — and, for a tour, a linked showing event. That's the payoff of publishing: the listing doesn't just advertise the unit, it feeds your pipeline. The full picture of what those forms write is in Web Inquiries & Tour Requests. After a visitor submits, they're sent to a thank-you page you configure (a separate one for each form; see the configuration records below).
Admin configuration reference
An implementation sets a handful of configuration records once, so the search behaves and the pages know where to point. These are administrator settings, distinct from the per-property fields above:
| Configuration record | What the administrator sets | Notes |
|---|---|---|
| Google Map Key | The maps key that powers the map pins | Mask everywhere; rotate and restrict — see the warning below |
| Google Map Id | The map style | |
| Unit Public URL | The marketing-site unit-detail page the search links out to | Points at your website's detail page |
| Default thumbnail | A fallback image when a unit has none | |
| Thank-you URL (contact form) | Where the contact form sends visitors after submit | |
| Thank-you URL (showing form) | Where the tour form sends visitors after submit |
The public search also accepts a range of filters in its address — sort order, result limit, portfolio (Residential or Commercial), action (rent or buy), property type, amenities, region, building, language, and the full UTM set — so your web team can link visitors straight to a pre-filtered view.
Worked example: publishing Meridian Court #101
Meridian Properties wants #101 on its website. The administrator:
A visitor filters the search to Residential rentals, opens #101's detail page (map pin drawn from the configured map key), and submits a tour request — creating an inquiry back in REDA, as described in Web Inquiries & Tour Requests.
Where to go next
- Web Inquiries & Tour Requests — what the listing's forms write back into REDA.
- Online Lease Applications (RLA) — the next step after an inquiry, for rentals.
- Amenities & Amenity Pricing — the amenity data the listing filters and displays.
- Suite Implementation Sequence — where site setup fits in the wider rollout.
Frequently asked questions
Work down the chain. First confirm the unit's region and property type are themselves published — a unit can't appear while the level above it is off, and this is the most common cause. Then check that a content record exists for the visitor's language, that the unit's own publish flag is set, and that the display essentials the pages need — rent or price, and a thumbnail — are populated.
From the property's thumbnail image URL field — populate it with the address of your hosted image. That field is the listing's image source.
Yes. Add one content record per language, each with its own language code, and the site serves the one that matches the visitor.
The Google Map Key or Map Id configuration record is unset, or the key is restricted so it won't load on your site. This is an implementation-administrator item — check those two configuration records.
Those flags require their web settings first. A region needs its web portfolio, currency code, geo latitude and longitude, map zoom and phone; a property type needs its web portfolio. REDA names the missing one for you — for example "Web portfolio must be provided to publish the property type to web." or "Web Map Zoom Level must be provided to publish the region to web." Fill the named field and save again.
Was this article helpful?