Indian Cities — Industrial Output and Real Estate

Detailed industrial sector profiles, key company ecosystems, real estate market data, and trade infrastructure intelligence for 91 Indian cities across all tiers. Essential for FDI targeting, mandate origination, and market entry strategy.

Totality lens · 32 points to ponder · 16 user POV + 16 developer POV · this hub

User POV — for the practitioner navigating the Cities hub

Eight dimensions

1 · Possibility

A practitioner can in principle navigate the entire AJG city graph — 1,584 cities across 197 countries spanning Tier-1, Tier-2 and Tier-3 economic hubs — using a single hub view that exposes filtering by tier, region, GDP-band, FTA membership, port-proximity, and trade-corridor adjacency. The hub is designed so that any cross-cut (for instance, Tier-2 cities in ASEAN with FTA preferential access to the EU) collapses to a single URL with a deterministic query string.

2 · Plausibility

Realistically, most users will engage with at most 30-50 cities meaningfully — typically the top-20 cities matching their corridor of interest plus a long-tail of one-off lookups. The hub is built for breadth-of-coverage to anchor SEO and scope, but the real conversion path narrows quickly once a user identifies a target geography. Designing for the long tail without privileging the head would be a mistake; the hub does both by separating the directory grid from the spotlight band.

3 · Probability

In practice, 60-70 percent of inbound traffic to the cities hub lands on individual city pages via search and traverses to no more than 2-3 adjacent cities before either converting (mandate-submit, contact, tools cross-link) or exiting. Only 10-15 percent uses the filter UI proactively; the rest treat the hub as a navigation artefact. This means filter UX matters less than the spotlight curation and the per-city template depth.

4 · What works

What works: a four-band grid (T1 elite / T1 / T2 / T3) that loads progressively, a filter row pinned at the top of the hub with country and region collapsible facets, prominent cross-links into FTAs / corridors / blocs from the city detail pages, and a 32-point TOTALITY block on each top-20 city for evaluator depth. Mandate-submit CTAs anchored at the hub bottom convert at 0.6-0.9 percent of hub sessions in the v149 cohort.

5 · What doesn't work

What does not work: maps as the primary navigation (latency-heavy, hard to crawl, weak on mobile, low conversion), city-comparison tables that require selecting four-plus cities (most users compare two), and gating any city detail behind a sign-up wall. Earlier hub iterations that emphasised a world-map landing buried text-search and reduced indexability — abandoned at v100 in favour of the current grid-first design.

6 · Common pitfall

The common pitfall is over-investing in city detail depth before the directory is fully populated. A handful of beautifully-rendered city pages with a sparse hub directory underneath signals 'demo' rather than 'reference'. The cities hub strategy at AJG is the inverse: ship every city as a serviceable stub first, then deepen the top-20 at TOTALITY depth, then deepen the next 100, then continue down the long tail.

7 · Counter-intuitive insight

Counter-intuitively, traffic to Tier-3 cities (small, less-known centres) often outperforms Tier-1 traffic on conversion-per-session because the search intent is sharper. A user querying a Tier-3 industrial cluster usually has a specific operational reason; a user querying London or Singapore may be researching at a much earlier stage of intent. The hub honours this by giving the same template depth to T3 as to T1.

8 · Highest-leverage move

The single highest-leverage move is to deepen the top-20 cities at 32-point TOTALITY first (done at v149.4.6 ALPHA), then bring the next 80 cities to layer-A through layer-H depth, then ensure every city has at minimum a 1,200-word factsheet. The compounding effect — each deepened city adds inbound links for adjacent cities and corridors — means depth at the head improves indexability across the entire 1,584-city long tail.

Eight user intents

9 · Who gains most

Operators evaluating where to base operations, exporters scoping target markets, founders comparing capital ecosystems, advisors building short-lists for clients, journalists researching geographic clusters, and students doing market-entry coursework. The most engaged segment is the operator-evaluator with a 6-12 month decision horizon; they typically traverse 8-15 cities before committing.

10 · Irreducible essence

The irreducible essence: a single canonical directory of every city in the AJG entity graph, with depth-stratified detail pages and consistent cross-links into FTAs, corridors, blocs, ports, SEZs, lexicon and tools. The hub is not a pretty map; it is the shortest path from 'I need a city' to 'I have decided on this city plus three credible adjacents'.

11 · Optimal timing

Best entered at the start of a market-entry decision (after vertical and corridor are roughly chosen but before the specific city short-list is locked), and re-entered at the cost-modelling stage to verify city-level inputs (rents, salaries, port fees) against the ATLAS toolkit calculators. Re-entry six months later is also valuable when conditions have moved (FTA milestones, currency, corridor capacity).

12 · Where (sub-areas)

The hub is global but weights by the AJG focus geography: India (289 cities), China (234), USA (205), Western Europe (UK 55, Germany 49, France 47), Japan (43), and Russia (33). Smaller markets get coverage proportional to their economic significance plus a deliberate over-weight for emerging clusters that AJG advisors actively support. Filter by region to bias the grid.

13 · Why misunderstood

Cities are misunderstood as interchangeable lists. They are not — the difference between Mumbai and Bengaluru for a Tier-1 supplier mandate is enormous. The hub exists because every other publicly-available city directory either over-aggregates (continent-only) or under-aggregates (one-page-per-city with no graph context). The hub gives both: a single graph view plus per-city depth.

14 · Highest-leverage sub-paths

For market-entry research, the highest-leverage sub-paths are: (a) start with the corridor view, then drill into cities; (b) cross-reference FTA preferential access on the city detail; (c) check port-proximity and SEZ availability on adjacent cities; (d) use the city-comparator (TRAV side) to triangulate cost-of-living against operator salary band. Skip the world map.

15 · Whose advice to trust

Trust: locally-resident operators with five-plus years on the ground in the city you are evaluating; AJG principals (we have lived in or operated from a meaningful subset of the cities); honest port and customs handlers (they know what flows actually move). Discount: tourism boards, real-estate brochures, and any source that does not disclose its commercial relationships to the city.

16 · How to proceed differently

Proceed by listing the three to five corridors that match your vertical, intersecting them with the cities hub filter to get a 30-50 city candidate set, then dropping into the top-three city detail pages on each corridor to read the TOTALITY block. From there, run the ATLAS toolkit (founder-readiness for an early-stage view, living-cost-arbitrage for an operator view) on the leading two cities to get cost and readiness deltas before committing.

Developer POV — for the architect, maintainer, future contributor to this hub

Eight dev dimensions

17 · Data architecture

The cities hub composes from data/cities-tier-data.php (34 cities × 33 fields for the deep tier-1), data/cities-global.php (666 global-city graph), data/cities-expansion.php (top-N per country, 1,158 cities), data/cities-tier3.php (426 tier-3 additions, total 1,584). Helpers: ajg_cities_all(), ajg_cities_filter(), ajg_city_by_slug(). Single-file render via cities.php hub at root, individual city pages routed through city-template.php (Indian) or global-city-template.php (rest of world) under the front-controller pattern. Zero database, zero runtime API.

18 · Schema markup

CollectionPage schema fires on the hub with ItemList of all cities; each city detail emits Place + AdministrativeArea + GeoCoordinates + ContainedInPlace (country) JSON-LD. BreadcrumbList walks Home → Cities → {Region} → {Country} → {City}. WebSite + SearchAction at the homepage cascades into the hub. The 32-point TOTALITY block emits TechArticle on top-20 cities. FAQPage on the hub answers 'how is the city directory built', 'how do I filter', 'what does each tier mean'.

19 · Internal linking

Forward to /ftas/, /blocs/, /corridors/, /institutions/, /tools/landed-cost-calculator.php and /tools/living-cost-arbitrage.php. Outward from each city to adjacent cities (3-5 nearest by graph distance), to its country page, to its continent page. Cross-content injector pulls Library + ScopeScape matches on tokens 'city', 'urban', 'metro', 'cluster'. Link weaver hyperlinks all 1,584 city names automatically across the entire site.

20 · Page-speed posture

The hub renders <80ms server-side at p95. The grid uses CSS-grid with deferred image loading; no client-side framework, zero blocking JS. Critical CSS inlined; design-tokens.css deferred via media-swap pattern (per v149.4.6 PageSpeed-100-v6 fix). HTML payload <90KB pre-gzip for the full 1,584-city grid. Lighthouse Performance held at 95+ on mobile, 99+ on desktop as of v150.1.

21 · Mobile UX

Hub grid collapses to a single column at <640px with horizontal-scroll filter pills. Each city card is a 48-px tap target minimum (per SO #57); 16-px body type, 1.6 line-height. The 32-point TOTALITY block on city detail collapses to one cell per row on mobile with section-headers sticky. Footer factsheet cards reflow 2-up on phones, 4-up on tablets, 6-up on desktop.

22 · Accessibility

WCAG 2.1 AAA on body text contrast (per SO #11 strict palette: navy #0B2447 on white = 14.83:1). All filter controls have aria-label and aria-expanded. The 32-point TOTALITY block uses semantic article + section + heading hierarchy; cell tags are span with role="text". Skip-to-content link present. Focus rings honour the navy + gold combination at 3-px width per the unified-chrome accessibility-toolbar.

23 · SEO saturation

Every city URL emits unique title, meta-description, canonical, OG + Twitter card with city-specific image, JSON-LD per the schema_markup field, dateModified from the data file mtime, and a 1,200-word minimum body. Per SO #2 data-anchored SEO. The hub itself is canonical at /cities/ with rel=prev/next pagination across the four-tier grid views. Sitemap entries live in sitemap-cities.xml (1,584 URLs).

24 · Extensibility

Adding a new city requires: append a row to data/cities-{tier}.php with 33 standard fields; the hub picks it up automatically on next request. Adding a new field across all cities requires touching the template (city-template.php or global-city-template.php) plus a data-migration helper script under admin/. Adding a new tier (say, Tier-4 micro-cities) is a 30-line change to the hub filter logic plus one new data file.

Eight dev intents

25 · Maintainer audience

Maintained by the AJG principals (Amit Jain in London, Vinod Kumar Jain in Panchkula) plus the cron-driven freshness layer at admin/master-refresh.php. Future contributors will need to understand the cities-tier-data → cities-global → cities-expansion → cities-tier3 layering and the city-template + global-city-template split. The 32-point TOTALITY block is currently authored by the principals for top-20; subsequent batches follow the BRAVO/CHARLIE pattern.

26 · Architectural commitment

For the architect: the cities hub is the canonical entry point for one of the four primary URL surfaces (cities + ftas + blocs + corridors form the multilateral spine). The architectural commitment is that any city referenced anywhere on the site must resolve to a real page; per SO #33 ZERO 404, no broken city links anywhere. The architectural commitment is that the hub remains <100KB pre-gzip even as the city count grows.

27 · Refresh cadence

Refresh cadence: monthly via admin/monthly-update.php (touches dateModified, regenerates city-tier counts, reruns sitemap-cities). New cities are added in version-batches (v15 mega-expansion brought 666→1,584). The 32-point TOTALITY block was added at v149.4 ALPHA-3a-g across 7 sub-batches; v151+ does not regress this depth. PageSpeed audit runs in admin/pagespeed-audit.php weekly.

28 · File map

Files: cities.php (hub, root), city-template.php (Indian city detail), global-city-template.php (global city detail), data/cities-tier-data.php (deep T1), data/cities-global.php (graph), data/cities-expansion.php (top-N/country), data/cities-tier3.php (T3 expansion), includes/totality-cities-block.php (32-point block), data/totality-cities-32point.php (block content). Sitemap: sitemap-cities.xml.

29 · Existence rationale

The hub exists at this fan-out depth because city-level intelligence is where AJG's differentiation is sharpest — competitors stop at country-level. The 32-point TOTALITY block is on cities-not-everywhere because cities are the most heavily-trafficked entity-type in our analytics; deepening lower-traffic entities first would mis-prioritise crawl budget and authoring effort.

30 · Highest-leverage extension

For maintainers: the highest-leverage extension is to push the 32-point TOTALITY block from top-20 to top-100 cities (BRAVO and beyond). The second-highest is to add a per-city corridor-tagging field so the hub filter can do corridor-cross-section without joining tables at request-time. The third is a per-city FTA-eligibility roll-up so the cities-hub doubles as an FTA-by-city lookup.

31 · Authoritative sources

Authoritative for code structure: the AJG SO registry (1-96+) governs every architectural decision. For data: the principals' on-the-ground experience plus the public sources cited per-page in the methodology. For SEO: PageSpeed audit + Lighthouse PDFs reviewed quarterly. Defer to: nobody on principals' content; defer to platform host (Nestify) on infrastructure constraints.

32 · Maintenance procedure

Proceed by reading docs/ROADMAP-v138-v200.md for the long-arc plan, then admin/coverage-tree.php for current state, then admin/command-center.php for the sentinel registry. Make changes in the order: data file → helper function → template → injection → sentinel → version bump → smoke test → coverage-tree update → command-center update → ship. Never skip the smoke test.

Cities Directory in the cross-Crucible framework

The /cities/ surface holds 110 hand-curated city pages (per v207.0 inventory recon) plus the GeoNames 231,715-city dataset reachable via the entity-view router when the curated city-master does not contain the requested slug. The Q2 verdict at v207.7 is to KEEP CURRENT 110 + add cross-Crucible synthesis — NOT to expand to a 2,326-city per-city URL surface (that's a separate v208.x consideration). The cross-Crucible angle below decodes the city-level decision-pattern: cities are not just lookup-table entries, they're multi-Crucible decision-points where Cost + Visa + Live + Business + Travel + Work compound into a single residence/operations choice.

Connect to Crucibles

Live atlas → Cities' lifestyle dimension — Mercer Quality of Living + OECD Better Life + EIU Liveability + Numbeo + WHO Health composite for 1,584 cities. The /cities/ surface lists the city; Live Crucible scores it on comparable scales.

Cost atlas → Cities' cost dimension — Numbeo cost-of-living + Mercer + EIU + UBS + World Bank ICP composite. /cities/ lists the city; Cost has the comparable PPP-adjusted dollar costs.

Visa atlas → City-tied residency considerations — Lisbon for D8/IFICI; Dubai for Golden Visa; Singapore for EP; London for Skilled Worker; New York for E-2/L-1; Mexico City for Permanent Resident. The city is often the proxy for the residency route; Visa Crucible has the route detail.

Business atlas → City-tied incorporation and operations considerations — Singapore for Pte Ltd + ASEAN; Dubai for Free Zone; Estonia (Tallinn) for OÜ; London for UK Limited; Delaware-Wyoming-Nevada for US-domestic optimisation. Business Crucible has the structuring detail.

Work atlas → City-tied labour-market depth — Bengaluru + Hyderabad + Pune for Indian engineering pool; Mexico City + São Paulo for LatAm; Singapore for APAC commercial; London + NYC for global commercial. Work Crucible has the labour-market data per city.

Travel atlas → City-tied air-connectivity + transit-time considerations — Singapore + Dubai + London + Frankfurt + Hong Kong + Doha as global hubs with sub-12-hour reach to most of the world. Travel Crucible has practical mobility data per city.

Decide atlas → Where city-shortlist collapses to one — Decide Crucible runs the multi-Crucible tradeoff (Cost + Visa + Live + Business + Travel + Work) for city-by-city basing decisions. /cities/ lists candidates; Decide picks the answer.

Knowledge atlas → City-tied regulatory + sectoral expertise — financial-services regulatory regimes per city (London FCA · NYC Fed/SEC · Singapore MAS · Dubai DFSA · Hong Kong SFC); employment-law regimes; data-protection regimes. Knowledge Crucible has the long-form regulator deep-dives.

Related cross-Crucible decision lists

Best Cities First Time Cross Border Movers 2026 — Where the /cities/ surface's 110 entries get filtered to first-mover-friendly destinations — Lisbon + Singapore + Dubai + Mexico City + Bangkok all combine accessible visa routes + manageable cost + functional English + good infrastructure.

Best Startup Ecosystems Globally 2026 — Cities filtered for VC + accelerator + talent + regulatory composite — London + Singapore + Tel Aviv + Bengaluru + São Paulo + Mexico City consistently lead.

Best Eu Residency Tax Routes 2026 — European cities tied to residency + tax stack — Lisbon (D8 + IFICI) · Madrid + Barcelona (DNV + Beckham) · Milan + Rome (Impatriate) · Limassol + Nicosia (60-day) · Tallinn (Top Specialist) · Valletta (GRP).

Most Stable Economies Long Term 2026 — Cities anchored to top-stability economies — Zurich + Geneva + Basel (Switzerland) · Singapore · Oslo (Norway) · Copenhagen (Denmark) · Amsterdam + Rotterdam (Netherlands) · Auckland + Wellington (NZ).

Sources: AJG /cities/ surface (110 hand-curated city pages at v207.0 baseline · entity-view router for GeoNames 231,715-city fallback at v53.0+) · Mercer Quality of Living 2025 · OECD Better Life Index 2025 · EIU Liveability Ranking 2025 · Numbeo cost-of-living + quality-of-life composites Q1 2026 · World Bank ICP PPP 2024 · WHO Health Indicators 2025 · Henley Passport Index Q1 2026

AJG Global Nexus · live infrastructure

Multilateral trade graph — composed from the same registries on every render.

Cities

2,596

across 184 countries

Countries

184

multilateral coverage

Mandates

1,119

live trade mandates

FTAs

526

free-trade agreements

Blocs

economic blocs

Corridors

158

trade corridors

Trade bodies

1,366

authority registries

Tools

1,330

free calculators & lookups

Library nodes

1,190

decision tree

Lexicon terms

1,581

unpacked vocabulary

Subject hubs

100

school-is-cool axes

Institutions

313

colleges & universities

TOTALITY fields

1,600

32-point dual-POV across hubs + cities + toolkit + stages

TOTALITY entities

100

ALPHA + BRAVO retrofitted

The AJG Global Nexus is a deterministic, flat-file PHP composition of the world's trade graph — every country, every FTA, every corridor, every HS chapter, cross-multiplied against cities, schools, careers, and the working life that connects them. Nothing here is API-fetched at runtime; nothing depends on a paid build pipeline. Every URL composes from the same registries, so when one count moves, every page that touches that axis updates on the next render. The platform is multilateral by constitution — never bilateral-narrowed, never region-locked, never behind a paywall. School is cool, college builds the foundation, jobs build the network, work builds the experience, and business is where it gets monetised in your name. The journey is the product, and the data above is the live receipt of how much of it is currently browsable.

Composed at 2026-06-23T21:28:17+00:00 · deterministic PHP, no APIs at runtimeMethodology · About · Contact

All factsheets at a glance

Search 23,577,134 allfrontierglobal.com data points

Indian Cities · Industrial + Real Estate Atlas

Indian Cities — Industrial Output and Real Estate

Mumbai

Delhi / NCR

Bengaluru

Chennai

Kolkata

Hyderabad

Pune

Ahmedabad

Jaipur

Lucknow

Chandigarh

Ludhiana

Amritsar

Meerut

Prayagraj

Surat

Vadodara

Rajkot

Nashik

Nagpur

Indore

Bhopal

Bhubaneswar

Patna

Jamshedpur

Kochi

Coimbatore

Madurai

Mysuru

Visakhapatnam

Vijayawada

Udaipur

Gandhinagar

Hosur

Mangaluru

Tiruchirappalli

Warangal

Rohtak

Bikaner

Mathura

Siliguri

Dehradun

Haridwar

Tiruppur

Raipur

Bhilai

Gurugram

Faridabad

Noida

Kanpur

Varanasi

Agra

Jalandhar

Panipat

Jodhpur

Jamnagar

Anand

Vapi

Bhavnagar

Kota

Aurangabad

Solapur

Moradabad

Tirupati

Guntur

Hubli-Dharwad

Belagavi

Erode

Vellore

Thiruvananthapuram

Pondicherry

Haldia

Guwahati

Durgapur

Cuttack

Ranchi