RERA Rules for Project Websites and Landing Pages

The performance-marketing team has the campaign ready to go: a Google Ads push, an Instagram carousel, a retargeting sequence, all pointing at a single project landing page built two weeks ago by a freelance developer. The page looks sharp — hero video, floor plans, a pricing table, a lead-capture form with a "Get Callback" button. Nobody on the marketing side has asked whether the page itself is a RERA advertisement, because it doesn't feel like one — it feels like a website. It is, legally, exactly an advertisement, and the moment paid traffic starts landing on it, every disclosure gap on that page becomes a live compliance exposure sitting behind the ad spend, not a design nitpick to fix later.

This is the gap this guide closes: what a project website or campaign landing page must carry under RERA, section by section, plus what a 2023-onward data-protection layer adds on top for any page with a lead form.

Why a Website Is "Advertisement" Under RERA

Section 2(b) of the Real Estate (Regulation and Development) Act, 2016 defines "advertisement" broadly — any document, notice, circular or communication, in any form, issued with a view to selling a real estate project. A project microsite exists for exactly that purpose: converting a visitor into a lead or a booking. State RERA authorities have consistently treated project websites and campaign landing pages as advertisements requiring the same registration-number and disclaimer treatment as a print ad or hoarding — the medium changed, the underlying solicitation intent did not.

This isn't an abstract legal point for developers running digital-first campaigns. According to the IBEF Real Estate Industry in India report (February 2026), the sector's institutional investment reached US$10.5 billion across 78 deals in 2025, alongside a broader market trajectory toward US$1 trillion by 2030 — growth increasingly driven by digital lead generation rather than walk-in footfall. A landing page is, for many projects today, the single highest-traffic advertising surface a developer runs, which is precisely why a disclosure gap there carries outsized exposure relative to one static banner.

Step by Step: The On-Page Disclosure Checklist

Work through a project page top to bottom the way an auditor would, rather than trusting that "it's somewhere on the page."

1. RERA registration number, above the fold. The number should appear in the hero section or header — not buried in an accordion at the bottom of the page that most visitors never open.
2. QR code, where the state requires it. Where the launch state's RERA authority requires a QR code on advertisements (MahaRERA is a prominent state-level example of this), the same QR treatment used on print and hoarding creative should carry onto the website, ideally linking through to the project's page on that state's RERA portal.
3. Carpet-area-first pricing. RERA's carpet-area disclosure norm means pricing and area figures on the page should lead with carpet area (not a "super built-up" figure alone) — a rule that applies to how the pricing table is built, not just to the sale agreement later.
4. Standard disclaimer text. A disclaimer directing visitors to the relevant state RERA website for the sanctioned plan, layout, and other project particulars belongs in the footer of every page a visitor might land on, including deep pages like a floor-plan gallery.
5. Consent checkbox on the lead form. Under the Digital Personal Data Protection Act, 2023, any form collecting a visitor's phone number or email for follow-up should carry a clear consent mechanism — a checkbox stating the purpose of collection (contact regarding this project) — rather than an implied "by submitting you agree" buried in tiny type.
6. Per-state registration numbers on multi-state campaigns. A national microsite serving buyers in Maharashtra, Karnataka and Telangana simultaneously (for a developer with projects in multiple states, or a landing page that geo-targets) needs to display the correct registration number for the project actually being advertised to that visitor — not a single number assumed to cover every state.

Disclosure Placement by Page Element

Geographic and Regulatory Specifics

MahaRERA's advertising norms have, as a notable state-level example, extended beyond the baseline registration-number requirement to direct that a QR code appear on advertisements, giving a visitor a direct scan-through path to the project's official record on the MahaRERA website. Other states maintain their own advertising circulars, and because these are updated periodically, the specific requirement in a developer's launch state should be confirmed against that state's current RERA website as of the campaign date rather than assumed to mirror Maharashtra's approach.

The Digital Personal Data Protection Act, 2023 (DPDP Act) adds a layer that sits alongside, not inside, RERA's advertising rules: any landing page collecting personal data through a lead form is a "data fiduciary" interaction, and the consent captured should be specific, informed and revocable — meaning a clear notice of what the phone number or email will be used for, ideally with a link to a privacy notice, rather than a blanket "I agree to terms." For a platform whose value proposition to buyers rests on consented, purposeful data collection rather than data harvesting, this consent layer is not a compliance afterthought — it's a differentiator that buyers increasingly notice.

Multi-state and NRI-facing landing pages deserve particular care. A developer running one national campaign that geo-targets NRI buyers across UAE, US and UK audiences, while promoting projects located in Hyderabad, Pune and Bengaluru, may be tempted to build a single generic landing page for cost efficiency. But if that one page shows content for multiple projects across multiple states, it needs to display the correct RERA registration number matched to whichever project is actually being shown to that visitor — a single "catch-all" number is not a substitute for project-specific disclosure, even on a page built for operational convenience.

Mini Scenario: A Hyderabad Microsite, Audited and Corrected

A mid-sized developer's Hyderabad project microsite, live for three months and driving a steady stream of Google Ads traffic, is pulled in for a routine compliance review ahead of a new funding round. The audit finds: the RERA number sits correctly in the header; the footer disclaimer is present on the homepage but missing from the standalone floor-plan gallery page that a large share of paid traffic lands on directly; the pricing table shows only a "super built-up area" figure with no carpet-area breakdown; and the lead form collects phone numbers with a plain "Submit" button and no consent checkbox. The corrections are straightforward once identified: the footer component (with disclaimer and RERA number) is applied site-wide rather than per-page, closing the floor-plan-gallery gap; a carpet-area column is added next to the existing area figure in the pricing table; and a consent checkbox with a one-line purpose statement is added ahead of the form's submit button. None of these fixes required rebuilding the page — they required auditing every page a paid-traffic visitor might actually land on, not just the homepage the internal team was used to reviewing.

Pro Tips for Compliant Landing Pages

• Apply the RERA disclaimer and registration number as a shared site-wide footer component rather than hand-copying it onto each page — this closes the "forgot the deep page" gap seen in the Hyderabad scenario above.
• Build carpet-area figures into the pricing table as a first-class column, not a footnote, so the carpet-area-first framing holds even when the table is skimmed.
• Treat the lead-capture consent checkbox as a template element reused across every campaign landing page, so a new page built quickly for a flash promotion doesn't skip it under deadline pressure.
• For multi-state or multi-project pages, build the RERA number as a dynamic field tied to the project/state actually being shown, rather than a hardcoded string in the page template.
• Re-audit live landing pages periodically, not just at launch — a registration renewal, a project-scope change, or a new state requirement can make a page that was compliant at launch drift out of compliance months later.

Common Mistakes to Avoid

• Publishing a footer disclaimer on the homepage only, while paid traffic actually lands on deep pages (a specific floor-plan or amenities page) that never carry it.
• Quoting only super built-up area in a pricing table without a carpet-area figure alongside it.
• Treating the lead form's "Submit" button as implicit consent rather than adding an explicit, purpose-stated checkbox under the DPDP Act.
• Building one landing page template for a multi-project or multi-state campaign with a single hardcoded RERA number that doesn't match every project shown.
• Letting a page's RERA number go stale after a registration renewal or scope change because nobody owns re-checking live pages after launch.

Bringing It Together on One Platform

The pattern behind most of these gaps is the same one that shows up in print and video compliance too: the RERA number and project particulars live in one place (a compliance spreadsheet, a PDF from the state RERA portal) while the landing page lives somewhere else entirely (a freelance developer's codebase, a third-party landing-page builder), and the two drift apart the moment either one is updated without the other. DrawMagic's listings tool gives you a canonical, disclosure-complete project listing that a landing page can link to or reference directly, so the microsite's RERA number, carpet-area figures and disclaimer text stay tied to the same underlying record rather than a copy-pasted snapshot from launch day. And because project setup is where the RERA number, carpet areas and approvals get captured once, at the source, every downstream page — the microsite, the print creative, the video walkthrough — draws from the same figures instead of three separately maintained versions that can quietly disagree with each other.

That consistency matters most under audit pressure, exactly like the Hyderabad scenario above: when a funder, a state RERA authority, or a buyer's lawyer asks to see the current disclosure on a specific page, the answer should be a quick lookup against one source of truth, not a scramble across multiple systems to confirm which number is actually correct today.

Key Takeaways

• A project website or campaign landing page is legally an "advertisement" under RERA the moment it's used to solicit buyer interest, carrying the same disclosure obligations as print and hoarding ads.
• Place the RERA registration number above the fold, not buried at the bottom of the page.
• Apply the footer disclaimer and registration number site-wide, including deep pages like floor-plan galleries, not just the homepage.
• Lead pricing tables with carpet-area figures rather than super built-up area alone, consistent with RERA's carpet-area disclosure norm.
• MahaRERA's QR-code requirement on advertisements is a state-level example — confirm your launch state's current requirement directly.
• Add an explicit, purpose-stated consent checkbox to any lead-capture form, in line with the Digital Personal Data Protection Act, 2023.
• Multi-state or multi-project microsites need the registration number matched to the specific project/state actually shown to each visitor.
• Re-audit live landing pages periodically — a page compliant at launch can drift out of compliance after a registration renewal or scope change.
• Centralising project data on DrawMagic's builder portal keeps a landing page's disclosures tied to one authoritative record instead of a stale copy.

FAQ

Does a "coming soon" pre-launch page need the same disclosures as a full project page? Any page soliciting interest, bookings, or contact details for a project ahead of RERA registration carries its own separate compliance considerations beyond disclosure placement, and should be reviewed with a licensed professional — a pre-launch page is not automatically exempt from RERA scrutiny.

Is a PDF brochure linked from the landing page also considered an advertisement? Generally yes — a downloadable brochure used to solicit interest in a project falls under the same broad "advertisement" definition and should carry the RERA number and disclaimer, consistent with the treatment given to the webpage that links to it.

What if the landing page is built and hosted by a third-party agency, not the developer directly? The developer as promoter typically retains the underlying compliance responsibility for advertisements about their project regardless of who built or hosts the page — agency-built pages should go through the same disclosure review as any in-house page.

Ready to bring your project's disclosures onto one page you control? Start on the builder portal to set up your project record and connect it to a compliant, disclosure-complete listing — and check DrawMagic's help resources if you have questions about mapping an existing landing page to the platform. This article is for general information only and is not legal advice; confirm current requirements with your state RERA authority and a licensed professional before launching any campaign.