Theme Options โ Map Configuration -> Number of Pins settings
โMaximum number of pins to show on the map.โ
This option helps improve site speed by limiting how many property pins load on the map at once.
๐ Learn more about performance tips here: Speed Tips
How This Option Works
You can configure the maximum number of pins to load per map view. This is especially helpful if you have many properties, as loading all pins at once may slow down the site. Choose a number that works best with your hosting resources.
Youโll also find a related option:
Use file reading for pins?
โ
Recommended if you have over 200 listings.
File reading is faster than MySQL and improves map performance.
How the Pin Limit Works in Practice
๐น Scenario A: Read from File = NO
In this mode, the pin limit (e.g., 30 pins) applies to:
-
Header Google Maps (Homepage or Global Header Media) โ shows 30 pins
-
Property List Standard with Header Map โ shows 30 pins per page
-
Property List Half Map โ shows 30 pins per page
-
Taxonomy pages (Category, Action, City, Area) โ shows 30 pins per page
-
Search Results (Standard or Half Map layout) โ shows pins only for the current page results
-
Owner Profile Page โ shows the number of pins set in Theme Options, regardless of listings per page
Note: When using sort filters in the standard list, map pins do not update. This is because AJAX pagination replaces the page content without refreshing the map.
Scenario B: Read from File = YES
In this mode, the pin limit (e.g., 30 pins) applies to:
-
Property List Standard with Header Map โ shows 30 pins per page
-
Property List Half Map โ shows 30 pins per page
-
Taxonomy pages (List or Half) โ shows 30 pins per page
-
Search Results (Standard or Half Map) โ shows pins for the current search page
-
Owner Profile Page โ shows the number of pins set in Theme Options
๐ Key Difference:
With โRead from Fileโ enabled, Header Google Maps (global) will show all pins, regardless of the limit set.