Skip to main content
View Categories

How to Use Lodgify Descriptions for Custom Property Data

Our application can automatically extract additional structured information (house rules, access details, tags, custom attributes, etc.) from your Lodgify listing description (additional locale) —if it follows a specific structure.

This guide shows you exactly how to format your Lodgify description so everything is parsed correctly.


Why This Matters #

By structuring your description properly, you unlock:

  • Better property details on your website
  • Automatic tagging and grouping
  • Featured property detection
  • Custom data fields (e.g. bedrooms, max guests, Wi-Fi speed)
  • Cleaner, more consistent content across platforms

If the structure is wrong, the system will ignore those sections.


Required Formatting Rules (Read This First) #

Follow these rules strictly:

  • Section titles must start with ** and end with **
  • Each section must be on its own line
  • Content must appear after its heading
  • Do not nest sections
  • Custom fields must use key=value
  • Tags must be one per line
  • Use plain text (HTML is okay, but unnecessary)

Supported Sections #

You can include any or all of the following sections.

1. Short Summary #

Used as a quick overview across listings.

**Short Summary**
A modern two-bedroom apartment near the city center, ideal for families and business travelers.

2. Space #

Describe the layout and what guests can expect inside.

**Space**
The apartment includes two bedrooms, a fully equipped kitchen, a living room, and a private balcony.

3. Neighbourhood #

Information about the surrounding area.

**Neighbourhood**
Quiet residential area with cafes, grocery stores, and parks within walking distance.

Note: “Neighborhood” is also accepted. We normalize it automatically.


4. Access #

Explain what parts of the property guests can use.

**Access**
Guests have full access to the entire apartment. Self check-in is available via smart lock.

5. Transit #

Nearby transportation options.

**Transit**
Bus and metro stations are within a 5-minute walk. Paid parking is available nearby.

6. Interaction #

How and when guests can contact you.

**Interaction**
We respect guest privacy but are available via phone or message if needed.

7. House Manual #

Rules and important instructions.

**House Manual**
No smoking indoors. Quiet hours after 10 PM. Please dispose of trash in designated bins.

8. Notes #

Optional extra information.

**Notes**
Early check-in or late check-out may be available upon request.

Custom Fields (Advanced) #

Custom fields let you define structured property data.

Format #

**Custom Fields**
bedrooms=2
bathrooms=1
max_guests=4
wifi_speed=300mbps
floor=3

Rules #

  • One field per line
  • Must use key=value
  • Keys should be lowercase, no spaces
  • Values can be text or numbers

These fields are stored and synced automatically.


Tags (Very Important) #

Tags are used to:

  • Assign categories
  • Create property groups
  • Define locations
  • Mark featured properties

Format #

**Tags**
family-friendly
city-center
pet-friendly
long-stay
featured

Rules #

  • One tag per line
  • No commas
  • Case-insensitive
  • Keep tags meaningful

If a “featured” tag is configured, it will automatically mark the property as featured.


Full Example (Copy & Paste) #

**Short Summary**
A modern two-bedroom apartment perfect for families and business travelers.

**Space**
Two bedrooms, fully equipped kitchen, living room, and private balcony.

**Neighbourhood**
Quiet area close to cafes, parks, and shops.

**Access**
Full apartment access with self check-in.

**Transit**
Metro and bus within 5 minutes walking distance.

**Interaction**
Available via phone or message if needed.

**House Manual**
No smoking. Quiet hours after 10 PM.

**Notes**
Early check-in subject to availability.

**Custom Fields**
bedrooms=2
bathrooms=1
max_guests=4
wifi_speed=300mbps

**Tags**
family-friendly
city-center
featured

Common Mistakes to Avoid #

❌ Missing ** around headings
❌ Writing multiple tags on one line
❌ Using : instead of = in custom fields
❌ Putting content before a heading
❌ Renaming section titles arbitrarily

If the parser can’t recognize a section, it will be ignored.


Need Help? #

If you’re unsure whether your description is structured correctly, contact support and share your listing ID. We’ll review it and confirm.