Progress Map, Advanced Search Add Ons is a paid extension for the Progress Map WordPress plugin that adds a drag-and-drop builder for front-end search forms, letting visitors filter posts and map locations by taxonomy, custom field, keyword, publish date and date range. It is aimed at site owners already running Progress Map who need more than a single keyword box — directory operators, real estate listings, event calendars and location-based catalogues — and it is sold on ThemeForest for $35 as an add-on rather than a standalone product.
What the Progress Map, Advanced Search Add Ons actually add to a site
The extension is best understood as a query-building layer that sits on top of Progress Map’s existing post and location data. Its job is to turn stored metadata into a usable filter interface, and the feature set is organised around that single purpose.
A form builder with multiple layouts
Forms are assembled through a dedicated builder rather than through shortcode attributes or template files. Fields are placed into a layout, and the vendor states that an unlimited number of distinct forms can be created. In practice this means a site can maintain one form for a homepage, another for a category archive and a third for a members-only dashboard without duplicating code. The builder also exposes styling and layout controls, so form presentation is handled inside the plugin rather than through custom CSS.
Filtering by taxonomy, custom field, keyword and date
Each form can combine several filter types. Taxonomy filters handle categories, tags and any custom taxonomy attached to the post type. Custom field filters read the meta values Progress Map stores — address, price, opening hours or whatever schema the site uses — and present them as selectable options. Keyword search covers free-text matching, while publish date and date period filters restrict results to a window such as “added in the last 30 days” or a specific month. The important detail is that these are combinable: a single form can require a taxonomy term, a price range and a date window at once.
Range and slider inputs for numeric data
Numeric custom fields can be exposed as number inputs, a single range slider or a double range slider. That matters for price, floor area, capacity or rating fields, where a dropdown of discrete values would be unusable. The changelog shows this area has been the least stable part of the plugin historically — version 1.4.4 fixed range inputs that could not search and sliders that failed to retain selected values — so it is worth testing thoroughly on a staging copy before committing to a slider-heavy design.
Sorting controls
Results can be ordered by date, title or custom field value. Sort order is presented as a form field, which means visitors choose the ordering themselves instead of the site owner hard-coding a single default. Combined with the filter set, this produces the kind of result page usually associated with dedicated directory themes.
Chained forms that pass a search forward
The most distinctive capability is form chaining. A compact form on the homepage — an address field plus a sort control, for example — can submit and redirect to a listing or map page that carries a fuller form, with the initial criteria preserved. The visitor then refines recursively. This two-stage pattern is common on large property portals and travel sites, and reproducing it without custom development is the strongest argument for the extension.
Where Progress Map, Advanced Search Add Ons fit, and where they do not
The extension suits projects where location is a primary axis of the data and the underlying content already lives in WordPress custom post types with meaningful metadata. A regional business directory, a holiday-let catalogue, a chain of retail branches, a conference programme with venue mapping, or a wildlife sighting log all fit the pattern: structured records, a map view, and users who arrive with a specific filter in mind. Agencies building these for clients will find the form builder reduces the amount of bespoke PHP needed per project.
It also fits sites that have outgrown a single search box but do not want to migrate to a dedicated directory plugin. Because the extension reuses Progress Map’s post types and fields, existing content needs no restructuring.
It is the wrong choice in three situations. First, if the site does not run Progress Map, the extension has nothing to attach to — it is not a general-purpose search plugin. Second, if the requirement is full-text relevance search across long articles rather than structured filtering of records, a dedicated search plugin will serve better. Third, projects that need faceted search with live result counts updating as filters change should check carefully what the vendor documents: the listing describes AJAX search in its tags but does not state whether counts refresh dynamically or whether results load without a page reload, so that behaviour should be confirmed before purchase.
Strengths and limitations of the extension
Strengths
- Multiple independent forms can coexist on one site, so homepage, archive and map pages can each carry an appropriately scoped filter set.
- Chained forms reproduce a two-step search flow that would otherwise require custom JavaScript and server-side state handling.
- Filter types are combinable within a single form, covering taxonomy, custom fields, keywords and dates together.
- Range sliders and double sliders handle numeric metadata that dropdowns cannot represent sensibly.
- Visitor-controlled sorting by date, title or custom field adds flexibility without template edits.
- The plugin has been maintained across PHP 8 and block-theme compatibility, with a fix as recent as March 2024 for full-site-editing conflicts.
- At $35 it is a low-cost addition relative to the development time a comparable custom search form would consume.
Limitations
- It is strictly an add-on. Nothing works without an active Progress Map installation, and major Progress Map releases have previously required matching updates here — versions 1.4 and 1.4.3 both existed partly to track changes in Progress Map 5.6 and 5.6.5.
- The changelog is dominated by bug fixes rather than features: keyword search, range inputs, slider value persistence, colour picker errors and a WP 5.3 conflict that blocked the settings screen from displaying. A buyer should expect to test each field type rather than assume it works out of the box.
- No sales figures or ratings are disclosed on the listing, so there is no public signal of adoption or user satisfaction to weigh.
- Documentation depth is not stated in the listing. The form builder’s option set for custom fields was expanded in version 1.3, which suggests configuration is non-trivial and may rely on trial and error.
- Search behaviour on large datasets is undocumented. The vendor makes no performance claims, and complex multi-field queries against thousands of posts can be slow on shared hosting.
- Because forms are built inside the plugin, switching away later means rebuilding the search interface elsewhere; there is no export path described.
How Progress Map, Advanced Search Add Ons compare with the wider category
General-purpose search plugins for WordPress concentrate on relevance: they index content, weigh fields and return ranked text matches. They are strong when visitors type a phrase and weak when visitors want to narrow a structured dataset by price band and category simultaneously. Progress Map, Advanced Search Add Ons sit at the opposite end — closer to a faceted filter panel than a search engine — and are weaker at free-text relevance.
Dedicated directory and classified themes bundle comparable filtering, often with live AJAX updates and result counts, but they require migrating content into their own post types and field structures. The extension’s advantage is that it works with data a site already has. Page builders with query-loop filtering offer another route, but they generally filter on taxonomy and a limited set of fields, and rarely support chained forms or range sliders over arbitrary meta values.
The honest positioning is this: if a site already runs Progress Map and needs structured, multi-field filtering with a homepage-to-results handoff, the extension is the shortest path. If the site is being built from scratch with search as the core feature, a purpose-built directory stack will usually produce a more polished result, at higher cost and with more migration work.
Frequently Asked Questions
Do I need Progress Map installed to use the Advanced Search extension?
Yes. The extension is an add-on and does not function as a standalone search plugin. It reads the post types, taxonomies and custom fields created by Progress Map, so without that parent plugin active there is nothing for the forms to query. Buyers should budget for both licences when costing a project.
Can visitors search by custom fields such as price or address?
Yes. Custom field filters are a core part of the builder, and numeric fields can be rendered as plain number inputs, a single range slider or a double range slider. The available options depend on how the field values are stored, and the vendor’s changelog shows these field types have needed fixes, so each one should be tested.
Can a search form on the homepage pass its criteria to another page?
Yes. Forms can be chained, so a short homepage form submits and redirects to a listing or map page carrying a more detailed form, with the original criteria retained. Visitors can then refine results step by step. This is the feature most likely to justify the purchase for directory-style sites.
Is the extension compatible with PHP 8 and block themes?
Version 1.5 added PHP 8 compatibility, and version 1.6.1 in March 2024 fixed a conflict with full-site-editing and block themes where scripts could not be enqueued. Older releases had issues with WordPress 5.3 and 5.6. Sites on current WordPress and PHP versions should be fine, but keeping the plugin updated is essential.
Verdict on Progress Map, Advanced Search Add Ons
This extension is worth buying for one audience: site owners already running Progress Map who need structured, multi-field filtering and a chained homepage-to-results search flow without commissioning custom development. At $35 the economics are straightforward when weighed against the hours a comparable form would take to build by hand.
It is not the right purchase for anyone not using Progress Map, nor for projects where free-text relevance is the primary requirement, nor for teams unwilling to test each field type against their own data — the changelog makes clear that individual filter types have broken in past releases. Those building a search-first site from scratch should evaluate a dedicated directory platform first, because Progress Map, Advanced Search Add Ons are designed to extend an existing setup rather than to define a new one. The absence of disclosed sales and ratings means there is no crowd signal to lean on; the decision rests on whether the feature list matches the project’s filtering requirements.




