Local Search for a One-Room Restaurant

Most advice about restaurant local search is written as though the mechanism were a secret. It is not. Google publishes what drives local ranking, names the three factors, and states plainly that there is no way to pay for a better one. The useful work is not guessing at the algorithm; it is doing the small number of concrete things Google actually names, and then making sure the website supports rather than contradicts them.

This is written for a single-location, chef-led restaurant. Multi-location groups have a different problem and deserve their own treatment.

What Google actually says

Google’s own help page, “Tips to improve your local ranking on Google”, is the primary document here, and it is short enough to read in full in a few minutes. It is worth doing that rather than relying on anyone’s paraphrase, including this one.

The three factors, in Google’s words

Google states that local results are based primarily on relevance, distance and prominence, and defines each.

Relevance is how well a local Business Profile matches what someone is searching for. Google’s suggested remedy is to add complete and detailed business information so it can better understand your business and match your profile to relevant searches.

Distance is how far each potential search result is from the location term used in a search. Where someone does not specify a location, Google says it will calculate distance based on what it knows about their location.

Prominence is how well known a business is, and Google says this is based on information it has about a business from across the web, such as links, articles and directories, as well as its position in its web results. Google names review count and review score as factors in local search ranking on the same page.

The sentence most advice leaves out

The same page states that there is no way to request or pay for a better local ranking, and that Google does its best to keep the details of the search algorithm confidential to make the ranking system as fair as possible for everyone.

That sentence rules out an entire category of offers a restaurant owner will be pitched. It does not rule out doing the work. It rules out buying the outcome.

Distance: the factor you mostly cannot change

Of the three, distance is the one a restaurant has the least leverage over, and understanding why saves a lot of wasted effort.

Why chasing a neighbourhood you are not in does not work

A restaurant three miles from a neighbourhood cannot make itself closer to it. The common response is to build a page targeting that neighbourhood’s name, which addresses relevance rather than distance, and usually addresses it badly: the page is near-identical to the page about the actual location, with a name swapped in.

Google’s guidance on creating helpful, reliable, people-first content is directly relevant here. It asks whether content provides substantial value when compared to other pages, and whether it is written primarily to attract search engine visits rather than to help people. A set of near-duplicate neighbourhood pages fails both questions for a single-location restaurant.

What to do instead

Write one genuinely good page about where you are. Not a paragraph with a map embed, but the page a person who has never been to the area would want: what the street is like, where to park, which transit stop is closest, what else is nearby, how long it takes to walk from the obvious landmark. That page is useful to a human being, it is not duplicated anywhere, and it says more about your location to a search engine than five thin pages naming five neighbourhoods.

Relevance: where the website does the work

Relevance is the factor where a website earns its place, because relevance depends on Google understanding what you actually are and what you actually serve.

Complete information, stated consistently

Google’s advice on relevance is to enter complete data: the profile’s category, attributes, hours, service options and description. That work happens inside the Business Profile, not on the website.

The website’s job is not to contradict it. If the profile says the kitchen closes at ten and the website says eleven, one of them is wrong and neither you nor Google knows which. The same applies to the business name, the address format and the phone number. This is the least glamorous item on this list and the one most likely to be quietly wrong.

Make the menu real text

This is the single largest thing a chef-led restaurant can do for relevance, and it is a website decision rather than a profile decision.

A menu published as a PDF or as an image is not page content in the way normal HTML text is. Google’s mobile-first indexing guidance is explicit that only the content shown on the version it crawls is used for indexing, and advises making sure the mobile site contains the same content as the desktop site.

The practical consequence: every dish name, every description of a preparation, every regional term your kitchen uses is either real crawlable text on a real page, or it is invisible to the search that would have matched it. A guest who searches for a specific dish, or for a style of cooking, or for a regional term your kitchen actually uses, can only find you if those words are text.

Describe the room, not just the food

Restaurants are searched for in ways that have nothing to do with dishes. People search for a room that suits an occasion, a size of party, a time of day. Relevance is served by having real pages that address those searches honestly: what the room is like, how many the largest table seats, whether the bar takes walk-ins, what service looks like on a Tuesday versus a Saturday.

This is not keyword work. It is writing down things you already know and that guests already ask, and it produces pages that are useful whether or not they ever rank.

Prominence: slow, real, and mostly not on your website

Prominence is the factor most often misrepresented, because it is the one that cannot be bought and takes the longest.

What Google names

Google describes prominence as based on information it has about a business from across the web, and gives links, articles and directories as examples. It also states that its position in web results is a factor, and that review count and review score factor into local search ranking.

Coverage is earned, not acquired

Links and articles from genuine local coverage, a guide, a food writer, a neighbourhood publication, a supplier’s site describing a partnership, are exactly the kind of information Google describes. They arrive because something worth writing about happened, not because someone bought them.

For a chef-led restaurant, the things that generate coverage are usually the things you are doing anyway: a new season’s menu, a collaboration, a supplier relationship worth explaining, a chef’s residency. The website’s job is to make each of those a durable page with a stable URL, so that when someone does write about it, there is something specific to link to rather than a homepage.

Reviews: read the policy yourself

Review count and score are named factors, which is why every restaurant owner is eventually advised to solicit reviews aggressively, sometimes in ways that violate policy.

Google’s prohibited and restricted content policy for user contributed content is the document that governs this, and it covers deceptive content, misrepresentation and other categories that operators need to understand before running any review campaign.

We are a website studio. We are not your compliance adviser, and the consequences of a policy violation land on your profile rather than on ours. Read the policy in full, decide what you are comfortable with, and if anything is ambiguous for your situation, ask someone qualified to advise you on it. What we will say is this: a restaurant that asks every departing guest a genuine question about their evening, and makes it easy for a guest who wants to write something to find where to write it, is doing something durable. A restaurant that offers a discount for a five star review is risking the asset it is trying to build.

Do not put invented numbers on your own site

A closely related trap: a site that displays a star rating, a review count or a customer number it made up. Beyond being dishonest, review and rating structured data has its own rules in Google’s documentation, and marking up ratings a business generated for itself is a known way to get a site into trouble. If you display reviews, display real ones. If you ever show a written example of what clients say, label it clearly as an example and do not emit rating markup for it.

Structured data: eligibility, not a guarantee

Structured data is where restaurant SEO advice most often overpromises.

What it does

Google’s local business structured data documentation describes how to mark up business details so they can be understood, including opening hours, address, and the menu for food establishments.

What it does not do

The same documentation is explicit that adding structured data makes a page eligible for a feature and that eligibility is not a guarantee of appearance. This is not a caveat buried in a footnote; it is how Google describes the whole mechanism.

That is still a reason to do it. Without the markup there is no eligibility at all, and the markup costs nothing recurring once it is generated from the same content the page already displays. It is a reason to be suspicious of anyone who promises a specific rich result as a deliverable.

Generate it, do not hand-write it

The failure mode with restaurant structured data is drift: the markup says the kitchen closes at ten and the page says eleven, because someone updated one and not the other. Google’s general structured data guidelines require that markup represent the content actually visible on the page.

A site that generates its markup from the same source the page renders from cannot drift. A site where the markup is a hand-maintained block of JSON in a header will drift, usually within two seasons.

Speed and mobile: the part that is not about search at all

Speed belongs in a local search discussion for a reason that has little to do with rankings.

Someone searching for a restaurant is frequently standing on a street, on a phone, on a poor connection, deciding between two options. A page that takes several seconds to show anything readable loses that person regardless of what position it held in the results. The search work got them to the door; the page decides whether they come in.

Mobile-first indexing makes the same page the one Google evaluates, so the fast, complete, readable mobile page is serving both purposes at once. This is the argument for treating the mobile menu page as the primary artefact of a restaurant website rather than as a shrunken version of the desktop one.

The handful of pages that carry the traffic

A restaurant website usually has between eight and twenty pages, and a small number of them carry most of the real traffic. Knowing which ones changes where the effort goes.

The menu page is the destination

For a chef-led restaurant the menu is almost always the most visited page after the home page, and frequently ahead of it, because people arrive at it directly from search and from links other people share. It is the page a guest opens at the table when deciding whether to book, and the page a friend sends to another friend.

That has three consequences. The menu page needs its own stable URL rather than being a tab on the home page, because a tab cannot be linked to or shared. It needs to load fast standing alone, not only after the home page has warmed the cache. And it deserves more typographic care than any other page on the site, because it is where the writing the kitchen agonised over actually gets read.

The hours and location answers

The second cluster is not really one page: it is a set of questions people arrive with. Are you open tonight. Where exactly are you. Do you take walk-ins. How do I book.

These get answered badly by default, because they are usually scattered across a footer, a contact page and a booking widget. A restaurant site does better by answering each one in plain text, in the place a person lands, rather than making them navigate. Hours in the footer of every page. The address as text, not only as a map embed, because a map embed is a picture to anything that cannot run it. The booking route stated in words before the widget loads.

Everything else is a long tail

The remaining pages, the story of the kitchen, the private dining page, the supplier notes, the articles, individually see modest traffic. Collectively they do two things worth the effort: they give coverage somewhere specific to link to, and they answer the searches that are too specific for the menu page to catch. Neither shows up in a weekly traffic screenshot. Both show up over a year.

Measuring without fooling yourself

Local search work is slow, which makes it unusually easy to misread.

Rank checking on your own phone is not a measurement

Searching for your own restaurant from your own phone, in your own restaurant, tells you almost nothing. Distance is one of the three named factors, and you are standing at zero distance. Your account has history with your own business. The result you see is the result nobody else sees.

If you want a sense of position, use a tool that reports from a specified location rather than from your pocket, and accept that the number it gives is an approximation of a personalised, location-dependent result rather than a fixed fact.

What to watch instead

Three things are more honest and more useful than a rank number.

The first is whether the pages you care about are actually indexed, which is a binary you can check directly in Search Console rather than an estimate. A menu page that is not indexed cannot rank, and that is a fixable problem hiding behind a disappointing rank report.

The second is which queries actually bring people to the site, as opposed to which queries you assumed would. This is where a chef-led restaurant usually finds something surprising, because guests search for a dish, a preparation or an occasion in words nobody inside the building would have chosen.

The third is what happens after arrival: whether people reach the booking step at all. A restaurant with good visibility and a booking flow that fails on a phone has a conversion problem wearing a search problem’s clothes, and no amount of additional visibility fixes it.

Give it a season

The most common error is judging local search work on a two-week window. Prominence in particular accumulates from things Google finds across the web over time, and a restaurant that changes its site, its profile and its approach every month never lets any of it settle. A season is a reasonable minimum before deciding whether something worked.

A sequence that works

If a restaurant owner asks where to start, this is the order we would give.

Claim and complete the Business Profile, filling in every field Google offers, because relevance is explicitly tied to completeness. Make the website’s business information identical to the profile’s, character for character where formats allow. Publish every menu as real HTML text on a real page, with a stable URL. Write one honest page about the location and one about the room. Give every notable event, collaboration or seasonal change its own durable page so coverage has somewhere to point. Generate structured data from the page content rather than maintaining it separately. Make the mobile page fast enough that a person on a street corner waits for it.

Then leave it alone long enough to mean anything. Prominence in particular is a slow signal, and a restaurant that rebuilds its site every four months never accumulates any.

What we do and what we do not

We build and manage the website. That covers the menu as structured text, the location and room pages, durable URLs for events and seasons, generated structured data, and the speed work that makes the mobile page usable on a street corner.

We do not manage your Business Profile’s policy decisions, we do not advise on review solicitation beyond pointing you at the policy, and we do not sell rankings, because Google states they cannot be sold. What we can do is make sure that when the factors Google names are working in your favor, the page they land on is the best one your kitchen could have.