Do I need Property Hive?
No. The Sigora Widget block and shortcode work on any WordPress site. If you do use Property Hive, the widget adds itself to your property pages and reads each listing’s location, so there is nothing to place by hand.
Can I choose which lenses appear?
Yes. Switch any of the nine lenses on or off for your website in the Sigora console. The smart rules for Crime and air quality are set there too.
Are the area reports really included?
Yes. Every paid plan includes 1,000 co-branded area reports a month, and the free trial includes 15. There is no per-report charge.
What versions are supported?
The compatibility floor is WordPress 6.0+, PHP 7.4+, and Property Hive 1.5+ when Property Hive mode is active. The admin Plugin health view reports the installed WordPress, PHP, and Property Hive versions.
How does the plugin authenticate with Sigora?
The plugin uses the public Sigora site key and the detected WordPress site origin. There is no plugin API key and no separate identity stack.
What does Test connection check?
Test connection calls the Sigora plugin diagnostic endpoint with the configured site key and detected site origin. It reports missing site key, invalid key, blocked origin, inactive site, plan-derived lens availability, and bundle URL state when the Sigora backend returns those fields.
Why is the widget not showing on a Property Hive listing?
Automatic placement uses Property Hive’s standard property page: it adds the widget after the property details, or after the description where a theme prints it through WordPress’s normal content output. Some custom themes build their own property page and skip both. If so, ask whoever built your website to add [sigora_widget] to your property page template where the widget should appear. On a Property Hive property page it needs nothing else: it uses that property’s own location. The diagnostic log also records missing-location and disabled-listing states for administrators.
Can I choose where the widget appears on my property pages?
Yes. Automatic placement uses one fixed spot. For a different spot, untick automatic placement, add [sigora_widget] (or the Sigora Widget block) to your property page template where you want it, and tick Custom property template so your listings are still counted. A page never shows two Sigora widgets.
What location fields does Property Hive mode use?
Sigora uses the property’s map pin from Property Hive ( _latitude and _longitude) first, then the older _property_location_latitude and _property_location_longitude fields, then RealEstateListing JSON-LD geo.latitude and geo.longitude . A 0,0 pin counts as not set. It also keeps a postcode from common Property Hive postcode meta fields when coordinates exist, because broadband and mobile evidence is postcode-keyed. A postcode is the fallback location only when no usable coordinates are available.
Where do I set the lenses, layout, colours and size?
In your Sigora console, the single place to configure the widget’s appearance. The plugin only needs your site key; it does not duplicate those settings, so nothing in WordPress can clash with your console. A single listing can still narrow the lenses with the _sigora_show custom field (it cannot unlock lenses that are not enabled for the site), and _sigora_disable skips injection for that listing.
How does the plugin get updates?
Through WordPress, from the WordPress.org plugin directory. The plugin contains no updater of its own and does not check any Sigora URL for new versions, so update checks, the update notice and the auto-updates toggle all behave exactly as they do for any other directory plugin. Builds installed from a direct ZIP before the directory listing existed are replaced by installing the directory version once, after which updates arrive automatically.
Automatic updates stay off until you turn them on. Click “Keep sigora up to date automatically” on the plugin’s Sigora page, or use “Enable auto-updates” on the Plugins screen; both change the same WordPress setting. Most improvements need no plugin update at all, because the widget itself is served by Sigora.
What data leaves my site?
See the External services section above. In short: visitors’ browsers load the widget from Sigora and Sigora returns local-area data for the listing location you configured. Nothing personal held by WordPress is sent.
Does the plugin track visitors?
No. The plugin renders the hosted Sigora widget, which sets no cookies and loads no analytics scripts. Widget events are aggregate runtime events tied to site and listing context, not visitor identity.
