maps.golfMost course websites that show any kind of map at all use one of two things: a flat photo gallery, or a static satellite screenshot embedded as a plain image or an unstyled iframe. Neither lets a visitor actually explore the layout — tilt to see elevation change, rotate to see a dogleg from a different angle, or check the distance to a specific pin. Adding real interactivity sounds like a development project. In practice, it's closer to pasting in a script tag.
What actually gets built
The map itself is built hole by hole: tee boxes, fairway, green, and bunkers, each as its own layer, drawn over photorealistic 3D imagery, with tee positions set from your scorecard. That's the part that takes real work, and it's done for you as part of onboarding, not something your team or web developer has to produce.
What you actually have to do
Once your course is mapped, embedding it is one snippet — a small script tag plus one placeholder element wherever you want the map to appear (your homepage, a dedicated course-tour page, an outings/events page, anywhere else). No backend changes, no API integration, no rebuilding your site around it.
The placeholder itself is deliberately lightweight: it renders a small poster/button in your page's normal flow and only loads the real interactive map once a visitor actually clicks it. That matters for cost, not just performance — a “map load” is what usage-based pricing bills against, so a page most visitors scroll past without clicking costs nothing.
What a visitor can actually do with it
Pan, zoom, tilt, and rotate around each hole on real satellite imagery. Switch holes without reloading the page. Click or drag anywhere on the map for an instant distance to the pin, from any tee. It's built to feel like a real tool a golfer would use to plan a round, not a static graphic with a caption underneath it.