{"id":2944,"date":"2026-10-20T08:40:00","date_gmt":"2026-10-20T07:40:00","guid":{"rendered":"https:\/\/wpgeodirectory.com\/documentation\/article\/google-maps-oops-something-went-wrong-2\/"},"modified":"2026-10-20T08:40:00","modified_gmt":"2026-10-20T07:40:00","slug":"google-maps-oops-something-went-wrong-2","status":"publish","type":"gd_place","link":"https:\/\/wpgeodirectory.com\/documentation\/article\/troubleshooting\/google-maps-oops-something-went-wrong-2\/","title":{"rendered":"How to fix the Google Maps &#8220;Oops! Something went wrong&#8221; error"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">&#8220;Oops! Something went wrong. This page didn&#8217;t load Google Maps correctly&#8221; comes from Google, not from GeoDirectory. Google shows it when it refuses to load the map for your API key. The browser console tells you exactly why.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Find the real error<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Open a page with a map on your site.<\/li>\n\n\n\n<li>Open your browser&#8217;s developer tools (F12 in most browsers) and go to the Console tab.<\/li>\n\n\n\n<li>Look for a Google Maps error name, such as RefererNotAllowedMapError, ApiNotActivatedMapError, BillingNotEnabledMapError or InvalidKeyMapError.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Common causes<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Billing: Google requires a billing account linked to the project that owns the key, even if you stay inside the free usage.<\/li>\n\n\n\n<li>APIs not enabled: the key needs the Maps JavaScript API, plus Places, Geocoding and Time Zone for the add listing form.<\/li>\n\n\n\n<li>Referrer restrictions: if the key is restricted to websites, the list must include your domain in the form your site uses, for example both <code>example.com\/*<\/code> and <code>www.example.com\/*<\/code>. Remove the restriction for a few minutes to test whether it is the cause.<\/li>\n\n\n\n<li>Wrong or old key: check that the key in GeoDirectory is the one you edited in Google Cloud.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Generate a key from GeoDirectory<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Go to GeoDirectory > Settings > General and find Google Maps API KEY. The Generate Key button opens Google Cloud with the APIs GeoDirectory uses already selected. Paste the new key in, save, and use the Verify button.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If your main key is restricted by HTTP referrer, geocoding and time zone requests from your server will fail with it. Add a second key without referrer restrictions in the Google Geocoding API Key setting (click Show Advanced).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Full steps are in <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/installation\/get-a-google-api-key\/\">get a Google API key<\/a>. If maps worked before and then stopped, 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<p class=\"wp-block-paragraph\">If you would rather not use Google, you can switch the Maps API setting to OpenStreetMap.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>&#8220;Oops! Something went wrong. This page didn&#8217;t load Google Maps correctly&#8221; comes from Google, not from GeoDirectory. Google shows it when it refuses to load the map for your API key. The browser console tells you exactly why. Find the real error Common causes Generate a key from GeoDirectory Go to GeoDirectory > Settings > [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"closed","template":"","meta":{"footnotes":""},"article\/tags":[],"article\/categories":[211,437],"class_list":["post-2944","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\/2944","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=2944"}],"version-history":[{"count":0,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2944\/revisions"}],"wp:attachment":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/media?parent=2944"}],"wp:term":[{"taxonomy":"gd_place_tags","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/tags?post=2944"},{"taxonomy":"gd_placecategory","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/categories?post=2944"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}