The Listdom Network App is a WordPress plugin that allows you to effortlessly connect multiple Listdom-powered websites into a unified network. With this plugin, you can designate one site as the Server (Master) and others as Client sites. Listings (and even bookings, if using the Booking addon) can be synced from clients to the server, creating a centralized directory that aggregates content from all child sites. This is perfect for franchises, multi-site directory businesses, or regional directories that roll up into a national site.
When the Network App plugin is installed on all sites (each child and the master), you’ll configure each site’s Site Method as either Client or Server. There should be exactly one server, the main site that will receive data, and one or more clients (subsidiary sites that send their listings to the server).
Server Site: Acts as the central hub. It collects listings from all connected clients. Typically, the server could be a global directory that aggregates all regions.
Client Site: A standalone Listdom site (like a regional directory) that will push its listings up to the server. It remains fully functional on its own, but also contributes data to the master site.
Connections are secured via API tokens. The Network App plugin uses the WordPress REST API to transfer data, authenticated by special tokens you generate.
If you choose “Server” as the method on a site, you’ll see options related to receiving data:
Push Listings to Clients: a toggle (on the server) to also send listings from server to clients. In most cases, you’ll leave this Off, because you likely want a one-way flow (clients to server). If enabled, the master’s listings would copy back to clients, which can lead to duplicates in a loop, use carefully.
A notice will display the server’s REST API URL (something like https://yourserver.com/wp-json/). You will need to give this URL to each client.
A list of Connected Clients will appear once clients connect. For each connected client, you’ll see its title, URL, admin email, and a status toggle (Enabled/Disabled). You can disable a client to stop syncing from that site without disconnecting completely.
You should also create an API Token on the server for the network communications:
Go to Listdom > Settings > API (the main Listdom API tokens section).
Generate a new token (give it a name like “NetworkToken”).
Copy this token string.
Keep this API token handy, each client will need it to authenticate when connecting.
For every child site, in Network settings select “Client” mode. You’ll then need to enter:
Server URL: The base URL of the server’s API. This is exactly the URL provided on the server site (ending in /wp-json/).
API Token (Server): The special API token you created on the server for network communication.
API for Communications (Client Token): On the client, you also need to select one of its own API tokens to use for identifying itself. Go to Listdom > Settings > API on the client site and create a token (e.g., “Client1Token”). Then select that token in this field. This token will be sent to the server to verify the client’s identity.
After filling in those fields, click the Connect button. The plugin will attempt to register the client with the server:
If successful, you’ll see a “Connected successfully!” message. The client site’s URL is now known to the server.
The Network settings will show a green success notice and the form will now display a Reconnect button (in case you need to change tokens).
On the server site’s Network panel, the new client will appear in the clients list (with its info). Ensure it’s enabled.
On Server site: Generate an API token and set site as Server.
On Client site: Create a client token and set site as Client.
Enter Server URL and Server API Token into the client’s Network settings.
Click Connect. Wait for the success message.
Verify on the Server site that the client appears and is enabled.
Once connected, the plugin will automatically start pushing content:
Listings: Whenever a new listing is published on a client site, it will be sent to the server site and added there (typically within a few minutes or even instantly via the REST API call). The listing on the server will carry a reference to its source client. Edits to the listing on the client should sync to the server as well. If a listing is deleted on the client, the server will eventually remove or disable it (depending on configuration).
Bookings: If you are using the Listdom Booking addon, there is a setting “Push Bookings to the server” on client sites. If enabled, any booking made on a client listing will also be sent up to the server. This is useful if the master site needs to aggregate booking data (say, a central booking calendar).
Push to Clients: On the server, if you enabled “Push Listings to Clients” and a client is set to receive them, any listing created on the server could be sent down. This is a less common scenario but might be used if the master site has some exclusive listings it wants to distribute to all sub-sites.
It’s important to note that each listing essentially lives on one primary site (the client). The server copy is like a mirror. The client owner still manages their listing on their site; the server site’s version might not be directly editable (or if edited, those changes could be overridden by the next sync from client). As the network admin, you’ll want to establish a clear content flow and inform your directory managers accordingly.
National and Regional Directories: A tourism board runs a main accommodations directory for the country. Regional offices in each state manage their own Listdom sites with local hotel listings. Using the Network app, all state sites connect to the main site. Now a traveler visiting the national directory sees every hotel from all states in one place. Each region controls its data, and the head office gets a master view.
Franchised Business Listings: A company offers branded directory websites to franchise partners (e.g., one site per franchisee, covering their territory). Thanks to the network, when Franchise A adds a new listing, it’s also published on the corporate master directory site. The master site stays up-to-date effortlessly, and franchisees benefit from extra visibility of being on the central site.
Backup and Redundancy: An directory owner sets up a client site as a sort of “live backup”. They input listings on their main site, which also pushes out to a private client site. In case the main (server) site has issues, they can quickly switch to using the client site. While not a typical use, the sync essentially cloned the content across sites, adding a layer of redundancy.
