Docs · Use Cases

Build a real-estate listings site

A full walkthrough: seed a property listings site with structured fields, galleries and descriptions through NIBWP.

Real-estate sites are data-heavy by nature: every property is price, beds, baths, area, location, a gallery and a description. Building one by hand means entering all of that, listing by listing. This guide replaces the data entry with a conversation. With a property CPT and NIBWP, an agent builds the listing structure, registers the fields, imports properties from a spreadsheet or export, and attaches photos — all as drafts you verify before they go live.

TL;DR

Use a property CPT or real-estate plugin, connect NIBWP, and have the agent register fields (price, beds, baths), import listings from a spreadsheet, attach galleries, and draft descriptions — all on review.

Who this is for

Agents and agencies launching a listings site, property managers digitizing a portfolio, and developers showcasing a project. You bring the property data; the agent builds the structure and fills it.

What you will build

  • Property listings with price, beds, baths, area and location
  • Photo galleries uploaded and attached automatically
  • Neighborhood and property-type taxonomies
  • Search-friendly titles and descriptions per property
  • A repeatable import for new listings

Before you start

You need a property CPT or real-estate plugin active, NIBWP with a write-scoped token, and a connected MCP client. A spreadsheet or MLS export of properties makes the import fast.

Keep property imports as draftsProperty data is detail-heavy and high-stakes — a wrong price or address matters. Force-draft lets you verify every listing before it is published.

The stack

LayerWhat handles it
ListingsA property CPT or real-estate plugin
Fieldsnibwp/acf-manage-fields for price, beds, baths, area
Contentnibwp/wp-create-post
Photosnibwp/wp-upload-media
SEOnibwp/seo-image-optimize

Step 1 — Register the property fields

Tell the agent the fields a listing needs and it registers them — price, beds, baths, area, location — so every property has a structured home for its data.

claude > nibwp
You: Add fields to the property type: price (number), beds\n     (number), baths (number), area_sqft (number), location (text).\nnibwp/acf-manage-fields { group: property, fields: [...] }\n5 fields registered on the property type

Step 2 — Import the listings

Feed the agent a spreadsheet or export. It drafts a property for each row with fields filled and a placeholder gallery, validated so a malformed price or missing field is caught before saving.

claude > nibwp
You: Import these 24 properties from the spreadsheet, fill all\n     fields, category by neighborhood, draft each.\nnibwp/wp-create-post { type: property, status: draft } x24\n24 properties drafted - fields filled, categorized

Step 3 — Attach photos and descriptions

The agent uploads and links the gallery images to each property, and drafts a description from the structured data — “Bright 2-bed with 95 sqm of living space in the East Side…” — consistent across the whole portfolio.

Step 4 — Review and publish

Walk the drafts, confirm prices and addresses, then bulk-publish. The audit log records every listing created, so you have a full account of the import.


FAQ

Can it import from an MLS export?
Yes — point it at the spreadsheet and it maps columns to property fields, drafting each listing.
Does it handle photo galleries?
Yes — it uploads images and links them to the right property; you supply the files or a source it can read.
Will listings publish without me?
Only with a publish scope. With write + force-draft, every property waits for your review.
A listings site that used to mean weeks of data entry fills up in an afternoon of import — every listing verified before it goes live.

Build your listings site

Seed a property site from a spreadsheet through NIBWP.

Start building

Connect your first agent.

Follow the quickstart, or book a demo and we'll walk you through it.