GBP, suburb pages, schema—what still works, what Google quietly killed.
Local SEO has two layers. There's the map pack—what shows in the three-business block at the top of results—and there's organic. Most businesses need both. They require different tactics.
In 2026, an optimised GBP beats a mediocre GBP in the map pack almost regardless of the website quality beneath it. That's changing as Google uses more page-level signals, but for now: if you're a Melbourne local service and your GBP isn't complete, that's the first fix.
What 'complete' actually means: primary and secondary categories accurate, business description using natural language (not keyword-stuffed), all services listed with descriptions, 20+ photos updated in the last 90 days, and review responses within 48 hours.
The mistake: creating a suburb page that's a copy of the homepage with the suburb name swapped in. Google sees this immediately and treats it as thin content.
Suburb pages earn rankings when they contain location-specific content: local landmarks used as distance references, real project examples from that area (even anonymised), the specific postcode range covered, and natural mentions of local context (a Richmond café fit-out reads differently from a Doncaster office).
“Five well-written suburb pages beat fifty templated ones. Every time. We've run this test on four client sites in the last year.”
LocalBusiness schema with accurate name, address, phone, and areaServed is still worth implementing. ServiceArea schema helps Google understand multi-suburb coverage. Review schema pulls from your GBP automatically if structured correctly.
Genuine review velocity. A plumber with 14 new reviews this month outranks one with 200 reviews last updated in 2023. Recency matters in local.
Core Web Vitals. Local service sites are often the slowest category of site. Page experience signals are a real tie-breaker at the margin.