On the page
Map & nearby places
A ready-made neighbourhood experience inside the listing template.
Map integrationWebsite language
Implementation guide · Software vendors
Separate shared platform settings from each customer’s appearance. Make the second integration a configuration task.
Decide the offer first
On the page
A ready-made neighbourhood experience inside the listing template.
Map integrationIn the copy
An address-based local section in the published property page.
Local contentIn the document
A map image in property reports and brochures.
Static mapsConfiguration boundaries
Scroll sideways to see all columns.
| Decision | Platform level | Customer level |
|---|---|---|
| Service scope | Licence, products and countries | Enabled modules within the agreed offer |
| Appearance | Shared defaults and supported options | Map style, accent colour and placement |
| Publishing | Caching and refresh policy | Supported language and template choices |
| Rollout | Integration and validation process | Preview and activation for each site |
Make it repeatable
First pilot
Use real addresses, the actual listing template and any property-document output.
Second pilot
Change the brand and enabled modules. Identify anything that still needs customer-specific code.
Rollout
Review data location, mobile layout, language availability and the page with optional modules disabled.
Implement the chosen outputs
Country and language coverage can differ. Make unsupported modules disappear cleanly rather than leaving empty blocks in a customer’s template.
Yatmo can provide a client-management API to generate a key per customer and manage authorised domains across your sites. This API is available on request and is not included in the public documentation.
A concrete first step
Share two representative customer sites and the modules you want to offer.