Third-Party HTML Widgets

Third-Party HTML Widgets

Effective Date: February 1, 2026   Last Updated: February 1, 2026

Hibu Policy

Hibu One Smart Sites support third-party functionality only through HTML-based widgets and client-side embed code. Plugin-based solutions, server-side integrations, and backend code execution are not supported. Third-party HTML widgets may be implemented only when they align with platform capabilities, performance standards, and compliance requirements.

This definition establishes the rules, limitations, and risk considerations associated with third-party HTML widgets. For a curated list of commonly recommended tools, refer to Preferred Third-Party Widgets. For technical integration capabilities, refer to How Third-Party Apps Are Integrated in Duda.

Definition

Third-Party HTML Widgets are externally hosted tools embedded into a Hibu One Smart Site using client-supplied HTML, CSS, JavaScript, or iframe code. These widgets execute entirely in the browser and do not interact with the site’s backend infrastructure.

Core Rules & Guidelines

  • Only client-side code (HTML, CSS, JavaScript, iframe) is supported.
  • Server-side languages (PHP, ASP, Node, Ruby, etc.) are not supported.
  • Plugins designed for CMS platforms (e.g., WordPress plugins) cannot be installed or executed.
  • Widgets must be provided as embed code by the client.
  • Hibu does not customize, debug, or maintain third-party code.
  • Third-party widgets must not compromise site performance, security, or usability.

Plugins vs. Widgets (Critical Distinction)

  • Plugins are software extensions that modify or extend a website’s backend functionality. They typically require direct access to the site’s content management system and server environment. Plugins are not compatible with Hibu One Smart Sites.
  • Widgets are self-contained code snippets that render functionality within a webpage using client-side technologies. Widgets do not require backend access and are the only supported method for third-party integrations on Hibu One.

CRM-Based Forms (Replacement Considerations)

Clients may choose to replace a native Hibu form with a form generated by a third-party CRM such as HubSpot, Salesforce, Zoho, or Pipedrive, provided the form is delivered as an embeddable widget.


Important considerations:

  • Form submissions will route directly to the client’s CRM.
  • Hibu conversion tracking for form submissions will no longer apply.
  • Reporting and attribution within Hibu marketing tools may be impacted.
  • Clients should consult directly with their CRM provider to confirm form capabilities and integration options.

MLS / IDX Widgets (Limited Support)

Full MLS or IDX integrations are not supported on Hibu One Smart Sites due to platform constraints.


Key Limitations

  • No backend access for MLS/IDX feeds
  • Limited or no API compatibility
  • Reduced SEO value when content is delivered via iframe
  • Potential delays or lack of real-time data updates
  • Strict MLS compliance rules that may exceed platform capabilities


Allowed Approach

Embeddable MLS/IDX widgets may be implemented when provided as client-side embed code. Supported examples include:

  • iHomefinder
  • IDX Broker Lite
  • RealBird


Clients must be informed of limitations and manage all subscriptions, setup, and compliance requirements.


Caution: Many MLS/IDX providers offer competing digital marketing services, including websites, SEO, paid search, and social media. Exercise care when recommending these tools, as they may encourage client migration away from Hibu services.

Ecommerce & Payment Platforms

Shopify

Embedding a full Shopify store directly into a Hibu One Smart Site is not recommended. Shopify is resource-intensive and can negatively impact site performance and Google Core Web Vitals when embedded.

Best Practice: Link to the Shopify store from the Hibu site rather than embedding it directly.


Square Plugins

WordPress-based plugins, such as the Square WooCommerce plugin, are not supported. Clients may use Square-provided embeddable widgets or payment buttons when available and supplied as HTML or JavaScript embed code.

Performance, SEO, and Compliance Considerations

  • Embedded widgets may affect page load speed and Core Web Vitals.
  • iframe-based widgets generally provide limited SEO value.
  • Third-party scripts may introduce accessibility or compliance risks.
  • Hibu reserves the right to restrict or remove widgets that negatively impact site stability or performance.

Client Responsibilities

  • Select and subscribe to the third-party service
  • Configure and maintain the widget
  • Provide valid embed code to Hibu
  • Manage updates, compliance, and billing with the provider

< Older Post

 Newer Post >