Local SEO in a map pack that keeps shrinking

The shrinking pack

Category-qualified 3-packs are common — a search for 'HVAC Austin' returns three cooling-focused results, while 'HVAC repair Austin' can return three different results focused on repair rather than installation. Multi-service businesses now compete for slots per service, not per business.

We split GBP strategy by service line for every multi-service client. That means primary category chosen to match the highest-margin service, secondary categories that reflect the actual service menu, a services list with pricing indicators where available, and posts weighted toward the service line that needs the most visibility that month.

The consequence: a two-location shop with three service lines effectively has six GBP surfaces to optimise (two locations × three service qualifiers). That's a real workload, and it's why we operationalise GBP as a weekly channel rather than a monthly checkbox.

GBP as a ranking asset

Weekly posts, monthly Q&A, product and service taxonomy tuned to actual booking language, category primary/secondary review every quarter, and photos updated at least monthly. Photos are underrated: profiles with fresh imagery from the last 30 days rank measurably higher in our tracked data than profiles with stale libraries.

The posts don't need to be marketing. The posts that perform best in our data are operational — 'we serviced 47 systems in Round Rock last week, here's the most common failure we saw' — because they carry entity and topical signals that Google's local systems seem to reward. Marketing posts (offers, promotions) perform fine for CTR but don't move the ranking.

The single biggest GBP lever most clients ignore: the Services tab. Populate it with every service you actually deliver, with clear descriptions and pricing indicators. This is now a ranking factor for service-qualified queries, and it takes an afternoon to set up.

Review velocity beats review count

A business earning 8 reviews a month with a mid-quality baseline outranks a business with 400 reviews and no fresh flow. Velocity matters more than volume, and freshness matters more than average rating within the 4.3–4.9 range.

Build the request into the fulfilment step, not the invoice. A polite ask from the technician who just finished the job earns reviews at roughly 4× the rate of an emailed request from the office. If the technician mentions Google specifically and offers to text the review link, the rate roughly doubles again.

The mistake we see most often: batch-requesting reviews before a big audit or a launch. Velocity spikes look artificial and can trigger filtering. Steady weekly velocity is what compounds. Boring beats clever.

Neighbourhood-level content

City pages are table stakes. Neighbourhood pages — real content, real photos, real reviews from residents of that neighbourhood — are the differentiator in dense metros like Austin, Dallas, and Houston.

For our Austin clients, that means dedicated pages for South Austin, East Austin, Round Rock, Cedar Park, Pflugerville, Georgetown, and the neighbourhoods within each — Barton Hills, Zilker, Mueller, Hyde Park. Each page has genuine local content: landmarks, common local issues (e.g., HVAC pages for a hot-attic neighbourhood mention that specifically), photos of local jobs, and reviews from residents of that area.

The competitors who ship 40 auto-generated city pages get filtered. The ones who ship 12 neighbourhood pages with real content earn rankings across all of them, including secondary and long-tail queries that the auto-generated pages never touch.

Local schema and NAP consistency

LocalBusiness schema (or the specific subtype — HVACBusiness, AutoRepair, Dentist, etc.) on the homepage and every location page. NAP (name, address, phone) that exactly matches Google Business Profile, character for character. Hours that exactly match GBP. sameAs to the GBP URL, plus verified profiles on Yelp, BBB, and any relevant industry directories.

Mismatched NAP is the most common quiet ranking killer we find in audits. A comma before the ZIP on the website that isn't on GBP, or a phone number formatted with parentheses on one and dashes on another, can be enough to slow entity resolution. Fixing this is free, fast, and disproportionately impactful.

A weekly operating rhythm

GBP posts Monday, Q&A audit Tuesday, review outreach Wednesday, competitor pack scan Thursday, weekly report Friday. That's it. Consistency beats cleverness.

The weekly report doesn't need to be long. Three numbers: local pack rank for the top-5 tracked queries, review count and velocity, and calls/leads attributed to GBP. If those three numbers are trending correctly, the underlying work is working. If they aren't, the report tells you which one to dig into.

The rhythm sounds trivial. It isn't. The businesses that hold local rankings do this every week without fail. The ones that don't lose ground quarterly to competitors who do.

The Austin lens

Austin's local market has two peculiarities worth naming. First, the metro is geographically large and functionally distinct — a Round Rock customer is not the same as a South Austin customer, and generic 'Austin' pages under-serve both. Second, seasonality is real: HVAC demand spikes in June through September, home services demand shifts around SXSW and ACL, and the tax/legal/real-estate cycle follows Texas state calendars.

Local content that reflects these patterns — a South Austin HVAC page that acknowledges older housing stock, a Round Rock roofer page that addresses the hail belt, a Cedar Park pool service page that reflects new-build density — earns rankings and calls in a way generic 'Austin' pages don't.

If you're planning your 2026 local budget, allocate 30% to GBP operations, 30% to neighbourhood content, 20% to reviews infrastructure, and 20% to local schema and citation cleanup. That mix has produced the most reliable results across our Austin engagements over the last two years.