Get started with PriceLabs now!
Want to learn what PriceLabs can do for you? See for yourself with a free trial. Get started now!

A comp set built from every listing within five miles of your property tells you almost nothing useful. It mixes studios with five-bedroom villas, four-star reviews with two-star ones, and pool homes with properties that have no outdoor space at all. Vacation rental comp sets only earn their name when they are narrow enough to reflect the guests actually choosing between your property and a handful of real alternatives, not the entire local market, a distinction covered further in the KPIs worth tracking once a set is live.
This guide covers the filtering criteria that make a comp set genuinely useful, the step by step process for building one, and how to keep it accurate as your market shifts. For the broader pricing context this fits into, see the guide to dynamic pricing for vacation rentals.
A comp set is a group of properties similar enough to yours to serve as a meaningful pricing benchmark. The value of a comp set comes entirely from that similarity. A broad set drowns real signal in noise, averaging together properties guests would never actually compare, while a set that is too narrow leaves you with too few data points to trust. The goal is the middle ground, typically five to fifteen properties, filtered tightly enough that every one of them is a genuine alternative a guest might book instead of yours, the same discipline behind setting a base rate in the first place.
Guest ratings are a proxy for quality and guest satisfaction, and comparing your pricing against properties with meaningfully different ratings distorts the benchmark in both directions. A tight comp set keeps review scores close to your own, typically within a few tenths of a point, and excludes clear outliers on either end so a handful of poorly rated listings do not drag your pricing signal down artificially, the same care behind reading occupancy against ADR rather than either number alone.

Occupancy tells you how well a comp is actually converting, not just how it is priced. A comp with occupancy well above yours may be priced more effectively, underpriced relative to demand, or simply benefiting from a stronger location within the same broad area. Filtering for comps in a similar occupancy range, then watching how that range shifts seasonally, keeps the comparison grounded in properties facing similar demand rather than outliers on either extreme, the same grounding pacing reports provide over time.

Two properties with the same bedroom count can serve completely different guests if one has a pool and the other does not. Matching on core amenities, Wi-Fi, parking, kitchen basics, keeps the baseline comparable, and matching on distinguishing features, beachfront access, a hot tub, pet friendliness, keeps the comparison relevant for whatever makes your property specifically competitive. Portfolio Analytics makes it easier to see which amenities correlate with a pricing premium in your specific market rather than assuming a generic list applies everywhere.
A studio and a five-bedroom house are never real alternatives for the same guest, no matter how close together they sit. Segmenting by bedroom count, property type, guest capacity, and even location nuance within a market, urban versus suburban, keeps every comparison an apples to apples one. Pricing multi-unit setups depends on getting this segmentation right before any of the other filters matter.
Start in your Market Dashboard, pulling data for your specific city, neighborhood, or zip code over the last three to six months. Apply property type and size filters first, matching bedroom count within roughly one room and guest capacity within a couple of guests, since this initial cut removes the largest source of noise before finer filtering begins.
From there, narrow by review score and occupancy, keeping ratings close to your own and excluding comps with extreme seasonality or significant data gaps that would skew the average. Apply amenity filters last, dropping anything missing your core essentials and prioritizing matches on the features that differentiate your listing. Aim to land somewhere between five and fifteen comps, reviewing the remaining list manually for any obvious outlier in pricing or quality that the filters missed.
Once the set is built, bring it into your pricing model. Dynamic Pricing uses the refined comp set to inform rate recommendations, and the tighter the input, the more the output actually reflects your real competitive position rather than a market-wide average.
Once a comp set is live, the dashboard views built around it are where the ongoing insight comes from. Heatmaps show geographic pricing clusters and where occupancy runs hot or cold within your area. Scatter plots comparing review score against nightly rate reveal whether guests in your market are actually paying a premium for quality or whether that assumption does not hold locally. Time series views show how pricing and occupancy for your comp set move through the seasons, which is what tells you whether a current dip is normal seasonality or an actual demand problem, the same read covered in slow season occupancy tactics.
Pacing reports extend this further, comparing how your comp set is filling this year against the same period last year, which catches a shift in relative competitiveness before it shows up as a revenue problem.
A narrow, well-built comp set surfaces market nuance that a broad set averages away entirely. It lets you price premium amenities with more confidence, because the comparison set genuinely reflects properties with and without those features rather than a blended average. It reacts faster to a real shift in your specific segment rather than a slower-moving market-wide trend, and it reduces the two failure modes that cost the most revenue, underpricing a property that is actually competitive, and overpricing one that is not, the same gap building owner trust with data depends on closing.
The most common obstacle is data scarcity. In a smaller or less saturated market, filtering tightly enough to get a meaningful comp set can leave you with too few properties to trust the average. When that happens, relaxing one filter, usually amenities before review score, is generally the better trade off than accepting a comp set of two or three listings, a call best made using Portfolio Analytics to see the tradeoff clearly.
The second is treating a comp set as a one time setup rather than a living input. Markets shift as new supply enters, seasonal patterns change, or a competitor renovates and repositions. Monitoring competitor pricing on an ongoing basis, alongside a quarterly review of the comp set itself, catches drift before it quietly skews your pricing. The third is underestimating the time cost of manual review, which is real but manageable with the filtering and dashboard tools built for exactly this workflow rather than a spreadsheet rebuilt from scratch each time.
Five to fifteen properties is the general target, tight enough to reflect genuine alternatives a guest would consider but wide enough to avoid drawing conclusions from too small a sample. In markets with limited comparable inventory, relaxing one filter is usually better than accepting a comp set of only two or three listings, the same tradeoff covered in Portfolio Analytics.
Property type and size come first, since a studio and a large home are never real alternatives regardless of location. Review scores, occupancy rates, and amenity matches refine the set further, and the order matters, filtering on the fundamentals before the finer details keeps the process efficient, the same sequencing behind pricing multi-unit setups.
Quarterly at minimum, with an additional check whenever a meaningful market change occurs, new supply entering the area, a competitor renovation, or a shift in seasonal demand patterns. A comp set built once and never revisited drifts out of relevance faster than most managers expect, the same drift monitoring competitor pricing regularly is meant to catch.
A broad comp set averages together properties guests would never actually compare, diluting the pricing signal. A hyper-specific comp set, filtered on property type, size, review score, occupancy, and amenities, reflects the real alternatives guests are choosing between, which makes the resulting pricing guidance far more actionable, the same actionability Dynamic Pricing depends on to recommend accurate rates.
Yes. Filtering too aggressively leaves too few comparable properties to form a reliable average, which is its own kind of noise. If a comp set shrinks below roughly five properties, relaxing the least important filter for your specific competitive position is usually the better fix than working with an unreliable sample, a judgment call easier to make with the underlying comp set concept clearly in mind.
Want to learn what PriceLabs can do for you? See for yourself with a free trial. Get started now!


