--- title: "How to Remove Google Maps API Error of browser console in WordPress?" url: https://nexterwp.com/docs/remove-google-maps-api-error/ date: 2023-02-01 modified: 2026-09-13 lang: en author: "Aditya Sharma" description: "If your browser console says Google Maps was included more than once, two parts of your site are loading the Google Maps API on the same page. This usually happens..." image: https://nexterwp.com/wp-content/uploads/2024/05/remove-google-maps-api-error-1024x519.jpg word_count: 402 --- # How to Remove Google Maps API Error of browser console in WordPress? ## Key Takeaways - Nexter Blocks Google Map block carga Google Maps dos veces cuando el tema o otro plugin ya carga la API en la misma página. - Nexter > Extra Options > Settings permite desactivar Connect Google Maps API Key para que Nexter Blocks no cargue Google Maps y dependa de la copia del tema o de otro plugin. - Una sola copia de Google Maps debe cargarse por página; si el mapa queda en blanco, el texto indica volver a activar Connect Google Maps API Key y quitar la clave del tema o del otro plugin. If your browser console says Google Maps was included more than once, two parts of your site are loading the Google Maps API on the same page. This usually happens when your theme or another plugin loads Google Maps and the Nexter Blocks Google Map block loads it too. *For every Google Map setting in one place, see the [Google Map block guide](https://nexterwp.com/docs/add-google-map-in-wordpress/).* [LIVE BLOCK LINK](https://nexterwp.com/nexter-blocks/blocks/wordpress-google-maps/) ## Before You Start - **Edition:** Free — applies to the Google Map block in Nexter Blocks (free) and with Nexter Blocks Pro.- **Block to enable:** Google Map, switched on under **Nexter > Blocks** in your WordPress dashboard.- **Know the other source:** check your theme and plugin settings for a Google Maps API key field. ## Steps - Open the page with the map, open your browser's developer tools and confirm the console error mentions Google Maps being loaded more than once. - Decide which part of your site should load Google Maps. If you only use maps from the Google Map block, remove the key from the theme or other plugin. - If another plugin needs to keep its Google Maps, go to **Nexter > Extra Options > Settings** and turn off **Connect Google Maps API Key**. ![The Connect Google Maps API Key switch in Nexter Extra Options Settings](https://nexterwp.com/wp-content/uploads/2026/09/google-map-api-key-settings.webp) - Clear any cache and reload the page. Check that the error is gone and the map still shows. ## How It Behaves - With **Connect Google Maps API Key** on, the Google Map block adds Google's Maps JavaScript API to pages that contain a map.- With it off, Nexter Blocks does not load Google Maps at all, so the block depends on the copy loaded by your theme or other plugin. ## Limitations - **Turning the switch off can leave the map blank** if the other copy of Google Maps does not load on that page. In that case, turn the switch back on and remove the other copy instead.- Only one copy of Google Maps should load per page, whichever source you keep. ## Troubleshooting ### The error is gone but the map is blank The other source is not loading Google Maps on this page. Turn **Connect Google Maps API Key** back on and remove the key from the theme or other plugin. ### The error is still there A third source may load Google Maps, or a cache is serving the old page. Clear the cache, then check your plugins one at a time. ## Related Docs - [Google Map block: all settings](https://nexterwp.com/docs/add-google-map-in-wordpress/)- [Generate a Google Maps API key](https://nexterwp.com/docs/generate-google-maps-api-key/)- [Add multiple locations to a Google Map](https://nexterwp.com/docs/add-multiple-locations-google-maps/) ## Frequently Asked Questions **Q: Why does the browser console say Google Maps was included more than once in WordPress?** A: That error usually means two parts of your site are loading the Google Maps API on the same page. In this setup, the most common conflict is a theme or another plugin loading Google Maps while the Nexter Blocks Google Map block loads it too. The fix is to keep only one source active per page, because duplicate API loads are what trigger the console warning. **Q: How do I remove the Google Maps API error without breaking my map?** A: The clean fix is to decide which source should own Google Maps on that page, then remove the other one. If the map only comes from the Google Map block, remove the key from the theme or other plugin. If another plugin must keep its map, turn off Connect Google Maps API Key in Nexter > Extra Options > Settings so Nexter Blocks stops loading its own copy. **Q: What should I check before trying to fix the Google Maps console error?** A: Start by confirming two things: the error really says Google Maps was loaded more than once, and the Google Map block is enabled under Nexter > Blocks in your WordPress dashboard. It also helps to look for a Google Maps API key field in your theme or plugin settings, because that is usually where the second copy is coming from. **Q: What happens if I turn off Connect Google Maps API Key?** A: Turning it off stops Nexter Blocks from loading Google Maps at all, so the block depends on whatever your theme or another plugin already loads on that page. That can remove the duplicate-load error, but only if that other copy is actually present. If nothing else loads Google Maps there, the map will go blank instead of rendering. **Q: Why is my map blank after fixing the duplicate Google Maps error?** A: A blank map usually means you turned off Connect Google Maps API Key, but the other source is not loading Google Maps on that page. In that case, turn Connect Google Maps API Key back on and remove the key from the theme or other plugin instead. The rule is simple: one page should load only one copy of Google Maps, but it still has to be a working copy. **Q: What if the Google Maps error still shows after I change the settings?** A: A third source may still be loading Google Maps, or cache may be serving an old version of the page. Clear any cache first, then test plugins one at a time to find who is adding the extra load. That matters because even if Nexter Blocks is configured correctly, another active source can keep reintroducing the same console error.