Nex Directory helps you launch a searchable directory on WordPress, with the important day-to-day workflow already handled: submissions, moderation, maps, calendars, imports, notifications, and member dashboards.
Use it for event directories, local business directories, job boards, simple marketplaces, member portals, and community hubs. Start from a guided setup, then rename labels, choose pages, control who can submit, and decide what needs approval.
With the WordPress.org plugin, you can publish unlimited listings and events. There is no built-in three-listing or three-event cap: you can publish as much as your site, hosting, storage, roles, and moderation settings allow.
Nex Directory includes shortcodes, Elementor widgets, REST endpoints for approved integrations, CSV/JSON import tools, and readable local browser assets. It is designed to be useful out of the box while still giving developers a clear structure to customize.
The plugin includes a Chrome Extension setup screen for the official Nex Directory Scanner. It shows connection status, recent activity, policy checks, and a secure connection key you can rotate.
Official Nex Directory Chrome extension:
https://chromewebstore.google.com/detail/nexdirectory-scanner/dnijcccaedhkbbekcbacgbhldmminpip
The extension is optional. Nex Directory opens the Chrome Web Store only when an administrator clicks the download link.
Nex Directory Pro is a separate add-on for sites that need more advanced workflows, such as AI-assisted setup, custom templates, advanced fields and filters, private attending calendars, ticketing, paid boosts, QR check-in, analytics exports, team tools, white-label controls, and search indexing hooks.
Those Pro tools and any services they use are not bundled in this WordPress.org plugin. The directory, event, submission, moderation, map, calendar, and member features listed here continue to work without Pro.
Nex Directory avoids contacting outside providers unless a related optional feature is configured, shown on the page, or deliberately clicked. These notes explain what may be shared when you choose to use those features. Requests can include normal browser data such as IP address, browser details, and referrer, along with the feature-specific data described below.
NexDirectory.com receives normal browser request data only when an administrator clicks a product, documentation, or support link. The Chrome Web Store receives the same type of data after an administrator clicks the extension download link.
NexDirectory terms: https://nexdirectory.com/terms-of-service/
NexDirectory privacy: https://nexdirectory.com/privacy-policy/
Google terms: https://policies.google.com/terms
Google privacy: https://policies.google.com/privacy
reCAPTCHA loads only after a site owner configures it; browser data and verification tokens are sent to Google. Google Maps and geocoding are used only when selected and can receive an API key, entered location, coordinates, or map position. Clicking “Google Calendar” sends the listing title, dates, description, and location to Google Calendar. Opening a Google Docs preview sends the document URL to Google Docs Viewer.
Google terms/privacy: https://policies.google.com/terms and https://policies.google.com/privacy
Google Maps terms: https://cloud.google.com/maps-platform/terms
When a site owner selects OpenStreetMap, OSM France HOT, OpenTopoMap, Mapbox, Google Maps, CARTO or a custom provider, map/tile requests can include map position, tile coordinates, zoom level and entered location text. Server-side geocoding sends location text; Mapbox validation can send the configured token and style path.
OpenStreetMap policies/privacy: https://operations.osmfoundation.org/policies/tiles/ and https://osmfoundation.org/wiki/Privacy_Policy
Nominatim policy: https://operations.osmfoundation.org/policies/nominatim/
OSM France terms: https://www.openstreetmap.fr/mentions-legales/
OpenTopoMap usage: https://opentopomap.org/about
Mapbox terms/privacy: https://www.mapbox.com/legal/tos and https://www.mapbox.com/legal/privacy/
CARTO terms/privacy: https://carto.com/legal/ and https://carto.com/privacy/
When an owner adds YouTube or Vimeo media, the provider can receive normal browser request data when its thumbnail/player loads or a visitor opens it. Google Docs previews are covered above. Clicking a Facebook, X, LinkedIn or WhatsApp share control sends the public listing URL and, where supported, its title to that provider.
YouTube terms/privacy: https://www.youtube.com/t/terms and https://policies.google.com/privacy
Vimeo terms/privacy: https://vimeo.com/terms and https://vimeo.com/privacy
Facebook terms/privacy: https://www.facebook.com/terms/ and https://www.facebook.com/privacy/policy/
X terms/privacy: https://x.com/en/tos and https://x.com/en/privacy
LinkedIn terms/privacy: https://www.linkedin.com/legal/user-agreement and https://www.linkedin.com/legal/privacy-policy
WhatsApp terms/privacy: https://www.whatsapp.com/legal/terms-of-service and https://www.whatsapp.com/legal/privacy-policy
All plugin-owned PHP, JavaScript, and CSS needed to inspect and modify the release is included. No build step is required to install or run it.
Bundled third-party browser libraries are versioned upstream runtime files. Exact versions, licenses, and public source URLs are listed in docs/THIRD_PARTY_LICENSES.md. The portable source and commands for regenerating the Tailwind utility bundle are in docs/SOURCE_AND_BUILD.md.