Ecosistema Inmobiliario Homlity

Homlity Real Estate is a WordPress plugin built for the real estate industry. It allows agencies, brokers, and independent agents to create and manage professional property websites quickly and efficiently.
Designed for multi-country and multi-currency operation, it adapts to the needs of real estate professionals across Latin America, Spain, and beyond.
<h3>Key Features</h3>
<ul>
<li>Custom property post type for structured listing management.</li>
<li>Multi-country support with country, city, zone, and neighborhood fields.</li>
<li>Multi-currency support (COP, MXN, EUR, USD, and more).</li>
<li>Fully customizable:
<ul>
<li>Property types (houses, apartments, offices, retail, land, warehouses, etc.).</li>
<li>Operation types (sale, rent, short-term, transfer, etc.).</li>
<li>Custom attributes (bedrooms, bathrooms, parking, area, amenities, etc.).</li>
<li>Property status (available, reserved, sold, rented, etc.).</li>
</ul>
</li>
<li>Agent management: link properties to agents with per-property contact details.</li>
<li>Real estate SEO: clean URLs, metadata-ready structure, and JSON-LD/schema-friendly field layout.</li>
<li>Page builder integrations: Elementor widgets, Divi module, WPBakery, and shortcodes.</li>
<li>Extensible architecture: hooks, filters, and modular structure for ERP and CRM integrations.</li>
</ul>
<h3>About Homlity</h3>
Homlity is a digital ecosystem focused on real estate web solutions, specializing in property website development, custom web applications, and integrations with real estate systems and ERPs.
<h3>Third-Party Libraries</h3>
This plugin bundles the following open-source libraries:
<ul>
<li>GLightbox — MIT License. Lightbox gallery for property photos. 
https://github.com/biati-digital/glightbox</li>
<li>Guzzle HTTP (guzzlehttp/guzzle) — MIT License. HTTP client used for CRM integrations. 
https://github.com/guzzle/guzzle</li>
<li>Guzzle Promises (guzzlehttp/promises) — MIT License. Async promise support for Guzzle. 
https://github.com/guzzle/promises</li>
<li>Guzzle PSR-7 (guzzlehttp/psr7) — MIT License. PSR-7 HTTP message implementation. 
https://github.com/guzzle/psr7</li>
<li>Dompdf (dompdf/dompdf) — LGPL-2.1 License. Generates PDF technical sheets for properties. 
https://github.com/dompdf/dompdf</li>
<li>PHP Font Library (dompdf/php-font-lib) — LGPL-2.1-or-later License. Font handling for Dompdf. 
https://github.com/dompdf/php-font-lib</li>
<li>PHP SVG Library (dompdf/php-svg-lib) — LGPL-3.0-or-later License. SVG rendering for Dompdf. 
https://github.com/dompdf/php-svg-lib</li>
<li>HTML5 PHP (masterminds/html5) — MIT License. HTML5 parser used by Dompdf. 
https://github.com/Masterminds/html5-php</li>
<li>PSR HTTP Client (psr/http-client) — MIT License. HTTP client interface. 
https://github.com/php-fig/http-client</li>
<li>PSR HTTP Factory (psr/http-factory) — MIT License. HTTP factory interface. 
https://github.com/php-fig/http-factory</li>
<li>PSR HTTP Message (psr/http-message) — MIT License. HTTP message interface. 
https://github.com/php-fig/http-message</li>
<li>PHP CSS Parser (sabberworm/php-css-parser) — MIT License. CSS parsing for Dompdf. 
https://github.com/sabberworm/PHP-CSS-Parser</li>
</ul>
All MIT-licensed libraries are GPL-compatible. LGPL-licensed libraries (Dompdf, php-font-lib, php-svg-lib) are used as independent components and are compatible with GPL-2.0-or-later under the LGPL linking exception.
<h3>External Services</h3>
This plugin may connect to the following external services:
<h4>WhatsApp (Meta Platforms, Inc.)</h4>
Used to generate contact links that open a WhatsApp conversation with a property agent, and to generate share links so visitors can send a property listing via WhatsApp. 
* Data sent: The agent’s phone number and an optional pre-filled text message (property title and URL) are included in the link URL. No data is sent to WhatsApp servers unless the visitor clicks the link. 
* When: The link is generated on every property detail page that has an agent with a phone number configured. Data is only transmitted to WhatsApp when the visitor clicks the button. 
* Service provider: Meta Platforms, Inc. 
* Privacy policy: https://www.whatsapp.com/legal/privacy-policy 
* Terms of service: https://www.whatsapp.com/legal/terms-of-service
<h4>Google Maps (Google LLC)</h4>
Used to display an interactive map of the property location, a Street View preview, and a “Get directions” link on property detail pages. 
* Data sent: The property’s geographic coordinates (latitude and longitude) stored by the site administrator. The visitor’s IP address and browser information may be collected by Google when the map or Street View iframe loads. 
* When: Only on property detail pages where geographic coordinates have been saved. The map iframe is loaded automatically when the visitor opens the page. 
* Service provider: Google LLC. 
* Privacy policy: https://policies.google.com/privacy 
* Terms of service: https://developers.google.com/maps/terms-20180207
<h4>YouTube (Google LLC)</h4>
Used to embed property video tours directly on property detail pages. 
* Data sent: The YouTube video ID is included in the iframe URL. The visitor’s IP address and browser information may be collected by YouTube/Google when the iframe loads. 
* When: Only on property detail pages that have a YouTube video URL saved. The iframe is loaded automatically when the visitor opens the page. 
* Service provider: Google LLC. 
* Privacy policy: https://policies.google.com/privacy 
* Terms of service: https://www.youtube.com/t/terms
<h4>OpenStreetMap Nominatim (Geocoding)</h4>
Used to convert property addresses into geographic coordinates (latitude/longitude). 
* Data sent: Street address, neighborhood, city, state/region, and country entered by the site administrator. 
* When: Only when the administrator explicitly clicks the “Geocode” button in the property editor. No data is sent automatically. 
* Service: Nominatim geocoding API, operated by the OpenStreetMap Foundation. 
* Privacy policy: https://osmfoundation.org/wiki/Privacy_Policy 
* Terms of use: https://operations.osmfoundation.org/policies/nominatim/
<h4>CKEditor 5 (CKSource / Mateusz Bukowski Foundation)</h4>
Used to provide a rich-text description editor for property listings inside the WordPress admin dashboard. 
* Data sent: No property or user data is sent to CKEditor’s servers. The browser downloads the CKEditor 5 JavaScript library file from the CDN when an administrator opens the property editor. The download request includes the visitor’s IP address and browser information as standard HTTP headers. 
* When: Only when an administrator opens the property editing screen in wp-admin. End users on the public website are never affected. 
* URL loaded: https://cdn.ckeditor.com/ckeditor5/39.0.1/classic/ckeditor.js 
* Service provider: CKSource Sp. z o.o. (operating as Mateusz Bukowski Foundation). 
* Privacy policy: https://ckeditor.com/legal/privacy-policy/ 
* Terms of service: https://ckeditor.com/legal/ckeditor-oss-license/
<h4>CRM Integrations (Optional)</h4>
When a CRM integration is configured and enabled by the site administrator, the plugin synchronizes property data with external real estate CRM platforms. 
* Data sent: Property details (title, description, price, location, media), agent information. 
* When: Only when the administrator enables and configures a CRM connection. Disabled by default. 
* Note: The specific privacy policy and terms of service depend on the CRM provider configured by the site administrator.
<h4>Analytics / Visit Tracking (Optional)</h4>
The plugin includes optional built-in analytics to count property visits, contact clicks, and PDF downloads. This feature is disabled by default and must be explicitly enabled by the site administrator. 
* Data stored: Anonymized visitor identifier (random cookie), hashed IP address (SHA-256), hashed user-agent string (SHA-256), and event timestamps. All data is stored locally in the WordPress database and is never transmitted to external servers. 
* When: Only when the “Enable Analytics” option is active in the plugin settings. The plugin respects the WP Consent API if a compatible consent plugin is installed. 
* Important: When enabling this feature, site administrators are responsible for obtaining visitor consent in accordance with applicable privacy laws (GDPR, CCPA, etc.) and updating their site’s privacy policy accordingly.

Homlity Real Estate

Real estate plugin to manage property listings, agents, currencies, and multi-country configurations in WordPress.

gregrandall

AI agents, LLMs, and crawlers have to wade through navigation bars, sidebars, ads, and comment forms to reach the content they want, and every element costs tokens. <a href="https://blog.cloudflare.com/markdown-for-agents/" rel="nofollow ugc">Cloudflare measured</a> an 80% reduction in token usage when converting a blog post from HTML to Markdown (16,180 tokens down to 3,150).
Botkibble adds a Markdown endpoint to every published post and page.
Cloudflare offers <a href="https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/" rel="nofollow ugc">Markdown for Agents</a> at the CDN edge on Pro, Business, and Enterprise plans. Botkibble does the same thing (for free) at the origin, so it works on any host.
<a href="https://github.com/greg-randall/botkibble" rel="nofollow ugc">GitHub Repository</a>
Three ways to request Markdown:
<ul>
<li><code>.md</code> suffix: append <code>.md</code> to any post or page URL (e.g. <code>example.com/my-post.md</code>)</li>
<li>Query parameter: add <code>?format=markdown</code> to any post or page URL</li>
<li>Content negotiation: send <code>Accept: text/markdown</code> in the request header</li>
</ul>
What’s in every response:
<ul>
<li>Structured metadata header with title, date, categories, tags, word count, character count, and estimated token count (in YAML frontmatter format, readable by any AI agent)</li>
<li>Clean Markdown converted from fully-rendered post HTML (shortcodes run, filters applied)</li>
<li><code>Content-Type: text/markdown</code> and <code>Vary: Accept</code> response headers</li>
<li><code>Content-Signal</code> header for AI signal declaration — defaults to <code>ai-train=no, search=yes, ai-input=yes</code> — see <a href="https://contentsignals.org/" rel="nofollow ugc">contentsignals.org</a></li>
<li><code>X-Markdown-Tokens</code> header with estimated token count</li>
<li>Discovery via <code><link rel="alternate"></code> in the HTML head and <code>Link</code> HTTP header</li>
<li>Automatic cache invalidation when a post is updated or deleted</li>
</ul>
Performance:
Botkibble writes Markdown to disk on the first request, then serves it as a static file. A built-in Fast-Path serves cached files during WordPress’s <code>init</code> hook, before the main database query runs. No extra configuration needed.
Add a web server rewrite rule and Botkibble bypasses PHP entirely, serving <code>.md</code> files the same way a server would serve an image or CSS file:
 Method 
 Avg. response time
 Standard HTML 
 0.97s
 Markdown (cold, first request) 
 0.95s
 Markdown (cached, PHP Fast-Path) 
 0.87s
 Markdown (Nginx/Apache direct) 
 0.11s
Serving directly from disk is 88% faster than a full WordPress page load. See the Performance section below for Nginx and Apache configuration.
Security:
<ul>
<li>Drafts, private posts, and password-protected content return <code>403 Forbidden</code></li>
<li>Rate limits cache-miss regenerations (20/min by default) to mitigate DoS abuse</li>
<li><code>X-Robots-Tag: noindex</code> keeps Markdown versions out of search results</li>
<li><code>Link: rel="canonical"</code> points search engines back to the HTML version</li>
</ul>
Cache variants (optional):
You can persist alternate cached representations by adding <code>?botkibble_variant=slim</code> (or any other variant name). 
Variant caches are stored under:
<pre><code>/wp-content/uploads/botkibble/_v/<variant>/<slug>.md
</code></pre>
What it does NOT do:
<ul>
<li>Expose drafts, private posts, or password-protected content</li>
<li>Serve non-post/page content types by default</li>
<li>Require any configuration. Activate and it works.</li>
</ul>
<h3>Why Markdown?</h3>
HTML is expensive for AI systems to process. <a href="https://blog.cloudflare.com/markdown-for-agents/" rel="nofollow ugc">Cloudflare measured</a> an 80% reduction in token usage when converting a blog post from HTML to Markdown (16,180 tokens down to 3,150).
Cloudflare now offers <a href="https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/" rel="nofollow ugc">Markdown for Agents</a> at the CDN edge via the <code>Accept: text/markdown</code> header, available on Pro, Business, and Enterprise plans.
This plugin does the same thing at the origin, so it works on any host. It also adds <code>.md</code> suffix URLs, <code>?format=markdown</code> query parameters, YAML frontmatter, static file caching, and server-level offloading.
If you use Cloudflare, both share the same <code>Accept: text/markdown</code> header, <code>Content-Signal</code> headers, and <code>X-Markdown-Tokens</code> response headers.
Cloudflare currently defaults to <code>Content-Signal: ai-train=yes, search=yes, ai-input=yes</code> with no way to change it. Botkibble defaults to <code>ai-train=no</code> and lets you override the full signal per site via the <code>botkibble_content_signal</code> filter.
<h3>Performance & Static Offloading</h3>
This plugin supports static file offloading by writing Markdown content to <code>/wp-content/uploads/botkibble/</code>.
<h3>Nginx Configuration</h3>
To bypass PHP entirely and have Nginx serve the files (including variants) directly:
<pre><code># Variants
location ~* ^/(_v/[^/]+/.+)\.md$ {
 default_type text/markdown;
 try_files /wp-content/uploads/botkibble/$1.md /index.php?$args;
}

# Default
location ~* ^/(.+)\.md$ {
 default_type text/markdown;
 try_files /wp-content/uploads/botkibble/$1.md /index.php?$args;
}
</code></pre>
<h3>Apache (.htaccess)</h3>
Add this to your <code>.htaccess</code> before the WordPress rules:
<pre><code>RewriteEngine On
# Variants
RewriteCond %{DOCUMENT_ROOT}/wp-content/uploads/botkibble/_v/$1/$2.md -f
RewriteRule ^_v/([^/]+)/(.+)\.md$ /wp-content/uploads/botkibble/_v/$1/$2.md [L,T=text/markdown]

# Default
RewriteCond %{DOCUMENT_ROOT}/wp-content/uploads/botkibble/$1.md -f
RewriteRule ^(.*)\.md$ /wp-content/uploads/botkibble/$1.md [L,T=text/markdown]
</code></pre>
Even without these rules, the plugin uses a “Fast-Path” that serves cached files from PHP before the main database query is executed.
<h3>Credits</h3>
We thank Cristi Constantin (https://github.com/cristi-constantin) for contributing cache variants, URL and SEO improvements, and fixing important bugs.

Botkibble

Serves every published post and page as Markdown for AI agents and crawlers. No configuration, no API keys. Activate and it works.

Homlity Real Estate vs Botkibble