How to Read Your Restaurant's Google Search Console (in Plain English)

Google Search Console is free, official, and tells you exactly which queries Google shows your restaurant for, how often visitors click through, and which pages are working. The interface is the problem. It's built for SEO professionals; the labels assume terminology a restaurant operator doesn't have.

You're thinking: I already have Google Analytics. Yes. And it tells you what they did once they got there. Search Console is what they typed before they got there. Different question.

This is the plain-English version. Four reports do the work. Skip the rest.

Set it up first (10 minutes, one time)

Go to search.google.com/search-console, sign in, add your domain. Verify ownership via DNS or via a meta tag your developer can drop in (most modern hosts have a one-click verification). Wait 24-48 hours for the data to populate.

If you've already been verified for a year and never logged back in, your account already has months of data — it's been collecting in the background.

Report 1: Performance — the headline numbers

This is the only screen most operators ever need. Four numbers across the top:

• Total clicks — how many people actually clicked through to your site from Google search.
• Total impressions — how many times your site appeared in any search result, whether anyone clicked or not.
• Average CTR — clicks ÷ impressions. The percentage of times your snippet won the click.
• Average position — your average rank across all queries that showed your site.

The leverage is almost always in CTR, not in position. A restaurant ranked #4 with a strong title + meta description outperforms a restaurant ranked #2 with a generic one. If your CTR for branded queries (your restaurant name) is below 40%, the snippet is broken — almost always the meta description. The pattern shows up sharpest when branded-query CTR is healthy (a customer searching for you by name finds you and clicks) but the cuisine-query CTR is in the low single digits. Same site. Same domain authority. Two different snippets — one written by a human who knows the room, one autogenerated from the page title.

Report 2: Queries — what people typed to find you

Below the headline numbers, click "Queries." This is the gold. Sort by impressions descending. The first 20-30 rows tell you exactly what Google thinks your restaurant is for.

What to look for:

• High-impression / low-CTR queries. These are queries Google thinks you should rank for but visitors aren't clicking. Almost always a snippet problem — the title or meta doesn't match what they expected.
• Surprise queries. Phrases like "best happy hour brookline" that you didn't deliberately target — those are clues for content you should add.
• Missing queries. If "tacos al pastor near me" doesn't appear at all, your menu schema is missing or broken.

The category of surprise queries worth watching closely: phrases Google has decided you might be relevant for, where you're already at page two without having tried. Adding a small section to the page — not a full pivot, just enough to acknowledge the query's intent — frequently moves position into clickable territory within a few weeks. Most of the time the gold isn't the queries you're trying to rank for; it's the queries Google has decided you might be for and you haven't met halfway.

Run the SEO Grader on the page that's getting the impressions but no clicks — it'll surface the title + meta issues directly.

The Queries report is the only place a customer's actual words land in your dashboard. Read it like a server reads a comment card.

Report 3: Pages — which pages are doing the work

Switch the tab from "Queries" to "Pages." Sort by clicks descending. The pattern most restaurants see:

• The homepage gets 60-70% of clicks.
• The menu page should get 15-25%.
• The reservation page typically gets 3-8%.
• Everything else is rounding error.

If your menu page is below 10% of total clicks, you have a menu-page problem — usually it's PDF (invisible to Google) or hidden behind a subdirectory that ranks badly. The fix is converting to a real HTML menu.

Report 4: Coverage / Pages indexed — the silent killer

In the left sidebar, under "Indexing," click "Pages." This tells you how many of your pages Google has actually added to its index. If 50% of your pages are "Excluded" or "Discovered — not indexed," you have a foundational problem — usually slow load, broken canonical tags, or thin content.

Run Restaurant Audit if this number looks bad. The audit's technical-SEO section diagnoses the most common indexing blockers.

The three weekly habits

1. Mondays — open Performance, look at week-over-week. Two minutes. If clicks dropped 20%+ week-over-week, something broke (Google update, site change, holiday weirdness). Investigate. Otherwise, close the tab.
2. First-of-month — sort Queries by impressions. Five minutes. Note any new queries appearing in the top 30. Decide whether to add content for them.
3. Quarterly — Pages report, sort by clicks. Ten minutes. The page distribution should match your business's actual conversion path. If it doesn't, you have content-architecture work to do.

Total weekly burden: under 20 minutes per month. Result: actionable signal you can't get anywhere else, including from any agency that "manages your SEO."

What Search Console doesn't tell you

Search Console only covers Google search clicks. It doesn't tell you about Google Maps clicks, Find a Table bookings, or AI-search citations from ChatGPT and Perplexity (those don't pass referrer headers). For the AI-search side, set up the FAQ schema mentioned in the AI article and watch your first-touch attribution in Plausible — that's where AI-driven visits show up.

Save the four-number screenshot to your Workshop monthly. The trend over six months tells the story; the single weekly check tells you when to investigate.

Position is what you can't easily move. CTR is what you can move on a Tuesday afternoon.