StrollPlace Developers
StrollPlace

Why Your “What’s Nearby” Widget Isn’t Showing

Find out why StrollPlace’s What’s Nearby widget is missing, shows city-level results, or appears on some IDX pages only.

A diagnostic timeline showing where a widget load fails.

Start with one listing URL where you expected the widget to appear. Open that exact URL in a private window. A working widget-builder preview confirms that your example location can return content. The actual listing still needs to load the script, expose usable location information, and match a placement your provider supports.

What you see

Where to start

The widget is missing on every listing

Check whether the published listing page loads the embed and whether the browser blocks it.

It appears on some listings

Compare the template and the location data on a working and a missing listing.

It appears on detail pages only

Check whether the provider supports search results and whether you enabled that placement.

It shows the city instead of the immediate area

Check what location detail the listing provides and what coverage exists for the area.

The card appears but a selected section is missing

That section appears only when data is available for the detected place.

1. Check that the embed reaches the listing page

Open browser developer tools on the listing URL and reload with the Network panel open. Filter requests for widgets.strollplace.com. If there’s no widget request, inspect the rendered page for a StrollPlace script or check for a browser error that blocked it before it could load. Confirm that your site published the complete snippet and that the code is present on the IDX page, which may use a separate wrapper or hostname.

Example. Your homepage loads the script, but a property opens on the IDX subdomain and the script is absent there. Add the embed to the wrapper that serves the IDX detail page. If properties appear inside an iframe, open a direct property URL to check which page would need the embed. The surrounding page’s script can’t detect a listing inside the iframe.

2. Check the browser console for blocked requests

If the console reports a Content Security Policy violation, reopen Content Security Policy (CSP) in the widget builder and use the requirements for the snippet you installed. Merge those requirements into the current policy. Preserve the script’s integrity, crossorigin, and data-* attributes when copying it or configuring an optimizer. StrollPlace Widgets caching and optimization notes

Example. The bootstrap loads, but the console reports a connect-src violation for https://widgets.strollplace.com. Compare the enforced policy with the current builder output and update the relevant directive. If you test a proposed policy in report-only mode, remember that the existing enforced policy still applies.

3. Check the provider and placement

Open the builder, choose Listing pages, and select your provider explicitly. Review the placements it exposes. A search result page, standalone property page, and listing lightbox are separate placements. If the builder supports search results and the section is configured to stay closed, check below the results for the expandable section before treating it as missing.

If you installed the WordPress plugin, check StrollPlace → Overview for service consent and StrollPlace → Listing pages for the active integration mode. Auto enables supported listings across the site. Manual relies on explicitly placed listing configurations. A container alone doesn’t activate listing detection. StrollPlace Widgets installation reference

4. Compare location data and coverage

Test a working and a missing listing using the same template. Compare their city and state, and verify whether the listing exposes coordinates through the integration. A city-only match may be the most specific area the widget can show for that listing.

Example. Preview Albuquerque, NM with latitude 35.084 and longitude -106.653, then clear both coordinates and preview the same city again. That gives you a way to compare a coordinate-based preview with a city-based preview. If the live result differs, use the listing page’s own location data when diagnosing it.

For a market page that should always show the same location, use a Place card and choose the location manually. This also works beside an IDX iframe.

The location form displays an error when latitude is entered without longitude.
Enter both coordinates together, or clear both and preview with city and state.

What to include when you ask for help

Share the public listing URL, your provider, the placement you expected, and any relevant browser console error. If another listing works on the same site, send that URL too. The two pages give support a way to compare the template, embed, and location inputs.

Contact StrollPlace

See the IDX Broker setup guide for wrapper placement.