Handled Locator - 2026 Pricing, Features, Reviews & Alternatives

Handled Locator is store locator software that embeds a searchable location finder into a website with a single line of script. It serves organizations that need to display physical locations, dealer networks, stockist lists or service areas on web properties, and it runs as a lightweight widget rather than a hosted microsite or a platform-specific app.

Integrations and installation

The widget installs on Shopify, WordPress, Squarespace, Webflow, Wix, BigCommerce, Ghost, Framer, Elementor, Drupal, Joomla, HubSpot, React, Next.js or standard HTML pages, with no plugin to maintain and no app permissions to grant. Location data enters by CSV import with column matching and address geocoding, by Google Sheets sync with creates, updates, conflicts and missing rows previewed before the first apply, or through the REST Location API. Mapbox and Google Maps are both supported as map providers and can be swapped without reconfiguring anything else.

AI assistant control over MCP

Handled Locator runs a Model Context Protocol server, the open standard that lets an AI assistant use a product's tools with the account holder's permission. Claude, ChatGPT, Claude Code and Cursor can add locations from a pasted list of addresses, tag them, add custom call-to-action buttons, restyle the widget, edit visitor-facing wording and return the embed code. Claude and ChatGPT connect by OAuth sign-in with no key to create; developer clients authenticate with an API key. Every configuration change goes through a propose step that returns an exact before-and-after diff, and the apply tool refuses to run without a proposal it can verify, so no change reaches the live widget without explicit approval. The connection is scoped to the single locator on the account that signed in, and disconnecting revokes access without altering stored data.

Security and access control

Team roles are owner, admin and editor, enforced on every write: editors manage locations and categories, admins configure the widget, owners hold account-level settings. API keys are account-scoped rather than personal, can be issued read-only or read-write, are shown once at creation, and are revocable. Rate limits are 120 reads and 30 writes per minute per key. Map provider keys are public by design and are restricted to the customer's own domain in the provider console, which the setup flow prompts for. Every configuration change is stored as a numbered version and an admin can restore an earlier one; restoring adds a new version, so history is never rewritten. Browser events emitted for analytics exclude visitor queries, coordinates and contact details.

Performance and specifications

The locator shell and map modules together stay under 100 KB gzipped, including search, filters and the results list. Self-serve plans serve up to 10,000 locations per account, with first results on screen in about 1.65 seconds at 5,000 locations, achieved by paging results as the visitor scrolls and by an index built for the public query. The widget renders inside a shadow root, so it cannot collide with the host page CSS and the host page CSS cannot break it. Rendering is verified on Chromium, Firefox and WebKit against the deployed build running on a third-party origin.

Configuration and design

85+ working settings cover search, results, filters, opening hours, maps, markers, layout, links and data formatting. Every visitor-facing string is editable, seven list, grid and map layouts are available, and markers can be pins, dots, logos or uploaded artwork. Custom CSS is supported where settings run out. No Handled branding appears on any plan.

Commercial model

Map usage is billed directly by Mapbox or Google at provider rates against the customer's own key, with no subscription markup, which separates locator cost from traffic-driven map cost. Plans start at $19 per month for 200 locations and 2 seats, every working setting is included on every tier, and a 7-day trial requires no card.