Methodology
How we build a valley census
VinoRadar publishes two kinds of data about Chilean wine tourism: valley censuses, built winery by winery, and a demand index measured inside our own platform. This page explains exactly how both are produced, what counts, what doesn't, and what we refuse to publish.
The single rule
Everything below follows from one principle.
If it cannot be verified on the winery's own official website, it is not counted as met.
Not as a maybe, not as a partial. It is recorded as not verifiable and counted as zero. This means every figure we publish is a floor, not an estimate. The real number can only be equal or higher, never lower.
What we measure
Five conditions, each with a strict definition. The definitions matter more than the results: a loose definition produces a flattering number that nobody can reproduce.
- 1 · Belongs to the valley
- The winery receives visitors in that valley. Producing wine there while hosting guests elsewhere does not qualify. Exclusions on this ground are declared by name in each report.
- 2 · Open to wine tourism
- The official site states that visits, tastings or experiences are available to the general public. A restaurant or a shop without a guided visit does not count. Neither does a navigation item labelled «Wine tourism» that links to a dead anchor.
- 3 · Booking without waiting for a person
- A booking engine, a shopping cart, or a WhatsApp link with a pre-filled message. These do not count: a contact email, a phone number, a contact form that waits for a human reply, a blank WhatsApp link, or a cart whose own page asks the visitor to confirm availability with the team before purchasing. The test is whether the visitor can finish alone, not whether a button exists.
- 4 · Price published
- A figure visible without writing to anyone, attached to a specific experience. «From $X» counts. «Enquire for rates» does not.
- 5 · Information in English
- An English page that covers the visit itself. Browser auto-translation does not count. Neither does a translated menu with an untranslated body, a language selector that leads to a different brand, or an English page that has not been updated in years.
- 6 · Winemaker identified
- The name appears on the winery's own site. A founder or a family surname does not count unless the site identifies that person as the winemaker.
How each field is recorded
Three things are stored for every field, every time.
- The exact URL where the condition was verified. Not the homepage: the specific page.
- The sentence that proves it, quoted at most briefly.
- The date of review. A census is a dated photograph. A figure without its date stops being true quite quickly.
Third-party sources — wine route associations, review platforms, travel agencies — are used only to discover that a winery exists. They are never used to fill a field. If a tour operator says a winery takes bookings but the winery's own site does not, the field is recorded as not verifiable.
How the figures are expressed
Two denominators, because one of them would distort the picture.
Conditions that depend on receiving visitors — booking, price, language — are reported both over the total number of registered wineries and over the subset that actually opens to the public. A winery closed to visitors cannot have a booking button, so measuring only against the full total exaggerates the friction a real visitor faces.
Both numbers appear in every report. Readers can choose which one answers their question.
The Demand Index
Measured inside VinoRadar, not estimated from external sources.
- What is counted
- Every confirmed search inside the VinoRadar wine finder, with the valley filter active at that moment. Typing is not recorded — only the confirmed search.
- What is excluded
- Page views, clicks, searches under three characters, repeats within the same session, traffic flagged as automated, and addresses exceeding the per-minute rate limit. Filtering happens server-side, before anything is stored.
- Time window
- A rolling window of 90 days, updated daily. We moved away from calendar months because the index reset to zero every first of the month, which made a working instrument look like a broken one.
- Publication threshold
- 30 searches per valley within the window. Below that, the valley is listed and labelled «insufficient sample». It is never silently omitted: omitting it would hide the shape of the data.
- Country of origin
- Resolved server-side from the request, never declared by the client. Clients can lie about their location; edge infrastructure cannot be asked politely.
What we will not publish
These limits are not a commercial restriction. They are what makes the rest of the data worth citing.
- Search terms tied to a named winery. The public index shows a headline, a ranking by valley and aggregate volume. The detail goes only to the winery concerned.
- Personal data of people who search. The IP address is converted into an irreversible fingerprint and discarded. No name, no email, no account required.
- Figures below the threshold. A valley with fewer than 30 searches shows a label, not a percentage.
- Anything we could not verify. Where sources disagree, we publish neither and say so.
Corrections
Being wrong is survivable. Being unwilling to correct is not.
If a winery finds a field recorded incorrectly, we fix it at no cost and leave a note of the correction. No commercial plan changes what a census says about a winery. A paying winery does not appear better rated. It appears better equipped, which is a different thing and is verifiable by anyone.
Corrections, questions and replication requests: contacto@vinoradar.cl