Maps, Autocomplete, and Search Troubleshooting

Start with these checks

1. Confirm that WP Job Manager Geolocation, WP Job Manager, WordPress, and PHP meet the versions listed in Installation and License Activation.
2. Confirm that Google Cloud billing is active and that Maps JavaScript API, Places API (New), and Geocoding API are enabled.
3. Confirm that the Browser API Key uses website/referrer restrictions and the Server API Key uses the outbound server IP restriction.
4. Clear page, object, host, optimization, and CDN caches.
5. Repeat the test in a logged-out browser window and inspect the browser console for Google errors.

New services and changed key restrictions can take several minutes to propagate.

Blank map or Google Maps error

A front-end map uses the Browser API Key. Check:

• Maps JavaScript API is enabled in the same Google Cloud project as the key.
• Billing is active.
• The current production, staging, and subdomain referrers are allowed by the key.
• The key’s API restrictions include Maps JavaScript API and the services required by the page.
• The configured map has a valid height such as 350px or 400px.
• No cache or optimization plugin is delaying, combining, or blocking the Google Maps script.

Messages such as RefererNotAllowedMapError, ApiNotActivatedMapError, or billing errors identify the corresponding Google Cloud configuration problem.

Autocomplete does not return suggestions

Autocomplete also uses the Browser API Key. Verify:

• Places API (New) is enabled. Places API (Legacy) does not replace it for version 3.0.
• Places API (New) is allowed by the Browser API Key’s API restrictions.
• The page referrer is allowed.
• Address autocomplete is enabled for the correct administrator, front-end submission, or search form.
• Autocomplete Countries is not excluding the address being tested.
• The browser console does not report REQUEST_DENIED, PERMISSION_DENIED, or a blocked service.

Use Generating Google Maps API Keys to review the browser-key configuration.

Server API Key test fails

The built-in Test API Key action tests the Server API Key against Geocoding API. It does not test maps or browser autocomplete.

• Confirm that Geocoding API is enabled.
• Confirm that the Server API Key uses an IP-address restriction, not a website/referrer restriction.
• Allow the outbound IP Google reports in the error or test response. That observed IP is authoritative when it differs from the address expected from the hosting dashboard.
• Confirm that the site can make outbound HTTPS requests to Google.
• Wait briefly after changing the key or enabling the service, then test again.

A Job or Resume has no indexed location

A saved address is not enough for proximity search; the listing also needs valid coordinates indexed in WPGeo location storage.

1. Edit and save the listing, then confirm that WP Job Manager reports it as geocoded.
2. Open Job Listings → Settings → Geolocation → Tools.
3. Run Scan for Missing Job Locations.
4. With Pro and Resume Manager active, use the corresponding Resume Tools scanner for Resumes.
5. Enable optional geocoding only for records that do not already contain coordinates. Geocoding may consume quota and incur charges.

When upgrading from 2.3.3, finish Location Upgrade first. The versioned migration copies legacy rows; the missing-location scanners are a separate repair workflow. See Location Tools: Migration and Repair.

Proximity search returns unexpected results

• Confirm that geolocation is enabled through wpjmgeo_mode="settings", wpjmgeo_mode="shortcode", or the selected Preset Page.
• Use a known listing and a radius large enough to include it.
• Confirm the units: miles use imperial; kilometers use metric.
• Confirm that the location field produces coordinates rather than only free text.
• Finish any pending location migration and repair missing indexed locations.
• Clear caches after changing settings or shortcodes.

A visible map is optional. Proximity filtering continues when the Results Map is disabled, so an absent map is not by itself evidence that the location query is disabled.

A separate Results Map stays empty

A Results Map shortcode is a placement target for a matching listings instance. Verify that:

• The map and listings shortcodes are on the same page.
• element_id on the Results Map exactly matches wpjmgeo_element_id on [jobs] or [resumes].
• The ID is unique to that search-and-map pair.
• The matching listings instance has its map enabled.

See Results Map Shortcode for complete examples.

Resume or Job Alerts features are missing

Both the correct plugin package and the corresponding upstream extension must be active:

• Resume geolocation requires WP Job Manager Geolocation Pro and WP Job Manager Resume Manager.
• Location-aware Job Alerts require WP Job Manager Geolocation Pro and WP Job Manager Job Alerts.

Activating a Pro license does not add the Pro module files to a Starter installation. Install the Pro package, activate a compatible license, clear caches, and verify the integration again.

Information to include with a support request

If the problem remains, include:

• WordPress, PHP, WP Job Manager, and WP Job Manager Geolocation versions.
• The installed package label: Starter or Pro.
• Resume Manager or Job Alerts versions when relevant.
• The affected public page URL and shortcode.
• A screenshot or exact text of browser-console and Google API errors.
• Whether the failure occurs while logged out after all caches are cleared.
• The result of the Server API Key test and any migration or repair-tool status.

Contact support after collecting those details.