Farm-to-Table Restaurant Web Design in Boise, ID

More Boise field notes →

Your food costs more on purpose. The website has thirty seconds to say why.

A farm-to-table restaurant in Boise pays Treasure Valley prices for Treasure Valley produce, buys lamb from a ranch in the Wood River Valley instead of off a broadline truck, and prints a menu that changes when the growers’ harvest changes. The plate costs more than the plate across the street, and it should. The trouble is that the diner deciding between the two is doing it on a phone, in about thirty seconds, and the phone has to make the case before the food ever gets the chance.

Most of the time it does not. The site shows a menu from two seasons ago, a paragraph about “local ingredients” that every restaurant in Ada County also uses, and no clear way to book. The diner reads the price without the reason and picks the place that looked easier. The owner never sees it happen. The kitchen was never the problem.

Who is choosing, and how

Boise’s dining crowd has changed faster than most of its restaurants. The people filling the North End, the Bench and the new apartments downtown came from Seattle, Portland, the Bay Area and Salt Lake with restaurant habits already formed. They research. They read a menu before they walk in, they check whether the trout is from Idaho or from a bag, and they decide on a Wednesday for a Saturday. Add the visitors in for a Boise State game, a Treefort weekend or a conference at the Boise Centre, who know nothing about the city and search for everything.

Both groups start in the same place: a search on a phone, usually with a neighborhood or an occasion attached. The restaurant that answers that search with a real page, a current menu and an obvious way to reserve gets the table. The one whose best content is a chalkboard in the dining room does not, no matter how good the beets were last night.

The sourcing story is a search asset, not decoration

This is where farm-to-table has an advantage it rarely uses. The specifics that make the cooking good are the same specifics that make a page rank and make a diner trust it. Naming the farm outside Kuna, the orchard in the Sunnyslope, the dairy that does the cheese course, the week the morels showed up: that is content no chain and no delivery app can write, because they do not know it. Search engines reward pages that are plainly about a real place, and a diner who reads that page believes the price.

The mistake is putting that story in a single About paragraph and leaving it there. Spread across a site that is built for it, with a seasonal menu page that actually changes, a page about the growers, a page about private dinners and the harvest table, it becomes the reason the restaurant shows up for a couple planning an anniversary in the North End and for a group planning lunch after the Saturday market on 8th Street.

Boise runs on a short, sharp calendar

The busy stretches here are predictable and brief. Treefort in March. Alive After Five and the Saturday market crowds from June into September. Football Saturdays in the fall, when the blue turf fills downtown. The holidays, when every office in the city books a dinner. Then the long quiet from January to the end of February, when the Bench and the North End regulars carry the room and Bogus Basin takes the weekend money instead.

A restaurant’s search visibility should be doing its heaviest work before those peaks, not during them. The Treefort visitor is searching in February. The parents coming for a Boise State graduation in May are looking in April. If the pages that rank for those moments are in place a season early, the busy weekends fill with people who chose the restaurant on purpose. If they are not, the busy weekends fill with whoever walked past, and the quiet weeks are quieter than they need to be.

Where farm-to-table owners usually get it wrong

The menu is the first failure. A seasonal kitchen that posts its menu as a photographed PDF, or that updates the site twice a year because changing it means calling someone, is telling search engines and diners the same wrong thing: that nothing here changes. The site should make a menu change a five-minute job for whoever runs the pass, and it should publish that change as real text that search can read.

The second failure is treating the site as a brochure and the reservation as an afterthought. A farm-to-table cover in Boise is worth protecting, because the margin on that plate is thinner than the price suggests. A diner who found the restaurant, read the menu, believed the price and then could not find the reserve button has done everything but pay, and then walked to a competitor. The third failure is generic copy. “Fresh, local, seasonal” is on every site in the valley. It ranks for nothing and convinces nobody. What ranks and convinces is the name of the farm and the name of the dish.

How North Sea helps

We design and build websites for restaurants whose food is specific and whose sites are not. For a Boise farm-to-table restaurant, that means a site that carries the sourcing story in a way search engines and diners both read, a seasonal menu the kitchen can change itself, a reservation path that works on a phone in a parking garage off 8th Street, and local SEO aimed at the neighborhoods and occasions that actually fill the room. We keep the whole thing fast, because a diner who is already hesitating over the price will not wait for a hero video. If the plate is telling a story the website has not caught up to, start a project with North Sea Strategic.