A MAP PARTNER FOR YOUR CLIENT PROJECT
Custom maps that belong on the client's website.
MapEdition designs, builds, integrates, and hosts custom interactive maps shaped around a client's places, content, and brand. We work with developers and agencies on the map while your team keeps control of the wider website.
When a map fits the brief
A dining guide, local publication, guest neighborhood guide, or property page can help visitors explore the places behind a story or destination. The client's selection and point of view lead the map; connected place cards, writing, images, links, and locations make it useful to browse. The working Charleston dining demonstration shows the interaction, and is labeled as an archived demonstration rather than a customer case study.
Publishing routes
These are illustrative arrangements, not one-click installations. We check the client platform, map host, domain control, and desired reader journey before agreeing a route. There is no universal plugin to install.
Embed the hosted map in the client's page
www.example.com/explore/containsMapEdition-hosted mapiframe within the page
The reader explores the map in the surrounding story or guide. The client's developer places a project-specific iframe where the website allows it; we supply the agreed map address and coordinate size, embedding permissions, links, and phone checks. Include a full-page map link when it helps.
Open a MapEdition-hosted map on the client's subdomain
www.example.comlinks tohosted mapmaps.example.comThe website and newsletter stay where they are. A normal link opens the map at its own branded address. This requires agreement on the map host, adding the subdomain to the hosting project, appropriate DNS, and HTTPS; a DNS record alone does not turn an arbitrary URL path into a subdomain. The client's domain administrator participates in setup.
Link to a dedicated hosted map page
agreed hosted address
A direct link is a practical fallback when an embed or custom domain is unavailable. It also works from email and from platforms such as Substack whose post editor does not accept raw iframe code.
Discuss a code handoff only when the project calls for it
The standard MapEdition offering is a hosted service, not a purchase of transferable map code. If a client needs to operate a map in its own environment, we can discuss whether a separately scoped code handoff is feasible, including responsibilities and terms, before making any commitment. This is not the default publishing route.
For platform details, an illustrative iframe example, and desktop and phone checks, read the detailed integration guide.
From brief to published page
- Share the context. Send the client site, platform, audience, intended map location, and any starting places or existing content. An address and an idea can be enough to start talking.
- Agree the scope. We discuss the map content, brand treatment, hosting address, integration route, responsibilities, and price before work begins.
- Review a working map. The client and web team can see the real interaction and give feedback before approving publication.
- Launch together. We handle the map and hosting, coordinate the agreed embed or link with your team, and check the published experience on desktop and phone.
The standard editorial map service has no upfront development fee and uses 12 monthly payments. After completing those payments, the unchanged map stays live with hosting under the agreed terms. An agreed customer-requested map update starts a fresh 12-payment period. If the customer leaves before completing the current period, remaining payments are not owed and the hosted map is taken offline. The map is a hosted service, not a transfer of code. See the service pricing and FAQ.
Have a client project in mind?
Tell us about the client site and where the map would live. We can discuss the right publishing route with you.
Discuss a client map