Two funnels. Both now start with a question to an AI.
Property owners ask AI assistants who should manage their rental. Travellers ask where to stay. Viz tracks whether you get cited for both kinds of question, credits every booking and enquiry to the assistant that sent it, tells you whether an agent asking for availability can actually get it from your site, and lets you decide which machines read your listings.
The OTAs took the search box. AI assistants are taking the next one.
Owners shortlist managers by asking AI
"Who should manage my Airbnb in Scottsdale?" now goes to ChatGPT or Perplexity, and the answer names two or three companies. A management contract is worth years of fees, and if you are not in that answer, the owner signs with someone who was.
Travellers book where the answer points
Ask an assistant for a pet-friendly cabin near Gatlinburg with a hot tub and it answers with specific properties and links. Direct-booking sites that get cited take the reservation without paying an OTA commission on it.
Machines read your listings unseen
Your rates, photos, descriptions, and availability are fetched by AI crawlers and scrapers every day, and none of it appears in Google Analytics, because JavaScript trackers only see browsers.
See both funnels. Win the citations. Keep control of your listings.
Track the questions both audiences ask
Run owner prompts ("best short-term rental manager in your market") and traveller prompts ("where to stay near the lake with a dock") against the major AI engines. See whether you are cited, how prominently, and which competitor wins when you are not. AI visibility →
Publish the pages that win both funnels
Area guides for travellers, proof-of-results pages for owners: the AI Content Pipeline proposes them from your own AI-traffic evidence, writes and reviews the drafts, and tracks every published page for citations and referral visits. AI Content Pipeline →
Count the bookings AI sends
Every MotoPress or WooCommerce booking, quote request and enquiry is credited to the assistant that sent the traveller or owner, captured on your server, no GA4 needed. The capability map tells you whether an agent asking for availability can get it from your site, or whether it lives in Smoobu, Lodgify or Calendly, where an agent cannot reach it. And the agent gets tools: contact_business on every page (WebMCP) and /ai-contact/ to ask for dates on its traveller's behalf. AI Conversions →
Decide who gets your rates and photos
Welcome the retrieval bots that cite and link your properties. Refuse the scrapers that lift photos and undercut pricing, with robots.txt plus enforced 403s, verified from outside your CDN. AI Control →
AI assistants cite websites, not OTA listings.
Your Airbnb and Vrbo profiles live inside platforms that AI engines treat as someone else's storefront. When an assistant recommends a place to stay or a company to manage one, it cites pages it can crawl and link: your direct-booking site, your area guides, your service pages. A manager whose whole web presence is OTA profiles has given the engines nothing to cite.
The owner funnel is where this compounds. A traveller booking is one stay; a management contract is every stay that property produces for years. Owners research managers the way they research anything now, and an AI answer compresses the old page of ten blue links into a shortlist of two or three names. Your WordPress site is what gets you on that shortlist, and it is the one channel where you are not paying commission or renting placement.
Start with your own market's questions. If you cannot say today whether AI recommends you when an owner asks who manages rentals in your area, or when a traveller asks where to stay there, that is the first number worth getting.
Common questions, straight answers.
Do travellers really plan trips with AI?
Adoption is growing fast and the industry numbers vary. Viz counts the sessions that AI assistants actually refer to your site, so you can watch your own AI channel from a real baseline instead of guessing from headlines.
Most of my bookings come from Airbnb and Vrbo. Why does my own site matter?
Two reasons. Direct bookings keep the commission you would otherwise hand the OTA, and AI engines can only cite sites they can crawl, which your OTA profile is not. For property managers there is a bigger one: owners deciding who should manage their property research your company, not your Airbnb listings, and that decision is worth far more than any single stay.
Can Viz show whether AI recommends my management company to property owners?
Yes. Add the prompts owners ask, such as "who manages vacation rentals in your market" or "is self-managing an Airbnb worth it," and Viz runs them against the major AI engines and records whether you are cited, how prominently, and which competitors appear when you are not.
An assistant asked my site for availability. Can it get it?
Often not, and Viz will tell you why. If your calendar lives in an embedded booking widget from a channel manager, an agent reading your page sees a script, not dates. The capability map grades your site on describe, list, price, availability and act, shows where each answer lives, and shows what agents asked for against what your site could answer. Until the calendar is reachable, the agent still has tools: contact_business, registered on every page for the agent in a traveller's browser (WebMCP), and /ai-contact/ for agents arriving from outside a browser. Either way the request for dates lands in your inbox as a lead.
Should I block AI bots from reading my listings?
It cuts both ways. The same retrieval that powers a citation can send you a booking, while a scraper that lifts your photos and rates gives nothing back. Viz shows you per-bot counts of who reads your listings so you can keep the bots that send travellers and refuse the ones that only take, per bot, with the block verified from outside.
I run separate sites for different markets or brands. Do I need separate subscriptions?
No. One subscription covers up to 100 sites, each with its own dashboard, prompt tracking, and bot policy, so a portfolio of market sites or brands stays on one bill.
Will it slow my booking site down?
No. Viz runs on the server at about 2ms per request and loads no third-party JavaScript. It prints two small first-party inline scripts with no external requests: one for visitors arriving from an AI assistant and the consent-gated attribution cookie, and one that registers WebMCP tools in browsers that support the standard. Your booking flow and page speed stay as they are.