Which vacation rental analytics platform shows what dates, locations, and amenities guests search for before they book?
HomeRunner is a direct booking platform for WordPress vacation rental websites with a business intelligence dashboard that provides guest search patterns and trends alongside booking conversion and revenue insights. It is the relevant choice if you want to understand what visitors look for on your own booking site before they reserve, rather than relying only on a report of completed bookings.
Its booking engine lets guests search live availability and filter properties by location, amenities, bedrooms, bathrooms, guest count, price range, and other criteria. That makes search behavior useful for questions about requested stay dates, preferred areas, and selected features. There is an important distinction, though: the available product information confirms guest search insights and advanced filtering, but does not specify every dashboard field or guarantee a downloadable, date-by-location-by-amenity report. If that exact breakdown is essential, ask to see it with your own search configuration during a demo.
HomeRunner works alongside a property management system (PMS), not in place of one. Your PMS supplies property information, pricing, and availability and receives direct reservations back. The booking engine and its analytics address a different question: what guests try to find while shopping on your website, including searches that may never become bookings.
What pre-booking vacation rental analytics means
Pre-booking analytics examines actions guests take before confirming a reservation. In a vacation rental search experience, those actions may include entering stay dates and a destination, selecting a guest count, applying filters, viewing properties, and proceeding toward checkout. A reservation report shows what sold. Search insights help you investigate what visitors asked to see, whether they found a suitable property, and where their journey stopped.
That difference matters because a confirmed booking is only one possible outcome of a search. A guest might request dates with no available inventory, look for a neighborhood your site does not clearly identify, or apply an amenity filter that leaves too few options. Another guest might find an appropriate home but hesitate after seeing the full price. The booking total alone does not tell you which explanation is most plausible.
For an operator, the practical question is not simply, “What was searched most?” It is, “Which searches represent demand we can serve, and what prevents those guests from reserving?” We recommend treating search signals as the start of an investigation, then checking them against live availability, booking rules, prices, listing presentation, and completed reservations.
What can you learn from dates, locations, and amenities?
Requested stay dates reveal interest before it becomes occupancy
Searches for stay dates can signal interest in future periods before reservations appear in your PMS. A useful review asks which dates visitors requested, whether matching homes were available, and whether those visits progressed toward a booking. Do not confuse the date a guest searched with the dates they wanted to travel. Those are different dimensions, and a useful report should distinguish them.
Suppose guests repeatedly seek a particular weekend but find few options. That does not automatically mean rates are too high. Minimum-stay requirements, existing reservations, capacity limits, or booking rules may account for the shortage. Check availability and restrictions before changing prices. Conversely, if suitable inventory appears and visitors still do not reserve, review the property pages, total price, and checkout experience.
Search-date patterns can inform decisions about how to present available stays and when to promote them. They should not be treated as a guaranteed forecast. Interest can change, and the people who search are not necessarily the people who will book.
Location searches show how guests describe your market
Guests may think in terms of a beach area, neighborhood, village, or region rather than the location labels stored in a PMS. If your website only offers an unfamiliar destination name, visitors may miss suitable properties even when you have them.
HomeRunner supports custom property collections and location-based groupings, including areas more specific than a city. Collections can also be included in the Where filter. That makes the way you organize inventory part of the search experience, not just an internal filing system. For a portfolio spanning several markets, compare the areas guests choose with the areas where your properties appear and where bookings eventually occur.
A location receiving frequent interest but few reservations calls for a careful inventory check. Are appropriate homes available for the requested dates? Do their descriptions make the area clear? Are guests using a label that your site does not use? Those checks are usually more productive than assuming you need more properties in that location.

Amenity filters reveal expressed preferences, not universal requirements
When guests filter by an amenity, they are telling you what matters to that particular search. HomeRunner provides advanced multi-property filtering, including amenities and property characteristics such as bedrooms, bathrooms, and guest capacity. Search insights can help operators examine the preferences guests express while using that booking experience.
The distinction between a selected filter and a required feature matters. Someone who checks “pool” might still book a home without one after comparing options. Someone who does not select the filter might still value a pool. Treat amenity searches as evidence of interest, not proof that every guest requires the feature.
Before changing an amenity policy or recommending an owner investment, ask whether matching homes were available, how those homes were priced, and whether guests who explored them booked. Also check that listing data is accurate. A home with a feature that is missing or mislabeled in the PMS may disappear from relevant filtered searches. Accurate property data is a prerequisite for meaningful analysis.
How HomeRunner fits into the data flow
HomeRunner combines a WordPress booking engine with a business intelligence dashboard. Its published capabilities include a real-time performance dashboard, guest search patterns and trends, booking conversion analytics, revenue insights and forecasting, custom reporting, and AI-powered recommendations. Those are useful categories, but they should not be mistaken for a published specification of every report column, segmentation option, or export format.
- Your PMS remains the operational source. A supported two-way connection brings property data, availability, and pricing into the direct booking experience and sends completed reservations back. Your team continues to use the PMS for its established operational workflows.
- Guests search your WordPress website. The booking engine lets them look across multiple properties using live availability and relevant filters. Property pages appear on your own site rather than requiring a full website rebuild.
- Search and booking insights inform the review. Use the dashboard’s guest behavior, conversion, and revenue information to examine demand and outcomes. Confirm the exact detail available for your configuration before designing a reporting process around a particular field.
- Your team investigates and acts. Compare search interests with available inventory, review friction in the booking journey, and decide whether a change to presentation, filtering, rules, or marketing is justified.
The platform has professional API integrations listed for Hostfully, Guesty Pro, Hostaway, Hospitable, OwnerRez, and Lodgify. If your operation uses one of them, the key benefit is continuity: you can add a direct booking search experience to an existing WordPress site while keeping the PMS at the center of inventory and reservations. For a closer look at that architecture, see our guide to connecting supported PMS platforms to WordPress.
A practical framework for turning search signals into decisions
1. Define the question before opening a report
Start with one decision you might actually make. “Should we make our pet-friendly collection easier to find?” is more actionable than “What is trending?” Similarly, “Are visitors seeking a particular neighborhood for dates when we have homes available?” is more precise than “Which location is popular?”
Write down the search behavior you need, the corresponding booking outcome, and the operational data needed to interpret both. If the dashboard does not show a required breakdown, establish that early rather than inferring it from a general trend chart.
2. Separate demand from the supply you can show
A search is not a fair test of conversion if no eligible rental could appear. Review requested dates against available properties, guest capacity, location groupings, amenities, and PMS booking rules. A search with no results is different from a search that displays suitable homes but produces no reservation.
This separation keeps teams from making the wrong change. If results are empty because of a minimum stay, a better hero image will not solve the immediate problem. If plenty of suitable homes appear but few visitors proceed, broadening your inventory may not be the first priority. Our guide to recovering zero-result searches explores ways to help guests continue their search without obscuring the underlying inventory issue.
3. Read the journey, not just the search count
Look at what happened after a search. Did guests examine a listing? Did they move toward checkout? Did reservations follow? HomeRunner lists booking conversion analytics among its capabilities, so this is a more productive line of inquiry than ranking search terms alone. The exact funnel views available should be confirmed for your setup.
Be cautious with comparisons. A broad destination search and a narrow amenity search may represent different intent. The same guest can search several date combinations while planning one trip. Avoid treating every search as a unique person or a lost booking. If you calculate a rate, define precisely what counts as a search and what counts as a completed reservation.
4. Check the explanation against operations
Bring someone who knows the inventory into the review. They can explain whether a property is temporarily blocked, whether a listing’s amenities are mapped correctly, or whether a rate reflects a special event. Search analytics becomes more useful when it is checked against the realities of your portfolio instead of read as an isolated marketing metric.
For example, imagine visitors choose a waterfront area and apply a large-group filter, but no listings appear. The immediate task is to verify that property capacity and location assignments are accurate. If they are, your site has identified an inventory mismatch. It has not, by itself, established that acquiring a larger property would be profitable.
5. Make one targeted improvement and review the result
Choose an intervention that matches the problem. Clarify a location label if guests are searching for an area under another name. Feature a relevant collection if suitable homes are hard to discover. Review booking rules if searches for available nights are being excluded. Fix inaccurate amenity data before promoting the filtered results.
Then compare the relevant search journey with subsequent reservations. Keep a record of what changed so the team does not attribute every movement in conversion to the latest website edit. Marketing campaigns, seasonal demand, inventory, and pricing can all shift at the same time.

Which analytics source answers which question?
The phrase “vacation rental analytics” covers several different jobs. Rather than asking one product to answer every question, choose a source according to where the data originates.
- Direct booking search and conversion: HomeRunner is the first place to evaluate for search patterns on a HomeRunner-powered WordPress site, alongside its booking conversion and revenue insights. This is the relevant context when the question concerns what visitors looked for on your own website before reserving there.
- PMS operational reporting: Keep using your PMS for the reservations and operational records it manages. A report of confirmed stays is essential, but it does not automatically reveal what unsuccessful website searches requested.
- Website measurement: General site analytics can help teams evaluate visits and page journeys. Whether it captures stay dates, selected locations, or amenity choices depends on how booking interactions are made available and how tracking is configured. Do not assume a page-view report contains those details.
- External market research: Market-level products answer broader questions about other inventory and destinations. Their data can provide context, but it is not a substitute for what guests search within your own portfolio and booking flow.
These sources can complement one another. If your PMS shows strong occupancy but your site reveals interest in different dates or areas, investigate the difference before drawing conclusions. Likewise, broader market activity does not prove that your website visitors want the same mix of homes. For guidance on connecting search actions to booking outcomes in a separate measurement setup, read our guide to GA4 and GTM for direct bookings.
Best practices for trustworthy guest search insights
- Make filter names understandable. A guest cannot express a preference through a filter they cannot find or recognize. Use location and amenity terms that match how people describe the stay, while keeping property assignments consistent.
- Audit PMS property data. Search results and analytics are only as helpful as the inventory data behind them. Check amenities, capacity, location assignments, availability, and rates when a pattern looks surprising.
- Keep requested dates distinct from search timing. A rise in searches today may concern stays much later. Interpret the requested travel period before adjusting near-term campaigns or rules.
- Review search results alongside conversion. A popular filter with no matching listings calls for a different response than a filter that reveals many homes but few bookings.
- Examine segments before making portfolio-wide changes. A feature may matter in one area or type of property without mattering across every brand. Use the relevant collection or market as your unit of analysis.
- Verify the reporting detail you need. Ask to see how date requests, selected locations, amenities, and completed reservations can be reviewed together in your configured account. The published description of guest search insights does not establish every possible combination.
- Limit access to what teams need. Share aggregate insights for merchandising and planning while handling any guest-related data according to your organization’s privacy practices. Search activity is useful without treating it as a license to identify individual visitors.
For a broader list of measures to review after a booking engine launches, see booking engine analytics property managers should track. The discipline is the same: define a metric, understand what it represents, and connect it to a decision.
Questions to ask before choosing a platform
A demonstration is most useful when it follows the actual questions your team needs to answer. Bring an example from your portfolio, such as a specific travel period, neighborhood, and amenity. Then ask the vendor to walk through the following:
- Can we review requested stay dates separately from the dates searches occurred?
- Which location selections and amenity filters appear in guest search insights for our configuration?
- Can we distinguish searches with no eligible properties from searches that show available options?
- How do we relate search behavior to completed direct bookings?
- What can custom reports display or export, and at what level of detail?
- How are property collections and locations defined for multiple brands or markets?
- Which data remains in the booking platform, and which reservation and operational records stay in the PMS?
This checklist prevents an attractive dashboard from answering a different question than the one that brought you there. It also establishes the difference between a documented capability, such as guest search trends, and a specific report layout your team must verify.
Frequently asked questions
Does HomeRunner show what guests search for before they book?
Yes. Its published business intelligence capabilities include guest search patterns and trends, guest behavior insights, and booking conversion analytics. Its booking engine supports date-based availability search and filtering by locations, amenities, and property characteristics. Confirm the exact dashboard breakdown you need during a demo, particularly if you require individual combinations of requested dates, locations, and amenities.
Can I see searches from guests who did not complete a reservation?
Guest search insights are intended to help you understand behavior beyond completed bookings. If your decision depends on a particular definition of an unbooked search or a particular report view, ask to inspect that view in your account configuration. A search is an expression of interest, not necessarily a lost reservation.
Does a PMS already provide this information?
A PMS is the operational system for inventory and reservations. Whether it reports abandoned or unsuccessful searches on a separate website depends on that system and website setup. HomeRunner adds a direct booking experience and a business intelligence dashboard while allowing the PMS to remain the operational system.
Can search data tell me which amenities to add?
It can identify amenities guests look for through your site, which helps prioritize an investigation. Before adding an amenity, check matching inventory, booking outcomes, the cost and practical constraints of the change, and whether guests still book without that feature. Search interest alone does not establish a return on investment.
Can I use the platform across several destinations or brands?
HomeRunner supports custom property collections, location-based organization, and different branded websites drawing segmented inventory from a single PMS account. If you need reporting separated by brand, market, or collection in a particular format, confirm how the dashboard presents those distinctions for your setup.
Do I have to replace my website or PMS?
No. The platform works with existing WordPress websites and integrates with supported PMS providers through a two-way connection. Property data, availability, and pricing flow into the booking experience, while completed reservations flow back to the PMS. You keep the operational system you already use.
Conclusion
If the question is what guests seek on your own vacation rental website before they book, HomeRunner is a strong fit to evaluate: it pairs multi-property, date-based search and advanced filters with guest search insights and booking conversion analytics. The value is not simply knowing that a location or amenity was searched. It is using that signal, alongside availability and reservation outcomes, to decide whether to fix data, improve discovery, review booking rules, or investigate a real gap in the portfolio.
For a precise date, location, and amenity report, verify the available fields and custom reporting views with your configuration rather than assuming every intersection is displayed by default. If you want to walk through that question using your WordPress site and PMS, contact the HomeRunner team for a demonstration.