Farm-to-Table Restaurant SEO in Portland, OR

More Portland, Oregon field notes →

The chanterelles are on the menu, and the menu is a photo on Instagram

A couple on Division Street at a quarter past six on a Friday is choosing between three restaurants, and they are doing it by reading menus on a phone. Yours has the chanterelles from the Coast Range that came in Tuesday, the Netarts Bay oysters, the lamb from a farm in Yamhill County. None of that is on your website, because the menu on the site is a PDF from June and the current one is a photograph posted this afternoon. They pick the place two doors down whose menu they could actually read. The kitchen that does the hard work of sourcing seasonally lost a table to one that does not, over a document.

That is the specific way a Portland restaurant loses. Not on the food, which is why anyone opens a restaurant here, but on the gap between what the kitchen is doing and what the diner can find out.

What a cover is worth on a rainy Tuesday in Sellwood

Farm-to-table economics are thinner than most diners realize. Sourcing from small Willamette Valley growers costs more than the broadline truck, the menu changes with the harvest so the kitchen re-costs constantly, and the margin on a cover is narrow enough that a slow night is a real loss rather than a quiet one. Summer patio season covers a lot. The long wet stretch from November to April is where the year is decided, and it is decided by whether locals in Sellwood, Alberta, Mississippi and the Pearl choose you on an ordinary weeknight.

Those diners are choosing by phone and choosing by neighborhood. A restaurant that ranks for its part of the city, for the kind of meal it serves, and for the questions a Portland diner actually asks, fills the Tuesday. One that only ranks for its own name fills it on reputation alone, and reputation in a city with this many good kitchens is a slow way to fill a room. The group booking a birthday, the couple choosing an anniversary dinner, the parents in town for a Reed or PSU weekend, all of them arrive through a search that a named page can win and an unnamed one cannot.

A diner who reads the menu before choosing the neighborhood

Portland has an unusually informed eater. People here know what is in season, know the names of the farms at the Saturday market at PSU, want to know where the oysters and the pinot came from, and read the menu before they leave the house. That is a gift to a restaurant whose online presence speaks that language and a liability to one whose site is a hero image and a reservation widget. When the pages name the farms, the region and the seasonal changes, the restaurant matches the exact intent of a diner who cares about the carrots. A generic site throws that advantage away and lets a chain with a tidy listing outrank it.

The visitor matters too. Summer brings people off the food-cart circuit and out-of-towners who do not know Division from Hawthorne, all searching blind. Content written for the way they search, what is near the hotel, what is worth the trip across the river, is how a kitchen on the east side gets found by someone staying downtown.

Name the farm on the page, not just the chalkboard

The sourcing story is usually the best content a farm-to-table restaurant has, and it usually lives on a chalkboard, a server’s script and a social post that disappears in a day. Put on the website, as real pages that describe the farms, the seasons and the dishes they become, it does two things. It gives the diner a reason to choose you that no competitor can copy, and it gives the search engines something specific to rank you for besides the word restaurant. Pages that rank for a kind of cooking in a part of Portland are written by people who do that cooking, and it shows. That is the heart of SEO for a restaurant like this one.

The menu itself is the most-read page and the most neglected. It should be live, as text, with prices, updated when the kitchen changes it, readable on a phone in the rain. A photograph or a PDF is invisible to the search engines and hostile to the diner. This is a build problem: a website built for a restaurant makes the menu the easiest thing on the site to change, so the chanterelles show up online the day they show up on the pass.

Summer patios and the long wet season

Where owners get this wrong is in treating the website as something finished at opening. The site goes live, the menu gets uploaded once, and the restaurant’s actual life, the seasonal shifts, the Dungeness crab in December, the first asparagus, the patio opening in May, never reaches it. Local SEO for a restaurant is the opposite: a site kept as current as the menu, tuned to each stretch of the year, with the hours honest and the reservations path working on a phone. A slow site that grinds while a photograph loads sends the diner back to the list to pick a different pin, and the search engines read that bounce as a vote against you. Speed and search visibility are the same project.

How North Sea helps

We build fast websites for restaurants and grow their search visibility, and we know how crowded Portland’s dining is. For a farm-to-table kitchen that means a live menu the search engines can read, sourcing content that ranks for what an informed Portland diner searches, neighborhood pages that fill the weeknights, and a reservations path that works in the rain. You run the kitchen. If you want the sourcing to sell the table before the diner arrives, start a project with North Sea Strategic.