{"id":2638,"date":"2026-10-20T08:35:23","date_gmt":"2026-10-20T07:35:23","guid":{"rendered":"https:\/\/wpgeodirectory.com\/documentation\/article\/this-page-cant-load-google-maps-correctly\/"},"modified":"2026-10-20T08:40:20","modified_gmt":"2026-10-20T07:40:20","slug":"this-page-cant-load-google-maps-correctly","status":"publish","type":"gd_place","link":"https:\/\/wpgeodirectory.com\/documentation\/article\/troubleshooting\/this-page-cant-load-google-maps-correctly\/","title":{"rendered":"How to fix &#8220;This page can&#8217;t load Google Maps correctly&#8221;"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Google shows this message when it refuses to load the map for your API key, or when the page sends no key at all. Your browser console tells you which. Open the developer tools (F12 in most browsers), go to the Console tab and reload the page. The Google Maps JavaScript API message there names the problem, for example NoApiKeys, ApiNotActivatedMapError, RefererNotAllowedMapError or BillingNotEnabledMapError.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The key is saved but Google says there is no key<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If your key is in GeoDirectory > Settings > General > Google Maps API KEY but the console says the API is used without a key, the page is usually being served from a cache made before the key was added or changed. Clear every cache: your caching plugin, your host&#8217;s server cache, any CDN, and any plugin that combines or minifies JavaScript.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A quick test is to load the page with <code>?x=y<\/code> on the end of the URL, which often skips the cache. If the map works there, caching is the cause. SiteGround users should read <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/how-tos\/siteground-cache-configuration-and-google-maps\/\">SiteGround cache configuration and Google Maps<\/a>, and for other caching plugins see <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/caching\/geodirectory-and-caching-compatibility\/\">GeoDirectory and caching compatibility<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Problems with the key itself<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Billing: Google Maps needs a Google Cloud project with a billing account attached, even when your usage stays inside the free allowance.<\/li>\n\n\n\n<li>APIs not enabled: the project must have the Maps JavaScript API and the other APIs GeoDirectory uses turned on. <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/installation\/get-a-google-api-key\/\">Get a Google API Key<\/a> lists them.<\/li>\n\n\n\n<li>Referrer restrictions: if you restrict the key to your website, the allowed referrers must match your domain, for example <code>https:\/\/example.com\/*<\/code>. A referrer-restricted key can&#8217;t be used for geocoding from your server, so put a separate key in the Google Geocoding API Key setting.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The Google Maps API KEY setting has a button that creates a correctly configured key with your Google account. If maps stopped working without any change on your side, also see <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/troubleshooting\/maps-have-stopped-working-on-my-site\/\">Maps have stopped working on my site<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Using OpenStreetMap instead<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you&#8217;d rather not use Google, go to GeoDirectory > Settings > General, click Show Advanced and set Maps API to OpenStreetMap API. See <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/how-tos\/differences-between-the-google-maps-and-openstreetmap-apis\/\">Differences between the Google Maps and OpenStreetMap APIs<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Google shows this message when it refuses to load the map for your API key, or when the page sends no key at all. Your browser console tells you which. Open the developer tools (F12 in most browsers), go to the Console tab and reload the page. The Google Maps JavaScript API message there names [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"article\/tags":[],"article\/categories":[211,437],"class_list":["post-2638","gd_place","type-gd_place","status-publish","hentry","gd_placecategory-tips-tricks-more","gd_placecategory-troubleshooting"],"_links":{"self":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2638","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article"}],"about":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/types\/gd_place"}],"author":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/comments?post=2638"}],"version-history":[{"count":1,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2638\/revisions"}],"predecessor-version":[{"id":2795,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2638\/revisions\/2795"}],"wp:attachment":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/media?parent=2638"}],"wp:term":[{"taxonomy":"gd_place_tags","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/tags?post=2638"},{"taxonomy":"gd_placecategory","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/categories?post=2638"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}