This guide is for real estate developers, promoters and marketing heads in Mumbai who are commissioning or rebuilding a project website and need to know what the site must legally contain, how listings should be structured, and what actually converts an enquiry into a site visit.
In this guide
What RERA legally requires on your website · The compliance checklist · How to structure project listings · Lead capture that works in real estate · Technical requirements · What it costs · FAQ
What RERA legally requires on your project website
Under Section 11(2) of the Real Estate (Regulation and Development) Act, 2016, every advertisement or prospectus a promoter issues must prominently display the project’s RERA registration number and the Authority’s website address. Since MahaRERA’s Order 46C/2025, effective 8 April 2025, Maharashtra projects must also display a scannable QR code, in the top-right corner, in a font size equal to or larger than the contact details.
The point most developers miss is the first one: your website is an advertisement.
Your website counts as an advertisement under the Act
RERA defines an advertisement broadly — any document, notice, circular or publicity in any form that informs people about a real estate project or invites them to purchase. A website, a landing page, a Google ad, an Instagram post and a WhatsApp forward all fall inside that definition.
MahaRERA made this explicit in its April 2025 order, which applies across newspapers, leaflets, booklets, hoardings, electronic media, banners, social media platforms and messaging services. There is no digital exemption. If your hoardings are compliant and your website is not, you are still exposed.
What must appear, and where
Three elements, together:
- The MahaRERA registration number for the specific project being advertised
- The MahaRERA website address — maharera.maharashtra.gov.in
- A scannable QR code linking to that project’s official page on the MahaRERA portal
The MahaRERA order specifies three formatting requirements that most web developers get wrong because they treat these as footer text:
- Font size equal to or larger than the largest font used for contact details and address
- Top-right placement on the advertisement or promotional material
- Distinct colour, with the QR code rendered at correct aspect ratio so it actually scans
MahaRERA issued the order specifically because registration details were being buried in small fonts and light colours. A pale grey RERA number in an 11px footer is exactly the practice the order was written to stop.
Penalties
Non-compliance attracts a penalty of ₹10,000 to ₹50,000 per violation. Developers get 10 days to rectify; failure to correct within that window is treated as a continuing offence and can trigger further action under the RERA Act.
“Per violation” matters. If you market six projects across a website, six landing pages and a set of social profiles, that is not one exposure.
Section 12: everything on the site must be true
Separate from disclosure, Section 12 of the Act makes the promoter responsible for the veracity of the advertisement. If a buyer makes a payment relying on an incorrect or misleading statement, they are entitled to compensation — and if they choose to withdraw, to a full refund with interest.
In practice this makes three common website habits genuinely risky: artist impressions presented without a disclaimer, amenity lists that include facilities not in the sanctioned plan, and stale possession dates left up after a timeline revision. The third is the most common. A website that still shows “Possession: Dec 2025” eighteen months after that date passed is a documented representation, and it is sitting on your own domain with your own name on it.
The RERA website compliance checklist
| Requirement | Where it goes | Common mistake |
|---|---|---|
| Project registration number | Top-right of every page for that project | One number in the site footer covering all projects |
| MahaRERA website address | Adjacent to the registration number | Omitted entirely |
| Project-specific QR code | Top-right, correct aspect ratio | Stretched by CSS until it stops scanning |
| Font size parity | Equal to or larger than contact details | Set in small footer type |
| Artist impression disclaimer | On every render and walkthrough | Applied to the brochure but not the website |
| Current possession date | Project page, matching the MahaRERA filing | Website says one date, portal says another |
| Landing pages and microsites | Same disclosure as the main site | Campaign pages built by the media agency with no disclosure at all |
| Channel partner pages | Vetted before publication | Broker sites reproducing your content non-compliantly |
Build the disclosure block as a CMS field, not as design. Registration number, QR code image and possession date should be database fields attached to each project, rendered automatically into a fixed component. If they are hard-coded into a page layout, updating them across a twelve-project site becomes a manual job that will eventually be skipped.
How to structure project listings
One page per project, always
The single most common architectural mistake on Mumbai developer websites is a “Projects” page listing everything, with a modal or accordion for each. It fails on three counts: each project cannot rank for its own name, the RERA disclosure cannot be project-specific, and you have nowhere clean to send ad traffic.
Buyers search project names. They search “[project name] price” and “[project name] possession date” and “[project name] review.” If you do not own a page for that query, an aggregator does — and the aggregator monetises your brand name by selling the lead to your competitors.
The data model
Every project should be a structured content type with these fields, not free-form page content:
- Project name, location, micro-market
- Status — upcoming, under construction, ready to move, completed
- Configuration and carpet area range
- Price range or “price on request”
- Possession date
- MahaRERA registration number and QR code
- Amenities (taxonomy, so you can filter across projects)
- Floor plans, master plan, location map
- Construction progress gallery with dates
- Downloadable brochure (gated or ungated — decide deliberately)
Structuring it this way means filters, comparisons and the “similar projects” module all become automatic rather than hand-built. It also means the compliance fields render consistently on every project page.
Handle completed projects properly
Most developers delete sold-out projects. That is a mistake on two counts. Completed projects are your credibility — a buyer evaluating an under-construction tower wants proof you have delivered before. And those pages already have search authority for their project names, which resale buyers and tenants are still searching.
Keep them, mark the status clearly as delivered, add handover photographs, and convert the enquiry form to a resale or rental enquiry.
Construction progress: the most under-used page in Indian real estate
A dated, photographed construction update page published monthly does three things at once. It reassures existing allottees, which reduces support calls. It gives prospective buyers evidence that you build on schedule. And it gives the site a stream of fresh, indexable content on every project page, which almost no competitor in Mumbai is producing.
Lead capture that actually works in real estate
The conversion is the site visit, not the form
Most developer websites are built as though the form submission is the goal. It is not. The economics of the funnel are roughly: enquiries convert to site visits at 15–30%, and site visits convert to bookings at a far higher rate. Optimising the form while ignoring what happens in the next ten minutes is optimising the wrong number.
Build the site so the primary call to action is “Schedule a site visit” with a date and time picker, not “Enquire now.” It is a bigger ask, so it produces fewer leads — and materially better ones.
Form design
Four fields, maximum: name, phone, project of interest, preferred visit date. Every additional field costs you completions, and your sales team can qualify budget and configuration on the call far better than a dropdown can.
Two things worth building in:
- Indian phone validation — 10 digits, +91 prefix handled automatically. Broken phone validation is the most common reason real estate leads arrive unusable.
- Source and campaign capture as hidden fields — UTM parameters, landing page URL, referrer. Without these you cannot tell which portal, keyword or hoarding produced the booking, and you will keep funding channels that do not work.
Speed to lead is the whole game
A property enquiry has a short half-life. The buyer filling your form has almost certainly filled two or three others in the same session, and the developer who calls first has a structural advantage.
Build for this rather than hoping for it: instant WhatsApp or SMS acknowledgement to the buyer, instant push to the sales team — not a daily email digest — and direct write into the CRM with source attached. If your site emails leads to a shared inbox, you are losing bookings to response time, not to price.
WhatsApp is not optional in this market
Indian property buyers will message before they will call, and they will call before they will email. A click-to-WhatsApp button pre-filled with the project name (“Hi, I’m interested in [Project Name], 2BHK”) typically outperforms a contact form on mobile by a wide margin, because it costs the buyer nothing and starts a conversation on a channel they already live in.
Route it through the WhatsApp Business API rather than a personal number, so conversations are logged, assignable and don’t leave with a salesperson.
Connect it to a CRM on day one
Real estate sales cycles run 3–18 months with multiple site visits and family decision-makers. A spreadsheet cannot hold that. Whether you use a standard CRM or a custom CRM built around your sales process, the website must write into it directly, with source, campaign and project attached to every record.
Technical requirements specific to real estate sites
Property websites are unusually image-heavy, and they are consumed overwhelmingly on mobile, frequently on patchy connections. That combination breaks a lot of otherwise competent builds.
| Requirement | Why it matters here |
|---|---|
| WebP images, lazy loading, CDN | Renders and galleries are the heaviest assets on any property site. Uncompressed hero images are the usual cause of a slow developer website |
| Zoomable floor plans | Buyers study these closely. A 900px JPEG that cannot be zoomed is a wasted page |
| Virtual tours and walkthroughs | Embed lazily. A 360° tour loading on page entry destroys mobile load time |
| Location and connectivity map | Distance to metro, school, hospital, airport — the single most-read module on a Mumbai project page |
| Schema markup | Residence, Organization, BreadcrumbList and FAQPage. Almost no Mumbai developer implements this, so it is uncontested advantage |
| EMI calculator | High engagement and a natural, low-friction lead capture point |
| Multilingual (Marathi / Hindi) | Meaningful for mid-segment and MMR peripheral projects, less so for luxury |
| Analytics and call tracking | A large share of property enquiries arrive as phone calls. Untracked calls make your channel data meaningless |
What a real estate developer website costs in Mumbai
| Scope | Typical range | What it includes |
|---|---|---|
| Single-project microsite | ₹60,000 – ₹1,20,000 | One project, compliant disclosure, gallery, floor plans, enquiry form, campaign-ready |
| Developer corporate site | ₹1,50,000 – ₹3,50,000 | Multi-project CMS, filters, completed portfolio, CRM integration, WhatsApp routing |
| Full sales platform | ₹4,00,000+ | Inventory and unit availability, channel partner portal, booking workflow, allottee login |
Add roughly ₹30,000–₹90,000 per year for hosting, licences and maintenance, plus 18% GST on everything. For a full breakdown of what sits outside the quoted price, see our guide to website development cost in Mumbai.
Note: This article covers website and marketing requirements from a development perspective. It is not legal advice. RERA orders are updated regularly — verify current requirements against the MahaRERA orders and circulars page and confirm your specific obligations with your legal counsel or RERA consultant before publishing.
Frequently asked questions
Does a real estate website need to display the RERA number?
Yes. Section 11(2) of the RERA Act, 2016 requires every advertisement or prospectus to prominently display the registration number and the Authority’s website address, and RERA defines advertisement to include publicity in any form. A website is an advertisement. In Maharashtra, a project-specific QR code is also mandatory.
What is the penalty for a non-compliant real estate advertisement in Maharashtra?
Under MahaRERA Order 46C/2025, non-compliance attracts a penalty of ₹10,000 to ₹50,000 per violation. Developers are given 10 days to rectify, after which it is treated as a continuing offence and may attract further action under the RERA Act.
Where exactly should the QR code appear on a webpage?
MahaRERA specifies the top-right corner of the advertisement, in a font size equal to or larger than the largest font used for contact details, in a distinct colour, with the QR code at correct aspect ratio. On a webpage this means a visible disclosure block on each project page — not footer text.
Should each project have its own website or its own page?
Its own page on your main domain, in almost every case. A page inherits your domain authority immediately, whereas a separate microsite domain starts from zero. Standalone microsites make sense mainly for very large launches with a distinct brand identity and a dedicated media budget.
How long does it take to build a real estate developer website?
A single-project microsite takes 3–4 weeks. A multi-project developer site with CMS and CRM integration takes 6–10 weeks. The usual delay is not development — it is waiting for approved renders, final floor plans and legally cleared copy.
Can we reuse brochure content on the website?
Yes, but check it first. Brochure disclaimers, amenity lists and possession dates are often approved once and then reused for years. Because Section 12 makes the promoter responsible for the veracity of every advertisement, anything that has drifted from the current sanctioned plan or MahaRERA filing needs correcting before it goes online.
The bottom line
A real estate developer website in Mumbai has to do two jobs that pull in different directions: satisfy a regulator that is actively penalising poor disclosure, and convert an expensive, hard-won visitor into a site visit.
Most developer sites in this market do neither well. The compliance block is buried in the footer, every project shares one page, and the enquiry form emails a shared inbox that gets checked twice a day. Fixing those three things is not a redesign — it is a build brief.
Get the disclosure rendered as structured data on every project page, give each project a page it can rank for, and route leads to a phone within minutes rather than a mailbox within hours.
Building or rebuilding a project website?
We build RERA-compliant developer websites and sales platforms — structured project listings, automated disclosure blocks, WhatsApp and CRM routing. Tell us what you are launching and we will send a costed scope within 48 hours.
Buzzlink Studios LLP builds websites, apps and custom software from offices in Mumbai (Andheri East), Chhatrapati Sambhajinagar and Rochester, NY. See our real estate web and app development work or browse client case studies.
