SiteCurb Listings

SiteCurb Listings puts an agent’s current listings on a WordPress site — a brokerage site, a team site, a personal blog — without re-entering anything. The listings are managed once on SiteCurb, and this plugin shows them wherever you drop the shortcode.

[sitecurb_listings]

Each card shows the first photo, the price, the headline, the city and state, and the facts (beds, baths, square feet), and links to the full listing page. Sold and pending listings carry a tag.

Features

• One shortcode — [sitecurb_listings] uses the site set on the settings page; every option can be overridden per shortcode
• Responsive grid — 1 to 4 columns, inherits your theme’s fonts and colours
• Status filter — show active listings only (default), sold, pending, or everything
• Featured only — featured="yes" for a homepage highlight strip
• Cached — listings are fetched from SiteCurb and kept for 15 minutes (configurable), so pages stay fast and nothing is fetched on every view
• No JavaScript, no external scripts — one small stylesheet, loaded only on pages that show listings
• Multiple agents — use site="..." to show different agents on different pages of a brokerage site

Shortcode reference

• site — the agent’s SiteCurb address: jane, jane.sitecurb.com, or a connected custom domain. Defaults to the site set under Settings → SiteCurb Listings.
• limit — number of listings to show, 1 to 50. Default 6.
• columns — 1 to 4. Default 3.
• status — active, pending, sold or all. Default active.
• featured — yes to show featured listings only. Default no.

Example: [sitecurb_listings site="jane" limit="3" columns="3" featured="yes"]

Who is it for?

Agents who already have a SiteCurb site and also appear on a brokerage or team WordPress site, and the web designers who build those brokerage sites. Add the shortcode once per agent and their listings stay current on both sites.

Privacy

The plugin fetches the public listings feed from the SiteCurb site you specify (https://<your-site>/feed). No visitor data is sent anywhere. The request is made by your server, not by your visitors’ browsers.