Website Catalogue Widget
IntegrationAvailable

Website Catalogue Widget

Display current MLS RealtyHub property and new-development inventory on your existing WordPress website, with less manual catalogue maintenance for your agency.

Website Catalogue Widget interface preview

Your agency website may look current while its property pages quietly fall behind. A price changes, a unit is no longer available, or a new development enters the working catalogue. If the website is maintained as a separate copy, someone has to find every difference and publish it again. The Website Catalogue Widget connects an existing WordPress website to catalogue data from MLS RealtyHub, so visitors can view current property inventory without the agency rebuilding the catalogue by hand.

Keep the website. Change how the catalogue is maintained

The Website Catalogue Widget is for an agency that already has a website and wants to show property inventory there. It adds a supported catalogue view to that existing site. MLS RealtyHub remains the professional B2B working environment, while the agency website remains the public destination controlled and branded by the agency.

This distinction matters. The widget does not create a second operational system for the team to maintain. The working property information stays in MLS RealtyHub, and the connected website presents the supported catalogue data to its visitors.

One catalogue should not become two maintenance jobs

Without a connection, the same property information can follow two separate routines. The team updates its working record, then repeats the change on the public website. Each extra routine creates another place to check and another opportunity for the public version to lag behind the working version.

The connected workflow

The widget changes the sequence:

  1. The agency maintains the relevant property information in MLS RealtyHub.
  2. The configured integration connects that catalogue data to the existing WordPress website.
  3. The website displays the supported catalogue view to visitors.
  4. When the working information changes, the connected view uses the current supported data rather than requiring the agency to rebuild a separate catalogue manually.

The principle is simple: improve the source, not every copy. This reduces repeated catalogue maintenance, but it does not mean that every page, file, portal, or external system updates automatically.

Two systems with a clear division of work

The integration brings together two systems with different jobs:

  1. MLS RealtyHub holds the working property inventory used by the agency or team.
  2. The agency’s WordPress website presents the connected catalogue to the public under the agency’s own web presence.
  3. The widget configuration provides the supported connection between the working catalogue and the website.

Catalogue information flows from MLS RealtyHub to the agency’s existing site. A visitor views the catalogue on the website; the agent or team continues managing the underlying working information in MLS RealtyHub. The widget does not provide bidirectional synchronisation, visitor data transfer into MLS RealtyHub, or CRM attribution as part of the described catalogue connection.

What moves through the connection

The widget brings an up-to-date MLS RealtyHub catalogue to an existing agency website, including current new-development inventory. This gives the public site a property view based on the supported working data rather than on a separately maintained set of listings.

The fields displayed, update frequency, and handling of interrupted updates depend on the specific implementation. An agency that relies on particular fields or update times should agree on those details during setup.

A practical agency scenario

Imagine an agency director whose team manages its inventory in MLS RealtyHub but already has a WordPress website with established branding and content. The director does not need a second website. The immediate problem is the property section: every change creates another publishing task, and the public catalogue can become detached from the team’s working information.

The agency requests the widget integration for its existing site. Once the supported connection is configured, the team continues working with property information in MLS RealtyHub, while website visitors see the connected catalogue. The result is not a new sales process or a replacement CRM. It is a simpler publishing arrangement for the catalogue the agency already needs to show.

When the widget is the right fit

The Website Catalogue Widget is a relevant option when:

  1. the agency already operates a WordPress website;
  2. the site needs a current property or new-development catalogue;
  3. the team works with the relevant inventory in MLS RealtyHub;
  4. maintaining a second set of public property records creates repeated work;
  5. the agency wants to preserve its existing website as the public destination.

For a company that needs an entirely new website, the Real Estate Website Service is a different scope. For a company that wants to send property data into its own custom-built system, API-Lite is a separate delivery option. Choosing the right route starts with the system that already exists and the result the company needs.

Setup starts with the existing site

This is a configured integration, not a universal switch inside a single MLS RealtyHub screen. The implementation is associated with the client’s own domain and WordPress website, and the exact setup must be discussed for that environment. Before setup, the agency should be ready to confirm:

  1. the existing website and its WordPress environment;
  2. the catalogue the site should present;
  3. the relevant MLS RealtyHub inventory and access;
  4. the required public presentation on the agency site;
  5. any implementation details that need technical confirmation.

Installation time, pricing, access method, WordPress compatibility, and configuration are discussed for the agency’s specific website and requirements.

What remains under the agency’s control

The agency keeps its own website, domain, brand, and professional context. Its team remains responsible for maintaining the working property information and for deciding what the public website is intended to show within the supported setup. MLS RealtyHub supplies the professional environment and the connected catalogue data; it does not become the agency, broker, or party to a transaction.

A live catalogue also has a clear boundary. It helps keep the connected presentation aligned with supported working data, but it cannot make separately downloaded files current, update unsupported external channels, or keep information copied elsewhere accurate.

Current availability and confirmed limits

The Website Catalogue Widget is Live. It is available as a professional integration for an existing website. The connection applies to the configured site and catalogue, rather than every website or publishing channel an agency may use.

Details to confirm

Discuss these details for the agency’s website before setup:

  1. the precise catalogue fields shown on the website;
  2. the update trigger and refresh frequency;
  3. handling of failed or delayed updates;
  4. technical access and authentication;
  5. compatibility if the site uses a platform other than WordPress;
  6. any requirements for analytics, lead capture, or CRM data flows.

These details define what the connected catalogue will do in the agency’s website environment.

Put your working catalogue on your existing website

If your team already manages property inventory in MLS RealtyHub and wants to present it through an existing WordPress site, the next step is to review the website, catalogue scope, and technical requirements together.

Frequently asked questions

Website Catalogue Widget, explained.

Does the widget replace our existing website?
No. It connects an MLS RealtyHub catalogue to an existing WordPress website. A separate website build belongs to the Real Estate Website Service.
Where does the team manage property information?
The team maintains the relevant working property information in MLS RealtyHub. The website presents the supported catalogue view through the configured connection.
Will every property field appear on our site?
The fields and presentation available for a specific website are agreed during the technical discussion.
Does the widget send website leads into a CRM?
Lead capture, visitor tracking, and CRM attribution are separate requirements from the catalogue connection. Discuss them as part of the implementation if your agency needs them.
Can the widget work with any website platform?
WordPress is the supported scenario described here. If your website uses another platform, discuss compatibility before planning the integration.
Website Catalogue WidgetCreate an Account ↗