Map Detection
Smart Local Google Maps finds Google Maps embeds using 21 built-in regex patterns, applied to the fully rendered page HTML during Joomla's onAfterRender event. You can add one more pattern of your own in the Expert Mode tab. Detection runs on front-end HTML pages only.
What's Covered
| Group | Detected markup |
|---|---|
| Standard | Google Maps API script tags (maps.googleapis.com, maps.google.com/maps/api), iframes (google.*/maps, google.com/maps/embed) |
| Widget platforms | Widgetkit, YOOtheme (uk-map), Gantry particles, Advanced Page Builder |
| Dedicated map plugins | Phoca Maps, Mike Reumer Google Maps, BT Google Maps, MyMapList, DG Fotomap |
| Event & booking | JCal Pro, JEM (Event Manager), Event Booking |
| Page builders | SP Page Builder (sppb-addon-gmap) |
| Generic fallback | Any <div> with an id starting with googlemap |
Each match is removed from the output before the page is sent to the browser. In overlay positions a single consent box is injected; in the inline placeholder position each match is replaced individually with a placeholder card.
Why So Many Patterns?
Google Maps reaches a Joomla page through dozens of routes — a raw iframe from the editor, a slider or page-builder addon, a dedicated maps component, or an events extension that renders a venue map. A consent manager that only strips the standard iframe leaves component markup leaking tiles and the visitor's IP to Google. Covering 21 forms means the common ways a map lands on your page are handled out of the box.
Non-Destructive
Detection and stripping happen on a copy of the rendered HTML during onAfterRender. Your articles, modules, and component data are never modified on disk — the plugin only changes what is sent to the browser for that request.
Custom Regex Pattern
When a template or extension uses markup none of the built-in patterns match, add your own regex in the Expert Mode tab (Custom Regex Pattern). It runs alongside the built-ins. See Expert Mode for syntax rules and a step-by-step workflow.
Debug Mode
Enable Debug Mode in the Expert Mode tab to see exactly which patterns matched on the current page and how many times — the fastest way to confirm coverage or diagnose a missed embed. Only Super Users logged in on the frontend see the debug box.
When Detection Isn't Enough
If a map is injected into the DOM client-side by JavaScript (rather than present in the server HTML), there is nothing in the rendered output to strip. In that case, target the initializing script with an Expert pattern, or build the map yourself with the {smartmap} shortcode, which is consent-wrapped by construction and needs no detection at all.