Collection rows and community pages on your HomeRunner site can be driven by tags in Guesty. Not every attribute needs a tag, so it helps to know when to create one and how to name it.
When you do not need a tag. Anything Guesty already stores as an amenity or listing setting, such as pool, hot tub, pet policy, beach access, bedrooms, or guest capacity, syncs automatically and filters in your site’s search without a tag. A collection page can also be pointed at an amenity or a guest-capacity minimum instead of a tag. Contact support if you want a row driven that way.
When to use a tag. Tags are for attributes Guesty has no built-in field for, such as oceanfront, a view, a community name, or a seasonal campaign. Before you create a tag, check how many homes would carry it. A near-universal amenity makes a poor filter, and a rarely used tag produces an empty row.
Naming tags. Use short Title Case names with one idea per tag, and keep the spelling consistent once a page is live. The page address is built from the tag name, so renaming the tag in Guesty removes the homes from that page.
Place tags. For communities or areas, use the location prefix configured on your HomeRunner connection. This prefix also adds the place to the area dropdown in your search bar. The prefix must match exactly, including whether brackets or parentheses are used and whether there is a trailing space, so confirm the correct format with support before tagging.
When new tags appear. New tags show up on your site after the next property sync, which typically runs within a few hours.