ExpressMapChecker
Knowledge base / Start here

How to read Google Maps errors in your browser console

7 min read•Updated August 2026•No coding required

“Oops! Something went wrong.” never tells you the cause. The real reason is one line in the browser console, and every fix in this knowledge base starts from that line. Here is how to reach it in each browser — desktop and mobile.

What you are looking for

A red console line from the Maps script. It almost always ends in MapError or contains Google Maps JavaScript API — for example:

Google Maps JavaScript API error: RefererNotAllowedMapError
Your site URL to be authorized: https://yourwebsite.com/map-page

The word before MapError is your diagnosis. Copy the whole line — the second line often names the exact host Google expected.

Chrome and Edge (Windows, macOS, Linux)

  1. 01Open the page with the broken map.
  2. 02Press F12, or Ctrl + Shift + J on Windows / ⌥ + ⌘ + J on macOS. Right-click → Inspect works too.
  3. 03Select the Console tab, then reload the page so errors are captured from the start.
  4. 04Type Map in the filter box to hide everything except the Maps errors.

Firefox

  1. 01Press Ctrl + Shift + K (Windows) or ⌥ + ⌘ + K (macOS) to open the Web Console.
  2. 02Make sure the Errors filter is switched on, then reload the page.
  3. 03Firefox groups repeats — click the arrow on the Maps error to expand it and see the full message.

Safari on macOS

  1. 01The developer tools are hidden by default: open Safari → Settings → Advanced and tick Show features for web developers.
  2. 02Press ⌥ + ⌘ + C to open the console, then reload the page.
  3. 03Use the Errors filter at the top of the console pane to isolate the Maps line.

iPhone and iPad

iOS has no on-device console, so you read it from a Mac over a cable.

  1. 01On the phone: Settings → Apps → Safari → Advanced and turn on Web Inspector.
  2. 02Connect it to a Mac, open the page on the phone, then choose it under Safari’s Develop menu on the Mac.
  3. 03The Mac console now shows the phone’s errors. No Mac to hand? Run a scan instead — it reports the same signature.

Android

  1. 01Enable Developer options → USB debugging on the phone and connect it to a computer.
  2. 02In desktop Chrome open chrome://inspect, find the tab, and click inspect.
  3. 03Read the Console tab exactly as you would on desktop.

Three things that hide the real error

  • A filter left on “Warnings only” or a log level that hides errors — reset the filter before you conclude the console is clean.
  • Opening the console after the page loaded. Maps errors fire once, at load; always reload with the console open.
  • Your own cached session or extensions. Test in a private window, and remember your visitors may see an error you never will.

Now match the error to its fix

Take the word before MapError and open its article:

RefererNotAllowedMapError Referrer restrictions that don’t break www ApiNotActivatedMapError Enabling the Maps JavaScript API BillingNotEnabledMapError Re-enabling a suspended project Something else Look it up in the error library →
Rather skip the console?

We read it for you and name the error, from a clean session.