Interactive maps can be some of the most useful material on a municipal website: road projects, transit service, parks, zoning, public works, and planning data all benefit from geographic context. They can also become one of the heaviest things on a page if they are embedded without a clear purpose.
Start with the public question
Do not add a map simply because one exists. Define the question it answers. “Which streets are affected this week?” needs a different map and page than “Where are public facilities?” A focused map needs fewer layers, fewer controls, and less explanation than an all-purpose GIS portal.
ArcGIS Online supports sharing and embedding maps and apps, but public access depends on the sharing settings of the map and its underlying layers. Esri’s guidance on sharing and embedding maps is a useful starting point for the GIS and website teams.
Make the embed behave like part of the site
- Give the map a descriptive heading and a short explanation before the interactive area.
- Load it on the page where it is needed, rather than on every page of the site.
- Test the map on mobile and avoid scroll behavior that traps the visitor.
- Provide a direct link to the full map or application for people who need more detail.
- Confirm that every layer a resident needs is public and visible without a sign-in.
Also consider performance. A homepage with a large map, multiple analytics scripts, video, and several widgets can become slow for the exact resident who needs a quick update on a phone. Sometimes a static preview image and a clear “View the interactive map” action is the better first experience.
The right ArcGIS integration makes data easier to use without asking the website to become a second GIS platform.