Elite module 01

Portal Feed Export setup.

Generate structured XML/CSV feeds for Property Finder, Bayut and Dubizzle supported workflows. Token-protected URLs, scheduled regeneration, validation.

What Portal Feed Export does

Portal Feed Export generates structured data feeds (XML and CSV) that work with the supported upload workflows of Dubai’s main real estate portals — Property Finder, Bayut and Dubizzle — plus any custom partner that accepts a standard feed format.

What this module does and doesn’t do. It produces the feed files in the right format. Whether each portal accepts your feed and how they authenticate it is handled directly between your agency and each portal. We don’t broker that relationship — that’s your existing portal account.

Activate the module

Make sure you have a valid Elite licence first. Then:

  1. Go to Elite → Modules in your WordPress admin
  2. Find Portal Feed Export in the module list
  3. Click Activate

A new menu appears: Elite → Portal Feeds. This is where you create and manage every feed.

Property Finder feed

Setting up a feed for Property Finder takes about five minutes.

  1. Elite → Portal Feeds → click Add Property Finder feed
  2. Set the filters — which properties to include. Filter by purpose (sale, rent, off-plan), type, community, featured-only, agent, or any combination.
  3. Click Save. Elite generates a token-protected feed URL.
  4. Copy the feed URL and send it to your Property Finder account manager.
  5. Property Finder’s system polls the URL on its own schedule (usually every few hours).

Your feed URL will look something like:

https://yoursite.com/feeds/property-finder?token=pn_a1b2c3d4e5f6

The token is rotatable. If a URL is ever shared by mistake or you want to change it, click Rotate token any time. The old URL stops working immediately and a new one is generated. You’ll need to send the new URL to Property Finder.

Bayut and Dubizzle feed

Bayut and Dubizzle share the same underlying inventory system in the UAE. One Bayut/Dubizzle feed exports to both portals. You don’t need two separate feeds.

  1. Elite → Portal Feeds → click Add Bayut/Dubizzle feed
  2. Configure the filters (same options as Property Finder)
  3. Save and copy the feed URL
  4. Paste the URL into your Bayut account → Sync Settings
Heads up. Bayut and Dubizzle accept slightly different field formats than Property Finder. Elite handles this automatically — the same property exports differently in each feed so each portal gets exactly what it expects.

Custom XML or CSV feeds

If you work with a partner portal, aggregator, or custom system that accepts a feed, you can generate one in any format.

  1. Elite → Portal Feeds → Add Custom feed
  2. Configure field mapping — pick which Prop Nexia fields go into which XML or CSV columns
  3. Choose the output format: XML, CSV, or JSON
  4. Save and share the URL with your partner

This is useful if you sell listings through a regional aggregator, a partner brokerage’s portal, or your own multi-site setup.

Refresh schedule

Feeds are regenerated automatically by WordPress on a schedule you control. The default is every 4 hours. You can change it for each feed individually.

FrequencyWhen to use it
Every 15 minutesActive agencies adding multiple listings per day. Highest load on your server.
HourlyMost agencies. Listings appear in your feeds within an hour of being added.
Every 4 hours (default)Balanced for typical agency workflows.
DailySlow-moving inventory or very large catalogues where regeneration is expensive.
Manual onlyYou trigger a regenerate from the admin when you’re ready to publish updates.

The feed is cached between regenerations. So even if the portal polls your URL more often than your regeneration schedule, the server response is fast and cheap.

Tip. If your site has heavy traffic or runs on shared hosting, set the schedule to Hourly or Every 4 hours. Set Every 15 minutes only if you genuinely add listings that often and your hosting can handle it.

Validate the feed

Before you send a feed URL to your portal account manager, validate it. Elite → Portal Feeds → click a feed → Validate.

The validator checks:

  • All required fields are present on every listing in the feed
  • Image URLs are reachable from the public internet
  • DLD permit numbers are formatted correctly (for Property Finder)
  • Price values are numeric and in the expected currency
  • No properties have a status that excludes them from the feed

If any property fails validation, the report tells you exactly which one and which field. Fix it in the property editor, run validation again, then share the URL with the portal.

Required fields per portal

Each portal has its own required fields. Prop Nexia’s listing form already includes all of them — but you have to actually fill them in. Listings missing required fields are skipped from the feed.

FieldProperty FinderBayut / Dubizzle
TitleRequiredRequired
Property typeRequiredRequired
Purpose (sale/rent)RequiredRequired
PriceRequiredRequired
Bedrooms and bathroomsRequiredRequired
Built-up area (sqft)RequiredRequired
Location (city + community)RequiredRequired
DLD permit numberRequiredRequired
Trakheesi numberRequired (rentals)Required (rentals)
PhotosMinimum 5Minimum 4
Agent assignedRequiredRequired

Optional but recommended for better placement: floor plan, video URL, 360° tour URL, description in English and Arabic.

Troubleshooting

Feed URL returns 404

Re-save your permalinks. Go to Settings → Permalinks → Save. WordPress rewrites can lose the feed endpoint on plugin updates, and re-saving fixes it. You don’t need to change anything — just clicking Save is enough.

Feed is empty or missing properties

Two common reasons:

  • Filters are too narrow. Check the filters on the feed. Filters like “featured + Dubai Marina + villa + under AED 2M” can result in zero matches.
  • Properties are missing required fields. Run validation. Any property missing DLD permit, photos, or other required fields is skipped from the feed.

Portal rejects the feed

Run the Validate step first. If validation passes but the portal still rejects the feed:

  1. Save the validator output
  2. Share it with your portal account manager — they can tell you which specific field they’re rejecting
  3. Email hello@propnexia.com with the validator output and the portal’s response. We’ll review the spec compliance.

Images don’t load on the portal

Portals fetch images from your URLs. If your hosting blocks external requests, or your images are behind authentication, the portal can’t load them. Check:

  • Image URLs are public (open one in an incognito browser to confirm)
  • Your hosting doesn’t have hotlink protection that blocks portal user agents
  • Images are not behind a paywall, password, or VPN

Feed is slow to load

The feed is cached, so it should be fast. If it’s slow, regeneration is probably running on every request. Check:

  • WP-Cron is running (sometimes blocked on shared hosting — install a real cron job)
  • Your hosting isn’t out of memory (large catalogues need at least 256MB PHP memory)
  • The schedule isn’t set to Every 15 minutes on a very large catalogue