TL;DR: In most of the United States you legally cannot sell a bottle from your own website. That single constraint should reshape the whole design. The site is not a store. It is the reason someone asks for your brand by name at a shop, so it has to do the wanting, and then tell them exactly where to go.
We built two concept sites in this category: one for Padrote Tequila and one for Ron Veleiro, a Dominican rum.
A note before we go further, because it matters: this business never hired us. We built that site unasked, as a demonstration of what we would do differently, and it is not their official site. It sits on our prototypes page with that label attached to it, and if the owner ever wants it taken down it comes down the same day.
Both are unusual builds because the normal conversion goal is off the table.
The constraint that changes everything
The three-tier system in the United States separates producers, distributors and retailers. With narrow exceptions that vary by state, a producer cannot ship a bottle to a consumer.
So there is no cart. There is no checkout. The metric a normal e-commerce agency would optimize does not exist.
What you have instead is a two-step conversion:
- Make someone want this specific bottle
- Tell them precisely where to buy it near them
Almost every mediocre spirits site fails step two while spending its whole budget on step one.
Where-to-buy is the most important page and usually the worst
You have seen the bad version. A page that says "available at fine retailers nationwide," or a store locator that returns a list of eleven addresses in a different state with no distances.
The good version is a map, a postcode field, and results sorted by how far away they are. If you can get product-level data from your distributor, say which ones actually stock which expression, because "carries the brand" and "has the añejo you just spent four minutes reading about" are different facts.
If you genuinely cannot build a live locator, do the honest fallback: name the chains and the specific independent shops, by city, and keep it current. A short accurate list beats a broken map.
Mark the whole thing up with structured data so the locations can be understood by search engines rather than trapped in a widget.
Age gates: necessary, usually implemented wrong
You need one. Implemented carelessly, it will quietly wreck your search visibility.
The failure mode is blocking the page server-side, or redirecting to a separate gate URL, so a crawler asks for your product page and receives a door. You have effectively told Google your site is one page that says "how old are you."
Do it this way instead:
- Render the real page in the HTML
- Overlay the gate client-side
- Remember the answer so people are not asked six times in one session
- Never redirect to a separate gate URL
Test it by fetching your own page the way a crawler would and reading what comes back. If the content is not in there, fix it before you do anything else on this list.
One more thing, and this is taste rather than law: a date-of-birth spinner on a phone is a genuinely miserable experience. A single yes-or-no is legally equivalent in most jurisdictions and roughly a hundred times less annoying.
The bottle is the design brief
This is the one category where I will defend a slow, image-heavy, scroll-driven site.
People are not buying a utility. They are buying a thing that will sit on a shelf in their home and say something about them. The site should feel like the object costs what it costs.
For the Padrote concept that meant editorial type, deep colour, and a slow reveal down the page instead of a product grid. For Ron Veleiro it meant building the whole thing around the story: the cane fields, the distillery's history, recipes.
But there is a hard limit. Heavy does not mean slow. Big imagery with modern formats and proper compression can still load fast, and a luxury site that takes six seconds does not read as luxurious, it reads as broken. The mechanics are in image optimization and why page speed matters.
Build it bilingual if the brand is
Ron Veleiro is a Dominican rum. Padrote is a tequila. Both have audiences who would rather read Spanish, and both have origin stories that lose something in translation.
If you go bilingual, do it properly: real translated pages at their own URLs with hreflang annotations, not a browser-translate widget. A widget is invisible to search engines and usually mangles exactly the kind of evocative copy this category depends on.
Half-translating is worse than not translating. A Spanish-language landing page that dumps you into English on the second click reads as an afterthought about the culture the product came from.
Recipes are the traffic engine
Here is the practical SEO answer for a category that cannot sell online.
Nobody searches your brand name until they know it exists. But an enormous number of people search for cocktails. Recipes are how a spirits brand earns search traffic from people who have not heard of it yet.
Do them properly. One page per cocktail, real photography, exact measurements, Recipe structured data so they can appear as rich results. Link each one back to the expression it uses.
That is a content engine that runs for years, and it is the single most underused asset in this category.
Build a trade page, because buyers visit too
The consumer is not the only person on your website.
Distributors evaluating whether to carry you, retail buyers deciding on shelf space, bar managers building a back bar, and journalists writing a roundup all land on the same homepage as someone looking for a cocktail recipe. Most spirits sites give them nothing.
A trade section costs almost nothing and answers the questions that audience actually has:
- Which states and markets you are currently distributed in
- Who your distributor is in each, with contact details
- Case configuration, UPC codes, and ABV by expression
- Downloadable high-resolution bottle images and your logo
- A press kit with the founding story already written, so a journalist does not have to invent one
That last item quietly does the most work of anything on this list. If you do not write your own story cleanly, someone else will write a worse version of it, and that version is what ends up in the roundup.
Awards and provenance belong above the fold
This category is unusual in that third-party validation genuinely moves people.
A medal from a recognised competition, a rating from a spirits publication, a protected designation of origin, the year the distillery was founded. These are the shortcuts a customer uses to decide whether an unfamiliar bottle at forty-five dollars is worth the risk.
Put them where the decision happens, on the product page near the price context, not on a separate awards page nobody visits. And be specific: the name of the competition and the year, not a gold circle graphic with no words in it.
If the distillery has real history, that is your most defensible asset. Nobody can copy 1892.
What we would build, in order
- Age gate that overlays rather than blocks
- A story-led homepage that justifies the price
- Product pages per expression, with tasting notes and real photography
- A where-to-buy that actually finds nearby stock
- Recipes, one per page, with structured data
- Bilingual if the brand's origin warrants it
- A speed pass, because none of the above survives a six-second load
Both concepts are on our prototypes page, labelled as the unsolicited demonstrations they are. If you are building a drinks brand and want to talk about it, here is where.
