The Semrush list shows “smrt map” attaching to a depot location URL with lat/lng. Nearby SG refuses that pattern. Instead: brand hub + guide + station places (Bras Basah and more). How to plan: pick origin/destination stations, note interchange lines, read exit letters, and budget peak congestion. Deep links: /brands/smrt, /places/bras-basah-mrt, /places/kim-chuan-depot-smrt, /categories/transportation. Exit letters matter more than memorising every door.
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.