Skip to main content
View Categories

Property Tag System

1 min read

You can control HomeRunner’s behavior by adding tags to properties in your PMS. HomeRunner reads these tags and adjusts how it displays and handles each property.

Tag Prefixes #

Group Tags [g] #

The [g] prefix creates custom property groups based on shared characteristics or experiences that may not be captured by standard amenity filters.

Format: [g] Group Name

Example: [g] Romantic Getaways

Features:

  • Creates collections based on experience or theme
  • Useful for properties that share characteristics beyond standard amenities
  • Supports visual labels in property card views for select groups
  • Helps organize properties into meaningful collections for users

Location Tags [l] #

The [l] prefix (lowercase L) creates location-based collections that integrate with the search functionality.

Format: [l] Location Name

Example: [l] Region Name

Features:

  • Appears in the Where field of the multi-property search bar
  • Displays alongside city options in location searches
  • Case-insensitive but requires consistency across similar tags

Special Purpose Tags #

Featured Properties #

Tag: Featured

Features:

  • Designates premium property listings
  • Properties can be displayed in spotlight sections
  • Appears first in default search results
  • Sort order can be modified by user preference

Exclusion #

Tag: exclude

Features:

  • Prevents property display on the website
  • Works even for active PMS properties
  • Useful for temporary or permanent property removal from public view

Inclusion #

Tag: include

Features:

  • Only tagged properties will be synchronized to the website
  • Acts as a whitelist for property synchronization
  • Takes precedence over standard synchronization rules
  • Useful for selective property publishing

Hidden Properties #

Tag: hide

Features:

  • Properties sync to the website but remain hidden from browse and search views
  • Property details pages remain accessible via direct URL
  • Useful for properties that should be available when linked to directly, but not actively marketed
  • Allows selective visibility control while maintaining property data synchronization

Order Control Tags #

Sticky Positioning #

Tag Format: [sticky] number

Examples:

  • [sticky] 1
  • [sticky] 2

Features:

  • Forces specific order from the top of listings
  • Each number used only once
  • Higher priority than standard sort preferences
  • Useful for highlighting specific properties

Bottom Positioning #

Tag: [bottom]

Features:

  • Forces properties to appear at the end of listings
  • Overrides standard sort preferences
  • Useful for properties that should consistently appear last

Related Listings #

Tag: [rl]

Features:

  • Establishes relationships between properties
  • Useful for units and sub-units
  • Properties display on related property detail pages
  • Creates cohesive grouping for connected properties

Best Practices #

  1. Maintain consistency in tag naming across similar properties
  2. Use only one sticky position number per property
  3. Review excluded properties regularly
  4. Keep related listing tags synchronized between connected properties
  5. Consider user experience when creating custom groups