Property listings your agents can edit. Visits that know the home.
A real estate website is a page with many items for properties, detail URLs for each listing, and forms that tag the lead with that property. Your frontend owns the design; mywebcms owns the words, prices and galleries.
List. One Properties page. Every listing is an item with the same fields — title, price, bedrooms, locality — and its own slug.
Without a listings model
Fifty homes, fifty piles of content.
Hard-coded listing pages, prices in a sheet that never matches the site, and enquiry forms that forget which property someone opened.
Copy-paste per property
Details rewritten by hand on every property page. One update means a deploy — or many manual edits.BanerWakadLonavalaNo shared schema
Each property page drifts: different field names, missing media, filters the list page can't use.InconsistentLeads without a listing
Contact forms dump into one inbox. Nobody knows which property to follow up on.Which listing?CRM bolted on
A third-party form or sheet for site visits while the CMS holds yesterday's prices. Two sources of truth.Two tools
One schema for every listing
A page with many items — each item is a property.
Create a Properties page once. Define fields (title, price, bedrooms, locality, gallery). Every new listing is an item with its own slug, not a new site or a duplicated page.See how pages with many items work
Same fields everywhere
Title, price, bedrooms, locality, featured — optional fields cover differences. No per-listing schema drift.pricebedroomslocalityDirectory from the list API
GET the page slug for every visible property. Your cards read JSON — never hard-coded properties.GET /v1/pages/propertiesFilter and sort
Mark locality or featured as filters; sort by price. Configured on the schema — not custom code per site.locality=sort=priceAdd a property in admin
New listing = new item. Fill the fields, Release, and the list API includes it. No deploy for content.+ New item
A page for every listing
Each property gets its own address and sections.
The item template defines Hero, Gallery, Floor plan and Enquiry once. Every listing fills its own values. Rename a slug and the old one stays as a redirect.See how Releases ship changes
Stable detail URLs
Your site routes /properties/2-bhk-baner. The API is GET /v1/pages/properties/2-bhk-baner with every field./properties/<slug>Item sections
Hero, gallery, amenities, FAQ — the same section kinds as any page, scoped to the item. Design stays in your frontend.HeroGalleryEnquiryForm on the property
A form section on the item template shows the same form on every property page, with the item recorded on the lead.form · itemSlugSlug redirects
Rename a property URL and the old slug answers with the new one. Bookmarks and ads don't break.Old → new
Leads that know the property
Every site visit is tagged with its listing.
Forms on item pages send the item with the submission. Filter leads by property, assign an owner, and export without guessing which home they meant.See how forms and leads work
- Neha S.2 BHK, BanerSite visit requestNew
- Omar K.3 BHK, WakadSite visit requestContacted
- Priya R.Villa, LonavalaCallbackNew
Item on the lead
pagePath and itemSlug travel in the form context. Admin shows which property the visitor was on.itemSlug: 2-bhk-banerFilter by property
Work one property's queue separately from another's. Same statuses and owners as any other lead.BanerWakadOne inbox, many properties
Still one website's Forms & Leads — not a CRM per property. Access stays per module for the team.One websiteExport the filter
CSV of the current property filter or selection. WhatsApp and CRM delivery aren't built yet..csv
Who updates the listings
Agents edit. Design stays locked.
Give an editor Content access — they change price and status in Development. A Release (with approval if you want) puts it live. They never touch API keys or the frontend.See how team access works
Edit one property
Items check out independently. Updating Baner never locks Wakad.Per-item checkoutRelease to publish
Production stays read-only until someone merges. Same flow as any page — not an industry-only publish button.v3v4Access per module
Content Editor for properties; Leads Viewer for enquiries; Developer settings nowhere in sight.ContentLeadsSame platform, property schema
Nothing is hardcoded for real estate. Travel and hotels use the same building blocks with different fields.Configurable
FAQ
Questions about property sites.
Listings as items, site visits, portals, and who edits prices.
Get started
Build your next client site on mywebcms.
Start from a screenshot, give your client one simple place to run it, and ship it on any stack you like.
- Two steps to your first website:
- 1Create your workspace
- 2Add a client website
Everything that comes with mywebcms
Tap any feature to learn more.