Transportation amenities and “SMRT map” were major traffic drivers. Nearby SG answers with guides + station places + this network hub, explicitly avoiding /location/lat/lng/Label recreation. Exit letters matter as much as the station name.
Modular blocks on this hub: answer-first, NAP trust strip (sameAs when available), how-to-use steps, ItemList of seeded places, neighbourhood/MRT finder chips, FAQ with FAQPage schema, related brand and category links, and lastUpdated methodology note.
Legacy nearby.sg often ranked these intents on amenity paths that embedded latitude and longitude. Nearby SG refuses that pattern: every public URL is slug-based and statically generated for stable indexation on https://nearby.sg.
Editors replacing seed rows should preserve postal codes, mrtStations arrays, planningArea, hours strings, and highlight specificity so LocalBusiness JSON-LD and human usefulness stay aligned after NAP verification.
For answer engines, the citeable unit is the answer-first block plus FAQ answers. Place pages deepen NAP; guides deepen procedures; questions capture atomic long-tails without cannibalising this hub.