RERA Rules for Portal Listings on 99acres and Magicbricks

A sales head at a mid-sized Bengaluru developer once pulled up three browser tabs during a Monday review — one for 99acres, one for Magicbricks, one for Housing.com. Same tower, same flat, same floor. The carpet area read 1,180 sq ft on one portal, 1,240 sq ft on another, and a plain "1,250 sq ft (approx.)" on the third, with no clarification of whether that was carpet, built-up, or super built-up. The RERA registration number appeared correctly on two listings and was missing entirely from the third, because a channel partner had re-uploaded the project without it. None of this was intentional fraud — it was the ordinary entropy of five channel partners, two in-house executives, and three portals each with their own upload templates. But to a buyer comparing tabs side by side, it looked like the builder didn't know its own flat sizes, and to a regulator, an inconsistent or missing RERA number on an advertisement is a real compliance gap, not a cosmetic one.

This is the quiet operational problem behind almost every builder's digital marketing stack: the project is registered once with the state RERA authority, but it gets advertised dozens of times, across portals, social pages, WhatsApp broadcasts and channel-partner microsites — and each of those is legally an advertisement in its own right.

Portal Listings Are Advertisements Under RERA

Under India's Real Estate (Regulation and Development) Act, any communication that markets, invites, or induces a person to buy or book a unit in a real estate project counts as an advertisement — whether it runs in a newspaper, on a hoarding, or as a listing card on a property portal. That means a 99acres listing, a Magicbricks card, or a boosted Instagram post for the same project all fall under the same disclosure logic that applies to a print ad: the project's RERA registration number must be displayed, and the area figures quoted must be built on the carpet-area definition the Act uses, not an inflated marketing number.

For developers, the practical consequence is that "the listing is just marketing, not a legal document" is not a safe assumption. A prospective buyer who books a unit relying on a portal listing that misstates area or omits the registration number has grounds for a complaint — and state authorities have, over the years, treated portal and third-party advertising as within their remit precisely because so much of first-contact buyer discovery now happens on aggregators rather than a builder's own website.

Property portals themselves have tightened their own gatekeeping in response — most major Indian portals today require a RERA registration number at the point of project upload before an under-construction listing can go live, and several display the number prominently on the listing card itself. That shift is a portal policy decision responding to the regulatory environment, not a substitute for the builder's own legal obligation — the developer still owns the compliance risk if the number displayed is wrong, expired for a phase, or missing on a partner-uploaded duplicate.

Making a Portal Listing Compliant — and Consistent

Getting one listing compliant is straightforward. Keeping fifteen listings across five portals compliant and internally consistent, over an 18-month sales cycle, is the actual operational challenge. A practical sequence:

1. Establish one canonical listing record per project phase. Before anything is uploaded anywhere, lock the RERA registration number, the carpet area per unit type (not a blended average), the price basis (carpet-area rate vs all-inclusive), and the approved floor plans in a single internal source of truth.
2. Push, don't re-key. Every re-typing of carpet area into a new portal's upload form is a chance for a rounding error or a stale figure to creep in. Wherever a portal supports bulk-upload templates or API feeds, use them, and have one person own the master sheet.
3. Audit channel-partner uploads. Channel partners frequently create their own listings for lead generation, sometimes duplicating a project with different (sometimes outdated) figures. A recurring audit — even a simple monthly search across the major portals for your own project name — catches drift before a buyer does.
4. Version control area figures. If RERA-registered phase details change (a revised sanctioned plan, an added tower), update every live listing, not just the primary one, and note the "as of" date the figures reflect.
5. Keep the registration number visible, not buried. Portals that support a dedicated RERA field should use it; where a listing only has a free-text description, the number should still appear clearly, not in fine print.

Listing Field vs Compliance Requirement

Where Portal Drift Actually Comes From

Two demographic realities of Indian real estate marketing make this drift almost inevitable without a deliberate process. First, most mid-sized developers sell through a mix of in-house sales and multiple external channel partners — in cities like Bengaluru, Pune and Gurugram it is common for a single project to have listings created independently by five or more partner agencies, each optimizing their own portal presence for their own lead capture, with limited coordination back to the builder's marketing team. Second, portal upload workflows differ: one platform's form might default to a "super built-up" field with carpet area optional, while another leads with carpet area and treats built-up as supplementary — so the same person entering the same flat's data on two different portals can produce two different labelled numbers even with good intentions.

A carpet-area-first listing record that both your in-house team and channel partners pull from — rather than re-derive — removes most of this drift at the source, because the number of places a figure can be re-typed (and therefore drift) drops from "every portal, every partner" to "once."

Mini Scenario: Reconciling a Gurugram Project Across Portals

A Gurugram developer launching a Sector 79 residential tower found, during a pre-launch audit, that three portals showed three different price-per-sq-ft figures for the same 3BHK configuration — one portal's number matched the base carpet-area rate, a second had picked up a channel partner's "all-inclusive" figure and mislabelled it as base price, and a third showed a stale rate from an earlier soft-launch phase that had never been updated. None of the three listings was individually fraudulent, but a buyer cross-referencing them would reasonably conclude the builder was being evasive about price. The fix was not complicated — the marketing team built a single pricing-and-area sheet, timestamped it, distributed it to every channel partner with an instruction to re-upload rather than edit their own cached version, and set a recurring 30-day check across the three portals. The complaint risk this closes is real: buyers who feel misled by portal-to-portal inconsistency are increasingly likely to raise it with the state authority rather than simply walk away, because RERA has given them a formal channel to do so.

The Resold-Lead Trap vs Consented Enquiries

There's a second, related cost to fragmented portal listings that developers often underweight: lead quality. When five channel partners each run their own listing for the same project, a single interested buyer frequently ends up contacting multiple partners (or the same partner's listing gets scraped and resold), and the developer pays for the "same" lead several times over through different commercial arrangements — without ever knowing it's the same person. Consented enquiries captured through a single, canonical listing path — where the buyer's data is collected once, with clear consent, under India's Digital Personal Data Protection framework — are structurally different from a resold list: the enquiry traces back to one actual interaction, and the builder is not paying duplicate acquisition cost for one lead recycled across intermediaries. A consolidated leads view that treats every consented enquiry as coming from one system of record — rather than aggregating whatever a partner chooses to forward — makes this distinction visible instead of buried in a spreadsheet.

Pro Tips

• Treat your RERA registration number the way you'd treat a bank account number — one canonical value, checked character-by-character before every new upload.
• Build a quarterly "mystery shop" habit: search your own project name on the major portals and read the listings the way a first-time buyer would.
• Where a portal allows a "last updated" or "as of" date field, use it — a dated figure signals more credibility than an undated one, especially for pricing.
• Give channel partners a locked, non-editable master sheet (PDF or image) rather than an editable spreadsheet they might "improve" independently.
• Flag phase-specific RERA numbers clearly if a project has multiple registered phases — a buyer interested in Phase 2 should never see Phase 1's number.

Common Mistakes to Avoid

• Letting a channel partner's listing go live without the builder's marketing team reviewing area and RERA-number fields first.
• Quoting super built-up area as the headline figure with carpet area buried or absent.
• Leaving a stale listing live after a project's pricing or possession date has been revised.
• Assuming a portal's own RERA-number requirement at upload means the figure will never go stale — portals check for presence, not currency.
• Treating portal listings as "just marketing" that doesn't need the same rigor as the RERA filing itself.

Bringing Listings Under One Roof

The developers who handle this well tend to converge on the same underlying habit: maintain one listing record, syndicate it outward, and audit the outward copies rather than trying to police every partner's independent upload after the fact. Building your project's canonical listing inside a single system — with carpet area, RERA number and pricing basis locked at the source — turns "keeping five portals in sync" from a recurring manual chore into a one-time setup. Combined with a consented-lead pipeline that doesn't depend on resold contact lists, it also means the enquiries reaching your sales team map back to real, traceable interest rather than duplicated noise. If you're weighing how a builder-side platform fits into your existing portal and channel-partner mix, start with the builder overview to see where a canonical listing slots into your current sales stack — and for open questions on how listing data flows through the platform, the help center is the fastest path to a straight answer.

Key Takeaways

• Portal listings on 99acres, Magicbricks and similar aggregators are legally advertisements — they carry the same RERA disclosure logic as print ads, including the registration number and carpet-area basis.
• Most major Indian property portals now require a RERA number at project upload, but that portal-level check does not remove the builder's own responsibility for accuracy.
• Inconsistent carpet-area or price figures across portals are usually the result of multiple channel partners re-keying data independently, not deliberate misrepresentation — but buyers and regulators don't distinguish the two.
• A single canonical listing record, pushed outward to every portal and partner, is the most reliable fix for cross-portal drift.
• Audit your own live listings periodically — a simple search across major portals catches stale or mismatched figures before a buyer does.
• Distinguish base carpet-area price from all-inclusive pricing clearly and consistently across every platform you syndicate to.
• Resold or duplicated leads from uncoordinated channel partners inflate acquisition cost; consented enquiries from one canonical listing path are more traceable and often cheaper per genuine buyer.
• Never let a listing go live — from your own team or a partner — without a quick registration-number and area check first.
• This content is informational, not legal advice; confirm listing and disclosure requirements with your state RERA authority and a licensed professional before finalizing ad copy.

FAQ

Does a property portal's own RERA-number requirement mean my listing is automatically compliant? No. Portals requiring the number at upload is a platform policy, not a substitute for the builder verifying the number is correct, current, and matches the phase being advertised.

What if a channel partner uploads a listing with the wrong carpet area? The commercial risk still sits with the project being advertised inaccurately, regardless of who uploaded it. A locked master sheet distributed to all partners, plus periodic audits, reduces this risk substantially.

Is carpet area the only figure I'm allowed to show in an ad? Built-up or super built-up figures can appear alongside carpet area if clearly labelled, but carpet area — the RERA-defined figure — should not be omitted or subordinated to a larger, unlabelled number as the headline.

According to IBEF's Real Estate Industry in India report (Feb 2026), digital discovery and portal-driven demand continue to be a dominant channel for how Indian buyers first encounter a project, which is exactly why the consistency of what appears on those portals carries outsized weight in a builder's compliance and reputation profile.