No style pages
A gallery of can designs cannot answer "do you brew a dark beer" or "is your IPA bitter". Style pages capture the question before someone drives past.
Your next regular finds you by style, by neighbourhood or by patio. Your next distributor finds you by capacity, packaging and region. Both start with a search, and both land on whatever your site says about the beer.
Six lines on tap · taproom, tour and trade search
Nobody searches for "beverage producer near me". They search for a style, a feeling or an occasion, then check who is closest. That gap between what breweries publish and what drinkers type is where most taproom traffic goes missing.
Hazy IPA, pilsner, dry stout, sour, saison, barrel-aged porter and non-alcoholic options all carry their own search demand and their own expectations. A single "Our Beers" page with six logos cannot answer "what does your hazy IPA taste like" or "do you have anything dark on". Style pages can, and they keep working when the board rotates.
We build those pages around your actual brew sheet: grain bill outline, hop character, fermentation approach, packaging formats and where each beer pours. Descriptions stay factual. We do not invent tasting notes, we do not add health framing, and we do not turn a beer page into a medical claim.
A tap list last updated eleven months ago tells a visitor the brewery may be closed. We set up a lightweight board template your bar manager can update in a couple of minutes, with a visible "last updated" line and structured data that matches it.
Stage diagram: each vessel becomes a page topic, not a blog filler post.
A gallery of can designs cannot answer "do you brew a dark beer" or "is your IPA bitter". Style pages capture the question before someone drives past.
A tap list from last season makes visitors assume the place changed hands. Search engines see the same thing you do: a page nobody maintains.
Distributors and buyers want packaging formats, capacity, region and process. When that lives only in a PDF attached to an old email, the inquiry goes to a brewery with a page.
Tour queries are specific: private hire, group booking, weekend times. One paragraph cannot rank for four different intents.
Forty uncompressed taproom photos push mobile load time past the point where a visitor on a phone gives up before the address loads.
A full-page block that every crawler hits can hide content from search. A well-built gate remembers the choice and keeps indexable pages open.
We treat the taproom and the trade desk as two audiences sharing one site. The work splits accordingly, with the same technical spine underneath.
These two visitors share a love of beer and nothing else. One is deciding where to spend a Saturday. The other is deciding whether to put your kegs in twenty venues.
The trade side of the site is a business development tool. It is judged on qualified inquiries, not on session count.
Search language changes with the market. A US visitor asks for a "brewery near me" or "brew pub with food". A UK visitor types "taproom near me" or "craft beer bar". An Australian visitor searches "brewery tour" and "brewery restaurant". Export buyers add a country and a container format.
We map those differences instead of translating one page word for word. Where your site serves more than one market, we advise on hreflang, currency-neutral copy and region-specific tour or trade pages, so a distributor in one country is never shown a taproom offer in another.
Venue relationships matter too. Beer gardens, markets, stadiums and festival halls attract searches of their own. A short page for each recurring venue, with the dates you pour there, can capture demand that a generic events page misses.
Tour pages work when they answer group size, duration, access, what is included, and how to book. Private hire pages work when they list capacity, layout options and catering rules. Release days work when they carry a date, a style and a short note from the brewer. Each of these is a page, not a paragraph.
Most markets expect an age confirmation before alcohol content. That requirement is easy to meet without hiding the site from search engines. We build a gate that appears once, remembers the answer, and keeps the underlying pages readable by crawlers. Content stays in the HTML, not behind a screen that never resolves.
The gate wording is written per market, without health claims or drinking advice, and without pretending to be a legal opinion. Your team confirms the wording; we implement it cleanly and test it on mobile.
We review the site, the profile, the board, the trade pages and analytics, then write down the five queries you should own and do not.
Style, occasion, venue, region and packaging terms are grouped into page clusters, with a decision on what gets its own URL and what stays inside a page.
Templates and copy for the priority set: home, styles, tours, trade, events and contact. Photography is briefed at the same time so pages do not launch half dressed.
Profile categories, citations, reviews, schema and internal links. This is the slow part, and it is the part that makes the fast part stick.
A short monthly report: what moved, what did not, what we change next. Release pages get built before the release, not the week after.
Business types are generic. Figures are monthly and measured in the client's own analytics.
Taproom direction requests per month after six months, driven by style pages and a maintained board.
Wholesale inquiries per month in five months, after trade pages replaced a single contact form.
Non-brand organic sessions over seven months, with tour bookings doubling in the same window.
Two breweries with the same number of styles rarely need the same program. The quote reflects how many style and release pages you need, whether we write the copy, how many markets and languages you sell into, whether trade pages or export pages come first, and how much technical repair the current site needs.
You receive a written scope with page count, content duties, technical tasks, reporting cadence and the sequence of work. If a narrower first phase gets you to inquiries faster, we will propose that instead of a larger retainer.
Profile and local fixes can shift direction requests within four to six weeks. Style pages usually need two to three months before they hold a position against established competitors. Trade pages take longer because the queries are lower volume and the buyer is slower.
We draft from your brew sheet and a short interview with the brewer, then you approve every line. We do not invent flavour notes, awards or numbers. If a beer has no recorded ABV on your sheet, the page shows a placeholder until you supply it.
Yes, if the board is a template rather than a page builder project. We set up a simple editable board with a dated update line, and we train whoever closes the bar on how to publish it in a couple of minutes.
They usually help. The page answers buyer questions and routes the inquiry to you, and you decide who fulfils which region. We can also keep territory wording neutral so a distributor is not competing with your own page for the same term.
We implement the gate and the wording your team approves for each market. We are not a legal adviser, so the final compliance decision sits with you; our job is to make the gate fast, mobile friendly and invisible to crawlers.
Direction requests, phone taps, tour form completions, event ticket clicks and the share of new visitors from non-brand search. Where you have a booking or point-of-sale system, we tie those numbers back to pages.
Share your domain, your core styles and the markets you sell into. We will reply with the first pages we would build, the queries behind them and the order we would work in.