Singapore Pools was the top historical traffic amenity on nearby.sg. Nearby SG rebuilds that intent as a brand hub: answer-first orientation, ItemList of seeded retailers, neighbourhood/MRT finder context, and FAQ — without recreating /amenities/singapore-pools/.../lat/lng/Label paths. Authorised retailers differ from a single flagship branch: they are distributed points of sale. Shoppers typically search “Singapore Pools”, “Singapore Pools outlet”, or mall-specific variants (VivoCity, Orchard). Our modular pages split network discovery (this brand hub) from named places (Ngee Ann City, VivoCity) and a how-to guide. Use MRT-first planning and mall directories to locate the retailer desk.
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.