Most developer websites are organised the way the company is organised. Homepage, about, a projects list, one page per project, contact. That structure answers a single question: what does this builder own. Nobody types that question into Google.
Demand arrives as a locality and a number
New Town. Rajarhat. Ballygunge. Behala. Garia. Joka. EM Bypass. Those words are the demand. Bolted to them is a bedroom count and a budget band, and that pairing is the unit a Kolkata buyer searches in.
A locality is not a postcode, either. Rajarhat and New Town get used interchangeably by people who do not live in either. Action Area I is not Action Area III, and anyone who has waited for an autorickshaw in both knows it. Joka means the metro extension to one buyer and the far end of Diamond Harbour Road to another. Behala Chowrasta, Sakher Bazar and Thakurpukur are three separate conversations about the same stretch of road. Flatten those distinctions on your website and the page reads as though it were written in another city, which is precisely how a buyer decides not to trust you.
Three query shapes, three different pages
"3 BHK flats in New Town"
Inventory-shaped. The buyer wants a set, not a single project. If the only thing you own at that URL is a project page, you are answering a narrower question than the one asked. What matches is a stable listing page for that locality and configuration, holding every relevant unit you have, with the ones that no longer exist marked rather than removed.
"under construction projects near Garia"
Status plus proximity. Two things most property sites never expose to search. Construction status usually lives inside a PDF or a badge rendered by JavaScript, so no crawler ever sees it. Put possession status in text, in the heading, with a stage and a target quarter. "Near Garia" also deserves honesty about what near means in travel minutes rather than kilometres.
"flat price per square foot in Behala"
The research query, and the one developers refuse to answer. Somebody at this stage is not going to enquire today. They are calibrating. A page that explains what drives the rate in that pocket, carpet against built-up against super built-up, floor rise, corner and facing premiums, parking charged separately, does two things. It ranks against portal content written by nobody in particular, and it arrives in front of a buyer months before your competitors do.
One project, one URL, four different jobs
The page does not get rewritten at each stage. It gets re-pointed.
Pre-launch. No price, no promises, no registration number to quote yet, so the page can carry little. Location, the intent, an interest form. Thin by necessity, and it should be honestly labelled as pre-launch rather than dressed up as a live project.
Launch. The page fills out. Configurations, unit sizes, the master layout, the specification list, registration details, the possession target.
Under construction. Now the page earns its rankings on updates. Dated construction photographs, floor-slab progress, what has been handed to the contractor. This is the stage where sites go silent for three years and lose the ground they gained at launch.
Ready to move. The vocabulary of the search changes completely, and so should the page. "Ready to move" and "immediate possession" are queries in their own right, and they carry the strongest intent in the category.
Sold out is not a reason to delete the page
A project that has sold every unit still has a page that has spent years accumulating links, brand searches and the trust that comes with age. Deleting it throws all of that away and hands the URL to a portal listing the resale market.
Keep it. Mark it sold out plainly at the top. Leave the plans, the specification and the completed photographs in place, because they are now the strongest evidence you have that you finish what you start. Point the enquiry path at the nearest live project in that locality rather than at a dead form. Where a project genuinely no longer merits its own page, redirect it to the locality page, never to the homepage, which is where redirects go to be ignored.
Your own project name belongs to 99acres
Type the name of almost any Kolkata project into Google. The developer's own page is rarely first. 99acres, MagicBricks and Housing.com hold those positions because their pages are structured for that exact query while yours is a slideshow with the name in an image.
You will not remove them. You can outrank them for your own name, which is a lower bar than it sounds. Their page is generic by design and cannot say what yours can: the current construction stage, the actual availability by tower and floor, the registration number, the specification in full, the location written by somebody who has stood on the plot. Sort out the page title, the URL and a single clear H1 carrying the project name and the locality. Publish the brochure content as text instead of as a download. Add the plans as real pages. The portal has authority; you have the facts.
Locality guides that survive being read
A locality page fails when it reads like tourism copy. Emerging destination, excellent connectivity, all modern amenities. Nobody believes it and nothing in it can be checked.
What holds up is specific and slightly unflattering. How long Sector V takes from that address at nine on a Tuesday. Which schools are a walk and which are a bus. What the water situation is. Which plots around you are built and which are still hoardings. Whether the promised metro station has piers in the ground or only a notification. A buyer arrives at that page suspicious and leaves it convinced, and it will rank for the guide queries that project pages never touch. Krishna Realtors and Shree Vallabh Infra, which share an owner, sell into pockets of the city where this layer is worth more than the project pages, because geography is the first filter a Kolkata family applies. Common ownership also means the locality tier can be built once and serve both names, provided the project pages beneath it stay genuinely separate.
What to build first
Locality pages, then the configuration listings, then the project pages, then the guides. That order is deliberate: the top of the funnel is where you are absent and where the portals are weakest. Paid coverage for a launch window is a separate discipline with its own constraints, covered in Google Ads for property developers. If the site cannot hold a locality tier or expose possession status as text, the fix belongs upstream in real estate website development. The wider picture sits on our real estate marketing hub, and the discipline itself on our SEO service page.
Digi Kydo, 17R Dover Terrace, Ballygunge, Kolkata, West Bengal 700029. Call +91 98305 45687 or write to [email protected].