Documentation

Results Map Shortcode

Last modified: September 22, 2026

What the Results Map shortcode does

The Results Map shortcode moves the map belonging to a Jobs or Resumes search-results instance to another position on the page.

It does not run its own listing query and does not create an independent map. It outputs a placement target that the front-end search runtime fills after the matching results instance loads.

Use the same explicit element ID on both shortcodes. Without a matching listings instance, the Results Map shortcode has no search results or markers to display.

Jobs example

Place the map where it should appear:

[wpjmgeo_jobs_results_map element_id="jobs-directory"]

Place the matching Jobs listing elsewhere on the same page:

[jobs wpjmgeo_mode="settings" wpjmgeo_element_id="jobs-directory"]

The map follows the initial results and later AJAX searches performed by that Jobs instance.

Resumes example

Resume Results Maps require the Pro package and the separate WP Job Manager Resume Manager extension:

[wpjmgeo_resumes_results_map element_id="resume-directory"]
[resumes wpjmgeo_mode="settings" wpjmgeo_element_id="resume-directory"]

The element ID requirement

An integrated [jobs] or [resumes] instance receives a random ID automatically when no ID is supplied. That is sufficient when its map stays in the normal results layout.

A separately placed Results Map cannot predict that random ID. Assign the same explicit value to:

  • element_id on the Results Map shortcode.
  • wpjmgeo_element_id on the matching [jobs] or [resumes] shortcode.

Use letters, numbers, hyphens, or underscores and keep the value unique on the page.

Configure the map

The Results Map shortcode controls placement only. Configure the actual map through the matching search instance:

  • Use wpjmgeo_mode="settings" to load the saved Search & Map settings.
  • Use wpjmgeo_mode="shortcode" and the wpjmgeo_map_* attributes for page-specific dimensions and behavior.

For example:

[wpjmgeo_jobs_results_map element_id="remote-jobs"]
[jobs wpjmgeo_mode="shortcode" wpjmgeo_element_id="remote-jobs" wpjmgeo_radius="25,50,100" wpjmgeo_map="1" wpjmgeo_map_height="500px" wpjmgeo_marker_clusterer="1"]

If the matching listings shortcode disables the map with wpjmgeo_map="0", the separate placement target remains empty. Proximity filtering itself continues to work.

Multiple search instances

Every independent search-and-map pair needs a different element ID:

[wpjmgeo_jobs_results_map element_id="featured-jobs"]
[jobs wpjmgeo_mode="settings" wpjmgeo_element_id="featured-jobs"]

[wpjmgeo_jobs_results_map element_id="remote-jobs"]
[jobs wpjmgeo_mode="shortcode" wpjmgeo_element_id="remote-jobs" wpjmgeo_radius="100"]

Reusing one ID for unrelated searches can cause the wrong map to move or receive a results payload intended for another instance.

Troubleshooting

  • The map area stays empty: confirm that the Results Map and listings shortcodes use the same explicit ID and that the listings instance has its map enabled.
  • The wrong map moves: give every pair a unique ID.
  • The search works but no markers appear: verify that the matching results have indexed coordinates and that the Browser API Key can load Maps JavaScript API.
  • The map works only while logged in: clear page, object, host, and CDN caches and test the public page again.

See Geolocation Shortcode Attributes and Maps, Autocomplete, and Search Troubleshooting.

menu-circle