Mitasys × Rustomjee · Location Pages Audit

119 location pages reviewed for SEO accuracy & on-page experience.

A page-by-page review of every live location page on rustomjee.com — with before/after recommendations for titles, meta descriptions, URL slugs, project listings, content, FAQs, and a new "Buyers Also Search For" related-searches block.

Open Audit Sheet (119 pages) Jump to worked example ↓

What we did

The audit, in three steps.

We didn't just look at meta tags. We checked every live location page against the live-projects inventory, against Google Search Console traffic patterns, and against the template structure used on the strongest pages in the cluster.

1

Audited every live location page

119 pages across the /mumbai/ and /thane/ subdirectories — crawled, cleaned, and reviewed individually.

2

Cross-referenced with live projects

Every project name and URL on every page checked against the 24-project live inventory. Defunct references flagged for replacement with live alternatives.

3

Wrote before / after / why

Each page now has a Content Update document with specific changes, the rationale, a quality-gate checklist, and an implementation order.

Why this matters

Three outcomes the audit is built around.

SEO uplift

Correct titles, accurate meta descriptions, and clean URL slugs lift organic CTR. Most pages currently use legacy title formats that don't match the new pattern {Primary Keyword} | Rustomjee.

Factual accuracy

Multiple pages still reference projects no longer in the live inventory (Rustomjee Elements at Juhu, Rustomjee Erika at Bandra East, and several others). These mislead visitors and undermine trust.

UX & dwell time

A new on-page "Buyers Also Search For" block at the bottom of each page surfaces related searches as clickable internal links — gives the visitor an obvious next step without leaving the site.

Eight things we audited per page

One Content Update document per page, structured in 8 dimensions.

Each page's document follows the same structure so the writing team can implement consistently. The next section walks through one full example.

01

URL Slug

Does the slug match the H1 in slug form, with no filler words? If not, recommend the correct slug + 301 redirect.

02

Title Tag

Follows the {Primary Keyword} | Rustomjee pattern. No defunct project names. Under 70 characters.

03

Meta Description

Names a live project, uses correct configuration, includes the target keyword and a starting price where relevant.

04

Project Listings

Every project on the page cross-checked against the live inventory. Defunct projects → live replacements.

05

Headings (H2/H3)

Page structure matches the location-page template — Available Projects, contextual intro, topic H2s, FAQ.

06

Body Content

Target keyword appears in the first 100 words. Page word count in the 700–900 range.

07

FAQs

7 questions covering price, configurations, RERA, connectivity, schools, projects, and adjacent options.

08

Related-Searches Block

New H2 after the FAQ — 'Property Buyers Also Search For' — with a numbered list of related pages.

Worked example

Residential Properties in Juhu — the audit applied end-to-end.

This page currently ranks at average position 8.8 with 20 clicks and 1,919 impressions over the last 90 days. Below: every dimension, with the recommended change and the reason.

Target URL /mumbai/residential-properties-in-juhu/ Target Keyword residential properties in juhu

1. URL Slug

Check: slug equals H1 in slug form, target keyword only

Before/mumbai/residential-properties-in-juhu/
After/mumbai/residential-properties-in-juhu/ (no change)
WhySlug already matches the H1 in slug form and contains only the target keyword. No filler words like "explore" or "premium" — convention satisfied. Several other pages in the audit do need slug fixes (and 301 redirects); this one happens to pass.

2. Title Tag

Pattern: {Primary Keyword} | Rustomjee

BeforeLuxury Residential Property in Juhu | 3, 4 & 5 BHK Flats | Rustomjee Elements
AfterResidential Properties in Juhu | Rustomjee
WhyThe current title names Rustomjee Elements — a project no longer in the live inventory. It also claims "5 BHK" inventory, but live Juhu offers only 3–4 BHK. The new title removes both errors and adopts the standard pattern. New length: 39 characters (well within the 70-char limit).

3. Meta Description

Names a live project, uses correct configuration, includes target keyword

BeforeLuxury 3, 4 & 5 BHK Flats in Juhu — Rustomjee Elements occupies an expansive 5-acre premium location, featuring 3, 4, and 5 BHK residences in Juhu.
AfterDiscover Rustomjee's residential properties in Juhu. Rustomjee Ashiana offers exclusive 3–4 BHK luxury residences on Gulmohar Road with private decks. From ₹8.2 Cr.
WhyEvery fact in the current description is wrong: it names a defunct project, claims a "5 BHK" inventory that doesn't exist, and describes a "5-acre premium location" that applied to Elements. The new version is anchored to the live project (Ashiana), names the actual configuration (3–4 BHK), and gives a verified starting price. New length: 156 characters.

4. Project Listing

Defunct → Live replacement

BeforeRustomjee Elements, Juhu — not in the live inventory; the linked project page likely 404s.
AfterRustomjee Ashiana, Juhu — Premium segment (₹7–15 Cr), 3–4 BHK. The only live Rustomjee project in Juhu today.
WhyRustomjee Elements is not in the live-projects inventory and the linked URL likely 404s. The replacement — Ashiana — is the only live Juhu project per the authoritative inventory. The listing should also move from inline H3 into the "Available Projects" CMS section per the location-page template.

5. Headings (H2/H3)

Template: H1 → Available Projects → Contextual Intro → Topic H2s → FAQ → Buyers Also Search For

Before — current page structure H1: Residential Properties in Juhu
H3: Rustomjee Elements, Juhu (defunct)
H2: Introduction
(no other sections)
After — full template H1: Residential Properties in Juhu
H2: Available Projects (Ashiana)
H2: Juhu's Standing as Mumbai's Celebrity-Owned Address
H2: Why Choose Rustomjee in Juhu
H2: What Defines a Juhu Residential Address
H2: Connectivity and Daily Life in Juhu
H2: Configurations and Pricing for Juhu Residences
H2: Frequently Asked Questions (7 H3 questions)
H2: Juhu Property Buyers Also Search For (related links)
WhyThe page is currently 1 H1 + 1 misplaced H3 + 1 H2. The template the cluster's strongest pages follow has 8 H2 sections covering Available Projects, contextual intro, locality framing, brand reason-to-believe, locality attributes, connectivity, configurations + pricing, FAQ, and related searches. Restructuring to that gives both readers and search engines a clearer page structure.

6. Body Content

Target keyword in first 100 words; total length 700–900 words

Before"Home to celebrities and superstars alike, Juhu is an upmarket neighbourhood in Mumbai. Famous for the sprawling Juhu beach…"

~50 words total. The target keyword "residential properties in Juhu" doesn't appear anywhere in the body.
After"Residential properties in Juhu sit at the intersection of Mumbai's most cinematic locality and one of the city's tightest luxury supply lines…"

~800 words across 5 topic sections. Target keyword appears at words 1 and 47 — within the first 100 words, twice.
WhyThe current body is two sentences. There's no signal to Google or the reader about what's on this page beyond the title. The expanded body gives the page substance to rank on — and the keyword placement in the opening lifts on-page relevance for the head term.

7. FAQs

7 buyer-intent questions, 2–3 sentence answers

BeforeNo FAQ section.
After — 7 questions • What are the live residential properties in Juhu by Rustomjee?
• What is the price range for residential properties in Juhu?
• Are residential properties in Juhu RERA registered?
• How is Juhu connected to BKC and the airport?
• What schools are accessible from residential properties in Juhu?
• What configurations are available at Rustomjee's residential project in Juhu?
• Are there other Rustomjee projects near Juhu?
WhyAn FAQ block does three things at once: it answers buyer questions, captures featured-snippet potential, and surfaces facts Google's AI overview can quote. The questions are drawn from common buyer intents (price, RERA, schools, connectivity) plus the page's specific live-project context.

8. "Buyers Also Search For" Related-Searches Block

New H2 after the FAQ — turns related Rustomjee location pages into on-page internal links

BeforeNo related-searches block. Visitor reaches the bottom of the page and has no obvious next step except a back-button.
After — new H2 + 6 links Juhu Property Buyers Also Search For
  1. Luxury 3 BHK Flats in Juhu
  2. 5 BHK Flats in Juhu
  3. Flats in Juhu
  4. 4 BHK Flats in Juhu
  5. New Projects in Juhu
  6. 5 BHK Flats in Mumbai
WhyThis is the change with the broadest impact across the audit. Every one of the 119 pages gets a "[Locality] Property Buyers Also Search For" block at the bottom — surfacing 6–8 topically-related Rustomjee pages as clickable internal links. The visitor stays on the site; Google sees a denser internal-link graph; and each link is a natural keyword variation.

A closer look

The "Buyers Also Search For" block, explained.

One small block. Network-effect impact.

The block sits at the very bottom of the page, immediately after the FAQ. It's a simple H2 plus a numbered list of related Rustomjee pages — but it does several things at once.

For the visitor: a clear, useful next step. If they came in on "Residential Properties in Juhu" but actually want a 3-BHK Juhu flat, the next click is right there.

For Google: a denser internal-link graph across the location cluster, with every anchor being a natural keyword variation rather than a generic "click here".

For the cluster as a whole: 119 pages × 6–8 outbound links each = a small but meaningful uplift in how PageRank flows between related pages on the site.

↓ Page bottom — after FAQ

H2

Juhu Property Buyers Also Search For

  1. Luxury 3 BHK Flats in Juhu
  2. 4 BHK Flats in Juhu
  3. New Projects in Juhu
  4. …

Access

How to dig into the full audit.

Two ways in. The Sheet is the index — one row per page with a clickable link to that page's Content Update document. The folder is the full set of 119 Google Docs if you'd rather browse.

1

Audit Index Sheet

One row per page (119 in total). Columns: URL · Target Keyword · Google Doc (clickable) · Purpose. The fastest entry point.

Open Sheet
2

Drive Folder (119 Docs)

The same Content Update documents, organised in a single Drive folder for browsing. Each Doc is self-contained with 9 sections of recommendations.

Open Drive Folder

Next steps

Three things to do once you've reviewed the audit.

  1. Review the index Sheet. Open a handful of Content Update Docs to get a feel for the format. The Juhu example above is representative of the most thoroughly-affected pages; many pages need lighter touch-ups.
  2. Flag any project facts that disagree with our inventory. We've used the live-projects list as authoritative — if any of those facts have shifted, tell us and we'll re-issue.
  3. Decide rollout phasing. The audit is internally tiered by GSC traffic (Tier 1 = top 30 pages by clicks). Rolling out Tier 1 first captures the largest SEO impact fastest.