Google Search Console for Local Businesses: The Local SEO Playbook

Most local businesses treat Google Search Console (GSC) as a vanity dashboard. You log in once a month, glance at the clicks line, notice it's roughly flat, and close the tab. If you're a plumber, a dentist, a restaurant owner, or a marketer running a multi-location law firm, that habit is leaving money on the table. GSC is the only place where Google shows you, for free, the exact words real people typed before they landed on your website — including the city names, "near me" phrases, and service terms that drive local demand.

The catch is that GSC was not built with local businesses in mind. It reports on organic web results, not the map pack, and its default views bury the most useful local insights under thousands of rows. To get value, you have to know how to slice the Performance report by location, how to write regex query filters that isolate "near me" and city-name patterns, and how to spot the "[service] + [city]" queries where you rank on page two and could rank on page one with a single new landing page.

This playbook walks through that advanced local workflow step by step. We'll be precise about what GSC can and can't tell you, give you copy-paste regex you can drop straight into your own property, and show how each report maps to a concrete local SEO action. If you're new to the tool overall, start with our complete Google Search Console guide, then come back here for the local-specific tactics.

GSC Complements Google Business Profile — It Doesn't Replace It

The first thing to understand is the division of labor between Google Search Console and Google Business Profile (GBP, formerly Google My Business). They measure two different surfaces and you need both.

Google Business Profile owns your presence in the local pack (the three-result map box) and Google Maps. Its Performance insights tell you how many people called, requested directions, or clicked through from your map listing, and which search terms surfaced your profile in Maps. That data is about your listing.

Google Search Console owns your presence in the classic organic web results — the blue links below (and sometimes above) the map pack. It tells you which of your website's pages appeared, for which queries, how often, in what average position, and how many clicks each earned. That data is about your site.

A local searcher often sees both surfaces on the same results page: the map pack near the top, your service page ranking organically a few results down. GBP tells you how the listing performed; GSC tells you how the page performed. Optimizing one does not automatically fix the other. The workflow in this guide is entirely about the GSC half — your website's organic footprint for local queries.

Important accuracy note: GSC does not report map-pack or local-pack rankings. The "Average position" you see is the position of your website page in organic web results. If you want map-pack visibility data, that lives in Google Business Profile insights, not here.

Reading the Performance Report Through a Local Lens

Open the Performance > Search results report and you'll see four metrics: Total clicks, Total impressions, Average CTR, and Average position. For local work, two habits make this report far more useful.

First, lengthen the date range and add a comparison. Local search is seasonal, and 28 days hides the pattern. Set the range to the last 12 months, or compare this quarter to the same quarter last year. Clicks are the metric that matters most because a click is a real person arriving on your site — impressions without clicks usually mean you ranked too low to be seen, or your title didn't earn the tap.

Second, always work inside a filter. The unfiltered view mixes branded searches, irrelevant queries, and every city you serve into one blurry average. The real insights appear when you filter down to one location, one service page, or one query pattern at a time. For a deeper tour of every metric and tab, see our Performance report breakdown.

Breaking Performance Down by City and Region with Regex

This is the single highest-leverage move for a local business in GSC. Switch the Query filter from "Queries containing" to "Custom (regex)" and you can carve your traffic into the cities and intent patterns that actually matter.

Regex in GSC uses the RE2 syntax and matching is case-insensitive by default. Here are copy-paste patterns you can adapt by swapping in your own town names and services.

# Any query that ends in "near me"
near me$

# Any query containing one of your service cities
(austin|round rock|cedar park|pflugerville|georgetown)

# "near me" OR a city name — your full local-intent bucket
near me$|(austin|round rock|cedar park|pflugerville)

# A specific service paired with any of your cities
(plumber|plumbing|water heater).*(austin|round rock|cedar park)

# Emergency / urgent intent (high commercial value for trades)
^(emergency|24 hour|24/7|same day) .*

# Strip out your own brand so it doesn't skew the numbers
^(?!.*(your brand name)).*

Apply near me$|(your|city|list) as the query filter and the entire report — clicks, impressions, position, and the Pages, Countries, and Devices tabs — now reflects only your local-intent traffic. Compare that bucket month over month and you're tracking the demand that converts, not noise.

For multi-location businesses, run the city-group regex once per region to see which metro areas are pulling their weight. A dental group with offices in five suburbs can instantly see that one location's pages earn 80% of the clicks while another barely registers — a clear signal of where to invest.

If you want the full reference on building, testing, and debugging these expressions, our Google Search Console regex filters guide covers every operator with local examples.

Finding Which Service Page Ranks for Which Town

The reverse view is just as valuable. Go to the Pages tab, click one of your location or service pages to filter by it, then switch to the Queries tab. Now you see every search term that page actually ranks for.

This surfaces two common problems. The first is keyword cannibalization — two or more pages ranking for the same "[service] [city]" query, splitting clicks and confusing Google about which to rank. The second is mismatch — a page you built for "emergency plumber Cedar Park" that actually pulls most of its impressions for a neighboring town you never optimized for, telling you to either build that town its own page or fold the demand in.

Here's a simple way to map the relationship across a small multi-location site:

| Landing page | Top query (by clicks) | Avg. position | Action | |---|---|---|---| | /plumbing-austin | plumber austin | 4 | Hold; strong, monitor seasonally | | /plumbing-round-rock | plumbing round rock tx | 6 | On-page tune to push into top 3 | | /water-heater-repair | water heater repair near me | 11 | Striking distance — add internal links | | /plumbing-austin | plumber pflugerville | 14 | Build a dedicated Pflugerville page |

That last row is the tell: a single page absorbing demand for a town it doesn't target is a page-two ranking waiting to become a page-one ranking once it has its own home.

Spotting "[Service] + [City]" Striking-Distance Queries

Striking-distance queries are the ones sitting in average positions roughly 8 through 20 — page two and the bottom of page one. They already have impressions, so Google considers you relevant; they just need a nudge to climb into clickable territory. For local businesses, these are usually untapped "[service] + [city]" combinations.

To mine them, filter the Performance report to your local-intent regex (the patterns above), set a long date range, sort by impressions, and scan for any query with a decent impression count and an average position in the 8–20 band. Each one is a candidate for either an on-page tune or a brand-new location/service landing page.

A practical pattern for trades and clinics: if you find five or six queries like "[service] + [nearby town]" all ranking around position 12–15 on a single generic service page, that's your signal to spin up dedicated, genuinely useful pages for each town — with local content, real service-area detail, and proper internal links from your main service hub. Our deep dive on striking-distance keywords in Google Search Console shows how to prioritize them by opportunity, and our guide to using GSC for keyword research explains how to expand a single winning query into a full content cluster.

Fixing Low-CTR Local Title Tags

Sometimes the problem isn't position — it's that you rank well and still get few clicks. In the Performance report, look for queries or pages with high impressions, an average position in the top 5, and a noticeably low CTR. For top-of-page positions, click-through rates commonly land in the double digits; when a position-3 or position-4 local query is converting in the low single digits, your title tag and meta description are the likely culprits.

Local searchers scan for trust and proximity signals. Title tags that win local clicks usually include the city or service area, a trust marker (years in business, "licensed," "family-owned"), and where appropriate a call to action or differentiator ("Same-Day Service," "Free Estimates"). A generic "Plumbing Services | Acme Co." loses to "Emergency Plumber in Round Rock, TX | Same-Day Service" almost every time.

Rewrite the title and description, redeploy, then watch CTR in GSC over the following few weeks against the prior period. It's one of the fastest, lowest-effort wins available to a local site. For a structured approach with more examples, see how to fix low CTR in Google Search Console.

Tracking Seasonality

Local demand swings with the calendar — HVAC repair spikes in summer and winter, tax law firms peak in spring, restaurants ride holidays and local events. GSC's 16-month data window lets you see these rhythms instead of reacting blindly.

Filter to a seasonal service with regex (for example (ac repair|air conditioning|hvac).*(your city)), set the date range to 16 months, and watch the impressions and clicks curve. Now you can publish and promote seasonal landing pages ahead of the spike rather than during it, because pages need lead time to rank. Use last year's curve to schedule this year's content calendar.

Find your local opportunities automatically. Search Console Tools connects to your GSC property through Google OAuth and surfaces your local striking-distance keywords and low-CTR pages for you — no regex required. It's free, and it turns the workflow in this guide into a ready-to-action list of content briefs.

Frequently Asked Questions

Does Google Search Console show my Google Maps or local pack ranking?

No. GSC reports only on classic organic web results — the blue-link listings. Your average position there reflects your website page, not your map-pack or Google Maps position. For map and local pack performance, use Google Business Profile insights instead.

Do I still need Google Business Profile if I use Google Search Console?

Yes, you need both. Google Business Profile manages your map listing, calls, and direction requests, while Google Search Console measures how your website pages perform in organic search. They cover different surfaces of the same results page and optimizing one does not fix the other.

How do I see "near me" searches in Google Search Console?

Open Performance > Search results, set the Query filter to Custom (regex), and enter near me$ to match queries ending in that phrase. You can combine it with city names using near me$|(city1|city2) to capture your full local-intent traffic in one view.

What's the best way to find new local landing pages to create?

Filter the Performance report to your local-intent regex, sort by impressions, and look for "[service] + [town]" queries ranking in average positions roughly 8 to 20 on a page that doesn't specifically target that town. Each one is a striking-distance opportunity worth a dedicated, genuinely useful location page.

Why does my local page rank in the top 5 but get few clicks?

A high impression count and good position with low CTR usually points to a weak title tag or meta description. Local searchers respond to titles that name the city, include a trust signal, and state a clear offer, so rewriting them to add proximity and trust markers often lifts clicks within a few weeks.

How far back does Google Search Console data go for tracking seasonality?

GSC retains up to 16 months of Performance data. That's enough to compare this year's seasonal demand curve to last year's, so you can publish and promote seasonal local pages ahead of the spike instead of reacting after it has already started.